Amazon just announced support for CloudFront logging and again, Bucket Explorer is the first UI tool to announce support for Amazon’s new feature. We have uploaded a new version on our download page, which supports CloudFront Logging.
Our announcement in Amazon forums:
You can download the latest release from http://www.bucketexplorer.com/be-download.html
Just to summarize the new features we have added 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.