You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to run this example I get a weird "NO_WRITE_ACCESS_TO_OUTPUT: The provided data access role does not have write access to the output S3 URI" but I do have the roles needed.
When checking what goes in the API request I can see that:
And this is super weird because to the train/output file it adds a weird middle file with my ID followed by CLR and a random code. Checking the value of S3 train output uri it should be correct:
Nevermind, it's a weird Role and policy issue in AWS. The FULL ACCESS policies don't give the exact policy you need for the Comprehend. Better to use UI once to make a classifier and check the exact Role you need.
Hello!
When trying to run this example I get a weird "NO_WRITE_ACCESS_TO_OUTPUT: The provided data access role does not have write access to the output S3 URI" but I do have the roles needed.
When checking what goes in the API request I can see that:
"OutputDataConfig": { "S3Uri": "s3://comprehend-experiment-661346392611/train/output/661346392611-CLR-85826137aad9dca5c13352667268f0e0/output/output.tar.gz"
And this is super weird because to the train/output file it adds a weird middle file with my ID followed by CLR and a random code. Checking the value of S3 train output uri it should be correct:
train output = s3://comprehend-experiment-661346392611/train/output/
Do you know why this could happen?
The text was updated successfully, but these errors were encountered: