3 Answers
- Newest
- Most votes
- Most comments
0
An empty bucket policy is fine. You should only make your objects public if you want everyone in the world to have access.
If you’re using a SageMaker notebook server, then when you created it you would have created (or used an existing) IAM role for it. You should check to see it’s S3 permissions, and make sure that it has access to the bucket in question.
Hope that helps.
answered 4 years ago
0
Looks like an issue with a policy attached to your role. Do you want to paste it in here so we can take a look?
answered 4 years ago
0
The bucket policy its empty, change the bucket to public access, but the files aren't public, think that the directories are public and files not. What suggest put in bucket policy??
answered 4 years ago
Relevant content
- Accepted Answerasked a year ago
- asked 7 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago