Link Search Menu Expand Document Documentation Menu
Documentation

Removing migration infrastructure

Do not remove migration infrastructure immediately after a successful migration.

Before proceeding with removal, confirm the following:

  • Production traffic has been stable on the target.
  • You no longer need the source for rollback.
  • You no longer need replay or comparison checks.
  • Any snapshot artifacts you want to keep have been retained intentionally.

Other Kubernetes removal

To remove the Helm deployment and persistent volumes, run the following commands:

helm uninstall -n ma ma
kubectl -n ma delete pvc --all
kubectl delete namespace ma

Amazon EKS removal

If you used the EKS bootstrap path, remove the Helm release and then the CloudFormation stack:

helm uninstall -n ma ma
kubectl -n ma delete pvc --all
aws cloudformation delete-stack --stack-name <STACK_NAME>
aws cloudformation wait stack-delete-complete --stack-name <STACK_NAME>

This removes the EKS platform resources created by the solution stack.

Google Kubernetes Engine (GKE) removal

If you used the GKE Terraform path, uninstall the Helm release and then destroy the Terraform-managed infrastructure:

helm uninstall migration-assistant -n ma
kubectl -n ma delete pvc --all
terraform destroy \
  -var="project=<your-gcp-project>" \
  -var="region=<your-gcp-region>"

This removes the GKE cluster, networking, and snapshot resources that Terraform created.

Snapshot and artifact retention

Be deliberate about removing the snapshot bucket in object storage, such as Amazon S3 or Google Cloud Storage. The default migrations bucket is often still useful for:

  • Audit and rollback investigation
  • Preserving snapshots
  • Comparing post-cutover behavior

Delete the bucket only after you are certain you no longer need its contents.

Previous phase

The previous phase depends on your migration scenario:

350 characters left

Have a question? .

Want to contribute? or .