-
Notifications
You must be signed in to change notification settings - Fork 30
Accessing the Migration Console
The Migrations Assistant deployment includes an ECS task that hosts tools to run different phases of the migration and to check on progress/results of the migration.
Following the AWS solutions deployment the bootstrap box contains a script that makes it easier to access the migration console through that instance.
TODO: It is not clear how a user can get to accessContainer.sh. Please specify.
export STAGE=dev
export AWS_REGION=us-west-2
./deployment/cdk/opensearch-service-migration/accessContainer.sh migration-console ${STAGE} ${AWS_REGION}
Typically, STAGE is dev
, but may differ depending on what the user specified at deployment.
On a machine with the AWS CLI and the AWS Session Manager Plugin you can directly connect to the migration console. Note: you'll need to run aws configure
with credentials that have access to the environment.
export STAGE=dev
export SERVICE_NAME=migration-console
export TASK_ARN=$(aws ecs list-tasks --cluster migration-${STAGE}-ecs-cluster --family "migration-${STAGE}-${SERVICE_NAME}" | jq --raw-output '.taskArns[0]')
aws ecs execute-command --cluster "migration-${STAGE}-ecs-cluster" --task "${TASK_ARN}" --container "${SERVICE_NAME}" --interactive --command "/bin/bash"
TODO: Add steps to validate a user is on the migration console.
TODO: Add documentation on creating a github issue
owner: @mikaylathompson
Encountering a compatibility issue or missing feature?
- Search existing issues to see if it’s already reported. If it is, feel free to upvote and comment.
- Can’t find it? Create a new issue to let us know.
- Migration Assistant Overview
- Is Migration Assistant Right for You?
- Existing Data Migration - Quick Start Guide
- A. Snapshot Creation Verification
- B. Client Traffic Switchover Verification
- C. Traffic Capture Verification
- D. System Reset Before Migration