AWS First Steps
LanguageEnglish
Region expansion

Amazon RDS now supports AMD-based M8a instances

Amazon RDS now supports M8a database instances powered by 5th generation AMD EPYC processors for PostgreSQL, MySQL, and MariaDB, expanding options for database workloads

Amazon RDS now supports M8a database instances with 5th-gen AMD EPYC processors for PostgreSQL, MySQL, and MariaDB, expanding database workload options. Each M8a vCPU maps to a physical core, ensuring consistent per-core performance. These instances deliver up to 75 Gbps network bandwidth and 60 Gbps Amazon EBS bandwidth for high I/O workloads. Built on AWS Nitro systems with 6th-gen Nitro cards, M8a instances are available in US East (N. Virginia, Ohio), US West (Oregon), Asia Pacific (Mumbai, Tokyo, Hyderabad), and Europe (Ireland, Frankfurt, Spain) regions. You can launch M8a instances via the Amazon RDS console or AWS CLI; see RDS documentation for supported engine versions and the Amazon RDS pricing page for pricing details.

Why it matters

Aimed at users prioritizing database performance and scalability

Read the original AWS announcement

Related articles and terms

Amazon RDSA fully managed service for operating major relational databases including MySQL, PostgreSQL, Oracle, and SQL Server in the cloudRunning Managed Databases with Amazon RDS - Multi-AZ and Read Replica DesignEnsure high availability with Multi-AZ and distribute read workloads with read replicas. This article introduces Blue/Green Deployments and RDS Proxy usage patterns.Relational Databases - Achieving High Availability with Amazon RDS and AuroraLearn how to build highly available relational databases using Amazon RDS and Aurora.Amazon AuroraA high-performance database compatible with MySQL and PostgreSQL, delivering up to 5x better throughputAWS Purpose-Built Database Strategy - The Workload Optimization Philosophy Behind 15+ Specialized DatabasesWe explain the design philosophy behind AWS's 15+ purpose-built database services, comparing them with Azure Cosmos DB's unified approach and GCP's Cloud Spanner/Bigtable, and discuss the benefits of choosing the optimal database for each workload.