AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Moves T2 node types to Previous Generation section

Service: AmazonElastiCache · 2026-09-27 · Documentation low

File: AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.md

Summary

Restructures the ElastiCache supported node types page: renames 'Burstable Performance Instances' to 'Burstable Performance Nodes', adds a 'Previous Generation' section, and relocates cache.t2.micro/small/medium specs (and the T2 reserved-node deprecation notice) into it. No security content is added or removed.

Security assessment

The diff only reorganizes instance-type documentation (T2 moved to Previous Generation, headings renamed, T2 rows relocated). It contains no authentication, encryption, credential, or vulnerability content, so it is a non-security editorial change.

Evidence

+Previous generation node types are no longer available for new cluster creation. Existing clusters using these node types continue to function, but we recommend upgrading to current generation node types for better performance and cost efficiency.

Diff

diff --git a/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.md b/AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.md
index e74896797..f63d996a2 100644
--- a//AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.md
+++ b//AmazonElastiCache/latest/dg/CacheNodes.SupportedTypes.md
@@ -7 +7 @@
-Current Generation (Memcached)Current Generation (Valkey)Current Generation (Redis OSS)Burstable Performance InstancesSupported node types by AWS RegionRelated Information
+Current Generation (Memcached)Current Generation (Valkey)Current Generation (Redis OSS)Burstable Performance NodesPrevious GenerationSupported node types by AWS RegionRelated Information
@@ -19,2 +18,0 @@ For information on which node size to use, see [Choosing your node size](./Cache
-We are transitioning T2 instances to previous generation status. You will no longer be able to create new ElastiCache clusters using T2 instances or purchase new T2 reserved nodes. There is no impact to your existing T2 clusters or reservations. We recommend upgrading to T4g instances for better performance and cost efficiency. 
-
@@ -31 +29,3 @@ Instance types with burstable network performance use a network I/O credit mecha
-  * Burstable Performance Instances
+  * Burstable Performance Nodes
+
+  * Previous Generation
@@ -84,3 +83,0 @@ cache.t3.medium | 1.5.16 | 0.256 | 5.0 | 3.09
-cache.t2.micro | 1.5.16 | 0.064 | 1.024 | 0.555  
-cache.t2.small | 1.5.16 | 0.128 | 1.024 | 1.55  
-cache.t2.medium | 1.5.16 | 0.256 | 1.024 | 3.22  
@@ -189,3 +185,0 @@ cache.t3.medium | 7.2 | No | No | No | 0.256 | 5.0 | 3.09
-cache.t2.micro | 7.2 | No | No | No | 0.064 | 1.024 | 0.555  
-cache.t2.small | 7.2 | No | No | No | 0.128 | 1.024 | 1.55  
-cache.t2.medium | 7.2 | No | No | No | 0.256 | 1.024 | 3.22  
@@ -298,3 +291,0 @@ cache.t3.medium | 4.0.10 | N | N | N | 0.256 | 5.0 | 3.09
-cache.t2.micro | 4.0.10 | N | N | N | 0.064 | 1.024 | 0.555  
-cache.t2.small | 4.0.10 | N | N | N | 0.128 | 1.024 | 1.55  
-cache.t2.medium | 4.0.10 | N | N | N | 0.256 | 1.024 | 3.22  
@@ -356 +347 @@ cache.c7gn.16xlarge | 6.2 | Yes | Yes | Yes | 200 | N/A | 105.81
-## Burstable Performance Instances
+## Burstable Performance Nodes
@@ -358 +349 @@ cache.c7gn.16xlarge | 6.2 | Yes | Yes | Yes | 200 | N/A | 105.81
-You can launch general-purpose burstable T4g, T3-Standard and T2-Standard cache nodes in Amazon ElastiCache. These nodes provide a baseline level of CPU performance with the ability to burst CPU usage at any time until the accrued credits are exhausted. A _CPU credit_ provides the performance of a full CPU core for one minute.
+You can launch general-purpose burstable T4g and T3-Standard cache nodes in Amazon ElastiCache. These nodes provide a baseline level of CPU performance with the ability to burst CPU usage at any time until the accrued credits are exhausted. A _CPU credit_ provides the performance of a full CPU core for one minute.
@@ -360 +351 @@ You can launch general-purpose burstable T4g, T3-Standard and T2-Standard cache
-Amazon ElastiCache's T4g, T3 and T2 nodes are configured as standard and suited for workloads with an average CPU utilization that is consistently below the baseline performance of the instance. To burst above the baseline, the node spends credits that it has accrued in its CPU credit balance. If the node is running low on accrued credits, performance is gradually lowered to the baseline performance level. This gradual lowering ensures the node doesn't experience a sharp performance drop-off when its accrued CPU credit balance is depleted. For more information, see [CPU Credits and Baseline Performance for Burstable Performance Instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html) in the _Amazon EC2 User Guide _.__
+Amazon ElastiCache's T4g and T3 nodes are configured as standard and suited for workloads with an average CPU utilization that is consistently below the baseline performance of the instance. To burst above the baseline, the node spends credits that it has accrued in its CPU credit balance. If the node is running low on accrued credits, performance is gradually lowered to the baseline performance level. This gradual lowering ensures the node doesn't experience a sharp performance drop-off when its accrued CPU credit balance is depleted. For more information, see [CPU Credits and Baseline Performance for Burstable Performance Instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html) in the _Amazon EC2 User Guide _.__
@@ -365,0 +357 @@ Node type | CPU credits earned per hour |  Maximum earned credits that can be ac
+**Current generation**  
@@ -371,0 +364 @@ t3.medium | `24` | 576 | 2 | 20% | Up to 5 Gigabit | 3.09
+**Previous generation**  
@@ -382,4 +374,0 @@ The following CPU credit metrics are available for T3 and T4g burstable performa
-###### Note
-
-These metrics are not available for T2 burstable performance instances.
-
@@ -399 +388,4 @@ In addition, be aware of these details:
-  * Redis OSS append-only files (AOF) aren't supported for T2 instances. Redis OSS configuration variables `appendonly` and `appendfsync` aren't supported.
+  * Redis OSS configuration variables `appendonly` and `appendfsync` aren't supported.
+
+
+
@@ -400,0 +393 @@ In addition, be aware of these details:
+## Previous Generation
@@ -401,0 +395 @@ In addition, be aware of these details:
+Previous generation node types are no longer available for new cluster creation. Existing clusters using these node types continue to function, but we recommend upgrading to current generation node types for better performance and cost efficiency.
@@ -402,0 +397,5 @@ In addition, be aware of these details:
+Instance type | Baseline bandwidth (Gbps) | Burst bandwidth (Gbps) | Memory (GiB)  
+---|---|---|---  
+cache.t2.micro | 0.064 | 1.024 | 0.555  
+cache.t2.small | 0.128 | 1.024 | 1.55  
+cache.t2.medium | 0.256 | 1.024 | 3.22