CirrusHQs' Database Refresh solution automatically migrates Aurora and RDS database snapshots from a production AWS Account to a non-production AWS Account to securely refresh the non-production environment with production-level data to allow for performance testing at a production scale. Migrating Database Data cross-account can be a long, complex and manual process requiring a high level of effort due to long-running tasks which can be extremely error-prone. With this solution, the process is streamlined with a one-click approach to execute the migration process; simply sit back and wait for it to complete!

This solution provisions all infrastructure components by utilising Infrastructure as Code (IaC) and a CI/CD CodePipeline to deploy an AWS Step Function State Machine to orchestrate database snapshot copy, re-encryption, restore and cleanup of the non-production database with zero impact to the production database. Due to the end-to-end fully automated approach of this solution, errors due to human errors are mitigated. With Slack Integration as standard, your team is informed about the Database Refresh process every step of the way.

CirrusHQ Database Refresh is optionally executed on a schedule to periodically refresh non-production databases, customisable to the business requirements. Additional customisations and requirements can be discussed and designed to meet business needs;

• Database Anonymisation to randomise sensitive PII Data. Anonymisation scripts are custom to the Database Schema and your use case.
• Non-Production Database Table backup and restore to persist data specific to the environment, such as configuration tables.