Releases: aws-samples/aws-health-aware
2.3 - Updates for performance, terraform, Slack webhooks, general fixes and documentation
What's Changed
Performance Improvements
- from #93
Terraform updates
- Fix for template file / env vars / eventbridge schedule by @davedimm in #88
- Issue 76 Fixed Terraform script to include an Environment Variable for the configured endpoint by @calorie in #84
Slack Workflow 2.0 webhook support
- Add support for Slack 'triggers' webhooks - streamline webhook handling logic by @andrewcr7 in #90
- update to Slack webhook/trigger handling by @andrewcr7 in #94
General Fixes
- from #93
Documentation updates
- from #101, update docs for
- Sample ExcludeAccountIDs file and troubleshooting notes by @andrewcr7 in c3da096 & ccd1396
- Using AHA with AWS Health Delegated Administrator @andrewcr7 in update delegated admin notes and TOC
- Organizational View notes and link to documentation by @andrewcr7 in 0378ff6
New Contributors
- @davedimm made their first contribution in #88
- @calorie made their first contribution in #84
- @joyofhex made their first contribution in #93
Full Changelog: 2.2.2...2.3
2.3-beta - Updates for performance, terraform, Slack webhooks, general fixes and documentation
What's Changed
Performance Improvements
- from #93
Terraform updates
- Fix for template file / env vars / eventbridge schedule by @davedimm in #88
- Issue 76 Fixed Terraform script to include an Environment Variable for the configured endpoint by @calorie in #84
Slack Workflow 2.0 webhook support
- Add support for Slack 'triggers' webhooks - streamline webhook handling logic by @andrewcr7 in #90
- update to Slack webhook/trigger handling by @andrewcr7 in #94
General Fixes
- from #93
Documentation updates
- from #101, update docs for
- Sample ExcludeAccountIDs file and troubleshooting notes by @andrewcr7 in c3da096 & ccd1396
- Using AHA with AWS Health Delegated Administrator @andrewcr7 in update delegated admin notes and TOC
- Organizational View notes and link to documentation by @andrewcr7 in 0378ff6
New Contributors
- @davedimm made their first contribution in #88
- @calorie made their first contribution in #84
- @joyofhex made their first contribution in #93
Full Changelog: 2.2.2...2.3
2.2.2 Account Name and Secrets Manager lookup efficiency + Terraform and doc updates
What's Changed
- Update README.md - remove Terraform instruction from CloudFormation s… by @andrewcr7 in #58
- Improve terraform path module by @mukitaro in #62
- Update Lambda to not make API calls to Secrets Manager if secret is not configured. by @pbraz-aws in #74
- Issue 72 Fix Moving Account Name Lookup by @gdougaws in #78
New Contributors
- @mukitaro made their first contribution in #62
- @pbraz-aws made their first contribution in #74
- @gdougaws made their first contribution in #78
Full Changelog: 2.2.1...2.2.2
2.2.1 Upgrade runtime from Python 3.8 to 3.11
Boto3 SDK had a breaking change for the health api, version 3.11 has a newer boto3 version that includes the fix.
2.2 New Eventbridge Schema and Terraform Fixes
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.
2.01
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.
Multi-region support
AHA now support Multi-Region deployments
Fix for email only & assume role
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 and multi-region beta
New features include:
- Multi-region (in the multi-region beta folder)
- Exclude accounts
- Add account name to an account ID
- If running in non-org mode, will send the account # and resource(s) if available
- AssumeRole (moved out of beta, so not really new)
- Support for the investigation event type
- Ability to work with Slack Workflows now
Email only bug fix
As pointed out in #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.