AWS Elastic Beanstalk Adds Support for Customization of Health Monitoring
You can now configure an Elastic Beanstalk environment to ignore application HTTP 4xx responses in enhanced health monitoring. It helps in avoiding impact to Elastic Beanstalk environment health because of client-side errors.
You can now configure an Elastic Beanstalk environment to ignore application HTTP 4xx responses in enhanced health monitoring. It helps in avoiding impact to Elastic Beanstalk environment health because of client-side errors.
Enhanced health reporting gathers additional information about resources in your environment, and analyzes the information to provide a better picture of overall environment health. Client-side errors (ex. HTTP 404 Not Found) can sometimes cause degradation in environment health status, triggering in warning or severe events. Previously, there was no way to ignore application HTTP 4xx responses in enhanced health monitoring. Today’s launch adds a configuration option for the same. To learn more, refer to Configuring Enhanced Health Rules in Elastic Beanstalk.
Visit the AWS global region table for a full list of AWS Regions where AWS Elastic Beanstalk is available.
For more information on AWS Elastic Beanstalk: