# Amazon ElastiCache

Amazon ElastiCache is a fully managed caching service compatible with Valkey, Memcached, and Redis OSS, providing microsecond-latency caching for applications.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Handling large volume of transactions with AWS Lambda Managed Instances

DevFeed: [Handling large volume of transactions with AWS Lambda Managed Instances](<https://devfeed.tech/articles/handling-large-volume-of-transactions-with-aws-lambda-managed-instances-144755.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/handling-large-volume-of-transactions-with-aws-lambda-managed-instances/>)

Author: Mythili Annamalai Sekar

Published: 2026-11-19T21:20:28Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [can](<https://devfeed.tech/tags/can.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [compute](<https://devfeed.tech/tags/compute.md>), [concert](<https://devfeed.tech/tags/concert.md>), [handling](<https://devfeed.tech/tags/handling.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [large](<https://devfeed.tech/tags/large.md>), [managed](<https://devfeed.tech/tags/managed.md>), [post](<https://devfeed.tech/tags/post.md>), [reference](<https://devfeed.tech/tags/reference.md>), [run](<https://devfeed.tech/tags/run.md>), [sample](<https://devfeed.tech/tags/sample.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [test](<https://devfeed.tech/tags/test.md>), [this](<https://devfeed.tech/tags/this.md>), [transactions](<https://devfeed.tech/tags/transactions.md>), [volume](<https://devfeed.tech/tags/volume.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

AWS Lambda Managed Instances runs Lambda functions on EC2 capacity in the customer's account, with AWS managing provisioning, scaling, patching, and routing. Its warm execution environments can be scaled ahead of scheduled bursts and back down afterward; the article's ticketing sample reports 40,000 requests per second for 120 seconds across tests from 5,000 to 40,000 requests per second, with p99 latency within a 3 ms band. The design uses a Valkey atomic queue counter, DynamoDB conditional seat holds with 180-second TTLs, and a transaction that confirms bookings and writes records atomically. Setup requires AWS CLI, SAM, Python 3.13+, a VPC, and network access to DynamoDB and CloudWatch; peak tests also need higher EC2 vCPU and API Gateway throttle quotas. Managed Instances uses EC2 pricing plus a 15% management fee; the article estimates about $37 per simulated burst.

### Source excerpt

AWS Lambda Managed Instances keeps compute capacity warm before a predictable traffic burst and scales it back down afterward. This post walks through a concert-ticketing reference implementation that sustains 40,000 transactions per second for 120 seconds, with a deployable sample you can run, test, and clean up.

## Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache

DevFeed: [Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache](<https://devfeed.tech/articles/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache-144311.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache/>)

Author: Paul Ross

Published: 2026-11-19T18:39:15Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-managed-grafana](<https://devfeed.tech/tags/amazon-managed-grafana.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [insights](<https://devfeed.tech/tags/insights.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [latency](<https://devfeed.tech/tags/latency.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [node](<https://devfeed.tech/tags/node.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [query](<https://devfeed.tech/tags/query.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache for Valkey sends engine and host metrics to CloudWatch in OpenTelemetry format without an exporter or collector. The article demonstrates using ElastiCache Insights to locate a hot shard or node, then PromQL to rank nodes, inspect command latency, and alarm across all nodes as cluster membership changes. Standard monitoring publishes core metrics every 60 seconds; selected detailed metrics arrive every 15 seconds and can expose short latency spikes that a longer window smooths out. Core metrics and ElastiCache Insights are free, while selected detailed metrics, PromQL API scans, and alarms incur charges. The walkthrough requires a node-based Valkey cluster in a supported Region; its Grafana guidance covers version 13 or later, with a separate Prometheus data source approach for version 12.4.

### Source excerpt

Amazon ElastiCache for Valkey now offers OpenTelemetry metrics, detailed monitoring, ElastiCache Insights, and PromQL. This post walks through one troubleshooting path: turn on detailed monitoring, find a hot shard, query with PromQL, catch a short latency spike, and create one alarm that watches every node.

## Amazon ElastiCache Serverless turns three

DevFeed: [Amazon ElastiCache Serverless turns three](<https://devfeed.tech/articles/amazon-elasticache-serverless-turns-three-144309.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/amazon-elasticache-serverless-turns-three/>)

Author: Karthik Konaparthi

Published: 2026-11-19T18:35:55Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-coding-assistant](<https://devfeed.tech/tags/ai-coding-assistant.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [costs](<https://devfeed.tech/tags/costs.md>), [customers](<https://devfeed.tech/tags/customers.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [patch](<https://devfeed.tech/tags/patch.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

Amazon ElastiCache Serverless removes cache capacity planning by scaling with demand; billing is based on stored data (GB-hours) and requests (ECPUs). The article highlights Valkey's faster scaling, lower storage minimum and pricing, plus a 30% Database Savings Plans discount with a one-year commitment. New Valkey 9.0 features include public endpoints (IAM authentication and TLS 1.3 required), online migration from cluster-mode Valkey or Redis OSS with traffic continuing, search, and write-through DynamoDB caching. AWS applies minor and patch updates automatically; major-version upgrades are customer scheduled, and recent patching improvements preserve more connections and in-flight requests. Serverless is presented as a fit for variable traffic and many separate caches; node-based deployments may suit steady workloads, especially with reserved nodes and capacity-tuning staff. The article recommends estimating costs from actual stored data and representative request volume, then checking CloudWatch metrics in a trial workload. Serverless clients must support cluster mode and TLS.

### Source excerpt

In this post, we look back at three years of Amazon ElastiCache Serverless, show how customers use it, cover what we launched this year and how we patch your cache with minimal disruption, show how to estimate what it costs, and help you decide whether it fits your workload.

## Announcing distributed KV caching for self-hosted LLMs with Amazon ElastiCache

DevFeed: [Announcing distributed KV caching for self-hosted LLMs with Amazon ElastiCache](<https://devfeed.tech/articles/announcing-distributed-kv-caching-for-self-hosted-llms-with-amazon-elasticache-142000.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/announcing-distributed-kv-caching-for-self-hosted-llms-with-amazon-elasticache/>)

Author: Meet Bhagdev

Published: 2026-11-18T23:45:25Z

Content type: release

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Self Hosted AI Tools](<https://devfeed.tech/topics/self-hosted-ai-tools.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [TensorRT-LLM](<https://devfeed.tech/topics/tensorrt-llm.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [benefits](<https://devfeed.tech/tags/benefits.md>), [caching](<https://devfeed.tech/tags/caching.md>), [costs](<https://devfeed.tech/tags/costs.md>), [distributed-kv](<https://devfeed.tech/tags/distributed-kv.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [inference-costs](<https://devfeed.tech/tags/inference-costs.md>), [llm-inference](<https://devfeed.tech/tags/llm-inference.md>), [llm-inference-costs](<https://devfeed.tech/tags/llm-inference-costs.md>), [llms](<https://devfeed.tech/tags/llms.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-llms](<https://devfeed.tech/tags/self-hosted-llms.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Distributed KV caching with Amazon ElastiCache for Valkey adds a shared L2 tier across a GPU fleet, letting vLLM, SGLang, and TensorRT-LLM reuse prompt KV state when local GPU or host caches miss. An open-source LMCache connector requires a configuration change; cache.i8ge.48xlarge nodes use DRAM and NVMe tiering and RDMA over EFA. In tested workloads, gains depended on cache hits and prompt length: shared-document Q&A doubled requests per second and cut cost per million output tokens by 40% while meeting the stated interactivity targets; coding-agent and assistant throughput also increased. Reported TTFT reductions ranged from 55% to 93% across tested models. The post says the least benefit is expected for small deployments with KV state fitting in GPU memory, workloads without prompt reuse, and long outputs from short prompts. It recommends using the free KVTrace tool to estimate hit rate, savings, and cache size before deployment; estimates use hashed prompt data.

### Source excerpt

Today, we are announcing the general availability of distributed KV caching with Amazon ElastiCache for Valkey, a capability that cuts self-hosted LLM inference costs by up to 40% and time to first token by up to 80%. Learn how it works, review benchmark results across workloads and models, deploy it on your own GPU fleet, and size the savings with the open-source KVTrace tool.

## Which AWS Database should you use?

DevFeed: [Which AWS Database should you use?](<https://devfeed.tech/articles/which-aws-database-should-you-use-141386.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/which-aws-database-should-you-use/>)

Author: Joseph Idziorek

Published: 2026-11-18T17:10:51Z

Content type: comparison

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [Amazon DocumentDB](<https://devfeed.tech/topics/amazon-documentdb.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-com](<https://devfeed.tech/tags/amazon-com.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [building](<https://devfeed.tech/tags/building.md>), [customer-value](<https://devfeed.tech/tags/customer-value.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [job](<https://devfeed.tech/tags/job.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [legacy-application](<https://devfeed.tech/tags/legacy-application.md>), [managed](<https://devfeed.tech/tags/managed.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [selection](<https://devfeed.tech/tags/selection.md>), [thought-leadership](<https://devfeed.tech/tags/thought-leadership.md>)

### AI overview

The article recommends choosing an AWS database by workload: for migrations, use the managed equivalent of the existing database, starting with serverless when possible; for legacy relational refactoring, start with Aurora PostgreSQL serverless, and adopt multiple purpose-built databases only when access patterns or scaling needs warrant it. For new applications, use a database the team already knows; otherwise, start with PostgreSQL, with Aurora PostgreSQL serverless for managed PostgreSQL or Aurora DSQL for relational workloads needing scale and operational simplicity. DynamoDB is suggested for known access patterns and very high throughput, while ElastiCache for Valkey serverless can complement databases for caching. The article points specialized graph, time-series, and document workloads to corresponding services, and names Neptune for connected-data needs in agentic applications. These are opinionated starting points; the article says to match the choice to access patterns, scale, and operational constraints.

### Source excerpt

Database selection is a foundational decision when building an application. Choosing the right database enables you to focus effort on building customer value while the database scales with demand. AWS offers several fully managed database services. That breadth serves the diversity of the millions of customers who operate databases on AWS, but it raises a practical question: Where do I start? Based on our collective experience working with database customers, this post provides a direct, opinionated answer focused on the job you are trying to perform: migrating an existing workload, refactoring a legacy application, or building something new.

## Accelerate your DynamoDB workloads with DynamoDB caching with Amazon ElastiCache Serverless for Valkey

DevFeed: [Accelerate your DynamoDB workloads with DynamoDB caching with Amazon ElastiCache Serverless for Valkey](<https://devfeed.tech/articles/accelerate-your-dynamodb-workloads-with-dynamodb-caching-with-amazon-elasticache-serverless-for-valkey-138649.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/accelerate-your-dynamodb-workloads-with-dynamodb-caching-with-amazon-elasticache-serverless-for-valkey/>)

Author: Varun Gautam

Published: 2026-11-17T23:39:18Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [valkey](<https://devfeed.tech/topics/valkey.md>)

Tags: [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [costs](<https://devfeed.tech/tags/costs.md>), [dynamodb](<https://devfeed.tech/tags/dynamodb.md>), [hot-keys](<https://devfeed.tech/tags/hot-keys.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [keys](<https://devfeed.tech/tags/keys.md>), [minimal](<https://devfeed.tech/tags/minimal.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [serve](<https://devfeed.tech/tags/serve.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [write](<https://devfeed.tech/tags/write.md>), [write-through](<https://devfeed.tech/tags/write-through.md>)

### AI overview

DynamoDB caching for Amazon ElastiCache Serverless for Valkey routes supported DynamoDB SDK operations through a configured client, serving eventually consistent reads from cache and updating entries after writes reach DynamoDB. Strongly consistent reads bypass the cache and refresh it; unsupported operations and uncached tables go directly to DynamoDB. This can reduce hot-key read pressure and read charges, with sub-millisecond cache responses, while writes still incur DynamoDB costs. Setup requires a new Valkey 9+ serverless cache with DynamoDB caching enabled and IAM authentication, plus client configuration and permissions. The article's example estimates 40-46% lower monthly cost at 20,000 requests per second and a 90% hit rate, but says storage costs can outweigh savings below workload-dependent traffic thresholds; results depend heavily on hit rate and resident data size.

### Source excerpt

DynamoDB caching with Amazon ElastiCache Serverless for Valkey brings write-through caching to Amazon DynamoDB with sub-millisecond reads and minimal application changes. Serve hot keys from cache, reduce read throttling, and lower read costs while your application keeps calling the DynamoDB API as it does today.

## Migrate from Amazon EC2 to Amazon ElastiCache Serverless with zero downtime

DevFeed: [Migrate from Amazon EC2 to Amazon ElastiCache Serverless with zero downtime](<https://devfeed.tech/articles/migrate-from-amazon-ec2-to-amazon-elasticache-serverless-with-zero-downtime-129586.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/migrate-from-amazon-ec2-to-amazon-elasticache-serverless-with-zero-downtime/>)

Author: Rong Zhang

Published: 2026-11-11T18:12:18Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [downtime](<https://devfeed.tech/topics/downtime.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>)

Tags: [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-command-line-interface-aws-cli](<https://devfeed.tech/tags/aws-command-line-interface-aws-cli.md>), [aws-govcloud-us](<https://devfeed.tech/tags/aws-govcloud-us.md>), [console](<https://devfeed.tech/tags/console.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [managed](<https://devfeed.tech/tags/managed.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [migration](<https://devfeed.tech/tags/migration.md>), [online](<https://devfeed.tech/tags/online.md>), [oss](<https://devfeed.tech/tags/oss.md>), [redis](<https://devfeed.tech/tags/redis.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache's online migration lets workloads on self-managed Valkey or Redis OSS on EC2 move to ElastiCache Serverless for Valkey while clients keep using one endpoint. ElastiCache validates the source, provisions migration infrastructure, performs a full data sync followed by replication of writes, then routes the endpoint to the serverless cache at a fully synced window. Cutover can be manual, allowing validation first, or automatic; all shards switch together, and traffic continues through the same endpoint. At launch, serverless migrations require cluster-mode sources running Valkey 7.2-8.1 or Redis OSS 4.0-7.2, and target Valkey 7.2, 8.1, or 9.0 at least as new as the source. Prerequisites include an empty reachable target, TLS-capable clients, and source credentials and CA certificates where applicable. The migration is free for 180 days from the account's first preparation; afterward migration nodes are billed per node-hour, while the serverless cache is charged separately. The source should retain headroom and stable network, credentials, certificates, and shard layout until migration completes.

### Source excerpt

On October 20, 2026, Amazon ElastiCache introduced online migration to ElastiCache Serverless for Valkey from self-managed Valkey and Redis OSS on Amazon EC2 with zero downtime. This post shows what's supported at launch, how online migration works, and how to run a migration in the ElastiCache console.

## How Flickr modernized caching with Amazon ElastiCache for Valkey

DevFeed: [How Flickr modernized caching with Amazon ElastiCache for Valkey](<https://devfeed.tech/articles/how-flickr-modernized-caching-with-amazon-elasticache-for-valkey-129585.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-flickr-modernized-caching-with-amazon-elasticache-for-valkey/>)

Author: Wilson Lam

Published: 2026-11-11T15:54:48Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [Data Quality](<https://devfeed.tech/topics/data-quality.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [all](<https://devfeed.tech/tags/all.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [end-user](<https://devfeed.tech/tags/end-user.md>), [failover](<https://devfeed.tech/tags/failover.md>), [layer](<https://devfeed.tech/tags/layer.md>), [more](<https://devfeed.tech/tags/more.md>), [moving](<https://devfeed.tech/tags/moving.md>), [over](<https://devfeed.tech/tags/over.md>), [post](<https://devfeed.tech/tags/post.md>), [redis](<https://devfeed.tech/tags/redis.md>), [team](<https://devfeed.tech/tags/team.md>), [this](<https://devfeed.tech/tags/this.md>), [user](<https://devfeed.tech/tags/user.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Flickr moved more than 40 Redis clusters behind Twemproxy to cluster-mode Amazon ElastiCache for Valkey deployments, replacing Predis with PhpRedis and enabling multi-AZ automatic failover. Valkey's Redis OSS API compatibility through version 7.2 allowed an in-place engine swap without application changes or data migration. For topology changes, Flickr rolled out workload by workload, starting with regenerable data; data-sensitive workloads were copied with RIOT, using scan mode for bulk replication and live mode to keep data synchronized. A rollout exposed temporarily stale cached content from keys that had not synchronized, prompting targeted database backfill and use of RIOT compare mode before later cutovers. On the most fragmented workload, increasing RIOT threads and reducing batch size resolved stalled replication. After consolidation, Flickr reports monthly ElastiCache spend fell about 5%, despite improved replication and failover; parallel clusters temporarily raised costs during the migration.

### Source excerpt

Flickr, part of SmugMug, serves over 100 million photographers. In this post, the Flickr team shares how they modernized their caching layer by migrating from Redis and Twemproxy to Amazon ElastiCache for Valkey, consolidating more than 40 clusters, enabling cluster mode and multi-AZ failover, and moving to PhpRedis, all with no end-user disruption.

## Multi-tenancy with Amazon ElastiCache: Choosing the right isolation model

DevFeed: [Multi-tenancy with Amazon ElastiCache: Choosing the right isolation model](<https://devfeed.tech/articles/multi-tenancy-with-amazon-elasticache-choosing-the-right-isolation-model-129587.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/multi-tenancy-with-amazon-elasticache-choosing-the-right-isolation-model/>)

Author: Maria Gutovsky

Published: 2026-11-11T15:40:48Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-key-management-service-aws-kms](<https://devfeed.tech/tags/aws-key-management-service-aws-kms.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [multi-tenancy](<https://devfeed.tech/tags/multi-tenancy.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [saas](<https://devfeed.tech/tags/saas.md>), [shared-infrastructure](<https://devfeed.tech/tags/shared-infrastructure.md>), [tenant](<https://devfeed.tech/tags/tenant.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

The article frames ElastiCache tenant isolation as a choice between failure containment, trust boundaries, compliance needs, tenant count, and cost. Dedicated clusters provide physical and resource isolation but increase routing, monitoring, quota, and capacity burdens; serverless lowers operational overhead and cost for light-use tenants, though its per-Region cache quota is lower. Shared-cluster ACL/RBAC enforces key access but leaves CPU and memory shared and still depends on correct key prefixes. Valkey 9.1 database-scoped ACLs remove prefix construction while preserving shared-resource risks; the article recommends load-testing as database counts grow. It proposes mixing tiers behind a tenant-aware resolver that caches endpoint/database mappings in process. Cluster encryption protects at-rest and in-transit data with a cluster-level key, not plaintext in memory. Client-side encryption with the AWS Encryption SDK hierarchical keyring can provide tenant-specific keys; searchable cache lookups require application-built HMAC beacons, which leak equality.

### Source excerpt

Choosing a multi-tenancy isolation model for Amazon ElastiCache for Valkey comes up in nearly every SaaS architecture review. This post walks through the options, from dedicated clusters to shared infrastructure with per-tenant encryption, and shows how to match each model to your blast radius and compliance requirements.

## Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey

DevFeed: [Topstep's migration journey: Self-managed Redis OSS to Amazon ElastiCache for Valkey](<https://devfeed.tech/articles/topstep-s-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey-123996.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/topsteps-migration-journey-self-managed-redis-oss-to-amazon-elasticache-for-valkey/>)

Author: Gbeminiyi Abolarin

Published: 2026-11-09T16:59:06Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [cname](<https://devfeed.tech/tags/cname.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [migration](<https://devfeed.tech/tags/migration.md>), [oss](<https://devfeed.tech/tags/oss.md>), [redis](<https://devfeed.tech/tags/redis.md>), [tls](<https://devfeed.tech/tags/tls.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Topstep moved about 53 million keys from a single-node Redis OSS 7.4 instance to a Multi-AZ Amazon ElastiCache for Valkey 7.2.6 cluster using RedisShake in PSYNC mode. Since its source version fell outside the managed migration's supported range and the team required a blue/green rollback path, it replicated commands across peered VPCs, validated key counts and application behavior, then cut over by changing a Route 53 record. The change took seconds; the source remained available during a soak period. Valkey's protocol compatibility avoided code changes apart from TLS configuration. Because the custom DNS name did not match the cluster certificate, Topstep kept CA verification enabled while validating against an allowlist of AWS endpoint names. The team reports automatic Multi-AZ failover, managed patching and backups, read P99 latency around 1.25 ms and write P99 around 0.5 ms, and 1-2 engineer-days per month freed from maintenance.

### Source excerpt

Topstep migrated roughly 53 million keys from self-managed Redis OSS to a fully managed, Multi-AZ Amazon ElastiCache for Valkey cluster. Using RedisShake and a single Amazon Route 53 DNS change, the team completed a blue/green cutover in seconds with no application code changes beyond a small TLS configuration update.

## 6 Best Platforms for Semantic Caching in Enterprise LLM Apps

DevFeed: [6 Best Platforms for Semantic Caching in Enterprise LLM Apps](<https://devfeed.tech/articles/6-best-platforms-for-semantic-caching-in-enterprise-llm-apps-118610.md>)

Original publisher: [Read original article](<https://www.lyzr.ai/blog/platforms-for-semantic-caching-in-enterprise-llm-apps/>)

Author: Lyzr Team

Published: 2026-11-05T08:42:25Z

Content type: comparison

Language: en

Sources: [Lyzr.ai](<https://devfeed.tech/sources/lyzr-ai.md>)

Topics: [Large Language Model](<https://devfeed.tech/topics/llm.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Redis](<https://devfeed.tech/topics/redis.md>)

Tags: [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apps](<https://devfeed.tech/tags/apps.md>), [best](<https://devfeed.tech/tags/best.md>), [caching](<https://devfeed.tech/tags/caching.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [llm](<https://devfeed.tech/tags/llm.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [semantic](<https://devfeed.tech/tags/semantic.md>)

### AI overview

Semantic caching can cut LLM costs, but similarity hits can confidently return another question's answer, so accuracy and request ordering matter more than hit rate alone. In the cited banking test, an ATM query received loan-balance instructions; AWS's benchmark still had roughly one incorrect cached answer in fourteen at a strict threshold. The excerpt compares four gateways--Lyzr OpenController, Kong AI Gateway, Azure API Management and Portkey--with Redis LangCache and ElastiCache for Valkey, which require teams to build surrounding policy and lookup logic. Their differences include where identity and guardrail checks run, tenant partitioning, exact-match behavior, threshold semantics, deployment and operational requirements. It recommends putting checks before lookups, scoping entries by tenant, avoiding response caching for changing claim status, and measuring false hits on real traffic. The article is available here as an excerpt, so this overview does not establish full-document coverage.

### Source excerpt

TL;DR In a test of 1,000 banking queries published on InfoQ in November 2025, a customer asking where to find an ATM was served instructions...

## Nemo: Efficient Caching with Index Pushdown for Disaggregated OLTP Databases

DevFeed: [Nemo: Efficient Caching with Index Pushdown for Disaggregated OLTP Databases](<https://devfeed.tech/articles/nemo-efficient-caching-with-index-pushdown-for-disaggregated-oltp-databases-101504.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.33306>)

Author: Wenjie Hu, Xinjing Zhou, Zhihan Guo, Xiangpeng Hao, Xiangyao Yu

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>), [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [databases](<https://devfeed.tech/tags/databases.md>), [index](<https://devfeed.tech/tags/index.md>)

### AI overview

Nemo targets network bottlenecks in storage-disaggregated OLTP by pushing the full index to storage and caching hot records at compute. Its tree-structured record buffer combines caching and buffering for point and range queries, while caching negative search results reduces remote probes when a record is absent. Nemo also provides phantom protection without requiring knowledge of storage-side data layout. In the reported experiments, it outperformed page-based B+Tree and 2-Tree by up to 11.42x and 2.97x on positive point queries, and a hash-indexed record cache by up to 4.76x on negative searches. For phantom protection, it beat PCL by up to 1.55x in a dense key domain and maintained stable performance as the domain became large and sparse, where PCL degraded sharply.

### Source excerpt

arXiv:2610.33306v1 Announce Type: new Abstract: Storage-disaggregated databases decouple compute from storage, improving elasticity but suffering from network bottlenecks. Most cloud databases use page-based B+trees and buffer pools. Under disaggregation, each index traversal incurs serial network round-trips. Page-granularity transfers and caching also amplify network traffic and lower cache efficiency. Pushing down the full index to storage and caching only hot records at compute is appealing, but an efficient design must (1) provide a holistic record cache that accelerates both point and range queries, (2) mitigate the negative search penalty of confirming non-existence via remote probes, and (3) enforce phantom protection despite the index being encapsulated by the storage service. We introduce Nemo, a holistic index-and-buffer design optimized for storage-disaggregated OLTP with index pushdown. Nemo employs a tree-structured record buffer that unifies caching and buffering and accelerates both point and range queries. It further reduces the negative search penalty by caching negative search results. Nemo provides phantom protection that requires no knowledge of the storage-side data layout and is robust against large key domains, varying data skew, and partition schemes. Experiments show that Nemo outperforms page-based B+Tree and the state-of-the-art 2-Tree by up to 11.42x and 2.97x on positive point queries, and achieves up to 4.76x speedup on negative searches over a hash-indexed record cache. For phantom protection, Nemo outperforms PCL by up to 1.55x even under a dense key domain. Moreover, Nemo maintains stable performance while PCL degrades sharply as the key domain grows large and sparse.

## AWS Weekly Roundup: Amazon Polly Generative engine, TorchNeuron for Trainium, and more (October 26, 2026)

DevFeed: [AWS Weekly Roundup: Amazon Polly Generative engine, TorchNeuron for Trainium, and more (October 26, 2026)](<https://devfeed.tech/articles/aws-weekly-roundup-amazon-polly-generative-engine-torchneuron-for-trainium-and-more-october-26-2026-101068.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/aws-weekly-roundup-amazon-polly-generative-engine-torchneuron-for-trainium-and-more-october-26-2026/>)

Author: Daniel Abib

Published: 2026-10-26T15:02:24Z

Content type: news

Language: en

Sources: [AWS News Blog](<https://devfeed.tech/sources/aws-news-blog.md>)

Topics: [aws inspector](<https://devfeed.tech/topics/aws-inspector.md>), [AWS Trainium](<https://devfeed.tech/topics/aws-trainium.md>), [neuron](<https://devfeed.tech/topics/neuron.md>), [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [AWS AI chips](<https://devfeed.tech/topics/aws-ai-chips.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-elastic-file-system-efs](<https://devfeed.tech/tags/amazon-elastic-file-system-efs.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-polly](<https://devfeed.tech/tags/amazon-polly.md>), [amazon-sagemaker-ai](<https://devfeed.tech/tags/amazon-sagemaker-ai.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloud-financial-management](<https://devfeed.tech/tags/aws-cloud-financial-management.md>), [aws-datasync](<https://devfeed.tech/tags/aws-datasync.md>), [aws-neuron](<https://devfeed.tech/tags/aws-neuron.md>), [aws-trainium](<https://devfeed.tech/tags/aws-trainium.md>), [aws-waf](<https://devfeed.tech/tags/aws-waf.md>), [call](<https://devfeed.tech/tags/call.md>), [engine](<https://devfeed.tech/tags/engine.md>), [generative](<https://devfeed.tech/tags/generative.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [i](<https://devfeed.tech/tags/i.md>), [markets](<https://devfeed.tech/tags/markets.md>), [news](<https://devfeed.tech/tags/news.md>), [october](<https://devfeed.tech/tags/october.md>), [office](<https://devfeed.tech/tags/office.md>), [point](<https://devfeed.tech/tags/point.md>), [rds-for-oracle](<https://devfeed.tech/tags/rds-for-oracle.md>), [returning](<https://devfeed.tech/tags/returning.md>), [security](<https://devfeed.tech/tags/security.md>), [small](<https://devfeed.tech/tags/small.md>), [torchneuron](<https://devfeed.tech/tags/torchneuron.md>), [trainium](<https://devfeed.tech/tags/trainium.md>), [week-in-review](<https://devfeed.tech/tags/week-in-review.md>), [weekly](<https://devfeed.tech/tags/weekly.md>), [weekly-roundup](<https://devfeed.tech/tags/weekly-roundup.md>)

### AI overview

AWS Continuum is generally available as a vulnerability-management service that builds a context graph across repositories and AWS environments, tests findings in an isolated sandbox, ranks attack paths, and proposes fixes as pull requests requiring human approval. AWS honeypot telemetry recorded exploitation attempts four days before disclosure of two CVEs, with proof-of-concept exploits circulating before the embargo lifted, underscoring the short response window described in the article. Other launches include Amazon ECS Gateway, which lets platform teams configure shared networking while application teams connect services (up to 25 services per ALB), and an Amazon Polly upgrade adding 14 voices, including two Brazilian Portuguese voices, at unchanged API and price. TorchNeuron adds native PyTorch support for Trainium through a configuration change; SageMaker AI training sessions manage GPU operations while charging for processed tokens; Bedrock adds schema-compliant JSON for Claude models; and ElastiCache Serverless supports zero-downtime Valkey or Redis OSS migration.

### Source excerpt

A few weeks ago I presented to a small group of commercial and technology leaders from Brazilian agribusiness at the AWS office in São Paulo. My talk ran through where generative AI fits across the different stages of an agribusiness operation, and the point I kept returning to is that the markets we call traditional [...]

## AWS Weekly Roundup: Prime Day 2026 by the numbers, Claude Haiku 5.5, Amazon Nova 2.5 Sonic, and more (October 13, 2026)

DevFeed: [AWS Weekly Roundup: Prime Day 2026 by the numbers, Claude Haiku 5.5, Amazon Nova 2.5 Sonic, and more (October 13, 2026)](<https://devfeed.tech/articles/aws-weekly-roundup-prime-day-2026-by-the-numbers-claude-haiku-5-5-amazon-nova-2-5-sonic-and-more-october-13-2026-86343.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/aws-weekly-roundup-prime-day-2026-by-the-numbers-claude-haiku-5-5-amazon-nova-2-5-sonic-and-more-october-13-2026/>)

Author: Daniel Abib

Published: 2026-10-13T15:59:06Z

Content type: news

Language: en

Sources: [AWS News Blog](<https://devfeed.tech/sources/aws-news-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [AWS Network Firewall](<https://devfeed.tech/topics/aws-network-firewall.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Postman Agent Mode](<https://devfeed.tech/topics/postman-agent-mode.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [Redpanda](<https://devfeed.tech/topics/redpanda-data-streaming.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-mode](<https://devfeed.tech/tags/agent-mode.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-guardduty](<https://devfeed.tech/tags/amazon-guardduty.md>), [amazon-nova](<https://devfeed.tech/tags/amazon-nova.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fault-injection-service-fis](<https://devfeed.tech/tags/aws-fault-injection-service-fis.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-re-invent](<https://devfeed.tech/tags/aws-re-invent.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-haiku-5-5](<https://devfeed.tech/tags/claude-haiku-5-5.md>), [news](<https://devfeed.tech/tags/news.md>), [nova](<https://devfeed.tech/tags/nova.md>), [prime-day](<https://devfeed.tech/tags/prime-day.md>), [strands-agents](<https://devfeed.tech/tags/strands-agents.md>), [week-in-review](<https://devfeed.tech/tags/week-in-review.md>)

### AI overview

This AWS weekly roundup covers Prime Day 2026 infrastructure metrics, including high request volumes across ElastiCache, DynamoDB, Lambda, and EBS, alongside launches and updates involving Claude Haiku 5.5, Nova 2.5 Sonic, GuardDuty, Kafka, and Redshift. It also highlights agent sandboxing and code security tools.

### Source excerpt

Some numbers are hard to picture until you sit with them for a moment. Last week we published the Prime Day 2026 metrics, and the one that stuck with me is 2.3 quadrillion: the daily requests Amazon ElastiCache peaked at during the event. Prime Day ran back in June, so this post always lands as [...]

## Reducing cross-AZ latency with the AWS Lambda metadata endpoint

DevFeed: [Reducing cross-AZ latency with the AWS Lambda metadata endpoint](<https://devfeed.tech/articles/reducing-cross-az-latency-with-the-aws-lambda-metadata-endpoint-84345.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/reducing-cross-az-latency-with-the-aws-lambda-metadata-endpoint/>)

Author: Daniel Abib

Published: 2026-10-09T19:41:24Z

Content type: tutorial

Language: en

Sources: [AWS Compute Blog](<https://devfeed.tech/sources/aws-compute-blog.md>)

Topics: [Availability](<https://devfeed.tech/topics/availability.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-memorydb](<https://devfeed.tech/tags/amazon-memorydb.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cache](<https://devfeed.tech/tags/cache.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [latency](<https://devfeed.tech/tags/latency.md>)

### AI overview

AWS Lambda functions can retrieve their Availability Zone ID from a metadata endpoint and use it to favor same-zone endpoints for services such as ElastiCache, RDS, and MemoryDB. The article explains authenticated access, caching and SnapStart considerations, and fallback routing to reduce cross-zone latency and support zone-aware resilience.

### Source excerpt

AWS Lambda now exposes Availability Zone metadata through an endpoint in the execution environment, so your function can discover its AZ ID with an HTTP request. Use it to prefer same-AZ endpoints for services like ElastiCache, Amazon RDS, and MemoryDB, reduce cross-AZ latency and data transfer costs, and build AZ-aware resilience patterns.

## All the numbers: Amazon Prime Day 2026 powered by AWS

DevFeed: [All the numbers: Amazon Prime Day 2026 powered by AWS](<https://devfeed.tech/articles/all-the-numbers-amazon-prime-day-2026-powered-by-aws-65870.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/all-the-numbers-amazon-prime-day-2026-powered-by-aws/>)

Author: Channy Yun (윤석찬)

Published: 2026-10-06T16:09:36Z

Content type: article

Language: en

Sources: [AWS News Blog](<https://devfeed.tech/sources/aws-news-blog.md>)

Topics: [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [AWS Fault Injection Service (FIS)](<https://devfeed.tech/topics/aws-fault-injection-service-fis.md>), [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudfront](<https://devfeed.tech/tags/amazon-cloudfront.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-guardduty](<https://devfeed.tech/tags/amazon-guardduty.md>), [amazon-prime-day](<https://devfeed.tech/tags/amazon-prime-day.md>), [amazon-prime-day-2026](<https://devfeed.tech/tags/amazon-prime-day-2026.md>), [amazon-simple-email-service-ses](<https://devfeed.tech/tags/amazon-simple-email-service-ses.md>), [amazon-simple-queue-service-sqs](<https://devfeed.tech/tags/amazon-simple-queue-service-sqs.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [aws-fault-injection-service-fis](<https://devfeed.tech/tags/aws-fault-injection-service-fis.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-support](<https://devfeed.tech/tags/aws-support.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [graviton](<https://devfeed.tech/tags/graviton.md>), [kinesis-data-streams](<https://devfeed.tech/tags/kinesis-data-streams.md>)

### AI overview

The article reports AWS infrastructure metrics from Amazon Prime Day 2026, including compute, storage, database, messaging, monitoring, and security workloads. It highlights the scale of service activity and recommends AWS Countdown Premium for teams preparing for major traffic events, launches, and migrations.

### Source excerpt

Amazon Prime Day 2026 was exclusively for Prime members and ran June 23-26, 2026 with millions of deals across more than 35 categories. As part of our annual tradition of sharing how AWS powered Prime Day (2016, 2017, 2019, 2020, 2021, 2022, 2023, 2024, and 2025), I want to share the services and chart-topping metrics [...]

## How Intuit and AWS systematically improved resiliency on ElastiCache using AWS Fault Injection Service

DevFeed: [How Intuit and AWS systematically improved resiliency on ElastiCache using AWS Fault Injection Service](<https://devfeed.tech/articles/how-intuit-and-aws-systematically-improved-resiliency-on-elasticache-using-aws-fault-injection-service-42097.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-intuit-and-aws-systematically-improved-resiliency-on-elasticache-using-aws-fault-injection-service/>)

Author: Ryan Sheahan

Published: 2026-09-17T15:59:44Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [AWS Fault Injection Service (FIS)](<https://devfeed.tech/topics/aws-fault-injection-service-fis.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Availability](<https://devfeed.tech/topics/availability.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fault-injection-service-fis](<https://devfeed.tech/tags/aws-fault-injection-service-fis.md>), [caching](<https://devfeed.tech/tags/caching.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [customer-experience](<https://devfeed.tech/tags/customer-experience.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [resiliency](<https://devfeed.tech/tags/resiliency.md>)

### AI overview

AWS and Intuit describe validating Amazon ElastiCache resilience during an Availability Zone impairment with AWS Fault Injection Service. The post covers experiment setup, measurements, configuration issues, and reported recovery improvements under production-level load.

### Source excerpt

Learn how Intuit and AWS validated Amazon ElastiCache resilience under a real Availability Zone impairment using AWS Fault Injection Service, cutting recovery from over 50 minutes to under 2 minutes with no manual intervention and reducing customer impact to effectively zero.

## Player profiles to leaderboards: Choosing the right AWS database, Part 2

DevFeed: [Player profiles to leaderboards: Choosing the right AWS database, Part 2](<https://devfeed.tech/articles/player-profiles-to-leaderboards-choosing-the-right-aws-database-part-2-50138.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/gametech/player-profiles-to-leaderboards-choosing-the-right-aws-database-part-2/>)

Author: Alberto Lopez Pazos

Published: 2026-06-09T21:54:16Z

Content type: tutorial

Language: en

Sources: [AWS for Games Blog](<https://devfeed.tech/sources/aws-for-games-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Database](<https://devfeed.tech/topics/database.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [real-time](<https://devfeed.tech/topics/real-time.md>)

Tags: [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-memorydb](<https://devfeed.tech/tags/amazon-memorydb.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [amazon-redshift](<https://devfeed.tech/tags/amazon-redshift.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [amazon-timestream](<https://devfeed.tech/tags/amazon-timestream.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-well-architected-framework](<https://devfeed.tech/tags/aws-well-architected-framework.md>), [backend](<https://devfeed.tech/tags/backend.md>), [database](<https://devfeed.tech/tags/database.md>), [games](<https://devfeed.tech/tags/games.md>), [gaming](<https://devfeed.tech/tags/gaming.md>), [industries](<https://devfeed.tech/tags/industries.md>), [leaderboards](<https://devfeed.tech/tags/leaderboards.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

This tutorial compares AWS database services for real-time gaming workloads including leaderboards, matchmaking, chat, social graphs, and game analytics. It explains how Redis-compatible services support rank lookups and how DynamoDB can serve simpler or segmented leaderboard use cases.

### Source excerpt

In this post, we continue with the real-time, social, and analytical workloads: leaderboards, matchmaking, chat, social graph, and game analytics. Each of these has distinct access patterns that require different database choices. This post assumes familiarity with AWS database services and basic game backend architecture.

## Optimizing Stripe API performance in Lambda with caching strategies

DevFeed: [Optimizing Stripe API performance in Lambda with caching strategies](<https://devfeed.tech/articles/optimizing-stripe-api-performance-in-lambda-with-caching-strategies-81809.md>)

Original publisher: [Read original article](<https://stripe.dev/blog/optimizing-stripe-api-performance-lambda-caching-elasticache-dynamodb>)

Author: James Beswick

Published: 2025-04-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Stripe Dot Dev Blog](<https://devfeed.tech/sources/stripe-dot-dev-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Redis](<https://devfeed.tech/topics/redis.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [caching](<https://devfeed.tech/tags/caching.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [costs](<https://devfeed.tech/tags/costs.md>), [dynamodb](<https://devfeed.tech/tags/dynamodb.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [scalability](<https://devfeed.tech/tags/scalability.md>)

### AI overview

The article outlines caching strategies for improving Stripe API performance in AWS Lambda, using Amazon ElastiCache and DynamoDB to manage rate limits, lower latency and costs, and maintain consistency and scalability in high-volume applications.

### Source excerpt

Discover advanced caching strategies to optimize Stripe API performance in AWS Lambda using Amazon ElastiCache and DynamoDB. Learn how to manage API rate limits, reduce latency, and minimize costs while ensuring data consistency and scalability in high-volume applications.

## Varnish to Redis Migration

DevFeed: [Varnish to Redis Migration](<https://devfeed.tech/articles/varnish-to-redis-migration-26226.md>)

Original publisher: [Read original article](<https://medium.com/groupon-eng/varnish-to-redis-migration-887ad6d805d2?source=rss----5c13a88f9872---4>)

Author: Ravikumar

Published: 2022-03-22T15:39:20Z

Content type: article

Language: en

Sources: [Groupon Engineering](<https://devfeed.tech/sources/groupon-engineering-medium.md>)

Topics: [Redis](<https://devfeed.tech/topics/redis.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [cache-invalidation](<https://devfeed.tech/topics/cache-invalidation.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [cloud-migration](<https://devfeed.tech/topics/cloud-migration.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>)

Tags: [aws-eks](<https://devfeed.tech/tags/aws-eks.md>), [cache-invalidation](<https://devfeed.tech/tags/cache-invalidation.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cloud-migration](<https://devfeed.tech/tags/cloud-migration.md>), [distributed-transaction](<https://devfeed.tech/tags/distributed-transaction.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [migration](<https://devfeed.tech/tags/migration.md>), [redis](<https://devfeed.tech/tags/redis.md>), [varnish](<https://devfeed.tech/tags/varnish.md>)

### AI overview

Groupon chose Redis with client-side caching for its place read service as it moved workloads to AWS EKS. The service handles over a billion calls daily, peaking at about 2 million requests per minute; four 40 GB Varnish servers deliver a 95% hit rate. Randomized 30-60 minute TTLs reduce simultaneous expirations, but expire still-valid keys and lower hit rate. The team considered Kubernetes-hosted Varnish, Guava with Kafka invalidation, and Redis. Varnish offered the best performance and request coalescing, but duplicates data across pods and needs frequent cache warming. Guava offers key-level invalidation, but raises dual-write consistency concerns; Groupon planned a transactional outbox job every 30 minutes to publish invalidations, while heap limits, duplication, and scalability remained concerns. Redis 6 client-side caching suited a workload where the top 1% of keys receive over 90% of traffic. The excerpt says this nearly matched Varnish latency; managed ElastiCache and horizontal scaling also supported the choice.

### Source excerpt

At Groupon, we are in the process of migrating our app workloads to AWS EKS. As part of the migration, we are also in the process of re-architecting our services to make them cloud & Kubernetes optimised. In this article, we will focus on the impact of cloud migration on Varnish caching at Groupon. For the uninitiated, Varnish is a high-performance reverse caching proxy. For simplicity, you can think of it as a general proxy such as HAProxy or Nginx with caching support so that it doesn't have to go to a backend service every time it receives a request. Internally, Varnish cache uses pthreads heavily(to the tune of 1000s) to serve the requests. In contrast, Redis is single-threaded. Varnish at Groupon & Place Read Service We have been using Varnish for many of our high-traffic services. These read-heavy services get traffic to the tune of millions of RPM. One such service is our place read service which is called on each & every deal page visit; it will be the focus of this article. Place read service stores all the locations a deal can be redeemed. Ex: Redemption location details of the deal https://www.groupon.com/deals/parent-big-littles-3 is highlighted below. Traffic pattern of place read service The service is called more than a billion times a day with peak traffic of ~2 million requests per minute. Current architecture (simplified) The traffic is served by a cluster of 4 Varnish servers (40GB RAM). The current Varnish hit rate is 95%. This is admittedly a low hit rate for a read-heavy service, the main reason being our TTL-based cache invalidation logic. Varnish cache invalidation We are using TTL-based cache invalidation. This usually leads to a problem where Varnish starts bombarding the backend service when most of the keys expire at the same time. Request coalescing is not very helpful when the unique keys count is in millions (which is the case with our service). As a workaround, we use randomised TTLs (between 30 to 60 mins) so that all the keys don't

## GitHub reports service interruptions tied to database tier scaling challenges

DevFeed: [GitHub reports service interruptions tied to database tier scaling challenges](<https://devfeed.tech/articles/february-service-disruptions-68910.md>)

Original publisher: [Read original article](<https://github.blog/news-insights/company-news/february-service-disruptions/>)

Author: Keith Ballinger

Published: 2020-02-28T19:33:37Z

Content type: news

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>)

Tags: [company-news](<https://devfeed.tech/tags/company-news.md>), [github](<https://devfeed.tech/tags/github.md>), [news-insights](<https://devfeed.tech/tags/news-insights.md>), [partitioning](<https://devfeed.tech/tags/partitioning.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [service-interruptions](<https://devfeed.tech/tags/service-interruptions.md>)

### AI overview

GitHub says several distinct service interruptions exposed challenges scaling its database tier. Increased load on its largest database cluster contributed to degradations across multiple services. The company plans a more detailed technical report and says data partitioning initiatives are underway.

### Source excerpt

Recently, we've had multiple service interruptions on GitHub.com. We know how important reliability of our service is for your projects and teams. We take this responsibility very seriously and apologize...