<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Elasticache on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/elasticache/</link><description>Recent content in Elasticache on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 30 Oct 2026 16:53:40 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/elasticache/index.xml" rel="self" type="application/rss+xml"/><item><title>ElastiCache Serverless public endpoints now available in AWS GovCloud</title><link>https://curadevops.metacog.co.kr/insights/2026-10-30-public-endpoints-for-amazon-elasticache-serverless-now-in-aw/</link><pubDate>Fri, 30 Oct 2026 16:53:40 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-30-public-endpoints-for-amazon-elasticache-serverless-now-in-aw/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> GovCloud parity for ElastiCache Serverless public endpoints means IAM-authenticated Valkey caches can now be reached outside a VPC in GovCloud without a bastion or VPN. Worth noting for any GovCloud workloads that need serverless caching with simplified network topology.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Amazon ElastiCache for Valkey adds CloudWatch Insights dashboard</title><link>https://curadevops.metacog.co.kr/insights/2026-10-12-amazon-elasticache-for-valkey-introduces-elasticache-insight/</link><pubDate>Mon, 12 Oct 2026 20:04:11 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-12-amazon-elasticache-for-valkey-introduces-elasticache-insight/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> A new GA CloudWatch dashboard surfacing OTel metrics (memory, network, latency, keyspace, errors) for Valkey node clusters — worth scheduling adoption to consolidate cache observability; note that detailed 15-second metrics incur standard CloudWatch OTel pricing.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> AWS now bundles a pre-built observability layer for ElastiCache Valkey at no additional platform cost (standard CloudWatch OTel pricing applies for enhanced polling), relevant context if the org is evaluating its caching observability spend.&lt;/li>
&lt;/ul></description></item><item><title>ElastiCache for Valkey adds OpenTelemetry metrics with PromQL and 15s detailed monitoring</title><link>https://curadevops.metacog.co.kr/insights/2026-10-03-amazon-elasticache-for-valkey-now-supports-opentelemetry-met/</link><pubDate>Sat, 03 Oct 2026 15:01:20 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-03-amazon-elasticache-for-valkey-now-supports-opentelemetry-met/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> New GA capability lets teams query ElastiCache Valkey metrics via PromQL in Grafana and CloudWatch, with optional 15-second granularity for catching short-lived latency spikes; schedule enablement of standard OTel metrics now (free) and evaluate detailed monitoring for critical clusters this quarter.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>ElastiCache Serverless for Valkey adds public endpoint support</title><link>https://curadevops.metacog.co.kr/insights/2026-09-30-amazon-elasticache-serverless-for-valkey-now-supports-public/</link><pubDate>Wed, 30 Sep 2026 16:35:00 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-30-amazon-elasticache-serverless-for-valkey-now-supports-public/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> New GA capability for ElastiCache Serverless that enables internet-reachable Valkey caches without VPC config; useful for prototyping or external workloads but likely not a fit for production platform architecture where VPC isolation is the norm.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>ElastiCache Global Datastore adds tagging and tag-based access control</title><link>https://curadevops.metacog.co.kr/insights/2026-09-25-amazon-elasticache-global-datastore-now-supports-tagging-and/</link><pubDate>Fri, 25 Sep 2026 15:41:44 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-25-amazon-elasticache-global-datastore-now-supports-tagging-and/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams running ElastiCache Global Datastore across regions can now enforce consistent IAM/SCP policies and cost allocation via tags; worth updating your tagging standards and IAM policies this quarter to close the permission-model gap.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> This closes a cost-allocation and access-control gap in multi-region ElastiCache deployments, useful context if the org is standardizing FinOps tagging policies across AWS resources.&lt;/li>
&lt;/ul></description></item></channel></rss>