Read our blog for the latest insights on sales and marketing Take Me There
Webinar: Use Sugar Data to Easily Generate Complex Documents Register
Webinar: Advanced Calendar Solution for Sugar Register
You can now set the minimum capacity of your Aurora Serverless DB clusters to 1 Aurora Capacity Unit (ACU). With Aurora Serverless, you specify the minimum and maximum ACUs for your Aurora Serverless DB cluster instead of provisioning and managing database instances. Each ACU is a combination of processing and memory capacity. By setting the minimum capacity to 1 ACU, you can keep your Aurora Serverless DB cluster running at a lower cost.
Aurora Serverless now allows you to specify how a capacity change is applied to your DB cluster. By default, Aurora Serverless finds a point at which the capacity change is non-disruptive to your application. If it is unable to find a point, the capacity change is timed out and discarded. You can now choose to apply capacity changes even when a scaling point is not found. If you opt to forcibly apply capacity changes, active connections to your database may get dropped. This configuration could be used to more readily scale capacity of your Aurora Serverless DB clusters if your application is resilient to connection drops.
You can now share snapshots of Aurora Serverless DB clusters with other AWS accounts or publicly. We are also giving you the ability to copy Aurora Serverless DB cluster snapshots across AWS regions.
Authorized AWS accounts can restore a DB cluster directly from the shared DB cluster snapshot without copying it. DB cluster snapshots could be shared for a variety of scenarios, for example, when you use different AWS accounts for separation of development and production environments, share data with partners, or collaborate publicly on research projects. Copying DB cluster snapshots to another AWS region allows you to keep a copy of your data for disaster recovery. You may also copy DB cluster snapshots to other regions for database migration.
You can now restore MySQL 5.7 backups stored in Amazon S3 to Amazon Aurora with MySQL compatibility and Amazon RDS for MySQL.
If you are migrating a MySQL 5.5, 5.6, or 5.7 database to Aurora with MySQL compatibility or RDS for MySQL, you can copy database backups to an Amazon S3 bucket and restore them for a faster migration. Both full and incremental backups of your database can be restored. Restoring backups can be considerably quicker than moving data using the mysqldump utility, which replays SQL statements to recreate the database.
Restore your database backups with just a few clicks on the AWS management console or alternatively, use the latest AWS SDK or CLI. Refer Aurora with MySQL compatibility and RDS for MySQL documentation to learn more about migrations using database backups.