Elastic Beanstalk: IAM policy for deploying a multicontainer Docker environment from a private repository

by Dustin Oprea   Last Updated January 10, 2018 03:00 AM

How do I enable my environment under Elastic Beanstalk to talk to S3 so that it can get the authentication info and then pull my Docker image from a private repository in a multicontainer environment?

I found the name of the IAM role in my environment's instance config ("aws-elasticbeanstalk-ec2-role"), went to IAM, opened the "AWSElasticBeanstalkWebTier" policy in order to extend it for S3 access to the ARN for my bucket, but these policies are "AWS Managed" and read-only. Would merely attaching an existing S3 policy (e.g. AmazonS3ReadOnlyAccess, defined by AWS) to my instance-profile role be sufficient?

Related Questions

How to make AWS containers communicate

Updated January 02, 2018 23:00 PM

Best strategy for deploying Docker to Elastic Beanstalk

Updated February 02, 2018 11:00 AM

Multiple docker containers elastic beanstalk

Updated April 30, 2015 21:00 PM

Deploy a Docker environment on Elastic Beanstalk

Updated August 03, 2015 14:00 PM