3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 4 anni fa
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?
con risposta 4 anni fa
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??
con risposta 4 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa