AWSElasticBeanstalkFullAccess – Allows the user to create, modify, and delete Elastic Beanstalk applications, application versions, configuration settings, environments, and their underlying resources.
Assuming you now have a working app, the next step is to prepare it for deployment. First nitialize the app for ElasticBeanstalk. I prefer to organize my AWS accounts into profiles so we add the --profile flag.
eb init --profile name-of-my-profile
First determine which region you want to deploy the app in.
Next identify which app you want to deploy or select [Create new Application].
Name your ElasticBeanstalk app.
Since we created a new app using Ruby 2.6.x, I simply select the right option. If you want to learn more about the differences between Puma and Passanger, check out this consumer report.
This new prompt is where you are now asked to deploy your app on CodeCommit. I select yes.
CodeCommit will ask you to name the repository. I pick the same as the app itself.
CodeCommit will also ask for a default branch name. It's standard to pick "master".
AWS will ask you to name the keypair used for granting access.
Within an ElasticBeanstalk application, you can have multiple environments such as development, staging, production or beta, gamma, and production. As a first step, it helps to think about how you want to view your environment so as a first step, we will check for CNAME availability.
Let's check to see if we can use this CNAME for our environment.