Menu
Amazon Relational Database Service
User Guide (API Version 2014-10-31)

DB Instance Class

The computation and memory capacity of a DB instance is determined by its DB instance class. You can change the CPU and memory available to a DB instance by changing its DB instance class; to change the DB instance class, you must modify the DB instance. For pricing information on DB instance classes, go to the Amazon RDS pricing page.

The DB instance class you need depends on your processing power and memory requirements. There are DB instance classes that support both "bursty" database access and sustained access. For best practices suggestions on determining your memory needs, see DB Instance RAM Recommendations. For more information about storage choices, see Storage for Amazon RDS.

Current Generation DB Instance Classes

Current generation DB instance classes include the following:

Instance TypeCurrent Generation DB Instance Classes
Standard (Latest Generation)

db.m4.large | db.m4.xlarge | db.m4.2xlarge | db.m4.4xlarge | db.m4.10xlarge

Standard (Previous Generation)

db.m3.medium | db.m3.large | db.m3.xlarge | db.m3.2xlarge

Memory Optimizeddb.r3.large | db.r3.xlarge | db.r3.2xlarge | db.r3.4xlarge | db.r3.8xlarge
Burst Capabledb.t2.micro | db.t2.small | db.t2.medium | db.t2.large

The following list describes the current Amazon RDS DB instance classes and the Amazon EC2 instance type used for each:

  • Standard – Latest Generation (db.m4) – Third generation instances that provide more computing capacity than the second generation db.m3 instance classes at a lower price. This DB instance class requires that the DB instance be in a VPC.

    Note

    Multi-AZ deployments using db.m4 instance classes are not available in the Asia Pacific (Sydney) region.

    The db.m4 instance classes are not available for the South America (Sao Paulo) or China (Beijing) regions.

    Current generation instance classes are available for the following DB engines:

    DB EngineAvailability
    MySQLMySQL version 5.5 and 5.6 are supported.
    Oracle

    All versions are supported, except that Standard Edition,Standard Edition One, and Standard Edition Two only support db.m4.large and larger instance classes, up to db.m4.4xlarge. Only Oracle Enterprise Edition (Bring Your Own License) supports the db.m4.10xlarge instance class.

    SQL Server
    • db.m4 instance classes are not supported for SQL Server Express (License Included) and SQL Server Enterprise (License Included) editions.

    • SQL Server Standard (License Included) and SQL Server Web (License Included) editions only support db.m4.large and larger instance classes, up to db.m4.4xlarge.

    • Multi-AZ deployments using db.m4 instance classes are only available for SQL Server Standard (Bring Your Own License), SQL Server Standard (License Included), SQL Server Enterprise (Bring Your Own License), and SQL Server Enterprise (License Included) offerings, and are only available in the US West (Oregon), US East (N. Virginia), and EU (Ireland) regions.

    PostgreSQLAll versions are supported.
    AuroraAurora is not supported.
    MariaDBMariaDB version 10.0.17 is supported.
  • Standard – Previous Generation (db.m3) – Second generation instances that provide a balance of compute, memory, and network resources, and are a good choice for many applications.

  • Memory Optimized – Current Generation (db.r3) – Second generation instances that provide memory optimization and more computing capacity than the first generation db.m2 instance classes at a lower price. AWS provides db.r3 DB instance classes for MySQL 5.6, PostgreSQL, Amazon Aurora, MariaDB, SQL Server, and Oracle DB instances. The db.r3 DB instances classes are not available in the South America (Sao Paulo) and AWS GovCloud (US) regions.

    Memory optimized instances (db.r3) are available for the following DB engines:

    DB EngineAvailability
    MySQLMySQL version 5.5 and 5.6 are supported.
    Oracle

    Standard Edition supports db.r3.large and larger instance classes, up to db.r3.8xlarge.

    Enterprise Edition supports db.r3.large and larger instance classes, up to db.r3.8xlarge.

    Standard Edition One supports db.r3.large and larger instance classes, up to db.r3.4xlarge.

    Standard Edition Two supports db.r3.large and larger instance classes, up to db.r3.4xlarge.

    SQL Server
    • SQL Server Express is not supported due to Microsoft licensing restrictions.

    • SQL Server Standard with Bring Your Own License (BYOL) supports db.r3.2xlarge and smaller DB instance classes due to the editions' memory and CPU limitations. SQL Server Standard with License Included (LI) is not supported.

    • SQL Server Web supports db.r3.2xlarge and smaller DB instance classes due to the editions' memory and CPU limitations.

      Note

      SQL Server Multi-AZ deployments using db.r3 instance classes are currently available only for SQL Server Standard and SQL Server Enterprise.

    PostgreSQLAll versions are supported.
    AuroraAll versions are supported.
    MariaDBMariaDB version 10.0.17 is supported.

    MySQL DB instances created after April 23, 2014, can switch to the db.r3 instance classes by modifying the DB instance just as with any other modification. MySQL DB instances running MySQL versions 5.1 or 5.5 and created before April 23, 2014, must first upgrade to MySQL version 5.6. For information on upgrading a MySQL DB instance, see Upgrading Database Versions for a DB Instance. For more information, go to R3 Instances in the Amazon EC2 documentation.

    Oracle DB instances (Version's 11.2.0.4 and 12.1.0.2 and above) created after August 06, 2015 (except in the GovCloud region), can switch to the db.r3 instance classes by modifying the DB instance just as with any other modification. To migrate an existing instance launched before this date, first upgrade your instance to Oracle database version 11.2.0.4 or 12.1.0.2, and then create and restore a snapshot of that database instance to a new R3 or T2 instance.

  • Burst Capable – Current Generation (db.t2) – Instances that provide baseline performance level with the ability to burst to full CPU usage. This DB instance class requires that the DB instance be in a VPC. Currently, it is not supported in AWS GovCloud (US).

    If you have an existing DB instance that you want to move to the db.t2 DB instance class, note that the db.t2 DB instance class requires a VPC; if your current DB instance is not in a VPC, see Moving a DB Instance Not in a VPC into a VPC to find out how to move a DB instance not in a VPC into a VPC. For more information about T2 instances used with the db.t2 DB instance class, go to T2 Instances in the Amazon EC2 documentation.

    DB EngineAvailability
    MySQLMySQL version 5.5 and 5.6 are supported.
    Oracle

    Standard Edition is supported for Bring Your Own License (BYOL).

    Enterprise Edition is supported for Bring Your Own License (BYOL).

    Standard Edition Two is supported for Bring Your Own License (BYOL).

    Standard Edition One is supported for Bring Your Own License (BYOL) and License Included.

    If you want to use a micro DB instance class, the db.t2.micro DB instance class is recommended for use with Oracle versions 11.2.0.4 and 12.1.0.2. The db.t1.micro DB instance class only supports Oracle versions 11.2.0.2, 11.2.0.3, and 12.1.0.1.

    SQL Server

    SQL Server Standard is supported for Bring Your Own License (BYOL).

    SQL Server Enterprise Edition is supported for Bring Your Own License (BYOL).

    PostgreSQLAll versions are supported.
    AuroraAurora is not supported.
    MariaDBMariaDB version 10.0.17 is supported.

Previous Generation DB Instance Classes

Previous generation DB instance classes include the following:

Instance TypePrevious Generation DB Instance Classes
Standard

db.m1.small | db.m1.medium | db.m1.large | db.m1.xlarge

Memory Optimized

db.m2.xlarge | db.m2.2xlarge | db.m2.4xlarge | db.cr1.8xlarge

Microdb.t1.micro
  • Standard – Previous Generation – Previous generation general-purpose instances. For more information, go to Instance Type in the Amazon EC2 documentation.

  • Memory Optimized – Previous Generation (db.m2) – First generation memory-optimized instances. For more information, go to Instance Type in the Amazon EC2 documentation.

  • Micro Instances (db.t1.micro) – An instance sufficient for testing that should not be used for production applications. Using a db.t1.micro instance with Oracle is a limited test configuration. If you want to use a micro DB instance class, the db.t1.micro DB instance class only supports Oracle versions 11.2.0.2, 11.2.0.3, and 12.1.0.1.

    We recommend that you use db.t1.micro instances with Oracle to test setup and connectivity only; the system resources for a db.t1.micro instance do not meet the recommended configuration for Oracle. No Oracle options are supported on a db.t1.micro instance. For more information, see the Micro Instances topic in the Amazon EC2 documentation.

Specifications for All Available DB Instance Classes

The following table provides details of the Amazon RDS DB instance classes.

Instance ClassvCPUECUMemory (GB)EBS OptimizedNetwork Performance
Micro Instances     

db.t1.micro

1

1.615NoVery Low

db.m1.small

1

11.7NoVery Low
Standard - Current Generation (VPC only)     

db.m4.large

2

6.58450 MbpsModerate

db.m4.xlarge

4

1316750 MbpsHigh

db.m4.2xlarge

8

25.5321000 MbpsHigh

db.m4.4xlarge

16

53.5642000 MbpsHigh

db.m4.10xlarge

40

124.51604000 Mbps10 GBps
Memory Optimized - Current Generation     

db.r3.large

2

6.515NoModerate

db.r3.xlarge

4

1330.5500 MbpsModerate

db.r3.2xlarge

8

26611000 MbpsHigh

db.r3.4xlarge

16

521222000 MbpsHigh

db.r3.8xlarge

32

104244No10 Gbps
Burst Capable - Current Generation (VPC only)     

db.t2.micro

1

11NoLow

db.t2.small

1

12NoLow

db.t2.medium

2

24NoModerate

db.t2.large

2

28NoModerate
Standard - Previous Generation     

db.m3.medium

1

33.75NoModerate

db.m3.large

2

6.57.5NoModerate

db.m3.xlarge

4

1315500 MbpsHigh

db.m3.2xlarge

8

26301000 MbpsHigh
Memory Optimized - Previous Generation     

db.m2.xlarge

2

6.517.1NoModerate

db.m2.2xlarge

4

1334.2500 MbpsModerate

db.m2.4xlarge

8

2668.41000 MbpsHigh

db.cr1.8xlarge

32

88244No10 Gbps

Note

The table column information includes:

  • vCPU – A virtual CPU, or virtual central processing unit, 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 provide a consistent amount of CPU capacity no matter what the actual underlying hardware.

  • ECU – The EC2 Compute Unit provides the relative measure of the integer processing power of an Amazon EC2 instance. In order 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 (GB) – Specifies the RAM memory, in gigabytes, allocated to the DB instance. Note that there is often a consistent ratio between memory and vCPU. For example, the db.m1 DB instance class has the same memory to vCPU ratio as the db.m3 DB instance class, but db.m3 instance classes provide better, more consistent performance that db.m1 instances for most use cases. db.m3 instance classes are also less expensive than db.m1 instances.

  • EBS-optimized – DB instance uses an optimized configuration stack and provides additional, dedicated capacity for Amazon Elastic Block Store (Amazon EBS) I/O. This optimization provides the best performance for your Amazon EBS volumes by minimizing contention between Amazon EBS I/O and other traffic from your instance. For more information about Amazon EBS–optimized instances, go to Amazon EBS–Optimized Instances in the Amazon EC2 documentation.

  • Network Performance – The network speed relative to other DB instance classes.