Skip to main content

Disaster Recovery

The purpose of this section of the guide is to clarify what the Modernisation Platform offers in terms of disaster recovery, the processes to initiate different types of recovery, and roles and responsibilities of the Modernisation Platform and Service Teams.

What does the Modernisation Platform offer in terms of Disaster Recovery?

Modernisation Platform is provided to Service Teams as a managed service. To ensure business continuity, Modernisation Platform has a disaster recovery plan that facilitates quick recovery. Recovery plans have been tested and documented in the runbooks for the following scenarios:

  • Complete loss of the platform
  • Loss of an AWS account
  • Loss of networking

Other failures which will not affect the availability of an application, but will impact a team’s ability to deploy:

  • Loss of Terraform state
  • Loss of access
  • Loss of Github Actions
  • Loss of Github

In the case of all of the above the Modernisation Platform Team is responsible for recovery or raising incidents

However, in the event of the loss of the platform or AWS account we may require Service Teams to redeploy their services. This includes redeploying applications, restoring from backups, and any further manual steps required.

The Modernisation Platform Team is continually reviewing and identifying risks to our users and the platform. As each threat is identified we are testing and creating recovery plans.

What isn’t covered by the Modernisation Platform?

  • Loss or fault of infrastructure created in the member account that is not provided by the Modernisation Platform (anything other than the account baselines and SSO)
  • Restoration of member infrastructure backups.
  • Non production backups, or backups outside of the Modernisation Platform backup coverage.
  • Redeployment of applications - The Modernisation Platform doesn’t manage member application deployment pipelines. If there is a need to deploy a service as part of any restoration you will be asked to do so by the Modernisation Platform Team.
  • Only retain AWS RDS Snapshots for as long as they are required. Please clean-up any snapshots regularly.
  • 3rd party managed services (e.g. Github, CircleCI, - These 3rd party managed services will offer some form of back-up and recovery as part of their managed service, however these processes are out of the scope of recovery by the Modernisation Platform. If you need more information please contact #ask-operations-engineering.
  • Ensure your owner tag is kept up to date so that the Modernisation Platform Team knows how best to contact your team.
  • Ensure your team is added to the #modernisation-platform-update slack channel so that you can ensure you receive important messages from the Modernisation Platform Team.

Backups and restores

Backup information can be found on our backup page. Restores to backed up snapshots are the responsibility of the application teams.

How will we know if there is a Disaster in progress?

If there is a wider issue with the platform we will notify all users via #modernisation-platform-update channel in line with our operational processes. You should check #modernisation-platform-update for periodic status updates.

If we identify a specific issue relating to a single service we will contact the team via the owner tag detailed in your application tags.

How do I access these services if we have a problem or if we have any questions?

Please contact us over at #ask-modernisation-platform slack channel.

How will we deal with an incident?

See here our general incident runbook

This page was last reviewed on 27 September 2023. It needs to be reviewed again on 27 March 2024 by the page owner #modernisation-platform .
This page was set to be reviewed before 27 March 2024 by the page owner #modernisation-platform. This might mean the content is out of date.