Fluid Attacks policy on continuity and recovery | Fluid Attacks

Continuity and Recovery

We deploy our infrastructure everyday due to these key concepts:

  1. Everything as Code
  2. Regenerative Infrastructure

This approach has many benefits in terms of business continuity and disaster recovery. By adopting Infrastructure as a Code, and based on AWS, Terraform and GitLab CI features, we can:

  1. Destroy and deploy infrastructure quickly. We re-deploy the infrastructure constantly because autoscaling is done daily, based on usage. In such infrastructure environment, is expected that a server could not exist for more than 24 hours. This is the reason why we regenerate our infrastructure on a daily basis with an automated process while autoscaling.

Information on production branch of the Fluid Attacks platform

Autoscaling of the Fluid Attacks platform reference

  1. Monitor and review all the code in search for bugs or any other type of errors.
  2. Hack continuously our own code, infrastructure included.

Additionally, we have an extensive backup strategy and well defined recovery objectives.