Add TCX5 waiver to inline policies to pass deny list check.

cr: https://code.amazon.com/reviews/CR-224753718

Author: Laren-AWS

v2/guide/attributes.txt

@@ -2,3 +2,6 @@
 :arn-aws: pass:q[[.shared]``region.arn``]
 :aws: pass:q[[.shared]``AWS``]
 :aws-management-console: pass:q[[.shared]``consolelong``]
+
+:tcx5-2025-waiver: pass:[		 	 	 ]
+

v2/guide/best-practices-security.adoc

@@ -6,7 +6,6 @@ include::attributes.txt[]
 [[best-practices-security,best-practices-security.title]]
 = {aws} CDK security best practices
 :info_titleabbrev: Security
-:tcx5-2025-waiver: 		 	 	 
 :keywords: {aws} CDK, IAM, security, permissions, infrastructure, {aws} CloudFormation, {aws} CDK deployments
 
 [abstract]
@@ -131,4 +130,4 @@ If you want to work around this feature by replacing the automatically generated
 * A common workaround to using wildcards is to mandate that all resources be given a predictable name. However, this interferes with CloudFormation`'s ability to replace resources when necessary and may slow down or block development. Because of this, we recommend that you allow CloudFormation to create unique resource names for you.
 * It will be impossible to perform continuous delivery since manual actions must be performed prior to every deployment.
 
-When organizations want to prevent the CDK from creating roles, it is usually to prevent developers from being able to create IAM roles. The concern is that by giving developers permission to create IAM roles using the {aws} CDK, they could possibly elevate their own privileges. To mitigate against this, we recommend using  _permission boundaries_ or _service control policies (SCPs)_. With permission boundaries, you can set limits for what developers and the CDK are allowed to do. For more information on using permission boundaries with the CDK, see xref:customize-permissions-boundaries[Create and apply permissions boundaries for the {aws} CDK].
+When organizations want to prevent the CDK from creating roles, it is usually to prevent developers from being able to create IAM roles. The concern is that by giving developers permission to create IAM roles using the {aws} CDK, they could possibly elevate their own privileges. To mitigate against this, we recommend using  _permission boundaries_ or _service control policies (SCPs)_. With permission boundaries, you can set limits for what developers and the CDK are allowed to do. For more information on using permission boundaries with the CDK, see xref:customize-permissions-boundaries[Create and apply permissions boundaries for the {aws} CDK].

v2/guide/bootstrapping-env.adoc

@@ -5,7 +5,6 @@ include::attributes.txt[]
 [#bootstrapping-env]
 = Bootstrap your environment for use with the {aws} CDK
 :info_titleabbrev: Bootstrap your environment
-:tcx5-2025-waiver: 		 	 	 
 :keywords: {aws} CDK, {aws} Cloud Development Kit ({aws} CDK), {aws} account, {aws} Region, Bootstrapping, Bootstrap, Environment
 
 [abstract]

v2/guide/hello-world.adoc

@@ -8,7 +8,6 @@ include::attributes.txt[]
 :info_abstract: Get started with the {aws} Cloud Development Kit ({aws} CDK) by using the {aws} CDK Command Line Interface ({aws} CDK CLI) to develop your first \
 				CDK app, bootstrap your {aws} environment, and deploy your application on {aws}.
 :keywords: {aws} CDK, {aws} Cloud Development Kit ({aws} CDK), CDK app, {aws}, {aws} CloudFormation, Infrastructure as code, IaC
-:tcx5-2025-waiver: 		 	 	 
 
 [abstract]
 --
@@ -1663,4 +1662,4 @@ For additional resources, see the following:
 * Visit https://constructs.dev/search?q=&cdk=aws-cdk&cdkver=2&sort=downloadsDesc&offset=0[Construct Hub] to discover constructs created by {aws} and others.
 * Explore https://github.com/aws-samples/aws-cdk-examples[Examples] of using the {aws} CDK.
 
-The {aws} CDK is an open-source project. To contribute, see to  https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md[Contributing to the {aws} Cloud Development Kit ({aws} CDK)].
+The {aws} CDK is an open-source project. To contribute, see to  https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md[Contributing to the {aws} Cloud Development Kit ({aws} CDK)].

v2/guide/serverless_example.adoc

@@ -10,7 +10,6 @@ include::attributes.txt[]
 = Tutorial: Create a serverless Hello World application
 :info_titleabbrev: Tutorial: Serverless Hello World application
 :info_abstract: In this tutorial, you use the {aws} CDK to create a simple serverless Hello World application that implements a basic API backend.
-:tcx5-2025-waiver: 		 	 	 
 
 [abstract]
 --
@@ -1597,4 +1596,4 @@ $ aws lambda invoke --function-name CdkHelloWorldStack-HelloWorldFunctionunique-
 If `output.txt` shows a successful Lambda function response, the issue could be with how you defined your API Gateway REST API. The {aws} CLI invokes your Lambda directly, not through your endpoint. Check your code to ensure it matches this tutorial. Then, deploy again.
 +
 *Possible cause: Lambda resource is defined incorrectly in your stack file*:::
-If `output.txt` returns an error, the issue could be with how you defined your Lambda function. Check your code to ensure it matches this tutorial. Then deploy again.
+If `output.txt` returns an error, the issue could be with how you defined your Lambda function. Check your code to ensure it matches this tutorial. Then deploy again.

v2/guide/testing.adoc

@@ -6,7 +6,6 @@ include::attributes.txt[]
 [.topic]
 [#testing]
 = Test {aws} CDK applications
-:tcx5-2025-waiver: 		 	 	 
 
 // Content start
 
@@ -1552,4 +1551,4 @@ Don't copy and paste setup lines or common assertions. Instead, refactor this lo
 
 Don't try to do too much in one test. Preferably, a test should test one and only one behavior. If you accidentally break that behavior, exactly one test should fail, and the name of the test should tell you what failed. This is more an ideal to be striven for, however; sometimes you will unavoidably (or inadvertently) write tests that test more than one behavior. Snapshot tests are, for reasons we've already described, especially prone to this problem, so use them sparingly.
 
-include::testing-locally.adoc[leveloffset=+1]
+include::testing-locally.adoc[leveloffset=+1]