CloudWiki
Rules
Medium

Ensure RDS instances have Multi-AZ disabled in dev environments

AWS Cost Optimization
Description

In order to reduce costs and optimize resources in development environments, it is recommended to disable Multi-AZ deployment configurations for AWS RDS instances. This configuration is intended for high availability and redundancy in production environments, but it is not necessary for non-production environments where high availability is not a critical concern. Disabling Multi-AZ deployment can result in significant cost savings while still providing reliable database access for development and testing purposes.

Remediation

To ensure RDS instances have Multi-AZ disabled in dev environments, follow these remediation steps:

  1. Open the Amazon RDS console.
  2. Select the region where your RDS instance is located.
  3. Select the RDS instance for which you want to disable Multi-AZ.
  4. Choose "Instance actions", and then choose "Modify".
  5. Scroll down to the "Multi-AZ deployment" section and uncheck the box for "Enable Multi-AZ deployment".
  6. Review the other settings on the page and make any necessary changes.
  7. Click "Continue" and review the summary of changes.
  8. Click "Modify DB instance" to apply the changes.

Once Multi-AZ has been disabled, you can verify the change by checking the "Multi-AZ deployment" status for the RDS instance in the console. It should show as "No".

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.