Provider Permissions
The quick-start guides use broad permissions so setup can’t fail. Once everything works, you can narrow them. This page lists what each feature needs at your storage provider.
These lists come from the API calls the plugin makes. If a feature reports a permission error after you narrow a key, add back the permission it names.
Amazon S3
Replace my-bucket. The first statement is only needed for the wizard’s bucket list, and for creating buckets.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": ["s3:ListAllMyBuckets", "s3:CreateBucket"],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketPublicAccessBlock",
"s3:PutBucketPublicAccessBlock",
"s3:GetBucketOwnershipControls",
"s3:PutBucketOwnershipControls",
"s3:GetBucketPolicy",
"s3:PutBucketPolicy"
],
"Resource": "arn:aws:s3:::my-bucket"
},
{
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:GetObjectAcl",
"s3:PutObjectAcl",
"s3:AbortMultipartUpload",
"s3:ListMultipartUploadParts"
],
"Resource": "arn:aws:s3:::my-bucket/*"
}
]
}
Add these to the bucket statement for optional features:
| Feature | Actions |
|---|---|
Bucket CORS PRO | s3:GetBucketCORS, s3:PutBucketCORS |
Change Storage Class lifecycle rule PRO | s3:GetLifecycleConfiguration, s3:PutLifecycleConfiguration |
| Transfer Acceleration | s3:PutAccelerateConfiguration |
For CDN Cache Purge PRO on CloudFront, the keys also need cloudfront:CreateInvalidation on the distribution.
Google Cloud Storage
| Role | Use for |
|---|---|
| Storage Admin on the project | Listing and creating buckets, and everything else. Recommended for setup. |
| Storage Admin on one bucket | Everything for that bucket, including its public access, CORS, lifecycle, and Private Media. Type the bucket name in the wizard. |
| Storage Object Admin on one bucket | Uploading and deleting files only. Bucket settings, such as Private Media and Bucket CORS, won’t work. |
DigitalOcean Spaces
| Key | Use for |
|---|---|
| Full Access | Creating Spaces, bucket policies, Private Media, and Bucket CORS |
| Limited Access, Read/Write/Delete on a Space | Uploading and deleting in that Space. Limited keys can’t use bucket policies. |
Cloudflare R2
See Which token permission to choose.
S3-compatible providers
The key needs to read, write, list, and delete in the bucket. Private Media isn’t available, and Bucket CORS PRO also needs permission to change the bucket’s CORS configuration, if your provider supports it.
Who needs public access
Visitors, not the plugin, need to read your files.
| Delivery | Bucket must be public? |
|---|---|
| Straight from Amazon S3, GCS, Spaces, or an S3-compatible bucket | Yes |
| Cloudflare R2 | Through a custom domain or r2.dev |
| A CDN | Only if the CDN reads the bucket as a public visitor. CloudFront with OAC, and CDNs with S3 authentication, can read a private bucket. |