AWS Elastic Beanstalk

Task 1: Access the Elastic Beanstalk environment

1. In the console, in the search box to the right of to *Services*, search for and choose *Elastic Beanstalk*.
2. A page titled Environments should open, and it should show a table that lists the details for an existing Elastic Beanstalk application.
3. Note: If the status in the Health column is not Ok, it has not finished starting yet. Wait a few moments, and it should change to Ok.
4. Under the Environment name column, choose the name of the environment.
5. The Dashboard page for your Elastic Beanstalk environment opens.
6. Notice that the page shows that the health of your application is Ok.
7. The Elastic Beanstalk environment is ready to host an application. However, it does not yet have running code.
8. Test access to the environment.

• Near the top of the page, choose the Domain link (the URL ends in elasticbeanstalk.com).
• When you choose the URL, a new browser tab opens. However, you should see that it displays an HTTP Status 404 — Not Found message.
• This behavior is expected because this application server doesn’t have an application running on it yet.
• Return to the Elastic Beanstalk console.
• In the next step, you will deploy code in your Elastic Beanstalk environment.

Task 2: Deploy a sample application to Elastic Beanstalk

1. To download a sample application, choose this link: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/samples/tomcat.zip
2. Back in the Elastic Beanstalk Dashboard, choose Upload and Deploy.
3. Choose Choose File, then navigate to and open the tomcat.zip file that you just downloaded.
4. Choose Deploy.
5. It will take a minute or two for Elastic Beanstalk to update your environment and deploy the application.
6. After the deployment is complete, choose the Domain URL link (or, if you still have the browser tab that displayed the 404 status, refresh that page).
7. The web application that you deployed displays.
8. Congratulations, you have successfully deployed an application on Elastic Beanstalk!
9. Back in the Elastic Beanstalk console, choose Configuration in the left pane.
10. Notice the details here.
11. For example, in the Instance traffic and scaling panel, it indicates the EC2 Security groups, minimum and maximum instances, and instance type details of the Amazon Elastic Compute Cloud (Amazon EC2) instances that are hosting your web application.
12. In the Networking, database, and tags panel, no configuration details display, because the environment does not include a database.
13. In the Networking, database, and tags row, choose Edit.
14. Note that you could easily enable a database to this environment if you wanted to: you only need to set a few basic configurations and choose Apply. (However, for the purposes of this activity, you do not need to add a database.)
15. Choose Cancel at the bottom of the screen.
16. In the left panel under Environment, choose Monitoring.
17. Browse through the charts to see the kinds of information that are available to you.

Task 3: Explore the AWS resources that support your application

1. In the console, in the search box to the right of to *Services*, search for and choose EC2
2. Choose Instances.
3. Note that two instances that support your web application are running (they both contain samp in their names).
4. If you want to continue exploring the Amazon EC2 service resources that were created by Elastic Beanstalk, feel free to explore them. You will find:

5 A security group with port 80 open

• A load balancer that both instances belong to
• An Auto Scaling group that runs from two to six instances, depending on the network load

1. Though Elastic Beanstalk created these resources for you, you still have access to them.

Submitting your work

1. To record your progress, choose Submit at the top of these instructions.
2. When prompted, choose Yes.
3. After a couple of minutes, the grades panel appears and shows you how many points you earned for each task. If the results don’t display after a couple of minutes, choose Grades at the top of these instructions.
4. Important: Some of the checks made by the submission process in this lab will only give you credit if it has been at least 5 minutes since you completed the action. If you do not receive credit the first time you submit, you may need to wait a couple minutes and the submit again to receive credit for these items.
5. Tip: You can submit your work multiple times. After you change your work, choose Submit again. Your last submission is recorded for this lab.
6. To find detailed feedback about your work, choose Submission Report.
7. Tip: For any checks where you did not receive full points, there are sometimes helpful details provided in the submission report.