...
| Code Block |
|---|
{
"Version": "2012-10-17",
"Statement": [{
"Action": "s3:*",
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::<<Public-Media-Bucket>>",
"arn:aws:s3:::<<Public-Media-Bucket>>/*",
"arn:aws:s3:::<<Private-Media-Bucket>>",
"arn:aws:s3:::<<Private-Media-Bucket>>/*",
"arn:aws:s3:::<<3D-Files-Bucket>>",
"arn:aws:s3:::<<3D-Files-Bucket>>/*"
]
},
{
"Effect": "Allow",
"Action": "s3:ListAllMyBuckets",
"Resource": "arn:aws:s3:::*"
}
]
} |
Then, configure the 3D file storage with the following settings:
...
Settings Key
...
Possible Values
...
Description
...
AMAZON_BUCKET_NAME
...
A valid S3-Bucket name
...
Specify the name of the 3D file bucket
...
AMAZON_ACCESS_KEY
...
Any String
...
The Access Key of the IAM user that should be used to access the bucket
...
AMAZON_SECRET_KEY
...
Any String
...
The Secret key of the IAM user
...
AMAZON_REGION
...
An AWS Region
...
the Region of the S3 bucket
If you want to use AWS ec2 instance profiles for S3 authentication instead of specifying the access and secret keys, find and set the following variable:
| Code Block |
|---|
AMAZON_CREDENTIALS_PROVIDER=profile |
If static is used as a value, that application tries to login first using the provided access and secret keys. If it is set to profile, it assumes that the instance where it is running is already authenticated to the s3 api. Make sure, to set all access and secret keys to empty values for this:
| Code Block |
|---|
AMAZON_CREDENTIALS_PROVIDER=profile
S3_ACCESS_KEY=
S3_SECRET_KEY=
AMAZON_ACCESS_KEY=
AMAZON_SECRET_KEY= |