AWS mediatailor documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in titles, section headers, and troubleshooting content
Security assessment
Terminology standardization without altering troubleshooting steps or security recommendations. IAM permission guidance remains identical.
Diff
diff --git a/mediatailor/latest/ug/troubleshoot-deployment-issues.md b/mediatailor/latest/ug/troubleshoot-deployment-issues.md index bcf586579..99feaaa21 100644 --- a//mediatailor/latest/ug/troubleshoot-deployment-issues.md +++ b//mediatailor/latest/ug/troubleshoot-deployment-issues.md @@ -5 +5 @@ -AWS CloudFormation deployment issuesPlayback and ad insertion issues +CloudFormation deployment issuesPlayback and ad insertion issues @@ -7 +7 @@ AWS CloudFormation deployment issuesPlayback and ad insertion issues -# Troubleshoot common AWS CloudFormation deployment issues for CDN and MediaTailor integrations +# Troubleshoot common CloudFormation deployment issues for CDN and MediaTailor integrations @@ -11 +11 @@ AWS Elemental MediaTailor deployment issues can occur even with automation durin -If you encounter issues with your AWS CloudFormation deployment or the resulting MediaTailor and CloudFront integration, refer to these common problems and solutions: +If you encounter issues with your CloudFormation deployment or the resulting MediaTailor and CloudFront integration, refer to these common problems and solutions: @@ -13 +13 @@ If you encounter issues with your AWS CloudFormation deployment or the resulting -## AWS CloudFormation deployment issues +## CloudFormation deployment issues @@ -27 +27 @@ Stack creation fails with "Resource creation failed" error -**Solution:** Check the specific resource error in the AWS CloudFormation events tab. Verify that the content origin domain name is correctly formatted without protocol prefixes or paths. Ensure your IAM role has sufficient permissions to create all required resources. +**Solution:** Check the specific resource error in the CloudFormation events tab. Verify that the content origin domain name is correctly formatted without protocol prefixes or paths. Ensure your IAM role has sufficient permissions to create all required resources.