Should you have a backup & DR strategy once you’re in the AWS cloud?

In short, yes…

AWS has a shared responsibility model, which means you are responsible for what you run on AWS. This means the following risks can still be present.

  • Human error, people can still delete things they shouldn’t. In this case what’s your Recovery Point Objective (RPO) and Recovery Time Objective (RTO) needs?
  • Malicious attacks, Security is your responsibility remember. What’s your strategy to ensure a least privileged model? Do you have a security policy and Chief Information Security Officer (CISO) to manage this?
  • Compromised AWS accounts, who has access they shouldn’t? Have people and services got the right level of access to the AWS console? Could anyone compromise your business that relies on the AWS services.
  • AWS services outages, are you leveraging all available Availability Zones (AZ’s)? Have you got your services running across all available AZ’s for high availability (HA)?
  • AWS regional outages, could happen so are your systems fault tolerant (FT)? Do you need to set up cross region replication? Also, if an AWS region is lost can you quickly re-deploy your Virtual Private Cloud (VPC) settings in a new region?

So, you can see that even in the cloud you’ll never be free from potential disasters. Sometimes things go wrong, in & outside of your control, and when they do have you got these risks covered?

AWS has many tools you can switch on to cover these risks, but you need the skills to manage them. Additionally, you should look at automating much of the process to cut down further risk of human error.

By partnering with Duolc plus the leading AWS cloud backup software provider, Veeam. We can put a managed plan in place that automates your backup & DR in the cloud. You can then focus on business growth, knowing your data is secure and available.

Talk to us about our Well Architected Framework and earn $5000 back in credits from AWS!

More info here.

Close Bitnami banner