Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CloudWatch Alarm for Managed Update Failures #314

Open
pricerj opened this issue Jan 8, 2024 · 0 comments
Open

CloudWatch Alarm for Managed Update Failures #314

pricerj opened this issue Jan 8, 2024 · 0 comments
Labels

Comments

@pricerj
Copy link

pricerj commented Jan 8, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave "+1" or "me too" comments. They generate extra noise for issue followers and do not help prioritize the request.

Tell us about your request
What do you want us to build?
A CloudWatch alarm that will be able to generate an alert if Managed Updates faile.

Is this request specific to an Elastic Beanstalk platform?
If so, which one(s)? No, All Platforms

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
We had dozens of Elastic Beanstalk deployments go to production and Managed Updates were failing for months due to dependence on the service role to a specific SNS Topic name in the IAM permissions.

Seems pretty basic that if Managed Updates are failing tenants would want to know. Like if someone turned of another setting or config that breaks it.

Are you currently working around this issue?
How are you currently solving this problem? Manual validation

Additional context
Anything else we should know?

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant