Amazon Web Services announced on September 28, 2026, that customers can now postpone the start date of an Amazon EC2 Future-dated Capacity Reservation before capacity delivery. The change requires accepting a revised quote and can increase the reservation’s commitment duration. AWS announcement
A revised quote, not just a date change
Future-dated Capacity Reservations let customers secure EC2 capacity up to 120 days in advance by specifying their capacity requirements, start date and commitment duration. With the postponement workflow, EC2 presents a quote showing the new start date and required commitment duration. After the customer reviews and accepts the quote, EC2 updates the reservation with the new start date. AWS announcement
AWS says the commitment duration “can increase, depending on when you postpone the start date.” The announcement does not specify a formula for that increase or how far customers can push back delivery. Teams should therefore evaluate the revised commitment rather than treat postponement as only a calendar change. AWS announcement
Availability and planning implications
AWS says the feature is available to all Future-dated Capacity Reservation customers. For regional availability, it directs readers to AWS Capabilities by Region rather than listing supported regions in the announcement. AWS announcement
For engineering teams, the practical trade-off is between matching capacity delivery to project readiness and accepting a potentially longer commitment. A delayed migration or application launch could make postponement useful, but the revised quote deserves more scrutiny than a scheduling adjustment.
Before accepting, compare both the new start date and the required commitment duration with the updated demand forecast. The decision should account for how long the capacity will be needed, not just when it should arrive.
See the original announcement for availability and release details.