Clean up a Self-deployed environment
When you no longer need your Amazon Elastic VMware Service environment, delete its connectors, hosts, and the environment itself, to stop the charges for the hosts. You can use the Amazon EVS console or the AWS CLI. Then delete the network resources that you created outside of Amazon EVS.
Deleting the hosts and the environment deletes the VMware Cloud Foundation (VCF) installation that runs in the environment. You can’t undo this action. Back up or migrate any workloads that you want to keep before you start.
Delete the connectors
Delete all connectors of the environment. For instructions, see Delete a connector.
Delete the hosts and the environment
Delete all hosts before you delete the environment, because you can’t delete an environment that still has hosts. To delete the hosts and the environment in the Amazon EVS console or with the AWS CLI, use the following steps.
Example
Environment deletion also deletes the Amazon EVS VLAN subnets and the AWS Secrets Manager secrets that Amazon EVS created. It doesn’t delete the VPC, the route server, or other AWS resources that you created outside of Amazon EVS. These resources can continue to incur costs.
To remove a single host from a running cluster instead, see Delete a host (VCF 9.x).
Delete the remaining resources
To delete the remaining resources, do the following.
-
If you have Amazon EC2 Capacity Reservations that you no longer need, cancel them. For more information, see Cancel a Capacity Reservation in the Amazon EC2 User Guide.
-
If you used diskless hosts, delete your external storage, such as the file system and its volumes, to stop accruing storage charges. Deleting the environment doesn’t delete external storage.
-
Delete the network resources, such as the route server, the network ACL, the route tables, the subnets, and the VPC. For instructions, see Clean up network resources.
You have cleaned up the environment.