Missing i3en.metal-2tb about ec2-timeline HOT 3 CLOSED

🤔 indeed it's not mentioned in the product page but found the instance on the EC2 price list :

"5Z9MHDVSE3MBVMSJ" : {
      "sku" : "5Z9MHDVSE3MBVMSJ",
      "productFamily" : "Compute Instance (bare metal)",
      "attributes" : {
        "servicecode" : "AmazonEC2",
        "location" : "US West (Los Angeles)",
        "locationType" : "AWS Region",
        "instanceType" : "i3en.metal-2tb",
        "currentGeneration" : "Yes",
        "instanceFamily" : "Storage optimized",
        "vcpu" : "96",
        "physicalProcessor" : "Intel Xeon Platinum 8175 (Skylake)",
        "clockSpeed" : "3.1 GHz",
        "memory" : "768 GiB",
        "storage" : "32 x 2000 NVMe SSD",
        "networkPerformance" : "100 Gigabit",
        "processorArchitecture" : "64-bit",
        "tenancy" : "Host",
        "operatingSystem" : "Windows",
        "licenseModel" : "No License required",
        "usagetype" : "LAX1-HostBoxUsage:i3en.metal-2tb",
        "operation" : "RunInstances:0006",
        "availabilityzone" : "NA",
        "capacitystatus" : "Used",
        "classicnetworkingsupport" : "false",
        "dedicatedEbsThroughput" : "19000 Mbps",
        "ecu" : "NA",
        "enhancedNetworkingSupported" : "Yes",
        "intelAvxAvailable" : "Yes",
        "intelAvx2Available" : "Yes",
        "intelTurboAvailable" : "Yes",
        "marketoption" : "OnDemand",
        "normalizationSizeFactor" : "192",
        "preInstalledSw" : "SQL Std",
        "processorFeatures" : "Intel AVX; Intel AVX2; Intel AVX512; Intel Turbo",
        "servicename" : "Amazon Elastic Compute Cloud",
        "vpcnetworkingsupport" : "true"
      }
    }

One attributes stands out: usagetype
It refers to LAX1-HostBoxUsage:i3en.metal-2tb .. so I did some research and LAX refers to a Local Zone

It's listed in the pricing list under 10 different SKU's, all reserved/dedicated to the LAX Local Zone :

• 5Z9MHDVSE3MBVMSJ
• Q9SZ9UU39PUHDQE2
• T2ZUQHUEBNB2SXUT
• ACRK5JNGTBYNBRQ6
• HWY35KA9WABHFC9P
• DFX9FXY74Y876Q9W
• CPVCVXEZZRJZXTYY
• 3T22XA5UN2G8RYTP
• 8GS6F4523PDYV5C8
• YVNUCPJQY7Y3VQUY

Since this type is only available to the LAX Local Zone and not available for general commercial purposes, I would leave out the instance type from the timeline.

Not sure where you saw the relationship to "China (Ningxia)" though 🤔

from ec2-timeline.

I ran my query while my system was processing and I should have waited :P This instance is actually in two regions, ["China (Ningxia)", "US West (Los Angeles)"] with the following SKU's

• B9HRMZXHBG6W3RJG
• HWY35KA9WABHFC9P
• CHY9BEA9W62EAGD7
• CPVCVXEZZRJZXTYY
• 85T6NXJN8NE8HDEB
• 8GS6F4523PDYV5C8
• DFX9FXY74Y876Q9W
• 9BEVJ353MGAXVXHG
• NQ577N38669M4KYP
• Q9SZ9UU39PUHDQE2
• T2ZUQHUEBNB2SXUT
• EC43UJADPNBS9U2X
• X6BFY8699KXR2QKV
• YVNUCPJQY7Y3VQUY
• Z89S3TCP3K2URUSN
• ACRK5JNGTBYNBRQ6
• 3T22XA5UN2G8RYTP
• 5Z9MHDVSE3MBVMSJ
• 64784A973S9XDMCF
• 6JYWJ45JCZ4WDY86
• 6U2PQCPD27R2SPXZ
• GACJEXYSAZS66YKH

BTW, the reason you might not see china is if you are using the "bulk API" vs. the "query API". From the bulk API launch blog post: "It is available for all public AWS regions except China (Beijing)" https://aws.amazon.com/blogs/aws/new-aws-price-list-api/. I'm crawling the query API.

There are a number of instance types that aren't available in all regions, is the goal here to only list instances available everywhere? I lean to creating the most comprehensive list :-)

from ec2-timeline.

Actually I'm not making use of the API.. all published EC2 updates are fetched from both the Blog and What's new RSS feed, as these contain references to the launch/availability dates of new instance types. As you mentioned, the query/bulk API does not, so it's less suited for building a timeline 🙂

I do have a complementary Lambda function which dumps every change to the (public) price list to a S3 bucket (2.3GB json file) which I occasionally use for cross-referencing. I suspect the json dump contains the same data as what you would get from using the bulk API.

For now I'll stick to listing instances available everywhere, but I get you might opt for the most comprehensive list of instance types if -for example- you're building an app like the EC2 Instance Selector

from ec2-timeline.