We will discuss Elastic Beanstalk in more detail in the next chapter, but essentially our Elastic Beanstalk environments are self-contained applications that provide all the services required to run our code. The environments themselves are created in a transparent manner and should be monitored according to the features that are created within the environment.

For example, an Elastic Beanstalk application could be composed of EC2 instances, an ELB, a RDS database, an SQS queue, and so on. All of these components need to be monitored in the same way as if we created those services ourselves. We do have an additional set of metrics that we can follow in the CloudWatch overview section when selecting Elastic Beanstalk. Here, we can see the environment health status and the HTTP response codes ordered by class (200, 300, 400, and 500 errors) that our application is responding to requests with.

An example of an Elastic Beanstalk CloudWatch overview is provided in the following screenshot:

B10030_18_36