AWS backup and recovery

While varying degrees of resilience can be architected within AWS, AWS does not keep backups of your data. Per the AWS Shared Responsibility Model, it is the responsibility of the consumer to ensure their data is secured and protected, whether it is Infrastructure as a Service (IaaS), Platform as a Service (PaaS) or Software as a Service (SaaS). Just like on-premises, your applications and data need to be protected to overcome any kind of data loss such as accidental deletion, cybersecurity threats, ransomware, outages and more. Veeam provides easy-to-use, cost-effective and secure AWS backup and recovery to protect you from any cloud data loss.

1. Create AWS-native snapshots of your Amazon EC2 instances. While this can be done manually or with homegrown scripts, the best method is to leverage a third-party solution that can automate point-in-time snapshots based on policies. This ensures ease-of-use, scalability and visibility into what is and isn’t protected in your environment while also enabling automated lifecycle management to reduce the complexity of snapshots.
2. Create image-level backups. While native snapshots are great for delivering low recovery time objectives (RTOs) and recovery point objectives (RPOs), they represent a single point of failure in a data protection strategy and can become very costly. In addition to this snapshot, you should create image-level backups that capture the whole image of the Amazon EC2 instance at a specific point in time. The backup should then be offloaded into an Amazon S3 repository to dramatically reduce storage costs and enable compliance for long-term data retention.
3. Replicate snapshots. You can choose to replicate your snapshots and store them in any other AWS region within any AWS account. This is useful for disaster recovery (DR) scenarios if one AWS region were to fail, as well as migration situations.

1. Create AWS-native snapshots of your Amazon RDS instances. While this can be done manually or through homegrown scripts, the best method is to use a third-party solution that can automate these point-in-time snapshots based on policy. This ensures ease-of-use, scalability and visibility into what is and isn’t protected in your environment while enabling automated lifecycle management to reduce the complexity of snapshots.
2. Replicate snapshots. You can choose to replicate your snapshots and store them in any other AWS region within any AWS account. This is useful for DR scenarios if one AWS region were to fail, as well as migration situations.

Amazon VPC data can become incredibly complex and are crucial components of any AWS environment. It is critical to back up Amazon VPCs in order to troubleshoot configuration errors and perform DR as well as perform testing and cloning. You should be protecting all Amazon VPC data, including but not limited to subnet, NAT gateway, elastic IP, security group, VPN connection and more.