Step 3: Locate Migration Assistant and the migration role

Open a shell on the Migration Console pod, refreshing your kubeconfig first if you are on a new shell:

aws eks update-kubeconfig --region <REGION> --name migration-eks-cluster-<STAGE>-<REGION>
kubectl exec -it migration-console-0 -n ma -- /bin/bash

Confirm the installed schema version, because the workflow configuration can change by release:

console --version

The migration’s write identity is the IAM role <eks-cluster-name>-migrations-role, which you already added as the principal in the data access policy in Create the data access policy. From the Migration Console pod, confirm pod identity is delivering credentials:

aws sts get-caller-identity