AWS Security ChangesHomeSearch

AWS bedrock high security documentation change

Service: bedrock · 2026-05-13 · Security-related high

File: bedrock/latest/userguide/cross-account-access-cmi.md

Summary

Updated documentation for cross-account S3 access during custom model imports, clarified steps for KMS-encrypted buckets, and added details about console-created default roles.

Security assessment

The changes explicitly document how to configure IAM policies and KMS key policies for secure cross-account access to S3 buckets containing models. It addresses potential security gaps by specifying required permissions for decryption and access control, particularly for KMS-encrypted resources.

Diff

diff --git a/bedrock/latest/userguide/cross-account-access-cmi.md b/bedrock/latest/userguide/cross-account-access-cmi.md
index 3a155f843..fa5b341f1 100644
--- a//bedrock/latest/userguide/cross-account-access-cmi.md
+++ b//bedrock/latest/userguide/cross-account-access-cmi.md
@@ -11 +11,5 @@ Configure cross-account access to Amazon S3 bucketConfigure cross-account access
-If you are importing your model from Amazon S3 bucket and using cross-account Amazon S3 you will need to grant permissions to users in the bucket owner's account for accessing the bucket before you import your customized model. See [Prerequisites for importing custom model](./custom-model-import-prereq.html).
+If you are importing your model from an Amazon S3 bucket in a different AWS account, you will need to grant permissions for accessing the bucket before you import your customized model. See [Prerequisites for importing custom model](./custom-model-import-prereq.html).
+
+###### Note
+
+If the custom model import job was submitted through the Amazon Bedrock console, a default import execution role is created automatically. You must edit the default import execution role policy and replace the account ID specified for `aws:ResourceAccount` with the AWS account ID of the bucket owner.
@@ -15 +19 @@ If you are importing your model from Amazon S3 bucket and using cross-account Am
-This section walks you through the steps for creating policies for users in the bucket owners's account for accessing Amazon S3 bucket. 
+Follow these steps to configure cross-account access to an Amazon S3 bucket for a custom model import job.
@@ -17 +21,3 @@ This section walks you through the steps for creating policies for users in the
-  1. In the bucket owner account, create a bucket policy that provides access to the users in the bucket owner's account.
+  1. **Create an import execution role** – In the user's AWS account (the account that will run the import job), create an IAM role that Amazon Bedrock can assume. For more information about creating a service role for custom model import, see [Prerequisites for importing custom model](./custom-model-import-prereq.html).
+
+  2. **Create a bucket policy** – In the bucket owner's account, create a bucket policy that grants access to the import execution role in the user's account.
@@ -49 +55 @@ JSON
-  2. In the user’s AWS account, create an import execution role policy. For `aws:ResourceAccount` specify account id of the bucket owner's AWS account.
+  3. **Create an import execution role policy** – In the user's AWS account, attach a policy to the import execution role that allows access to the cross-account bucket. For `aws:ResourceAccount`, specify the account ID of the bucket owner's AWS account.
@@ -87 +93 @@ JSON
-If you have an Amazon S3 bucket that is encrypted with a custom AWS Key Management Service (AWS KMS) key, you will need to grant access to it to users from bucket owner's account.
+If the Amazon S3 bucket is encrypted with a custom AWS Key Management Service (AWS KMS) key, you need to perform additional steps to grant the import execution role permissions to decrypt the key.
@@ -89 +95 @@ If you have an Amazon S3 bucket that is encrypted with a custom AWS Key Manageme
-To configure cross-account access to Amazon S3 bucket encrypted with a custom AWS KMS key
+  1. **Create an import execution role** – In the user's AWS account, create an IAM role that Amazon Bedrock can assume. For more information, see [Prerequisites for importing custom model](./custom-model-import-prereq.html).
@@ -91 +97 @@ To configure cross-account access to Amazon S3 bucket encrypted with a custom AW
-  1. In the bucket owner account, create a bucket policy that provides access to the users in bucket owner's account.
+  2. **Create a bucket policy** – In the bucket owner's account, create a bucket policy that grants access to the import execution role in the user's account.
@@ -123 +129 @@ JSON
-  2. In the bucket owner account, create the following resource policy to allow user's account import role to decrypt.
+  3. **Update the AWS KMS key policy** – In the bucket owner's account, add the following statement to the AWS KMS key policy to allow the user's import execution role to decrypt objects.
@@ -129 +135 @@ JSON
-       "AWS": "arn:aws:iam::"arn:aws:iam::123456789123:role/ImportRole"
+            "AWS": "arn:aws:iam::123456789123:role/ImportRole"
@@ -137,0 +144 @@ JSON
+  4. **Create an import execution role policy** – In the user's AWS account, attach a policy to the import execution role that allows access to the cross-account bucket and the AWS KMS key. For `aws:ResourceAccount`, specify the account ID of the bucket owner's AWS account.
@@ -139,3 +146 @@ JSON
-  3. In the user’s AWS account, create an import execution role policy. For `aws:ResourceAccount` specify account id of the bucket owner's AWS account. Also, provide access to the AWS KMS key that is used to encrypt the bucket.
-
-The following example import execution role policy in the user's account provides the bucket owner's account id `111222333444555` access to Amazon S3 bucket `s3://amzn-s3-demo-bucket` and the AWS KMS key `arn:aws:kms:`us-west-2:123456789098`:key/`111aa2bb-333c-4d44-5555-a111bb2c33dd``
+The following example import execution role policy provides access to the bucket owner's Amazon S3 bucket `s3://amzn-s3-demo-bucket` in account `111222333444555` and the AWS KMS key `arn:aws:kms:`us-west-2:123456789098`:key/`111aa2bb-333c-4d44-5555-a111bb2c33dd``.