We have an EC2 t2.xlarge
instance in eu-west-1
region, for which we wish to purchase a Reserved Instance (RI).
The EC2 reservations we had purchased previously in us-east-1
, are of type "Linux/UNIX (Amazon VPC)".
But for eu-west-1
it looks like "Linux/UNIX (Amazon VPC)" type reservations are not available; only available option is "Linux/UNIX" - confirmed by the output (removed for brevity) of the following AWS CLI command:
aws ec2 describe-reserved-instances-offerings \
--region eu-west-1 \
--offering-class standard \
--instance-tenancy default \
--offering-type "All Upfront" \
--instance-type t2.xlarge \
--product-description "Linux/UNIX (Amazon VPC)" \
--filters \
Name=scope,Values="Region" \
Name=duration,Values=31536000
So we are concerned: will purchasing a "Linux/UNIX" reservation slot, allow us to cover ("match") our existing t2.xlarge
instance?
Based on AWS documentation:
Determining Whether You Are Using the EC2-VPC or EC2-Classic Platform (from RDS docs, but offers a decent explanation of EC2-Classic
vs EC2-VPC
):
Accounts that only support the EC2-VPC platform have a default VPC
You can create a VPC on the EC2-Classic platform, but one is not created for you by default
Our AWS account has a default VPC in eu-west-1
- which leads us to believe that it is of EC2-VPC
type.
AWS CLI: aws ec2 describe-reserved-instances-offerings help
:
Instances that include (Amazon VPC) in the product platform description ... are for use with Amazon VPC.
My EC2 Reserved Instance isn't applying to my billing—why?
Your RI must exactly match a running EC2 instance’s characteristics. A running instance must match the type, Availability Zone, platform, and tenancy of your RI exactly.
So, based on the above, purchasing a RI offering with "Linux/UNIX" (non-VPC) platform (which is the only available option) may not match/cover our existing (EC2-VPC) instance in eu-west-1
.
Can anybody prove me wrong - or suggest an approach to secure a RI (or a comparable billing advantage) for our instance in eu-west-1
?
We did contact AWS Support - but only got back vague responses like "your RI must exactly match the configurations of your existing instance".