Determining an instance class Changing an instance's class Supported instance classes by Region Instance class specifications

Managing instance classes

The instance class determines the computation and memory capacity of an Amazon DocumentDB (with MongoDB compatibility) instance. The instance class you need depends on your processing power and memory requirements.

Amazon DocumentDB supports the R4, R5, R6G, R8G, T3, and T4G families of instance classes. These classes are current-generation instance classes that are optimized for memory-intensive applications. For the specifications on these classes, see Instance class specifications.

Determining an instance class

To determine the class of an instance, you can use the AWS Management Console or the describe-db-instances AWS CLI operation.

Using the AWS Management Console

To determine the instance class for your cluster's instances, complete the following steps in the console.

Sign in to the AWS Management Console, and open the Amazon DocumentDB console at https://console.aws.amazon.com/docdb.
In the navigation pane, choose Clusters to find the instance that you're interested in.

Tip
If you don't see the navigation pane on the left side of your screen, choose the menu icon () in the upper-left corner of the page.
In the Clusters navigation box, you’ll see the column Cluster Identifier. Your instances are listed under clusters, similar to the following screenshot.
In the list of instances, expand the cluster to find the instances you are interested in. Find the instance that you want. Then, look at the Size column of the instance's row to see its instance class.

In the following image, the instance class for instance robo3t is db.r5.4xlarge.

Using the AWS CLI

To determine the class of an instance using the AWS CLI, use the describe-db-instances operation with the following parameters.

--db-instance-identifier — Optional. Specifies the instance that you want to find the instance class for. If this parameter is omitted, describe-db-instances returns a description for up to 100 of your instances.
--query — Optional. Specifies the members of the instance to include in the results. If this parameter is omitted, all instance members are returned.

Example

The following example finds the instance name and class for the instance sample-instance-1.

For Linux, macOS, or Unix:


aws docdb describe-db-instances \
    --query 'DBInstances[*].[DBInstanceIdentifier,DBInstanceClass]' \
    --db-instance-identifier sample-instance-1

For Windows:


aws docdb describe-db-instances ^
    --query 'DBInstances[*].[DBInstanceIdentifier,DBInstanceClass]' ^
    --db-instance-identifier sample-instance-1

Output from this operation looks something like the following.


[
    [
        "sample-instance-1",
        "db.r5.large"
    ]

Example

The following example finds the instance name and class for up to 100 Amazon DocumentDB instances.

For Linux, macOS, or Unix:


aws docdb describe-db-instances \
    --query 'DBInstances[*].[DBInstanceIdentifier,DBInstanceClass]' \
    --filter Name=engine,Values=docdb

For Windows:


aws docdb describe-db-instances ^
    --query 'DBInstances[*].[DBInstanceIdentifier,DBInstanceClass]' ^
    --filter Name=engine,Values=docdb

Output from this operation looks something like the following.


[
    [
        "sample-instance-1",
        "db.r5.large"
    ],
    [
        "sample-instance-2",
        "db.r5.large"
    ],
    [
        "sample-instance-3",
        "db.r5.4xlarge"
    ],
    [
        "sample-instance-4",
        "db.r5.4xlarge"
    ]
]

For more information, see Describing Amazon DocumentDB instances.

Changing an instance's class

You can change the instance class of your instance using the AWS Management Console or the AWS CLI. For more information, see Modifying an Amazon DocumentDB instance.

Supported instance classes by Region

Amazon DocumentDB supports the following instance classes:

R8G—Latest generation of memory-optimized instances powered by Arm-based AWS Graviton4 processors that provide up to 30% better performance over R6G instances.
R6G—Memory-optimized instances powered by Arm-based AWS Graviton2 processors that provide up to 30% better performance over R5 instances at 5% less cost.
R6GD—Memory-optimized R6G instances with local non-volatile memory express (NVMe)-based Solid-State Drive (SSD) storage for ephemeral data.
R5—Memory-optimized instances that provide up to 100% better performance over R4 instances for the same instance cost.
R4—Previous generation of memory-optimized instances.
T4G—Latest-generation low cost burstable general-purpose instance type powered by Arm-based AWS Graviton2 processors that provides a baseline level of CPU performance, delivering up to 35% better price performance over T3 instances and ideal for running applications with moderate CPU usage that experience temporary spikes in usage.
T3—Low cost burstable general-purpose instance type that provides a baseline level of CPU performance with the ability to burst CPU usage at any time for as long as required.

For detailed specifications on the instance classes, see Instance class specifications.

Note

I/O-Optimized storage is only available on engine versions 5.0 and 8.0 (instance-based clusters).

A particular instance class may or may not be supported in a given Region. The following table specifies which instance classes are supported by Amazon DocumentDB in each Region.

Supported instance classes by Region
	Instance Classes
Region	R8G	R6GD	R6G	R5	R4	T4G	T3	Serverless
US East (Ohio)	Supported	Supported	Supported	Supported	Supported	Supported	Supported	Supported
US East (N. Virginia)	Supported	Supported	Supported	Supported	Supported	Supported	Supported	Supported
US West (Oregon)	Supported	Supported	Supported	Supported	Supported	Supported	Supported	Supported
Africa (Cape Town)			Supported	Supported		Supported	Supported	Supported
South America (São Paulo)	Supported	Supported	Supported	Supported		Supported	Supported	Supported
Asia Pacific (Hong Kong)	Supported		Supported	Supported		Supported	Supported	Supported
Asia Pacific (Hyderabad)			Supported	Supported		Supported	Supported	Supported
Asia Pacific (Malaysia)			Supported			Supported	Supported	Supported
Asia Pacific (Mumbai)	Supported	Supported	Supported	Supported		Supported	Supported	Supported
Asia Pacific (Osaka)	Supported	Supported	Supported	Supported		Supported	Supported	Supported
Asia Pacific (Seoul)	Supported	Supported	Supported	Supported		Supported	Supported	Supported
Asia Pacific (Sydney)	Supported	Supported	Supported	Supported		Supported	Supported	Supported
Asia Pacific (Jakarta)	Supported	Supported	Supported	Supported		Supported	Supported	Supported
Asia Pacific (Melbourne)			Supported	Supported		Supported	Supported	Supported
Asia Pacific (Singapore)	Supported	Supported	Supported	Supported		Supported	Supported	Supported
Asia Pacific (Thailand)			Supported			Supported	Supported	Supported

Managing instance classes

Topics

Determining an instance class

Tip

Example

Example

Changing an instance's class

Supported instance classes by Region

Note