Skip to content

elasticache-memcached: use amazon-elasticache-memcached endoflife.date product#81

Merged
bakayolo merged 1 commit into
mainfrom
fix/elasticache-memcached-product-id
May 20, 2026
Merged

elasticache-memcached: use amazon-elasticache-memcached endoflife.date product#81
bakayolo merged 1 commit into
mainfrom
fix/elasticache-memcached-product-id

Conversation

@bakayolo

@bakayolo bakayolo commented May 20, 2026

Copy link
Copy Markdown
Collaborator

AWS still supports Memcached 1.5.x on ElastiCache (see AWS docs), but upstream Memcached EOL'd 1.5 in March 2020. The current config queries the upstream memcached product and mislabels 1.5.x clusters as EOL.

Switches elasticache-memcached to the AWS-flavored amazon-elasticache-memcached product. Upstream product PR: endoflife-date/endoflife.date#10129.

@bakayolo
bakayolo requested a review from a team as a code owner May 20, 2026 00:00
@bakayolo
bakayolo force-pushed the fix/elasticache-memcached-product-id branch from 1822a2a to 785b2b3 Compare May 20, 2026 01:02
…e product

AWS still supports Memcached 1.5.x on ElastiCache even though upstream
Memcached EOL'd 1.5 in March 2020, so the upstream `memcached` product
mislabels 1.5.x clusters as EOL. Switch to the AWS-flavored
`amazon-elasticache-memcached` product (upstream PR:
endoflife-date/endoflife.date#10129).

Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e42a4-2ed6-745e-94d0-9d47956a0f3f
@bakayolo
bakayolo force-pushed the fix/elasticache-memcached-product-id branch from 785b2b3 to 25571ba Compare May 20, 2026 01:24
@bakayolo
bakayolo merged commit 720884e into main May 20, 2026
7 checks passed
@bakayolo
bakayolo deleted the fix/elasticache-memcached-product-id branch May 20, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants