You can deploy Horizon 7 on VMware Cloud on AWS for the following scenarios.

Data Center Expansion and Bursting

Use this scenario if you have an existing on-premises Horizon 7 infrastructure and need to expand capacity but don't want to procure additional hardware. By extending the Horizon 7 deployment to VMware Cloud on AWS, you can use cloud capacity and still manage on-premises and private cloud deployments in a single federated space. You can also utilize the cloud platform to provide temporary capacity for contractors and seasonal workers. The on-premises deployment is optional. Based on your needs, you can decide to consolidate and move the on-premises deployment completely to VMware Cloud on AWS.

Application locality

Use this scenario when you want to move published applications that are latency-sensitive to VMware Cloud on AWS and need virtual desktops and RDS hosts to be co-located with your published applications. You can also have other published applications that are still on-premises. When you extend your Horizon 7 deployment to VMware Cloud on AWS you can allow end-users to connect to the nearest virtual desktop or RDS host to launch the application regardless of whether the application is on premises or on VMware Cloud on AWS.

Disaster Recovery (DR) and business continuity

Use this scenario if you want to build DR infrastructure. The cost of building an on-premises DR infrastructure can be expensive. When you use VMware Cloud on AWS, you pay for the use of DR infrastructure during those times when the primary infrastructure is down or when you require a small pilot during normal operations for a quick Recovery Time Objective (RTO) during a disaster event. Having a unified Horizon 7 architecture across the primary site on premises and the DR site on VMware Cloud on AWS makes the failover process simple. In addition, when you use the Cloud Pod Architecture feature to deploy Horizon 7 across multiple VMware Cloud on AWS instances, there is high availability across multiple cloud nodes.