This is a technical post for users that are familiar with AWS EC2.
When you are launching an EC2 instance you can assign it with an IAM role with specific permissions to AWS resources. This enables you to use security credentials on EC2 to access S3 that are temporary and rotated automatically. Refer to IAM Roles for Amazon EC2.
We have now added a login option to the current snapshot builds of 4.7 available through a connection profile that allows to connect from EC2 with Cyberduck on Windows or the CLI version on Linux instances with IAM role credentials obtained from instance metadata.
The S3 (Temporary Credentials) profile can be installed from the wiki. See Connecting with temporary access credentials from EC2. Make sure to edit the role name in the profile to match your IAM configuration.
We think this will make deployments of the duck to EC2 a lot easier without the need to distribute credentials along with.
The latest snapshot and beta builds of Cyberduck for Mac & Windows now support lifecycle configuration for S3 buckets. One can specify after how many days a file in a bucket should be moved to Amazon Glacier or deleted.
The latest snapshot build of Cyberduck for Mac & Windows allows the configuration of server side encryption for files in Amazon S3. Server side encryption provides you the ability to encrypt data stored in Amazon S3. You can encrypt data on upload simply by selecting AES256 as the default encryption algorithm for uploads to S3 in the Preferences or selecting the checkbox in the Info panel for data already uploaded. Decryption happens automatically when data is retrieved.
Amazon now supports hosting static websites on S3. The latest snapshot build of Cyberduck supports configuring website distributions for S3 buckets.
Update: You can now also configure Website Configuration Endpoint Distributions with CloudFront CDN.
Configuring a bucket in S3 to make its content available through the Amazon CloudFront CDN (Content distribution network) was always most straight forwarded in Cyberduck. Both distributions for static files and streaming can be configured using the Distribution tab of the Info panel when connected to your S3 account with a snap.
Because Amazon has now lifted the requirement to upload your content to S3 to make it available in CloudFront, their powerful CDN feature can now be used with any server used as the origin source for content. This is especially useful for content generated only on demand or where your workflow just doesn’t allow to upload content additionally to S3.
As of the latest beta and snapshot builds of Cyberduck, you can connect to any server using FTP or SFTP and configure it as the origin of a new Amazon CloudFront CDN distribution. We expect this to make CloudFront a lot more popular for users that are tied to existing server resources but want to make us of content distribution in the cloud.
Detailed usage instructions can be found in the help wiki. Give it a try!
Amazon S3, the cloud storage service Cyberduck can connect to, supports a versioning feature. This allows to revert to previous revisions of a file replaced in S3. The latest snapshot build of Cyberduck supports versioning in S3 in the following way:
- Toggle the versioning status using File → Info → S3
- Display previous versions and deleted files in the browser using View → Show Hidden Files. Past revisions are displayed in a grey text colour and can be downloaded or permanently deleted like regular files.
- Revert files to a previous version using File → Revert or the Browser context menu.
- Optionally enabling Multi-Factor Authentication (MFA) Delete
In addition to the existing cloud storage providers Amazon S3 and Rackspace Cloudfiles, support for the recently announced Google Storage is on track. Interested parties having access to the currently invite-only service in Google Labs are welcome to give it a try using the latest snapshot build of Cyberduck.