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
I have a IAM user with S3 write access privileges and a generic maven repository bucket (Buckets and objects not public) without any AWS Bucket Policy specified.
Why do I have to set the flag [Public Access Settings -> Manage public access control list (ACLs) -> Block new public ACLs and uploading public objects] to False for the deploy to work?
The similar operation with "aws s3 cp ... " command, and same credentials used for mvn deploy, works well with all [Public Access Settings] flags set to True.
I have a IAM user with S3 write access privileges and a generic maven repository bucket (Buckets and objects not public) without any AWS Bucket Policy specified.
Why do I have to set the flag [Public Access Settings -> Manage public access control list (ACLs) -> Block new public ACLs and uploading public objects] to False for the deploy to work?
The similar operation with "aws s3 cp ... " command, and same credentials used for mvn deploy, works well with all [Public Access Settings] flags set to True.