Once you’ve ensured everything looks good go ahead and click Create User. This next step is important, as you’ll be given your Access and Secret keys. Check the box next to the AmazonS3FullAccess option and move on to the next page. Here, you’ll select the box for Attach existing policies directly, and filter for AmazonS3FullAccess. Ensure that you check the box labeled Programmatic Access to be able to generate the proper keys to connect to your S3 buckets. For Username you can choose whatever name you would like to use with Cyberduck (e.g. Once on the IAM page, select Users and then the blue Add User button. Under Services in the AWS Console, in the Security, Identity, and Compliance section navigate to IAM. Now that the new bucket is created, we’ll need to create an IAM User for Cyberduck to be able to connect to your S3 account and manipulate your buckets and objects within. This validation file will be used by WP Engine Support to confirm your bucket is configured properly.

largefs) found in the root of your old bucket and upload it into the new bucket with Public-Read permissions. Once your bucket is created, you’ve enabled static website hosting, and configured your bucket policy, download the LargeFS validation file (ends with. First, you’ll need to create your new bucket in the region that you’d like via the AWS Console following the Setup Guide on WP Engine.

Cyberduck s3 set permissions