Traffic Capture Verification

This guide will describe how once the traffic capture proxy is deployed the captured traffic can be verified.

Replication setup and validation

1. Navigate to Migration ECS Cluster in AWS Console
2. Navigate to Capture Proxy Service
3. Verify > 0 desired count and running
   • if not, update service to increase to at least 1 and wait for startup
4. Within "Load balancer health" on "Health and Metrics" tab, verify all targets are reporting healthy
   • This means the ALB is able to connect to the source cluster through the capture proxy
5. Navigate to the Migration Console Terminal
6. Execute console kafka describe-topic-records
7. Wait 30 seconds for another elb health check to be recorded
8. Execute console kafka describe-topic-records again, Verify RECORDS increased between runs
9. Execute console replay start to start the replayer
10. Run tail -f /shared-logs-output/traffic-replayer-default/*/tuples/tuples.log | jq '.targetResponses[]."Status-Code"' to confirm that the Kafka requests were sent to the the target and that it responded as expected... If responses don't appear
    • check that the migration-console can access the target cluster by running ./catIndices.sh, which should show indices on the source and target.
    • confirm that messages are still being recorded to Kafka.
    • check for errors in the replayer logs ("/migration/STAGE/default/traffic-replayer-default") via CloudWatch
11. (Reset) Update Traffic Capture Proxy service desired count back to original value in ECS

Troubleshooting

Health checks response with 401/403 status code

If the source cluster is configured to require authentication the capture proxy will not be able to verify beyond receiving 401/403 status code for ALB healthchecks

Traffic does not reach the source cluster

Verify the Source Cluster allows traffic ingress from Capture Proxy Security Group.

Look for failing tasks by navigating to Traffic Capture Proxy ECS Tasks. Change "Filter desired status" to "Any desired status" in order to see all tasks and navigate to logs for stopped tasks.

Related Links

• Traffic Capture Proxy Failure Modes