Goal: I'm trying to deploy a simple labeling job inside SM Grount Truth where users can basically classify objects inside images.
Step-by-step problem:
- Create a fresh new s3 bucket in sa-east-1;
- Create a private workforce;
- While ensuring you're still on sa-east-1, create a label job by configuring the console crawler with a fully-access IAM role (all buckets, just for debbuging purposes) and set configurations up;
ERROR: s3 bucket not valid, Bad Request (Service: Amazon S3; Status Code: 400; Error Code: 400 Bad Request)
Sometimes, the error doesn't show - the configuration just works and the manifest is created - but I don't see any patterns in this error appearences. And, for some odd reasion, when it does not show any errors, it will eventualy show another error in the next page when we preview the jobs, where no images shows up.
I'm just too much stuck in a simple task. Yes, I have the right access on the aws account. Any suggestions?