Traffic Capture Verification

Assumptions

• Traffic Capture Proxy deployed in ECS (not within cluster nodes)
• Migration Console deployed

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. (Reset) Update Traffic Capture Proxy service desired count back to original value in ECS

Limitations

• If source cluster requires auth, will not be able to verify beyond receiving 401/403 status code for ALB healthchecks

Troubleshooting

• Verify Source Cluster allows traffic ingress from Capture Proxy Security Group
• Navigate to Traffic Capture Proxy ECS Tasks to investigate failing 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

How to Contribute

Cut a GitHub issue referencing page and assigning to

owner: @AndreKurait