AWS Health

What Plutus imports

• Reserved Instance & Savings Plan expiry notices
• Instance retirements and scheduled replacements
• Service deprecation and end-of-support notices

Connecting

Method: IAM Role (cross-account)

1. Check that the AWS account has a Business, Enterprise On-Ramp, or Enterprise Support plan under AWS Support Center → Support plans. AWS blocks the Health API entirely on Basic and Developer Support, so this event source can’t connect without one of those plans.
2. This event source reuses the same PlutusCostReader IAM role and External ID as the AWS cost source — there’s no new credential to create.
3. Re-apply the PlutusCostReader Terraform module or CloudFormation template so the role also grants health:DescribeEvents and health:DescribeEventDetails. If the role was created before this event source existed, it won’t have these permissions yet.
4. Paste the same Role ARN you used for the AWS cost source into the Role ARN field.
5. Optionally, set Event Type Codes to a comma-separated list (max 10) of specific AWS Health event type codes, e.g. AWS_EC2_PERSISTENT_INSTANCE_RETIREMENT_SCHEDULED. Leave this blank to use the built-in cost-relevance filter (commitment expiry and retirement notices) — setting it replaces that filter entirely rather than adding to it.
6. Click Save & connect, then Sync now to pull commitment expiry and retirement notices onto your cost charts.

Notes

Single-account only for now: a payer account sees its own management-account events, not the organization-wide view. Separate from the “AWS” cost source — this only overlays notices on your charts, it does not read spend.