- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello,
Thank you for using sagemaker Ground-Truth. Usually this exception occurs when the labeling job is not able to access the S3 bucket, Assuming that the bucket is located in the same region and sagemaker full access policy[1] is attached to the role. Please verify below points.
- Please check if any bucket policy is attached, which is blocking or restricting access[2]
- Verify if any organizational SCP(service control policy) is setting a permission boundary on this account to prevent S3 access.[3]
Post checking these policies, please try to re-run the job. If you have any difficulty in verifying any of the above mentioned points or if you still run into issue, Please reach out to AWS Support[4] (Sagemaker), along with your issue/use case in detail and share relevant AWS resource names. We will troubleshoot accordingly by verifying relevant job logs.
[1] https://docs.aws.amazon.com/sagemaker/latest/dg/security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonSageMakerFullAccess [2] https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html [3] https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html [4] https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-casehttps://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case
Contenuto pertinente
- AWS UFFICIALEAggiornata 8 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa