- ElasticBeanstalk no longer allow to create EC2 instance profile. We need to create it manually. See article
EC2InstanceProfileRoleForBeanstalk
. These AWS-managed policies would be sufficient:
AWSElasticBeanstalkServiceRolePolicy
AWSElasticBeanstalkWebTier
AWSElasticBeanstalkMulticontainerDocker
AWSElasticBeanstalkWorkerTier
ElasticBeanstalkRole
, can be created automatically by Beanstalk, and must have these 2 AWS-managed policies:
AWSElasticBeanstalkEnhancedHealth
AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy
- Choose default VPC, security group and deployment availablity zones
- Disabled Automatic Managed Update, and Enhanced Monitoring
- Create a Procfile to instruct Elastic Beanstalk on how to start the application. See Procfile
- (IMPORTANT) we must not zip the parent folder, and we can ignore
node_modules
, README.md and any non-prod files. See Instructions
- Tutorials
- See similar
Procfile
andbuildspec.yml
at chatter-backend