I tried to use s3cmd to set policy of a space. The policy file is like:
{
"Statement": [
{
"Sid": "Allow get requests referred by localhost",
"Effect": "Allow",
"Principal": {
"AWS": "*"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::my-bucket/policy/*",
"Condition": {
"StringLike": {
"aws:Referer": [
"http://localhost:8080/*"
]
}
}
}
]
}
and then run
s3cmd setpolicy policy s3://my-bucket
The command run without error, but when get the info:
s3cmd info s3://my-bucket
It showed there is no policy on this space:
s3://my-bucket/ (bucket):
Location: sgp1
Payer: BucketOwner
Expiration Rule: none
Policy: none
...
And I still can not access the private file at localhost.
Does space support setpolicy or I done something wrong?
Subscribe
Share
Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Sign in to AnswerThese answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
Here is my bucket policy.json create from AWS S3 and It work with DO Spaces. Don’t forget to change to your bucketname and your domain.
{
"Version": "2017-10-17",
"Id": "http referer policy example",
"Statement": [
{
"Sid": "Allow get requests originating from www.yourdomain.com and subdomain.yourdomain.com.",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::yourbucketname/*",
"Condition": {
"StringLike": {
"aws:Referer": [
"https://www.yourdomain.com/*",
"https://subdomain.yourdomain.com/*"
]
}
}
}
]
}
My DO spaces is in nyc3 region. Also I just try setpolicy with sgp1 region. It’s work. Here is the bucket info. Notice : It seem sgp1 region have some problem, the connection fail many times. Hope DO staff will check and solve this problem.
This comment has been deleted
Try to create policy.json instead policy and run s3cmd setpolicy policy.json s3://my-bucket If still don’t work recheck the policy.json path is correct.
It’s work for me.