To create a blue/green deployment by using the AWS CLI, use the create-blue-green-deployment command with the following options:
Creating a blue/green deployment
When you create a blue/green deployment, you specify the source DB instance to copy in the deployment. The DB instance you choose is the production DB instance, and it becomes the primary DB instance in the blue environment. This DB instance is copied to the green environment, and RDS configures replication from the DB instance in the blue environment to the DB instance in the green environment.
RDS copies the blue environment’s topology to a staging area, along with its configured features. When the blue DB instance has read replicas, the read replicas are copied as read replicas of the green DB instance in the deployment. If the blue DB instance is a Multi-AZ DB instance deployment, then the green DB instance is created as a Multi-AZ DB instance deployment.
Topics
- Preparing an RDS for PostgreSQL DB instance for a blue/green deployment
- Specifying changes when creating a blue/green deployment
- Handling lazy loading when you create a blue/green deployment
- Creating a blue/green deployment
Preparing an RDS for PostgreSQL DB instance for a blue/green deployment
Before you create a blue/green deployment for an RDS for PostgreSQL DB instance, make sure to do the following:
- Associate the instance with a custom DB parameter group with logical replication ( rds.logical_replication ) turned on. Logical replication is required for replication from the blue environment to the green environment. For instructions, see Modifying parameters in a DB parameter group. In addition, depending on your database workload, tune the following configuration settings :
- max_replication_slots
- max_wal_sender
- max_logical_replication_worker
- max_worker_processes
After you enable logical replication and set all configuration options, make sure to reboot the DB instance so that your changes take effect. Blue/green deployments require that the DB instance be in sync with the DB parameter group, otherwise creation fails. For more information, see Rebooting a DB instance.
Specifying changes when creating a blue/green deployment
You can make the following changes to the DB instance in the green environment when you create the blue/green deployment.
You can make other modifications to the DB instance in the green environment after it is deployed. For example, you might make schema changes to your database or change the DB instance class used by one or more DB instances in the green environment .
For information about modifying a DB instance, see Modifying an Amazon RDS DB instance.
Specify a higher engine version
You can specify a higher engine version if you want to test a DB engine upgrade. Upon switchover, the database is upgraded to the major or minor DB engine version that you specify.
Specify a different DB parameter group
You can test how parameter changes affect the DB instances in the green environment or specify a parameter group for a new major DB engine version in the case of an upgrade.
If you specify a different DB parameter group, the specified DB parameter group is associated with all of the DB instances in the green environment. If you don’t specify a different parameter group, each DB instance in the green environment is associated with the parameter group of its corresponding blue DB instance.
Enable RDS Optimized Writes
You can use Blue/Green Deployments to upgrade to a DB instance class that supports RDS Optimized Writes. You can only enable RDS Optimized Writes on a database that was created with a supported DB instance class. Thus, this option creates a green database that uses a supported DB instance class, which enables you to turn on RDS Optimized Writes on the green DB instance.
If you’re upgrading from a DB instance class that doesn’t support RDS Optimized Writes to one that does, you must also upgrade the storage configuration of the green DB instance. For more information, see Upgrade the storage configuration.
You can only upgrade the DB instance class of the primary green DB instance. By default, read replicas in the green environment inherit the DB instance settings from the blue environment. After the green environment is successfully created, you must manually modify the DB instance class of the read replicas in the green environment.
Some instance class upgrades aren’t supported depending on the engine version and instance class of the blue DB instance. For more information about DB instance classes, see DB instance classes.
Upgrade the storage configuration
If your blue database isn’t on the latest storage configuration, RDS can migrate the green DB instance from the older storage configuration (32-bit file system) to the preferred configuration. You can use RDS Blue/Green Deployments to overcome the scaling limitations on storage and file size for older 32-bit file systems. In addition, this setting changes the storage configuration to be compatible with RDS Optimized Writes if the specified DB instance class supports Optimized Writes.
Note
Upgrading the storage configuration is an I/O-intensive operation and leads to longer creation times for blue/green deployments. The storage upgrade process is faster if the blue DB instance uses Provisioned IOPS SSD (io1) storage, and if you provisoned the green environment with an instance size of 4xlarge or larger. Storage upgrades involving General Purpose SSD (gp2) storage can deplete your I/O credit balance, resulting in longer upgrade times. For more information, see Amazon RDS DB instance storage.
During the storage upgrade process, the database engine isn’t available. If the storage consumption on your blue DB instance is greater than or equal to 90% of the allocated storage size, the storage upgrade process will increase the allocated storage size by 10% for the green instance.
This option is only available if your blue database is not on the latest storage configuration, or if you’re changing the DB instance class within the same request.
Step 1
Before painting, fill holes with filler, then sand* smooth.
When painting over dark walls with light paint colors, use a white primer. Using a primer will help to ensure that your color comes out true when dry, with no dark base color muting a light one or a light base color making it impossible to get bold color coverage. Using primer also lessens the need for additional coats of paint to get complete coverage.
Glidden Paint Primer
Step 2
When painting over dark walls with light paint colors, use a white primer. Using a primer will help to ensure that your color comes out true when dry, with no dark base color muting a light one or a light base color making it impossible to get bold color coverage. Using primer also lessens the need for additional coats of paint to get complete coverage.
When rolling the paint on the wall, roll in large, wide “M” or “W” shapes. When re-loading the roller, make sure to roll in on the slanted part of the paint tray to remove some of the paint. This will help to avoid roller lines in the paint finish. Let dry.
Applying Primer with W shape
Step 3
When rolling the paint on the wall, roll in large, wide “M” or “W” shapes. When re-loading the roller, make sure to roll in on the slanted part of the paint tray to remove some of the paint. This will help to avoid roller lines in the paint finish. Let dry.
Add a second coat to areas in which you can still see any of the previous color through the primer. Let dry.
Glidden Primer on wall
