2 Answers
- Newest
- Most votes
- Most comments
0
In addition to the S3 bucket policy, You should verify that your instance has the correct permissions for Amazon S3.
https://aws.amazon.com/premiumsupport/knowledge-center/elastic-beanstalk-s3-bucket-instance/
By default, aws-elasticbeanstalk-ec2-role
is attached as an instance profile to the Elastic Beanstalk applications.
Please confirm that the role has the permissions including "s3:PutObject"
answered a year ago
0
After adding "s3:PutObjectAcl" along with s3:PutObject, it worked perfectly.
answered a year ago
Relevant content
- Accepted Answerasked 10 months ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Hi Kihyeon,
I searched a lot and later found on a forum that "s3:PutObjectAcl" is also needed along with s3:PutObject, once I added this, it worked perfectly.
Thank you for updating the status