Along the lines of issue #13: The r6id family that got added this month should be classified as Memory Optimized, not Compute Optimized. (#13 got r3 and r5 already, but according to https://aws.amazon.com/ec2/instance-types/ all of the "R" category are tagged as Memory Optimized.)

This is my first comment ever on GitHub, so I apologize if the formatting or style is off.

Your EC2 time-line (which is great) shows that the C5 instance was created in December 2016, but they weren't created until November of 2017.

Release in November 2017: https://www.businesswire.com/news/home/20171106006573/en/AWS-Announces-Availability-C5-Instances-Amazon-EC2
Blog Announcement: https://aws.amazon.com/blogs/aws/now-available-compute-intensive-c5-instances-for-amazon-ec2/
News on the 2017 launch announcement
https://cloudcomputing-news.net/news/2017/nov/09/aws-launches-c5-instances-ec2-alongside-new-cloud-optimised-hypervisor/

https://aws.amazon.com/blogs/aws/new-amazon-ec2-g4ad-instances-featuring-amd-gpus-for-graphics-workloads/

https://aws.amazon.com/blogs/aws/now-available-i3-instances-for-demanding-io-intensive-applications/

I can't find much on this instance other than its "Storage Optimized VMware High I/O Hextuple Extra Large"

The new C7i instances announced today will be added to the timeline next week. Currently on holiday 😎

Got another odd one, never seen this naming convention, but it's there, in the AWS price book... I can't find any release/announcement information on it, however. Only available in "China (Ningxia)"

Question raised by @powdahound, maintainer of the Amazon EC2 instance comparison site https://ec2instances.info - repo

@nrollr Any plans to expose the data in other formats?

Reference: vantage-sh/ec2instances.info#358

https://aws.amazon.com/about-aws/whats-new/2022/11/introducing-amazon-ec2-r7iz-instances/
https://aws.amazon.com/ec2/instance-types/r7iz/

Following feedback/input from @nicoleachou, a number of inconsistencies in terms of classification have been identified.

This includes:

• the t2.micro instance should be categorized as Micro (not General Purpose)
• the r3.large, r3.xlarge, r3.2xlarge, r3.4xlarge, r3.8xlarge instances should be Memory Optimized (not General Purpose)
• the u-6tb1.metal, u-9tb1.metal, u-12tb1.metal instances should be Memory Optimized (not High Memory)
• the u-18tb1.metal, u-24tb1.metal instances should also be Memory Optimized (not High Memory)
• ALL m5n and m5dn instances should be General Purpose (not Memory Optimized)
• ALL r5n and r5dn instances should be Memory Optimized (not General Purpose)
• the p4d.24xlarge instance should be Accelerated Computing (not GPU Optimized)
• ALL bare metal instances should have the correct category, yet without "(bare metal)" appended

Additionally, a number of instances was missing from the html page (yet mentioned in the json file)

• u-6tb1.56xlarge, u-6tb1.112xlarge, u-9tb1.112xlarge, u-12tb1.112xlarge
• These will also be categorized as Memory Optimized (not High Memory)

Pre-announced on the AWS HPC blog - 18 Nov 2021
Availability announced on the AWS news blog 10 Jan 2022

hpc6a.48xlarge

see https://aws.amazon.com/about-aws/whats-new/2021/05/four-ec2-high-memory-instances-with-up-to-12tb-memory-available-with-on-demand-and-savings-plan-purchase-options/

The new R7a instances announced today will be added to the timeline next week. Currently on holiday 😎

News article: https://aws.amazon.com/about-aws/whats-new/2023/02/amazon-ec2-m7g-r7g-instances/

https://aws.amazon.com/about-aws/whats-new/2021/04/amazon-ec2-instances-featuring-amd-epyc-processors-are-now-available-in-additional-regions/

Hi

C4 and T2 Instances still showing as current - I believe they should have been replaced by C5 and T3 respectively?

See https://aws.amazon.com/blogs/aws/new-m5n-and-r5n-instances-with-up-to-100-gbps-networking/