AWS xray documentation change
Summary
Changed 'AWS CloudFormation template' to 'CloudFormation template' in documentation about IAM permissions for X-Ray tracing
Security assessment
The change appears to be a minor terminology update (removing 'AWS' prefix from CloudFormation) rather than addressing security concerns. While the context mentions IAM policies for permissions, this is existing guidance and not a new security-related addition.
Diff
diff --git a/xray/latest/devguide/xray-services-stepfunctions.md b/xray/latest/devguide/xray-services-stepfunctions.md index f36ed9d43..2bb769eb4 100644 --- a//xray/latest/devguide/xray-services-stepfunctions.md +++ b//xray/latest/devguide/xray-services-stepfunctions.md @@ -45 +45 @@ AWS X-Ray integrates with AWS Step Functions to trace and analyze requests for S -When you create a new state machine, it's automatically traced if the request is sampled and tracing is enabled in an upstream service such as Amazon API Gateway or AWS Lambda. For any existing state machine not configured through the console, for example through an AWS CloudFormation template, check that you have an IAM policy that grants sufficient permissions to enable X-Ray traces. +When you create a new state machine, it's automatically traced if the request is sampled and tracing is enabled in an upstream service such as Amazon API Gateway or AWS Lambda. For any existing state machine not configured through the console, for example through an CloudFormation template, check that you have an IAM policy that grants sufficient permissions to enable X-Ray traces.