PowerShell for Amazon S3

amazon_powershellAfter Jeffrey blogged about PowerShell snapin for GoGrid it did not take too long before a snapin for Amazon appeared.

Specifically, the folks at CloudBerry Lab who produce utilities for Amazon services have made available (for free!) 10 cmdlets for Amazon’s Simple Storage Service (S3):

  • Add-CloudFolder – Create new folder
  • Copy-CloudItem – Copy cloud item (file or folder) to the Destination
  • Get-CloudFilesystemConnection – Get connection to local file system
  • Get-CloudItem – List files and folder in current folder
  • Get-CloudRootFolder – Get root folders
  • Get-CloudS3Connection – Get S3 connection
  • Move-CloudItem – Move cloud item (file or folder) to the Destination
  • Remove-CloudItem – Remove cloud items (file or folder)
  • Rename-CloudItem – Rename cloud item (file or folder)
  • Select-CloudFolder – Get cloud folder. Must be used for getting folder for other commands as current folder.

As you can see, this basically lets you operate with the files on the Amazon side, and move/copy files to the services and back.

They have a nice (Norton Commander-like) UI as well, but it is great that they added PowerShell as it makes it much easier to automate storage management. E.g. you could create a script which would go through your local files and back up the ones you recently changed to the cloud – nice!

One piece of feedback I would submit is considering making the snapin a provider so you can treat your Amazon storage as just another file drive attached to your computer. To my test this would be much more natural.

Still, good job, and great to see yet another platform falling into the PowerShell realm! 🙂

You can read more about the cmdlets here and download them here.

Tags: , ,


4 Responses to “PowerShell for Amazon S3”

  1. 1 halr9000 November 15, 2008 at 11:01 pm

    Ooh, great find Dmitry!

  2. 2 AndreyS November 22, 2008 at 2:57 pm

    Dmitry, I am glad you liked our product! We are going to introduce some enhancements to CloudBerry Explorer PowerShell interface in the next release which is coming out next week. Thanks!

  3. 3 Dmitry Sotnikov November 24, 2008 at 2:10 pm

    Thanks Andrey! Looking forward to that. By the way, it occurred to me that you cannot actually go 100% provider because of PowerShell’s current limitation of not allowing to copy objects between providers. So cmdlets will be required even if you implement a provider as I recommended in my post above.

  1. 1 More Amazon S3 cmdlets and PowerPack « Dmitry’s PowerBlog: PowerShell and beyond Trackback on April 22, 2010 at 8:46 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

My Recent Tweets


The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

November 2008
« Oct   Dec »

%d bloggers like this: