You can read more about Bucket Explorer & AWS Import Export Service on this link:
http://www.bucketexplorer.com/documentation/amazon-s3–aws-import-export-service.html

You can follow updates of Bucket Explorer at twitter too:
http://twitter.com/bucketexplorer

http://developer.amazonwebservices.com/connect/message.jspa?messageID=128502#128502

In the current release of Bucket Explorer, we save (automatically) a copy of the older version in a special bucket, every time a file is re-uploaded with the same name (& different content) again.  This functionality will be deprecated when Amazon starts supporting versioning natively in S3 API.

Until then, I believe we are the only one who support versioning, without changing file name or breaking the files in smaller propertiary chunks.

Amazon’s announcement:

http://developer.amazonwebservices.com/connect/ann.jspa?annID=440 

Our announcement in Amazon forums:

http://developer.amazonwebservices.com/connect/thread.jspa?threadID=31605&tstart=0

You can downlaod the latest release from http://www.bucketexplorer.com/be-download.html

Just to refresh, we have added many features in past few months which can help CloudFront users:

1. Create new Cloud-Front distributions.

2. Manage existing distributions (edit, update, delete).

3. Map CNAME entries to Cloud-Front Distributions.

4. Set logging on a distribution. All access logs are collected in a S3 bucket specified by the user when enabling the logging feature.

5. Update ACLs in bulk / batch mode to change ACLs on a few to several million files in a bucket.

6. Update meta-data to add content headers in bulk / batch mode on a few to several million files in a bucket.

7. Bucket Explorer can automatically set user defined default headers on all files uploaded in a bucket.

8. Bucket Explorer can automatically set user defined default ACLs on all files uploaded in a bucket.

9. An easy to use comparer tool, which can help in comparing data between two buckets or between a local folder and a bucket. Makes it easy to keep track of changes and commits from local machine to a bucket.

10. Bucket Commander enables you to automate bucket backups. A CloudFront bucket can be backed up to another S3 bucket or to a local disk automatically on schedule using Bucket Commander.

11. Bucket Explorer allows copying / moving data between two buckets. You can use this feature to keep a staging bucket in one S3 account, where a designer can upload the content and then move it to production buckets using Bucket Explorer.

12. Bucket Explorer automatically keeps older versions of files when different content with same name is uploaded to a bucket. The existing file is automatically moved to a version bucket before it overwrites it.

13. Bucket Explorer automatically moves all deleted files from a bucket to a “trash” folder. The files are not permanently deleted until the user wants to do so.

Thanks

Saurabh

Another big improvement is a new feature to compare only name & file size, instead of hash of entire file. This should make incremental backups faster (much faster).

More details about this release can be found here ->

http://www.bucketexplorer.com/documentation/amazon-s3–bucketexplorer-2009.04.html

All comments on this blog are closed. For any feedback, please use Bucket Explorer Support Forum.

Thanks

They also announced FREE SimpleDB trial for upto 2,000,000 queries per month, every month for next six months.
http://blog.sdbexplorer.com/2008/12/simpledb-2000000-free-requests-for-next-six-months/

What does this mean for Bucket Explorer?

We added “Audit Reports” in Bucket Explorer’s June 2008 release. Not many people have been able to use that since SimpleDB was in private beta. Now since its available to everyone, more Bucket Explorer users can choose the option the create Audit Reports in SimpleDB. This is especially useful for Team Edition, where you may need to track S3 usage by team members with whom you have shared your S3 account.

Another important feature, which our users should expect within next few months is “indexing of S3 meta data in SimpleDB”. This will make Bucket Explorer much more responsive when managing buckets with a large number of objects.

We have added support for all API operations related to CloudFront in Bucket Explorer. To use CloudFront, signup for cloudfront @ http://aws.amazon.com/cloudfront . You also need to be signed up for S3.

1. Upload your contents to S3, choose a bucket with same name as the CNAME you want to choose for the CloudFront CDN. This will allow you to switch between S3 & CloudFront, by just changing the DNS entry for the CNAME.

2.  Make all files in that bucket publicly readable using Bucket Explorer’s “ACL” button.

3. Use the new release of Bucket Explorer, which supports CloudFront and create a new cloudfront distribution for this new Bucket.

You can read more about these steps on our Introduction to ClodFront page and download the beta from there as well.

All comments on this blog are disabled. Please use our CloudFront forum to provide feedback.

Thanks

Saurabh

More details about changes in this version can be found at the release notes page:
http://www.bucketexplorer.com/documentation/amazon-s3–bucketexplorer-2008.11.html

You can download the latest release from our download page:
http://www.bucketexplorer.com/be-download.html

As always, all comments on this blog are disabled. Please use our support forum / contactus link to provide feedback.

We have made several improvements in the June release and have added some new features:

1. Preview of Team Edition. Using this release, now you can use Bucket Explorer and S3 to share buckets. We have a shared bucket feature in earlier versions, but that required multiple Amazon S3 accounts. The team edition works with a single S3 account and you don’t need to expose AWS credentials with every team member. Team Edition (along with commander will be focus of new improvements for new versions in next few months). So, send us your feedback and we will improve it.

2. Improvements in the commander for uploads and downloads.

3. “Trash” Bucket. Now we keep versions of all deleted files in a “trash” bucket. This is specially useful for Team Edition where you want to give all team members delete access but want to prevent data loss.

4. “Versions” - Now we automatically maintain older versions of the files in a “versions” bucket, when you upload a newer (changed) version and opt to overwrite the files.

5. Full Installer for Vista / XP, which respects Microsoft’s recommend folders for keeping config & logs. We no longer write log files & temp file to “Program Files” folder.

The “trash” and “versions” features combined take us one step closer to implementing a “sync” feature. If we can keep older versions during a sync process, both we and our users will be more confident in using sync.

We have made several other improvements in this release related to queue performance etc. We will be adding a detailed release notes page and documentation soon.

Here are the links to downlaod the beta. Remember - this is beta software.

<edit>Links updated - November - 4th </edit>

Windows Full Installer ->

http://downloads.bucketexplorer.com/win/Bucket-Explorer-2008.11.01.01-setup.exe

Windows Zipped / USB Version->

http://downloads.bucketexplorer.com/win/BucketExplorer2008110101.zip

Linux Version ->
http://downloads.bucketexplorer.com/linux/BucketExplorer2008110101.tar.gz

OSX Version ->

http://downloads.bucketexplorer.com/osx/BucketExplorer2008110101.zip

As always, comments on this blog are closed. You can use our forum to provide feedback, and subscribe to the blog if you want to get updates on new releases.

1. Support for “copy”, “rename” & “move”
2. Queueing and enhanced visualization of uploads, downloads, Copy, Move, Rename & deletes
3. Support for updating meta data on existing files.
4. Compare local files & folder with S3 files & virtual folders.
5. Enhanced Proxy Support for NTML proxy.
6. Command line version of Bucket Explorer-Bucket Commander
7. Run multiple instances on same machine
8. Audit reports using SimpleDB
9. Bucket Defaults to set default meta data and default ACLs.

More details on what’s new in this release can be found here ->
http://tinyurl.com/68wy67

This version is a free upgrade for all existing Bucket Explorer Users.

Saurabh

Comments are not enabled on this blog. Please use the forum if you want to provide any feedback

Amazon S3 does not have any concept for folders and files within a Bucket.  When we upload files to a bucket, we don’t need to create a “folder” on S3 to maintain a folder & sub-folder structure. We just use a “/” in file name and when displaying that file, we treat the first part of the file name as folder.

To upload empty folders, which don’t have any files in them, we used a naming convention which was used by a few other S3 client UIs at the time when we released Bucket Explorer 1.0.  We uploaded an empty file with extension _$folder$ to represent an empty folder.

In Bucket Explorer 2.0, we have changed that extension. Now empty folders will be uploaded using “/” at the end instead of “_$folder$”. We have also eliminated the need for these empty files for listing folder structure. You only need these files on S3, if there is an empty folder.

The result is that now you can use Bucket Explorer to explore files uploaded to S3 using virtually any S3 client, including support for Jungle Disk 2.0’s compatibility buckets.