With all of these changes now complete, commit these changes to your git repo.
The last thing left to do before starting up your environment is to give the Elastic Beanstalk application access to the MySQL RDS instance.
Head to the and click on “Security Groups” under “Network & Security”. Here you should see two security groups: the default security group and a security group created for you Elastic Beanstalk application.
Click on the Elastic Beanstalk security group (for us, it’s called development, just like our environment) and copy the Group ID.
Right click on the default security group and select “Edit Inbound Rules”.
Since we’ve added this environment’s Security Group ID to the inbound rules of the default Security Group, we need to first remove that rule in the EC2 Management Console.
After that rule is removed, deleting the environment is a simple command line/terminal command:
eb stop
Alternatively, you can terminate the environment from the management console from within your environment.
This may take some time as all the AWS resources created for your environment need to be deleted. You can monitor progress from the command line/terminal or from the Elastic Beanstalk Management Console.
To delete your application, ensure all environments have been successfully terminated. If there are un-terminated environments, check the event log for errors in that environment during the termination process.