- Newest
- Most votes
- Most comments
Thank you for your detailed questions about creating a read replicated database instance in Amazon RDS. I'll address each of your points:
- When you create a read replica, it doesn't necessarily inherit all configurations from the source database. By default:
- The instance class will be the same as the source.
- The storage type will be the same, but you can choose a different type.
- The allocated storage will be the same.
- Other settings like availability, connectivity, subnet group, public access, VPC security group, certificate authority, and database authentication may differ and can be configured separately for the read replica.
- Regarding the Availability/Deployment options:
2a) The Multi-AZ option you're seeing is not about creating a read replica. It's an additional feature you can apply to your read replica for high availability. Your read replica will still be created in Oregon based on the primary in Ohio.
2b) The wording refers to the Multi-AZ deployment of the read replica itself, not the replication from Ohio to Oregon.
2c) This is describing the standby instance in the Multi-AZ setup of the read replica, not the read replica itself. The read replica will support read workloads, but its standby (if you choose Multi-AZ) will not.
- Yes, once created, the replica database will be displayed in the Oregon region's "Databases" list with a "Role" value of "Replica".
Remember, creating a cross-region read replica involves additional considerations, such as data transfer costs and potentially increased replication lag due to network latency between regions.
Sources
Creating a read replica - Amazon Relational Database Service
Working with DB instance read replicas - Amazon Relational Database Service
Working with Multi-AZ read replica deployments with MySQL - Amazon Relational Database Service
CreateDBInstanceReadReplica - Amazon Relational Database Service
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 3 years ago

Thank you AI Agent for your answers and explainations!
Regarding, "2a) The Multi-AZ option you're seeing is not about creating a read replica. It's an additional feature you can apply to your read replica for high availability. Your read replica will still be created in Oregon based on the primary in Ohio."
What if we don't want any HA for the read replica, it seems there is not an option to not have HA. The other option is only a write HA instance of the the read replica. What happens if we chose "Single DB Instance"? Does that mean will have an single db instance as an HA instance for the read replica?
Thank you for your time and help! Best Regards, Donald