OP, your strategy is mostly correct. Instances will become unavailable during the instance modification. With that in mind, you can upgrade your readers one at a time, or if you need at least two readers up at all times to handle load, add additional readers to the cluster in your target instance type and size. Once the readers are upgraded or added, you can fail the writer instance over to one of the upgraded readers. During the failover read and write operations fail with an exception. However, service is typically restored in less than 60 seconds, and often less than 30 seconds. You can improve this process with RDS Proxy. The proxy automatically routes traffic to a new database instance while preserving application connections. It also bypasses Domain Name System (DNS) caches to reduce failover times by up to 66% for Aurora Multi-AZ databases. Once you have three upgraded instances (one writer and two readers), you can delete any additional unnecessary instances. More information about high availability for Amazon Aurora is available in the User Guide. Answer from Jared Persinger on repost.aws
AWS
aws.amazon.com › amazon rds › amazon aurora › instance types
Amazon Aurora Instance Types - Amazon Web Services
3 days ago - Amazon Aurora provides a selection of instance types optimized to fit different relational database use cases. Instance types comprise varying combinations of CPU, memory, storage, and networking capacity and give you the flexibility to choose the appropriate mix of resources for your database.
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › what is amazon aurora? › amazon aurora db instance classes
Amazon Aurora DB instance classes - Amazon Aurora
The DB instance class determines the computation and memory capacity of an Amazon Aurora 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.
Aurora cluster, DB Instance class for my region
Your input can influence how we create and update our content to better support your AWS journey. ... EngineVersion=8.0.mysql_aurora.3.06.0, for this version what are the supported DB instance classes I tried to find out but didn't get any relevant document please help me out. More on repost.aws
AWS Aurora Mysql different instance types for writer/reader
That is completely supported, and recommended, by many people. Why spend the extra money on resources you won't utilize. Just make sure you understand the limitations of the instance class you are using for the reader, and how it affects the IO, CPU and memory characteristics. (Especially on a pretty constrained t3 instance (relative to an r5), if you end up doing a lot of joins, use temp tables, etc...). If your database is read-mostly, perhaps consider changing it around and shift most traffic to the reader (with the bigger instance), and limit the read traffic going to the writer. EDIT: you should make sure you also understand how the system will behave in the event of a failure/failover of the writer. If the smaller instance is promoted, and doesn't have the capacity to handle all of the traffic, you will end up having a bad time More on reddit.com
Choosing RDS/Aurora instance
I'd also query whether the right database for you is actually AWS Athena, and putting the data into S3. More on reddit.com
Is there no longer a small MySQL aurora instance available?
Move to aurora serverless v2 mysql8 ? Scales to 0. Should be nearly identical. The old 5.7 is now extended support and thus more costly. More on reddit.com
Top answer 1 of 3
1
OP, your strategy is mostly correct. Instances will become unavailable during the instance modification. With that in mind, you can upgrade your readers one at a time, or if you need at least two readers up at all times to handle load, add additional readers to the cluster in your target instance type and size. Once the readers are upgraded or added, you can fail the writer instance over to one of the upgraded readers. During the failover read and write operations fail with an exception. However, service is typically restored in less than 60 seconds, and often less than 30 seconds. You can improve this process with RDS Proxy. The proxy automatically routes traffic to a new database instance while preserving application connections. It also bypasses Domain Name System (DNS) caches to reduce failover times by up to 66% for Aurora Multi-AZ databases. Once you have three upgraded instances (one writer and two readers), you can delete any additional unnecessary instances. More information about high availability for Amazon Aurora is available in the User Guide.
2 of 3
2
There is no way to change instance class of Aurora instances. It may take up to 15 mins. From this link :
"Scaling isn't instantaneous. It can take 15 minutes or more to complete the change to a different DB instance class. We recommend that if use this approach to modify the DB instance class, you apply the change during the next scheduled maintenance window (rather than immediately) to avoid affecting users. "
Laravel Cloud
cloud.laravel.com
Laravel Cloud
Yes, enterprise customers have access to custom database integrations with AWS products like RDS, Aurora, DSQL, ElastiCache, and more.
AWS
aws.amazon.com › about-aws › whats-new › 2020 › 12 › introducing-amazon-aurora-r6g-instance-types-powered-by-aws-graviton-2-processors-in-preview
Introducing Amazon Aurora R6g instance types, powered ...
September 10, 2025 - You can launch Graviton2 R6g database instances in the Amazon RDS Management Console or using the AWS CLI. Graviton2 is supported by Aurora MySQL version 2.09.1 and higher, and Aurora PostgreSQL version 11.9 and higher. Upgrading a database instance to Graviton2 requires a simple instance type ...
AWS
aws.amazon.com › amazon rds › amazon aurora › pricing
Amazon Aurora Pricing
3 days ago - To fully utilize the benefits of your RI discounts with Aurora I/O-Optimized, you can purchase 30% additional RIs similar to your current RIs. You will be billed for each hour of the term regardless of whether any usage has occurred. You purchase a Reserved Instance for each database instance you plan to use. You may designate database instances as Reserved Instances by calling the Purchasing API or selecting the Reserved Instance option in the AWS console.
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › what is amazon aurora? › amazon aurora db instance classes › hardware specifications for db instance classes for aurora
Hardware specifications for DB instance classes for Aurora - Amazon Aurora
For information on using Amazon ... for Aurora PostgreSQL with CloudWatch metrics. The following tables show the compute, memory, storage, and bandwidth specifications for the memory-optimized instance classes. db.x2g – memory-optimized instance classes with AWS Graviton2 ...
Percona
percona.com › home › aurora vs rds: how to choose the right aws database solution
Aurora vs RDS: How to Choose the Right AWS Database Solution
February 24, 2025 - You can enable automated monitoring, and you can define the log types to publish to Amazon CloudWatch. Percona Monitoring and Management (PMM) can also be used to gather metrics. Be aware that for Aurora, there is a limitation for the T2 instances such that Performance Schema can cause the host to run out of memory if enabled.
AWSstatic
d1.awsstatic.com › training-and-certification › docs-cloud-practitioner › AWS-Certified-Cloud-Practitioner_Exam-Guide.pdf pdf
AWS Certified Cloud Practitioner (CLF-C02) Exam Guide Introduction
• AWS compute services · Version 1.0 CLF-C02 · 8 | PAGE · Skills in: • Recognizing the appropriate use of different EC2 instance types (for example, compute optimized, storage optimized) • Recognizing the appropriate use of different container options (for example, Amazon ECS, Amazon EKS) • Recognizing the appropriate use of different serverless compute options (for ·
Top answer 1 of 2
1
**To list the DB instance classes** that are supported by a specific DB engine version in an Amazon Web Services **Region**, run the following command.
**For Linux, macOS, or Unix:**
aws rds describe-orderable-db-instance-options --engine engine --engine-version version \
--query "OrderableDBInstanceOptions[].{DBInstanceClass:DBInstanceClass,SupportedEngineModes:SupportedEngineModes[0]}" \
--output table \
--region region
**For Windows:**
aws rds describe-orderable-db-instance-options --engine engine --engine-version version ^
--query "OrderableDBInstanceOptions[].{DBInstanceClass:DBInstanceClass,SupportedEngineModes:SupportedEngineModes[0]}" ^
--output table ^
--region region
The output also shows the engine modes that are supported for each DB instance class. grateful for my own efforts!!!
2 of 2
0
**Using AWS CLI**:
To list the DB engine versions that support a specific DB instance class in an Amazon Web Services Region, run the following command:
**For Linux**
aws rds describe-orderable-db-instance-options --engine engine --db-instance-class DB_instance_class \
--query "OrderableDBInstanceOptions[].{EngineVersion:EngineVersion,SupportedEngineModes:SupportedEngineModes[0]}" \
--output table \
--region region
**For Windows:**
aws rds describe-orderable-db-instance-options --engine engine --db-instance-class DB_instance_class ^
--query "OrderableDBInstanceOptions[].{EngineVersion:EngineVersion,SupportedEngineModes:SupportedEngineModes[0]}" ^
--output table ^
--region region
**Refer to the AWS documentation page**:
https://docs.amazonaws.cn/en_us/AmazonRDS/latest/AuroraUserGuide/Concepts.DBInstanceClass.html#Concepts.DBInstanceClass.SupportAurora
AWS
aws.amazon.com › blogs › database › evaluating-the-right-fit-for-your-amazon-aurora-workloads-provisioned-or-serverless-v2
Evaluating the right fit for your Amazon Aurora workloads: provisioned or Serverless v2 | AWS Database Blog
October 23, 2024 - Aurora Serverless v1 enabled users to automatically scale the size of an Aurora instance based on workload, rather than pre-provisioning compute resources using provisioned instances. Flash forward to 2022 when AWS launched Amazon Aurora Serverless v2. Aurora Serverless v2 was a major leap forward over version one. The primary difference between the two being that while Aurora Serverless v1 required a specific type of cluster (Aurora Serverless cluster), Aurora Serverless v2 was implemented as a new instance type.
DEV Community
dev.to › kazuya_dev › aws-reinvent-2025-aws-graviton-the-best-price-performance-for-your-aws-workloads-cmp307-4k0
AWS re:Invent 2025 - AWS Graviton: The best price performance for your AWS workloads (CMP307) - DEV Community
2 weeks ago - So when viewed in aggregate today, we have more than 90,000 AWS customers that are running on Graviton. And these range from some of the hottest startups all the way to very well-established Fortune 500 enterprises. And our goal is to enable a deep and a broad portfolio of Graviton instance types so that our customers can choose the right instance for the right workload.
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › what is amazon aurora? › amazon aurora storage
Amazon Aurora storage - Amazon Aurora
However, for NVMe-based DB instances, switching between Aurora I/O-Optimized and Aurora Standard storage options requires a database engine restart, which may cause a brief period of downtime. For information on AWS Region and version support, see Supported Regions and Aurora DB engines for cluster storage configurations.
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › what is amazon aurora? › amazon aurora db instance classes › db instance class types
DB instance class types - Amazon Aurora
The following Optimized Reads instance class types are available: 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.
Informatica
docs.informatica.com › ecosystem – amazon › amazon aurora connector › data type reference › amazon aurora and transformation data types
Amazon Aurora and transformation data types
Amazon Aurora mapping task example · Data type reference · Data type reference overview · Amazon Aurora and transformation data types · Back Next · The following table lists the Amazon Aurora data types that · Data Integration supports and the corresponding transformation data types: ...
Noise
noise.getoto.net › tag › rds-for-mysql
RDS for MySQL | Noise
MySQL 8.0 on Aurora MySQL, also known as Aurora MySQL 3, unlocks support for popular Aurora features, such as Global Database, Amazon RDS Proxy, Performance Insights, Parallel Query, and Serverless v2 deployments. Upgrading to RDS for MySQL 8.0 provides features including up to three times higher performance versus MySQL 5.7, such as Multi-AZ cluster deployments, Optimized Reads, Optimized Writes, and support for AWS Graviton2 and Graviton3-based instances.
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › working with amazon aurora postgresql › performance and scaling for amazon aurora postgresql
Performance and scaling for Amazon Aurora PostgreSQL - Amazon Aurora
Don't use db.t2 or db.t3 instance classes for larger Aurora clusters of size greater than 40 terabytes (TB). We recommend using the T DB instance classes only for development and test servers, or other non-production servers. For more details on the T instance classes, see DB instance class types.
MySQL
mysql.com
MySQL
Use automated and integrated generative AI and machine learning (ML) in one cloud service for transactions and lakehouse scale analytics. Get faster insights from all your data with unmatched performance and deploy apps in your choice of cloud providers. Learn More » · MySQL AI provides ...