Home / Methodology
METHODOLOGY
Methodology and data sources
How we collect AWS end-of-support dates and fees, how we check them every day, and what to keep in mind when you use them.
Sources, in order of authority
- AWS documentation. Release calendars, version-support pages, the AWS Lambda runtimes pages, the AWS Services in Sunset list and AWS What's New posts. When sources disagree, AWS documentation wins.
- AWS pricing pages. Extended-support fees come only from AWS's published pricing (for example the EKS and RDS pricing pages). We don't estimate fees AWS hasn't published.
- endoflife.date. A community-maintained dataset we use as a starting point for version lists and dates, then check against AWS.
How the data is updated
- Daily refresh. Every morning (around 6 AM US Eastern) we fetch fresh data and rebuild the site. The time of the latest snapshot is shown on the home page and in the footer of every page.
- Daily accuracy check. A separate automated check re-fetches the AWS documentation and pricing pages behind our data and compares them with the previous day. Any change, such as a new version, a moved date or a new shutdown, is reviewed and reflected on the site.
- Corrections layer. When endoflife.date and AWS documentation differ, we apply a correction with its AWS source and the date we checked it. Corrections are listed on the corrections page.
How to read our dates
- Standard support ends is the last day of AWS standard support. For services with paid extended support (EKS, RDS, Aurora and others), AWS usually starts billing extended support automatically the next day.
- Month-only dates. Where AWS publishes only a month, we show only the month rather than inventing a day.
- Lambda runtimes have three dates: deprecation, then a block on creating new functions, then a block on updating existing ones. Existing functions keep running.
- Minor versions (for example RDS for MySQL minors) can have earlier end dates than their major version. We show each one's own date.
- Preview releases are not listed until AWS makes them generally available.
How cost estimates work
- EKS: AWS charges $0.10 per cluster-hour in standard support and $0.60 in extended support. We show the difference over 730 hours a month.
- RDS and Aurora: AWS's published example rate for US East (Ohio): $0.10 per vCPU-hour in years 1 and 2 and $0.20 in year 3, using AWS's published year-3 start dates. Every instance on the old version is billed, including read replicas and Multi-AZ standbys.
- OpenSearch and ElastiCache use the fee structures on their AWS pricing pages.
- Estimates exclude taxes, discounts, Savings Plans and other charges, and other regions have different rates. For future versions, we show today's published rates; AWS may change them before that version's extended support starts.
Limitations
AWS can change dates and prices without notice, and some changes appear on one AWS page before another. Our data can lag AWS by up to a day. AWS sometimes removes older minor versions from its tables, so dates for those versions can no longer be re-checked. Always confirm with AWS before acting. See the terms of use.
Report a problem
If something looks wrong, email eolwatch@proton.me. See the corrections policy.