Remove IAM policy change - address in new PR instead

Apply suggestion from doc review

Author: kbatuigas

modules/manage/pages/iceberg/iceberg-topics-aws-glue.adoc

@@ -46,7 +46,7 @@ If you want to use partitioning, you must implement custom partitioning using yo
 
 [NOTE]
 ====
-In Redpanda versions 25.2.1, and 25.1.9 and earlier, an empty partition spec () can cause a known issue that prevents certain engines like Amazon Redshift from successfully querying the table. To resolve this issue, specify custom partitioning, or upgrade Redpanda to versions 25.2.2 or 25.1.10 and later.
+In Redpanda versions 25.2.1 and earlier, an empty partition spec `()` can cause a known issue that prevents certain engines like Amazon Redshift from successfully querying the table. To resolve this issue, specify custom partitioning, or upgrade Redpanda to versions 25.2.2 or later.
 ====
 
 === Manual deletion of Iceberg tables
@@ -65,7 +65,6 @@ When `iceberg_delete` or the topic override `redpanda.iceberg.delete` is set to
 
 == Authorize access to AWS Glue
 
-ifndef::env-cloud[]
 You must allow Redpanda access to AWS Glue services in your AWS account. You can use the same access credentials that you configured for S3 (IAM role, access keys, and KMS key), as long as you have also added read and write access to AWS Glue Data Catalog.
 
 For example, you could create a separate IAM policy that manages access to AWS Glue, and attach it to the IAM role that Redpanda also uses to access S3. It is recommended to add all AWS Glue API actions in the policy (`"glue:*"`) on the following resources:
@@ -95,64 +94,6 @@ Your IAM policy should include a statement similar to the following:
   ]
 }
 ----
-endif::[]
-
-ifdef::env-cloud[]
-You must allow Redpanda access to AWS Glue services in your AWS account. It is recommended to create a new IAM policy or role that manages access to AWS Glue, allowing all AWS Glue API actions (`"glue:*"`) on the following resources:
-
-- Root catalog (`catalog`)
-- All databases (`database/*`)
-- All tables (`table/\*/*`)
-
-Your IAM policy should include a statement similar to the following:
-
-[,json]
-----
-{
-  "Version": "2012-10-17",
-  "Statement": [
-    {
-      "Effect": "Allow",
-      "Action": [
-        "glue:*"
-      ],
-      "Resource": [
-        "arn:aws:glue:<aws-region>:<aws-account-id>:catalog",
-        "arn:aws:glue:<aws-region>:<aws-account-id>:database/*",
-        "arn:aws:glue:<aws-region>:<aws-account-id>:table/*/*"
-        ]
-    },
-    {
-      "Effect": "Allow",
-      "Action": [
-        "s3:PutObject",
-        "s3:PutObjectAcl",
-        "s3:DeleteObject"
-      ],
-      "Resource": [
-        "arn:aws:s3:::redpanda-cloud-storage-<redpanda-cluster-id>/redpanda-iceberg-catalog/*"
-      ]
-    },
-    {
-      "Effect": "Allow",
-      "Action": [
-        "s3:ListBucket"
-      ],
-      "Resource": [
-        "arn:aws:s3:::redpanda-cloud-storage-<redpanda-cluster-id>"
-      ],
-      "Condition": {
-        "StringLike": {
-          "s3:prefix": [
-            "redpanda-iceberg-catalog/*"
-          ]
-        }
-      }
-    }
-  ]
-}
-----
-endif::[]
 
 For more information on configuring IAM permissions, see the https://docs.aws.amazon.com/glue/latest/dg/configure-iam-for-glue.html[AWS Glue documentation^].