Enable support for blue/green deployments on RDS instances

[ArsHaider]

Customers are requesting that blue/green deployments be enabled/supported. The reason for this request is so that they can more seamlessly upgrade their RDS instances with no downtime. Using the blue/green deployment scheme changes could be made to the database without affecting production workloads and without customer data leaving the cloud.gov system’s boundary.

Notes

Users must have the required permissions to perform operations related to blue/green deployments. AWS documentation states that IAM policies can be created that grant users and roles permission to perform specific API operations on the specified resources they need.

Specifically:
The user who creates a blue/green deployment must have permissions to perform the following RDS operations:

• rds:AddTagsToResource
• rds:CreateDBInstanceReadReplica

The user who switches over a blue/green deployment must have permissions to perform the following RDS operations:

• rds:ModifyDBInstance
• rds:PromoteReadReplica

The user who deletes a blue/green deployment must have permissions to perform the following RDS operation:

• rds:DeleteDBInstance

Linked here are considerations for blue/green deployments, as well as best practices and general limitations.

Linked here is the relevant customer ticket.