(Robert Wheeler has been working as a DevSecOps engineer in an IT company for the past 5 years. His organization develops software products and web…

Rapid7 tCell integrates with AWS CloudFront by using Lambda@Edge. This AWS service allows code (a Lambda function) to run at AWS edge locations, closer to the end-user. This function intercepts viewer requests and responses as they pass through the CloudFront distribution. The tCell agent, packaged as a Lambda@Edge function and deployed via a CloudFormation stack, can inspect traffic, apply security policies, and protect the application at the edge, before malicious traffic reaches the origin server. This is the standard and officially supported method for this type of integration.

A. A standard Lambda function runs in a specific region and is not suitable for inspecting traffic at all global CloudFront edge locations.

B. Plugging into CloudFormation is nonsensical. CloudFormation is an Infrastructure as Code (IaC) service used for deployment, not a runtime environment to plug into.

D. This option incorrectly states plugging into CloudFormation. While Lambda@Edge is the correct technology, it integrates with CloudFront, not CloudFormation.

- Rapid7. (2023). AWS CloudFront with Lambda@Edge. tCell Documentation. Retrieved from https://docs.tcell.io/docs/aws-cloudfront-with-lambdaedge. (This official vendor documentation explicitly states, "The tCell agent can be plugged into CloudFront through Lambda@Edge.")

- Amazon Web Services. (2023). What Is Lambda@Edge?. Amazon CloudFront Developer Guide. Retrieved from https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-at-the-edge.html. (This official AWS documentation describes how Lambda@Edge works to customize content delivered through CloudFront, which is the mechanism used by tools like tCell.)