//
Busque em todas as páginas da documentação
7 pages in this section.
Where a managed in-memory cache fits in a request path, what the AWS SDK owns versus what a Redis client owns, and why ElastiCache sits between your app and its database.
Provision a small Redis/Valkey replication group with the AWS SDK, discover its endpoint, and connect from application code with a Redis client - in both boto3 and AWS SDK v3.
Choose between Redis/Valkey and Memcached for ElastiCache - data structures, replication, and failover versus multi-threaded simplicity - and provision each with the right SDK call.
Provision ElastiCache Serverless with CreateServerlessCache - no node sizing, pay for stored data plus ECPUs - discover its single endpoint, and connect with a TLS Redis client.
A checklist for building on ElastiCache from the SDK - engine and topology choice, endpoint handling, eviction and TTL, failover testing, cache-stampede prevention, security, and cost.