Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NO_WRITE_ACCESS_TO_OUTPUT #4

Closed
harrisonford opened this issue Dec 10, 2020 · 1 comment
Closed

NO_WRITE_ACCESS_TO_OUTPUT #4

harrisonford opened this issue Dec 10, 2020 · 1 comment

Comments

@harrisonford
Copy link

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?

@harrisonford
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant