codepipeline/codepush with EB2

0

whenever I push a change into my elastic beanstalk using codepush with github CI/CD I get lots of emails telling me the system is on severe state and not updating itself Enter image description here

asked 5 days ago32 views
1 Answer
0

The issue you're experiencing with frequent emails about severe state and update failures during CodePipeline/CodePush deployments to Elastic Beanstalk is a common concern. This behavior is likely due to the default notification settings in Elastic Beanstalk combined with the temporary state changes that occur during deployments.

When you push changes and trigger a deployment, Elastic Beanstalk goes through a process of updating your environment. During this process, there may be brief periods where the environment health degrades as instances are being updated, which triggers these notifications.

To address this, you have a few options:

  1. Adjust notification settings: You can modify the Elastic Beanstalk notification settings to reduce the frequency of emails or change the conditions under which they are sent. This can be done through the Elastic Beanstalk console or by using configuration files.

  2. Use Amazon EventBridge: For more granular control over notifications, you can set up custom event rules using Amazon EventBridge. This allows you to define specific conditions for when you want to receive notifications, potentially reducing unnecessary alerts during normal deployment processes.

  3. Optimize your deployment strategy: Consider using Elastic Beanstalk's rolling updates with an additional batch or immutable deployment options. These strategies can help maintain application availability during updates and potentially reduce the occurrence of health status changes that trigger notifications.

  4. Review your health check settings: Ensure your application's health check settings are appropriately configured. Overly sensitive health checks might cause false alarms during deployments.

  5. Monitor deployments actively: Instead of relying solely on email notifications, you can use the Elastic Beanstalk console, AWS CLI, or integrate with your CI/CD pipeline to actively monitor deployment status and health.

By implementing these strategies, you should be able to reduce the number of unnecessary notifications while still maintaining visibility into critical issues with your Elastic Beanstalk environment during the CI/CD process.
Sources
Does elastic beanstalk notify me of changes | AWS re:Post
Deploy to Elastic Beanstalk with GitHub Actions | .NET on AWS Blog

profile picture
answered 5 days ago
  • I tried to follow your steps but couldnt get any changes done, would you like to share a tutorial for this topic?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions