#AmazonElastiCache
Amazon ElastiCache for Valkey now supports changing durability on existing clusters #cloud
Amazon ElastiCache for Valkey now supports changing durability on existing clusters
https://aws.amazon.com/about-aws/whats-new/2026/10/elasticache-changing-durability/ https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/durability.html
dlvr.it
October 29, 2026 at 8:33 PM
🆕 Amazon ElastiCache now supports data tiering on R8gd and R7gd nodes in Europe (Spain) and Asia Pacific (Hyderabad) for lower-cost scaling of Valkey clusters, leveraging Graviton4 and Graviton3 processors for improved throughput and lower latency.

#AWS #AmazonElasticache
Amazon ElastiCache expands data tiering to R8gd and R7gd nodes in Europe (Spain) and Asia Pacific (Hyderabad)
Amazon ElastiCache for Valkey data tiering is now available on Graviton4-based R8gd nodes in the AWS Europe (Spain) Region, and on Graviton3-based R7gd nodes in the Europe (Spain) and Asia Pacific (Hyderabad) Regions. Data tiering is a lower-cost way to scale your Valkey clusters to hundreds of terabytes of capacity. It uses solid state drives (SSDs) on each node alongside memory. When memory fills up, ElastiCache automatically moves the least recently used items to SSD. When your application reads an item stored on SSD, ElastiCache moves it back into memory before serving the request. Data tiering is a good fit for workloads that regularly access up to 20% of their dataset, and for applications that can tolerate some extra latency when they read data from SSD. R8gd nodes are powered by AWS Graviton4 processors. They deliver up to 47% higher throughput, up to 43% lower P99 latency, and up to 31% better price-performance than Graviton3-based nodes of the same size. R7gd nodes are powered by AWS Graviton3 processors. They deliver up to 28% more throughput (read and write operations per second), up to 21% better P99 latency, and up to 25% more network bandwidth than Graviton2-based nodes. Actual performance varies by node size and workload. You can use data tiering on R8gd and R7gd nodes with Valkey 7.2 and later. To get started, create a new cluster or upgrade an existing one with the AWS Management Console, the AWS CLI, or the AWS SDKs. For pricing, see the  Amazon ElastiCache pricing page . To learn more, see  Data tiering  and  Supported node types  in the ElastiCache documentation.
aws.amazon.com
October 28, 2026 at 10:10 PM
Amazon ElastiCache expands data tiering to R8gd and R7gd nodes in Europe (Spain) and Asia Pacific (Hyderabad)

Amazon ElastiCache for Valkey data tiering is now available on Graviton4-based R8gd nodes in the AWS Europe (Spain) Region, and on Graviton3-based R7gd nodes in ...

#AWS #AmazonElasticache
Amazon ElastiCache expands data tiering to R8gd and R7gd nodes in Europe (Spain) and Asia Pacific (Hyderabad)
Amazon ElastiCache for Valkey data tiering is now available on Graviton4-based R8gd nodes in the AWS Europe (Spain) Region, and on Graviton3-based R7gd nodes in the Europe (Spain) and Asia Pacific (Hyderabad) Regions. Data tiering is a lower-cost way to scale your Valkey clusters to hundreds of terabytes of capacity. It uses solid state drives (SSDs) on each node alongside memory. When memory fills up, ElastiCache automatically moves the least recently used items to SSD. When your application reads an item stored on SSD, ElastiCache moves it back into memory before serving the request. Data tiering is a good fit for workloads that regularly access up to 20% of their dataset, and for applications that can tolerate some extra latency when they read data from SSD. R8gd nodes are powered by AWS Graviton4 processors. They deliver up to 47% higher throughput, up to 43% lower P99 latency, and up to 31% better price-performance than Graviton3-based nodes of the same size. R7gd nodes are powered by AWS Graviton3 processors. They deliver up to 28% more throughput (read and write operations per second), up to 21% better P99 latency, and up to 25% more network bandwidth than Graviton2-based nodes. Actual performance varies by node size and workload. You can use data tiering on R8gd and R7gd nodes with Valkey 7.2 and later. To get started, create a new cluster or upgrade an existing one with the AWS Management Console, the AWS CLI, or the AWS SDKs. For pricing, see the   https://aws.amazon.com/elasticache/pricing/. To learn more, see   https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/data-tiering.html and   https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.html in the ElastiCache documentation.
aws.amazon.com
October 28, 2026 at 10:05 PM
🆕 Amazon ElastiCache for Valkey now lets you change durability on existing clusters, offering sync and async options. This boosts flexibility for persistent data, like AI memory, in all regions with ElastiCache 9.0+. Enable via AWS Management Console, SDK, or CLI.

#AWS #AmazonElasticache
Amazon ElastiCache for Valkey now supports changing durability on existing clusters
Amazon ElastiCache for Valkey now lets you enable or disable durability on your existing node-based clusters without creating a new cluster. Previously, you couldn't change the durability configuration of an existing cluster in place. This made it harder to move from caching to persistent data store use cases, or to adapt as your application requirements change. Now you can change durability at any point in your application's lifecycle. You can choose between two durability options: synchronous and asynchronous writes. Synchronous writes persist data across at least two AZs before responding to the client, designed for zero data loss at single-digit millisecond write latency. Asynchronous writes persist data after responding to the client, maintaining microsecond write latency at no additional cost. However, up to 10 seconds of uncommitted data could be lost in the rare event of a failure. Both options maintain microsecond read latency. You can now use ElastiCache for a broader set of use cases beyond caching where data loss is unacceptable such as AI agent long-term memory, AI agent workflow state, knowledge bases for RAG applications, payment tokenization, and real-time inventory management. This feature is available in all AWS Regions where ElastiCache for Valkey 9.0 and later is available. To get started, use the AWS Management Console, AWS SDK, or AWS CLI. For pricing, see the  Amazon ElastiCache pricing page . To learn more, see  Durability  in the ElastiCache documentation.
aws.amazon.com
October 27, 2026 at 10:10 PM
Amazon ElastiCache for Valkey now supports changing durability on existing clusters

Amazon ElastiCache for Valkey now lets you enable or disable durability on your existing node-based clusters without creating a new cluster. Previously, you couldn't change the durability...

#AWS #AmazonElasticache
Amazon ElastiCache for Valkey now supports changing durability on existing clusters
Amazon ElastiCache for Valkey now lets you enable or disable durability on your existing node-based clusters without creating a new cluster. Previously, you couldn't change the durability configuration of an existing cluster in place. This made it harder to move from caching to persistent data store use cases, or to adapt as your application requirements change. Now you can change durability at any point in your application's lifecycle. You can choose between two durability options: synchronous and asynchronous writes. Synchronous writes persist data across at least two AZs before responding to the client, designed for zero data loss at single-digit millisecond write latency. Asynchronous writes persist data after responding to the client, maintaining microsecond write latency at no additional cost. However, up to 10 seconds of uncommitted data could be lost in the rare event of a failure. Both options maintain microsecond read latency. You can now use ElastiCache for a broader set of use cases beyond caching where data loss is unacceptable such as AI agent long-term memory, AI agent workflow state, knowledge bases for RAG applications, payment tokenization, and real-time inventory management. This feature is available in all AWS Regions where ElastiCache for Valkey 9.0 and later is available. To get started, use the AWS Management Console, AWS SDK, or AWS CLI. For pricing, see the   https://aws.amazon.com/elasticache/pricing/. To learn more, see   https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/ in the ElastiCache documentation.
aws.amazon.com
October 27, 2026 at 10:05 PM
Amazon ElastiCache Serverless for Valkey now supports online migration with zero downtime

https://aws.amazon.com/elasticache/ Serverless for Valkey now supports online migration from self-managed Valkey and Redis OSS on Amazon EC2 with zero downtime. Zero downtime means ...

#AWS #AmazonElasticache
Amazon ElastiCache Serverless for Valkey now supports online migration with zero downtime
https://aws.amazon.com/elasticache/ Serverless for Valkey now supports online migration from self-managed Valkey and Redis OSS on Amazon EC2 with zero downtime. Zero downtime means zero Errors returned to the client during migration, measured the same way the https://aws.amazon.com/elasticache/sla/ measures availability. Your application continues reading and writing through cutover, and you do not need third-party replication tools. Online migration runs in three steps. You prepare the migration, start the data sync, and complete the cutover. ElastiCache gives you a migration endpoint your application can point to when you prepare the migration, and data replicates continuously from your source once you start the sync. You choose when writes move to the serverless cache, with a manual cutover or an automatic one once your data is in sync. ElastiCache records each step as an event on the cache’s Events tab, with the reason for any failed step. Online migration connects to your source using encryption in transit (TLS) and authentication, and reads credentials from AWS Secrets Manager, so your existing security controls stay in place. Online migration supports self-managed caches in cluster mode on Amazon EC2 running Redis OSS 4.0 through 7.2 or Valkey 7.2 through 8.1, and you can migrate them straight to Valkey 9.0. Migration usage is free for the first 180 days per AWS account, starting when the account first prepares a migration. After that, you pay per node-hour for the migration nodes that ElastiCache runs to replicate your data, for as long as a migration is active. The ElastiCache Serverless cache is billed separately at standard data storage and ECPU rates, including during the free period. For pricing details, see https://aws.amazon.com/elasticache/pricing/. Online migration is available in all commercial AWS Regions, the China Regions, and the AWS GovCloud (US) Regions.  To get started, create or select an empty ElastiCache Serverless cache to migrate into, then start the migration from the https://console.aws.amazon.com/elasticache/ or the AWS CLI. To learn more, see the https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/migration-to-serverless.html.
aws.amazon.com
October 20, 2026 at 11:05 PM
🆕 Amazon ElastiCache Serverless for Valkey offers zero-downtime migration from self-managed Redis/Valkey on EC2. It uses encryption, costs nothing for 180 days, then per node-hour. Available in all AWS regions. See documentation for details.

#AWS #AmazonElasticache
Amazon ElastiCache Serverless for Valkey now supports online migration with zero downtime
Amazon ElastiCache Serverless for Valkey now supports online migration from self-managed Valkey and Redis OSS on Amazon EC2 with zero downtime. Zero downtime means zero Errors returned to the client during migration, measured the same way the ElastiCache SLA measures availability. Your application continues reading and writing through cutover, and you do not need third-party replication tools. Online migration runs in three steps. You prepare the migration, start the data sync, and complete the cutover. ElastiCache gives you a migration endpoint your application can point to when you prepare the migration, and data replicates continuously from your source once you start the sync. You choose when writes move to the serverless cache, with a manual cutover or an automatic one once your data is in sync. ElastiCache records each step as an event on the cache’s Events tab, with the reason for any failed step. Online migration connects to your source using encryption in transit (TLS) and authentication, and reads credentials from AWS Secrets Manager, so your existing security controls stay in place. Online migration supports self-managed caches in cluster mode on Amazon EC2 running Redis OSS 4.0 through 7.2 or Valkey 7.2 through 8.1, and you can migrate them straight to Valkey 9.0. Migration usage is free for the first 180 days per AWS account, starting when the account first prepares a migration. After that, you pay per node-hour for the migration nodes that ElastiCache runs to replicate your data, for as long as a migration is active. The ElastiCache Serverless cache is billed separately at standard data storage and ECPU rates, including during the free period. For pricing details, see Amazon ElastiCache pricing. Online migration is available in all commercial AWS Regions, the China Regions, and the AWS GovCloud (US) Regions.  To get started, create or select an empty ElastiCache Serverless cache to migrate into, then start the migration from the ElastiCache console or the AWS CLI. To learn more, see the documentation.
aws.amazon.com
October 20, 2026 at 11:10 PM
Amazon ElastiCache for Valkey introduces ElastiCache Insights

https://aws.amazon.com/elasticache/ for Valkey now features ElastiCache Insights, a pre-built dashboard in Amazon CloudWatch for your node-based clusters. ElastiCache Insights brings cluster health, memory, co...

#AWS #AmazonElasticache
Amazon ElastiCache for Valkey introduces ElastiCache Insights
https://aws.amazon.com/elasticache/ for Valkey now features ElastiCache Insights, a pre-built dashboard in Amazon CloudWatch for your node-based clusters. ElastiCache Insights brings cluster health, memory, compute, network, command throughput, latency, keyspace, and errors into a single view sourced from a set of OpenTelemetry metrics that ElastiCache publishes automatically. You can use ElastiCache Insights to check the health of your cache workloads across a Region at a glance, detect when a node nears its memory, network, or connection limits, and filter your view to a cluster, shard, node, or Availability Zone. You can also save a copy as the starting point for a custom dashboard tailored to your workload. With detailed monitoring, you can choose metrics to publish every 15 seconds and view them on the Metrics tab or in your custom dashboard. https://aws.amazon.com/cloudwatch/pricing/ applies to ElastiCache detailed monitoring. To get started, open the Metrics tab for a cluster in the https://console.aws.amazon.com/elasticache/ and choose View in ElastiCache Insights. You can also choose ElastiCache Insights under Infrastructure Monitoring in the Amazon CloudWatch console. ElastiCache Insights is available for node-based Valkey clusters in all AWS Regions where Amazon CloudWatch supports OpenTelemetry metrics. To learn more about ElastiCache Insights, see https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/otel-metrics.html#otel-metrics.insights-dashboard in the Amazon ElastiCache User Guide.
aws.amazon.com
October 12, 2026 at 7:05 PM
🆕 Amazon ElastiCache for Valkey now offers ElastiCache Insights, a CloudWatch dashboard for monitoring node-based clusters, providing detailed metrics on health, memory, network, and more. Available in all AWS regions supporting OpenTelemetry metrics.

#AWS #AmazonElasticache
Amazon ElastiCache for Valkey introduces ElastiCache Insights
Amazon ElastiCache for Valkey now features ElastiCache Insights, a pre-built dashboard in Amazon CloudWatch for your node-based clusters. ElastiCache Insights brings cluster health, memory, compute, network, command throughput, latency, keyspace, and errors into a single view sourced from a set of OpenTelemetry metrics that ElastiCache publishes automatically. You can use ElastiCache Insights to check the health of your cache workloads across a Region at a glance, detect when a node nears its memory, network, or connection limits, and filter your view to a cluster, shard, node, or Availability Zone. You can also save a copy as the starting point for a custom dashboard tailored to your workload. With detailed monitoring, you can choose metrics to publish every 15 seconds and view them on the Metrics tab or in your custom dashboard. CloudWatch pricing for OpenTelemetry metrics applies to ElastiCache detailed monitoring. To get started, open the Metrics tab for a cluster in the Amazon ElastiCache console and choose View in ElastiCache Insights. You can also choose ElastiCache Insights under Infrastructure Monitoring in the Amazon CloudWatch console. ElastiCache Insights is available for node-based Valkey clusters in all AWS Regions where Amazon CloudWatch supports OpenTelemetry metrics. To learn more about ElastiCache Insights, see Monitoring ElastiCache with OpenTelemetry metrics in the Amazon ElastiCache User Guide.
aws.amazon.com
October 12, 2026 at 7:10 PM
🆕 Amazon ElastiCache for Valkey now supports OpenTelemetry metrics in CloudWatch, providing Standard and Detailed monitoring modes for enhanced cluster insights, no extra ElastiCache charge, and full Prometheus Query Language support, with Detailed mode publishing metrics …

#AWS #AmazonElasticache
Amazon ElastiCache for Valkey now supports OpenTelemetry metrics and detailed monitoring
Amazon ElastiCache for Valkey now publishes OpenTelemetry metrics to Amazon CloudWatch for your node-based clusters, and each metric carries attributes you can filter and aggregate on with Prometheus Query Language (PromQL) expressions. ElastiCache now offers two monitoring modes. Standard monitoring, the existing experience, continues to publish CloudWatch Metrics (Classic) every 60 seconds and now also publishes a core set of OpenTelemetry metrics at the same interval at no additional charge. Detailed monitoring, the new mode, lets you select from the full set of OpenTelemetry metrics and publish them every 15 seconds. With OpenTelemetry metrics, you can detect any node in a cluster nearing its connection limit, break errors down by type during an incident, or forecast if a node will run out of memory. You can run these queries in CloudWatch and Grafana, keeping PromQL skills your team already has. With detailed monitoring, you can balance diagnostic depth and cost, with 15-second metrics enabling detection of short-lived events like latency spikes. The core set of OpenTelemetry metrics also powers ElastiCache Insights, a pre-built dashboard in Amazon CloudWatch. To get started, open the Metrics tab for a cluster in the Amazon ElastiCache console, select Detailed, and choose Configure detailed metrics. OpenTelemetry metrics and detailed monitoring are available for node-based Valkey clusters in all AWS Regions where Amazon CloudWatch supports OpenTelemetry metrics. There is no additional charge from ElastiCache for detailed monitoring. CloudWatch pricing for OpenTelemetry metrics applies to the detailed monitoring metrics you select, alarms you create, and PromQL API queries you run. To learn more, see Monitoring ElastiCache with OpenTelemetry metrics in the Amazon ElastiCache User Guide.
aws.amazon.com
October 2, 2026 at 7:10 PM
Amazon ElastiCache for Valkey now supports OpenTelemetry metrics and detailed monitoring

https://aws.amazon.com/elasticache/ for Valkey now publishes OpenTelemetry metrics to Amazon CloudWatch for your node-based clusters, and each metric carries attributes you can filte...

#AWS #AmazonElasticache
Amazon ElastiCache for Valkey now supports OpenTelemetry metrics and detailed monitoring
https://aws.amazon.com/elasticache/ for Valkey now publishes OpenTelemetry metrics to Amazon CloudWatch for your node-based clusters, and each metric carries attributes you can filter and aggregate on with Prometheus Query Language (PromQL) expressions. ElastiCache now offers two monitoring modes. Standard monitoring, the existing experience, continues to publish CloudWatch Metrics (Classic) every 60 seconds and now also publishes a core set of OpenTelemetry metrics at the same interval at no additional charge. Detailed monitoring, the new mode, lets you select from the full set of OpenTelemetry metrics and publish them every 15 seconds. With OpenTelemetry metrics, you can detect any node in a cluster nearing its connection limit, break errors down by type during an incident, or forecast if a node will run out of memory. You can run these queries in CloudWatch and Grafana, keeping PromQL skills your team already has. With detailed monitoring, you can balance diagnostic depth and cost, with 15-second metrics enabling detection of short-lived events like latency spikes. The core set of OpenTelemetry metrics also powers https://console.aws.amazon.com/cloudwatch/home#dashboards/insights/elasticache, a pre-built dashboard in Amazon CloudWatch. To get started, open the Metrics tab for a cluster in the https://console.aws.amazon.com/elasticache/, select Detailed, and choose Configure detailed metrics. OpenTelemetry metrics and detailed monitoring are available for node-based Valkey clusters in all AWS Regions where Amazon CloudWatch supports OpenTelemetry metrics. There is no additional charge from ElastiCache for detailed monitoring. https://aws.amazon.com/cloudwatch/pricing/ applies to the detailed monitoring metrics you select, alarms you create, and PromQL API queries you run. To learn more, see https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/otel-metrics.html in the Amazon ElastiCache User Guide.
aws.amazon.com
October 2, 2026 at 7:05 PM
Amazon ElastiCache adds thirteen new Amazon CloudWatch metrics for network capacity planning and engine diagnostics

https://aws.amazon.com/elasticache/ customers can now detect network throttling, memory fragmentation, and connection exhaustion, using thirteen new Amazon...

#AWS #AmazonElasticache
Amazon ElastiCache adds thirteen new Amazon CloudWatch metrics for network capacity planning and engine diagnostics
https://aws.amazon.com/elasticache/ customers can now detect network throttling, memory fragmentation, and connection exhaustion, using thirteen new Amazon CloudWatch metrics for node-based clusters. You can monitor these host-level and engine-level diagnostics directly from CloudWatch without running INFO commands on individual nodes or calculating baselines from raw byte counters. Network capacity: NetworkBaselineUsageInPercentage, NetworkBaselineUsageOutPercentage, NetworkBaselineMaxUsageInPercentage, and NetworkBaselineMaxUsageOutPercentage report network utilization relative to instance baseline, enabling portable alarms that remain valid across instance type changes. Values above 100 percent signal that a host is consuming burst credits, a leading indicator that a sustained workload will eventually lead to credit exhaustion and throttling. The variants capturing max report per-second bursts that averaged metrics can hide. Memory health: UsedMemoryDataset shows memory consumed by actual stored data excluding engine overhead. AllocatorFragmentationBytes and AllocatorFragmentationRatio isolate fragmentation that the https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/ParameterGroups.Engine.html can address. MajorPageFaults captures OS-level page faults that indicate memory pressure beyond what the engine can surface. Connectivity health: BlockedConnections and RejectedConnections surface connections waiting on blocking commands and connections turned away when the maxclients limit is reached. When RejectedConnections is non-zero, raise maxclients or diagnose client-side connection pool leaks. Pub/sub workloads: PubSubChannels and PubSubShardChannels expose active classic and sharded channels on each node. When classic channel counts are growing with utilization, consider switching to sharded pub/sub to scale horizontally. Command throughput: ProcessedCommands provides total command throughput across all command types. These metrics are available for node-based clusters in all commercial AWS Regions and the AWS China and AWS GovCloud (US) Regions where ElastiCache is supported, at no additional cost. To get started, view the new metrics in the https://console.aws.amazon.com/elasticache/ monitoring tab or in the AWS/ElastiCache namespace in the CloudWatch console. To learn more, see https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheMetrics.HostLevel.htmland https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/CacheMetrics.Redis.html.
aws.amazon.com
May 6, 2026 at 9:18 PM
#うひーメモ
2023-12-05 00:31:57
Amazon ElastiCacheがサーバーレスになって運用がバチクソ楽になった #AWSreInvent
#技術系ブログ等
#amazonelasticache
#awsreinventaws
#memcached
Amazon ElastiCacheがサーバーレスになって運用がバチクソ楽になった #AWSreInvent
AWSが提供するRedis・Memcachedなどのキャッシュ系マネージドサービスAmazonElastiCacheのサーバーレス版が年のreInventで発表されましたRedis・MemcachedやA
dev.classmethod.jp
December 4, 2023 at 3:31 PM
#うひーメモ
2023-11-28 09:03:43
Amazon ElastiCacheの耐障害性を考える
#Program
#amazonelasticache
#devopsonaws
Amazon ElastiCacheの耐障害性を考える
はじめにこの記事はDevOpsonAWS大全の一部ですDevOpsonAWS大全の一覧はこちらこの記事ではAmazonElastiCacheを耐障害性の観点から超詳細解説していま
qiita.com
November 28, 2023 at 12:03 AM
#うひーメモ
2023-11-20 18:05:18
週刊AWS – 2023/11/13週
#AWS
#amazonbedrock
#amazonelasticache
#awslambdajava
週刊AWS – 2023/11/13週
PartyRockの発表StepFunctionsが再開機能をサポートLlamaChatBとCohereがAmazonBedrockで提供開始RedisがAmazonElastiCacheで提供開始AWSLambdaJavaサポート
aws.amazon.com
November 20, 2023 at 9:05 AM