A Look at Elastic Beanstalk’s Launch Activities

by pgurnig

Using Elastic Beanstalk makes it easy to spin up a Web or Worker Application. If you’ve done so manually, you can really appreciate the fact that AWS can consistently create a working environment.

In this example, we’ll review the major steps that occurred while spinning up a sample .NET web application. 11 steps were output to the console over a 20-minute period.

  1. createEnvironment message.
  2. Specified an S3 storage bucket for environment data. Noted that this bucket was now associated with my account. The bucket creation date was 6/19/2016 which is almost a full two years prior to creating this site.
  3. Security Group created.
  4. Created an Elastic IP.
  5. EC2 instance waiting message.
  6. Adding specific EC2 instance message.
  7. Added EC2 instance to Auto Scaling Group.
  8. Started Application message.
  9. UpdateAppVersion Completed message.
  10. Environment Health to green message.
  11. Successful launch message.

Once created, I clicked on the available URL and noted the working web application.

My next step was to delete the application and to observe whether the Elastic IP, EC2 instance, Security Group and Auto Scaling Group were all removed. They were and I noted the following:

  • the EC2 instance had as its name tag, the name of the website created. It was showing as terminated in the Console.
  • the S3 bucket persisted in my account.

 

Feature Photo by Joel Filipe on Unsplash