# What is Amazon Relational Database Service (Amazon RDS)?
<a name="Welcome"></a>

Amazon Relational Database Service (Amazon RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the AWS Cloud. It provides cost-efficient, resizable capacity for an industry-standard relational database and manages common database administration tasks.

**Note**  
This guide covers Amazon RDS database engines other than Amazon Aurora. For information about using Amazon Aurora, see the [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html).

If you are new to AWS products and services, begin learning more with the following resources:
+ For an overview of all AWS products, see [What is cloud computing?](http://aws.amazon.com/what-is-aws/)
+ Amazon Web Services provides a number of database services. To learn more about the variety of database options available on AWS, see [Choosing an AWS database service](https://aws.amazon.com/getting-started/decision-guides/databases-on-aws-how-to-choose) and [Running databases on AWS](http://aws.amazon.com/running_databases/). 

## Advantages of Amazon RDS
<a name="Welcome.Concepts.on-prem"></a>

Amazon RDS is a managed database service. It's responsible for most management tasks. By eliminating tedious manual processes, Amazon RDS frees you to focus on your application and your users. 

Amazon RDS provides the following principal advantages over database deployments that aren't fully managed:
+ You can use database engines that you are already familiar with: IBM Db2, MariaDB, Microsoft SQL Server, MySQL, Oracle Database, and PostgreSQL.
+ Amazon RDS manages backups, software patching, automatic failure detection, and recovery.
+ You can turn on automated backups, or manually create your own backup snapshots. You can use these backups to restore a database. The Amazon RDS restore process works reliably and efficiently.
+ You can get high availability with a primary DB instance and a synchronous secondary DB instance that you can fail over to when problems occur. You can also use read replicas to increase read scaling.
+ In addition to the security in your database package, you can control access by using AWS Identity and Access Management (IAM) to define users and permissions. You can also help protect your databases by putting them in a virtual private cloud (VPC).

## Comparison of responsibilities with Amazon EC2 and on-premises deployments
<a name="Welcome.Concepts.comparison"></a>

We recommend Amazon RDS as your default choice for most relational database deployments. The following alternatives have the disadvantage of making you spend more time managing software and hardware:

**On-premises deployment**  
When you buy an on-premises server, you get CPU, memory, storage, and IOPS, all bundled together. You assume full responsibility for the server, operating system, and database software.

**Amazon EC2**  
Amazon Elastic Compute Cloud (Amazon EC2) provides scalable computing capacity in the AWS Cloud. Unlike in an on-premises server, CPU, memory, storage, and IOPS are separated so that you can scale them independently. AWS manages the hardware layers, which eliminates some of the burden of managing an on-premises database server.  
The disadvantage to running a database on Amazon EC2 is that you're more prone to user errors. For example, when you update the operating system or database software manually, you might accidentally cause application downtime. You might spend hours checking every change to identify and fix an issue.

The following table compares the management models for on-premises databases, Amazon EC2, and Amazon RDS.


|  Feature  |  On-premises management  |  Amazon EC2 management  |  Amazon RDS management  | 
| --- | --- | --- | --- | 
|  Application optimization  |  Customer  |  Customer  | Customer | 
|  Scaling  |  Customer  |  Customer  |  AWS  | 
|  High availability  |  Customer  |  Customer  |  AWS  | 
|  Database backups  |  Customer  |  Customer  |  AWS  | 
|  Database software patching  |  Customer  |  Customer  |  AWS  | 
|  Database software install  |  Customer  |  Customer  |  AWS  | 
|  Operating system (OS) patching  |  Customer  |  Customer  |  AWS  | 
|  OS installation  |  Customer  |  Customer  |  AWS  | 
|  Server maintenance  |  Customer  |  AWS  |  AWS  | 
|  Hardware lifecycle  |  Customer  |  AWS  |  AWS  | 
|  Power, network, and cooling  |  Customer  |  AWS  |  AWS  | 

## Amazon RDS shared responsibility model
<a name="Welcome.Concepts.SharedResponsibility"></a>

Amazon RDS is responsible for hosting the software components and infrastructure of DB instances and DB clusters. You are responsible for query tuning, which is the process of adjusting SQL queries to improve performance. Query performance is highly dependent on database design, data size, data distribution, application workload, and query patterns, which can vary greatly. Monitoring and tuning are highly individualized processes that you own for your RDS databases. You can use Amazon RDS Performance Insights and other tools to identify problematic queries.

## Amazon RDS DB instances
<a name="Welcome.Concepts.DBInstance"></a>

A *DB instance* is an isolated database environment in the AWS Cloud. The basic building block of Amazon RDS is the DB instance. Your DB instance can contain one or more user-created databases. The following diagram shows a virtual private cloud (VPC) that contains two Availability Zones, with each AZ containing two DB instances.

![\[Shows a VPC that spans two Availability Zones. Each AZ hosts two DB instances.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/db-instances.png)


You can access your DB instances by using the same tools and applications that you use with a standalone database instance. You can create and modify a DB instance by using the AWS Command Line Interface (AWS CLI), the Amazon RDS API, or the AWS Management Console.

**Topics**
+ [

### Amazon RDS application architecture: example
](#Welcome.Concepts.DBInstance.architecture)
+ [

### DB engines
](#Welcome.Concepts.DBInstance.engine)
+ [

### DB instance classes
](#Welcome.Concepts.DBInstance.instance-class)
+ [

### DB instance storage
](#Welcome.Concepts.DBInstance.storage)
+ [

### DB instances in an Amazon Virtual Private Cloud (Amazon VPC)
](#Welcome.Concepts.DBInstance.VPC)

### Amazon RDS application architecture: example
<a name="Welcome.Concepts.DBInstance.architecture"></a>

The following image shows a typical use case of a dynamic website that uses Amazon RDS DB instances for database storage:

![\[Shows a Region that contains a VPC containing two Availability Zones. Each AZ contains an application server and DB instance. An Elastic Load Balancer forwards user requests to the application servers.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/aws-cloud-deployment-architecture.png)


The primary components of the preceding architecture are as follows:

**Elastic Load Balancing**  
AWS routes user traffic through Elastic Load Balancing. A load balancer distributes workloads across multiple compute resources, such as virtual servers. In this sample use case, the Elastic Load Balancer forwards client requests to application servers.

**Application servers**  
Application servers interact with RDS DB instances. An application server in AWS is typically hosted on EC2 instances, which provide scalable computing capacity. The application servers reside in public subnets with different Availability Zones (AZs) within the same Virtual Private Cloud (VPC). 

**RDS DB instances**  
The EC2 application servers interact with RDS DB instances. The DB instances reside in private subnets within different Availability Zones (AZs) within the same Virtual Private Cloud (VPC). Because the subnets are private, no requests from the internet are permitted.   
The primary DB instance replicates to another DB instance, called a read replica. Both DB instances are in private subnets within the VPC, which means that Internet users can't access them directly.

### DB engines
<a name="Welcome.Concepts.DBInstance.engine"></a>

A *DB engine* is the specific relational database software that runs on your DB instance. Amazon RDS supports the following database engines:
+ IBM Db2

  For more information, see [Amazon RDS for Db2](CHAP_Db2.md).
+ MariaDB

  For more information, see [Amazon RDS for MariaDB](CHAP_MariaDB.md).
+ Microsoft SQL Server

  For more information, see [Amazon RDS for Microsoft SQL Server](CHAP_SQLServer.md).
+ MySQL

  For more information, see [Amazon RDS for MySQL](CHAP_MySQL.md).
+ Oracle Database

  For more information, see [Amazon RDS for Oracle](CHAP_Oracle.md).
+ PostgreSQL

  For more information, see [Amazon RDS for PostgreSQL](CHAP_PostgreSQL.md).

Each DB engine has its own supported features, and each version of a DB engine can include specific features. Support for Amazon RDS features varies across AWS Regions and specific versions of each DB engine. To check feature support in different engine versions and Regions, see [Supported features in Amazon RDS by AWS Region and DB engine](Concepts.RDSFeaturesRegionsDBEngines.grids.md).

Additionally, each DB engine has a set of parameters in a DB parameter group that control the behavior of the databases that it manages. For more information about parameter groups, see [Parameter groups for Amazon RDS](USER_WorkingWithParamGroups.md).

### DB instance classes
<a name="Welcome.Concepts.DBInstance.instance-class"></a>

A *DB instance class* determines the computation and memory capacity of a DB instance. A DB instance class consists of both the DB instance class type and the size. Amazon RDS supports the following instance class types, where the asterisk (\$1) represents the generation, optional attribute, and size:
+ General purpose – db.m\$1
+ Memory optimized – db.z\$1, db.x\$1, db.r\$1
+ Compute optimized – db.c\$1
+ Burstable performance – db.t\$1

Each instance class offers different compute, memory, and storage capabilities. For example, db.m7g is a 7th-generation, general-purpose DB instance class type powered by AWS Graviton3 processors. When you create a DB instance, you specify a DB instance class such as db.m7g.2xlarge, where 2xlarge is the size. For more information about the hardware specifications for the different instance classes, see [Hardware specifications for DB instance classes](Concepts.DBInstanceClass.Summary.md).

You can select the DB instance class that best meets your requirements. If your requirements change over time, you can change your DB instance class. For example, you might scale up your db.m7g.2xlarge instance to db.m7g.4xlarge. For more information, see [DB instance classes](Concepts.DBInstanceClass.md).

**Note**  
For pricing information on DB instance classes, see the Pricing section of the [Amazon RDS](http://aws.amazon.com/rds/) product page.

### DB instance storage
<a name="Welcome.Concepts.DBInstance.storage"></a>

Amazon EBS provides durable, block-level storage volumes that you can attach to a running instance. DB instance storage comes in the following types:
+ General Purpose (SSD)

  This cost-effective storage type is ideal for a broad range of workloads running on medium-sized DB instances. General Purpose storage is best suited for development and testing environments.
+ Provisioned IOPS (PIOPS)

  This storage type is designed to meet the needs of I/O-intensive workloads, particularly database workloads, that require low I/O latency and consistent I/O throughput. Provisioned IOPS storage is best suited for production environments.
+ Magnetic

  Amazon RDS supports magnetic storage for backward compatibility. We recommend that you use General Purpose SSD or Provisioned IOPS SSD for any new storage needs. 

The storage types differ in performance characteristics and price. You can tailor your storage performance and cost to the requirements of your database. 

Each DB instance has minimum and maximum storage requirements depending on the storage type and the database engine it supports. It's important to have sufficient storage so that your databases have room to grow. Also, sufficient storage makes sure that features for the DB engine have room to write content or log entries. For more information, see [Amazon RDS DB instance storage](CHAP_Storage.md).

### DB instances in an Amazon Virtual Private Cloud (Amazon VPC)
<a name="Welcome.Concepts.DBInstance.VPC"></a>

You can run a DB instance on a virtual private cloud (VPC) using the Amazon Virtual Private Cloud (Amazon VPC) service. When you use a VPC, you have control over your virtual networking environment. You can choose your own IP address range, create subnets, and configure routing and access control lists. 

The basic functionality of Amazon RDS is the same whether it's running in a VPC or not. Amazon RDS manages backups, software patching, automatic failure detection, and recovery. There's no additional cost to run your DB instance in a VPC. For more information on using Amazon VPC with RDS, see [Amazon VPC and Amazon RDS](USER_VPC.md). 

Amazon RDS uses Network Time Protocol (NTP) to synchronize the time on DB instances.

## AWS Regions and Availability Zones
<a name="Welcome.Concepts.Regions"></a>

Amazon cloud computing resources are housed in highly available data center facilities in different areas of the world (for example, North America, Europe, or Asia). Each data center location is called an AWS Region. With Amazon RDS, you can create your DB instances in multiple Regions.

The following scenario shows an RDS DB instance in one Region that replicates asynchronously to a standby DB instance in a different Region. If one Region becomes unavailable, the instance in the other Region is still available.

![\[Cross-Region read replica configuration\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/read-replica-cross-region.png)


### Availability Zones
<a name="Welcome.Concepts.Regions.AZ"></a>

Each AWS Region contains multiple distinct locations called Availability Zones, or AZs. Each Availability Zone is engineered to be isolated from failures in other Availability Zones. Each is engineered to provide inexpensive, low-latency network connectivity to other Availability Zones in the same AWS Region. By launching DB instances in separate Availability Zones, you can protect your applications from the failure of a single location. For more information, see [Regions, Availability Zones, and Local Zones](Concepts.RegionsAndAvailabilityZones.md).

### Multi-AZ deployments
<a name="Welcome.Concepts.Regions.MAZ"></a>

You can run your DB instance in several Availability Zones, an option called a Multi-AZ deployment. When you choose this option, Amazon automatically provisions and maintains one or more secondary standby DB instances in a different AZ. Your primary DB instance is replicated across Availability Zones to each secondary DB instance.

A Multi-AZ deployment provides the following advantages:
+ Providing data redundancy and failover support
+ Eliminating I/O freezes
+ Minimizing latency spikes during system backups
+ Serving read traffic on secondary DB instances (Multi-AZ DB clusters deployment only)

The following diagram depicts a Multi-AZ DB instance deployment, where Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone. The replica database doesn't serve read traffic.

![\[High availability scenario for a Multi-AZ instance deployment\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/con-multi-AZ.png)


The following diagram depicts a Multi-AZ DB cluster deployment, which has a writer DB instance and two reader DB instances in three separate Availability Zones in the same AWS Region. All three DB instances can serve read traffic.

![\[High availability scenario for a Multi-AZ cluster deployment\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/multi-az-db-cluster.png)


For more information, see [Configuring and managing a Multi-AZ deployment for Amazon RDS](Concepts.MultiAZ.md).

## Access control with security groups
<a name="Welcome.Concepts.SecurityGroups"></a>

A *security group *controls the access to a DB instance by allowing access to IP address ranges or Amazon EC2 instances that you specify. You can apply a security group to one or more DB instances.

A common use of a DB instance in a VPC is to share data with an application server in the same VPC. The following example uses VPC security group `ec2-rds-x` to define inbound rules that use the IP addresses of the client application as the source. The application server belongs to this security group. A second security group named `rds-ec2-x` specifies `ec2-rds-x` as the source and attaches to an RDS DB instance. According to the security group rules, client applications can't directly access the DB instance, but the EC2 instance can access the DB instance.

![\[DB instance and EC2 instance in a VPC\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/con-VPC-sec-grp.png)


For more information about security groups, see [Security in Amazon RDS ](UsingWithRDS.md).

## Amazon RDS monitoring
<a name="Welcome.Monitoring"></a>

Monitoring is an important part of maintaining the reliability, availability, and performance of Amazon RDS and your other AWS solutions. AWS provides various monitoring tools to watch Amazon RDS, report when something is wrong, and take automatic actions when appropriate.

You can track the performance and health of your DB instances using various automated and manual tools:

**Amazon RDS DB instance status and recommendations**  
View details about the current status of your instance by using the Amazon RDS console, AWS CLI, or RDS API. You can also respond to automated recommendations for database resources, such as DB instances, read replicas, and DB parameter groups. For more information, see [Recommendations from Amazon RDS](monitoring-recommendations.md).

**Amazon CloudWatch metrics for Amazon RDS**  
You can use the Amazon CloudWatch service to monitor the performance and health of a DB instance. CloudWatch performance charts are shown in the Amazon RDS console. Amazon RDS automatically sends metrics to CloudWatch every minute for each active database. You don't get additional charges for Amazon RDS metrics in CloudWatch.  
Using Amazon CloudWatch alarms, you can watch a single Amazon RDS metric over a specific time period. You can then perform one or more actions based on the value of the metric relative to a threshold that you set. For more information, see [Monitoring Amazon RDS metrics with Amazon CloudWatch](monitoring-cloudwatch.md).

**Amazon RDS Performance Insights and operating-system monitoring**  
Performance Insights assesses the load on your database, and determine when and where to take action. For more information, see [Monitoring DB load with Performance Insights on Amazon RDS](USER_PerfInsights.md). Amazon RDS Enhanced Monitoring looks at metrics in real time for the operating system. For more information, see [Monitoring OS metrics with Enhanced Monitoring](USER_Monitoring.OS.md).

**Integrated AWS services**  
Amazon RDS is integrated with Amazon EventBridge, Amazon CloudWatch Logs, and Amazon DevOps Guru. For more information, see [Monitoring metrics in an Amazon RDS instance](CHAP_Monitoring.md). 

## User interfaces to Amazon RDS
<a name="Welcome.Interfaces"></a>

You can interact with Amazon RDS in multiple ways.

**Topics**
+ [

### AWS Management Console
](#Welcome.Interfaces.Console)
+ [

### Command line interface
](#Welcome.Interfaces.CLI)
+ [

### Amazon RDS APIs
](#Welcome.Interfaces.API)

### AWS Management Console
<a name="Welcome.Interfaces.Console"></a>

The AWS Management Console is a simple web-based user interface. You can manage your DB instances from the console with no programming required. To access the Amazon RDS console, sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/). 

![\[Home page of the RDS console. The left panel includes links for Dashboard, Databases, and so on. The central panel lists resources such as DB instances.\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/rds_console.png)


### Command line interface
<a name="Welcome.Interfaces.CLI"></a>

You can use the AWS Command Line Interface (AWS CLI) to access the Amazon RDS API interactively. To install the AWS CLI, see [Installing the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/installing.html). To begin using the AWS CLI for RDS, see [AWS Command Line Interface reference for Amazon RDS](https://docs.aws.amazon.com/cli/latest/reference/rds/index.html). 

### Amazon RDS APIs
<a name="Welcome.Interfaces.API"></a>

If you are a developer, you can access the Amazon RDS programmatically using APIs. For more information, see [Amazon RDS API reference](ProgrammingGuide.md). 

For application development, we recommend that you use one of the AWS Software Development Kits (SDKs). The AWS SDKs handle low-level details such as authentication, retry logic, and error handling, so that you can focus on your application logic. AWS SDKs are available for a wide variety of languages. For more information, see [Tools for Amazon web services ](https://aws.amazon.com/tools/). 

AWS also provides libraries, sample code, tutorials, and other resources to help you get started more easily. For more information, see [Sample code & libraries](https://aws.amazon.com/code). 

## How you are charged for Amazon RDS
<a name="Welcome.Costs"></a>

When you use Amazon RDS, you can choose to use on-demand DB instances or reserved DB instances. For more information, see [DB instance billing for Amazon RDS ](User_DBInstanceBilling.md). 

For Amazon RDS pricing information, see the [Amazon RDS product page](https://aws.amazon.com/rds/pricing).

## AWS Free Tier on Amazon RDS
<a name="free-tier-limitations"></a>

You can use AWS Free Tier on Amazon RDS with the following engines and DB instance classes:
+ **Engine types** – MariaDB, MySQL, PostgreSQL, or SQL Server Express Edition
+ **DB instance classes** 
  + **t3.micro** – For all engine types
  + **t4g.micro** – For all engine types except SQL Server Express Edition

You can't use the following features, resources, and actions with AWS Free Tier on Amazon RDS:
+ Amazon RDS custom engine options
+ Reserved DB instances
+ Deployment options other than Single-AZ
+ Migrating snapshots
+ Query editor
+ Creating Aurora read replicas

These limitations are subject to change as the AWS Free Tier program evolves. For more information about AWS Free Tier, see [Explore AWS services with AWS Free Tier](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/free-tier.html). For more information about Amazon RDS Free Tier, see [Amazon RDS Free Tier](https://aws.amazon.com/rds/free/).

If you were an AWS Free Tier customer before July 17, 2025, you can continue to use Amazon RDS Free Tier until the 12 months of your free usage expires. During this time period, you remain eligible for the following usage:
+ 750 hours each month of Single-AZ db.t3.micro and db.t4g.micro instance classes running MySQL, MariaDB, or PostgreSQL on Amazon RDS
+ 750 hours each month of a db.t3.micro instance class running SQL Server Express Edition on Amazon RDS

After July 17, 2025, any new AWS Free Tier resources that you create on AWS will use the new AWS Free Tier offering.

## What's next?
<a name="Welcome.WhatsNext"></a>

The preceding section introduced you to the basic infrastructure components that RDS offers. What should you do next? 

### Getting started
<a name="Welcome.WhatsNext.GettingStarted"></a>

Create a DB instance using instructions in [Getting started with Amazon RDS](CHAP_GettingStarted.md). 

### Topics specific to database engines
<a name="Welcome.WhatsNext.DBTopics"></a>

You can review information specific to a particular DB engine in the following sections:
+ [Amazon RDS for Db2](CHAP_Db2.md)
+ [Amazon RDS for MariaDB](CHAP_MariaDB.md)
+ [Amazon RDS for Microsoft SQL Server](CHAP_SQLServer.md)
+ [Amazon RDS for MySQL](CHAP_MySQL.md)
+ [Amazon RDS for Oracle](CHAP_Oracle.md)
+ [Amazon RDS for PostgreSQL](CHAP_PostgreSQL.md)

# Amazon RDS DB instances
<a name="Overview.DBInstance"></a>

A *DB instance* is an isolated database environment running in the cloud. It is the basic building block of Amazon RDS. A DB instance can contain multiple user-created databases, and can be accessed using the same client tools and applications you might use to access a standalone database instance. DB instances are simple to create and modify with the AWS command line tools, Amazon RDS API operations, or the AWS Management Console. 

**Note**  
Amazon RDS supports access to databases using any standard SQL client application. Amazon RDS does not allow direct host access except with RDS Custom. 

You can have up to 40 Amazon RDS DB instances, with the following limitations:
+ 10 for each SQL Server edition (Enterprise, Standard, Web, and Express) under the "license-included" model
+ 10 for Oracle under the "license-included" model
+ 40 for Db2 under the "bring-your-own-license" (BYOL) licensing model
+ 40 for MySQL, MariaDB, or PostgreSQL
+ 40 for Oracle under the "bring-your-own-license" (BYOL) licensing model

**Note**  
If your application requires more DB instances, you can request additional DB instances by using [this form](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-rds-instances).

Each DB instance has a DB instance identifier. This customer-supplied name uniquely identifies the DB instance when interacting with the Amazon RDS API and AWS CLI commands. The DB instance identifier must be unique for that customer in an AWS Region.

The DB instance identifier forms part of the DNS hostname allocated to your instance by RDS. For example, if you specify `db1` as the DB instance identifier, then RDS will automatically allocate a DNS endpoint for your instance. An example endpoint is `db1.abcdefghijkl.us-east-1.rds.amazonaws.com`, where `db1` is your instance ID. 

In the example endpoint `db1.abcdefghijkl.us-east-1.rds.amazonaws.com`, the string `abcdefghijkl` is a unique identifier for a specific combination of AWS Region and AWS account. The identifier `abcdefghijkl` in the example is internally generated by RDS and doesn't change for the specified combination of Region and account. Thus, all your DB instances in this Region share the same fixed identifier. Consider the following features of the fixed identifier:
+ If you rename your DB instance, the endpoint is different but the fixed identifier is the same. For example, if you rename `db1` to `renamed-db1`, the new instance endpoint is `renamed-db1.abcdefghijkl.us-east-1.rds.amazonaws.com`. 
+ If you delete and re-create a DB instance with the same DB instance identifier, the endpoint is the same. 
+ If you use the same account to create a DB instance in a different Region, the internally generated identifier is different because the Region is different, as in `db2.mnopqrstuvwx.us-west-1.rds.amazonaws.com`. 

Each DB instance supports a database engine. Amazon RDS currently supports Db2, MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server, and Amazon Aurora database engines. 

When creating a DB instance, some database engines require that a database name be specified. A DB instance can host multiple databases or a single Oracle database with multiple schemas. The database name value depends on the database engine:
+ For the Db2 database engine, the database name is the name of the database hosted in your DB instance. This field is optional. You can create a database later by calling the `rdsadmin.create_database` stored procedure. For more information, see [Creating a database](db2-managing-databases.md#db2-creating-database). 
+ For the MySQL and MariaDB database engines, the database name is the name of a database hosted in your DB instance. Databases hosted by the same DB instance must have a unique name within that instance. 
+ For the Oracle database engine, database name is used to set the value of ORACLE\$1SID, which must be supplied when connecting to the Oracle RDS instance. 
+ For the Microsoft SQL Server database engine, database name is not a supported parameter.
+ For the PostgreSQL database engine, the database name is the name of a database hosted in your DB instance. A database name is not required when creating a DB instance. Databases hosted by the same DB instance must have a unique name within that instance.

Amazon RDS creates a master user account for your DB instance as part of the creation process. This master user has permissions to create databases and to perform create, delete, select, update, and insert operations on tables the master user creates. You must set the master user password when you create a DB instance, but you can change it at any time using the AWS CLI, Amazon RDS API operations, or the AWS Management Console. You can also change the master user password and manage users using standard SQL commands. 

**Note**  
This guide covers non-Aurora Amazon RDS database engines. For information about using Amazon Aurora, see the [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html).

# DB instance classes
<a name="Concepts.DBInstanceClass"></a>

The DB instance class determines the computation and memory capacity of an Amazon RDS DB instance. The DB instance class that you need depends on your processing power and memory requirements.

A DB instance class consists of both the DB instance class type and the size. For example, db.r6g is a memory-optimized DB instance class type powered by AWS Graviton2 processors. Within the db.r6g instance class type, db.r6g.2xlarge is a DB instance class. The size of this class is 2xlarge.

For more information about instance class pricing, see [Amazon RDS pricing](https://aws.amazon.com/rds/pricing/).

For more information about DB instance class types, supported DB engines, supported AWS Regions, changing your DB instance class, configuring the processor for RDS for Oracle, or hardware specifications for DB instance classes, see the following sections.

**Topics**
+ [

# DB instance class types
](Concepts.DBInstanceClass.Types.md)
+ [

# Supported DB engines for DB instance classes
](Concepts.DBInstanceClass.Support.md)
+ [

# Determining DB instance class support in AWS Regions
](Concepts.DBInstanceClass.RegionSupport.md)
+ [

## Changing your DB instance class
](#Concepts.DBInstanceClass.Changing)
+ [

# Configuring the processor for a DB instance class in RDS for Oracle
](USER_ConfigureProcessor.md)
+ [

# Hardware specifications for DB instance classes
](Concepts.DBInstanceClass.Summary.md)

# DB instance class types
<a name="Concepts.DBInstanceClass.Types"></a>

Amazon RDS supports DB instance classes for the following use cases:
+ [General-purpose](#Concepts.DBInstanceClass.Types.general-purpose)
+ [Memory-optimized](#Concepts.DBInstanceClass.Types.memory)
+ [Compute-optimized](#Concepts.DBInstanceClass.Types.compute)
+ [Burstable-performance](#Concepts.DBInstanceClass.Types.burstable)
+ [Optimized Reads](#Concepts.DBInstanceClass.Types.optimized-reads)

 For more information about Amazon EC2 instance types, see [Instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html) in the Amazon EC2 documentation. 

## General-purpose instance class types
<a name="Concepts.DBInstanceClass.Types.general-purpose"></a>

The following general-purpose DB instance classes are available:
+ **db.m8g** – General-purpose DB instance classes powered by AWS Graviton4 processors. These instance classes deliver balanced compute, memory, and networking for a broad range of general-purpose workloads. Compared to seventh-generation AWS Graviton3-based M7g instances, these new classes offer larger instance sizes with up to 3x more vCPUs and memory. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.

  You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton4 processors. To do so, complete the same steps as with any other DB instance modification.
+ **db.m8i** – General-purpose DB instance classes powered by Intel Xeon 6 processors. These instances deliver the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. The M8i offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances.
+ **db.m7i** – General-purpose DB instance classes powered by 4th Generation Intel Xeon Scalable processors. The db.m7i instances are SAP certified and ideal for supporting enterprise applications that need larger instance sizes or high continuous CPU usage. These instance classes deliver balanced compute, memory, and networking for a broad range of general-purpose workloads. This instance class type delivers up to 40,000 Mbps EBS bandwidth and up to 50 Gbps network bandwidth. The db.m7i instances deliver up to 15% better price performance compared to db.m6i instances. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.m7g** – General-purpose DB instance classes powered by AWS Graviton3 processors. These instance classes deliver balanced compute, memory, and networking for a broad range of general-purpose workloads. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor. 

  You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton3 processors. To do so, complete the same steps as with any other DB instance modification.
+ **db.m6g** – General-purpose DB instance classes powered by AWS Graviton2 processors. These instances deliver balanced compute, memory, and networking for a broad range of general-purpose workloads. The db.m6gd instance classes have local NVMe-based SSD block-level storage for applications that need high-speed, low latency local storage.

  You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton2 processors. To do so, complete the same steps as with any other DB instance modification.
+ **db.m6i** – General-purpose DB instance classes powered by 3rd Generation Intel Xeon Scalable processors. These instances are SAP Certified and ideal for workloads such as backend servers supporting enterprise applications, gaming servers, caching fleets, and application development environments. The db.m6id and db.m6idn instance classes offer up to 7.6 TB of local NVMe-based SSD storage, whereas db.m6in offers EBS-only storage. The db.m6in and db.m6idn classes offer up to 200 Gbps of network bandwidth. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.m5** –General-purpose DB instance classes that provide a balance of compute, memory, and network resources, and are a good choice for many applications. The db.m5d instance class offers NVMe-based SSD storage that is physically connected to the host server. The db.m5 instance classes provide more computing capacity than the previous db.m4 instance classes. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.m4** – General-purpose DB instance classes that provide more computing capacity than the previous db.m3 instance classes.

  For the RDS for Oracle DB engines, Amazon RDS no longer supports db.m4 DB instance classes. If you had previously created RDS for Oracle db.m4 DB instances, Amazon RDS automatically upgrades those DB instances to equivalent db.m5 DB instance classes.

  For the RDS for MariaDB, RDS for MySQL, RDS for SQL Server, and RDS for PostgreSQL DB engines, Amazon RDS has started the end-of-support process for this DB instance class using the following schedule. For all RDS DB instances that use this instance class, we recommend that you upgrade to a newer generation DB instance class as soon as possible.    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.Types.html)
+ **db.m3** – General-purpose DB instance classes that provide more computing capacity than the previous db.m1 instance classes.

  For the RDS for MariaDB, RDS for MySQL, and RDS for PostgreSQL DB engines, Amazon RDS has started the end-of-life process for db.m3 DB instance classes using the following schedule, which includes upgrade recommendations. For all RDS DB instances that use db.m3 DB instance classes, we recommend that you upgrade to a higher generation DB instance class as soon as possible.    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.Types.html)

## Memory-optimized instance class types
<a name="Concepts.DBInstanceClass.Types.memory"></a>

The memory-optimized Z family supports the following instance classes:
+ **db.z1d** – Instance classes optimized for memory-intensive applications. These instance classes offer both high compute capacity and a high memory footprint. High frequency z1d instances deliver a sustained all-core frequency of up to 4.0 GHz.

The memory-optimized X family supports the following instance classes:
+ **db.x2g** – Instance classes optimized for memory-intensive applications and powered by AWS Graviton2 processors. These instance classes offer low cost per GiB of memory.

  You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton2 processors. To do so, complete the same steps as with any other DB instance modification.
+ **db.x2i** – Instance classes optimized for memory-intensive applications. The **db.x2iedn** and **db.x2idn** instance class types are powered by third-generation Intel Xeon Scalable processors (Ice Lake). They include up to 3.8 TB of local NVMe SSD storage, up to 100 Gbps of networking bandwidth, and up to 4 TiB (db.x2iden) or 2 TiB (db.x2idn) of memory. The **db.x2iezn** type is powered by second-generation Intel Xeon Scalable processors (Cascade Lake) with an all-core turbo frequency of up to 4.5 GHz and up to 1.5 TiB of memory and by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.x1** – Instance classes optimized for memory-intensive applications. These instance classes offer one of the lowest price per GiB of RAM among the DB instance classes and up to 1,952 GiB of DRAM-based instance memory. The **db.x1e** instance class type offers up to 3,904 GiB of DRAM-based instance memory.

The memory-optimized R family supports the following instance class types:
+ **db.r8g** – Instance classes powered by AWS Graviton4 processors. These instance classes are ideal for running memory-intensive workloads in open-source databases such as MySQL and PostgreSQL. These instances offer larger instance sizes with up to 3x more vCPUs and memory than the seventh-generation AWS Graviton3-based db.r7g instances. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton4 processors. To do so, complete the same steps as with any other DB instance modification.
+ **db.r8i** – Instance classes powered by Intel Xeon 6 processors. These instance classes are ideal for running memory-intensive workloads that benefit from high-performance local storage, including in-memory databases, real-time big data analytics, large in-memory caches, scientific computing applications requiring scratch space, and data processing applications needing high-speed local storage.
+ **db.r7g** – Instance classes powered by AWS Graviton3 processors. These instance classes are ideal for running memory-intensive workloads in open-source databases such as MySQL and PostgreSQL.

  You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton3 processors. To do so, complete the same steps as with any other DB instance modification. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.r7i** – Instance classes powered by 4th Generation Intel Xeon Scalable processors. These instance classes are SAP-Certified and are ideal for running memory-intensive workloads in open-source databases such as MySQL and PostgreSQL. You can modify a DB instance to use one of the DB instance classes powered by 4th Generation Intel Xeon Scalable processors. To do so, complete the same steps as with any other DB instance modification. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.r6g** – Instance classes powered by AWS Graviton2 processors. These instance classes are ideal for running memory-intensive workloads in open-source databases such as MySQL and PostgreSQL. The **db.r6gd** type offers local NVMe-based SSD block-level storage for applications that need high-speed, low latency local storage. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton2 processors. To do so, complete the same steps as with any other DB instance modification.
+ **db.r6i** – Instance classes powered by 3rd Generation Intel Xeon Scalable processors. These instance classes are SAP-Certified and are an ideal fit for memory-intensive workloads in open-source databases such as MySQL and PostgreSQL. The **db.r6id**, **db.r6in**, and **db.r6idn** instance classes have a memory-to-vCPU ratio of 8:1 and a maximum memory of 1 TiB. The db.r6id and db.r6idn classes offer up to 7.6 TB of direct-attached NVMe-based SSD storage, whereas db.r6in offers EBS-only storage. The db.r6idn and db.r6in classes offer up to 200 Gbps of network bandwidth. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.r5b** – Instance classes that are memory-optimized for throughput-intensive applications. Powered by the AWS Nitro System, db.r5b instances deliver up to 60 Gbps bandwidth and 260,000 IOPS of EBS performance. This is the fastest block storage performance on EC2.
+ **db.r5d** – Instance classes that are optimized for low latency, very high random I/O performance, and high sequential read throughput.
+ **db.r5** – Instance classes optimized for memory-intensive applications. These instance classes offer improved networking performance. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.
+ **db.r4** – Instance classes that provide improved networking over previous db.r3 instance classes.

  For the RDS for Oracle DB engines, Amazon RDS has started the end-of-life process for db.r4 DB instance classes using the following schedule, which includes upgrade recommendations. For RDS for Oracle DB instances that use db.r4 instance classes, we recommend that you upgrade to a higher generation instance class as soon as possible.    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.Types.html)

  For the RDS for MariaDB, RDS for MySQL, RDS for SQL Server, and RDS for PostgreSQL DB engines, Amazon RDS has started the end-of-support process for this DB instance class using the following schedule. For all RDS DB instances that use this instance class, we recommend that you upgrade to a newer generation DB instance class as soon as possible.    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.Types.html)
+ **db.r3** – Instance classes that provide memory optimization.

  For the RDS for MariaDB, RDS for MySQL, and RDS for PostgreSQL DB engines, Amazon RDS has started the end-of-life process for db.r3 DB instance classes using the following schedule, which includes upgrade recommendations. For all RDS DB instances that use db.r3 DB instance classes, we recommend that you upgrade to a higher generation DB instance class as soon as possible.    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.Types.html)

## Compute-optimized instance class type
<a name="Concepts.DBInstanceClass.Types.compute"></a>

The following compute-optimized instance class types are available:
+ **db.c6gd** – Instance classes that are ideal for running advanced compute-intensive workloads. Powered by AWS Graviton2 processors, these instance classes offer local NVMe-based SSD block-level storage for applications that need high-speed, low latency local storage.
**Note**  
The c6gd instance classes are supported only for Multi-AZ DB cluster deployments. They're the only instance class supported for Multi-AZ DB clusters that offer the `medium` instance size. For more information, see [Multi-AZ DB cluster deployments for Amazon RDS](multi-az-db-clusters-concepts.md).

## Burstable-performance instance class types
<a name="Concepts.DBInstanceClass.Types.burstable"></a>

The following burstable-performance DB instance class types are available:
+ **db.t4g** – General-purpose instance classes powered by Arm-based AWS Graviton2 processors. These instance classes deliver better price performance than previous burstable-performance DB instance classes for a broad set of burstable general-purpose workloads. Amazon RDS db.t4g instances are configured for Unlimited mode. This means that they can burst beyond the baseline over a 24-hour window for an additional charge.

  You can modify a DB instance to use one of the DB instance classes powered by AWS Graviton2 processors. To do so, complete the same steps as with any other DB instance modification.
+ **db.t3** – Instance classes that provide a baseline performance level, with the ability to burst to full CPU usage. The db.t3 instances are configured for Unlimited mode. These instance classes provide more computing capacity than the previous db.t2 instance classes. They are powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor. 
+ **db.t2** – Instance classes that provide a baseline performance level, with the ability to burst to full CPU usage. The db.t2 instances are configured for Unlimited mode. We recommend using these instance classes only for development and test servers, or other non-production servers.

  For the RDS for MariaDB, RDS for MySQL, RDS for SQL Server, and RDS for PostgreSQL DB engines, Amazon RDS has started the end-of-support process for this DB instance class using the following schedule. For all RDS DB instances that use this instance class, we recommend that you upgrade to a newer generation DB instance class as soon as possible.    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.Types.html)

**Note**  
The DB instance classes that use the AWS Nitro System (db.m5, db.r5, db.t3) are throttled on combined read plus write workload.

For DB instance class hardware specifications, see [Hardware specifications for DB instance classes](Concepts.DBInstanceClass.Summary.md).

## Optimized Reads instance class types
<a name="Concepts.DBInstanceClass.Types.optimized-reads"></a>

The following Optimized Reads instance class types are available:
+ **db.m8gd** – Instance classes powered by AWS Graviton4 processor. These instance classes are ideal for general purpose workloads that need high-speed, low latency storage. They offer a maximum memory of 786 GiB and up to 11.4 TB of direct-attached NVMe-based SSD storage.
+ **db.r8gd** – Instance classes powered by Graviton4 processors. These instance classes are ideal for running memory-intensive workloads and offer local NVMe-based SSD block-level storage for applications that need high-speed, low latency local storage. They offer a maximum memory of 1.5 TiB and up to 11.4 TB of direct-attached NVMe-based SSD storage.
+ **db.r6gd** – Instance classes powered by AWS Graviton2 processors. These instance classes are ideal for running memory-intensive workloads and offer local NVMe-based SSD block-level storage for applications that need high-speed, low latency local storage.
+  **db.r6id** – Instance classes powered by 3rd Generation Intel Xeon Scalable processors. These instance classes are SAP-Certified and are an ideal fit for memory-intensive workloads. They offer a maximum memory of 1 TiB and up to 7.6 TB of direct-attached NVMe-based SSD storage.

# Supported DB engines for DB instance classes
<a name="Concepts.DBInstanceClass.Support"></a>

The following are DB engine–specific considerations for DB instance classes:

**Db2**  
DB instance class support varies according to the version and edition of Db2. For instance class support by version and edition, see [Amazon RDS for Db2 instance classes](Db2.Concepts.General.InstanceClasses.md). 

**Microsoft SQL Server**  
DB instance class support varies according to the version and edition of SQL Server. For instance class support by version and edition, see [DB instance class support for Microsoft SQL Server](SQLServer.Concepts.General.InstanceClasses.md). 

**Oracle**  
DB instance class support varies according to the Oracle Database version and edition. RDS for Oracle supports additional memory-optimized instance classes. These classes have names of the form db.r5.*instance\$1size*.tpc*threads\$1per\$1core*.mem*ratio*. For the vCPU count and memory allocation for each optimized class, see [Supported RDS for Oracle DB instance classes](Oracle.Concepts.InstanceClasses.md#Oracle.Concepts.InstanceClasses.Supported).

**RDS Custom**  
For information about the DB instance classes supported in RDS Custom, see [DB instance class support for RDS Custom for Oracle](custom-oracle-feature-support.md#custom-reqs-limits.instances) and [DB instance class support for RDS Custom for SQL Server](custom-reqs-limits.instancesMS.md).

In the following table, you can find details about supported Amazon RDS DB instance classes for each Amazon RDS DB engine. The cell for each engine contains one of the following values:

Yes  
The instance class is supported for all versions of the DB engine.

No  
The instance class isn't supported for the DB engine.

*specific-versions*  
The instance class is supported only for the specified database versions of the DB engine.

Amazon RDS periodically deprecates major and minor DB engine versions. Not all AWS Regions might have support for earlier engine versions. For information about current supported versions, see topics for the individual DB engines: [Db2 versions](Db2.Concepts.VersionMgmt.Supported.md), [MariaDB versions](MariaDB.Concepts.VersionMgmt.md#MariaDB.Concepts.VersionMgmt.Supported), [Microsoft SQL Server versions](SQLServer.Concepts.General.VersionSupport.md), [MySQL versions](MySQL.Concepts.VersionMgmt.md), [Oracle versions](Oracle.Concepts.database-versions.md), and [PostgreSQL versions](PostgreSQL.Concepts.General.DBVersions.md).

**Topics**
+ [

## Supported DB engines for general-purpose instance classes
](#gen-purpose-inst-classes)
+ [

## Supported DB engines for memory-optimized instance classes
](#mem-opt-inst-classes)
+ [

## Supported DB engines for compute-optimized instance classes
](#compute-opt-inst-classes)
+ [

## Supported DB engines for burstable-performance instance classes
](#burstable-inst-classes)
+ [

## Supported DB engines for Optimized Reads instance classes
](#read-opt-inst-classes)

## Supported DB engines for general-purpose instance classes
<a name="gen-purpose-inst-classes"></a>

The following tables show the supported databases and database versions for the general-purpose instance classes.

**db.m8g – general-purpose instance classes powered by AWS Graviton4 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m8g.48xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.24xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.16xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.12xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.8xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.4xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.2xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m8g.large | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 

**db.m8i – general-purpose instance classes powered by Intel Xeon 6 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m8i.48xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.m8i.24xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.m8i.16xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.m8i.12xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.m8i.8xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.m8i.4xlarge | No | No | No | No | BYOL only, all editions | No | 
| db.m8i.2xlarge | No | No | No | No | BYOL only, all editions | No | 
| db.m8i.xlarge | No | No | No | No | BYOL only, all editions | No | 
| db.m8i.large | No | No | No | No | BYOL only, all editions | No | 
| db.m8i.metal-96xl | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.m8i.metal-48xl | No | No | No | No | BYOL only, Enterprise Edition only | No | 

**db.m7i – general-purpose instance classes powered by 4th generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m7i.48xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, Enterprise Edition only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.24xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, Enterprise Edition only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.16xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, Enterprise Edition only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.12xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, Enterprise Edition only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.8xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, Enterprise Edition only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.4xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.2xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.large | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.m7i.metal-48xl | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.m7i.metal-24xl | No | No | No | No | BYOL only, Enterprise Edition only | No | 

**db.m7g – general-purpose instance classes powered by AWS Graviton3 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m7g.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.m7g.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.m7g.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.m7g.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.m7g.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.m7g.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.m7g.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 

**db.m6g – general-purpose instance classes powered by AWS Graviton2 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6g.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.m6g.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.m6g.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.m6g.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.m6g.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.m6g.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.m6g.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 

**db.m6gd – general-purpose instance classes powered by AWS Graviton2 processors and SSD storage**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6gd.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, and 14 versions; 13.7 and higher 13 versions; and 13.4 | 
| db.m6gd.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, and 14 versions; 13.7 and higher 13 versions; and 13.4 | 
| db.m6gd.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, and 14 versions; 13.7 and higher 13 versions; and 13.4 | 
| db.m6gd.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, and 14 versions; 13.7 and higher 13 versions; and 13.4 | 
| db.m6gd.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, and 14 versions; 13.7 and higher 13 versions; and 13.4 | 
| db.m6gd.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, and 14 versions; 13.7 and higher 13 versions; and 13.4 | 
| db.m6gd.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, and 14 versions; 13.7 and higher 13 versions; and 13.4 | 

**db.m6id – general-purpose instance classes powered by 3rd generation Intel Xeon Scalable processors and SSD storage**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6id.32xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.24xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.16xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.12xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.8xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.4xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.2xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.large | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6id.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.m6idn – general-purpose instance classes with 3rd Generation Intel Xeon Scalable processors, SSD storage, and network optimization**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6idn.32xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.24xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.16xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.12xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.8xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.4xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.2xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.m6idn.large | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 

**db.m6in – general-purpose instance classes powered by 3rd generation Intel Xeon Scalable processors and network optimization**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6in.32xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.24xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.16xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.12xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.8xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.4xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.2xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.large | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.m6in.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.m6i – general-purpose instance classes powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6i.32xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.24xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.16xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.12xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.8xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.4xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.2xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.large | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Oracle Database 19c  |  All available versions  | 
| db.m6i.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.m5d – general-purpose instance classes powered by Intel Xeon Platinum processors and SSD storage**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m5d.24xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.m5d.16xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.m5d.12xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.m5d.8xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.m5d.4xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.m5d.2xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.m5d.xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.m5d.large | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 

**db.m5 – general-purpose instance classes 2.5 GHz Intel Xeon Platinum processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m5.24xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.m5.16xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.m5.12xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.m5.8xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.m5.4xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.m5.2xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.m5.xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.m5.large | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 

**db.m4 – general-purpose instance classes with Intel Xeon processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m4.16xlarge | No | Deprecated |  Deprecated  | Deprecated |  Deprecated  | Deprecated | 
| db.m4.10xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.m4.4xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.m4.2xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.m4.xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.m4.large | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 

**db.m3 – general-purpose instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m3.2xlarge | No | No |  Deprecated  | Yes |  Deprecated  | Deprecated | 
| db.m3.xlarge | No | No |  Deprecated  | Yes |  Deprecated  | Deprecated | 
| db.m3.large | No | No |  Deprecated  | Yes |  Deprecated  | Deprecated | 
| db.m3.medium | No | No |  Deprecated  | Yes |  Deprecated  | Deprecated | 

## Supported DB engines for memory-optimized instance classes
<a name="mem-opt-inst-classes"></a>

The following tables show the supported databases and database versions for the memory-optimized instance classes.

**db.z1d – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.z1d.12xlarge | No | No | Yes | No |  Yes  | No | 
| db.z1d.6xlarge | No | No | Yes | No |  Yes  | No | 
| db.z1d.3xlarge | No | No | Yes | No |  Yes  | No | 
| db.z1d.2xlarge | No | No | Yes | No |  Yes  | No | 
| db.z1d.xlarge | No | No | Yes | No |  Yes  | No | 
| db.z1d.large | No | No | Yes | No |  Yes  | No | 

**db.x2g – memory-optimized instance classes powered by AWS Graviton2 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x2g.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.x2g.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.x2g.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.x2g.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.x2g.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.x2g.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.x2g.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 

**db.x2idn – memory-optimized instance classes powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x2idn.32xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | Enterprise Edition only | PostgreSQL 15 versions, 14.6, and 13.9 | 
| db.x2idn.24xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | Enterprise Edition only | PostgreSQL 15 versions, 14.6, and 13.9 | 
| db.x2idn.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | Enterprise Edition only | PostgreSQL 15 versions, 14.6, and 13.9 | 
| db.x2idn.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.x2iedn – memory-optimized instance classes with local NVMe-based SSDs, powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x2iedn.32xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Enterprise and Standard Editions only, SQL Server 2014 12.00 and higher | MySQL 8.4 and 8.0 | Enterprise Edition only | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.x2iedn.24xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Enterprise and Standard Editions only, SQL Server 2014 12.00 and higher | MySQL 8.4 and 8.0 | Enterprise Edition only | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.x2iedn.16xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Enterprise and Standard Editions only, SQL Server 2014 12.00 and higher | MySQL 8.4 and 8.0 | Enterprise Edition only | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.x2iedn.8xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Enterprise and Standard Editions only, SQL Server 2014 12.00 and higher | MySQL 8.4 and 8.0 | Enterprise Edition only | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.x2iedn.4xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Enterprise and Standard Editions only, SQL Server 2014 12.00 and higher | MySQL 8.4 and 8.0 | Enterprise Edition and Standard Edition 2 (SE2) | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.x2iedn.2xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Enterprise and Standard Editions only, SQL Server 2014 12.00 and higher | MySQL 8.4 and 8.0 | Enterprise Edition and Standard Edition 2 (SE2) | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.x2iedn.xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Enterprise and Standard Editions only, SQL Server 2014 12.00 and higher | MySQL 8.4 and 8.0 | Enterprise Edition and Standard Edition 2 (SE2) | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.x2iedn.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.x2iezn – memory-optimized instance classes powered by 2nd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x2iezn.metal | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.x2iezn.8xlarge | No | No | No | No | Enterprise Edition only | No | 
| db.x2iezn.6xlarge | No | No | No | No | Enterprise Edition only | No | 
| db.x2iezn.4xlarge | No | No | No | No | Enterprise Edition and Standard Edition 2 (SE2) | No | 
| db.x2iezn.2xlarge | No | No | No | No | Enterprise Edition and Standard Edition 2 (SE2) | No | 

**db.x1e – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x1e.32xlarge | No | No | Deprecated | No | Deprecated | No | 
| db.x1e.16xlarge | No | No | Deprecated | No | Deprecated | No | 
| db.x1e.8xlarge | No | No | Deprecated | No | Deprecated | No | 
| db.x1e.4xlarge | No | No | Deprecated | No | Deprecated | No | 
| db.x1e.2xlarge | No | No | Deprecated | No | Deprecated | No | 
| db.x1e.xlarge | No | No | Deprecated | No | Deprecated | No | 

**db.x1 – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x1.32xlarge | No | No | Deprecated | No | Deprecated | No | 
| db.x1.16xlarge | No | No | Deprecated | No | Deprecated | No | 

**db.r8g – memory-optimized instance classes powered by AWS Graviton4 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r8g.48xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.24xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.16xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.12xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.8xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.4xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.2xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.xlarge | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r8g.large | No | MariaDB 11.8.3 and higher, 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher | No | MySQL 8.0.32 and higher | No | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 

**db.r8i – memory-optimized instance classes powered by Intel Xeon 6 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r8i.48xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.r8i.24xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.r8i.16xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.r8i.12xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.r8i.8xlarge | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.r8i.4xlarge | No | No | No | No | BYOL only, all editions | No | 
| db.r8i.2xlarge | No | No | No | No | BYOL only, all editions | No | 
| db.r8i.xlarge | No | No | No | No | BYOL only, all editions | No | 
| db.r8i.large | No | No | No | No | BYOL only, all editions | No | 
| db.r8i.metal-96xl | No | No | No | No | BYOL only, Enterprise Edition only | No | 
| db.r8i.metal-48xl | No | No | No | No | BYOL only, Enterprise Edition only | No | 

**db.r7i – memory-optimized instance classes preconfigured for high memory, storage, and I/O**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r7i.8xlarge.tpc2.mem3x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.8xlarge.tpc2.mem2x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.6xlarge.tpc2.mem4x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.6xlarge.tpc2.mem2x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.4xlarge.tpc2.mem4x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.4xlarge.tpc2.mem3x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.4xlarge.tpc2.mem2x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.3xlarge.tpc2.mem4x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.2xlarge.tpc2.mem8x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.2xlarge.tpc2.mem4x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.xlarge.tpc2.mem4x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 
| db.r7i.xlarge.tpc2.mem2x | No | No | No | No | BYOL only, Enterprise Edition and Standard Edition 2 | No | 

**db.r7i – memory-optimized instance classes powered by 4th generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r7i.48xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.24xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.16xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.12xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.8xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.4xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.2xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.xlarge | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.large | Db2 11.5 | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.0.32 and higher | BYOL only, all editions | PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher | 
| db.r7i.metal-48xl | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 
| db.r7i.metal-24xl | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.r7g – memory-optimized instance classes powered by AWS Graviton3 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r7g.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.r7g.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.r7g.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.r7g.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.r7g.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.r7g.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 
| db.r7g.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.4 and higher 13 versions | 

**db.r6g – memory-optimized instance classes powered by AWS Graviton2 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6g.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r6g.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r6g.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r6g.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r6g.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r6g.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r6g.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 

**db.r6gd – memory-optimized instance classes powered by AWS Graviton2 processors** 


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6gd.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 

**db.r6id – memory-optimized instance classes powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6id.32xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.24xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.16xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.12xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.8xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.4xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.2xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.large | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.r6idn – memory-optimized instance classes powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6idn.32xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6idn.24xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6idn.16xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6idn.12xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6idn.8xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6idn.4xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6idn.2xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6idn.xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | No |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 

**db.r6in – memory-optimized instance classes powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6in.32xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.24xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.16xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.12xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.8xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.4xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.2xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.xlarge | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.large | Yes |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.3 and higher 14 versions, 13.7 and higher 13 versions, 12.11 and higher 12 versions, and 11.16 and higher 11 versions  | 
| db.r6in.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.r6i – memory-optimized instance classes preconfigured for high memory, storage, and I/O**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6i.8xlarge.tpc2.mem4x | No | No | No | No |  Enterprise Edition only  | No | 
| db.r6i.8xlarge.tpc2.mem3x | No | No | No | No |  Enterprise Edition only  | No | 
| db.r6i.6xlarge.tpc2.mem4x | No | No | No | No |  Enterprise Edition only  | No | 
| db.r6i.4xlarge.tpc2.mem4x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.4xlarge.tpc2.mem3x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.4xlarge.tpc2.mem2x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.2xlarge.tpc2.mem8x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.2xlarge.tpc2.mem4x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.2xlarge.tpc1.mem2x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.xlarge.tpc2.mem4x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.xlarge.tpc2.mem2x | No | No | No | No |  EE and SE2 BYOL  | No | 
| db.r6i.large.tpc1.mem2x | No | No | No | No |  EE and SE2 BYOL  | No | 

**db.r6i – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6i.32xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.24xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.16xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.12xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.8xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.4xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.2xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.xlarge | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.large | Yes | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 |  Yes  | All PostgreSQL 17, 16, 15, and 14 versions, 13.4 and higher 13 versions, 12.8 and higher 12 versions, 11.13 and higher 11 versions, and 10.21 and higher 10 versions | 
| db.r6i.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

**db.r5d – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5d.24xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r5d.16xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r5d.12xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r5d.8xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r5d.4xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r5d.2xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r5d.xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r5d.large | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 

**db.r5b – memory-optimized instance classes preconfigured for high memory, storage, and I/O**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5b.8xlarge.tpc2.mem3x | No | No | No | No | Yes | No | 
| db.r5b.6xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5b.4xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5b.4xlarge.tpc2.mem3x | No | No | No | No | Yes | No | 
| db.r5b.4xlarge.tpc2.mem2x | No | No | No | No | Yes | No | 
| db.r5b.2xlarge.tpc2.mem8x | No | No | No | No | Yes | No | 
| db.r5b.2xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5b.2xlarge.tpc1.mem2x | No | No | No | No | Yes | No | 
| db.r5b.xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5b.xlarge.tpc2.mem2x | No | No | No | No | Yes | No | 
| db.r5b.large.tpc1.mem2x | No | No | No | No | Yes | No | 

**db.r5b – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5b.24xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r5b.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r5b.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r5b.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | >Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r5b.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r5b.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r5b.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.r5b.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | Yes | MySQL 8.4 and 8.0 | Yes | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 

**db.r5 – memory-optimized instance classes preconfigured for high memory, storage, and I/O**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5.12xlarge.tpc2.mem2x | No | No | No | No | Yes | No | 
| db.r5.8xlarge.tpc2.mem3x | No | No | No | No | Yes | No | 
| db.r5.6xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5.4xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5.4xlarge.tpc2.mem3x | No | No | No | No | Yes | No | 
| db.r5.4xlarge.tpc2.mem2x  | No | No | No | No | Yes | No | 
| db.r5.2xlarge.tpc2.mem8x | No | No | No | No | Yes | No | 
| db.r5.2xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5.2xlarge.tpc1.mem2x | No | No | No | No | Yes | No | 
| db.r5.xlarge.tpc2.mem4x | No | No | No | No | Yes | No | 
| db.r5.xlarge.tpc2.mem2x | No | No | No | No | Yes | No | 
| db.r5.large.tpc1.mem2x | No | No | No | No | Yes | No | 

**db.r5 – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5.24xlarge | No | Yes | Yes | Yes |  Yes  |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.r5.16xlarge | No | Yes | Yes | Yes | Yes |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.r5.12xlarge | No | Yes | Yes | Yes |  Yes  |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.r5.8xlarge | No | Yes | Yes | Yes |  Yes  |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.r5.4xlarge | No | Yes | Yes | Yes |  Yes  |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.r5.2xlarge | No | Yes | Yes | Yes |  Yes  |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.r5.xlarge | No | Yes | Yes | Yes |  Yes  |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 
| db.r5.large | No | Yes | Yes | Yes |  Yes  |  All PostgreSQL 17, 16, 15, 14, 13, 12, and 11 versions; 10.17 and higher 10 versions; and 9.6.22 and higher 9 versions  | 

**db.r4 – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r4.16xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.r4.8xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.r4.4xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.r4.2xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.r4.xlarge | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 
| db.r4.large | No | Deprecated |  Deprecated  | Deprecated | Deprecated | Deprecated | 

**db.r3 – memory-optimized instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r3.8xlarge\$1\$1 | No | All MariaDB 10.6, 10.5, 10.4, and 10.3 versions |  Deprecated  | Yes |  Deprecated  | Deprecated | 
| db.r3.4xlarge | No | All MariaDB 10.6, 10.5, 10.4, and 10.3 versions |  Deprecated  | Yes |  Deprecated  | Deprecated | 
| db.r3.2xlarge | No | All MariaDB 10.6, 10.5, 10.4, and 10.3 versions |  Deprecated  | Yes |  Deprecated  | Deprecated | 
| db.r3.xlarge | No | All MariaDB 10.6, 10.5, 10.4, and 10.3 versions |  Deprecated  | Yes |  Deprecated  | Deprecated | 
| db.r3.large | No | All MariaDB 10.6, 10.5, 10.4, and 10.3 versions |  Deprecated  | Yes |  Deprecated  | Deprecated | 

## Supported DB engines for compute-optimized instance classes
<a name="compute-opt-inst-classes"></a>

The following tables show the supported databases and database versions for the compute-optimized instance classes.

**db.c6gd – compute-optimized instance classes (for Multi-AZ DB cluster deployments only)**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.c6gd.16xlarge | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 
| db.c6gd.12xlarge | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 
| db.c6gd.8xlarge | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 
| db.c6gd.4xlarge | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 
| db.c6gd.2xlarge | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 
| db.c6gd.xlarge | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 
| db.c6gd.large | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 
| db.c6gd.medium | No | No | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, and 15 versions; 14.5 and higher 14 versions; 13.4 and 13.7 and higher 13 versions | 

## Supported DB engines for burstable-performance instance classes
<a name="burstable-inst-classes"></a>

The following tables show the supported databases and database versions for the burstable-performance instance classes.

**db.t4g – burstable-performance instance classes powered by AWS Graviton2 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.t4g.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.t4g.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.t4g.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.t4g.medium | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.t4g.small | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 
| db.t4g.micro | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions | 

**db.t3 – burstable-performance instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.t3.2xlarge | Yes | Yes | Yes | Yes | Yes | All PostgreSQL 17, 16, 15, 14, 13, 12, 11, and 10 versions; and 9.6.22 and higher 9 versions | 
| db.t3.xlarge | Yes | Yes | Yes | Yes |  Yes  | All PostgreSQL 17, 16, 15, 14, 13, 12, 11, and 10 versions; and 9.6.22 and higher 9 versions | 
| db.t3.large | Yes | Yes | Yes | Yes | Yes | All PostgreSQL 17, 16, 15, 14, 13, 12, 11, and 10 versions; and 9.6.22 and higher 9 versions | 
| db.t3.medium | Yes | Yes | Yes | Yes |  Yes  | All PostgreSQL 17, 16, 15, 14, 13, 12, 11, and 10 versions; and 9.6.22 and higher 9 versions | 
| db.t3.small | Yes | Yes | Yes | Yes | Yes | All PostgreSQL 17, 16, 15, 14, 13, 12, 11, and 10 versions; and 9.6.22 and higher 9 versions | 
| db.t3.micro | No | Yes | Yes | Yes | Only on Oracle Database 12c Release 1 (12.1.0.2), which is deprecated | All PostgreSQL 17, 16, 15, 14, 13, 12, 11, and 10 versions; and 9.6.22 and higher 9 versions | 

**db.t2 – burstable-performance instance classes**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.t2.2xlarge | No | Deprecated | No | Deprecated |  Deprecated  | Deprecated | 
| db.t2.xlarge | No | Deprecated | No | Deprecated |  Deprecated  | Deprecated | 
| db.t2.large | No | Deprecated |  Deprecated  | Deprecated |  Deprecated  | Deprecated | 
| db.t2.medium | No | Deprecated |  Deprecated  | Deprecated |  Deprecated  | Deprecated | 
| db.t2.small | No | Deprecated |  Deprecated  | Deprecated |  Deprecated  | Deprecated | 
| db.t2.micro | No | Deprecated |  Deprecated  | Deprecated |  Deprecated  | Deprecated | 

## Supported DB engines for Optimized Reads instance classes
<a name="read-opt-inst-classes"></a>

The following tables show the supported databases and database versions for the Optimized Reads instance classes.

**db.m8gd – memory-optimized instance classes that support Optimized Reads and are powered by AWS Graviton4 processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m8gd.48xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No | MySQL 8.4 and 8.0 | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.24xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.16xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.12xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.8xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.4xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.2xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.m8gd.large | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 

**db.r8gd – memory-optimized instance classes that support Optimized Reads and are powered by AWS Graviton4 processors** 


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r8gd.48xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No | MySQL 8.4 and 8.0 | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.24xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.16xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.12xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.8xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.4xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.2xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.xlarge | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 
| db.r8gd.large | No | MariaDB 10.5.27 and higher, 10.6.19 and higher, 10.11.9 and higher, 11.4.3 and higher, 11.8.3 and higher | No |  MySQL 8.0.40 and higher, 8.4.3 and higher  | No |  PostgreSQL 13.18 and higher, 14.17 and higher, 15.10 and higher, 16.6 and higher, 17.2 and higher, 18.1 and higher  | 

**db.r6gd – memory-optimized instance classes that support Optimized Reads and are powered by AWS Graviton2 processors** 


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6gd.16xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.12xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.8xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.4xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.2xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.xlarge | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 
| db.r6gd.large | No | MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4 | No | MySQL 8.4 and 8.0 | No | All PostgreSQL 17, 16 and 15 versions, 14.5 and higher 14 versions, 13.7 and higher 13 versions, and 13.4 | 

**db.r6id – memory-optimized instance classes that support Optimized Reads and are powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | Db2 | MariaDB | Microsoft SQL Server | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6id.32xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.24xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.16xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.12xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.8xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | EE and BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.4xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.2xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.xlarge | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.large | No |  MariaDB 11.8, 11.4, 10.11, 10.6, 10.5, and 10.4  | No | MySQL 8.4 and 8.0 | BYOL only |  All PostgreSQL 17, 16, and 15 versions, 14.5 and higher 14 versions, and 13.7 and higher 13 versions  | 
| db.r6id.metal | No | No | No | No |  BYOL only, Enterprise Edition only  | No | 

# Determining DB instance class support in AWS Regions
<a name="Concepts.DBInstanceClass.RegionSupport"></a>

To determine the DB instance classes supported by each DB engine in a specific AWS Region, you can take one of several approaches. You can use the AWS Management Console, the [Amazon RDS Pricing](https://aws.amazon.com/rds/pricing/) page, or the [describe-orderable-db-instance-options](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-orderable-db-instance-options.html) command for the AWS Command Line Interface (AWS CLI).

**Note**  
When you perform operations with the AWS Management Console, it automatically shows the supported DB instance classes for a specific DB engine, DB engine version, and AWS Region. Examples of the operations that you can perform include creating and modifying a DB instance. 

**Contents**
+ [

## Using the Amazon RDS pricing page to determine DB instance class support in AWS Regions
](#Concepts.DBInstanceClass.RegionSupport.PricingPage)
+ [

## Using the AWS CLI to determine DB instance class support in AWS Regions
](#Concepts.DBInstanceClass.RegionSupport.CLI)
  + [

### Listing the DB instance classes that are supported by a specific DB engine version in an AWS Region
](#Concepts.DBInstanceClass.RegionSupport.CLI.Example1)
  + [

### Listing the DB engine versions that support a specific DB instance class in an AWS Region
](#Concepts.DBInstanceClass.RegionSupport.CLI.Example2)
  + [

### Listing AWS Regions that support a specific DB engine and instance class
](#Concepts.DBInstanceClass.RegionSupport.CLI.Example3)

## Using the Amazon RDS pricing page to determine DB instance class support in AWS Regions
<a name="Concepts.DBInstanceClass.RegionSupport.PricingPage"></a>

You can use the [Amazon RDS Pricing](https://aws.amazon.com/rds/pricing/) page to determine the DB instance classes supported by each DB engine in a specific AWS Region. 

**To use the pricing page to determine the DB instance classes supported by each engine in a Region**

1. Go to [Amazon RDS Pricing](https://aws.amazon.com/rds/pricing/).

1. In the **AWS Pricing Calculator for Amazon RDS** section, choose **Create your custom estimate now**.

1. In **Choose a Region**, choose an AWS Region.

1. In **Find a Service**, enter **Amazon RDS**.

1. Choose **Configure** for your configuration option and DB engine.

1. Use the section for compatible instances to view the supported DB instance classes.

1. (Optional) Choose other options in the calculator, and then choose **Save and view summary** or **Save and add service**.

## Using the AWS CLI to determine DB instance class support in AWS Regions
<a name="Concepts.DBInstanceClass.RegionSupport.CLI"></a>

You can use the AWS CLI to determine which DB instance classes are supported for specific DB engines and DB engine versions in an AWS Region. The following table shows the valid DB engine values.


****  

| Engine names | Engine values in CLI commands | More information about versions | 
| --- | --- | --- | 
|  Db2  |  `db2-ae` `db2-se`  |  [Db2 on Amazon RDS versions](Db2.Concepts.VersionMgmt.md)  | 
|  MariaDB  |  `mariadb`  |  [MariaDB on Amazon RDS versions](MariaDB.Concepts.VersionMgmt.md)  | 
|  Microsoft SQL Server  |  `sqlserver-ee` `sqlserver-se` `sqlserver-ex` `sqlserver-web`  |  [Microsoft SQL Server versions on Amazon RDS](SQLServer.Concepts.General.VersionSupport.md)  | 
|  MySQL  |  `mysql`  |  [MySQL on Amazon RDS versions](MySQL.Concepts.VersionMgmt.md)  | 
|  Oracle  |  `oracle-ee` `oracle-se2`  |  [https://docs.aws.amazon.com/AmazonRDS/latest/OracleReleaseNotes/Welcome.html](https://docs.aws.amazon.com/AmazonRDS/latest/OracleReleaseNotes/Welcome.html)  | 
|  PostgreSQL  |  `postgres`  |  [Available PostgreSQL database versions](PostgreSQL.Concepts.General.DBVersions.md)  | 

For information about AWS Region names, see [AWS RegionsAvailability Zones](Concepts.RegionsAndAvailabilityZones.md#Concepts.RegionsAndAvailabilityZones.Regions).

The following examples demonstrate how to determine DB instance class support in an AWS Region using the [describe-orderable-db-instance-options](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-orderable-db-instance-options.html) AWS CLI command.

**Note**  
To limit the output, the following examples show results only for the General Purpose SSD (`gp2`) storage type. If necessary, you can change the storage type to General Purpose SSD (`gp3`), Provisioned IOPS (`io1`), Provisioned IOPS Block Express (`io2`), or magnetic (`standard`) in the commands.

**Topics**
+ [

### Listing the DB instance classes that are supported by a specific DB engine version in an AWS Region
](#Concepts.DBInstanceClass.RegionSupport.CLI.Example1)
+ [

### Listing the DB engine versions that support a specific DB instance class in an AWS Region
](#Concepts.DBInstanceClass.RegionSupport.CLI.Example2)
+ [

### Listing AWS Regions that support a specific DB engine and instance class
](#Concepts.DBInstanceClass.RegionSupport.CLI.Example3)

### Listing the DB instance classes that are supported by a specific DB engine version in an AWS Region
<a name="Concepts.DBInstanceClass.RegionSupport.CLI.Example1"></a>

To list the DB instance classes that are supported by a specific DB engine version in an AWS Region, run the following command.

For Linux, macOS, or Unix:

```
aws rds describe-orderable-db-instance-options --engine engine --engine-version version \
    --query "*[].{DBInstanceClass:DBInstanceClass,StorageType:StorageType}|[?StorageType=='gp2']|[].{DBInstanceClass:DBInstanceClass}" \
    --output text \
    --region region
```

For Windows:

```
aws rds describe-orderable-db-instance-options --engine engine --engine-version version ^
    --query "*[].{DBInstanceClass:DBInstanceClass,StorageType:StorageType}|[?StorageType=='gp2']|[].{DBInstanceClass:DBInstanceClass}" ^
    --output text ^
    --region region
```

For example, the following command lists the supported DB instance classes for version 13.6 of the RDS for PostgreSQL DB engine in US East (N. Virginia).

For Linux, macOS, or Unix:

```
aws rds describe-orderable-db-instance-options --engine postgres --engine-version 15.4 \
    --query "*[].{DBInstanceClass:DBInstanceClass,StorageType:StorageType}|[?StorageType=='gp2']|[].{DBInstanceClass:DBInstanceClass}" \
    --output text \
    --region us-east-1
```

For Windows:

```
aws rds describe-orderable-db-instance-options --engine postgres --engine-version 15.4 ^
    --query "*[].{DBInstanceClass:DBInstanceClass,StorageType:StorageType}|[?StorageType=='gp2']|[].{DBInstanceClass:DBInstanceClass}" ^
    --output text ^
    --region us-east-1
```

### Listing the DB engine versions that support a specific DB instance class in an AWS Region
<a name="Concepts.DBInstanceClass.RegionSupport.CLI.Example2"></a>

To list the DB engine versions that support a specific DB instance class in an AWS Region, run the following command.

For Linux, macOS, or Unix:

```
aws rds describe-orderable-db-instance-options --engine engine --db-instance-class DB_instance_class \
    --query "*[].{EngineVersion:EngineVersion,StorageType:StorageType}|[?StorageType=='gp2']|[].{EngineVersion:EngineVersion}" \
    --output text \
    --region region
```

For Windows:

```
aws rds describe-orderable-db-instance-options --engine engine --db-instance-class DB_instance_class ^
    --query "*[].{EngineVersion:EngineVersion,StorageType:StorageType}|[?StorageType=='gp2']|[].{EngineVersion:EngineVersion}" ^
    --output text ^
    --region region
```

For example, the following command lists the DB engine versions of the RDS for PostgreSQL DB engine that support the db.r5.large DB instance class in US East (N. Virginia).

For Linux, macOS, or Unix:

```
aws rds describe-orderable-db-instance-options --engine postgres --db-instance-class db.m7g.large \
    --query "*[].{EngineVersion:EngineVersion,StorageType:StorageType}|[?StorageType=='gp2']|[].{EngineVersion:EngineVersion}" \
    --output text \
    --region us-east-1
```

For Windows:

```
aws rds describe-orderable-db-instance-options --engine postgres --db-instance-class db.m7g.large ^
    --query "*[].{EngineVersion:EngineVersion,StorageType:StorageType}|[?StorageType=='gp2']|[].{EngineVersion:EngineVersion}" ^
    --output text ^
    --region us-east-1
```

### Listing AWS Regions that support a specific DB engine and instance class
<a name="Concepts.DBInstanceClass.RegionSupport.CLI.Example3"></a>

The following bash script lists all the AWS Regions that support the specified combination of DB engine and instance class.

```
#!/usr/bin/env bash
# Usage: check_region_support.sh <db-engine> <db-instance-class>

if [ $# -ne 2 ]; then
  echo "Usage: $0 <db-engine> <db-instance-class>"
  exit 1
fi
ENGINE="$1"
INSTANCE_CLASS="$2"
REGIONS=$(aws ec2 describe-regions --query "Regions[].RegionName" --output text)
for region in $REGIONS; do
  supported_count=$(aws rds describe-orderable-db-instance-options \
    --region "$region" \
    --engine "$ENGINE" \
    --db-instance-class "$INSTANCE_CLASS" \
    --query 'length(OrderableDBInstanceOptions)' \
    --output text 2>/dev/null || echo "0")
  if [ "$supported_count" -gt 0 ]; then
    echo "$region supports $INSTANCE_CLASS for $ENGINE."
  else
    echo "$region doesn't support $INSTANCE_CLASS for $ENGINE."
  fi
done
```

The following sample output checks Region support for RDS for MySQL using the db.r8g.large instance class.

```
./check_region_support.sh mysql db.r8g.large
ap-south-1 doesn't support db.r8g.large for mysql.
eu-north-1 doesn't support db.r8g.large for mysql.
eu-west-3 doesn't support db.r8g.large for mysql.
eu-west-2 doesn't support db.r8g.large for mysql.
eu-west-1 doesn't support db.r8g.large for mysql.
ap-northeast-3 doesn't support db.r8g.large for mysql.
ap-northeast-2 doesn't support db.r8g.large for mysql.
ap-northeast-1 doesn't support db.r8g.large for mysql.
ca-central-1 doesn't support db.r8g.large for mysql.
sa-east-1 doesn't support db.r8g.large for mysql.
ap-southeast-1 doesn't support db.r8g.large for mysql.
ap-southeast-2 doesn't support db.r8g.large for mysql.
eu-central-1 supports db.r8g.large for mysql.
us-east-1 supports db.r8g.large for mysql.
us-east-2 supports db.r8g.large for mysql.
us-west-1 doesn't support db.r8g.large for mysql.
us-west-2 supports db.r8g.large for mysql.
```

## Changing your DB instance class
<a name="Concepts.DBInstanceClass.Changing"></a>

You can change the CPU and memory available to a DB instance by changing its DB instance class. To change the DB instance class, modify your DB instance by following the instructions in [Modifying an Amazon RDS DB instance](Overview.DBInstance.Modifying.md). 

# Configuring the processor for a DB instance class in RDS for Oracle
<a name="USER_ConfigureProcessor"></a>

Amazon RDS DB instance classes support Intel Hyper-Threading Technology, which enables multiple threads to run concurrently on a single Intel Xeon CPU core. Each thread is represented as a virtual CPU (vCPU) on the DB instance. A DB instance has a default number of CPU cores, which varies according to DB instance class. For example, a db.m4.xlarge DB instance class has two CPU cores and two threads per core by default—four vCPUs in total.

**Note**  
Each vCPU is a hyperthread of an Intel Xeon CPU core.

**Topics**
+ [

## Overview of processor configuration for RDS for Oracle
](#USER_ConfigureProcessor.Overview)
+ [

## DB instance classes that support processor configuration
](#USER_ConfigureProcessor.CPUOptionsDBInstanceClass)
+ [

## Setting the CPU cores and threads per CPU core for a DB instance class
](#USER_ConfigureProcessor.SettingCPUOptions)

## Overview of processor configuration for RDS for Oracle
<a name="USER_ConfigureProcessor.Overview"></a>

When you use RDS for Oracle, you can usually find a DB instance class that has a combination of memory and number of vCPUs to suit your workloads. However, you can also specify the following processor features to optimize your RDS for Oracle DB instance for specific workloads or business needs:
+ **Number of CPU cores** – You can customize the number of CPU cores for the DB instance. You might do this to potentially optimize the licensing costs of your software with a DB instance that has sufficient amounts of RAM for memory-intensive workloads but fewer CPU cores.
+ **Threads per core** – You can disable Intel Hyper-Threading Technology by specifying a single thread per CPU core. You might do this for certain workloads, such as high-performance computing (HPC) workloads.

You can control the number of CPU cores and threads for each core separately. You can set one or both in a request. After a setting is associated with a DB instance, the setting persists until you change it.

The processor settings for a DB instance are associated with snapshots of the DB instance. When a snapshot is restored, its restored DB instance uses the processor feature settings used when the snapshot was taken.

If you modify the DB instance class for a DB instance with nondefault processor settings, either specify default processor settings or explicitly specify processor settings at modification. This requirement ensures that you are aware of the third-party licensing costs that might be incurred when you modify the DB instance.

There is no additional or reduced charge for specifying processor features on an RDS for Oracle DB instance. You're charged the same as for DB instances that are launched with default CPU configurations.

## DB instance classes that support processor configuration
<a name="USER_ConfigureProcessor.CPUOptionsDBInstanceClass"></a>

You can configure the number of CPU cores and threads per core only when the following conditions are met: 
+ You're configuring an RDS for Oracle DB instance. For information about the DB instance classes supported by different Oracle Database editions, see [RDS for Oracle DB instance classes](Oracle.Concepts.InstanceClasses.md).
+ Your DB instance is using the Bring Your Own License (BYOL) licensing option of RDS for Oracle. For more information about Oracle licensing options, see [RDS for Oracle licensing options](Oracle.Concepts.Licensing.md).
+ Your DB instance doesn't belong to one of the db.r5 or db.r5b instance classes that have predefined processor configurations. These instance classes have names in the form db.r5.*instance\$1size*.tpc*threads\$1per\$1core*.mem*ratio* or db.r5b.*instance\$1size*.tpc*threads\$1per\$1core*.mem*ratio*. For example, db.r5b.xlarge.tpc2.mem4x is preconfigured with 2 threads per core (tpc2) and 4x as much memory as the standard db.r5b.xlarge instance class. You can't configure the processor features of these optimized instance classes. For more information, see [Supported RDS for Oracle DB instance classes](Oracle.Concepts.InstanceClasses.md#Oracle.Concepts.InstanceClasses.Supported).

You can use the following AWS CLI command to show the default vCPUs, cores, threads per core, and valid numbers of cores for an instance class. Replace `r7i.48xlarge` in the sample command with the name of your instance class.

```
aws ec2 describe-instance-types \
    --instance-types r7i.48xlarge \
    --query '{
        DefaultVCPUs: InstanceTypes[0].VCpuInfo.DefaultVCpus,
        DefaultCores: InstanceTypes[0].VCpuInfo.DefaultCores,
        DefaultThreadsPerCore: InstanceTypes[0].VCpuInfo.DefaultThreadsPerCore,
        ValidCores: InstanceTypes[0].VCpuInfo.ValidCores
    }' \
    --output json
```

In the following table, you can find the DB instance classes that support setting a number of CPU cores and CPU threads per core. You can also find the default value and the valid values for the number of CPU cores and CPU threads per core for each DB instance class.


****  

| DB instance class | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core | 
| --- | --- | --- | --- | --- | --- | 
| db.m6i – memory-optimized instance classes | 
|  db.m6i.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.m6i.xlarge  |  4  |  2  |  2  |  2  |  1, 2  | 
|  db.m6i.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.m6i.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.m6i.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.m6i.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.m6i.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
|  db.m6i.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.m6i.24xlarge  |  96  |  48  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
|  db.m6i.32xlarge  |  128  |  64  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64  |  1, 2  | 
| db.m5 – general-purpose instance classes | 
|  db.m5.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.m5.xlarge  |  4  |  2  |  2  |  2  |  1, 2  | 
|  db.m5.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.m5.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.m5.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.m5.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
|  db.m5.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.m5.24xlarge  |  96  |  48  |  2  |  4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
| db.m5d – general-purpose instance classes | 
|  db.m5d.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.m5d.xlarge  |  4  |  2  |  2  |  2  |  1, 2  | 
|  db.m5d.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.m5d.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.m5d.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.m5d.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
|  db.m5d.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.m5d.24xlarge  |  96  |  48  |  2  |  4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
| db.m4 – general-purpose instance classes | 
|  db.m4.10xlarge  |  40  |  20  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20  |  1, 2  | 
|  db.m4.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
| db.r7i – memory-optimized instance classes | 
|  db.r7i.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.r7i.xlarge  |  4  |  2  |  2  |  1, 2  |  1, 2  | 
|  db.r7i.2xlarge  |  8  |  4  |  2  |  1, 2, 3, 4  |  1, 2  | 
|  db.r7i.4xlarge  |  16  |  8  |  2  |  1, 2, 3, 4, 5, 6, 7, 8  |  1, 2  | 
|  db.r7i.8xlarge  |  32  |  16  |  2  |  1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16  |  1, 2  | 
|  db.r7i.12xlarge  |  48  |  24  |  2  |  1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24  |  1, 2  | 
|  db.r7i.16xlarge  |  64  |  32  |  2  |  1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32  |  1, 2  | 
|  db.r7i.24xlarge  |  96  |  48  |  2  |  1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48  |  1, 2  | 
|  db.r7i.48xlarge  |  192  |  96  |  2  |  4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, 96  |  1, 2  | 
| db.r6i – memory-optimized instance classes | 
|  db.r6i.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.r6i.xlarge  |  4  |  2  |  2  |  1, 2  |  1, 2  | 
|  db.r6i.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.r6i.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.r6i.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.r6i.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
|  db.r6i.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.r6i.24xlarge  |  96  |  48  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
|  db.r6i.32xlarge  |  128  |  64  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64  |  1, 2  | 
| db.r5 – memory-optimized instance classes | 
|  db.r5.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.r5.xlarge  |  4  |  2  |  2  |  2  |  1, 2  | 
|  db.r5.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.r5.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.r5.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.r5.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
|  db.r5.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.r5.24xlarge  |  96  |  48  |  2  |  4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
| db.r5 – memory-optimized instance classes | 
|  db.r5b.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.r5b.xlarge  |  4  |  2  |  2  |  2  |  1, 2  | 
|  db.r5b.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.r5b.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.r5b.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.r5b.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
|  db.r5b.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.r5b.24xlarge  |  96  |  48  |  2  |  4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
| db.r5d – memory-optimized instance classes | 
|  db.r5d.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.r5d.xlarge  |  4  |  2  |  2  |  2  |  1, 2  | 
|  db.r5d.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.r5d.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.r5d.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.r5d.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
|  db.r5d.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.r5d.24xlarge  |  96  |  48  |  2  |  4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
| db.r4 – memory-optimized instance classes | 
|  db.r4.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.r4.xlarge  |  4  |  2  |  2  |  1, 2  |  1, 2  | 
|  db.r4.2xlarge  |  8  |  4  |  2  |  1, 2, 3, 4  |  1, 2  | 
|  db.r4.4xlarge  |  16  |  8  |  2  |  1, 2, 3, 4, 5, 6, 7, 8  |  1, 2  | 
|  db.r4.8xlarge  |  32  |  16  |  2  |  1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16  |  1, 2  | 
|  db.r4.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
| db.r3 – memory-optimized instance classes | 
|  db.r3.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.r3.xlarge  |  4  |  2  |  2  |  1, 2  |  1, 2  | 
|  db.r3.2xlarge  |  8  |  4  |  2  |  1, 2, 3, 4  |  1, 2  | 
|  db.r3.4xlarge  |  16  |  8  |  2  |  1, 2, 3, 4, 5, 6, 7, 8  |  1, 2  | 
|  db.r3.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
| db.x2idn – memory-optimized instance classes | 
|  db.x2idn.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.x2idn.24xlarge  |  96  |  48  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
|  db.x2idn.32xlarge  |  128  |  64  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64  |  1, 2  | 
| db.x2iedn – memory-optimized instance classes | 
|  db.x2iedn.xlarge  |  4  |  2  |  2  |  1, 2  |  1, 2  | 
|  db.x2iedn.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.x2iedn.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.x2iedn.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.x2iedn.16xlarge  |  64  |  32  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32  |  1, 2  | 
|  db.x2iedn.24xlarge  |  96  |  48  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48  |  1, 2  | 
|  db.x2iedn.32xlarge  |  128  |  64  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64  |  1, 2  | 
| db.x2iezn – memory-optimized instance classes | 
|  db.x2iezn.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.x2iezn.4xlarge  |  16  |  8  |  2  |  2, 4, 6, 8  |  1, 2  | 
|  db.x2iezn.6xlarge  |  24  |  12  |  2  |  2, 4, 6, 8, 10, 12  |  1, 2  | 
|  db.x2iezn.8xlarge  |  32  |  16  |  2  |  2, 4, 6, 8, 10, 12, 14, 16  |  1, 2  | 
|  db.x2iezn.12xlarge  |  48  |  24  |  2  |  2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 
| db.z1d – memory-optimized instance classes | 
|  db.z1d.large  |  2  |  1  |  2  |  1  |  1, 2  | 
|  db.z1d.xlarge  |  4  |  2  |  2  |  2  |  1, 2  | 
|  db.z1d.2xlarge  |  8  |  4  |  2  |  2, 4  |  1, 2  | 
|  db.z1d.3xlarge  |  12  |  6  |  2  |  2, 4, 6  |  1, 2  | 
|  db.z1d.6xlarge  |  24  |  12  |  2  |  2, 4, 6, 8, 10, 12  |  1, 2  | 
|  db.z1d.12xlarge  |  48  |  24  |  2  |  4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24  |  1, 2  | 

**Note**  
You can use AWS CloudTrail to monitor and audit changes to the process configuration of Amazon RDS for Oracle DB instances. For more information about using CloudTrail, see [Monitoring Amazon RDS API calls in AWS CloudTrail](logging-using-cloudtrail.md).

## Setting the CPU cores and threads per CPU core for a DB instance class
<a name="USER_ConfigureProcessor.SettingCPUOptions"></a>

You can configure the number of CPU cores and threads per core for the DB instance class when you perform the following operations:
+ [Creating an Amazon RDS DB instance](USER_CreateDBInstance.md)
+ [Modifying an Amazon RDS DB instance](Overview.DBInstance.Modifying.md)
+ [Restoring to a DB instance](USER_RestoreFromSnapshot.md)
+ [Restoring a DB instance to a specified time for Amazon RDS](USER_PIT.md)

**Note**  
When you modify a DB instance to configure the number of CPU cores or threads per core, there is a brief DB instance outage.

You can set the CPU cores and the threads per CPU core for a DB instance class using the AWS Management Console, the AWS CLI, or the RDS API.

### Console
<a name="USER_ConfigureProcessor.Console"></a>

When you are creating, modifying, or restoring a DB instance, you set the DB instance class in the AWS Management Console. The **Instance specifications** section shows options for the processor. The following image shows the processor features options.

![\[Configure processor options\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/vcpu-config.png)


Set the following options to the appropriate values for your DB instance class under **Processor features**:
+ **Core count – **Set the number of CPU cores using this option. The value must be equal to or less than the maximum number of CPU cores for the DB instance class.
+ **Threads per core** – Specify **2** to enable multiple threads per core, or specify **1** to disable multiple threads per core.

When you modify or restore a DB instance, you can also set the CPU cores and the threads per CPU core to the defaults for the instance class.

When you view the details for a DB instance in the console, you can view the processor information for its DB instance class on the **Configuration** tab. The following image shows a DB instance class with one CPU core and multiple threads per core enabled.

![\[View processor options\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/vcpu-view.png)


For Oracle DB instances, the processor information only appears for Bring Your Own License (BYOL) DB instances.

### AWS CLI
<a name="USER_ConfigureProcessor.CLI"></a>

You can set the processor features for a DB instance when you run one of the following AWS CLI commands:
+ [create-db-instance](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html)
+ [modify-db-instance](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-instance.html)
+ [restore-db-instance-from-db-snapshot](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-instance-from-db-snapshot.html)
+ [restore-db-instance-from-s3](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-instance-from-s3.html)
+ [restore-db-instance-to-point-in-time](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-instance-to-point-in-time.html)

To configure the processor of a DB instance class for a DB instance by using the AWS CLI, include the `--processor-features` option in the command. Specify the number of CPU cores with the `coreCount` feature name, and specify whether multiple threads per core are enabled with the `threadsPerCore` feature name. 

The option has the following syntax.

```
--processor-features "Name=coreCount,Value=<value>" "Name=threadsPerCore,Value=<value>"
```

The following are examples that configure the processor:

**Topics**
+ [

#### Setting the number of CPU cores for a DB instance
](#USER_ConfigureProcessor.CLI.Example1)
+ [

#### Setting the number of CPU cores and disabling multiple threads for a DB instance
](#USER_ConfigureProcessor.CLI.Example2)
+ [

#### Viewing the valid processor values for a DB instance class
](#USER_ConfigureProcessor.CLI.Example3)
+ [

#### Returning to default processor settings for a DB instance
](#USER_ConfigureProcessor.CLI.Example4)
+ [

#### Returning to the default number of CPU cores for a DB instance
](#USER_ConfigureProcessor.CLI.Example5)
+ [

#### Returning to the default number of threads per core for a DB instance
](#USER_ConfigureProcessor.CLI.Example6)

#### Setting the number of CPU cores for a DB instance
<a name="USER_ConfigureProcessor.CLI.Example1"></a>

**Example**  
The following example modifies `mydbinstance` by setting the number of CPU cores to 4. The changes are applied immediately by using `--apply-immediately`. If you want to apply the changes during the next scheduled maintenance window, omit the `--apply-immediately` option.   
For Linux, macOS, or Unix:  

```
aws rds modify-db-instance \
    --db-instance-identifier mydbinstance \
    --processor-features "Name=coreCount,Value=4" \
    --apply-immediately
```
For Windows:  

```
aws rds modify-db-instance ^
    --db-instance-identifier mydbinstance ^
    --processor-features "Name=coreCount,Value=4" ^
    --apply-immediately
```

#### Setting the number of CPU cores and disabling multiple threads for a DB instance
<a name="USER_ConfigureProcessor.CLI.Example2"></a>

**Example**  
The following example modifies `mydbinstance` by setting the number of CPU cores to `4` and disabling multiple threads per core. The changes are applied immediately by using `--apply-immediately`. If you want to apply the changes during the next scheduled maintenance window, omit the `--apply-immediately` option.  
For Linux, macOS, or Unix:  

```
aws rds modify-db-instance \
    --db-instance-identifier mydbinstance \
    --processor-features "Name=coreCount,Value=4" "Name=threadsPerCore,Value=1" \
    --apply-immediately
```
For Windows:  

```
aws rds modify-db-instance ^
    --db-instance-identifier mydbinstance ^
    --processor-features "Name=coreCount,Value=4" "Name=threadsPerCore,Value=1" ^
    --apply-immediately
```

#### Viewing the valid processor values for a DB instance class
<a name="USER_ConfigureProcessor.CLI.Example3"></a>

**Example**  
You can view the valid processor values for a particular DB instance class by running the [describe-orderable-db-instance-options](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-orderable-db-instance-options.html) command and specifying the instance class for the `--db-instance-class` option. For example, the output for the following command shows the processor options for the db.r3.large instance class.  

```
aws rds describe-orderable-db-instance-options --engine oracle-ee --db-instance-class db.r3.large
```
Following is sample output for the command in JSON format.  

```
    {
                "SupportsIops": true,
                "MaxIopsPerGib": 50.0,
                "LicenseModel": "bring-your-own-license",
                "DBInstanceClass": "db.r3.large",
                "SupportsIAMDatabaseAuthentication": false,
                "MinStorageSize": 100,
                "AvailabilityZones": [
                    {
                        "Name": "us-west-2a"
                    },
                    {
                        "Name": "us-west-2b"
                    },
                    {
                        "Name": "us-west-2c"
                    }
                ],
                "EngineVersion": "12.1.0.2.v2",
                "MaxStorageSize": 32768,
                "MinIopsPerGib": 1.0,
                "MaxIopsPerDbInstance": 40000,
                "ReadReplicaCapable": false,
                "AvailableProcessorFeatures": [
                    {
                        "Name": "coreCount",
                        "DefaultValue": "1",
                        "AllowedValues": "1"
                    },
                    {
                        "Name": "threadsPerCore",
                        "DefaultValue": "2",
                        "AllowedValues": "1,2"
                    }
                ],
                "SupportsEnhancedMonitoring": true,
                "SupportsPerformanceInsights": false,
                "MinIopsPerDbInstance": 1000,
                "StorageType": "io1",
                "Vpc": false,
                "SupportsStorageEncryption": true,
                "Engine": "oracle-ee",
                "MultiAZCapable": true
    }
```
In addition, you can run the following commands for DB instance class processor information:  
+ [describe-db-instances](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-instances.html) – Shows the processor information for the specified DB instance.
+ [describe-db-snapshots](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-snapshots.html) – Shows the processor information for the specified DB snapshot.
+ [describe-valid-db-instance-modifications](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-valid-db-instance-modifications.html) – Shows the valid modifications to the processor for the specified DB instance.
In the output of the preceding commands, the values for the processor features are not null only if the following conditions are met:  
+ You are using an RDS for Oracle DB instance.
+ Your RDS for Oracle DB instance supports changing processor values.
+ The current CPU core and thread settings are set to nondefault values.
If the preceding conditions aren't met, you can get the instance type using [describe-db-instances](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-db-instances.html). You can get the processor information for this instance type by running the EC2 operation [describe-instance-types](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-types.html).

#### Returning to default processor settings for a DB instance
<a name="USER_ConfigureProcessor.CLI.Example4"></a>

**Example**  
The following example modifies `mydbinstance` by returning its DB instance class to the default processor values for it. The changes are applied immediately by using `--apply-immediately`. If you want to apply the changes during the next scheduled maintenance window, omit the `--apply-immediately` option.   
For Linux, macOS, or Unix:  

```
aws rds modify-db-instance \
    --db-instance-identifier mydbinstance \    
    --use-default-processor-features \
    --apply-immediately
```
For Windows:  

```
aws rds modify-db-instance ^
    --db-instance-identifier mydbinstance ^
    --use-default-processor-features ^
    --apply-immediately
```

#### Returning to the default number of CPU cores for a DB instance
<a name="USER_ConfigureProcessor.CLI.Example5"></a>

**Example**  
The following example modifies `mydbinstance` by returning its DB instance class to the default number of CPU cores for it. The threads per core setting isn't changed. The changes are applied immediately by using `--apply-immediately`. If you want to apply the changes during the next scheduled maintenance window, omit the `--apply-immediately` option.   
For Linux, macOS, or Unix:  

```
aws rds modify-db-instance \
    --db-instance-identifier mydbinstance \
    --processor-features "Name=coreCount,Value=DEFAULT" \
    --apply-immediately
```
For Windows:  

```
aws rds modify-db-instance ^
    --db-instance-identifier mydbinstance ^
    --processor-features "Name=coreCount,Value=DEFAULT" ^
    --apply-immediately
```

#### Returning to the default number of threads per core for a DB instance
<a name="USER_ConfigureProcessor.CLI.Example6"></a>

**Example**  
The following example modifies `mydbinstance` by returning its DB instance class to the default number of threads per core for it. The number of CPU cores setting isn't changed. The changes are applied immediately by using `--apply-immediately`. If you want to apply the changes during the next scheduled maintenance window, omit the `--apply-immediately` option.  
For Linux, macOS, or Unix:  

```
aws rds modify-db-instance \
    --db-instance-identifier mydbinstance \
    --processor-features "Name=threadsPerCore,Value=DEFAULT" \
    --apply-immediately
```
For Windows:  

```
aws rds modify-db-instance ^
    --db-instance-identifier mydbinstance ^
    --processor-features "Name=threadsPerCore,Value=DEFAULT" ^
    --apply-immediately
```

### RDS API
<a name="USER_ConfigureProcessor.API"></a>

You can set the processor features for a DB instance when you call one of the following Amazon RDS API operations:
+ [CreateDBInstance](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBInstance.html)
+ [ModifyDBInstance](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBInstance.html)
+ [RestoreDBInstanceFromDBSnapshot](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBInstanceFromDBSnapshot.html)
+ [RestoreDBInstanceFromS3](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBInstanceFromS3.html)
+ [RestoreDBInstanceToPointInTime](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_RestoreDBInstanceToPointInTime.html)

To configure the processor features of a DB instance class for a DB instance by using the Amazon RDS API, include the `ProcessFeatures` parameter in the call.

The parameter has the following syntax.

```
ProcessFeatures "Name=coreCount,Value=<value>" "Name=threadsPerCore,Value=<value>"
```

Specify the number of CPU cores with the `coreCount` feature name, and specify whether multiple threads per core are enabled with the `threadsPerCore` feature name. 

You can view the valid processor values for a particular DB instance class by running the [DescribeOrderableDBInstanceOptions](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeOrderableDBInstanceOptions.html) operation and specifying the instance class for the `DBInstanceClass` parameter. You can also use the following operations:
+ [DescribeDBInstances](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeDBInstances.html) – Shows the processor information for the specified DB instance.
+ [DescribeDBSnapshots](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeDBSnapshots.html) – Shows the processor information for the specified DB snapshot.
+ [DescribeValidDBInstanceModifications](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeValidDBInstanceModifications.html) – Shows the valid modifications to the processor for the specified DB instance.

In the output of the preceding operations, the values for the processor features are not null only if the following conditions are met:
+ You are using an RDS for Oracle DB instance.
+ Your RDS for Oracle DB instance supports changing processor values.
+ The current CPU core and thread settings are set to nondefault values.

If the preceding conditions aren't met, you can get the instance type using [DescribeDBInstances](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeDBInstances.html). You can get the processor information for this instance type by running the EC2 operation [DescribeInstanceTypes](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInstanceTypes.html).

# Hardware specifications for DB instance classes
<a name="Concepts.DBInstanceClass.Summary"></a>

In the tables in this section, you can find hardware details about the Amazon RDS DB instance classes. 

For information about Amazon RDS DB engine support for each DB instance class, see [Supported DB engines for DB instance classes](Concepts.DBInstanceClass.Support.md). 

**Topics**
+ [

## Hardware terminology for DB instance classes
](#Concepts.DBInstanceClass.hardware-terminology)
+ [

## Hardware specifications for the general-purpose instance classes
](#hardware-specifications.gen-purpose-inst-classes)
+ [

## Hardware specifications for the memory-optimized instance classes
](#hardware-specifications.mem-opt-inst-classes)
+ [

## Hardware specifications for the compute-optimized instance classes
](#hardware-specifications.compute-opt-inst-classes)
+ [

## Hardware specifications for the burstable-performance instance classes
](#hardware-specifications.burstable-inst-classes)

**Note**  
RDS for SQL Server supports Optimize CPU starting with 7th generation instance classes (such as db.m7i and db.r7i). The vCPU counts documented below may differ for these instance classes. For accurate vCPU counts, refer to [DB instance classes that support Optimize CPUDB instance class support](SQLServer.Concepts.General.OptimizeCPU.Support.md).

## Hardware terminology for DB instance classes
<a name="Concepts.DBInstanceClass.hardware-terminology"></a>

The following terminology is used to describe hardware specifications for DB instance classes:

**vCPU**  
The number of virtual central processing units (CPUs). A *virtual CPU *is a unit of capacity that you can use to compare DB instance classes. Instead of purchasing or leasing a particular processor to use for several months or years, you are renting capacity by the hour. Our goal is to make a consistent and specific amount of CPU capacity available, within the limits of the actual underlying hardware.

**ECU**  
The relative measure of the integer processing power of an Amazon EC2 instance. To make it easy for developers to compare CPU capacity between different instance classes, we have defined an Amazon EC2 Compute Unit. The amount of CPU that is allocated to a particular instance is expressed in terms of these EC2 Compute Units. One ECU currently provides CPU capacity equivalent to a 1.0–1.2 GHz 2007 Opteron or 2007 Xeon processor.

**Memory (GiB)**  
The RAM, in gibibytes, allocated to the DB instance. There is often a consistent ratio between memory and vCPU. As an example, take the db.r4 instance class, which has a memory to vCPU ratio similar to the db.r5 instance class. However, for most use cases the db.r5 instance class provides better, more consistent performance than the db.r4 instance class. 

**EBS-optimized**  
The DB instance uses an optimized configuration stack and provides additional, dedicated capacity for I/O. This optimization provides the best performance by minimizing contention between I/O and other traffic from your instance. For more information about Amazon EBS–optimized instances, see [Amazon EBS–Optimized instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html) in the *Amazon EC2 User Guide.*   
EBS-optimized instances have a baseline and maximum IOPS rate. The maximum IOPS rate is enforced at the DB instance level. A set of EBS volumes that combine to have an IOPS rate that is higher than the maximum can't exceed the instance-level threshold. For example, if the maximum IOPS for a particular DB instance class is 40,000, and you attach four 64,000 IOPS EBS volumes, the maximum IOPS is 40,000 rather than 256,000. For the IOPS maximum specific to each EC2 instance type, see [Supported instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html#ebs-optimization-support) in the *Amazon EC2 User Guide for Linux Instances*.

**Max. EBS bandwidth (Mbps)**  
The maximum EBS bandwidth in megabits per second. Divide by 8 to get the expected throughput in megabytes per second.   
General Purpose SSD (gp2) volumes for Amazon RDS DB instances have a throughput limit of 250 MiB/s in most cases. However, the throughput limit can vary depending on volume size. For more information, see [Amazon EBS volume types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html) in the *Amazon EC2 User Guide.*

**Network bandwidth**  
The network speed relative to other DB instance classes.

## Hardware specifications for the general-purpose instance classes
<a name="hardware-specifications.gen-purpose-inst-classes"></a>

The following tables show the compute, memory, storage, and bandwidth specifications for the general-purpose instance classes.

**db.m8g – general-purpose instance classes powered by AWS Graviton4 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m8g.48xlarge | 192 | — | 768 | EBS-optimized only | 40,000 | 50 | 
| db.m8g.24xlarge | 96 | — | 384 | EBS-optimized only | 30,000 | 40 | 
| db.m8g.16xlarge | 64 | — | 256 | EBS-optimized only | 20,000 | 30 | 
| db.m8g.12xlarge | 48 | — | 192 | EBS-optimized only | 15,000 | 22.5 | 
| db.m8g.8xlarge | 32 | — | 128 | EBS-optimized only | 10,000 | 15 | 
| db.m8g.4xlarge\$1 | 16 | — | 64 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.m8g.2xlarge\$1 | 8 | — | 32 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.m8g.xlarge\$1 | 4 | — | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m8g.large\$1 | 2 | — | 8 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.m7i – general-purpose instance classes powered by 4th generation Intel Xeon Scalable processors**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.m7i.metal-48xl | 192 | 96 | 2 | — | 768 | EBS-optimized only | 40,000 | 50 | 
| db.m7i.metal-24xl | 96 | 48 | 1 | — | 384 | EBS-optimized only | 30,000 | 37.5 | 
| db.m7i.48xlarge | 192 | — | — | — | 768 | EBS-optimized only | 40,000 | 50 | 
| db.m7i.24xlarge | 96 | — | — | — | 384 | EBS-optimized only | 30,000 | 37.5 | 
| db.m7i.16xlarge | 64 | — | — | — | 256 | EBS-optimized only | 20,000 | 25 | 
| db.m7i.12xlarge | 48 | — | — | — | 192 | EBS-optimized only | 15,000 | 18.75 | 
| db.m7i.8xlarge | 32 | — | — | — | 128 | EBS-optimized only | 10,000 | 12.5 | 
| db.m7i.4xlarge | 16 | — | — | — | 64 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m7i.2xlarge | 8 | — | — | — | 32 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m7i.xlarge | 4 | — | — | — | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m7i.large | 2 | — | — | — | 8 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.m7g – general-purpose instance classes powered by AWS Graviton3 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m7g.16xlarge | 64 | — | 256 | EBS-optimized only | 20,000 | 30 | 
| db.m7g.12xlarge | 48 | — | 192 | EBS-optimized only | 15,000 | 22.5 | 
| db.m7g.8xlarge | 32 | — | 128 | EBS-optimized only | 10,000 | 15 | 
| db.m7g.4xlarge | 16 | — | 64 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.m7g.2xlarge\$1 | 8 | — | 32 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.m7g.xlarge\$1 | 4 | — | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m7g.large\$1 | 2 | — | 8 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.m6g – general-purpose instance classes powered by AWS Graviton2 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6g.16xlarge | 64 | — | 256 | EBS-optimized only | 19,000 | 25 | 
| db.m6g.12xlarge | 48 | — | 192 | EBS-optimized only | 14,250 | 20 | 
| db.m6g.8xlarge | 32 | — | 128 | EBS-optimized only | 9,500 | 12 | 
| db.m6g.4xlarge | 16 | — | 64 | EBS-optimized only | 4,750 | Up to 10 | 
| db.m6g.2xlarge\$1 | 8 | — | 32 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.m6g.xlarge\$1 | 4 | — | 16 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.m6g.large\$1 | 2 | — | 8 | EBS-optimized only | Up to 4,750 | Up to 10 | 

**db.m6gd – general-purpose instance classes powered by AWS Graviton2 processors and SSD storage**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6gd.16xlarge | 64 | — | 256 | 2 x 1900 NVMe SSD | 19,000 | 25 | 
| db.m6gd.12xlarge | 48 | — | 192 | 2 x 1425 NVMe SSD | 14,250 | 20 | 
| db.m6gd.8xlarge | 32 | — | 128 | 1 x 1900 NVMe SSD | 9,500 | 12 | 
| db.m6gd.4xlarge\$1 | 16 | — | 64 | 1 x 950 NVMe SSD | 4,750 | Up to 10 | 
| db.m6gd.2xlarge\$1 | 8 | — | 32 | 1 x 474 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.m6gd.xlarge\$1 | 4 | — | 16 | 1 x 237 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.m6gd.large\$1 | 2 | — | 8 | 1 x 118 NVMe SSD | Up to 4,750 | Up to 10 | 

**db.m6id – general-purpose instance classes powered by 3rd generation Intel Xeon Scalable processors and SSD storage**


| Instance class | vCPU | Physical cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.m6id.metal | 128 | 64 | 2 | — | 512 | 4 x 1900 NVMe SSD | 40,000 | 50 | 
| db.m6id.32xlarge | 128 | — | — | — | 512 | 4 x 1900 NVMe SSD | 40,000 | 50 | 
| db.m6id.24xlarge | 96 | — | — | — | 384 | 4 x 1425 NVMe SSD | 30,000 | 37.5 | 
| db.m6id.16xlarge | 64 | — | — | — | 256 | 2 x 1900 NVMe SSD | 20,000 | 25 | 
| db.m6id.12xlarge | 48 | — | — | — | 192 | 2 x 1425 NVMe SSD | 15,000 | 18.75 | 
| db.m6id.8xlarge | 32 | — | — | — | 128 | 1 x 1900 NVMe SSD | 10,000 | 12.5 | 
| db.m6id.4xlarge\$1 | 16 | — | — | — | 64 | 1 x 950 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.m6id.2xlarge\$1 | 8 | — | — | — | 32 | 1 x 474 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.m6id.xlarge\$1 | 4 | — | — | — | 16 | 1 x 237 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.m6id.large\$1 | 2 | — | — | — | 8 | 1 x 118 NVMe SSD | Up to 10,000 | Up to 12.5 | 

**db.m6idn – general-purpose instance classes with 3rd Generation Intel Xeon Scalable processors, SSD storage, and network optimization**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m6idn.32xlarge | 128 | — | 512 | 4 x 1900 NVMe SSD | 100,000 | 200 | 
| db.m6idn.24xlarge | 96 | — | 384 | 4 x 1425 NVMe SSD | 75,000 | 150 | 
| db.m6idn.16xlarge | 64 | — | 256 | 2 x 1900 NVMe SSD | 50,000 | 100 | 
| db.m6idn.12xlarge | 48 | — | 192 | 2 x 1425 NVMe SSD | 37,500 | 75 | 
| db.m6idn.8xlarge | 32 | — | 128 | 1 x 1900 NVMe SSD | 25,000 | 50 | 
| db.m6idn.4xlarge\$1 | 16 | — | 64 | 1 x 950 NVMe SSD | Up to 25,000 | Up to 50 | 
| db.m6idn.2xlarge\$1 | 8 | — | 32 | 1 x 474 NVMe SSD | Up to 25,000 | Up to 40 | 
| db.m6idn.xlarge\$1 | 4 | — | 16 | 1 x 237 NVMe SSD | Up to 25,000 | Up to 30 | 
| db.m6idn.large\$1 | 2 | — | 8 | 1 x 118 NVMe SSD | Up to 25,000 | Up to 25 | 

**db.m6in – general-purpose instance classes powered by 3rd generation Intel Xeon Scalable processors and network optimization**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.m6in.metal | 128 | 64 | 2 | — | 512 | EBS-optimized only | 100,000 | 200 | 
| db.m6in.32xlarge | 128 |  |  | — | 512 | EBS-optimized only | 100,000 | 200 | 
| db.m6in.24xlarge | 96 |  |  | — | 384 | EBS-optimized only | 75,000 | 150 | 
| db.m6in.16xlarge | 64 |  |  | — | 256 | EBS-optimized only | 50,000 | 100 | 
| db.m6in.12xlarge | 48 |  |  | — | 192 | EBS-optimized only | 37,500 | 75 | 
| db.m6in.8xlarge | 32 |  |  | — | 128 | EBS-optimized only | 25,000 | 50 | 
| db.m6in.4xlarge\$1 | 16 |  |  | — | 64 | EBS-optimized only | Up to 25,000 | Up to 50 | 
| db.m6in.2xlarge\$1 | 8 |  |  | — | 32 | EBS-optimized only | Up to 25,000 | Up to 40 | 
| db.m6in.xlarge\$1 | 4 |  |  | — | 16 | EBS-optimized only | Up to 25,000 | Up to 30 | 
| db.m6in.large\$1 | 2 |  |  | — | 8 | EBS-optimized only | Up to 25,000 | Up to 25 | 

**db.m6i – general-purpose instance classes powered by 3rd generation Intel Xeon Scalable processors**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.m6i.metal | 128 | 64 | 2 | — | 512 | EBS-optimized only | 40,000 | 50 | 
| db.m6i.32xlarge | 128 |  |  | — | 512 | EBS-optimized only | 40,000 | 50 | 
| db.m6i.24xlarge | 96 |  |  | — | 384 | EBS-optimized only | 30,000 | 37.5 | 
| db.m6i.16xlarge | 64 |  |  | — | 256 | EBS-optimized only | 20,000 | 25 | 
| db.m6i.12xlarge | 48 |  |  | — | 192 | EBS-optimized only | 15,000 | 18.75 | 
| db.m6i.8xlarge | 32 |  |  | — | 128 | EBS-optimized only | 10,000 | 12.5 | 
| db.m6i.4xlarge\$1 | 16 |  |  | — | 64 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m6i.2xlarge\$1 | 8 |  |  | — | 32 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m6i.xlarge\$1 | 4 |  |  | — | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.m6i.large\$1 | 2 |  |  | — | 8 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.m5d – general-purpose instance classes powered by Intel Xeon Platinum processors and SSD storage**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m5d.24xlarge | 96 | 345 | 384 | 4 x 900 NVMe SSD | 19,000 | 25 | 
| db.m5d.16xlarge | 64 | 262 | 256 | 4 x 600 NVMe SSD | 13,600 | 20 | 
| db.m5d.12xlarge | 48 | 173 | 192 | 2 x 900 NVMe SSD | 9,500 | 12 | 
| db.m5d.8xlarge | 32 | 131 | 128 | 2 x 600 NVMe SSD | 6,800 | 10 | 
| db.m5d.4xlarge | 16 | 61 | 64 | 2 x 300 NVMe SSD | 4,750 | Up to 10 | 
| db.m5d.2xlarge\$1 | 8 | 31 | 32 | 1 x 300 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.m5d.xlarge\$1 | 4 | 15 | 16 | 1 x 150 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.m5d.large\$1 | 2 | 10 | 8 | 1 x 75 NVMe SSD | Up to 4,750 | Up to 10 | 

**db.m5 – general-purpose instance classes with Intel Xeon Platinum processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m5.24xlarge | 96 | 345 | 384 | EBS-optimized only | 19,000 | 25 | 
| db.m5.16xlarge | 64 | 262 | 256 | EBS-optimized only | 13,600 | 20 | 
| db.m5.12xlarge | 48 | 173 | 192 | EBS-optimized only | 9,500 | 12 | 
| db.m5.8xlarge | 32 | 131 | 128 | EBS-optimized only | 6,800 | 10 | 
| db.m5.4xlarge | 16 | 61 | 64 | EBS-optimized only | 4,750 | Up to 10 | 
| db.m5.2xlarge\$1 | 8 | 31 | 32 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.m5.xlarge\$1 | 4 | 15 | 16 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.m5.large\$1 | 2 | 10 | 8 | EBS-optimized only | Up to 4,750 | Up to 10 | 

**db.m4 – general-purpose instance classes with Intel Xeon Scalable processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m4.16xlarge | 64 | 188 | 256 | EBS-optimized only | 10,000 | 25 | 
| db.m4.10xlarge | 40 | 124.5 | 160 | EBS-optimized only | 4,000 | 10 | 
| db.m4.4xlarge | 16 | 53.5 | 64 | EBS-optimized only | 2,000 | High | 
| db.m4.2xlarge | 8 | 25.5 | 32 | EBS-optimized only | 1,000 | High | 
| db.m4.xlarge | 4 | 13 | 16 | EBS-optimized only | 750 | High | 
| db.m4.large | 2 | 6.5 | 8 | EBS-optimized only | 450 | Moderate | 

**db.m3 – general-purpose instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m3.2xlarge | 8 | 26 | 30 | EBS-optimized only | 1,000 | High | 
| db.m3.xlarge | 4 | 13 | 15 | EBS-optimized only | 500 | High | 
| db.m3.large | 2 | 6.5 | 7.5 | EBS only | — | Moderate | 
| db.m3.medium | 1 | 3 | 3.75 | EBS only | — | Moderate | 

\$1 These DB instance classes can support maximum performance for 30 minutes at least once every 24 hours. For more information on baseline performance of the underlying EC2 instance types, see [Amazon EBS-optimized instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html) in the *Amazon EC2 User Guide.*

## Hardware specifications for the memory-optimized instance classes
<a name="hardware-specifications.mem-opt-inst-classes"></a>

The following tables show the compute, memory, storage, and bandwidth specifications for the memory-optimized instance classes.

**db.z1d – memory-optimized instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.z1d.12xlarge | 48 | 271 | 384 | 2 x 900 NVMe SSD | 19,000 | 25 | 
| db.z1d.6xlarge | 24 | 134 | 192 | 1 x 900 NVMe SSD | 9,500 | 12 | 
| db.z1d.3xlarge | 12 | 75 | 96 | 1 x 450 NVMe SSD | 4,750 | Up to 10 | 
| db.z1d.2xlarge | 8 | 53 | 64 |  1 x 300 NVMe SSD  | 3,170 | Up to 10 | 
| db.z1d.xlarge\$1 | 4 | 28 | 32 | 1 x 150 NVMe SSD | Up to 3,170 | Up to 10 | 
| db.z1d.large\$1 | 2 | 15 | 16 | 1 x 75 NVMe SSD | Up to 3,170 | Up to 10 | 

**db.x2g – memory-optimized instance classes with AWS Graviton2 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x2g.16xlarge | 64 | — | 1024 | EBS-optimized only | 19,000 | 25 | 
| db.x2g.12xlarge | 48 | — | 768 | EBS-optimized only | 14,250 | 20 | 
| db.x2g.8xlarge | 32 | — | 512 | EBS-optimized only | 9,500 | 12 | 
| db.x2g.4xlarge | 16 | — | 256 | EBS-optimized only | 4,750 | Up to 10 | 
| db.x2g.2xlarge | 8 | — | 128 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.x2g.xlarge | 4 | — | 64 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.x2g.large | 2 | — | 32 | EBS-optimized only | Up to 4,750 | Up to 10 | 

**db.x2idn – memory-optimized instance classes with 3rd generation Intel Xeon Scalable processors**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.x2idn.metal | 128 | 64 | 2 | — | 2,048 | 2 x 1900 NVMe SSD | 80,000 | 100 | 
| db.x2idn.32xlarge | 128 | — | — | — | 2,048 | 2 x 1900 NVMe SSD | 80,000 | 100 | 
| db.x2idn.24xlarge | 96 | — | — | — | 1,536 | 2 x 1425 NVMe SSD | 60,000 | 75 | 
| db.x2idn.16xlarge | 64 | — | — | — | 1,024 | 1 x 1900 NVMe SSD | 40,000 | 50 | 

**db.x2iedn – memory-optimized instance classes with local NVMe-based SSDs, with 3rd generation Intel Xeon Scalable processors**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.x2iedn.metal | 128 | 64 | 2 | — | 4,096 | 2 x 1900 NVMe SSD | 80,000 | 100 | 
| db.x2iedn.32xlarge | 128 | — | — | — | 4,096 | 2 x 1900 NVMe SSD | 80,000 | 100 | 
| db.x2iedn.24xlarge | 96 | — | — | — | 3,072 | 2 x 1425 NVMe SSD | 60,000 | 75 | 
| db.x2iedn.16xlarge | 64 | — | — | — | 2,048 | 1 x 1900 NVMe SSD | 40,000 | 50 | 
| db.x2iedn.8xlarge | 32 | — | — | — | 1,024 | 1 x 950 NVMe SSD | 20,000 | 25 | 
| db.x2iedn.4xlarge | 16 | — | — | — | 512 | 1 x 475 NVMe SSD | Up to 20,000 | Up to 25 | 
| db.x2iedn.2xlarge | 8 | — | — | — | 256 | 1 x 237 NVMe SSD | Up to 20,000 | Up to 25 | 
| db.x2iedn.xlarge | 4 | — | — | — | 128 | 1 x 118 NVMe SSD | Up to 20,000 | Up to 25 | 

**db.x2iezn – memory-optimized instance classes with 2nd generation Intel Xeon Scalable processors**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.x2iezn.metal | 48 | 24 | 2 | — | 1,536 | EBS-optimized only | 19,000 | 100 | 
| db.x2iezn.12xlarge | >48 | — | — | — | 1,536 | EBS-optimized only | 19,000 | 100 | 
| db.x2iezn.8xlarge | 32 | — | — | — | 1,024 | EBS-optimized only | 12,000 | 75 | 
| db.x2iezn.6xlarge | 24 | — | — | — | 768 | EBS-optimized only | Up to 9,500 | 50 | 
| db.x2iezn.4xlarge | 16 | — | — | — | 512 | EBS-optimized only | Up to 4,750 | Up to 25 | 
| db.x2iezn.2xlarge | 8 | — | — | — | 256 | EBS-optimized only | Up to 3,170 | Up to 25 | 

**db.x1e – memory-optimized instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x1e.32xlarge | 128 | 340 | 3,904 | EBS-optimized only | 14,000 | 25 | 
| db.x1e.16xlarge | 64 | 179 | 1,952 | EBS-optimized only | 7,000 | 10 | 
| db.x1e.8xlarge | 32 | 91 | 976 | EBS-optimized only | 3,500 | Up to 10 | 
| db.x1e.4xlarge | 16 | 47 | 488 | EBS-optimized only | 1,750 | Up to 10 | 
| db.x1e.2xlarge | 8 | 23 | 244 | EBS-optimized only | 1,000 | Up to 10 | 
| db.x1e.xlarge | 4 | 12 | 122 | EBS-optimized only | 500 | Up to 10 | 

**db.x1 – memory-optimized instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.x1.32xlarge | 128 | 349 | 1,952 | EBS-optimized only | 14,000 | 25 | 
| db.x1.16xlarge | 64 | 174.5 | 976 | EBS-optimized only | 7,000 | 10 | 

**db.m8gd – memory-optimized instance classes powered by AWS Graviton4 processors and SSD storage** 


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.m8gd.48xlarge | 192 | — | 768 | 6 x 1900 NVMe SSD | 40,000 | 50 | 
| db.m8gd.24xlarge | 96 | — | 384 | 3 x 1900 NVMe SSD | 30,000 | 40 | 
| db.m8gd.16xlarge | 64 | — | 256 | 2 x 1900 NVMe SSD | 20,000 | 30 | 
| db.m8gd.12xlarge | 48 | — | 192 | 3 x 950 NVMe SSD | 15,000 | 22.5 | 
| db.m8gd.8xlarge | 32 | — | 128 | 1 x 1900 NVMe SSD | 10,000 | 15 | 
| db.m8gd.4xlarge | 16 | — | 64 | 1 x 950 NVMe SSD | Up to 10,000 | Up to 15 | 
| db.m8gd.2xlarge | 8 | — | 32 | 1 x 474 NVMe SSD | Up to 10,000 | Up to 15 | 
| db.m8gd.xlarge | 4 | — | 16 | 1 x 237 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.m8gd.large | 2 | — | 8 | 1 x 118 NVMe SSD | Up to 10,000 | Up to 12.5 | 

**db.r8gd – memory-optimized instance classes with AWS Graviton4 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r8gd.48xlarge | 192 | — | 1536 | 6 x 1900 NVMe SSD | 40,000 | 50 | 
| db.r8gd.24xlarge | 96 | — | 768 | 3 x 1900 NVMe SSD | 30,000 | 40 | 
| db.r8gd.16xlarge | 64 | — | 512 | 2 x 1900 NVMe SSD | 20,000 | 30 | 
| db.r8gd.12xlarge | 48 | — | 384 | 3 x 950 NVMe SSD | 15,000 | 22.5 | 
| db.r8gd.8xlarge | 32 | — | 256 | 1 x 1900 NVMe SSD | 10,000 | 15 | 
| db.r8gd.4xlarge | 16 | — | 128 | 1 x 950 NVMe SSD | Up to 10,000 | Up to 15 | 
| db.r8gd.2xlarge | 8 | — | 64 | 1 x 474 NVMe SSD | Up to 10,000 | Up to 15 | 
| db.r8gd.xlarge | 4 | — | 32 | 1 x 237 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.r8gd.large | 2 | — | 16 | 1 x 118 NVMe SSD | Up to 10,000 | Up to 12.5 | 

**db.r8g – memory-optimized instance classes with AWS Graviton4 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r8g.48xlarge | 192 | — | 1536 | EBS-optimized only | 40,000 | 50 | 
| db.r8g.24xlarge | 96 | — | 768 | EBS-optimized only | 30,000 | 40 | 
| db.r8g.16xlarge | 64 | — | 512 | EBS-optimized only | 20,000 | 30 | 
| db.r8g.12xlarge | 48 | — | 384 | EBS-optimized only | 15,000 | 22.5 | 
| db.r8g.8xlarge | 32 | — | 256 | EBS-optimized only | 10,000 | 15 | 
| db.r8g.4xlarge\$1 | 16 | — | 128 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.r8g.2xlarge\$1 | 8 | — | 64 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.r8g.xlarge\$1 | 4 | — | 32 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r8g.large\$1 | 2 | — | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.r7i – memory-optimized instance classes powered by 4th generation Intel Xeon Scalable processors**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Normalized units | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.r7i.metal-48xl | 192 | 96 | 2 | — | 1536 | 192 | EBS-optimized only | 40,000 | 50 | 
| db.r7i.metal-24xl | 96 | 48 | 1 | — | 768 | 96 | EBS-optimized only | 30,000 | 37.5 | 
| db.r7i.48xlarge | 192 | — | — | — | 1536 | 192 | EBS-optimized only | 40,000 | 50 | 
| db.r7i.24xlarge | 96 | — | — | — | 768 | 96 | EBS-optimized only | 30,000 | 37.5 | 
| db.r7i.16xlarge | 64 | — | — | — | 512 | 64 | EBS-optimized only | 20,000 | 25 | 
| db.r7i.12xlarge | 48 | — | — | — | 384 | 48 | EBS-optimized only | 15,000 | 18.75 | 
| db.r7i.8xlarge.tpc2.mem3x | 32 | — | — | — | 768 | 96 | EBS-optimized only | 30,000 | 12.5 | 
| db.r7i.8xlarge.tpc2.mem2x | 32 | — | — | — | 512 | 64 | EBS-optimized only | 20,000 | 12.5 | 
| db.r7i.8xlarge | 32 | — | — | — | 256 | 32 | EBS-optimized only | 10,000 | 12.5 | 
| db.r7i.6xlarge.tpc2.mem4x | 24 | — | — | — | 768 | 96 | EBS-optimized only | 30,000 | Up to 12.5 | 
| db.r7i.6xlarge.tpc2.mem2x | 24 | — | — | — | 384 | 48 | EBS-optimized only | 15,000 | Up to 12.5 | 
| db.r7i.4xlarge.tpc2.mem4x | 16 | — | — | — | 512 | 64 | EBS-optimized only | 20,000 | Up to 12.5 | 
| db.r7i.4xlarge.tpc2.mem3x | 16 | — | — | — | 384 | 48 | EBS-optimized only | 15,000 | Up to 12.5 | 
| db.r7i.4xlarge.tpc2.mem2x | 16 | — | — | — | 256 | 32 | EBS-optimized only | 10,000 | Up to 12.5 | 
| db.r7i.4xlarge | 16 | — | — | — | 128 | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r7i.3xlarge.tpc2.mem4x | 12 | — | — | — | 384 | 48 | EBS-optimized only | 15,000 | Up to 12.5 | 
| db.r7i.2xlarge.tpc2.mem8x | 8 | — | — | — | 512 | 64 | EBS-optimized only | 20,000 | Up to 12.5 | 
| db.r7i.2xlarge.tpc2.mem4x | 8 | — | — | — | 256 | 32 | EBS-optimized only | 10,000 | Up to 12.5 | 
| db.r7i.2xlarge | 8 | — | — | — | 64 | 8 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r7i.xlarge.tpc2.mem4x | 4 | — | — | — | 128 | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r7i.xlarge.tpc2.mem2x | 4 | — | — | — | 64 | 8 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r7i.xlarge | 4 | — | — | — | 32 | 4 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r7i.large | 2 | — | — | — | 16 | 2 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.r7g – memory-optimized instance classes with AWS Graviton3 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r7g.16xlarge | 64 | — | 512 | EBS-optimized only | 20,000 | 30 | 
| db.r7g.12xlarge | 48 | — | 384 | EBS-optimized only | 15,000 | 22.5 | 
| db.r7g.8xlarge | 32 | — | 256 | EBS-optimized only | 10,000 | 15 | 
| db.r7g.4xlarge | 16 | — | 128 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.r7g.2xlarge\$1 | 8 | — | 64 | EBS-optimized only | Up to 10,000 | Up to 15 | 
| db.r7g.xlarge\$1 | 4 | — | 32 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r7g.large\$1 | 2 | — | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.r6g – memory-optimized instance classes with AWS Graviton2 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6g.16xlarge | 64 | — | 512 | EBS-optimized only | 19,000 | 25 | 
| db.r6g.12xlarge | 48 | — | 384 | EBS-optimized only | 14,250 | 20 | 
| db.r6g.8xlarge | 32 | — | 256 | EBS-optimized only | 9,500 | 12 | 
| db.r6g.4xlarge | 16 | — | 128 | EBS-optimized only | 4,750 | Up to 10  | 
| db.r6g.2xlarge\$1 | 8 | — | 64 | EBS-optimized only | Up to 4,750 | Up to 10  | 
| db.r6g.xlarge\$1 | 4 | — | 32 | EBS-optimized only | Up to 4,750 | Up to 10  | 
| db.r6g.large\$1 | 2 | — | 16 | EBS-optimized only | Up to 4,750 | Up to 10  | 

**db.r6gd – memory-optimized instance classes with AWS Graviton2 processors and SSD storage** 


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6gd.16xlarge | 64 | — | 512 | 2 x 1900 NVMe SSD | 19,000 | 25 | 
| db.r6gd.12xlarge | 48 | — | 384 | 2 x 1425 NVMe SSD | 14,250 | 20 | 
| db.r6gd.8xlarge | 32 | — | 256 | 1 x 1900 NVMe SSD | 9,500 | 12 | 
| db.r6gd.4xlarge | 16 | — | 128 | 1 x 950 NVMe SSD | 4,750 | Up to 10  | 
| db.r6gd.2xlarge | 8 | — | 64 | 1 x 474 NVMe SSD | Up to 4,750 | Up to 10  | 
| db.r6gd.xlarge | 4 | — | 32 | 1 x 237 NVMe SSD | Up to 4,750 | Up to 10  | 
| db.r6gd.large | 2 | — | 16 | 1 x 118 NVMe SSD | Up to 4,750 | Up to 10  | 

**db.r6id – memory-optimized instance classes with 3rd generation Intel Xeon Scalable processors and SSD storage**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.r6id.metal | 128 | 64 | 2 | — | 1,024 | 4 x 1900 NVMe SSD | 40,000 | 50 | 
| db.r6id.32xlarge | 128 | — | — | — | 1,024 | 4x1900 NVMe SSD | 40,000 | 50 | 
| db.r6id.24xlarge | 96 | — | — | — | 768 | 4x1425 NVMe SSD | 30,000 | 37.5 | 
| db.r6id.16xlarge | 64 | — | — | — | 512 | 2x1900 NVMe SSD | 20,000 | 25 | 
| db.r6id.12xlarge | 48 | — | — | — | 384 | 2x1425 NVMe SSD | 15,000 | 18.75 | 
| db.r6id.8xlarge | 32 | — | — | — | 256 | 1x1900 NVMe SSD | 10,000 | 12.5 | 
| db.r6id.4xlarge\$1 | 16 | — | — | — | 128 | 1x950 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.r6id.2xlarge\$1 | 8 | — | — | — | 64 | 1x474 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.r6id.xlarge\$1 | 4 | — | — | — | 32 | 1x237 NVMe SSD | Up to 10,000 | Up to 12.5 | 
| db.r6id.large\$1 | 2 | — | — | — | 16 | 1x118 NVMe SSD | Up to 10,000 | Up to 12.5 | 

**db.r6idn – memory-optimized instance classes with 3rd generation Intel Xeon Scalable processors, SSD storage, and network optimization**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6idn.32xlarge | 128 | — | 1,024 | 4x1900 NVMe SSD | 100,000 | 200 | 
| db.r6idn.24xlarge | 96 | — | 768 | 4x1425 NVMe SSD | 75,000 | 150 | 
| db.r6idn.16xlarge | 64 | — | 512 | 2x1900 NVMe SSD | 50,000 | 100 | 
| db.r6idn.12xlarge | 48 | — | 384 | 2x1425 NVMe SSD | 37,500 | 75 | 
| db.r6idn.8xlarge | 32 | — | 256 | 1x1900 NVMe SSD | 25,000 | 50 | 
| db.r6idn.4xlarge\$1 | 16 | — | 128 | 1x950 NVMe SSD | Up to 25,000 | Up to 50 | 
| db.r6idn.2xlarge\$1 | 8 | — | 64 | 1x474 NVMe SSD | Up to 25,000 | Up to 40 | 
| db.r6idn.xlarge\$1 | 4 | — | 32 | 1x237 NVMe SSD | Up to 25,000 | Up to 30 | 
| db.r6idn.large\$1 | 2 | — | 16 | 1x118 NVMe SSD | Up to 25,000 | Up to 25 | 

**db.r6in – memory-optimized instance classes with 3rd generation Intel Xeon Scalable processors and network optimization**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.r6in.metal | 128 | 64 | 2 | — | 1,024 | EBS-optimized only | 100,000 | 200 | 
| db.r6in.32xlarge | 128 | — | — | — | 1,024 | EBS-optimized only | 100,000 | 200 | 
| db.r6in.24xlarge | 96 | — | — | — | 768 | EBS-optimized only | 75,000 | 150 | 
| db.r6in.16xlarge | 64 | — | — | — | 512 | EBS-optimized only | 50,000 | 100 | 
| db.r6in.12xlarge | 48 | — | — | — | 384 | EBS-optimized only | 37,500 | 75 | 
| db.r6in.8xlarge | 32 | — | — | — | 256 | EBS-optimized only | 25,000 | 50 | 
| db.r6in.4xlarge\$1 | 16 | — | — | — | 128 | EBS-optimized only | Up to 25,000 | Up to 50 | 
| db.r6in.2xlarge\$1 | 8 | — | — | — | 64 | EBS-optimized only | Up to 25,000 | Up to 40 | 
| db.r6in.xlarge\$1 | 4 | — | — | — | 32 | EBS-optimized only | Up to 25,000 | Up to 30 | 
| db.r6in.large\$1 | 2 | — | — | — | 16 | EBS-optimized only | Up to 25,000 | Up to 25 | 

**db.r6i – Oracle memory-optimized instance classes preconfigured for high memory, storage, and I/O**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r6i.8xlarge.tpc2.mem4x | 32 | — | 1024 | EBS-optimized only | 40,000 | 50 | 
| db.r6i.8xlarge.tpc2.mem3x | 32 | — | 768 | EBS-optimized only | 30,000 | 37.5 | 
| db.r6i.6xlarge.tpc2.mem4x | 24 | — | 768 | EBS-optimized only | 30,000 | 37.5 | 
| db.r6i.4xlarge.tpc2.mem4x | 16 | — | 512 | EBS-optimized only | 20,000 | 25 | 
| db.r6i.4xlarge.tpc2.mem3x | 16 | — | 384 | EBS-optimized only | 15,000 | 18.75 | 
| db.r6i.4xlarge.tpc2.mem2x | 16 | — | 256 | EBS-optimized only | 10,000 | 12.5 | 
| db.r6i.2xlarge.tpc2.mem8x | 8 | — | 512 | EBS-optimized only | 20,000 | 25 | 
| db.r6i.2xlarge.tpc2.mem4x | 8 | — | 256 | EBS-optimized only | 10,000 | 12.5 | 
| db.r6i.2xlarge.tpc1.mem2x | 8 | — | 128 | EBS-optimized only | Up to 10,000 | 12.5 | 
| db.r6i.xlarge.tpc2.mem4x | 4 | — | 128 | EBS-optimized only | Up to 10,000 | 12.5 | 
| db.r6i.xlarge.tpc2.mem2x | 4 | — | 64 | EBS-optimized only | Up to 10,000 | 12.5 | 
| db.r6i.large.tpc1.mem2x | 2 | — | 32 | EBS-optimized only | Up to 10,000 | 12.5 | 

**db.r6i – memory-optimized instance classes with 3rd Generation Intel Xeon Scalable processors**


| Instance class | vCPU | Processor cores | Sockets | ECU | Memory (GiB) | Normalized units | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| db.r6i.metal | 128 | 64 | 2 | — | 1,024 | 256 | EBS-optimized only | 40,000 | 50 | 
| db.r6i.32xlarge | 128 | — | — | — | 1,024 | 256 | EBS-optimized only | 40,000 | 50 | 
| db.r6i.24xlarge | 96 | — | — | — | 768 | 192 | EBS-optimized only | 30,000 | 37.5 | 
| db.r6i.16xlarge | 64 | — | — | — | 512 | 128 | EBS-optimized only | 20,000 | 25 | 
| db.r6i.12xlarge | 48 | — | — | — | 384 | 96 | EBS-optimized only | 15,000 | 18.75 | 
| db.r6i.8xlarge | 32 | — | — | — | 256 | 64 | EBS-optimized only | 10,000 | 12.5 | 
| db.r6i.4xlarge\$1 | 16 | — | — | — | 128 | 32 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r6i.2xlarge\$1 | 8 | — | — | — | 64 | 16 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r6i.xlarge\$1 | 4 | — | — | — | 32 | 8 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 
| db.r6i.large\$1 | 2 | — | — | — | 16 | 4 | EBS-optimized only | Up to 10,000 | Up to 12.5 | 

**db.r5d – memory-optimized instance classes with Intel Xeon Platinum processors and SSD storage**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5d.24xlarge | 96 | 347 | 768 | 4 x 900 NVMe SSD | 19,000 | 25 | 
| db.r5d.16xlarge | 64 | 264 | 512 | 4 x 600 NVMe SSD | 13,600 | 20 | 
| db.r5d.12xlarge | 48 | 173 | 384 | 2 x 900 NVMe SSD | 9,500 | 12 | 
| db.r5d.8xlarge | 32 | 132 | 256 | 2 x 600 NVMe SSD | 6,800 | 10 | 
| db.r5d.4xlarge | 16 | 71 | 128 | 2 x 300 NVMe SSD | 4,750 | Up to 10 | 
| db.r5d.2xlarge\$1 | 8 | 38 | 64 | 1 x 300 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.r5d.xlarge\$1 | 4 | 19 | 32 | 1 x 150 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.r5d.large\$1 | 2 | 10 | 16 | 1 x 75 NVMe SSD | Up to 4,750 | Up to 10 | 

**db.r5b – Oracle memory-optimized instance classes preconfigured for high memory, storage, and I/O**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5b.8xlarge.tpc2.mem3x | 32 | — | 768 | EBS-optimized only | 60,000 | 25 | 
| db.r5b.6xlarge.tpc2.mem4x | 24 | — | 768 | EBS-optimized only | 60,000 | 25 | 
| db.r5b.4xlarge.tpc2.mem4x | 16 | — | 512 | EBS-optimized only | 40,000 | 20 | 
| db.r5b.4xlarge.tpc2.mem3x | 16 | — | 384 | EBS-optimized only | 30,000 | 12 | 
| db.r5b.4xlarge.tpc2.mem2x | 16 | — | 256 | EBS-optimized only | 20,000 | 10 | 
| db.r5b.2xlarge.tpc2.mem8x | 8 | — | 512 | EBS-optimized only | 40,000 | 20 | 
| db.r5b.2xlarge.tpc2.mem4x | 8 | — | 256 | EBS-optimized only | 20,000 | 10 | 
| db.r5b.2xlarge.tpc1.mem2x | 8 | — | 128 | EBS-optimized only | 10,000 | Up to 10 | 
| db.r5b.xlarge.tpc2.mem4x | 4 | — | 128 | EBS-optimized only | 10,000 | Up to 10 | 
| db.r5b.xlarge.tpc2.mem2x | 4 | — | 64 | EBS-optimized only | Up to 10,000 | Up to 10 | 
| db.r5b.large.tpc1.mem2x | 2 | — | 32 | EBS-optimized only | Up to 10,000 | Up to 10 | 

**db.r5b – memory-optimized instance classes with Intel Xeon Platinum processors and EBS optimization**


| Instance class | vCPU | ECU | Memory (GiB) | Normalized units | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | 
| db.r5b.24xlarge | 96 | 347 | 768 | 192 | EBS-optimized only | 60,000 | 25 | 
| db.r5b.16xlarge | 64 | 264 | 512 | 128 | EBS-optimized only | 40,000 | 20 | 
| db.r5b.12xlarge | 48 | 173 | 384 | 96 | EBS-optimized only | 30,000 | 12 | 
| db.r5b.8xlarge | 32 | 132 | 256 | 64 | EBS-optimized only | 20,000 | 10 | 
| db.r5b.4xlarge | 16 | 71 | 128 | 32 | EBS-optimized only | 10,000 | Up to 10 | 
| db.r5b.2xlarge\$1 | 8 | 38 | 64 | 16 | EBS-optimized only | Up to 10,000 | Up to 10 | 
| db.r5b.xlarge\$1 | 4 | 19 | 32 | 8 | EBS-optimized only | Up to 10,000 | Up to 10 | 
| db.r5b.large\$1 | 2 | 10 | 16 | 4 | EBS-optimized only | Up to 10,000 | Up to 10 | 

**db.r5 – Oracle memory-optimized instance classes preconfigured for high memory, storage, and I/O**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r5.12xlarge.tpc2.mem2x | 48 | — | 768 | EBS-optimized only | 19,000 | 25 | 
| db.r5.8xlarge.tpc2.mem3x | 32 | — | 768 | EBS-optimized only | 19,000 | 25 | 
| db.r5.6xlarge.tpc2.mem4x | 24 | — | 768 | EBS-optimized only | 19,000 | 25 | 
| db.r5.4xlarge.tpc2.mem4x | 16 | — | 512 | EBS-optimized only | 13,600 | 20 | 
| db.r5.4xlarge.tpc2.mem3x | 16 | — | 384 | EBS-optimized only | 9,500 | 12 | 
| db.r5.4xlarge.tpc2.mem2x | 16 | — | 256 | EBS-optimized only | 6,800 | 10 | 
| db.r5.2xlarge.tpc2.mem8x | 8 | — | 512 | EBS-optimized only | 13,600 | 20 | 
| db.r5.2xlarge.tpc2.mem4x | 8 | — | 256 | EBS-optimized only | 6,800 | 10 | 
| db.r5.2xlarge.tpc1.mem2x | 8 | — | 128 | EBS-optimized only | 4,750 | Up to 10 | 
| db.r5.xlarge.tpc2.mem4x | 4 | — | 128 | EBS-optimized only | 4,750 | Up to 10 | 
| db.r5.xlarge.tpc2.mem2x | 4 | — | 64 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.r5.large.tpc1.mem2x | 2 | — | 32 | EBS-optimized only | Up to 4,750 | Up to 10 | 

**db.r5 – memory-optimized instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Normalized units | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | --- | 
| db.r5.24xlarge | 96 | 347 | 768 | 192 | EBS-optimized only | 19,000 | 25 | 
| db.r5.16xlarge | 64 | 264 | 512 | 128 | EBS-optimized only | 13,600 | 20 | 
| db.r5.12xlarge | 48 | 173 | 384 | 96 | EBS-optimized only | 9,500 | 12 | 
| db.r5.8xlarge | 32 | 132 | 256 | 64 | EBS-optimized only | 6,800 | 10 | 
| db.r5.4xlarge | 16 | 71 | 128 | 32 | EBS-optimized only | 4,750 | Up to 10 | 
| db.r5.2xlarge\$1 | 8 | 38 | 64 | 16 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.r5.xlarge\$1 | 4 | 19 | 32 | 8 | EBS-optimized only | Up to 4,750 | Up to 10 | 
| db.r5.large\$1 | 2 | 10 | 16 | 4 | EBS-optimized only | Up to 4,750 | Up to 10 | 

**db.r4 – memory-optimized instance classes with Intel Xeon Scalable processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r4.16xlarge | 64 | 195 | 488 | EBS-optimized only | 14,000 | 25 | 
| db.r4.8xlarge | 32 | 99 | 244 | EBS-optimized only | 7,000 | 10 | 
| db.r4.4xlarge | 16 | 53 | 122 | EBS-optimized only | 3,500 | Up to 10 | 
| db.r4.2xlarge | 8 | 27 | 61 | EBS-optimized only | 1,700 | Up to 10 | 
| db.r4.xlarge | 4 | 13.5 | 30.5 | EBS-optimized only | 850 | Up to 10 | 
| db.r4.large | 2 | 7 | 15.25 | EBS-optimized only | 425 | Up to 10 | 

**db.r3 – memory-optimized instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.r3.8xlarge\$1\$1 | 32 | 104 | 244 | EBS only | — | 10 | 
| db.r3.4xlarge | 16 | 52 | 122 | EBS-optimized only | 2,000 | High | 
| db.r3.2xlarge | 8 | 26 | 61 | EBS-optimized only | 1,000 | High | 
| db.r3.xlarge | 4 | 13 | 30.5 | EBS-optimized only | 500 | Moderate | 
| db.r3.large | 2 | 6.5 | 15.25 | EBS-optimized only | — | Moderate | 

\$1 These DB instance classes can support maximum performance for 30 minutes at least once every 24 hours. For more information on baseline performance of the underlying EC2 instance types, see [Amazon EBS-optimized instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html) in the *Amazon EC2 User Guide.*

\$1\$1 The r3.8xlarge DB instance class doesn't have dedicated EBS bandwidth and therefore doesn't offer EBS optimization. For this instance class, network traffic and Amazon EBS traffic share the same 10-gigabit network interface.

## Hardware specifications for the compute-optimized instance classes
<a name="hardware-specifications.compute-opt-inst-classes"></a>

The following tables show the compute, memory, storage, and bandwidth specifications for the compute-optimized instance classes.

**db.c6gd – compute-optimized instance classes (for Multi-AZ DB cluster deployments only)**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.c6gd.16xlarge | 64 | — | 128 | 2 x 1900 NVMe SSD | 19,000 | 25 | 
| db.c6gd.12xlarge | 48 | — | 96 | 2 x 1425 NVMe SSD | 14,250 | 20 | 
| db.c6gd.8xlarge | 32 | — | 64 | 1 x 1900 NVMe SSD | 9,500 | 12 | 
| db.c6gd.4xlarge | 16 | — | 32 | 1 x 950 NVMe SSD | 4,750 | Up to 10 | 
| db.c6gd.2xlarge | 8 | — | 16 | 1 x 474 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.c6gd.xlarge | 4 | — | 8 | 1 x 237 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.c6gd.large | 2 | — | 4 | 1 x 118 NVMe SSD | Up to 4,750 | Up to 10 | 
| db.c6gd.medium | 1 | — | 2 | 1 x 59 NVMe SSD | Up to 4,750 | Up to 10 | 

## Hardware specifications for the burstable-performance instance classes
<a name="hardware-specifications.burstable-inst-classes"></a>

The following tables show the compute, memory, storage, and bandwidth specifications for the burstable-performance instance classes.

**db.t4g – burstable-performance instance classes powered by AWS Graviton2 processors**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.t4g.2xlarge\$1 | 8 | — | 32 | EBS-optimized only | Up to 2,780 | Up to 5 | 
| db.t4g.xlarge\$1 | 4 | — | 16 | EBS-optimized only | Up to 2,780 | Up to 5 | 
| db.t4g.large\$1 | 2 | — | 8 | EBS-optimized only | Up to 2,780 | Up to 5 | 
| db.t4g.medium\$1 | 2 | — | 4 | EBS-optimized only | Up to 2,085 | Up to 5 | 
| db.t4g.small\$1 | 2 | — | 2 | EBS-optimized only | Up to 2,085 | Up to 5 | 
| db.t4g.micro\$1 | 2 | — | 1 | EBS-optimized only | Up to 2,085 | Up to 5 | 

**db.t3 – burstable-performance instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.t3.2xlarge\$1 | 8 | Variable | 32 | EBS-optimized only | Up to 2,780 | Up to 5 | 
| db.t3.xlarge\$1 | 4 | Variable | 16 | EBS-optimized only | Up to 2,780 | Up to 5 | 
| db.t3.large\$1 | 2 | Variable | 8 | EBS-optimized only | Up to 2,780 | Up to 5 | 
| db.t3.medium\$1 | 2 | Variable | 4 | EBS-optimized only | Up to 2,085 | Up to 5 | 
| db.t3.small\$1 | 2 | Variable | 2 | EBS-optimized only | Up to 2,085 | Up to 5 | 
| db.t3.micro\$1 | 2 | Variable | 1 | EBS-optimized only | Up to 2,085 | Up to 5 | 

**db.t2 – burstable-performance instance classes**


| Instance class | vCPU | ECU | Memory (GiB) | Instance storage (GiB) | Max. EBS bandwidth (Mbps) | Network bandwidth (Gbps) | 
| --- | --- | --- | --- | --- | --- | --- | 
| db.t2.2xlarge | 8 | Variable | 32 | EBS only | — | Moderate | 
| db.t2.xlarge | 4 | Variable | 16 | EBS only | — | Moderate | 
| db.t2.large | 2 | Variable | 8 | EBS only | — | Moderate | 
| db.t2.medium | 2 | Variable | 4 | EBS only | — | Moderate | 
| db.t2.small | 1 | Variable | 2 | EBS only | — | Low | 
| db.t2.micro | 1 | Variable | 1 | EBS only | — | Low | 

\$1 These DB instance classes can support maximum performance for 30 minutes at least once every 24 hours. For more information on baseline performance of the underlying EC2 instance types, see [Amazon EBS-optimized instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html) in the *Amazon EC2 User Guide.*

# Amazon RDS DB instance storage
<a name="CHAP_Storage"></a>

DB instances for Amazon RDS for Db2, MariaDB, MySQL, PostgreSQL, Oracle, and Microsoft SQL Server use Amazon Elastic Block Store (Amazon EBS) volumes for database and log storage.

In some cases, your database workload might not be able to achieve 100 percent of the IOPS that you have provisioned. For more information, see [Factors that affect database performance](#CHAP_Storage.Other.Factors).

For more information about instance storage pricing, see [Amazon RDS pricing](https://aws.amazon.com/rds/pricing/).

**Topics**
+ [

## Amazon RDS storage types
](#Concepts.Storage)
+ [

## Provisioned IOPS SSD storage
](#USER_PIOPS)
+ [

## General Purpose SSD storage
](#Concepts.Storage.GeneralSSD)
+ [

## Performance characteristics of solid-state drive (SSD) storage types
](#storage-comparison)
+ [

## Magnetic storage (legacy, not recommended)
](#CHAP_Storage.Magnetic)
+ [

## Additional storage volumes
](#Welcome.AdditionalStorageVolumes)
+ [

## Dedicated log volume (DLV)
](#CHAP_Storage.dlv)
+ [

## Monitoring database performance
](#Concepts.Storage.Metrics)
+ [

## Factors that affect database performance
](#CHAP_Storage.Other.Factors)

**Important**  
Amazon RDS is deprecating magnetic storage on April 30, 2026. We recommend that you upgrade your magnetic storage volumes to gp3 or io2 before April 29, 2026. After April 29, 2026, Amazon RDS will begin forced migration of magnetic storage volumes to gp3 storage volumes. In addition, the default storage type when restoring snapshots of magnetic volumes will be changed to gp3 by June 1, 2026. You can override this default with your preferred storage type.

## Amazon RDS storage types
<a name="Concepts.Storage"></a>

Amazon RDS provides three storage types: Provisioned IOPS SSD (also known as io1 and io2 Block Express), General Purpose SSD (also known as gp2 and gp3), and magnetic (also known as standard). They differ in performance characteristics and price, which means that you can tailor your storage performance and cost to the needs of your database workload. You can create Db2, MySQL, MariaDB, and PostgreSQL RDS DB instances with up to 64 tebibytes (TiB) of storage. You can create Oracle and SQL Server instances with up to 256 TiB of storage with additional storage volumes. For more information, see [Additional storage volumes](#Welcome.AdditionalStorageVolumes). RDS for Db2 doesn't support the gp2 and magnetic storage types.

The following list briefly describes the three storage types:
+ **Provisioned IOPS SSD** – Provisioned IOPS storage is designed to meet the needs of I/O-intensive workloads, particularly database workloads, that require low I/O latency and consistent I/O throughput. Provisioned IOPS storage is best suited for production environments.

  For more information about Provisioned IOPS storage, including the storage size ranges, see [Provisioned IOPS SSD storage](#USER_PIOPS).
+ **General Purpose SSD** – General Purpose SSD volumes offer cost-effective storage that is ideal for a broad range of workloads running on medium-sized DB instances. General Purpose storage is best suited for development and testing environments.

  For more information about General Purpose SSD storage, including the storage size ranges, see [General Purpose SSD storage](#Concepts.Storage.GeneralSSD).
+ **Magnetic** – Amazon RDS also supports magnetic storage for backward compatibility. We recommend that you use General Purpose SSD or Provisioned IOPS SSD for any new storage needs. The maximum amount of storage allowed for DB instances on magnetic storage is 3 TiB. For more information, see [Magnetic storage (legacy, not recommended)](#CHAP_Storage.Magnetic).

## Provisioned IOPS SSD storage
<a name="USER_PIOPS"></a>

For a production application that requires fast and consistent I/O performance, we recommend Provisioned IOPS storage. Provisioned IOPS storage is a storage type that delivers predictable performance, and consistently low latency. Provisioned IOPS storage is optimized for online transaction processing (OLTP) workloads that require consistent performance. Provisioned IOPS helps performance tuning of these workloads.

Amazon RDS offers two types of Provisioned IOPS SSD storage: io2 and io1. When you create a DB instance, you specify the IOPS rate and the size of the volume. Amazon RDS provides that IOPS rate for the DB instance until you change it.

**Topics**
+ [

### io2 Block Express storage (recommended)
](#USER_PIOPS.io2)
+ [

### io1 storage (previous generation)
](#USER_PIOPS.io1)
+ [

### Combining Provisioned IOPS storage with Multi-AZ deployments or read replicas
](#Overview.ProvisionedIOPS-support)
+ [

### Provisioned IOPS storage costs
](#Overview.ProvisionedIOPS-cost)
+ [

### Getting the best performance from Amazon RDS Provisioned IOPS storage
](#Overview.ProvisionedIOPS.gettingthemostoutofpiops)

### io2 Block Express storage (recommended)
<a name="USER_PIOPS.io2"></a>

For I/O-intensive and latency-sensitive workloads, we recommend that you use Provisioned IOPS SSD io2 Block Express storage to achieve up to 256,000 I/O operations per second (IOPS). The throughput of io2 Block Express volumes varies based on the amount of IOPS provisioned per volume and on the size of the I/O operations being run.

All RDS io2 volumes based on the AWS Nitro System are io2 Block Express volumes and provide sub-millisecond average latency. DB instances not based on the AWS Nitro System are io2 volumes. 

The following table shows the range of Provisioned IOPS and maximum throughput per storage volume for each database engine and storage size range. In Amazon RDS for Oracle and SQL Server, you can attach up to three additional storage volumes in addition to the primary storage volumes to provision up to 256 TiB storage size in total. With additional storage volumes, you can have higher provisioned IOPS and maximum throughput for your DB instance. However, your DB instance might not be able to fully utilize the provisioned IOPS and maximum throughput if your instance class has lower limits than the values you've provisioned for your storage volumes. For more information, see [Factors that affect database performance](#CHAP_Storage.Other.Factors).


| Database engine | Range of storage size | Range of Provisioned IOPS | Maximum throughput | 
| --- | --- | --- | --- | 
| Db2, MariaDB, MySQL, and PostgreSQL | 100–65,536 GiB | 1,000–256,000 IOPS | 16,000 MiB/s | 
| Oracle | 100–199 GiB | 1,000–199,000 IOPS | 4,000 MiB/s | 
| Oracle | 200–65,536 GiB | 1,000–256,000 IOPS | 16,000 MiB/s | 
| SQL Server | 20–65,536 GiB | 1,000–256,000 IOPS | 4,000 MiB/s | 

The IOPS and storage size ranges have the following constraints:
+ The ratio of IOPS to allocated storage (in GiB) must be from 0.5–1,000. For DB instances not based on the AWS Nitro System, the ratio must be from 0.5–500.
+ Maximum IOPS can be provisioned with volumes 256 GiB and larger (1,000 IOPS × 256 GiB = 256,000 IOPS). For DB instances not based on the AWS Nitro System, maximum IOPS are achieved at 512 GiB (500 IOPS x 512 GiB = 256,000 IOPS).
+ Throughput scales proportionally up to 0.256 MiB/s per provisioned IOPS. Maximum throughput of 4,000 MiB/s can be achieved at 256,000 IOPS with a 16-KiB I/O size and 16,000 IOPS or higher with a 256-KiB I/O size. For DB instances not based on the AWS Nitro System, maximum throughput of 2,000 MiB/s can be achieved at 128,000 IOPS with a 16-KiB I/O size.
+ If you're using storage autoscaling, the same ratios between IOPS and maximum storage threshold (in GiB) also apply. For more information on storage autoscaling, see [Managing capacity automatically with Amazon RDS storage autoscaling](USER_PIOPS.Autoscaling.md).

Amazon RDS io2 Block Express volumes are available in all commercial AWS Regions and AWS GovCloud (US) Regions. These volumes aren't available in the China Regions. 

### io1 storage (previous generation)
<a name="USER_PIOPS.io1"></a>

For I/O-intensive workloads, you can use Provisioned IOPS SSD io1 storage and achieve up to 256,000 I/O operations per second (IOPS). The throughput of io1 volumes varies based on the amount of IOPS provisioned per volume and on the size of the I/O operations being run. We recommend using io2 Block Express storage where it's available.

The following table shows the range of Provisioned IOPS and maximum throughput for each database engine and storage size range.


| Database engine | Range of storage size | Range of Provisioned IOPS | Maximum throughput | 
| --- | --- | --- | --- | 
| Db2, MariaDB, MySQL, and PostgreSQL | 100–399 GiB | 1,000–19,950 IOPS | 500 MiB/s | 
| Db2, MariaDB, MySQL, and PostgreSQL | 400–65,536 GiB | 1,000–256,000 IOPS | 4,000 MiB/s | 
| Oracle | 100–199 GiB | 1,000–9,950 IOPS | 500 MiB/s | 
| Oracle | 200–65,536 GiB | 1,000–256,000 IOPS¹ | 4,000 MiB/s | 
| SQL Server | 20–16,384 GiB | 1,000–64,000 IOPS² | 1,000 MiB/s | 

**Note**  
¹ For Oracle, you can provision the maximum 256,000 IOPS only on the r5b instance type.  
² For SQL Server, the maximum 64,000 IOPS is guaranteed only on [Nitro-based instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances) that are on the m5\$1, m6i, r5\$1, r6i, and z1d instance types. Other instance types guarantee performance up to 32,000 IOPS.

The IOPS and storage size ranges have the following constraints:
+ The ratio of IOPS to allocated storage (in GiB) must be from 1–50 on RDS for SQL Server, and 0.5–50 on other RDS DB engines.
+ If you're using storage autoscaling, the same ratios between IOPS and maximum storage threshold (in GiB) also apply. 

  For more information on storage autoscaling, see [Managing capacity automatically with Amazon RDS storage autoscaling](USER_PIOPS.Autoscaling.md).

### Combining Provisioned IOPS storage with Multi-AZ deployments or read replicas
<a name="Overview.ProvisionedIOPS-support"></a>

For production OLTP use cases, we recommend that you use Multi-AZ deployments for enhanced fault tolerance with Provisioned IOPS storage for fast and predictable performance.

You can also use Provisioned IOPS storage with read replicas for MySQL, MariaDB or PostgreSQL. The type of storage for a read replica is independent of that on the primary DB instance. For example, you might use General Purpose SSD for read replicas with a primary DB instance that uses Provisioned IOPS SSD storage to reduce costs. However, your read replica's performance in this case might differ from that of a configuration where both the primary DB instance and the read replicas use Provisioned IOPS storage.

### Provisioned IOPS storage costs
<a name="Overview.ProvisionedIOPS-cost"></a>

With Provisioned IOPS storage, you are charged for the provisioned resources whether or not you use them in a given month.

For more information about pricing, see [Amazon RDS pricing](https://aws.amazon.com/rds/pricing/).

### Getting the best performance from Amazon RDS Provisioned IOPS storage
<a name="Overview.ProvisionedIOPS.gettingthemostoutofpiops"></a>

If your workload is I/O constrained, using Provisioned IOPS storage can increase the number of I/O requests that the system can process concurrently. Increased concurrency allows for decreased latency because I/O requests spend less time in a queue. Decreased latency allows for faster database commits, which improves response time and allows for higher database throughput.

Provisioned IOPS storage provides a way to reserve I/O capacity by specifying IOPS. However, as with any other system capacity attribute, its maximum throughput under load is constrained by the resource that is consumed first. That resource might be network bandwidth, CPU, memory, or database internal resources.

## General Purpose SSD storage
<a name="Concepts.Storage.GeneralSSD"></a>

General Purpose storage offers cost-effective storage that is acceptable for most database workloads that aren't latency or performance sensitive.

**Note**  
DB instances that use General Purpose storage can experience much longer latency than instances that use Provisioned IOPS storage. If you need a DB instance with minimum latency after these operations, we recommend using [Provisioned IOPS SSD storage](#USER_PIOPS).

Amazon RDS offers two types of General Purpose storage: [gp3 storage (recommended)](#gp3-storage) and [gp2 storage (previous generation)](#gp2-storage).

### gp3 storage (recommended)
<a name="gp3-storage"></a>

By using General Purpose gp3 storage volumes, you can customize storage performance independently of storage capacity. *Storage performance* is the combination of I/O operations per second (IOPS) and how fast the storage volume can perform reads and writes (storage throughput). On gp3 storage volumes, Amazon RDS provides a baseline storage performance of 3000 IOPS and 125 MiB/s.

For every RDS DB engine except RDS for SQL Server, when the storage size for gp3 volumes reaches a certain threshold, the baseline storage performance increases. This is because of *volume striping*, where the storage uses four volumes instead of one. RDS for SQL Server doesn't support volume striping, and therefore doesn't have a threshold value. For striped volumes, Amazon RDS provides a baseline storage performance of 12,000 IOPS and 500 MiB/s.

Storage performance for gp3 volumes on Amazon RDS DB engines, including the threshold per storage volume, is shown in the following table. In RDS for Oracle and SQL Server, you can attach up to three additional storage volumes in addition to the primary storage volume. You can provision up to 256 TiB storage size in total with three gp3 additional storage volumes in RDS for Oracle. You can provision up to 64 TiB storage size in total with three gp3 additional storage volumes in RDS for SQL Server because each gp3 storage volume can be sized up to 16 TiB. With additional storage volumes, you can have higher provisioned IOPS and maximum throughput for your DB instance. However, your DB instance might not be able to fully utilize the provisioned IOPS and maximum throughput if your instance class has lower limits than the values you've provisioned for your storage volumes. For more information, see [Factors that affect database performance](#CHAP_Storage.Other.Factors). 


| DB engine | Storage size | Baseline storage performance | Range of Provisioned IOPS | Range of provisioned storage throughput | 
| --- | --- | --- | --- | --- | 
| Db2, MariaDB, MySQL, and PostgreSQL | 20–399 GiB | 3,000 IOPS/125 MiB/s | N/A | N/A | 
| Db2, MariaDB, MySQL, and PostgreSQL | 400–65,536 GiB | 12,000 IOPS/500 MiB/s | 12,000–64,000 IOPS | 500–4,000 MiB/s | 
| Oracle | 20–199 GiB | 3,000 IOPS/125 MiB/s | N/A | N/A | 
| Oracle | 200–65,536 GiB  | 12,000 IOPS/500 MiB/s | 12,000–64,000 IOPS | 500–4,000 MiB/s | 
| SQL Server | 20–16,384 GiB | 3,000 IOPS/125 MiB/s | 3,000–16,000 IOPS | 125–1,000 MiB/s | 

For every DB engine except RDS for SQL Server, you can provision additional IOPS and storage throughput when storage size is at or above the threshold value. For RDS for SQL Server, you can provision additional IOPS and storage throughput for any available storage size. For all DB engines, you pay for only the additional provisioned storage performance. For more information, see [Amazon RDS pricing](https://aws.amazon.com/rds/pricing/).

Although the added Provisioned IOPS and storage throughput aren't dependent on the storage size, they are related to each other. When you raise the IOPS above 32,000 for MariaDB and MySQL, the storage throughput value automatically increases from 500 MiBps. For example, when you set the IOPS to 40,000 on RDS for MySQL, the storage throughput must be at least 625 MiBps. The automatic increase doesn't happen for Db2, Oracle, PostgreSQL, and SQL Server DB instances.

For Multi-AZ DB clusters, Amazon RDS automatically sets the throughput value based on the IOPS that you provision. You can't modify the throughput value.

Storage performance values for gp3 volumes on RDS have the following constraints:
+ The maximum ratio of storage throughput to IOPS is 0.25 for all supported DB engines.
+ The minimum ratio of IOPS to allocated storage (in GiB) is 0.5 on RDS for SQL Server. There is no minimum ratio for the other supported DB engines.
+ The maximum ratio of IOPS to allocated storage is 500 for all supported DB engines.
+ If you're using storage autoscaling, the same ratios between IOPS and maximum storage threshold (in GiB) also apply. 

  For more information on storage autoscaling, see [Managing capacity automatically with Amazon RDS storage autoscaling](USER_PIOPS.Autoscaling.md).

### gp2 storage (previous generation)
<a name="gp2-storage"></a>

When your applications don't need high storage performance, you can use General Purpose SSD gp2 storage. Baseline I/O performance for gp2 storage is 3 IOPS for each GiB, with a minimum of 100 IOPS. This relationship means that larger volumes have better performance. For example, baseline performance for one 100 GiB volume is 300 IOPS. Baseline performance for one 1,000 GiB volume is 3,000 IOPS.

Individual gp2 volumes below 1,000 GiB in size also have the ability to burst to 3,000 IOPS for extended periods of time. Volume I/O credit balance determines burst performance. For a more detailed description of how baseline performance and I/O credit balance affect performance, see the post [Understanding burst vs. baseline performance with Amazon RDS and gp2](https://aws.amazon.com/blogs/database/understanding-burst-vs-baseline-performance-with-amazon-rds-and-gp2/) on the AWS Database Blog.

Many workloads never deplete the burst balance. However, some workloads can exhaust the 3,000 IOPS burst storage credit balance, so plan your storage capacity to meet the needs of your workloads.

For gp2 volumes larger than 4,000 GiB, the baseline performance is greater than the burst performance. For such volumes, burst is irrelevant because the baseline performance is better than the 3,000 IOPS burst performance. However, for DB instances of certain engines and sizes, storage is *striped* across four volumes providing four times the baseline throughput, and four times the burst IOPS of a single volume.

Storage performance for gp2 volumes of various storage sizes on Amazon RDS DB engines is shown in the following table.


| DB engine | RDS storage size | Range of baseline IOPS | Range of baseline throughput | Burst IOPS | 
| --- | --- | --- | --- | --- | 
| MariaDB, MySQL, and PostgreSQL | 5–399 GiB | 100-1197 IOPS | 128-250 MiB/s | 3,000 | 
| MariaDB, MySQL, and PostgreSQL | 400–1,335 GiB  | 1,200-4,005 IOPS | 512-1,000 MiB/s | 12,000 | 
| MariaDB, MySQL, and PostgreSQL | 1,336–3,999 GiB  | 4008-11,997 IOPS | 1,000 MiB/s | 12,000 | 
| MariaDB, MySQL, and PostgreSQL | 4,000–65,536 GiB  | 12,000-64,000 IOPS | 1,000 MiB/s | N/A¹ | 
| Oracle | 20–199 GiB | 100-597 IOPS | 128-250 MiB/s | 3,000 | 
| Oracle | 200–1,335 GiB | 600-4,005 IOPS | 512-1,000 MiB/s | 12,000 | 
| Oracle | 1,336–3,999 GiB | 4008-11,997 IOPS | 1,000 MiB/s | 12,000 | 
| Oracle | 4,000–65,536 GiB | 12,000-64,000 IOPS | 1,000 MiB/s | N/A¹ | 
| SQL Server | 20–333 GiB | 100-999 IOPS | 128-250 MiB/s | 3,000 | 
| SQL Server | 334–999 GiB | 1,002-2,997 IOPS | 250 MiB/s | 3,000 | 
| SQL Server | 1,000–16,384 GiB | 3,000-16,000 IOPS | 250 MiB/s | N/A¹ | 

¹ The baseline performance of the volume exceeds the maximum burst performance.

## Performance characteristics of solid-state drive (SSD) storage types
<a name="storage-comparison"></a>

The following table describes use cases and per-volume performance characteristics for the SSD storage volumes used by Amazon RDS.


| Characteristic | Provisioned IOPS (io2 Block Express) | Provisioned IOPS (io1) | General Purpose (gp3) | General Purpose (gp2) | 
| --- | --- | --- | --- | --- | 
| Description |  Highest performance within the RDS storage portfolio (IOPS, throughput, latency) Designed for latency-sensitive, transactional workloads  |  Consistent storage performance (IOPS, throughput, latency) Designed for latency-sensitive, transactional workloads  |  Flexibility in provisioning storage, IOPS, and throughput independently Balances price performance for a wide variety of transactional workloads  |  Provides burstable IOPS Balances price performance for a wide variety of transactional workloads  | 
| Use cases |  Business-critical transactional workloads that require sub-millisecond latency and sustained IOPS performance up to 256,000 IOPS  |  Transactional workloads that require sustained IOPS performance up to 256,000 IOPS  |  Broad range of workloads running on medium-sized relational databases in development/test environments  |  Broad range of workloads running on medium-sized relational databases in development/test environments  | 
| Latency |  Sub-millisecond, provided consistently 99.9% of the time  |  Single-digit millisecond, provided consistently 99.9% of the time  |  Single-digit millisecond, provided consistently 99% of the time  |  Single-digit millisecond, provided consistently 99% of the time  | 
| Volume size |  100–65,536 GiB  |  100–65,536 GiB (20–16,384 GiB on RDS for SQL Server)  |  20–65,536 GiB (16,384 GiB on RDS for SQL Server)  |  20–65,536 GiB (16,384 GiB on RDS for SQL Server)  | 
| Maximum IOPS |  256,000  |  256,000 (64,000 on RDS for SQL Server)  |  64,000 (16,000 on RDS for SQL Server)  |  64,000 (16,000 on RDS for SQL Server)  You can't provision IOPS directly on gp2 storage. IOPS varies with the allocated storage size.   | 
| Maximum throughput |  Scales based on Provisioned IOPS up to 4,000 MB/s Throughput scales proportionally up to 0.256 MiB/s per provisioned IOPS. Maximum throughput of 4,000 MiB/s can be achieved at 256,000 IOPS with a 16-KiB I/O size and 16,000 IOPS or higher with a 256-KiB I/O size. For instances not based on the AWS Nitro System, maximum throughput of 2,000 MiB/s can be achieved at 128,000 IOPS with a 16-KiB I/O size.  |  Scales based on Provisioned IOPS up to 4,000 MB/s  |  Provision additional throughput up to 4,000 MB/s (1000 MB/s on RDS for SQL Server)  |  1000 MB/s (250 MB/s on RDS for SQL Server)  | 
| AWS CLI and RDS API name | io2 | io1 | gp3 | gp2 | 



### Automatic striping across SSD volumes
<a name="ssd-striping"></a>

When you select General Purpose SSD or Provisioned IOPS SSD, depending on the engine selected and the amount of storage requested, Amazon RDS automatically stripes across multiple volumes to enhance performance, as shown in the following table.


| Database engine | Amazon RDS storage size | Number of volumes provisioned | 
| --- | --- | --- | 
| Db2 | Less than 400 GiB | 1 | 
| Db2 | 400–65,536 GiB | 4 | 
| MariaDB, MySQL, and PostgreSQL | Less than 400 GiB | 1 | 
| MariaDB, MySQL, and PostgreSQL | 400–65,536 GiB | 4 | 
| Oracle | Less than 200 GiB | 1 | 
| Oracle | 200–65,536 GiB | 4 | 
| SQL Server | Any | 1 | 

### Performance impact when you modify an SSD volume
<a name="ssd-volume-mod"></a>

When you modify a General Purpose SSD or Provisioned IOPS SSD volume, it goes through a sequence of states. While the volume is in the `optimizing` state, your volume performance is between the source and target configuration specifications. Transitional volume performance will be no less than the lower of the two specifications.

When you modify an instance’s storage so that it goes from one volume to four volumes, or when you modify an instance using magnetic storage, Amazon RDS doesn't use the Elastic Volumes feature. Instead, Amazon RDS provisions new volumes and transparently moves the data from the old volume to the new volumes. This operation consumes a significant amount of IOPS and throughput of both the old and new volumes. Depending on the size of the volume and the amount of database workload present during the modification, this operation can consume a high amount of IOPS, significantly increase I/O latency, and take several hours to complete, while the RDS instance remains in the `Modifying` state.

### Baseline and maximum IOPS rates for EBS-optimized instances
<a name="baseline-max-iops-rate"></a>

EBS-optimized instances have a baseline and maximum IOPS rate. The maximum IOPS rate is enforced at the DB instance level. A set of EBS volumes that combine to have an IOPS rate that is higher than the maximum can't exceed the instance-level threshold. For example, if the maximum IOPS for a particular DB instance class is 40,000, and you attach four 64,000 IOPS EBS volumes, the maximum IOPS is 40,000 rather than 256,000. For the IOPS maximum specific to each EC2 instance type, see [Supported instance types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html#ebs-optimization-support) in the *Amazon EC2 User Guide for Linux Instances*.

## Magnetic storage (legacy, not recommended)
<a name="CHAP_Storage.Magnetic"></a>

**Warning**  
Amazon RDS is deprecating magnetic storage on April 30, 2026. We recommend that you upgrade your magnetic storage volumes to the latest SSD-based storage volumes (gp3 or io2) before April 29, 2026. After April 29, 2026, Amazon RDS will begin forced migration of magnetic storage volumes to gp3 storage volumes.  
In addition, the default storage type when restoring snapshots of magnetic volumes will be changed to gp3 by June 1, 2026. You can override this default with your preferred storage type.

Amazon RDS also supports magnetic storage for backward compatibility. We recommend that you use General Purpose SSD or Provisioned IOPS SSD for any new storage needs. The following are some limitations for magnetic storage:
+ Doesn't allow you to scale storage when using the SQL Server database engine.
+ Doesn't allow you to convert to a different storage type when using the SQL Server database engine.
+ Doesn't support storage autoscaling.
+ Doesn't support zero-ETL integrations with Amazon Redshift.
+ Doesn't support elastic volumes.
+ Limited to a maximum size of 3 TiB.
+ Limited to a maximum of 1,000 IOPS.

## Additional storage volumes
<a name="Welcome.AdditionalStorageVolumes"></a>

With RDS for Oracle and RDS for SQL Server, you can attach up to three additional storage volumes to your DB instance. Depending on your workload requirements, choose between gp3 and io2 storage for each volume.

Additional storage volumes provide the following benefits:
+ **Flexible storage configuration and performance optimization** – Mix different storage types (gp3 and io2) to optimize for both cost and performance based on your data access patterns. Separate frequently accessed data on high-performance io2 storage from archival data on cost-effective gp3 storage.
+ **Enhanced capacity** – Scale your total storage up to 256 TiB per DB instance by combining primary and additional storage volumes.
+ **Expand and reduce storage capacity as needed** – Create a volume when you need additional storage, as during data migration, and then later delete the volume. In this way, you can expand and reduce the total DB instance storage.
+ **Online data movement** – Use the built-in capabilities of Oracle Database to move data between volumes without downtime.

**Note**  
You can remove additional storage volumes but you can't remove the primary volume.

The additional volumes must use the volume names shown in the following table.


| RDS for Oracle volume name | RDS for SQL Server volume name | 
| --- | --- | 
| rdsdbdata2 | H: | 
| rdsdbdata3 | I: | 
| rdsdbdata4 | J: | 

For more information about working with additional storage volumes, see the following sections:
+ [Working with storage for Amazon RDS DB instances](USER_PIOPS.StorageTypes.md)
+ [Working with storage in RDS for Oracle](User_Oracle_AdditionalStorage.md)
+ [Working with storage in RDS for SQL Server](Appendix.SQLServer.CommonDBATasks.DatabaseStorage.md)

## Dedicated log volume (DLV)
<a name="CHAP_Storage.dlv"></a>

You can use a dedicated log volume (DLV) for a DB instance that uses Provisioned IOPS (PIOPS) storage by using the Amazon RDS console, AWS CLI, or Amazon RDS API. A DLV moves PostgreSQL database transaction logs and MySQL/MariaDB redo logs and binary logs to a storage volume that's separate from the volume containing the database tables. A DLV makes transaction write logging more efficient and consistent. DLVs are ideal for databases with large allocated storage, high I/O per second (IOPS) requirements, or latency-sensitive workloads.

DLVs are supported for PIOPS storage (io1 and io2 Block Express), and are created with a fixed size of 1,024 GiB and 3,000 Provisioned IOPS.

**Note**  
DLVs aren't supported for General Purpose storage (gp2 and gp3).

Amazon RDS supports DLVs in all AWS Regions for the following versions:
+ MariaDB 10.6.7 and higher 10 versions
+ MySQL 8.0.28 and higher 8.0 versions, MySQL 8.4.3 and higher 8.4 versions
+ PostgreSQL 13.10 and higher 13 versions, 14.7 and higher 14 versions, 15.2 and higher 15 versions, and 16.1 and higher 16 versions

RDS supports DLVs with Multi-AZ deployments. When you modify or create a Multi-AZ instance, A DLV is created for both the primary and the secondary.

RDS supports DLVs with read replicas. If the primary DB instance has a DLV enabled, all read replicas created after enabling DLV will also have a DLV. Any read replicas created before the switch to DLV will not have it enabled unless explicitly modified to do so. We recommend all read replicas attached to a primary instance before DLV was enabled also be manually modified to have A DLV.

After you modify the DLV setting for a DB instance, the DB instance must be rebooted.

For information on enabling a DLV, see [Using a dedicated log volume (DLV)](USER_PIOPS.dlv.md).

## Monitoring database performance
<a name="Concepts.Storage.Metrics"></a>

Amazon RDS provides several metrics that you can use to determine how your DB instance is performing. You can view the metrics on the summary page for your instance in Amazon RDS Management Console. You can also use Amazon CloudWatch to monitor these metrics. For more information, see [Viewing metrics in the Amazon RDS console](USER_Monitoring.md). Enhanced Monitoring provides more detailed I/O metrics; for more information, see [Monitoring OS metrics with Enhanced Monitoring](USER_Monitoring.OS.md).

The following metrics are useful for monitoring performance for your DB instance:
+ `DiskQueueDepth` – The number of I/O requests in the queue waiting to be serviced. These are I/O requests that have been submitted by the application but have not been sent to the device because the device is busy servicing other I/O requests. Time spent waiting in the queue is a component of latency and service time (not available as a metric). This metric is reported as the average queue depth for a given time interval. Amazon RDS reports queue depth at 1-minute intervals. Typical values for queue depth range from zero to several hundred.
+ `EBSByteBalance%` – The percentage of throughput credits remaining in the burst bucket of your RDS database. This metric is available for basic monitoring only. The metric value is based on the throughput of all volumes, including the root volume, rather than on only those volumes containing database files.

  When this metric approaches zero, it means that your DB instance is running out of computing capacity. If this happens regularly, consider upgrading to a larger instance class size, for example from db.r6g.large to db.r6g.xlarge. For more information, see [DB instance class](#other-factors-instance).
+ `ReadIOPS` and `WriteIOPS` – The number of I/O operations completed each second. This metric is reported as the average IOPS for a given time interval. Amazon RDS reports read and write IOPS separately at 1-minute intervals. `TotalIOPS` is the sum of the read and write IOPS. Typical values for IOPS range from zero to tens of thousands per second.

  If your `TotalIOPS` values regularly approach the Provisioned IOPS value that you have set for your DB instance, then consider increasing the Provisioned IOPS (io1, io2 Block Express, and gp3 storage types).

  Measured IOPS values are independent of the size of the individual I/O operation. This means that when you measure I/O performance, make sure to look at the throughput of the instance, not simply the number of I/O operations.
+ `ReadLatency` and `WriteLatency` – The elapsed time between the submission of an I/O request and its completion. This metric is reported as the average latency for a given time interval. Amazon RDS reports read and write latency separately at 1-minute intervals. Typical values for latency are in milliseconds (ms).
+ `ReadThroughput` and `WriteThroughput` – The number of bytes each second that are transferred to or from disk. This metric is reported as the average throughput for a given time interval. Amazon RDS reports read and write throughput separately at 1-minute intervals using units of bytes per second (B/s). Typical values for throughput range from zero to the I/O channel's maximum bandwidth.

  If your throughput values regularly approach the maximum throughput for your DB instance, then consider provisioning more storage throughput if you're using the gp3 storage type.

## Factors that affect database performance
<a name="CHAP_Storage.Other.Factors"></a>

System activities, database workload, and DB instance class can affect database performance.

**Topics**
+ [

### System activities
](#other-factors-system)
+ [

### Database workload
](#other-factors-workload)
+ [

### DB instance class
](#other-factors-instance)

### System activities
<a name="other-factors-system"></a>

The following system-related activities consume I/O capacity and might reduce DB instance performance while in progress:
+ Multi-AZ standby creation
+ Read replica creation
+ Changing storage types

### Database workload
<a name="other-factors-workload"></a>

In some cases, your database or application design results in concurrency issues, locking, or other forms of database contention. In these cases, you might not be able to use all the provisioned bandwidth directly. In addition, you might encounter the following workload-related situations:
+ The throughput limit of the underlying instance type is reached.
+ Queue depth is consistently less than 1 because your application isn't driving enough I/O operations.
+ You experience query contention in the database even though some I/O capacity is unused.

In some cases, there isn't a system resource that is at or near a limit, and adding threads doesn't increase the database transaction rate. In such cases, the bottleneck is most likely contention in the database. The most common forms are row lock and index page lock contention, but there are many other possibilities. If this is your situation, seek the advice of a database performance tuning expert.

### DB instance class
<a name="other-factors-instance"></a>

To get the most performance out of your Amazon RDS DB instance, choose a current generation instance type with enough bandwidth and IOPS to support your storage type. For example, you can choose Amazon EBS–optimized instances and instances with 10-gigabit network connectivity.

**Important**  
Depending on the instance class you're using, you might see lower bandwidth, throughput and IOPS performance than the maximum that you can provision with RDS. For specific information on bandwidth, throughput and IOPS performance for DB instance classes, see [Amazon EBS–optimized instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html) in the *Amazon EC2 User Guide*. We recommend that you determine the maximum bandwidth, throughput and IOPS for the instance class before setting a Provisioned IOPS and throughput value for your storage volumes in your DB instance.

We encourage you to use the latest generation of instances to get the best performance. Previous generation DB instances can also have lower maximum storage.

Some older 32-bit file systems might have lower storage capacities. To determine the storage capacity of your DB instance, you can use the [describe-valid-db-instance-modifications](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-valid-db-instance-modifications.html) AWS CLI command.

The following list shows the maximum storage that most DB instance classes can scale to for each database engine: 
+ Db2 – 64 TiB
+ MariaDB – 64 TiB
+ Microsoft SQL Server – 64 TiB
+ MySQL – 64 TiB
+ Oracle – 64 TiB
+ PostgreSQL – 64 TiB

The following table shows some exceptions for maximum storage (in TiB). All RDS for Microsoft SQL Server DB instances apart from io2 Block Express storage have a maximum storage of 16 TiB, so there are no entries for SQL Server. 


| Instance class | Db2 | MariaDB | MySQL | Oracle | PostgreSQL | 
| --- | --- | --- | --- | --- | --- | 
| db.m3 – standard instance classes | 
| db.t4g – burstable-performance instance classes | 
| db.t4g.medium | N/A | 16 | 16 | N/A | 32 | 
| db.t4g.small | N/A | 16 | 16 | N/A | 16 | 
| db.t4g.micro | N/A | 6 | 6 | N/A | 6 | 
| db.t3 – burstable-performance instance classes | 
| db.t3.medium | 32 | 16 | 16 | 32 | 32 | 
| db.t3.small | 32 | 16 | 16 | 32 | 16 | 
| db.t3.micro | N/A | 6 | 6 | 32 | 6 | 
| db.t2 – burstable-performance instance classes | 

For more details about all instance classes supported, see [Previous generation DB instances](https://aws.amazon.com/rds/previous-generation/).

# Regions, Availability Zones, and Local Zones
<a name="Concepts.RegionsAndAvailabilityZones"></a>

Amazon cloud computing resources are hosted in multiple locations world-wide. These locations are composed of AWS Regions, Availability Zones, and Local Zones. Each *AWS Region* is a separate geographic area. Each AWS Region has multiple, isolated locations known as *Availability Zones*.

**Note**  
For information about finding the Availability Zones for an AWS Region, see [Describe your Availability Zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#availability-zones-describe) in the Amazon EC2 documentation.

By using Local Zones, you can place resources, such as compute and storage, in multiple locations closer to your users. Amazon RDS enables you to place resources, such as DB instances, and data in multiple locations. Resources aren't replicated across AWS Regions unless you do so specifically.

Amazon operates state-of-the-art, highly-available data centers. Although rare, failures can occur that affect the availability of DB instances that are in the same location. If you host all your DB instances in one location that is affected by such a failure, none of your DB instances will be available.

![\[AWS Region\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/Con-AZ-Local.png)


It is important to remember that each AWS Region is completely independent. Any Amazon RDS activity you initiate (for example, creating database instances or listing available database instances) runs only in your current default AWS Region. The default AWS Region can be changed in the console, or by setting the [https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-region](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-region) environment variable. Or it can be overridden by using the `--region` parameter with the AWS Command Line Interface (AWS CLI). For more information, see [Configuring the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html), specifically the sections about environment variables and command line options. 

Amazon RDS supports special AWS Regions called AWS GovCloud (US). These are designed to allow US government agencies and customers to move more sensitive workloads into the cloud. The AWS GovCloud (US) Regions address the US government's specific regulatory and compliance requirements. For more information, see [What is AWS GovCloud (US)?](https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html) 

To create or work with an Amazon RDS DB instance in a specific AWS Region, use the corresponding regional service endpoint.

## AWS Regions
<a name="Concepts.RegionsAndAvailabilityZones.Regions"></a>

Each AWS Region is designed to be isolated from the other AWS Regions. This design achieves the greatest possible fault tolerance and stability.

When you view your resources, you see only the resources that are tied to the AWS Region that you specified. This is because AWS Regions are isolated from each other, and we don't automatically replicate resources across AWS Regions.

### Region availability
<a name="Concepts.RegionsAndAvailabilityZones.Availability"></a>

The following table shows the AWS Regions where Amazon RDS is currently available and the endpoint for each Region.

[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html)

If you do not explicitly specify an endpoint, the US West (Oregon) endpoint is the default.

When you work with a DB instance using the AWS CLI or API operations, make sure that you specify its regional endpoint.

## Availability Zones
<a name="Concepts.RegionsAndAvailabilityZones.AvailabilityZones"></a>

When you create a DB instance, you can choose an Availability Zone or have Amazon RDS choose one for you randomly. An Availability Zone is represented by an AWS Region code followed by a letter identifier (for example, `us-east-1a`).

Use the [describe-availability-zones](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-availability-zones.html) Amazon EC2 command as follows to describe the Availability Zones within the specified Region that are enabled for your account.

```
aws ec2 describe-availability-zones --region region-name
```

For example, to describe the Availability Zones within the US East (N. Virginia) Region (us-east-1) that are enabled for your account, run the following command:

```
aws ec2 describe-availability-zones --region us-east-1
```

You can't choose the Availability Zones for the primary and secondary DB instances in a Multi-AZ DB deployment. Amazon RDS chooses them for you randomly. For more information about Multi-AZ deployments, see [Configuring and managing a Multi-AZ deployment for Amazon RDS](Concepts.MultiAZ.md).

**Note**  
Random selection of Availability Zones by RDS doesn't guarantee an even distribution of DB instances among Availability Zones within a single account or DB subnet group. You can request a specific AZ when you create or modify a Single-AZ instance, and you can use more-specific DB subnet groups for Multi-AZ instances. For more information, see [Creating an Amazon RDS DB instance](USER_CreateDBInstance.md) and [Modifying an Amazon RDS DB instance](Overview.DBInstance.Modifying.md).

## Local Zones
<a name="Concepts.RegionsAndAvailabilityZones.LocalZones"></a>

A *Local Zone* is an extension of an AWS Region that is geographically close to your users. You can extend any VPC from the parent AWS Region into Local Zones. To do so, create a new subnet and assign it to the AWS Local Zone. When you create a subnet in a Local Zone, your VPC is extended to that Local Zone. The subnet in the Local Zone operates the same as other subnets in your VPC.

When you create a DB instance, you can choose a subnet in a Local Zone. Local Zones have their own connections to the internet and support Direct Connect. Thus, resources created in a Local Zone can serve local users with very low-latency communications. For more information, see [AWS Local Zones](https://aws.amazon.com/about-aws/global-infrastructure/localzones/).

A Local Zone is represented by an AWS Region code followed by an identifier that indicates the location, for example `us-west-2-lax-1a`.

**Note**  
A Local Zone can't be included in a Multi-AZ deployment.

**To use a Local Zone**

1. Enable the Local Zone in the Amazon EC2 console.

   For more information, see [Enabling Local Zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#enable-zone-group) in the *Amazon EC2 User Guide.*

1. Create a subnet in the Local Zone.

   For more information, see [Creating a subnet in your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet) in the *Amazon VPC User Guide.*

1. Create a DB subnet group in the Local Zone.

   When you create a DB subnet group, choose the Availability Zone group for the Local Zone.

   For more information, see [Creating a DB instance in a VPC](USER_VPC.WorkingWithRDSInstanceinaVPC.md#USER_VPC.InstanceInVPC).

1. Create a DB instance that uses the DB subnet group in the Local Zone.

   For more information, see [Creating an Amazon RDS DB instance](USER_CreateDBInstance.md).

**Important**  
Currently, the only AWS Local Zone where Amazon RDS is available is Los Angeles in the US West (Oregon) Region.

# Supported features in Amazon RDS by AWS Region and DB engine
<a name="Concepts.RDSFeaturesRegionsDBEngines.grids"></a>

Support for Amazon RDS features and options varies across AWS Regions and specific versions of each DB engine. To identify RDS DB engine version support and availability in a given AWS Region, you can use the following sections.

Amazon RDS features are different from engine-native features and options. For more information on engine-native features and options, see [Engine-native features.](Concepts.RDS_Fea_Regions_DB-eng.Feature.EngineNativeFeatures.md)

**Topics**
+ [

## Table conventions
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.TableConventions)
+ [

## Feature quick reference
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.QuickReferenceTable)
+ [Blue/Green Deployments](Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.md)
+ [Cross-Region automated backups](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.md)
+ [Cross-Region read replicas](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.md)
+ [Database activity streams](Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.md)
+ [Dual-stack mode](Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.md)
+ [Export snapshots to S3](Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.md)
+ [IAM database authentication](Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.md)
+ [Kerberos authentication](Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.md)
+ [Multi-AZ DB clusters](Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.md)
+ [Performance Insights](Concepts.RDS_Fea_Regions_DB-eng.Feature.PerformanceInsights.md)
+ [RDS Custom](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.md)
+ [Amazon RDS Proxy](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSProxy.md)
+ [Secrets Manager integration](Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager.md)
+ [Zero-ETL integrations](Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.md)
+ [Engine-native features](Concepts.RDS_Fea_Regions_DB-eng.Feature.EngineNativeFeatures.md)

## Table conventions
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.TableConventions"></a>

The tables in the feature sections use these patterns to specify version numbers and level of availability:
+  **Version x.y** – The specific version alone is available. 
+ **Version x.y and higher** – The specified version and all higher minor versions of its major version are supported. For example, "version 10.11 and higher" means that versions 10.11, 10.11.1, and 10.12 are available.

## Feature quick reference
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.QuickReferenceTable"></a>

The following quick reference table lists each feature and available RDS DB engine. Region and specific version availability appears in the later feature sections.


| Feature | RDS for Db2 | RDS for MariaDB | RDS for MySQL | RDS for Oracle | RDS for PostgreSQL | RDS for SQL Server | 
| --- | --- | --- | --- | --- | --- | --- | 
| Blue/Green Deployments | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.md) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.md) | Not available | 
| Cross-Region automated backups | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.db2) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.mdb) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.my) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.ora) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.pg) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.sq) | 
| Cross-Region read replicas | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.mdb) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.my) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.ora) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.pg) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.sq) | 
| Database activity streams | Not available | Not available | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.ora) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.SQLServer) | 
| Dual-stack mode | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.mdb) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.my) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.ora) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.pg) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.sq) | 
| Export Snapshot to Amazon S3 | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.mdb) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.my) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.pg) | Not available | 
| AWS Identity and Access Management (IAM) database authentication | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.mdb) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.my) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.pg) | Not available | 
| Kerberos authentication | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.my) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.my) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.ora) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.pg) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.sq) | 
| Multi-AZ DB clusters | Not available | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.my) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.pg) | Not available | 
| Performance Insights | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.PerformanceInsights.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.PerformanceInsights.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.PerformanceInsights.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.PerformanceInsights.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.PerformanceInsights.md) | 
| RDS Custom | Not available | Not available | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.ora) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.sq) | 
| RDS Proxy | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSProxy.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.mdb) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSProxy.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.my) | Not available | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSProxy.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.pg) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSProxy.md#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.sq) | 
| Secrets Manager integration | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager.md) | [Available](Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager.md) | 

# Supported Regions and DB engines for Amazon RDS Blue/Green Deployments
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments"></a>

A blue/green deployment copies a production database environment in a separate, synchronized staging environment. By using Amazon RDS Blue/Green Deployments, you can make changes to the database in the staging environment without affecting the production environment. For example, you can upgrade the major or minor DB engine version, change database parameters, or make schema changes in the staging environment. When you are ready, you can promote the staging environment to be the new production database environment. For more information, see [Using Amazon RDS Blue/Green Deployments for database updates](blue-green-deployments.md).

Blue/green deployments are supported in all AWS Regions.

Blue/green deployments are *not* supported with the following engines:
+ RDS for Db2
+ RDS for SQL Server
+ RDS for Oracle

**Topics**
+ [

## Blue/green deployments with RDS for MariaDB
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.mdb)
+ [

## Blue/green deployments with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.mysql)
+ [

## Blue/green deployments with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.postgres)

## Blue/green deployments with RDS for MariaDB
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.mdb"></a>

For RDS for MariaDB, blue/green deployments are supported for the following versions:
+ RDS for MariaDB 11.8 (All available versions)
+ RDS for MariaDB 11.4 (All available versions)
+ RDS for MariaDB 10.2 and higher 10 versions

## Blue/green deployments with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.mysql"></a>

For RDS for MySQL, blue/green deployments are supported for the following versions:
+ RDS for MySQL 8.4 (All available versions) 
+ RDS for MySQL 8.0 (All available versions) 
+ RDS for MySQL 5.7 (All available versions) 

## Blue/green deployments with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.BlueGreenDeployments.postgres"></a>

For RDS for PostgreSQL, blue/green deployments are supported for version 11.1 and all higher major and minor versions. 

**Note**  
Under certain conditions, RDS for PostgreSQL uses logical replication instead of physical replication to keep the green environment in sync with the blue environment. For more information, see [PostgreSQL replication methods for blue/green deployments](blue-green-deployments-replication-type.md).

# Supported Regions and DB engines for cross-Region automated backups in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups"></a>

By using backup replication in Amazon RDS, you can configure your RDS DB instance to replicate snapshots and transaction logs to a destination Region. When backup replication is configured for a DB instance, RDS starts a cross-Region copy of all snapshots and transaction logs when they're ready. For more information, see [Replicating automated backups to another AWS Region](USER_ReplicateBackups.md).

For information about AWS Regions where backup replication is available, see [Replicating automated backups to another AWS Region](USER_ReplicateBackups.md).

**Topics**
+ [

## Backup replication with RDS for Db2
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.db2)
+ [

## Backup replication with RDS for MariaDB
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.mdb)
+ [

## Backup replication with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.my)
+ [

## Backup replication with RDS for Oracle
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.ora)
+ [

## Backup replication with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.pg)
+ [

## Backup replication with RDS for SQL Server
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.sq)

## Backup replication with RDS for Db2
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.db2"></a>

Amazon RDS supports backup replication for all currently available versions of RDS for Db2.

## Backup replication with RDS for MariaDB
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.mdb"></a>

Amazon RDS supports backup replication for all currently available versions of RDS for MariaDB.

## Backup replication with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.my"></a>

Amazon RDS supports backup replication for all currently available versions of RDS for MySQL.

## Backup replication with RDS for Oracle
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.ora"></a>

Amazon RDS supports backup replication for all currently available versions of RDS for Oracle.

## Backup replication with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.pg"></a>

Amazon RDS supports backup replication for all currently available versions of RDS for PostgreSQL.

## Backup replication with RDS for SQL Server
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionAutomatedBackups.sq"></a>

Amazon RDS supports backup replication for all currently available versions of RDS for SQL Server.

# Supported Regions and DB engines for cross-Region read replicas in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas"></a>

By using cross-Region read replicas in Amazon RDS, you can create a MariaDB, MySQL, Oracle, PostgreSQL, SQL Server, or Db2 read replica in a different Region from the source DB instance. For more information about cross-Region read replicas, including source and destination Region considerations, see [Creating a read replica in a different AWS Region](USER_ReadRepl.XRgn.md).

**Topics**
+ [

## Cross-Region read replicas with RDS for MariaDB
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.mdb)
+ [

## Cross-Region read replicas with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.my)
+ [

## Cross-Region read replicas with RDS for Oracle
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.ora)
+ [

## Cross-Region read replicas with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.pg)
+ [

## Cross-Region read replicas with RDS for SQL Server
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.sq)
+ [

## Cross-Region read replicas with RDS for Db2
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.db2)

## Cross-Region read replicas with RDS for MariaDB
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.mdb"></a>

Cross-Region read replicas with RDS for MariaDB are available in all Regions for the following versions:
+ RDS for MariaDB 11.8 (All available versions)
+ RDS for MariaDB 11.4 (All available versions)
+ RDS for MariaDB 10.11 (All available versions)
+ RDS for MariaDB 10.6 (All available versions)
+ RDS for MariaDB 10.5 (All available versions)
+ RDS for MariaDB 10.4 (All available versions)

## Cross-Region read replicas with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.my"></a>

Cross-Region read replicas with RDS for MySQL are available in all Regions for the following versions:
+ RDS for MySQL 8.4 (All available versions)
+ RDS for MySQL 8.0 (All available versions)
+ RDS for MySQL 5.7 (All available versions)

## Cross-Region read replicas with RDS for Oracle
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.ora"></a>

Cross-Region read replicas for RDS for Oracle are available in all AWS Regions for all supported database versions using Enterprise Edition. Replicas are supported only in non-CDBs and in the single-tenant configuration of the CDB architecture. Cross-Region read replicas aren't supported in the multi-tenant configuration of the CDB architecture. 

For more information on additional requirements for cross-Region read replicas with RDS for Oracle, see [Requirements and considerations for RDS for Oracle replicas](oracle-read-replicas.limitations.md). 

## Cross-Region read replicas with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.pg"></a>

Cross-Region read replicas with RDS for PostgreSQL are available in all Regions for the following versions:
+ RDS for PostgreSQL 18 (All available versions)
+ RDS for PostgreSQL 17 (All available versions)
+ RDS for PostgreSQL 16 (All available versions)
+ RDS for PostgreSQL 15 (All available versions)
+ RDS for PostgreSQL 14 (All available versions)
+ RDS for PostgreSQL 13 (All available versions)
+ RDS for PostgreSQL 12 (All available versions)
+ RDS for PostgreSQL 11 (All available versions)
+ RDS for PostgreSQL 10 (All available versions)

## Cross-Region read replicas with RDS for SQL Server
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.sq"></a>

Cross-Region read replicas with RDS for SQL Server are available in all Regions for the following versions using Microsoft SQL Server Enterprise Edition:
+ RDS for SQL Server 2022
+ RDS for SQL Server 2019 (Version 15.00.4073.23 and higher)
+ RDS for SQL Server 2017 (Version 14.00.3281.6 and higher)
+ RDS for SQL Server 2016 (Version 13.00.6300.2 and higher)

## Cross-Region read replicas with RDS for Db2
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.CrossRegionReadReplicas.db2"></a>

Cross-Region read replicas with RDS for Db2 are available in all Regions for the following versions:
+ RDS for Db2 11.5.9 (All available versions)

# Supported Regions and DB engines for database activity streams in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams"></a>

 By using database activity streams in Amazon RDS, you can monitor and set alarms for auditing activity in your Oracle database and SQL Server database. For more information, see [Overview of Database Activity Streams](DBActivityStreams.md#DBActivityStreams.Overview).

Database activity streams aren't available with the following engines:
+ RDS for Db2
+ RDS for MariaDB
+ RDS for MySQL
+ RDS for PostgreSQL

**Topics**
+ [

## Database activity streams with RDS for Oracle
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.ora)
+ [

## Database activity streams with RDS for SQL Server
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.SQLServer)

## Database activity streams with RDS for Oracle
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.ora"></a>

The following Regions and engine versions are available for database activity streams with RDS for Oracle.

For more information on additional requirements for database activity streams with RDS for Oracle, see [Overview of Database Activity Streams](DBActivityStreams.md#DBActivityStreams.Overview).


| Region | RDS for Oracle 21c | RDS for Oracle 19c | 
| --- | --- | --- | 
| US East (N. Virginia) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| US East (Ohio) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| US West (N. California) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| US West (Oregon) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Africa (Cape Town) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Hong Kong) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Hyderabad) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Jakarta) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Malaysia) | Not available | Not available | 
| Asia Pacific (Melbourne) | Not available | Not available | 
| Asia Pacific (Mumbai) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (New Zealand) | Not available | Not available | 
| Asia Pacific (Osaka) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Seoul) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Singapore) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Sydney) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Asia Pacific (Taipei) | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | 
| Asia Pacific (Tokyo) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Canada (Central) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Canada West (Calgary) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| China (Beijing) | Not available | Not available | 
| China (Ningxia) | Not available | Not available | 
| Europe (Frankfurt) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Europe (Ireland) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Europe (London) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Europe (Milan) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Europe (Paris) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Europe (Spain) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Europe (Stockholm) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Europe (Zurich) | Not available | Not available | 
| Asia Pacific (Melbourne) | Not available | Not available | 
| Mexico (Central) | Not available | Not available | 
| Middle East (Bahrain) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| Middle East (UAE) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| South America (São Paulo) | Not available | Oracle Database 19.0.0.0.ru-2019-07.rur-2019-07.r1 and higher, using either Enterprise Edition (EE) or Standard Edition 2 (SE2) | 
| AWS GovCloud (US-East) | Not available | Not available | 
| AWS GovCloud (US-West) | Not available | Not available | 

## Database activity streams with RDS for SQL Server
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DBActivityStreams.SQLServer"></a>

The following Regions and engine versions are available for database activity streams with RDS for SQL Server.

For more information on additional requirements for database activity streams with RDS for SQL Server, see [Overview of Database Activity Streams](DBActivityStreams.md#DBActivityStreams.Overview).


| Region | RDS for SQL Server 2019 | RDS for SQL Server 2017 | RDS for SQL Server 2016 | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | Not available | Not available | Not available | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | 
| China (Beijing) | Not available | Not available | Not available | 
| China (Ningxia) | Not available | Not available | Not available | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | 
| Europe (Zurich) | Not available | Not available | Not available | 
| Israel (Tel Aviv) | Not available | Not available | Not available | 
| Mexico (Central) | Not available | Not available | Not available | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | Not available | Not available | Not available | 
| AWS GovCloud (US-West) | Not available | Not available | Not available | 

# Supported Regions and DB engines for dual-stack mode in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode"></a>

By using dual-stack mode in RDS, resources can communicate with a DB instance over Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), or both. For more information, see [Dual-stack mode](USER_VPC.WorkingWithRDSInstanceinaVPC.md#USER_VPC.IP_addressing.dual-stack-mode).

**Topics**
+ [

## Dual-stack mode with RDS for Db2
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.db2)
+ [

## Dual-stack mode with RDS for MariaDB
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.mdb)
+ [

## Dual-stack mode with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.my)
+ [

## Dual-stack mode with RDS for Oracle
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.ora)
+ [

## Dual-stack mode with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.pg)
+ [

## Dual-stack mode with RDS for SQL Server
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.sq)

## Dual-stack mode with RDS for Db2
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.db2"></a>

The following Regions and engine versions are available for dual-stack mode with RDS for Db2.


| Region | RDS for Db2 11.5 | 
| --- | --- | 
| US East (N. Virginia) | All available versions | 
| US East (Ohio) | All available versions | 
| US West (N. California) | All available versions | 
| US West (Oregon) | All available versions | 
| Africa (Cape Town) | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | 
| Asia Pacific (Hyderabad) | Not available | 
| Asia Pacific (Jakarta) | All available versions | 
| Asia Pacific (Malaysia) | All available versions | 
| Asia Pacific (Melbourne) | Not available | 
| Asia Pacific (Mumbai) | All available versions | 
| Asia Pacific (New Zealand) | Not available | 
| Asia Pacific (Osaka) | All available versions | 
| Asia Pacific (Seoul) | All available versions | 
| Asia Pacific (Singapore) | All available versions | 
| Asia Pacific (Sydney) | All available versions | 
| Asia Pacific (Taipei) | All available versions | 
| Asia Pacific (Thailand) | All available versions | 
| Asia Pacific (Tokyo) | All available versions | 
| Canada (Central) | All available versions | 
| Canada West (Calgary) | All available versions | 
| China (Beijing) | Not available | 
| China (Ningxia) | Not available | 
| Europe (Frankfurt) | All available versions | 
| Europe (Ireland) | All available versions | 
| Europe (London) | All available versions | 
| Europe (Milan) | All available versions | 
| Europe (Paris) | All available versions | 
| Europe (Spain) | Not available | 
| Europe (Stockholm) | All available versions | 
| Europe (Zurich) | Not available | 
| Israel (Tel Aviv) | All available versions | 
| Mexico (Central) | All available versions | 
| Middle East (Bahrain) | All available versions | 
| Middle East (UAE) | All available versions | 
| South America (São Paulo) | All available versions | 
| AWS GovCloud (US-East) | Not available | 
| AWS GovCloud (US-West) | Not available | 

## Dual-stack mode with RDS for MariaDB
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.mdb"></a>

The following Regions and engine versions are available for dual-stack mode with RDS for MariaDB.


| Region | RDS for MariaDB 11.8 | RDS for MariaDB 11.4 | RDS for MariaDB 10.11 | RDS for MariaDB 10.6 | RDS for MariaDB 10.5 | RDS for MariaDB 10.4 | 
| --- | --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 

## Dual-stack mode with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.my"></a>

The following Regions and engine versions are available for dual-stack mode with RDS for MySQL.


| Region | RDS for MySQL 8.4 | RDS for MySQL 8.0 | RDS for MySQL 5.7 (under RDS Extended Support) | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | Not available | Not available | Not available | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | Not available | Not available | Not available | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | 
| Europe (Spain) | Not available | Not available | Not available | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | 
| Europe (Zurich) | Not available | Not available | Not available | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | 
| Middle East (UAE) | Not available | Not available | Not available | 
| South America (São Paulo) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | 

## Dual-stack mode with RDS for Oracle
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.ora"></a>

The following Regions and engine versions are available for dual-stack mode with RDS for Oracle.


| Region | RDS for Oracle 21c | RDS for Oracle 19c | 
| --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | 

## Dual-stack mode with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.pg"></a>

The following Regions and engine versions are available for dual-stack mode with RDS for PostgreSQL.


| Region | RDS for PostgreSQL 18 | RDS for PostgreSQL 17 | RDS for PostgreSQL 16 | RDS for PostgreSQL 15 | RDS for PostgreSQL 14 | RDS for PostgreSQL 13 | RDS for PostgreSQL 12 | RDS for PostgreSQL 11 | RDS for PostgreSQL 10 | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 

## Dual-stack mode with RDS for SQL Server
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.DualStackMode.sq"></a>

The following Regions and engine versions are available for dual-stack mode with RDS for SQL Server.


| Region | RDS for SQL Server 2019 | RDS for SQL Server 2017 | RDS for SQL Server 2016 | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | 

# Supported Regions and DB engines for exporting snapshots to S3 in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3"></a>

You can export RDS DB snapshot data to an Amazon S3 bucket. You can export all types of DB snapshots—including manual snapshots, automated system snapshots, and snapshots created by AWS Backup. After the data is exported, you can analyze the exported data directly through tools like Amazon Athena or Amazon Redshift Spectrum. For more information, see [Exporting DB snapshot data to Amazon S3 for Amazon RDS](USER_ExportSnapshot.md). 

Exporting snapshots to S3 is not available for the following engines:
+ RDS for Db2
+ RDS for Oracle
+ RDS for SQL Server

**Topics**
+ [

## Export snapshots to S3 with RDS for MariaDB
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.mdb)
+ [

## Export snapshots to S3 with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.my)
+ [

## Export snapshots to S3 with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.pg)

## Export snapshots to S3 with RDS for MariaDB
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.mdb"></a>

The following Regions and engine versions are available for exporting snapshots to S3 with RDS for MariaDB.


| Region | RDS for MariaDB 11.8 | RDS for MariaDB 11.4 | RDS for MariaDB 10.11 | RDS for MariaDB 10.6 | RDS for MariaDB 10.5 | RDS for MariaDB 10.4 | 
| --- | --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 

## Export snapshots to S3 with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.my"></a>

The following Regions and engine versions are available for exporting snapshots to S3 with RDS for MySQL.


| Region | RDS for MySQL 8.4 | RDS for MySQL 8.0 | RDS for MySQL 5.7 (under RDS Extended Support) | 
| --- | --- | --- | --- | 
| US East (Ohio) | All available versions | All available versions | All available versions | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | All available versions | All available versions | All available versions | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | 

## Export snapshots to S3 with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ExportSnapshotToS3.pg"></a>

The following Regions and engine versions are available for exporting snapshots to S3 with RDS for PostgreSQL.


| Region | RDS for PostgreSQL 18 | RDS for PostgreSQL 17 | RDS for PostgreSQL 16 | RDS for PostgreSQL 15 | RDS for PostgreSQL 14 | RDS for PostgreSQL 13 | RDS for PostgreSQL 12 | RDS for PostgreSQL 11 | RDS for PostgreSQL 10 | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| US East (Ohio) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 

# Supported Regions and DB engines for IAM database authentication in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication"></a>

By using IAM database authentication in Amazon RDS, you can authenticate without a password when you connect to a DB instance. Instead, you use an authentication token. For more information, see [IAM database authentication for MariaDB, MySQL, and PostgreSQL](UsingWithRDS.IAMDBAuth.md). 

IAM database authentication isn't available with the following engines: 
+ RDS for Db2
+ RDS for Oracle
+ RDS for SQL Server

**Topics**
+ [

## IAM database authentication with RDS for MariaDB
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.mdb)
+ [

## IAM database authentication with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.my)
+ [

## IAM database authentication with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.pg)

## IAM database authentication with RDS for MariaDB
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.mdb"></a>

The following Regions and engine versions are available for IAM database authentication with RDS for MariaDB.


| Region | RDS for MariaDB 11.8 | RDS for MariaDB 11.4 | RDS for MariaDB 10.11 | RDS for MariaDB 10.6 | RDS for MariaDB 10.5 | RDS for MariaDB 10.4 | 
| --- | --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| US East (Ohio) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| US West (N. California) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| US West (Oregon) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (Hyderabad) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (Malaysia) | All available versions | All available versions | Not available | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (New Zealand) | All available versions | All available versions | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Asia Pacific (Taipei) | All available versions | All available versions | Not available | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | All available versions | All available versions | Not available | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Canada (Central) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| China (Beijing) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| China (Ningxia) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Europe (Ireland) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Europe (London) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Europe (Milan) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Europe (Paris) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Europe (Spain) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Europe (Zurich) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Israel (Tel Aviv) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Mexico (Central) | All available versions | All available versions | Not available | Not available | Not available | Not available | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| Middle East (UAE) | Not available | Not available | Not available | Not available | Not available | Not available | 
| South America (São Paulo) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | Not available | Not available | Not available | 

## IAM database authentication with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.my"></a>

IAM database authentication with RDS for MySQL is available in all Regions for the following versions:
+ RDS for MySQL 8.4 – All available versions
+ RDS for MySQL 8.0 – All available versions
+ RDS for MySQL 5.7 – All available versions

## IAM database authentication with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.IamDatabaseAuthentication.pg"></a>

IAM database authentication with RDS for PostgreSQL is available in all Regions for the following versions:
+ RDS for PostgreSQL 18 – All available versions
+ RDS for PostgreSQL 17 – All available versions
+ RDS for PostgreSQL 16 – All available versions
+ RDS for PostgreSQL 15 – All available versions
+ RDS for PostgreSQL 14 – All available versions
+ RDS for PostgreSQL 13 – All available versions
+ RDS for PostgreSQL 12 – All available versions
+ RDS for PostgreSQL 11 – All available versions
+ RDS for PostgreSQL 10 – All available versions

# Supported Regions and DB engines for Kerberos authentication in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication"></a>

By using Kerberos authentication in Amazon RDS, you can support external authentication of database users using Kerberos and Microsoft Active Directory. Using Kerberos and Active Directory provides the benefits of single sign-on and centralized authentication of database users.

Kerberos authentication isn't available with the following engines:
+ RDS for MariaDB

Although most AWS Regions are active by default for your AWS account, certain Regions are activated only when you manually select them. These Regions are referred to as *opt-in Regions*. In contrast, Regions that are active by default, as soon as your AWS account is created, are referred to as *commercial Regions*, or simply, *Regions*. For opt-in Regions, you must use a regionalized service principal of the form `directoryservice.rds.region_name.amazonaws.com`. For example, for Africa (Cape Town), you must add service principal `directoryservice.rds.af-south-1.amazonaws.com` to your trust policy. For more information, see [Kerberos authentication](database-authentication.md#kerberos-authentication).

**Topics**
+ [

## Kerberos authentication with RDS for Db2
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.db2)
+ [

## Kerberos authentication with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.my)
+ [

## Kerberos authentication with RDS for Oracle
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.ora)
+ [

## Kerberos authentication with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.pg)
+ [

## Kerberos authentication with RDS for SQL Server
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.sq)

## Kerberos authentication with RDS for Db2
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.db2"></a>

The following Regions and engine versions are available for Kerberos authentication with RDS for Db2.


| Region | RDS for Db2 11.5 | 
| --- | --- | 
| US East (N. Virginia) | All versions | 
| US East (Ohio) | All versions | 
| US West (N. California) | All versions | 
| US West (Oregon) | All versions | 
| Africa (Cape Town) | All versions | 
| Asia Pacific (Hong Kong) | Not available | 
| Asia Pacific (Hyderabad) | All versions | 
| Asia Pacific (Jakarta) | All versions | 
| Asia Pacific (Malaysia) | Not available | 
| Asia Pacific (Melbourne) | All versions | 
| Asia Pacific (Mumbai) | All versions | 
| Asia Pacific (New Zealand) | Not available | 
| Asia Pacific (Osaka) | Not available | 
| Asia Pacific (Seoul) | All versions | 
| Asia Pacific (Singapore) | All versions | 
| Asia Pacific (Sydney) | All versions | 
| Asia Pacific (Taipei) | Not available | 
| Asia Pacific (Thailand) | Not available | 
| Asia Pacific (Tokyo) | All versions | 
| Canada (Central) | All versions | 
| Canada West (Calgary) | Not available | 
| China (Beijing) | Not available | 
| China (Ningxia) | Not available | 
| Europe (Frankfurt) | All versions | 
| Europe (Ireland) | All versions | 
| Europe (London) | All versions | 
| Europe (Milan) | All versions | 
| Europe (Paris) | Not available | 
| Europe (Spain) | All versions | 
| Europe (Stockholm) | All versions | 
| Europe (Zurich) | All versions | 
| Israel (Tel Aviv) | All versions | 
| Mexico (Central) | Not available | 
| Middle East (Bahrain) | All versions | 
| Middle East (UAE) | All versions | 
| South America (São Paulo) | All versions | 
| AWS GovCloud (US-East) | Not available | 
| AWS GovCloud (US-West) | Not available | 

## Kerberos authentication with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.my"></a>

The following Regions and engine versions are available for Kerberos authentication with RDS for MySQL.


| Region | RDS for MySQL 8.4 | RDS for MySQL 8.0 | RDS for MySQL 5.7 (under RDS Extended Support) | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | All versions | All versions | All versions | 
| US East (Ohio) | All versions | All versions | All versions | 
| US West (N. California) | All versions | All versions | All versions | 
| US West (Oregon) | All versions | All versions | All versions | 
| Africa (Cape Town) | All versions | All versions | All versions | 
| Asia Pacific (Hong Kong) | All versions | All versions | All versions | 
| Asia Pacific (Hyderabad) | All versions | All versions | All versions | 
| Asia Pacific (Jakarta) | All versions | All versions | All versions | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | All versions | All versions | All versions | 
| Asia Pacific (Mumbai) | All versions | All versions | All versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All versions | All versions | All versions | 
| Asia Pacific (Seoul) | All versions | All versions | All versions | 
| Asia Pacific (Singapore) | All versions | All versions | All versions | 
| Asia Pacific (Sydney) | All versions | All versions | All versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | All versions | All versions | All versions | 
| Canada (Central) | All versions | All versions | All versions | 
| Canada West (Calgary) | Not available | Not available | Not available | 
| China (Beijing) | All versions | All versions | All versions | 
| China (Ningxia) | All versions | All versions | All versions | 
| Europe (Frankfurt) | All versions | All versions | All versions | 
| Europe (Ireland) | All versions | All versions | All versions | 
| Europe (London) | All versions | All versions | All versions | 
| Europe (Milan) | All versions | All versions | All versions | 
| Europe (Paris) | All versions | All versions | All versions | 
| Europe (Spain) | All versions | All versions | All versions | 
| Europe (Stockholm) | All versions | All versions | All versions | 
| Europe (Zurich) | All versions | All versions | All versions | 
| Israel (Tel Aviv) | All versions | All versions | All versions | 
| Mexico (Central) | Not available | Not available | Not available | 
| Middle East (Bahrain) | All versions | All versions | All versions | 
| Middle East (UAE) | All versions | All versions | All versions | 
| South America (São Paulo) | All versions | All versions | All versions | 
| AWS GovCloud (US-East) |  All versions  |  All versions  |  All versions  | 
| AWS GovCloud (US-West) |  All versions  |  All versions  |  All versions  | 

## Kerberos authentication with RDS for Oracle
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.ora"></a>

The following Regions and engine versions are available for Kerberos authentication with RDS for Oracle.


| Region | RDS for Oracle 21c | RDS for Oracle 19c | 
| --- | --- | --- | 
| US East (N. Virginia) | All versions | All versions | 
| US East (Ohio) | All versions | All versions | 
| US West (N. California) | All versions | All versions | 
| US West (Oregon) | All versions | All versions | 
| Africa (Cape Town) (opt-in Region) | All versions | All versions | 
| Asia Pacific (Hong Kong) (opt-in Region) | All versions | All versions | 
| Asia Pacific (Hyderabad) (opt-in Region) | All versions | All versions | 
| Asia Pacific (Jakarta) (opt-in Region) | All versions | All versions | 
| Asia Pacific (Malaysia) | Not available | Not available | 
| Asia Pacific (Melbourne) (opt-in Region) | All versions | All versions | 
| Asia Pacific (Mumbai) | All versions | All versions | 
| Asia Pacific (New Zealand) | Not available | Not available | 
| Asia Pacific (Osaka) | Not available | Not available | 
| Asia Pacific (Seoul) | All versions | All versions | 
| Asia Pacific (Singapore) | All versions | All versions | 
| Asia Pacific (Sydney) | All versions | All versions | 
| Asia Pacific (Taipei) | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | 
| Asia Pacific (Tokyo) | All versions | All versions | 
| Canada (Central) | All versions | All versions | 
| Canada West (Calgary) | Not available | Not available | 
| China (Beijing) | Not available | Not available | 
| China (Ningxia) | Not available | Not available | 
| Europe (Frankfurt) | All versions | All versions | 
| Europe (Ireland) | All versions | All versions | 
| Europe (London) | All versions | All versions | 
| Europe (Milan) (opt-in Region) | All versions | All versions | 
| Europe (Paris) | Not available | Not available | 
| Europe (Spain) (opt-in Region) | All versions | All versions | 
| Europe (Stockholm) | All versions | All versions | 
| Europe (Zurich) (opt-in Region) | All versions | All versions | 
| Israel (Tel Aviv) (opt-in Region) | All versions | All versions | 
| Mexico (Central) | Not available | Not available | 
| Middle East (Bahrain) (opt-in Region) | All versions | All versions | 
| Middle East (UAE) (opt-in Region) | All versions | All versions | 
| South America (São Paulo) | All versions | All versions | 
| AWS GovCloud (US-East) | All versions | All versions | 
| AWS GovCloud (US-West) | All versions | All versions | 

## Kerberos authentication with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.pg"></a>

The following Regions and engine versions are available for Kerberos authentication with RDS for PostgreSQL.


| Region | RDS for PostgreSQL 18 | RDS for PostgreSQL 17 | RDS for PostgreSQL 16 | RDS for PostgreSQL 15 | RDS for PostgreSQL 14 | RDS for PostgreSQL 13 | RDS for PostgreSQL 12 | RDS for PostgreSQL 11 | RDS for PostgreSQL 10 | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| US East (Ohio) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| US West (N. California) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| US West (Oregon) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Africa (Cape Town) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Hong Kong) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Hyderabad) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Jakarta) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Mumbai) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Seoul) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Singapore) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Sydney) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Canada (Central) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Canada West (Calgary) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| China (Beijing) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| China (Ningxia) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (Frankfurt) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (Ireland) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (London) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (Milan) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (Paris) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (Spain) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (Stockholm) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Europe (Zurich) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Israel (Tel Aviv) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Mexico (Central) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Middle East (Bahrain) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| Middle East (UAE) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| South America (São Paulo) | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | All versions | 
| AWS GovCloud (US-East) |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  | 
| AWS GovCloud (US-West) |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  |  All versions  | 

## Kerberos authentication with RDS for SQL Server
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.KerberosAuthentication.sq"></a>

The following Regions and engine versions are available for Kerberos authentication with RDS for SQL Server.


| Region | RDS for SQL Server 2022 | RDS for SQL Server 2019 | RDS for SQL Server 2017 | RDS for SQL Server 2016 | 
| --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All versions | All versions | All versions | All versions | 
| US East (Ohio) | All versions | All versions | All versions | All versions | 
| US West (N. California) | All versions | All versions | All versions | All versions | 
| US West (Oregon) | All versions | All versions | All versions | All versions | 
| Africa (Cape Town) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Hong Kong) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Hyderabad) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Mumbai) | All versions | All versions | All versions | All versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Seoul) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Singapore) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Sydney) | All versions | All versions | All versions | All versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | All versions | All versions | All versions | All versions | 
| Canada (Central) | All versions | All versions | All versions | All versions | 
| Canada West (Calgary) | Not available | Not available | Not available | Not available | 
| China (Beijing) | All versions | All versions | All versions | All versions | 
| China (Ningxia) | All versions | All versions | All versions | All versions | 
| Europe (Frankfurt) | All versions | All versions | All versions | All versions | 
| Europe (Ireland) | All versions | All versions | All versions | All versions | 
| Europe (London) | All versions | All versions | All versions | All versions | 
| Europe (Milan) | All versions | All versions | All versions | All versions | 
| Europe (Paris) | All versions | All versions | All versions | All versions | 
| Europe (Spain) | All versions | All versions | All versions | All versions | 
| Europe (Stockholm) | All versions | All versions | All versions | All versions | 
| Europe (Zurich) | All versions | All versions | All versions | All versions | 
| Israel (Tel Aviv) | Not available | Not available | Not available | Not available | 
| Mexico (Central) | Not available | Not available | Not available | Not available | 
| Middle East (Bahrain) | All versions | All versions | All versions | All versions | 
| Middle East (UAE) | All versions | All versions | All versions | All versions | 
| South America (São Paulo) | All versions | All versions | All versions | All versions | 
| AWS GovCloud (US-East) | All versions | All versions | All versions | All versions | 
| AWS GovCloud (US-West) | All versions | All versions | All versions | All versions | 

# Supported Regions and DB engines for Multi-AZ DB clusters in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters"></a>

A Multi-AZ DB cluster deployment in Amazon RDS provides a high availability deployment mode of Amazon RDS with two readable standby DB instances. A Multi-AZ DB cluster has a writer DB instance and two reader DB instances in three separate Availability Zones in the same Region. Multi-AZ DB clusters provide high availability, increased capacity for read workloads, and lower write latency when compared to Multi-AZ DB instance deployments. For more information, see [Multi-AZ DB cluster deployments for Amazon RDS](multi-az-db-clusters-concepts.md). 

Multi-AZ DB clusters aren't available with the following engines:
+ RDS for Db2
+ RDS for MariaDB
+ RDS for Oracle
+ RDS for SQL Server

**Topics**
+ [

## Multi-AZ DB clusters with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.my)
+ [

## Multi-AZ DB clusters with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.pg)

## Multi-AZ DB clusters with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.my"></a>

The following Regions and engine versions are available for Multi-AZ DB clusters with RDS for MySQL. 


| Region | RDS for MySQL 8.4 | RDS for MySQL 8.0 | 
| --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | 
| US West (N. California) | Not available | Not available | 
| US West (Oregon) | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | 
| Asia Pacific (Taipei) | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | 
| Asia Pacific (Tokyo) | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | 
| AWS GovCloud (US-East) | Not available | Not available | 
| AWS GovCloud (US-West) | Not available | Not available | 

You can list the available versions in a Region for a given DB instance class using the AWS CLI. Change the DB instance class to show the available engine versions for it.

For Linux, macOS, or Unix:

```
aws rds describe-orderable-db-instance-options \
--engine mysql \
--db-instance-class db.r5d.large \
--query '*[]|[?SupportsClusters == `true`].[EngineVersion]'  \
--output text
```

For Windows:

```
aws rds describe-orderable-db-instance-options ^
--engine mysql ^
--db-instance-class db.r5d.large ^
--query "*[]|[?SupportsClusters == `true`].[EngineVersion]"  ^
--output text
```

## Multi-AZ DB clusters with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.MultiAZDBClusters.pg"></a>

The following Regions and engine versions are available for Multi-AZ DB clusters with RDS for PostgreSQL.


| Region | RDS for PostgreSQL 18 | RDS for PostgreSQL 17 | RDS for PostgreSQL 16 | RDS for PostgreSQL 15 | RDS for PostgreSQL 14 | RDS for PostgreSQL 13 | 
| --- | --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| US East (Ohio) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| US West (N. California) | Not available | Not available | Not available | Not available | Not available | Not available | 
| US West (Oregon) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Africa (Cape Town) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Hong Kong) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Hyderabad) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Jakarta) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Malaysia) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Melbourne) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Mumbai) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Seoul) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Singapore) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Sydney) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Canada (Central) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Canada West (Calgary) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| China (Beijing) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| China (Ningxia) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (Frankfurt) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (Ireland) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (London) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (Milan) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (Paris) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (Spain) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (Stockholm) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Europe (Zurich) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Israel (Tel Aviv) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Mexico (Central) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Middle East (Bahrain) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| Middle East (UAE) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| South America (São Paulo) | All PostgreSQL 18 versions | All PostgreSQL 17 versions | All PostgreSQL 16 versions | All PostgreSQL 15 versions | Version 14.5 and higher | Version 13.4 and version 13.7 and higher | 
| AWS GovCloud (US-East) | Not available | Not available | Not available | Not available | Not available | Not available | 
| AWS GovCloud (US-West) | Not available | Not available | Not available | Not available | Not available | Not available | 

You can list the available versions in a Region for a given DB instance class using the AWS CLI. Change the DB instance class to show the available engine versions for it.

For Linux, macOS, or Unix:

```
aws rds describe-orderable-db-instance-options \
--engine postgres \
--db-instance-class db.r5d.large \
--query '*[]|[?SupportsClusters == `true`].[EngineVersion]'  \
--output text
```

For Windows:

```
aws rds describe-orderable-db-instance-options ^
--engine postgres ^
--db-instance-class db.r5d.large ^
--query "*[]|[?SupportsClusters == `true`].[EngineVersion]"  ^
--output text
```

# Supported Regions and DB engines for Performance Insights in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.PerformanceInsights"></a>

**Important**  
 AWS has announced the end-of-life date for Performance Insights: June 30, 2026. After this date, Amazon RDS will no longer support the Performance Insights console experience, flexible retention periods (1-24 months), and their associated pricing. The Performance Insights API will continue to exist with no pricing changes. Costs for the Performance Insights API will appear in your AWS bill with the cost of CloudWatch Database Insights.   
 We recommend that you upgrade any DB instances using the paid tier of Performance Insights to the Advanced mode of Database Insights before June 30, 2026. For information about upgrading to the Advanced mode of Database Insights, see [Turning on the Advanced mode of Database Insights for Amazon RDS](USER_DatabaseInsights.TurningOnAdvanced.md).   
 If you take no action, DB instances using Performance Insights will default to using the Standard mode of Database Insights. With Standard mode of Database Insights, you might lose access to performance data history beyond 7 days and might not be able to use execution plans and on-demand analysis features in the Amazon RDS console. After June 30, 2026 only the Advanced mode of Database Insights will support execution plans and on-demand analysis.   
 With CloudWatch Database Insights, you can monitor database load for your fleet of databases and analyze and troubleshoot performance at scale. For more information about Database Insights, see [Monitoring Amazon RDS databases with CloudWatch Database Insights](USER_DatabaseInsights.md). For pricing information, see [Amazon CloudWatch Pricing](https://aws.amazon.com/cloudwatch/pricing/). 

Performance Insights in Amazon RDS expands on existing Amazon RDS monitoring features to illustrate and help you analyze your database performance. With the Performance Insights dashboard, you can visualize the database load on your Amazon RDS DB instance. You can also filter the load by waits, SQL statements, hosts, or users. For more information, see [Monitoring DB load with Performance Insights on Amazon RDS](USER_PerfInsights.md).

Performance Insights is available for all RDS DB engines, except RDS for Db2.

For the available DB engines, Performance Insights is available with all of the available engine versions and in all AWS Regions.

For the Region, DB engine, and instance class support information for Performance Insights features, see [Amazon RDS DB engine, Region, and instance class support for Performance Insights features](USER_PerfInsights.Overview.Engines.md#USER_PerfInsights.Overview.PIfeatureEngnRegSupport).

# Supported Regions and DB engines for RDS Custom
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom"></a>

Amazon RDS Custom automates database administration tasks and operations. By using RDS Custom, as a database administrator you can access and customize your database environment and operating system. With RDS Custom, you can customize to meet the requirements of legacy, custom, and packaged applications. For more information, see [Amazon RDS Custom](rds-custom.md).

RDS Custom is supported for the following DB engines only:

**Topics**
+ [

## Supported Regions and DB engines for RDS Custom for Oracle
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.ora)
+ [

## Supported Regions and DB engines for RDS Custom for SQL Server
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.sq)

## Supported Regions and DB engines for RDS Custom for Oracle
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.ora"></a>

The following Regions and engine versions are available for RDS Custom for Oracle.


| Region | Oracle Database 19c | Oracle Database 18c | Oracle Database 12c | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| US East (Ohio) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| US West (N. California) | Not available | Not available | Not available | 
| US West (Oregon) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Africa (Cape Town) | Not available | Not available | Not available | 
| Asia Pacific (Hong Kong) | Not available | Not available | Not available | 
| Asia Pacific (Jakarta) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | Not available | Not available | Not available | 
| Asia Pacific (Mumbai) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Asia Pacific (Seoul) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Asia Pacific (Singapore) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Asia Pacific (Sydney) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Canada (Central) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Canada West (Calgary) | Not available | Not available | Not available | 
| China (Beijing) | Not available | Not available | Not available | 
| China (Ningxia) | Not available | Not available | Not available | 
| Europe (Frankfurt) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Europe (Ireland) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Europe (London) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Europe (Milan) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Europe (Paris) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Europe (Stockholm) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| Israel (Tel Aviv) | Not available | Not available | Not available | 
| Mexico (Central) | Not available | Not available | Not available | 
| Middle East (Bahrain) | Not available | Not available | Not available | 
| Middle East (UAE) | 19c with the January 2021 or higher RU/RUR  | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| South America (São Paulo) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| AWS GovCloud (US-East) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 
| AWS GovCloud (US-West) | 19c with the January 2021 or higher RU/RUR | 18c with the January 2021 or higher RU/RUR | 12.1 and 12.2 with the January 2021 or higher RU/RUR | 

## Supported Regions and DB engines for RDS Custom for SQL Server
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.sq"></a>

You can deploy RDS Custom for SQL Server by using either an RDS provided engine version (RPEV) or a custom engine version (CEV):
+ If you use an RPEV, it includes the default Amazon Machine Image (AMI) and SQL Server installation. RDS Custom for SQL Server also supports operating system updates through maintenance actions for RDS provided engine version (RPEV). If you customize or modify the operating system (OS), your changes might not persist during patching, snapshot restore, or automatic recovery.
+ If you use a CEV, you choose your own AMI with either pre-installed Microsoft SQL Server or SQL Server that you install using your own media. When using an AWS provided CEV, you choose the latest Amazon EC2 image (AMI) available by AWS, which has the cumulative update (CU) supported by RDS Custom for SQL Server. With a CEV, you can customize both the OS and SQL Server configuration to meet your enterprise needs.

Currently, you can only use the Windows 2019 operating system.

The following AWS Regions and DB engine versions are available for RDS Custom for SQL Server. The engine version support depends on whether you're using RDS Custom for SQL Server with an RPEV, AWS provided CEV, or customer-provided CEV.


| Region | RPEV | AWS provided CEV | Customer-provided CEV | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| US East (Ohio) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| US West (N. California) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| US West (Oregon) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Africa (Cape Town) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Asia Pacific (Hong Kong) | Not available | Not available | Not available | 
| Asia Pacific (Hyderabad) | Not available | Not available | Not available | 
| Asia Pacific (Jakarta) | Not available | Not available | Not available | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | Not available | Not available | Not available | 
| Asia Pacific (Mumbai) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Asia Pacific (Seoul) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Asia Pacific (Singapore) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Asia Pacific (Sydney) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Canada (Central) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Canada West (Calgary) | Not available | Not available | Not available | 
| China (Beijing) | Not available | Not available | Not available | 
| China (Ningxia) | Not available | Not available | Not available | 
| Europe (Frankfurt) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Europe (Ireland) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Europe (London) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Europe (Milan) | Not available | Not available | Not available | 
| Europe (Paris) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Europe (Spain) | Not available | Not available | Not available | 
| Europe (Stockholm) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| Europe (Zurich) | Not available | Not available | Not available | 
| Israel (Tel Aviv) | Not available | Not available | Not available | 
| Mexico (Central) | Not available | Not available | Not available | 
| Middle East (Bahrain) | Not available | Not available | Not available | 
| Middle East (UAE) | Not available | Not available | Not available | 
| South America (São Paulo) | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | SQL Server 2022 Enterprise, Standard, Developer, or Web, with CU9, CU13, CU14-GDR, CU15-GDR, CU16, CU17, CU18, CU19, CU19-GDR, CU20-GDR, CU21-GDR, CU22 and CU22-GDR. SQL Server 2019 Enterprise, Standard, Developer, or Web, with CU8, CU17, CU18, CU20, CU24, CU26, CU28-GDR, CU29-GDR, CU30, CU32, and CU32-GDR. | 
| AWS GovCloud (US-East) | Not available | Not available | Not available | 
| AWS GovCloud (US-West) | Not available | Not available | Not available | 

# Supported Regions and DB engines for Amazon RDS Proxy
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSProxy"></a>

Amazon RDS Proxy is a fully managed, highly available database proxy that makes applications more scalable by pooling and sharing established database connections. For more information, see [Amazon RDS Proxy](rds-proxy.md).

RDS Proxy isn't available for the following engines:
+ RDS for Db2
+ RDS for Oracle

**Topics**
+ [

## RDS Proxy with RDS for MariaDB
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.mdb)
+ [

## RDS Proxy with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.my)
+ [

## RDS Proxy with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.pg)
+ [

## RDS Proxy with RDS for SQL Server
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.sq)

## RDS Proxy with RDS for MariaDB
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.mdb"></a>

The following Regions and engine versions are available for RDS Proxy with RDS for MariaDB.


| Region | RDS for MariaDB 11.8 | RDS for MariaDB 11.4 | RDS for MariaDB 10.11 | RDS for MariaDB 10.6 | RDS for MariaDB 10.5 | 
| --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Mexico (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | All available versions | All available versions | 

## RDS Proxy with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.my"></a>

The following Regions and engine versions are available for RDS Proxy with RDS for MySQL. 


| Region | RDS for MySQL 8.4 | RDS for MySQL 8.0 | RDS for MySQL 5.7 | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | 
| Asia Pacific (Thailand) |  All available versions  |  All available versions  |  All available versions  | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | 
| Mexico (Central) |  All available versions  |  All available versions  |  All available versions  | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | 

## RDS Proxy with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.pg"></a>

The following Regions and engine versions are available for RDS Proxy with RDS for PostgreSQL.


| Region | RDS for PostgreSQL 18 | RDS for PostgreSQL 17 | RDS for PostgreSQL 16 | RDS for PostgreSQL 15 | RDS for PostgreSQL 14 | RDS for PostgreSQL 13 | RDS for PostgreSQL 12 | RDS for PostgreSQL 11 | RDS for PostgreSQL 10 | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Mexico (Central) |  All available versions  |  All available versions  |  All available versions  |  All available versions  |  All available versions  |  All available versions  |  All available versions  |  All available versions  |  All available versions  | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | All available versions | 

## RDS Proxy with RDS for SQL Server
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDS_Proxy.sq"></a>

The following Regions and engine versions are available for RDS Proxy with RDS for SQL Server.


| Region | RDS for SQL Server 2019 | RDS for SQL Server 2017 | RDS for SQL Server 2016 | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | All available versions | 
| US West (Oregon) | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | All available versions | 
| Asia Pacific (Jakarta) | All available versions | All available versions | All available versions | 
| Asia Pacific (Malaysia) | All available versions | All available versions | All available versions | 
| Asia Pacific (Melbourne) | All available versions | All available versions | All available versions | 
| Asia Pacific (Mumbai) | All available versions | All available versions | All available versions | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | All available versions | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | All available versions | All available versions | All available versions | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | All available versions | 
| China (Beijing) | All available versions | All available versions | All available versions | 
| China (Ningxia) | All available versions | All available versions | All available versions | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | All available versions | 
| Europe (Paris) | All available versions | All available versions | All available versions | 
| Europe (Spain) | All available versions | All available versions | All available versions | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | All available versions | 
| Israel (Tel Aviv) | All available versions | All available versions | All available versions | 
| Mexico (Central) |  All available versions  |  All available versions  |  All available versions  | 
| Middle East (Bahrain) | All available versions | All available versions | All available versions | 
| Middle East (UAE) | All available versions | All available versions | All available versions | 
| South America (São Paulo) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-West) | All available versions | All available versions | All available versions | 

# Supported Regions and DB engines for the Secrets Manager integration with Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.SecretsManager"></a>

With AWS Secrets Manager, you can replace hard-coded credentials in your code, including database passwords, with an API call to Secrets Manager to retrieve the secret programmatically. For more information about Secrets Manager, see [AWS Secrets Manager User Guide](https://docs.aws.amazon.com/secretsmanager/latest/userguide/).

You can specify that Amazon RDS manages the master user password in Secrets Manager for an Amazon RDS DB instance or Multi-AZ DB cluster. RDS generates the password, stores it in Secrets Manager, and rotates it regularly. For more information, see [Password management with Amazon RDS and AWS Secrets Manager](rds-secrets-manager.md).

Secrets Manager integration is available in all AWS Regions.

# Supported Regions and DB engines for Amazon RDS zero-ETL integrations
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL"></a>

RDS zero-ETL integrations is a fully managed solution for making transactional data available in Amazon Redshift or Amazon SageMaker after it's written to an Amazon RDS DB instance. For more information, see [Amazon RDS zero-ETL integrations](zero-etl.md).

**Topics**
+ [

## Zero-ETL integrations with RDS for MySQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.mysql)
+ [

## Zero-ETL integrations with RDS for PostgreSQL
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.PostgreSQL)
+ [

## Zero-ETL integrations with RDS for Oracle
](#Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.Oracle)

## Zero-ETL integrations with RDS for MySQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.mysql"></a>

The following Regions and engine versions are available for RDS for MySQL zero-ETL integrations with Amazon Redshift and Amazon SageMaker.


| Region | Zero-ETL integration with Amazon Redshift for RDS for MySQL 8.4 | Zero-ETL integration with Amazon Redshift for RDS for MySQL 8.0 | Zero-ETL integration with Amazon SageMaker for RDS for MySQL 8.4 | Zero-ETL integration with Amazon SageMaker for RDS for MySQL 8.0 | 
| --- | --- | --- | --- | --- | 
| US East (N. Virginia) | All available versions | All available versions | All available versions | All available versions | 
| US East (Ohio) | All available versions | All available versions | All available versions | All available versions | 
| US West (N. California) | All available versions | All available versions | Not available | Not available | 
| US West (Oregon) | All available versions | All available versions | All available versions | All available versions | 
| Africa (Cape Town) | All available versions | All available versions | Not available | Not available | 
| Asia Pacific (Hong Kong) | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | All available versions | Not available | Not available | 
| Asia Pacific (Jakarta) | All available versions | All available versions | Not available | Not available | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | All available versions | All available versions | Not available | Not available | 
| Asia Pacific (Mumbai) | All available versions | All available versions | Not available | Not available | 
| Asia Pacific (New Zealand) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Osaka) | All available versions | All available versions | Not available | Not available | 
| Asia Pacific (Seoul) | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Singapore) | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Sydney) | All available versions | All available versions | All available versions | All available versions | 
| Asia Pacific (Taipei) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Thailand) | Not available | Not available | Not available | Not available | 
| Asia Pacific (Tokyo) | All available versions | All available versions | All available versions | All available versions | 
| Canada (Central) | All available versions | All available versions | All available versions | All available versions | 
| Canada West (Calgary) | All available versions | All available versions | Not available | Not available | 
| China (Beijing) | Not available | Not available | Not available | Not available | 
| China (Ningxia) | Not available | Not available | Not available | Not available | 
| Europe (Frankfurt) | All available versions | All available versions | All available versions | All available versions | 
| Europe (Ireland) | All available versions | All available versions | All available versions | All available versions | 
| Europe (London) | All available versions | All available versions | All available versions | All available versions | 
| Europe (Milan) | All available versions | All available versions | Not available | Not available | 
| Europe (Paris) | All available versions | All available versions | Not available | Not available | 
| Europe (Spain) | All available versions | All available versions | Not available | Not available | 
| Europe (Stockholm) | All available versions | All available versions | All available versions | All available versions | 
| Europe (Zurich) | All available versions | All available versions | Not available | Not available | 
| Israel (Tel Aviv) | All available versions | All available versions | Not available | Not available | 
| Mexico (Central) | Not available | Not available | Not available | Not available | 
| Mexico (Central) | Not available | Not available | Not available | Not available | 
| Middle East (Bahrain) | All available versions | All available versions | Not available | Not available | 
| Middle East (UAE) | All available versions | All available versions | Not available | Not available | 
| South America (São Paulo) | All available versions | All available versions | All available versions | All available versions | 
| AWS GovCloud (US-East) | Not available | Not available | Not available | Not available | 
| AWS GovCloud (US-West) | Not available | Not available | Not available | Not available | 

## Zero-ETL integrations with RDS for PostgreSQL
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.PostgreSQL"></a>

The following Regions and engine versions are available for RDS for PostgreSQL zero-ETL integrations with Amazon Redshift.


| Region | Zero-ETL integration with Amazon Redshift for RDS for PostgreSQL 15 | Zero-ETL integration with Amazon Redshift for RDS for PostgreSQL 16 | Zero-ETL integration with Amazon Redshift for RDS for PostgreSQL 17 | 
| --- | --- | --- | --- | 
| US East (N. Virginia) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| US East (Ohio) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| US West (N. California) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| US West (Oregon) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Africa (Cape Town) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Hong Kong) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Hyderabad) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Jakarta) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Malaysia) | Not available | Not available | Not available | 
| Asia Pacific (Melbourne) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Mumbai) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Osaka) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Seoul) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Singapore) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Sydney) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Thailand) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Asia Pacific (Tokyo) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Canada (Central) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Canada West (Calgary) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| China (Beijing) | Not available | Not available | Not available | 
| China (Ningxia) | Not available | Not available | Not available | 
| Europe (Frankfurt) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Europe (Ireland) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Europe (London) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Europe (Milan) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Europe (Paris) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Europe (Spain) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Europe (Stockholm) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Europe (Zurich) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Israel (Tel Aviv) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Middle East (Bahrain) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| Middle East (UAE) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| South America (São Paulo) | Version 15.11 and higher | Version 16.7 and higher | Version 17.3 and higher | 
| AWS GovCloud (US-East) | Not available | Not available | Not available | 
| AWS GovCloud (US-West) | Not available | Not available | Not available | 

## Zero-ETL integrations with RDS for Oracle
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.ZeroETL.Oracle"></a>

The following Regions and engine versions are available for RDS for Oracle zero-ETL integrations with Amazon Redshift.


| Region | Zero-ETL integration with Amazon Redshift for RDS for Oracle 19c | 
| --- | --- | 
| US East (N. Virginia) | All available versions | 
| US East (Ohio) | All available versions | 
| US West (N. California) | All available versions | 
| US West (Oregon) | All available versions | 
| Africa (Cape Town) | All available versions | 
| Asia Pacific (Hong Kong) | All available versions | 
| Asia Pacific (Hyderabad) | All available versions | 
| Asia Pacific (Jakarta) | All available versions | 
| Asia Pacific (Malaysia) | Not available | 
| Asia Pacific (Melbourne) | All available versions | 
| Asia Pacific (Mumbai) | All available versions | 
| Asia Pacific (Osaka) | All available versions | 
| Asia Pacific (Seoul) | All available versions | 
| Asia Pacific (Singapore) | All available versions | 
| Asia Pacific (Sydney) | All available versions | 
| Asia Pacific (Thailand) | All available versions | 
| Asia Pacific (Tokyo) | All available versions | 
| Canada (Central) | All available versions | 
| Canada West (Calgary) | All available versions | 
| China (Beijing) | Not available | 
| China (Ningxia) | Not available | 
| Europe (Frankfurt) | All available versions | 
| Europe (Ireland) | All available versions | 
| Europe (London) | All available versions | 
| Europe (Milan) | All available versions | 
| Europe (Paris) | All available versions | 
| Europe (Spain) | All available versions | 
| Europe (Stockholm) | All available versions | 
| Europe (Zurich) | All available versions | 
| Israel (Tel Aviv) | All available versions | 
| Middle East (Bahrain) | All available versions | 
| Middle East (UAE) | All available versions | 
| South America (São Paulo) | All available versions | 
| AWS GovCloud (US-East) | Not available | 
| AWS GovCloud (US-West) | Not available | 

# Engine-native features in Amazon RDS
<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.EngineNativeFeatures"></a>

Amazon RDS database engines also support many of the most common engine-native features and functionality. These features are different than the Amazon RDS-native features listed on this page. Some engine-native features might have limited support or restricted privileges.

For more information on engine-native features, see:
+ [Amazon RDS for Db2 features](Db2.Concepts.FeatureSupport.md)
+ [MariaDB feature support on Amazon RDS](MariaDB.Concepts.FeatureSupport.md)
+ [MySQL feature support on Amazon RDS](MySQL.Concepts.FeatureSupport.md)
+ [RDS for Oracle features](Oracle.Concepts.FeatureSupport.md)
+ [Working with PostgreSQL features supported by Amazon RDS for PostgreSQL](PostgreSQL.Concepts.General.FeatureSupport.md)
+ [Microsoft SQL Server features on Amazon RDS](SQLServer.Concepts.General.FeatureSupport.md)

# DB instance billing for Amazon RDS
<a name="User_DBInstanceBilling"></a>

Amazon RDS instances are billed based on the following components:
+ DB instance hours (per hour) – Based on the DB instance class of the DB instance (for example, db.t2.small or db.m4.large). Pricing is listed on a per-hour basis, but bills are calculated down to the second and show times in decimal form. RDS usage is billed in 1-second increments, with a minimum of 10 minutes. For more information, see [DB instance classes](Concepts.DBInstanceClass.md).
+ Storage (per GiB per month) – Storage capacity that you have provisioned to your DB instance. If you scale your provisioned storage capacity within the month, your bill is prorated. For more information, see [Amazon RDS DB instance storage](CHAP_Storage.md).
+ Input/output (I/O) requests (per 1 million requests) – Total number of storage I/O requests that you have made in a billing cycle, for Amazon RDS magnetic storage only.
+ Provisioned IOPS (per IOPS per month) – Provisioned IOPS rate, regardless of IOPS consumed, for Amazon RDS Provisioned IOPS (SSD) and General Purpose (SSD) gp3 storage. Provisioned storage for EBS volumes are billed in 1-second increments, with a minimum of 10 minutes.
+ Backup storage (per GiB per month) – *Backup storage *is the storage that is associated with automated database backups and any active database snapshots that you have taken. Increasing your backup retention period or taking additional database snapshots increases the backup storage consumed by your database. Per second billing doesn't apply to backup storage (metered in GB-month).

  For more information, see [Backing up, restoring, and exporting data](CHAP_CommonTasks.BackupRestore.md).
+ Data transfer (per GB) – Data transfer in and out of your DB instance from or to the internet and other AWS Regions. For useful examples, see the AWS blog post [Exploring Data Transfer Costs for AWS Managed Databases](https://aws.amazon.com/blogs/architecture/exploring-data-transfer-costs-for-aws-managed-databases).

Amazon RDS provides the following purchasing options to enable you to optimize your costs based on your needs:
+ **On-Demand instances** – Pay by the hour for the DB instance hours that you use. Pricing is listed on a per-hour basis, but bills are calculated down to the second and show times in decimal form. RDS usage is now billed in 1-second increments, with a minimum of 10 minutes.
+ **Reserved instances** – Reserve a DB instance for a one-year or three-year term and get a significant discount compared to the on-demand DB instance pricing. With Reserved Instance usage, you can launch, delete, start, or stop multiple instances within an hour and get the Reserved Instance benefit for all of the instances.

For Amazon RDS pricing information, see the [Amazon RDS pricing page](https://aws.amazon.com/rds/pricing).

**Topics**
+ [

# On-Demand DB instances for Amazon RDS
](USER_OnDemandDBInstances.md)
+ [

# Reserved DB instances for Amazon RDS
](USER_WorkingWithReservedDBInstances.md)

# On-Demand DB instances for Amazon RDS
<a name="USER_OnDemandDBInstances"></a>

Amazon RDS on-demand DB instances are billed based on the class of the DB instance (for example, db.t3.small or db.m5.large). For Amazon RDS pricing information, see the [Amazon RDS product page](https://aws.amazon.com/rds/pricing).

Billing starts for a DB instance as soon as the DB instance is available. Pricing is listed on a per-hour basis, but bills are calculated down to the second and show times in decimal form. Amazon RDS usage is billed in one-second increments, with a minimum of 10 minutes. In the case of billable configuration change, such as scaling compute or storage capacity, you're charged a 10-minute minimum. Billing continues until the DB instance terminates, which occurs when you delete the DB instance or if the DB instance fails.

If you no longer want to be charged for your DB instance, you must stop or delete it to avoid being billed for additional DB instance hours. For more information about the DB instance states for which you are billed, see [Viewing Amazon RDSDB instance status](accessing-monitoring.md#Overview.DBInstance.Status).

## Stopped DB instances
<a name="USER_OnDemandDBInstances.Stopped"></a>

While your DB instance is stopped, you're charged for provisioned storage, including Provisioned IOPS. You are also charged for backup storage, including storage for manual snapshots and automated backups within your specified retention window. You aren't charged for DB instance hours.

## Multi-AZ DB instances
<a name="USER_OnDemandDBInstances.MultiAZ"></a>

A Multi-AZ setup enhances data durability and availability by automatically provisioning and maintaining a synchronous standby replica in a different Availability Zone. Due to the additional resources and increased availability, Multi-AZ deployments are priced higher than Single-AZ deployments, and can cost approximately twice as much due to the additional standby instance and associated resources.

Consider the following important details about Multi-AZ pricing:
+ **Compute costs**: Billed per DB instance-hour for both the primary and standby instances.
+ **Storage costs**: Charged per GB-month for the storage provisioned for both the primary and standby instances.
+ **Data transfer costs**: Replication between the primary and standby instances is included in the cost, but other data transfer charges might apply based on your usage.

To accurately estimate your monthly costs based on your specific use case and AWS Region, you can use the AWS Pricing Calculator. This tool lets you to input your configuration details and provides a comprehensive cost breakdown.

**Note**  
Pricing is subject to change. See the [Amazon RDS Pricing page](https://aws.amazon.com/rds/pricing/) for the most up-to-date information.

# Reserved DB instances for Amazon RDS
<a name="USER_WorkingWithReservedDBInstances"></a>

Using reserved DB instances, you can reserve a DB instance for a one- or three-year term. Reserved DB instances provide you with a significant discount compared to on-demand DB instance pricing. Reserved DB instances are not physical instances, but rather a billing discount applied to the use of certain on-demand DB instances in your account. Discounts for reserved DB instances are tied to instance type and AWS Region.

The general process for working with reserved DB instances is: First get information about available reserved DB instance offerings, then purchase a reserved DB instance offering, and finally get information about your existing reserved DB instances.

For information about purchasing reserved DB instances and viewing the billing for reserved DB instances, see the following sections.
+ [Purchasing reserved DB instances for Amazon RDS](USER_WorkingWithReservedDBInstances.WorkingWith.md)
+ [Viewing the billing for reserved DB instances for Amazon RDS](reserved-instances-billing.md)

## Overview of reserved DB instances
<a name="USER_WorkingWithReservedDBInstances.Overview"></a>

When you purchase a reserved DB instance in Amazon RDS, you purchase a commitment to getting a discounted rate, on a specific DB instance type, for the duration of the reserved DB instance. To use an Amazon RDS reserved DB instance, you create a new DB instance just like you do for an on-demand instance.

The new DB instance that you create must have the same specifications as the reserved DB instance for the following:
+ AWS Region
+ DB engine (The DB engine's version number doesn't need to match.)
+ DB instance type
+ DB instance size (RDS for Db2, RDS for SQL Server, and RDS for Oracle License Included)
+ Edition (RDS for Db2, RDS for SQL Server, and RDS for Oracle)
+ License type (license-included or bring-your-own-license)

If the specifications of the new DB instance match an existing reserved DB instance for your account, you are billed at the discounted rate offered for the reserved DB instance. Otherwise, the DB instance is billed at an on-demand rate.

You can modify a DB instance that you're using as a reserved DB instance. If the modification is within the specifications of the reserved DB instance, part or all of the discount still applies to the modified DB instance. If the modification is outside the specifications, such as changing the instance class, the discount no longer applies. For more information, see [Size-flexible reserved DB instances](#USER_WorkingWithReservedDBInstances.SizeFlexible).

**Topics**
+ [

### Offering types
](#USER_WorkingWithReservedDBInstances.OfferingTypes)
+ [

### Size-flexible reserved DB instances
](#USER_WorkingWithReservedDBInstances.SizeFlexible)
+ [

### Reserved DB instance billing example
](#USER_WorkingWithReservedDBInstances.BillingExample)
+ [

### Reserved DB instances for a Multi-AZ DB cluster
](#USER_WorkingWithReservedDBInstances.MultiAZDBClusters)
+ [

### Deleting a reserved DB instance
](#USER_WorkingWithReservedDBInstances.Cancelling)

For more information about reserved DB instances, including pricing, see [Amazon RDS reserved instances](http://aws.amazon.com/rds/reserved-instances/#2).

### Offering types
<a name="USER_WorkingWithReservedDBInstances.OfferingTypes"></a>

Reserved DB instances are available in three varieties—No Upfront, Partial Upfront, and All Upfront—that let you optimize your Amazon RDS costs based on your expected usage.

**Note**  
Not all RDS instance classes support all Reserved Instance offering types. For example, some instance classes might not offer the No Upfront option. To confirm availability, review the Reserved Instance offerings in the AWS Management Console or use the `describe-reserved-db-instances-offerings` AWS CLI command.

**No Upfront**  
This option provides access to a reserved DB instance without requiring an upfront payment. Your No Upfront reserved DB instance bills a discounted hourly rate for every hour within the term, regardless of usage, and no upfront payment is required. This option is only available as a one-year reservation.

**Partial Upfront**  
This option requires a part of the reserved DB instance to be paid upfront. The remaining hours in the term are billed at a discounted hourly rate, regardless of usage. This option is the replacement for the previous Heavy Utilization option.

**All Upfront**  
Full payment is made at the start of the term, with no other costs incurred for the remainder of the term regardless of the number of hours used.

If you are using consolidated billing, all the accounts in the organization are treated as one account. This means that all accounts in the organization can receive the hourly cost benefit of reserved DB instances that are purchased by any other account. For more information about consolidated billing, see [Amazon RDS reserved DB instances](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidatedbilling-other.html#consolidatedbilling-rds) in the *AWS Billing and Cost Management User Guide*.

### Size-flexible reserved DB instances
<a name="USER_WorkingWithReservedDBInstances.SizeFlexible"></a>

When you purchase a reserved DB instance, one thing that you specify is the instance class, for example db.r5.large. For more information about DB instance classes, see [DB instance classes](Concepts.DBInstanceClass.md).

If you have a DB instance, and you need to scale it to larger capacity, your reserved DB instance is automatically applied to your scaled DB instance. That is, your reserved DB instances are automatically applied across all DB instance class sizes. Size-flexible reserved DB instances are available for DB instances with the same AWS Region and database engine. Size-flexible reserved DB instances can only scale in their instance class type. For example, a reserved DB instance for a db.r6i.large can apply to a db.r6i.xlarge, but not to a db.r6id.large or db.r7g.large, because db.r6id.large and db.r7g.large are different instance class types.

Reserved DB instance benefits apply to both Multi-AZ and Single-AZ configurations. This means that you can move freely between configurations within the same DB instance class type. For example, you can move from a Single-AZ deployment running on one large DB instance (four normalized units per hour) to a Multi-AZ deployment running on two medium DB instances (2\$12 = 4 normalized units per hour).

Size-flexible reserved DB instances are available for the following Amazon RDS database engines:
+ RDS for Db2
+ RDS for MariaDB
+ RDS for MySQL
+ RDS for Oracle, Bring Your Own License
+ RDS for PostgreSQL

Size flexibility does not apply to RDS for SQL Server and RDS for Oracle License Included.

For details about using size-flexible reserved instances with Aurora, see [Reserved DB instances for Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithReservedDBInstances.html). 

You can compare usage for different reserved DB instance sizes by using normalized units per hour. For example, one unit of usage on two db.r3.large DB instances is equivalent to eight normalized units per hour of usage on one db.r3.small. The following table shows the number of normalized units per hour for each DB instance size.


| Instance size | Single-AZ normalized units per hour (deployment with one DB instance) | Multi-AZ DB instance normalized units per hour (deployment with one DB instance and one standby) | Multi-AZ DB cluster normalized units per hour (deployment with one DB instance and two standbys) | 
| --- | --- | --- | --- | 
|  micro  |  0.5  |  1  | 1.5 | 
|  small  |  1  |  2  | 3 | 
|  medium  |  2  |  4  | 6 | 
|  large  |  4  |  8  | 12 | 
|  xlarge  |  8  |  16  | 24 | 
|  2xlarge  |  16  |  32  | 48 | 
|  4xlarge  |  32  |  64  | 96 | 
|  6xlarge  |  48  |  96  | 144 | 
|  8xlarge  |  64  |  128  | 192 | 
|  10xlarge  |  80  |  160  | 240 | 
|  12xlarge  |  96  |  192  | 288 | 
|  16xlarge  |  128  |  256  | 384 | 
|  24xlarge  |  192  |  384  | 576 | 
|  32xlarge  |  256  |  512  | 768 | 

For example, suppose that you purchase a `db.t2.medium` reserved DB instance, and you have two running `db.t2.small` DB instances in your account in the same AWS Region. In this case, the billing benefit is applied in full to both instances.

![\[Applying a reserved DB instance in full to smaller DB instances\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/ri-db-instance-flex-full.png)


Alternatively, if you have one `db.t2.large` instance running in your account in the same AWS Region, the billing benefit is applied to 50 percent of the usage of the DB instance. 

![\[Applying a reserved DB instance in part to a larger DB instance\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/ri-db-instance-flex-partial.png)


### Reserved DB instance billing example
<a name="USER_WorkingWithReservedDBInstances.BillingExample"></a>

The price for a reserved DB instance doesn't provide a discount for the costs associated with storage, backups, and I/O. It provides a discount only on the hourly, on-demand instance usage. The following example illustrates the total cost per month for a reserved DB instance:
+ An RDS for MySQL reserved Single-AZ db.r5.large DB instance class in US East (N. Virginia) with the No Upfront option at a cost of \$10.12 for the instance, or \$190 per month
+ 400 GiB of General Purpose SSD (gp2) storage at a cost of 0.115 per GiB per month, or \$145.60 per month
+ 600 GiB of backup storage at \$10.095, or \$119 per month (400 GiB free)

Add all of these charges (\$190 \$1 \$145.60 \$1 \$119) with the reserved DB instance, and the total cost per month is \$1154.60.

If you choose to use an on-demand DB instance instead of a reserved DB instance, an RDS for MySQL Single-AZ db.r5.large DB instance class in US East (N. Virginia) costs \$10.1386 per hour, or \$1101.18 per month. So, for an on-demand DB instance, add all of these options (\$1101.18 \$1 \$145.60 \$1 \$119), and the total cost per month is \$1165.78. You save a little over \$111 per month by using the reserved DB instance.

**Note**  
The prices in this example are sample prices and might not match actual prices. For Amazon RDS pricing information, see [Amazon RDS pricing](https://aws.amazon.com/rds/pricing).

### Reserved DB instances for a Multi-AZ DB cluster
<a name="USER_WorkingWithReservedDBInstances.MultiAZDBClusters"></a>

To purchase the equivalent reserved DB instances for a Multi-AZ DB cluster, you can do one of the following:
+ Reserve three Single-AZ DB instances that are the same size as the instances in the cluster.
+ Reserve one Multi-AZ DB instance and one Single-AZ DB instance that are the same size as the DB instances in the cluster.

For example, suppose that you have one cluster consisting of three db.m6gd.large DB instances. In this case, you can either purchase three db.m6gd.large Single-AZ reserved DB instances, or one db.m6gd.large Multi-AZ reserved DB instance and one db.m6gd.large Single-AZ reserved DB instance. Either of these options reserves the maximum reserved instance discount for the Multi-AZ DB cluster.

Alternately, you can use size-flexible DB instances and purchase a larger DB instance to cover smaller DB instances in one or more clusters. For example, if you have two clusters with six total db.m6gd.large DB instances, you can purchase three db.m6gd.xl Single-AZ reserved DB instances. Doing so reserves all six DB instances in the two clusters. For more information, see [Size-flexible reserved DB instances](#USER_WorkingWithReservedDBInstances.SizeFlexible).

You might reserve DB instances that are the same size as the DB instances in the cluster, but reserve fewer DB instances than the total number of DB instances in the cluster. However, if you do so, the cluster is only partially reserved. For example, suppose that you have one cluster with three db.m6gd.large DB instances, and you purchase one db.m6gd.large Multi-AZ reserved DB instance. In this case, the cluster is only partially reserved, because only two of the three instances in the cluster are covered by reserved DB instances. The remaining DB instance is charged at the on-demand db.m6gd.large hourly rate.

For more information about Multi-AZ DB clusters, see [Multi-AZ DB cluster deployments for Amazon RDS](multi-az-db-clusters-concepts.md).

### Deleting a reserved DB instance
<a name="USER_WorkingWithReservedDBInstances.Cancelling"></a>

The terms for a reserved DB instance involve a one-year or three-year commitment. You can't cancel a reserved DB instance. However, you can delete a DB instance that is covered by a reserved DB instance discount. The process for deleting a DB instance that is covered by a reserved DB instance discount is the same as for any other DB instance.

You're billed for the upfront costs regardless of whether you use the resources.

If you delete a DB instance that is covered by a reserved DB instance discount, you can launch another DB instance with compatible specifications. In this case, you continue to get the discounted rate during the reservation term (one or three years).

# Purchasing reserved DB instances for Amazon RDS
<a name="USER_WorkingWithReservedDBInstances.WorkingWith"></a>

You can use the AWS Management Console, the AWS CLI, and the RDS API to work with reserved DB instances.

## Console
<a name="USER_WorkingWithReservedDBInstances.CON"></a>

You can use the AWS Management Console to work with reserved DB instances as shown in the following procedures. 

**To get pricing and information about available reserved DB instance offerings**

1. Sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).

1. In the navigation pane, choose **Reserved instances**. 

1. Choose **Purchase Reserved DB Instance**.

1. For **Product description**, choose the DB engine and licensing type.

1. For **DB instance class**, choose the DB instance class.

1. For **Deployment Option**, choose whether you want a Single-AZ or Multi-AZ DB instance deployment.
**Note**  
To purchase the equivalent reserved DB instances for a Multi-AZ DB cluster deployment, either purchase three Single-AZ reserved DB instances, or one Multi-AZ and one Single-AZ reserved DB instance. For more information, see [Reserved DB instances for a Multi-AZ DB cluster](USER_WorkingWithReservedDBInstances.md#USER_WorkingWithReservedDBInstances.MultiAZDBClusters).

1. For **Term**, choose the length of time to reserve the the DB instance.

1. For **Offering type**, choose the offering type. 

   After you select the offering type, you can see the pricing information. 
**Important**  
Choose **Cancel** to avoid purchasing the reserved DB instance and incurring any charges. 

After you have information about the available reserved DB instance offerings, you can use the information to purchase an offering as shown in the following procedure. 

**To purchase a reserved DB instance**

1. Sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).

1. In the navigation pane, choose **Reserved instances**. 

1. 
**Important**  
Before proceeding, verify that you are in the correct AWS Region. Reserved DB instances are Region-specific and cannot be transferred between Regions. Check the Region selector in the upper-right corner of the console to ensure you are purchasing the reserved instance in the intended Region.

1. Choose **Purchase reserved DB instance**.

1. For **Product description**, choose the DB engine and licensing type.

1. For **DB instance class**, choose the DB instance class.

1. For **Multi-AZ deployment**, choose whether you want a Single-AZ or Multi-AZ DB instance deployment.
**Note**  
To purchase the equivalent reserved DB instances for a Multi-AZ DB cluster deployment, either purchase three Single-AZ reserved DB instances, or one Multi-AZ and one Single-AZ reserved DB instance. For more information, see [Reserved DB instances for a Multi-AZ DB cluster](USER_WorkingWithReservedDBInstances.md#USER_WorkingWithReservedDBInstances.MultiAZDBClusters).

1. For **Term**, choose the length of time you want the DB instance reserved.

1. For **Offering type**, choose the offering type.

   After you choose the offering type, you can see the pricing information.  
![\[Purchase reserved DB instance console\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/reservedinstance.png)

1. (Optional) You can assign your own identifier to the reserved DB instances that you purchase to help you track them. For **Reserved Id**, type an identifier for your reserved DB instance.

1. Choose **Submit**.

   Your reserved DB instance is purchased, then displayed in the **Reserved instances** list.

After you have purchased reserved DB instances, you can get information about your reserved DB instances as shown in the following procedure.

**To get information about reserved DB instances for your AWS account**

1. Sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).

1. In the **Navigation** pane, choose **Reserved instances**.

   The reserved DB instances for your account appear. To see detailed information about a particular reserved DB instance, choose that instance in the list. You can then see detailed information about that instance in the detail pane at the bottom of the console.

## AWS CLI
<a name="USER_WorkingWithReservedDBInstances.CLI"></a>

You can use the AWS CLI to work with reserved DB instances as shown in the following examples.

**Example of getting available reserved DB instance offerings**  
To get information about available reserved DB instance offerings, call the AWS CLI command [https://docs.aws.amazon.com/cli/latest/reference/rds/describe-reserved-db-instances-offerings.html](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-reserved-db-instances-offerings.html).  

```
aws rds describe-reserved-db-instances-offerings
```
This call returns output similar to the following:   

```
 1. OFFERING  OfferingId                            Class         Multi-AZ  Duration  Fixed Price  Usage Price  Description  Offering Type
 2. OFFERING  438012d3-4052-4cc7-b2e3-8d3372e0e706  db.r3.large   y         1y        1820.00 USD  0.368 USD    mysql        Partial  Upfront
 3. OFFERING  649fd0c8-cf6d-47a0-bfa6-060f8e75e95f  db.r3.small   n         1y         227.50 USD  0.046 USD    mysql        Partial  Upfront
 4. OFFERING  123456cd-ab1c-47a0-bfa6-12345667232f  db.r3.small   n         1y         162.00 USD   0.00 USD    mysql        All      Upfront
 5.     Recurring Charges:   Amount  Currency  Frequency        
 6.     Recurring Charges:   0.123   USD       Hourly
 7. OFFERING  123456cd-ab1c-37a0-bfa6-12345667232d  db.r3.large   y         1y         700.00 USD   0.00 USD    mysql        All      Upfront
 8.     Recurring Charges:   Amount  Currency  Frequency
 9.     Recurring Charges:   1.25    USD       Hourly
10. OFFERING  123456cd-ab1c-17d0-bfa6-12345667234e  db.r3.xlarge  n         1y        4242.00 USD   2.42 USD    mysql        No       Upfront
```

After you have information about the available reserved DB instance offerings, you can use the information to purchase an offering.

To purchase a reserved DB instance, use the AWS CLI command [https://docs.aws.amazon.com/cli/latest/reference/rds/purchase-reserved-db-instances-offering.html](https://docs.aws.amazon.com/cli/latest/reference/rds/purchase-reserved-db-instances-offering.html) with the following parameters:
+ `--reserved-db-instances-offering-id` – The ID of the offering that you want to purchase. See the preceding example to get the offering ID.
+ `--reserved-db-instance-id` – You can assign your own identifier to the reserved DB instances that you purchase to help track them.

**Example of purchasing a reserved DB instance**  
The following example purchases the reserved DB instance offering with ID *649fd0c8-cf6d-47a0-bfa6-060f8e75e95f*, and assigns the identifier of *MyReservation*.  
For Linux, macOS, or Unix:  

```
aws rds purchase-reserved-db-instances-offering \
    --reserved-db-instances-offering-id 649fd0c8-cf6d-47a0-bfa6-060f8e75e95f \
    --reserved-db-instance-id MyReservation
```
For Windows:  

```
aws rds purchase-reserved-db-instances-offering ^
    --reserved-db-instances-offering-id 649fd0c8-cf6d-47a0-bfa6-060f8e75e95f ^
    --reserved-db-instance-id MyReservation
```
The command returns output similar to the following:   

```
1. RESERVATION  ReservationId      Class        Multi-AZ  Start Time                Duration  Fixed Price  Usage Price  Count  State            Description  Offering Type
2. RESERVATION  MyReservation      db.r3.small  y         2011-12-19T00:30:23.247Z  1y        455.00 USD   0.092 USD    1      payment-pending  mysql        Partial  Upfront
```

After you have purchased reserved DB instances, you can get information about your reserved DB instances.

To get information about reserved DB instances for your AWS account, call the AWS CLI command [https://docs.aws.amazon.com/cli/latest/reference/rds/describe-reserved-db-instances.html](https://docs.aws.amazon.com/cli/latest/reference/rds/describe-reserved-db-instances.html), as shown in the following example.

**Example of getting your reserved DB instances**  

```
aws rds describe-reserved-db-instances
```
The command returns output similar to the following:   

```
1. RESERVATION  ReservationId     Class        Multi-AZ  Start Time                Duration  Fixed Price  Usage Price  Count  State    Description  Offering Type
2. RESERVATION  MyReservation     db.r3.small  y         2011-12-09T23:37:44.720Z  1y        455.00 USD   0.092 USD    1      retired  mysql        Partial  Upfront
```

## RDS API
<a name="USER_WorkingWithReservedDBInstances.API"></a>

You can use the RDS API to work with reserved DB instances:
+ To get information about available reserved DB instance offerings, call the Amazon RDS API operation [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeReservedDBInstancesOfferings.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeReservedDBInstancesOfferings.html).
+ After you have information about the available reserved DB instance offerings, you can use the information to purchase an offering. Call the [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_PurchaseReservedDBInstancesOffering.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_PurchaseReservedDBInstancesOffering.html) RDS API operation with the following parameters:
  + `--reserved-db-instances-offering-id` – The ID of the offering that you want to purchase.
  + `--reserved-db-instance-id` – You can assign your own identifier to the reserved DB instances that you purchase to help track them.
+ After you have purchased reserved DB instances, you can get information about your reserved DB instances. Call the [https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeReservedDBInstances.html](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_DescribeReservedDBInstances.html) RDS API operation.

# Viewing the billing for reserved DB instances for Amazon RDS
<a name="reserved-instances-billing"></a>

You can view the billing for your reserved DB instances in the Billing Dashboard in the AWS Management Console.

**To view reserved DB instance billing**

1. Sign in to the AWS Management Console.

1. From the **account menu** at the upper right, choose **Billing Dashboard**.

1. Choose **Bill Details** at the upper right of the dashboard.

1. Under **AWS Service Charges**, expand **Relational Database Service**.

1. Expand the AWS Region where your reserved DB instances are, for example **US West (Oregon)**.

   Your reserved DB instances and their hourly charges for the current month are shown under **Amazon Relational Database Service for *Database Engine* Reserved Instances**.  
![\[View monthly costs for a reserved DB instance\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/ri-db-billing1.png)

   The reserved DB instance in this example was purchased All Upfront, so there are no hourly charges.

1. Choose the **Cost Explorer** (bar graph) icon next to the **Reserved Instances** heading.

   The Cost Explorer displays the **Monthly EC2 running hours costs and usage** graph.

1. Clear the **Usage Type Group** filter to the right of the graph.

1. Choose the time period and time unit for which you want to examine usage costs.

   The following example shows usage costs for on-demand and reserved DB instances for the year to date by month.  
![\[View usage costs for on-demand and reserved DB instances\]](http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/images/ri-db-billing2.png)

   The reserved DB instance costs from January through June 2021 are monthly charges for a Partial Upfront instance, while the cost in August 2021 is a one-time charge for an All Upfront instance.

   The reserved instance discount for the Partial Upfront instance expired in June 2021, but the DB instance wasn't deleted. After the expiration date, it was simply charged at the on-demand rate.