By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

RDS Auto Scaling - Bug/feature request

0

Hello there,

We have enabled Auto Scaling for one of our RDS Aurora MySQL Cluster.

Writer Size: db.r6g.2xlarge

Reader Size: db.r6g.large

  • Whenever scale out happens, it creates new instance with the same size as Writer node(in this case size is db.r6g.2xlarge). We expected it to create new instances with same size as Reader node(db.r6g.large).

  • Also the new instance doesn't inherit the tags from the cluster.

If it's not bug, please take this as feature request

  • Higher
    a year ago

    As best practice you should have the WRITER and the READER with the same size, in case of failover your reader could get short on resources if they are different.

Topics
Migration & ModernizationAnalyticsDatabaseManagement & Governance
Tags
Amazon Relational Database ServiceAWS Auto ScalingAurora MySQL
Language
English
AWS-User-0417258
asked a year ago272 views
1 Answer
2
Accepted Answer

Hello,

As per this documentation, When Aurora Auto Scaling adds a new Aurora Replica, the new Aurora Replica is the same DB instance class as the one used by the primary instance. This is recommended as in case the reader promoted as writer, to give similar performance as old writer.

However, understand your requirements to have configurable instance types while autoscaling aurora replicas. Will forward this feature request . Thank you !

Thank you !

AWS
gokul_guna
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content