Generated with sparks and insights from 4 sources

img10

img11

img12

img13

img14

img15

Introduction

  • Aurora MySQL version 3 does not support the db.t3.small instance class.

  • The smallest instance classes supported by Aurora MySQL version 3 are db.t3.medium and db.t4g.medium.

  • This change can have cost implications, as the db.t3.medium is more expensive than the db.t3.small.

  • Aurora MySQL version 3 supports a different set of instance classes compared to version 2, which included db.t3.small.

  • The db.t3.small instance class is intended for development and test scenarios, not for production workloads.

Instance Class Support [1]

  • Aurora MySQL version 3 supports instance classes such as db.t3.medium and db.t4g.medium for smaller instances.

  • Larger instance classes supported include db.r5, db.r6g, and db.x2g.

  • Instance classes like db.r4, db.r3, db.t3.small, and db.t2 are not supported in Aurora MySQL version 3.

  • Check your administration scripts for any CLI statements that create Aurora MySQL DB instances to ensure compatibility.

  • Use the [describe-orderable-db-instance-options](prompt://ask_markdown?question=describe-orderable-db-instance-options) AWS CLI command to check instance classes for specific combinations of Aurora MySQL version and AWS Region.

img10

Cost Implications [2]

  • The smallest instance class available in Aurora MySQL version 3 is db.t3.medium, which is more expensive than db.t3.small.

  • This change can increase costs, especially for development environments where multiple instances are used.

  • For cost-sensitive applications, consider using Aurora MySQL version 2, which supports db.t3.small.

  • The db.t4g.medium instance class is the cheapest option available in Aurora MySQL version 3.

  • Evaluate the cost differences between instance classes to determine the best fit for your budget.

Development vs. Production [3]

  • The db.t3.small instance class is intended for development and test scenarios, not for production workloads.

  • Aurora MySQL version 3's lack of support for db.t3.small means developers need to use db.t3.medium or larger instances.

  • For production workloads, consider using larger instance classes like db.r5 or db.r6g.

  • Development environments can still use Aurora MySQL version 2 if db.t3.small is required.

  • Evaluate the performance and cost trade-offs when choosing instance classes for development versus production.

Feature Differences [1]

  • Aurora MySQL version 3 supports MySQL 8.0, while version 2 supports MySQL 5.7.

  • Version 3 does not support Aurora Serverless v1 clusters, only Aurora Serverless v2.

  • The query cache is removed in Aurora MySQL version 3.

  • Aurora MySQL version 3 includes improvements like Instant DDL and compatibility with MySQL hash join feature.

  • The default character set in Aurora MySQL version 3 is utf8mb4, compared to latin1 in version 2.

Scaling Aurora MySQL [3]

  • Aurora MySQL supports instance scaling and read scaling.

  • Instance scaling involves modifying the DB instance class for each DB instance in the cluster.

  • Read scaling can be achieved by adding read replicas to the cluster.

  • Do not use db.t2 or db.t3 instance classes for larger Aurora clusters of size greater than 40 TB.

  • For detailed specifications of supported DB instance classes, refer to the Aurora DB instance classes documentation.

Related Videos

<br><br>

<div class="-md-ext-youtube-widget"> { "title": "Change the RDS DB instance type | Increase or decrease a ...", "link": "https://www.youtube.com/watch?v=mvZqOp197W4", "channel": { "name": ""}, "published_date": "Jun 17, 2023", "length": "" }</div>