How to Back Up VMware VMs to AWS: S3, EC2, and AWS Backup

3 Methods to Back Up VMware to AWS

When a local server fails or a data center goes down, recovering quickly depends on having your VMware VMs backed up to AWS before disaster strikes.

This guide covers 3 ways to back up VMware to AWS. The first two keep your on-premises environment in place while protecting data in the cloud. The third moves your VMs to run directly on AWS.

• AWS Backup: Back up on-premises VMware VMs using native AWS tooling, with no changes to your existing environment
• Amazon S3: Store VM backups in S3 for flexible, cost-effective cloud storage and long-term archiving
• AWS EC2 Migration: Move VMs to run on EC2, suited for data center transitions or disaster recovery (DR) failover

Method 1: Back Up On-Premises VMware Using AWS Backup

AWS Backup provides a centralized service to back up VMware VMs to AWS without changing your on-premises setup. It works with VMs managed by vCenter 6.7, 7.0, or 8.0.

This method suits teams already using AWS services and looking for a native, policy-driven backup solution.

Prerequisites

Before you begin, confirm the following:

• An AWS account with appropriate IAM permissions
• Outbound internet access from the gateway host to AWS endpoints
• vCenter credentials with permission to create snapshots and read disk data
• Sufficient local storage for the gateway’s cache

Step-by-Step Configuration

1. Deploy the AWS Backup gateway on-premises

• Download the gateway as an OVA template from the AWS Backup console
• Deploy it using the vSphere Client and assign a static IP address
• Confirm the gateway can reach AWS endpoints

2. Activate the gateway

• In the AWS console, go to AWS Backup > External resources > Gateways
• Enter the gateway’s IP address to activate it

3. Connect the gateway to vCenter

• Select Connect to hypervisor
• Enter your vCenter hostname and credentials

4. Create a backup plan and assign resources

• Go to Backup plans > Create backup plan
• Set your schedule and retention period
• Use Assign resources to select specific VMs, or apply resource tags to include them automatically

5. Monitor backup jobs

• Check the Jobs dashboard to track backup status
• For failed or slow jobs, review logs in Amazon CloudWatch

 

Limitations

• AWS Backup for VMware relies on Changed Block Tracking (CBT). If CBT is disabled or reset, the next job runs as a full backup, increasing transfer time and storage usage
• File-level recovery is not supported; you need to restore the full virtual disk or VM

Method 2: Back Up VMware VMs to Amazon S3

Amazon S3 is a widely used storage target for VMware backups. It works as a scalable, off-site repository — useful for long-term archiving and protecting against local hardware failure or ransomware attacks.

Why VMware Backup to Amazon S3

S3 offers virtually unlimited capacity and high durability, with no need to manage physical tapes or maintain a secondary data center. Different storage tiers let you balance cost against how quickly you need to retrieve data.

Step-by-Step Configuration

1. Export or capture VM data using a backup tool
   • Use a backup solution that supports image-level VM capture with deduplication and compression — this reduces the volume of data sent over the internet
   • Choose a tool that supports incremental backups after the first full backup, so only changed data blocks are uploaded each time
2. Configure S3 as the backup destination
   • Create an S3 bucket in your preferred AWS region
   • In your backup software, configure the S3 bucket as the target destination
   • For authentication, use an IAM role where possible — if using access keys, ensure the associated IAM user has at minimum s3:PutObject and s3:ListBucket permissions
3. Set retention and lifecycle policies
   • In the S3 Management Console, go to your bucket’s Management tab
   • Create Lifecycle rules to automatically move older backups to cheaper storage tiers, such as S3 Glacier or S3 Glacier Deep Archive
   • Set expiration rules to delete backups that exceed your retention period

 

Key Considerations

• Storage costs: S3 charges for PUT requests and data retrieval, not just storage. Monitor usage regularly to avoid unexpected costs
• Transfer speed: Uploading large VMs can saturate your internet connection. For more consistent throughput, consider AWS Direct Connect or AWS Storage Gateway
• Encryption: Enable Server-Side Encryption (SSE) on your S3 bucket to protect data at rest. Also confirm your backup tool encrypts data in transit before it reaches AWS

Method 3: Migrate VMware VMs to AWS EC2

This approach differs from backup. Instead of storing a copy of your data, you move the workload to run directly on Amazon EC2. Once complete, the VM no longer runs in your local environment.

Use this method when you want to permanently shift workloads to AWS, not just protect them.

When to Use This Approach

• Data center consolidation: Reducing on-premises hardware and moving workloads to the cloud permanently
• Platform transition: Shifting to a cloud-native infrastructure as part of a longer-term strategy
• DR failover: Using AWS as a hot or warm standby site that can take over production during an emergency

Step-by-Step Migration Process

1. Assess VM compatibility
   • Check the AWS Application Migration Service (MGN) documentation to confirm your OS version and kernel are supported
   • Note any legacy software or configurations that may not be compatible with the AWS Nitro environment
2. Prepare the VM for migration
   • Ensure the VM is configured for DHCP so it can receive a new IP address when launched in AWS
   • Remove any on-premises-specific configurations that may conflict with AWS networking
3. Replicate or import to EC2
   • Use AWS MGN for continuous, block-level replication — this is the recommended approach for live workloads as it minimizes downtime
   • Alternatively, use VM Import/Export to upload an OVA or VMDK file to an S3 bucket for conversion — better suited for offline or test migrations
4. Validate and launch on EC2
   • Launch a test instance before cutting over production traffic
   • Verify the application starts correctly and that security groups allow the required traffic
   • Confirm network connectivity and check for any driver issues in the AWS Nitro environment

 

Key Considerations

• Driver compatibility: Some VMs may need driver adjustments to boot correctly in the AWS Nitro environment; AWS MGN handles most of this automatically
• Licensing: License requirements for certain operating systems or enterprise software may change when moving from on-premises to the cloud; verify this before migrating

How i2Backup Supports VMware Backup to AWS

The methods above work well for straightforward scenarios, but managing VMware backups to AWS at scale introduces new challenges — consistent scheduling, encryption compliance, storage cost control, and centralized visibility across multiple VMs.

This is where a dedicated backup solution like i2Backup adds value. It handles VMware-to-AWS backup through a single platform, reducing the operational overhead of managing each component separately.

Key Features of i2Backup

• Agentless VM Backup: i2Backup uses native virtualization platform APIs to back up VMware VMs without installing agents on each machine. This means zero impact on production workloads during backup jobs. It supports all mainstream virtualization platforms including VMware and Hyper-V.
• Backup VMware to S3: i2Backup supports Amazon S3 as a backup destination, allowing you to store VM backups directly in the cloud. It also supports other storage targets including local disks, NAS, tape libraries, and object storage — giving you flexibility over where backups land.
• Backup for AWS EC2 and Cloud Workloads: i2Backup also extends protection to your AWS environment. It supports backup and recovery for AWS EC2 instances, with the same enterprise-level security and management capabilities applied to your on-premises VMware environment.
• Block-Level Change Tracking: i2Backup uses block-level change tracking to capture only modified data after the initial full backup. This enables near real-time backup with minute-level RPO, while reducing transfer volume and storage costs, particularly important when backing up to cloud destinations like AWS S3.
• Flexible Scheduling and Automated Workflows: Backup schedules can be configured by hour, day, week, or month. Once set, jobs run automatically with no manual intervention. Outdated backups are removed based on your retention rules, keeping storage usage under control.

For teams backing up VMware workloads to AWS, i2Backup consolidates what would otherwise be a fragmented set of tools into a single, manageable platform — with encryption, automation, and multi-destination support built in.

Best Practices for VMware Backup to AWS

Following these practices helps ensure your backups are recoverable and your AWS costs stay predictable.

1. Use incremental backups after the initial full backup

Only transfer changed data blocks on subsequent jobs. This reduces network usage, shortens backup windows, and lowers monthly storage costs significantly

2. Encrypt data in transit and at rest

Use SSL/TLS for data transfers and enable AES-256 or AWS KMS encryption for stored backup images. Confirm your backup tool encrypts data before it leaves your environment, not just after it arrives in AWS

3. Automate schedules and set up failure alerts

Manual backups are prone to being skipped or delayed. Configure automated schedules and enable email or SMS notifications so you know immediately when a job fails

4. Test restores regularly, not just backups

A completed backup job does not guarantee a successful restore. Run periodic restore drills to verify VMs boot correctly and that you can meet your Recovery Time Objective (RTO) when it matters

5. Use S3 lifecycle policies to manage storage costs

Move older backups to S3 Glacier or S3 Glacier Deep Archive automatically once they pass a set age. This keeps long-term retention affordable without manual cleanup

Conclusion

Backing up VMware workloads to AWS is not a one-size-fits-all process. The right approach depends on what you are trying to achieve.

• AWS Backup suits teams already in the AWS ecosystem who want native, policy-driven protection for on-premises VMware VMs
• Amazon S3 works well as a flexible, cost-effective destination for long-term VM backup and archiving
• AWS EC2 migration is the right choice when the goal is to move workloads permanently to the cloud, not just protect them

Whichever method you choose, the fundamentals remain the same: use incremental backups to control costs, encrypt data in transit and at rest, automate your schedules, and test restores regularly — not just backup completion.

For teams managing VMware and AWS workloads at scale, i2Backup by Info2Soft brings these elements together in a single platform, with agentless VM backup, S3 and EC2 support, and centralized management across your entire environment.