AWS S3
Create the bucket
Section titled “Create the bucket”In the S3 console, create a general purpose bucket and note its region. Leave public access blocked, because Fileee uses signed URLs.
Create a credential
Section titled “Create a credential”Create an IAM user just for Fileee, and give it access to this bucket only.
- In the IAM console, create a user. It doesn’t need console access.
- Open the user, then go to Permissions > Add permissions > Create inline policy.
- Paste the policy from Connect a bucket, with
YOUR-BUCKETreplaced by your bucket’s name. - Create an access key for the user. The secret is only available when you create it, so copy it then.
Connect it
Section titled “Connect it”| Field | Value |
|---|---|
| Provider | AWS S3 |
| Bucket | Your bucket’s name |
| Region | Your bucket’s region, as eu-west-1 |
| Path-style URLs | Off |
Allow browser access
Section titled “Allow browser access”Run Apply for me, then Test. That policy includes the two CORS permissions it needs.
To add the rule by hand, copy it from How to set up. In the S3 console, go to General purpose buckets, choose your bucket, open Permissions, and choose Edit under Cross-origin resource sharing (CORS). Paste the rule and choose Save changes. See the AWS guide for more.
Public CDN links
Section titled “Public CDN links”CloudFront can serve just one prefix, using an origin path and a bucket policy limited to it, so a prefix in the same bucket should work. See Public CDN links.