If you use containers for deployment (including Docker and Heroku), you should not store files within the container’s filesystem.
This integration allows you to delegate storing such files to Amazon’s S3 service.
|Your AWS access key.|
|Access Control List for uploaded files. By default, none is assigned.|
|The S3 bucket name to use for the media files.|
|The custom domain to use for the media bucket.|
|Enabling query parameter authentication from the generated URLs.|
|The number of seconds which a generated URL is valid for.|
|Your AWS secret access key.|
|The custom domain to use for the static bucket.|
|The S3 bucket name to use for the static files.|
Serving media files from an S3 bucket
"Media files" are the files uploaded through the dashboard. They include product images, category images, and non-image files. If you want to use S3 to store and serve media files, you need to configure at least the bucket name (see table above). A custom domain will allow you to use your CloudFront distribution or the public domain of your S3 bucket's static hosting. If you are experiencing problems accessing uploaded files, ensure that permissions are correctly configured (AWS_DEFAULT_ACL environment variable).
Serving static files from an S3 bucket
"Static files" are assets required for Saleor to operate. They include assets used in default email templates. If you also wish to use S3 for your static files, you need to configure at least the bucket name (see table above). A custom domain will allow you to use your CloudFront distribution or the public domain of your S3 bucket's static hosting.
Cross-Origin Resource Sharing
"AllowedMethods": ["GET", "HEAD"],
Refer to the AWS CORS documentation for more details.