Starting March 11, RedShift supports Stop and Start operations. Till now, a RedShift cluster had to be on all the time. Now, AWS is providing more flexibility for cost-saving operations. RedShift is meant for big warehouses, so destroying and recreating databases was not an option, especially for development purposes. AWS has implemented three kinds of pause operations:
The latest option could be quite interesting for developers, so they can have the system ready when they start to work.
These operations are also available through the API
$ aws redshift pause-cluster --cluster identifier
$ aws redshift resume-cluster --cluster identifier
which makes it quite interesting also for the CICD pipelines.
When the cluster is paused, only storage costs are incurred. These actions will allow you more flexibility and control over your costs for the RedShift clusters.