Skip to content

NO_WRITE_ACCESS_TO_OUTPUT #4

Closed
Closed
@harrisonford

Description

@harrisonford

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions