This chapter covers ElastiCache Reserved Nodes, a pricing model that offers significant discounts in exchange for a commitment to a specific node configuration for a 1- or 3-year term. For the SAA-C03 exam, understanding Reserved Nodes is critical for cost optimization (Domain 4) and for designing cost-effective caching architectures. While not a frequent standalone topic, it appears in roughly 5-10% of cost-related questions, often as a distractor or as a correct answer for steady-state workloads.
Jump to a section
Imagine you regularly order books from an online bookstore. You can either pay the full price for each book individually (On-Demand), or you can buy an Amazon Prime subscription that gives you a significant discount on every book you buy, but you commit to paying the annual fee upfront. The Prime subscription is like a Reserved Node: you pay a fixed amount upfront (or partially upfront) for a 1-year or 3-year term, and in return, you get a lower hourly rate for each node you run. If you stop ordering books, the Prime subscription cost is still sunk—you don't get a refund. Similarly, if you delete your ElastiCache cluster, you still pay for the reserved capacity. However, if your book orders exceed a certain volume, the savings from the discounted prices more than offset the subscription cost. ElastiCache Reserved Nodes work the same way: you commit to a specific node type and region, pay an upfront fee (or not), and receive a discounted hourly rate for the duration of the term. If your usage is steady, you save up to 55% compared to On-Demand. But if your workload is unpredictable, you risk paying for idle capacity.
What Are ElastiCache Reserved Nodes?
ElastiCache Reserved Nodes are a billing and capacity reservation mechanism that allows you to reserve cache nodes (for Memcached or Redis) in a specific AWS region for a 1- or 3-year term. In exchange, you receive a significant discount on the hourly usage rate compared to On-Demand pricing. Reserved Nodes are not a separate instance type; they are a pricing construct applied to existing node types (e.g., cache.r6g.large, cache.m5.xlarge). When you purchase a Reserved Node, AWS reserves capacity for that node type in the specified region (and optionally Availability Zone), ensuring that the node will be available when you need it. However, the reservation is not tied to a specific cluster or instance ID; it is applied at the account level. AWS automatically applies the discounted rate to any running node that matches the attributes (node type, region, offering class) of your reservation.
Why Reserved Nodes Exist
Reserved Nodes exist to provide cost savings for predictable, steady-state workloads. AWS data centers have fixed costs, and by committing to long-term usage, you allow AWS to better plan capacity. In return, AWS passes on savings to you. For the SAA-C03 exam, you need to know that Reserved Nodes can reduce costs by up to 55% compared to On-Demand, depending on the term and upfront payment option. This is a key cost optimization strategy for production caching layers that run 24/7.
How Reserved Nodes Work Internally
When you purchase a Reserved Node, you specify: - Region: The AWS region where the reservation applies. - Node Type: The specific instance family and size (e.g., cache.r6g.large). - Term: 1 year or 3 years. - Payment Option: No Upfront, Partial Upfront, or All Upfront. - Offering Class: Standard (lower discount) or Convertible (higher flexibility, lower discount). - Availability Zone: Optional; if specified, the reservation is zonal (capacity reserved in that AZ). If not, it is regional (capacity reserved in the region but not tied to a specific AZ).
After purchase, the Reserved Node appears in your account as a recurring line item on the billing dashboard. It does not launch any actual instance; it is purely a billing construct. When you launch an ElastiCache node that matches the attributes, AWS automatically applies the discounted rate. If you run multiple matching nodes, the discount is applied to the first nodes that match, up to the number of reserved nodes you purchased. Any additional nodes are billed at On-Demand rates.
Key Values, Defaults, and Timers
- Term: 1 year (12 months) or 3 years (36 months). - Payment Options: - No Upfront: No upfront payment; you pay a discounted hourly rate for the entire term. - Partial Upfront: Pay a portion upfront (typically 50-60% of the total cost), and receive a higher discount on the hourly rate. - All Upfront: Pay the entire cost upfront; receive the highest discount (up to 55%). - Discount Ranges: - 1-year term: 20-40% discount (varies by node type and payment option). - 3-year term: 40-55% discount. - Offering Classes: - Standard: Lower discount, but the reservation is not modifiable (except for cancellation within the first 7 days). - Convertible: Higher discount? No, actually Convertible offers lower discount (typically 5-10% less than Standard) but allows you to change the node type, region, or other attributes during the term. This is a common exam trap: Convertible offers more flexibility but less savings. - Modification: Standard Reserved Nodes cannot be modified after purchase. Convertible Reserved Nodes can be exchanged for another Convertible Reserved Node with different attributes, as long as the new reservation has equal or greater value. - Cancellation: Reserved Nodes cannot be cancelled after the first 7 days (the grace period). If you cancel within 7 days, you receive a full refund. After that, you are billed for the full term. - Regional vs. Zonal: If you specify an Availability Zone, the reservation reserves capacity in that AZ. If you do not, the reservation is regional and does not guarantee capacity in any specific AZ, but still provides the discount.
Configuration and Verification
You purchase Reserved Nodes via the AWS Management Console, AWS CLI, or API. The CLI command is:
aws elasticache purchase-reserved-cache-nodes-offering \
--reserved-cache-nodes-offering-id <offering-id> \
--cache-node-count <count>To view your Reserved Nodes:
aws elasticache describe-reserved-cache-nodesThis command returns details such as the Reserved Node ID, offering type, state (active or retired), and the number of nodes reserved.
Interaction with Related Technologies
Reserved Nodes interact with: - Cost Explorer: You can use Cost Explorer to analyze your usage and recommend Reserved Node purchases. - AWS Budgets: You can set budgets to alert you when your Reserved Node coverage is low. - Auto Scaling: If you use Auto Scaling for ElastiCache (e.g., with Redis Cluster Mode), Reserved Nodes can reduce costs for the baseline cluster size. However, scaling out adds On-Demand nodes. - Savings Plans: AWS also offers Compute Savings Plans, which apply to ElastiCache and provide similar discounts without requiring a specific node type commitment. The exam may test the difference: Reserved Nodes are specific to a node type and region, while Savings Plans are more flexible.
Identify workload patterns
Analyze your ElastiCache usage over the past 30 days using Cost Explorer or Trusted Advisor. Determine if the workload is steady-state (e.g., a production Redis cluster running 24/7) or variable (e.g., a development environment that is turned off at night). For steady-state workloads, Reserved Nodes provide the best savings. For variable workloads, On-Demand or Spot Instances (if available) may be more cost-effective. Note the node type, region, and average number of nodes running concurrently.
Choose term and payment option
Select a 1-year or 3-year term. A 3-year term offers higher discounts but requires a longer commitment. Then choose a payment option: No Upfront, Partial Upfront, or All Upfront. All Upfront provides the highest discount but requires a large initial payment. Partial Upfront balances upfront cost and savings. No Upfront has no upfront cost but the lowest discount. For the exam, remember that All Upfront is best for maximum savings, while No Upfront is best when you want to avoid upfront costs.
Select offering class
Choose between Standard and Convertible. Standard offers higher discounts but cannot be modified. Convertible allows you to exchange the reservation for a different node type or region during the term, but with a lower discount. If you anticipate changes in your workload (e.g., upgrading to a newer instance family), choose Convertible. Otherwise, Standard is more cost-effective.
Purchase Reserved Nodes
Use the AWS Management Console, CLI, or API to purchase the Reserved Nodes. Specify the node type, region, term, payment option, and count. If you want capacity reservation in a specific Availability Zone, specify it. After purchase, the Reserved Nodes appear in your account immediately. AWS automatically applies the discounted rate to any matching running nodes. You can verify the purchase using the `describe-reserved-cache-nodes` CLI command.
Monitor and optimize coverage
After purchase, monitor your Reserved Node utilization using Cost Explorer or the AWS Billing console. Ensure that you are using at least the number of nodes you reserved. If you have unused Reserved Nodes, consider modifying your cluster to use the reserved node type (if possible) or exchange Convertible reservations. Also, set up AWS Budgets to alert you if your coverage drops below a threshold (e.g., 80%). For the exam, know that you can sell unused Standard Reserved Nodes on the Reserved Instance Marketplace, but this is not available for ElastiCache Reserved Nodes (only for EC2).
Enterprise Scenario 1: Production Redis Cache for E-Commerce Platform
A large e-commerce company runs a Redis cluster with 10 cache.r6g.xlarge nodes in us-east-1 to cache product catalog and session data. The cluster runs 24/7 with minimal scaling. The cloud architect purchases 10 Standard Reserved Nodes with a 3-year term and All Upfront payment. This reduces the hourly cost from $0.375 per node (On-Demand) to $0.169 per node, saving approximately 55%. The total upfront cost is around $44,000, but over three years, the savings exceed $60,000. The architect sets up a budget to monitor coverage and ensures that any new nodes added for scaling are On-Demand. When the cluster needs to be upgraded to a newer instance type (e.g., cache.r7g), the architect must wait until the term ends or use Convertible reservations if they had chosen that option. Since they chose Standard, they cannot modify the reservation, so they plan the upgrade for the end of the term.
Enterprise Scenario 2: Multi-Region Disaster Recovery Cache
A financial services company operates a Redis cache in eu-west-1 (primary) and a smaller cluster in eu-central-1 (DR). The DR cluster runs only 2 nodes and is used only during failover tests, so it is not a steady-state workload. The architect decides to use On-Demand for the DR cluster because Reserved Nodes would be wasted. However, they purchase Reserved Nodes for the primary cluster. During a failover test, the DR cluster is scaled up to 10 nodes temporarily, all billed at On-Demand rates. This is acceptable because the test lasts only a few hours. The architect also considers using Savings Plans (Compute Savings Plan) to cover both EC2 and ElastiCache usage, but since the DR usage is minimal, On-Demand is more cost-effective.
Common Pitfalls
Over-reserving: Purchasing more Reserved Nodes than needed leads to wasted spend. Always base the purchase on actual usage history.
Ignoring Convertible options: If you expect to change node types, choosing Standard locks you in. Convertible is worth the slightly lower discount.
Not monitoring coverage: Without monitoring, you might launch additional nodes that are billed at On-Demand rates, reducing overall savings.
SAA-C03 Exam Focus
This topic falls under Domain 4: Cost-Optimized Architectures (Objective 4.4: Identify cost-effective storage and database options). The exam tests your ability to choose between pricing models (On-Demand, Reserved, Spot) for ElastiCache. Key areas: - Reserved Nodes vs. On-Demand: Know the maximum discount (55%) and the term lengths (1 and 3 years). - Payment Options: Understand the trade-offs: All Upfront = highest discount, No Upfront = lowest discount, Partial Upfront = middle. - Standard vs. Convertible: Standard = higher discount, no modifications; Convertible = lower discount, modifiable. - Regional vs. Zonal: Zonal reserves capacity in a specific AZ; regional does not guarantee capacity but still provides discount. - Savings Plans: Know that Compute Savings Plans also apply to ElastiCache and offer more flexibility than Reserved Nodes.
Common Wrong Answers
"Reserved Nodes provide capacity reservation in a specific Availability Zone by default." – Wrong. Regional reservations do not reserve capacity in any specific AZ. Only zonal reservations do. This is a common trap.
"Convertible Reserved Nodes offer higher discounts than Standard." – Wrong. Standard offers higher discounts. Convertible trades discount for flexibility.
"You can cancel a Reserved Node at any time." – Wrong. You can only cancel within the first 7 days. After that, you are billed for the full term.
"Reserved Nodes are tied to a specific cluster." – Wrong. They are applied at the account level to any matching node.
Specific Numbers and Terms
Maximum discount: 55% (3-year, All Upfront).
Term lengths: 1 year, 3 years.
Payment options: No Upfront, Partial Upfront, All Upfront.
Offering classes: Standard, Convertible.
Grace period: 7 days for cancellation.
Edge Cases
If you purchase a Convertible Reserved Node and then exchange it for a different node type, the new reservation must have equal or greater value. If the new node type is more expensive, you pay the difference; if less expensive, you receive no refund.
Reserved Nodes cannot be shared across accounts via Consolidated Billing unless the payer account purchases them and the linked accounts use matching nodes. The discount applies to the entire consolidated bill.
How to Eliminate Wrong Answers
If a question asks for the most cost-effective option for a steady-state workload, choose Reserved Nodes (especially All Upfront, 3-year).
If the question mentions flexibility (e.g., "the company may change instance types next year"), choose Convertible Reserved Nodes or Compute Savings Plans.
If the question involves a temporary workload, choose On-Demand or Spot (if available).
Reserved Nodes offer up to 55% discount for 3-year All Upfront commitment.
Standard Reserved Nodes have higher discount but cannot be modified; Convertible offers flexibility at a lower discount.
Reserved Nodes are applied at the account level, not tied to a specific cluster.
You can cancel Reserved Nodes only within the first 7 days; after that, full term is billed.
Regional reservations do not guarantee capacity in a specific AZ; zonal reservations do.
Compute Savings Plans provide more flexibility than Reserved Nodes but may offer lower discounts for ElastiCache.
For steady-state workloads, Reserved Nodes are the most cost-effective option.
These come up on the exam all the time. Here's how to tell them apart.
Standard Reserved Nodes
Higher discount (up to 55%)
Cannot be modified after purchase
Best for stable, predictable workloads
No flexibility to change node type or region
Cannot be exchanged; must wait until term ends
Convertible Reserved Nodes
Lower discount (typically 5-10% less than Standard)
Can be exchanged for another Convertible reservation with equal or greater value
Best for workloads that may change instance family or region
Flexibility to modify attributes during the term
Can exchange multiple times, but each exchange must meet value requirements
Reserved Nodes
Specific to ElastiCache node type and region
Up to 55% discount
Requires 1- or 3-year commitment
No flexibility if you change to a different service (e.g., EC2)
Capacity reservation available (zonal)
Compute Savings Plans
Applies to EC2, Fargate, Lambda, and ElastiCache
Up to 66% discount (for EC2) but typically lower for ElastiCache
Requires 1- or 3-year commitment
Flexible across services and instance families (within compute)
No capacity reservation; discount only
Mistake
Reserved Nodes are physical instances that you must launch.
Correct
Reserved Nodes are a billing discount, not actual instances. You still need to launch ElastiCache clusters separately. The reservation is applied automatically to matching running nodes.
Mistake
Reserved Nodes can be cancelled at any time for a full refund.
Correct
You can cancel only within the first 7 days of purchase. After that, you are billed for the entire term, even if you delete the cluster.
Mistake
Convertible Reserved Nodes offer the highest discount.
Correct
Standard Reserved Nodes offer higher discounts (up to 55%). Convertible offers lower discounts (typically 5-10% less) in exchange for the ability to modify the reservation.
Mistake
Regional Reserved Nodes guarantee capacity in every Availability Zone.
Correct
Regional reservations do not guarantee capacity in any specific AZ. Only zonal reservations (where you specify an AZ) reserve capacity in that zone.
Mistake
Reserved Nodes are specific to a single ElastiCache cluster.
Correct
Reserved Nodes are applied at the account level. Any cluster running matching node types in the same region will receive the discounted rate, up to the number of reserved nodes purchased.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Yes, Reserved Nodes are available for both Memcached and Redis. The node type you reserve must match the engine you intend to use. For example, a cache.r6g.large Reserved Node can be used for either Memcached or Redis, as long as the node type is supported by the engine. The discount applies to the hourly rate of the node, regardless of the engine.
You still pay for the Reserved Nodes for the entire term. The reservation is a commitment, and deleting the cluster does not cancel the reservation. You can launch a new cluster with matching node types to utilize the reservation, or you can leave it unused and continue paying. There is no way to get a refund after the 7-day grace period.
No, Standard Reserved Nodes cannot be modified. If you need flexibility, choose Convertible Reserved Nodes. With Convertible, you can exchange the reservation for another Convertible reservation with different attributes, as long as the new reservation has equal or greater value.
Reserved Nodes cover the baseline number of nodes you reserved. If you scale out, additional nodes are billed at On-Demand rates. If you scale in, you may have unused Reserved Nodes. For cost optimization, reserve only the minimum number of nodes you expect to run continuously.
Yes, when purchasing, you can specify an Availability Zone. This creates a zonal reservation that reserves capacity in that AZ. If you do not specify an AZ, the reservation is regional and does not guarantee capacity in any specific AZ, but still provides the discount.
Reserved Nodes are available for most current generation node types (e.g., r6g, r5, m5, etc.). Older generation types may not be available. Check the AWS documentation for the latest list. Also, some node types may only be available in certain regions.
If you use AWS Organizations with Consolidated Billing, Reserved Nodes purchased by the payer account can be shared with linked accounts. The discount is applied to any matching nodes across all accounts in the organization. However, capacity reservation (zonal) is not shared; it applies only to the purchasing account.
You've just covered ElastiCache Reserved Nodes — now see how well it sticks with free SAA-C03 practice questions. Full explanations included, no account needed.
Done with this chapter?