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.ĭetailed usage instructions can be found in the help wiki. This is especially useful for content generated only on demand or where your workflow just doesn’t allow to upload content additionally to S3.Īs 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. 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.īecause 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. Tagged aws, ec2, iam, s3 1 Comment Lifecycle Configuration for S3Ĭonfiguring a bucket in S3 to make its content available through the Amazon CloudFront CDN (Content distribution network) was always most straight forwarded in Cyberduck. We think this will make deployments of the duck to EC2 a lot easier without the need to distribute credentials along with. Make sure to edit the role name in the profile to match your IAM configuration. See Connecting with temporary access credentials from EC2. The S3 (Temporary Credentials) profile can be installed from the wiki. 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. Click the top bar and select 'Amazon S3' as the connection type. Click on the '+' symbol at the bottom left corner to create a bookmark. This enables you to use security credentials on EC2 to access S3 that are temporary and rotated automatically. Once Cyberduck is installed, we can create a bookmark. You should consider disabling the 'Use Keychain' option by default. There should be an option (and command line switch whenever the cli interface is improved on the GUI app) to deactivate saving history.
When you are launching an EC2 instance you can assign it with an IAM role with specific permissions to AWS resources. The username should not be auto-saved, unless the user has explicitly added it in the bookmark settings. This is a technical post for users that are familiar with AWS EC2.
0 kommentar(er)
