Skip to content

[New Product] Amazon Aurora MySQL#9534

Open
rugginic wants to merge 3 commits intoendoflife-date:masterfrom
rugginic:amazon-aurora-mysql
Open

[New Product] Amazon Aurora MySQL#9534
rugginic wants to merge 3 commits intoendoflife-date:masterfrom
rugginic:amazon-aurora-mysql

Conversation

@rugginic
Copy link
Copy Markdown
Contributor

Summary

  • Adds products/amazon-aurora-mysql.md for Amazon Aurora MySQL
  • Covers major versions 2 (MySQL 5.7, EOL 2024-10-31, EOES 2027-02-28) and 3 (MySQL 8.0, EOL 2028-04-30, EOES 2029-07-31), plus deprecated version 1
  • Mirrors the existing amazon-aurora-postgresql.md pattern
  • Includes auto: config with rds: and release_table: methods for automated updates from the AWS release calendar page

Data source

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html

Test plan

  • Netlify deploy preview renders the product page correctly
  • EOL/EOES columns display for versions 2 and 3
  • Verify dates match AWS release calendar table

@rugginic rugginic changed the title Add Amazon Aurora MySQL [New Product] Amazon Aurora MySQL Feb 23, 2026
@rugginic
Copy link
Copy Markdown
Contributor Author

Hi, @marcwrobel. Does this PR look good?

@captn3m0 captn3m0 added the new-product This PR adds a new product to the website. label Feb 28, 2026
@rugginic
Copy link
Copy Markdown
Contributor Author

@captn3m0 does this one look okay?

Add version availability timeline, quarterly release cadence, deprecation
windows (3-month minor, 6-month major), upgrade behavior with link to AWS
docs, and maintenance window details. Move extended support paragraph to
end for consistency with other Aurora/RDS products.
@rugginic
Copy link
Copy Markdown
Contributor Author

rugginic commented Mar 9, 2026

Updated body text to match the amazon-aurora-postgresql.md pattern:

  • Version line mapping (v2 = MySQL 5.7, v3 = MySQL 8.0)
  • Minor version quarterly release cadence
  • Deprecation windows (3 months for minor, 6 months for major)
  • Upgrade behavior paragraph with link to AWS docs
  • Maintenance window details
  • Extended support paragraph (moved to end, consistent with other AWS products)

Frontmatter was already correct — no changes there.

CI is green. Deploy preview

@rugginic
Copy link
Copy Markdown
Contributor Author

Hey @captn3m0 any progress here?

@rugginic
Copy link
Copy Markdown
Contributor Author

@captn3m0 any updates here?

@bakayolo
Copy link
Copy Markdown

mmmhh how do we get this merged? :)

bakayolo added a commit to block/version-guard that referenced this pull request Apr 15, 2026
… and improve classification (#17)

## Summary

Fixes the detection pipeline to produce real, usable compliance data for
EKS and ElastiCache using only [endoflife.date](https://endoflife.date)
for EOL data — no AWS API credentials needed.

### What changed

**Temporal payload fix**
- Removed `RetrieveFindings` activity that returned all findings through
Temporal gRPC (12K+ findings = 10MB, exceeds 4MB limit)
- `CreateSnapshot` now reads directly from the in-memory store —
findings never transit Temporal
- Fails hard on empty snapshots (all workflows failed) or store read
errors

**EOL data from endoflife.date only**
- `ProductCycle.EOL` and `.Support` changed from `string` to `any`
(endoflife.date returns booleans or date strings)
- Enabled EKS via endoflife.date (was blocked by
`ProductsWithNonStandardSchema`)
- Fixed `aurora-postgresql` mapping to `amazon-aurora-postgresql`
- Added `aurora-mysql` mapping (pending
[endoflife.date#9534](endoflife-date/endoflife.date#9534))
- Removed `ProductsWithNonStandardSchema` blocklist and dead code

**Version matching**
- EOL provider uses prefix matching: cycle `8.0` matches resource
version `8.0.35`
- Policy uses prefix matching with `k8s-` prefix normalization

**Classification**
- Extended support is now YELLOW, not RED (check order fix + policy fix)
- EKS 1.30/1.32 correctly show "in extended support (6x standard cost)"
- ElastiCache Redis 5.0.6 correctly shows extended support

### Validated with docker-compose (real Wiz data)

| Resource | Findings | Yellow | Green | Unknown |
|----------|----------|--------|-------|---------|
| EKS | 155 | 90 (1.30, 1.32 in ext. support) | 65 | 0 |
| ElastiCache | 3,974 | 138 (Redis 5.0.6) | 3,739 | 97 |
| Aurora MySQL | 12,238 | 0 | 0 | 12,238 (no EOL source yet) |

### Single-pod assumption

The in-memory store is shared between detection and snapshot activities
because everything runs on a single Temporal worker. This is intentional
— we don't anticipate scaling this service to multiple pods.

---------

Co-authored-by: Amp <amp@ampcode.com>
bakayolo added a commit to block/version-guard that referenced this pull request Apr 17, 2026
## Summary

Adds a lightweight mechanism to patch EOL lifecycle data locally when
upstream [endoflife.date](https://endoflife.date) PRs are pending
review.

## Problem

Version Guard depends on endoflife.date for all EOL data. When a product
is missing or has incomplete cycles upstream, resources show as UNKNOWN
— hiding real compliance issues. Upstream PRs can take weeks to merge.

## Solution

An nginx sidecar container that:
1. Serves local JSON overrides from `deploy/endoflife-override/api/`
2. Proxies everything else to upstream endoflife.date

No fork to maintain, no Ruby/Jekyll build. Just drop a `.json` file and
restart.

## Changes

- `deploy/endoflife-override/` — nginx config + patched JSON files +
documentation
- `cmd/server/main.go` — `EOL_BASE_URL` env var support
- `docker-compose.yaml` — `endoflife` service + wiring
- `README.md` — WIP/Experimental disclaimer, updated docs

## Current Overrides

| Product | Issue | Upstream PR |
|---------|-------|-------------|
| `amazon-aurora-mysql` | Product doesn't exist yet |
[#9534](endoflife-date/endoflife.date#9534) |
| `amazon-opensearch` | Missing 3.3 and 3.5 cycles |
[#9919](endoflife-date/endoflife.date#9919) |

## Impact

Before (upstream only): Aurora = 4,231 UNKNOWN (0% compliance)
After (with overrides): Aurora = 4,224 GREEN + 7 YELLOW (**99.8%
compliance**)

Overall compliance: 45.8% → **94.8%**

Co-authored-by: Amp <amp@ampcode.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-product This PR adds a new product to the website.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants