

# Deploy the solution
<a name="deploy-the-solution"></a>

This solution provides two deployment options: ECS-based deployment and EKS-based deployment. Choose the option that best fits your migration requirements.

Before you begin, review the [cost](cost.md), [architecture](architecture-overview.md), [network security](security-1.md), and other considerations discussed earlier in this guide.

**Important**  
To update to a newer version of this solution, [uninstall](uninstall-the-solution.md) and redeploy it. This solution isn’t backwards-compatible.

**Important**  
This solution sends operational metrics to AWS. We use this data to better understand how customers use this solution and related services and products. AWS owns the data gathered though this survey. Data collection is subject to the [Privacy Notice](https://aws.amazon.com/privacy/).

## Deployment options
<a name="deployment-options"></a>

### EKS deployment (recommended)
<a name="eks-deployment"></a>

The EKS-based deployment is the recommended deployment option for Migration Assistant 3.0. It leverages Amazon Elastic Kubernetes Service (Amazon EKS) to provide a simplified workflow experience with faster configuration changes and built-in orchestration.

#### Launch the CloudFormation stack
<a name="launch-the-cloudformation-stack"></a>

Choose one of the following options to deploy the EKS infrastructure:
+  [Launch with a new VPC](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?templateURL=https://solutions-reference.s3.amazonaws.com/migration-assistant-for-amazon-opensearch-service/latest/migration-assistant-for-amazon-opensearch-service-create-vpc-eks.template) — Creates a new VPC with all required networking.
+  [Launch into an existing VPC](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?templateURL=https://solutions-reference.s3.amazonaws.com/migration-assistant-for-amazon-opensearch-service/latest/migration-assistant-for-amazon-opensearch-service-import-vpc-eks.template&redirectId) — Uses an existing VPC (requires proper subnet and security group configuration).

After the CloudFormation stack deploys, run the bootstrap script to install the Helm chart and configure the EKS cluster. For detailed instructions, see [Deploying to EKS on GitHub](https://github.com/opensearch-project/opensearch-migrations/wiki/Deploying-to-EKS).

The deployment guide provides detailed instructions for:
+ Prerequisites and environment setup
+ CloudFormation-based infrastructure deployment (new VPC or existing VPC)
+ Helm chart installation and configuration
+ Migration execution using the Workflow CLI
+ Monitoring and troubleshooting

For the complete Migration Assistant documentation, see [Migration Assistant for OpenSearch](https://docs.opensearch.org/latest/migration-assistant/).

### ECS deployment (support only)
<a name="ecs-deployment"></a>

**Important**  
The ECS-based deployment is in support-only mode and will reach end of support on **July 15, 2026**. No new features will be developed for the ECS deployment. New deployments should use the EKS deployment option.

The ECS-based deployment has been available since Migration Assistant 1.0. Existing ECS deployments will continue to function, but customers are encouraged to migrate to the EKS deployment for access to new features and ongoing support.

For ECS deployment documentation, see [Migration Assistant (Classic)](https://docs.opensearch.org/classic/migration-assistant/).