From 889c95d0f2b5a977fa0b02088cdab57bfbca5664 Mon Sep 17 00:00:00 2001
From: Hima <31167870+himaatluri@users.noreply.github.com>
Date: Wed, 24 Sep 2025 23:20:46 -0400
Subject: [PATCH 1/2] Update cross-account-access.adoc

Removed some weird (at least for me) text in the policy doc examples.

Weird text removed - "&TCX5-2025-waiver;"
---
 .../ug/manage-access/aws-access/cross-account-access.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/latest/ug/manage-access/aws-access/cross-account-access.adoc b/latest/ug/manage-access/aws-access/cross-account-access.adoc
index 72267f78..8674c058 100644
--- a/latest/ug/manage-access/aws-access/cross-account-access.adoc
+++ b/latest/ug/manage-access/aws-access/cross-account-access.adoc
@@ -44,7 +44,7 @@ In this example, Account B creates an IAM policy with the permissions to give to
 [source,json,subs="verbatim,attributes"]
 ----
 {
-  "Version": "2012-10-17",&TCX5-2025-waiver;{tcx5-waiver}
+  "Version": "2012-10-17",
   "Statement": [
     {
       "Effect": "Allow",
@@ -63,7 +63,7 @@ Account A creates a role with a trust policy that gets credentials from the iden
 [source,json,subs="verbatim,attributes"]
 ----
 {
-  "Version": "2012-10-17",&TCX5-2025-waiver;{tcx5-waiver}
+  "Version": "2012-10-17",
   "Statement": [
     {
       "Effect": "Allow",
@@ -81,7 +81,7 @@ Account A attaches a policy to that role with the following permissions to assum
 [source,json,subs="verbatim,attributes"]
 ----
 {
-    "Version": "2012-10-17",&TCX5-2025-waiver;{tcx5-waiver}
+    "Version": "2012-10-17",
     "Statement": [
         {
             "Effect": "Allow",
@@ -107,4 +107,4 @@ role_arn={arn-aws}iam::111122223333:role/account-a-role
 
 To specify chained profiles for other {aws} SDKs, consult the documentation for the SDK that you're using. For more information, see link:developer/tools/[Tools to Build on {aws},type="marketing"].
 
-====
\ No newline at end of file
+====

From 6f8113676c7ade7886571c7166a8cbaad513773f Mon Sep 17 00:00:00 2001
From: pgasca <87044997+pgasca@users.noreply.github.com>
Date: Mon, 29 Sep 2025 10:33:57 -0500
Subject: [PATCH 2/2] Update cross-account-access.adoc

---
 .../ug/manage-access/aws-access/cross-account-access.adoc   | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/latest/ug/manage-access/aws-access/cross-account-access.adoc b/latest/ug/manage-access/aws-access/cross-account-access.adoc
index 8674c058..ebc76c52 100644
--- a/latest/ug/manage-access/aws-access/cross-account-access.adoc
+++ b/latest/ug/manage-access/aws-access/cross-account-access.adoc
@@ -44,7 +44,7 @@ In this example, Account B creates an IAM policy with the permissions to give to
 [source,json,subs="verbatim,attributes"]
 ----
 {
-  "Version": "2012-10-17",
+  "Version": "2012-10-17",{tcx5-waiver}
   "Statement": [
     {
       "Effect": "Allow",
@@ -63,7 +63,7 @@ Account A creates a role with a trust policy that gets credentials from the iden
 [source,json,subs="verbatim,attributes"]
 ----
 {
-  "Version": "2012-10-17",
+  "Version": "2012-10-17",{tcx5-waiver}
   "Statement": [
     {
       "Effect": "Allow",
@@ -81,7 +81,7 @@ Account A attaches a policy to that role with the following permissions to assum
 [source,json,subs="verbatim,attributes"]
 ----
 {
-    "Version": "2012-10-17",
+    "Version": "2012-10-17",{tcx5-waiver}
     "Statement": [
         {
             "Effect": "Allow",