Case study on Lambda tracing with Amazon X-Ray

The software engineering team just started using Lambda functions. For them, it is exciting to be able to deploy applications easier, due to the automated pipeline you have created for them using Amazon CodePipeline. So, deployments are smooth and fast. They also have access to the logs of the application in the CloudWatch console, so they can view the logs of each Lambda function. But they notice that data does not move from one function to the other. A particular Lambda function is supposed to call another Lambda function in succession, about six of them call each other in that manner. What service and feature will you use to show the path of the request from the first Lambda function to the last function?

Solution

It is obvious that the challenge they are facing is the inability to trace a request from one Lambda function to another. The service that can help with this is AWS X-Ray. The features in X-Ray are both service maps...