Editing Upgrading An Elastic Beanstalk Platform (section)

== Create new EBS environment ==

=== Select tier ===

'''Select environment tier:''' Web server environment

=== Create a web server environment ===

'''Application name''': Will create a new application for the environment. Try entering an existing application name?

'''Environment name''': ''[Environment identifier]''

'''Platform:''' Managed platform

'''Platform:''' Choose the platform for the environment, e.g. PHP, Python, etc.
'''Platform branch:''' Version of the environment.

'''Application code:''' Sample application (this will be overwritten with `eb deploy`

Wait for the environment to be created. The status under '''Health''' will change from "pending" to "ok".

A new EC2 instance will be created for the new EBS environment. 

=== Copy configuration ===

Copy any configuration stored in the old environment.

'''Environment''' > '''Configuration''' > '''Software''' > '''Edit''' > '''Environment Properties'''

=== Configure EC2 instance ===

==== Add inbound rules ====

* '''EC2 console''' > '''Security Groups''' > ''Select EC2 instance from list'' 
* In the instance details below, click the '''Inbound rules''' tab.
* Click '''Edit inbound rules'''
** Add 3 rules: 
** HTTPS, source ::/0 (Anywhere IPv6)
** HTTPS, source 0.0.0.0/0 (Anywhere IPv4)
** SSH,  source [REMOTE_IP]/32 (My IP)

==== Create a key pair ====

See [[Enabling_SSH_Connections_to_an_Elastic_Beanstalk_Environment#Key_Pairs|Key Pairs]] in [[Enabling SSH Connections to an Elastic Beanstalk Environment]]

=== Update DNS ===

* '''Route 53''' console > '''Hosted zones''' > ''Select domain name'' > '''View Details''' button
* Select a hosted subdomain > '''Edit record''' button > Select the new EBS environment under '''Route traffic to'''

=== Configure security certificates ===

See [[Elastic Beanstalk Security Certificates]]

=== Deploy app ===

==== Update ESB environment app settings ====

In the local project, update environment settings in `.elasticbeanstalk/config.yml`:

* `branch-defaults.develop.environment`
* `branch-defaults.master.environment`
* `environment-defaults`
* `global.application_name`
* `global.default_ec2_keyname`
* `global.default_platform`

==== Confirm GitHub access, if needed ====

If the deployment requires installing anything from private GitHub repos, confirm that [[Troubleshooting_Elastic_Beanstalk_Deployment#Errors_running_composer_install|the GitHub personal access token has not expired]].

==== Deploy the app using eb-cli ====

Deploy the app with

<syntaxhighlight lang="bash">
$ eb deploy
</syntaxhighlight>

Or with the `--staged` option if files have been modified but not pushed to remote yet. The files have to be added to the commit to be included. 

<syntaxhighlight lang="bash">
$ eb deploy --staged
</syntaxhighlight>

=== Cleanup ===

Delete the old EBS environment and its EC2 instance as soon as possible to avoid unnecessary charges.

[[Category:Elastic Beanstalk]] [[Category:AWS]] [[Category:Web Development]]