Skip to content

Switching Traffic from Source to Target

Andre Kurait edited this page Aug 7, 2024 · 7 revisions

Assumptions

  • All client traffic is being routed through switchover listener in MigrationAssistant ALB
  • Client traffic has been verified to be compatible with Target Cluster
  • Target cluster is in a good state to accept client traffic (i.e. backfill/replay is complete as needed)
  • Target Proxy Service is deployed

Steps

  1. Within the AWS Console, navigate to ECS > Migration Assistant Cluster
  2. Note down the desired count of the Capture Proxy (it should be > 1)
  3. Update the ECS Service of the Target Proxy to be at least as large as the Traffic Capture Proxy
  4. Wait for tasks to startup, verify all targets healthy within Target Proxy Service "Load balancer health"
  5. Within the AWS Console, navigate to EC2 > Load Balancers > Migration Assistant ALB
  6. Navigate to the Capture Proxy Target Group (ALBSourceProxy--TG) > Monitoring
  7. Examine Metrics Requests, Target (2XX, 3XX, 4XX, 5XX), and Target Response Time, Metrics
    1. Verify that this looks as expected and includes all traffic expected to be included in the switchover
    2. Note details that would help identify anomalies during the switchover including expected response time and response code rate.
  8. Navigate back to ALB and click on Target Proxy Target Group (ALBTargetProxy--TG)
  9. Verify all expected targets are healthy and none are in draining state
  10. Navigate back to ALB and to the Listener on port 9200
  11. Click on the Default rule and Edit
  12. Modify the weights of the targets to shift desired traffic over to the target proxy
    1. To perform a full switchover, modify the weight to 1 on Target Proxy and 0 on Source Proxy
  13. Click Save Changes
  14. Navigate to both SourceProxy and TargetProxy TG Monitoring metrics and verify traffic is shifting over as expected

Troubleshooting

Related Links

How to Contribute

owner: @AndreKurait

Clone this wiki locally