If you discover a potential security issue in this project, we ask that you notify AWS Security via our vulnerability reporting page. Please do not create a public GitHub issue for security vulnerabilities.
This repository contains a static JSON dataset with no executable code. Security concerns for this project include:
- Data integrity: Incorrect lifecycle dates or statuses that could cause consumers to make flawed operational decisions
- Source authenticity: Broken or manipulated
sourceUrlreferences that undermine the verification model - Supply-chain trust: Unauthorized modifications to the dataset that bypass the review process
- All data changes require CODEOWNERS approval before merge
- CI validates the JSON schema (including an official AWS
sourceUrlon every documentation-sourced entry), date consistency, and freshness on every change - Every
behaviorand every documentation-sourced entry links official AWS documentation for independent verification; API-sourced dates come from the AWS Health Version Catalog (DescribeServiceLifecycle) - The
generatedAtfield shows when the dataset was last checked against its sources, andlastUpdatedwhen the data last changed
- For critical business decisions (upgrade deadlines, cost forecasting, compliance), always verify dates against the official AWS documentation linked in the entry (
behavior.sourceUrl, orprovenance.sourceUrlfor documentation-sourced entries) - Pin to tagged releases rather than tracking the main branch for production integrations
- Treat the
statusfield as advisory; validate against date fields programmatically for automated decisions