New AMD EPYC-Powered Amazon EC2 M5ad and R5ad Instances

Last year I told you about our New Lower-Cost, AMD-Powered M5a and R5a EC2 Instances. Built on the AWS Nitro System, these instances are powered by custom AMD EPYC processors running at 2.5 GHz. They are priced 10% lower than comparable EC2 M5 and R5 instances, and give you a new opportunity to balance your instance mix based on cost and performance.

Today we are adding M5ad and R5ad instances, both powered by custom AMD EPYC 7000 series processors and built on the AWS Nitro System.

M5ad and R5ad Instances
These instances add high-speed, low latency local (physically connected) block storage to the existing M5a and R5a instances that we launched late last year.

M5ad instances are designed for general purpose workloads such as web servers, app servers, dev/test environments, gaming, logging, and media processing. They are available in 6 sizes:

Instance NamevCPUsRAMLocal StorageEBS-Optimized BandwidthNetwork Bandwidth
m5ad.large
28 GiB1 x 75 GB NVMe SSDUp to 2.120 GbpsUp to 10 Gbps
m5ad.xlarge
416 GiB1 x 150 GB NVMe SSDUp to 2.120 GbpsUp to 10 Gbps
m5ad.2xlarge
832 GiB1 x 300 GB NVMe SSDUp to 2.120 GbpsUp to 10 Gbps
m5ad.4xlarge
1664 GiB2 x 300 GB NVMe SSD2.120 GbpsUp to 10 Gbps
m5ad.12xlarge
48192 GiB2 x 900 GB NVMe SSD5 Gbps10 Gbps
m5ad.24xlarge
96384 GiB4 x 900 GB NVMe SSD10 Gbps20 Gbps

R5ad instances are designed for memory-intensive workloads: data mining, in-memory analytics, caching, simulations, and so forth. The R5ad instances are available in 6 sizes:

Instance NamevCPUsRAMLocal StorageEBS-Optimized BandwidthNetwork Bandwidth
r5ad.large
216 GiB1 x 75 GB NVMe SSDUp to 2.120 GbpsUp to 10 Gbps
r5ad.xlarge
432 GiB1 x 150 GB NVMe SSDUp to 2.120 GbpsUp to 10 Gbps
r5ad.2xlarge
864 GiB1 x 300 GB NVMe SSDUp to 2.120 GbpsUp to 10 Gbps
r5ad.4xlarge
16128 GiB2 x 300 GB NVMe SSD2.120 GbpsUp to 10 Gbps
r5ad.12xlarge
48384 GiB2 x 900 GB NVMe SSD5 Gbps10 Gbps
r5ad.24xlarge
96768 GiB4 x 900 GB NVMe SSD10 Gbps20 Gbps

Again, these instances are available in the same sizes as the M5d and R5d instances, and the AMIs work on either, so go ahead and try both!

Here are some things to keep in mind about the local NMVe storage on the M5ad and R5ad instances:

Naming – You don’t have to specify a block device mapping in your AMI or during the instance launch; the local storage will show up as one or more devices (/dev/nvme*1 on Linux) after the guest operating system has booted.

Encryption – Each local NVMe device is hardware encrypted using the XTS-AES-256 block cipher and a unique key. Each key is destroyed when the instance is stopped or terminated.

Lifetime – Local NVMe devices have the same lifetime as the instance they are attached to, and do not stick around after the instance has been stopped or terminated.

M5ad and R5ad instances are available in the US East (N. Virginia), US West (Oregon), US East (Ohio), and Asia Pacific (Singapore) Regions in On-Demand, Spot, and Reserved Instance form.

Jeff;