Friday 2 November 2018

Now, Start and Stop for Multi AZ Database Instaces allowed in Amazon RDS

For a natural fit of production database workloads, Amazon RDS Multi-AZ deployments gives amplified availability and durability for Database (DB) Instances. Amazon RDS automatically generates a primary DB Instance and synchronously reproduces the data to a standby instance in a discrete Availability Zone (AZ) when you gives a Multi-AZ DB Instance. Each AZ operates on its personal physically different, independent infrastructure, and is engineered to be mostly valid. Amazon RDS executes an automatic failover to the standby (or to a read replica in the case of Amazon Aurora) when an infrastructure fails, so that you can restart database operations as soon as the failover is finish. Since the endpoint for your DB Instance stays the same after a failover, your application can restart database operation without the require for manual administrative involvement.

Amazon RDS for MySQL, MariaDB, PostgreSQL, and Oracle now allow you to stop and start database instances that are running in a Multi-AZ configuration. This makes it simple and inexpensive to use databases for development and test reasons that match the configuration of your production databases but are not needed to be executing all of the time.

To start and stop a database instance needs just a few clicks in the AWS Management Console, or a single call using the AWS API or AWS CLI. You are charged for provisioned database storage and backup storage, when your database instance is stopped but not for database instance hours.

To read more about stopping and starting a database instance, go through Stopping and Starting a DB Instance in the Amazon RDS User Guide.

No comments:

Post a Comment

Maximizing Content Delivery Efficiency: Optimizing Performance in AWS CloudFront

  Unleash Blazing-Fast Content Delivery: Your Guide to CloudFront Optimization Introduction: AWS CloudFront stands as a cornerstone of moder...