Suggestion: Guide on managing XRay as a separate service

I stumbled on issues #24 and #53 while Googling to help me do the same tasks. I was still a little unclear on the process surrounding setting up ECS as a separate service and have other microservices interact with it. So, a setup design guide along the same lines would be incredibly helpful in adoption as it's a relatively new but exciting feature. Feel free to close the issue if it seems irrelevant.

Read issues #24 and #53 first, then examine the existing AWS X-Ray daemon and ECS setup guidance to identify the missing separate-service workflow. Document how ECS can run X-Ray independently and how other microservices interact with it; done means a clear setup design guide that supports adoption.

Written by the indexing model from the issue text.