AHA is an incident management & communication framework to provide real-time alert customers when there are active AWS event(s). For customers with AWS Organizations, customers can get aggregated active account level events of all the accounts in the Organization. Customers not using AWS Organizations still benefit alerting at the account level.
Full Changelog: https://github.com/aws-samples/aws-health-aware/compare/2.2.1...2.2.2
Boto3 SDK had a breaking change for the health api, version 3.11 has a newer boto3 version that includes the fix.
Release 2.2 introduces an updated schema for Health events delivered to an EventBridge bus. This allows simplified matching of events which you can then consume with other AWS services or SaaS solutions.
AHA 2.1 Beta Release with updated eventbridge schema and examples posted. This will allow customers to have EventBridge be the point for endpoint connection, filtering, etc.
AHA now support Multi-Region deployments
Fixed a bug where if you were only doing email as an endpoint AND were using the assumerole function, the Lambda would not have the required permissions in the IAM policy.
New features include:
As pointed out in https://github.com/aws-samples/aws-health-aware/issues/1 if a user ONLY selects email as an endpoint, the IAM policy fails. This was due to the IAM policy condition for secrets. Chime, Slack, Eventbridge and Teams are all stored as secrets. If none of those endpoints are created, the resources for the policy are null and thus give the error: "Policy statement must contain resources".
Solution was to create another condition that verifies if any combination of secrets conditions were met and if true, add that particular permission to the overall policy.
Initial Deployment for AWS Health Aware (AHA)