AWS Security ChangesHomeSearch

AWS b2bi medium security documentation change

Service: b2bi · 2025-10-19 · Security-related medium

File: b2bi/latest/userguide/b2bi-prereq.md

Summary

Restructured S3 bucket policy configuration section with detailed step-by-step instructions, added EventBridge notification setup guidance, and expanded documentation about temporary file management permissions

Security assessment

The changes emphasize proper S3 bucket policy configuration and KMS key management, which are critical for access control and data encryption security. Specific security implications include: 1) Explicit requirement for s3:DeleteObject permission to prevent persistent temporary files (security risk if sensitive data remains) 2) Warning against using non-editable AWS managed keys for KMS 3) Detailed encryption policy requirements for SSE-KMS/DSSE-KMS buckets

Diff

diff --git a/b2bi/latest/userguide/b2bi-prereq.md b/b2bi/latest/userguide/b2bi-prereq.md
index f0355ad44..0b46aab56 100644
--- a//b2bi/latest/userguide/b2bi-prereq.md
+++ b//b2bi/latest/userguide/b2bi-prereq.md
@@ -5 +5 @@
-Sign up for an AWS accountCreate a user with administrative accessConfigure an Amazon S3 bucketAmazon S3 bucket policies and permissions
+Sign up for an AWS accountCreate a user with administrative accessConfigure an Amazon S3 bucketSetting up S3 bucket policies and permissions
@@ -93 +93,23 @@ You need to have an Amazon S3 bucket set up and ready to use. B2B Data Interchan
-## Amazon S3 bucket policies and permissions
+## Setting up S3 bucket policies and permissions
+
+Before you can transform and generate Electronic Data Interchange (EDI) documents, you must configure S3 bucket policies for your trading capabilities. This topic provides step-by-step instructions and example policies to help you get started.
+
+### Configuring S3 bucket policies
+
+Follow these steps to configure policies for both your input and output buckets. If your buckets use SSE-KMS encryption, you must also update your AWS KMS key policy. For policy examples, see Example policies.
+
+###### To configure a bucket policy
+
+  1. Open the Amazon S3 console at [https://console.aws.amazon.com/s3/](https://console.aws.amazon.com/s3/).
+
+  2. Navigate to your bucket and choose the **Permissions** tab.
+
+  3. In the **Bucket policy** section, choose **Edit**.
+
+  4. Do one of the following:
+
+     * Copy an example policy from Example policies and paste it into the policy editor.
+
+     * Choose **Copy policy** when creating a trading capability, and paste the copied policy.
+
+  5. Choose **Save changes**.
@@ -95 +116,0 @@ You need to have an Amazon S3 bucket set up and ready to use. B2B Data Interchan
-Before you can begin transforming and generating Electronic Interchange Data (EDI) documents, you need to set up the Amazon S3 bucket policies that you need for working with B2B Data Interchange resources. This topic also provides example policies to help you get started.
@@ -97 +117,0 @@ Before you can begin transforming and generating Electronic Interchange Data (ED
-### Configure your Amazon S3 bucket policies
@@ -99 +118,0 @@ Before you can begin transforming and generating Electronic Interchange Data (ED
-You can copy example policies as described in the preceding section. If one or both of your buckets use SSE-KMS encryption, you also need to update your AWS KMS key policy, as described in Example bucket policies.
@@ -103 +122 @@ You can copy example policies as described in the preceding section. If one or b
-For details on temporary files and directories, see Temporary files and Amazon S3 permissions.
+For information about temporary files and related permissions, see Managing temporary files and permissions.
@@ -105 +124 @@ For details on temporary files and directories, see Temporary files and Amazon S
-Perform this procedure for both your input and output directories.
+### Enabling EventBridge notifications
@@ -107 +126 @@ Perform this procedure for both your input and output directories.
-###### Configure your bucket policy
+You must enable Amazon EventBridge notifications for your input S3 bucket.
@@ -109 +128 @@ Perform this procedure for both your input and output directories.
-  1. Sign into the AWS Management Console and open the Amazon S3 console at [https://console.aws.amazon.com/s3/](https://console.aws.amazon.com/s3/) and navigate to your bucket.
+###### To enable EventBridge notifications
@@ -111 +130 @@ Perform this procedure for both your input and output directories.
-  2. After you open the detail page for your bucket, choose the **Permissions** tab.
+  1. Open the Amazon S3 console at [https://console.aws.amazon.com/s3/](https://console.aws.amazon.com/s3/).
@@ -113 +132 @@ Perform this procedure for both your input and output directories.
-  3. In the **Bucket policy** panel, choose **Edit**.
+  2. Navigate to your bucket and choose the **Properties** tab.
@@ -115 +134 @@ Perform this procedure for both your input and output directories.
-  4. Paste in the appropriate bucket policy, depending on whether this is your input or output bucket.
+  3. Scroll to the **EventBridge** section.
@@ -117 +136 @@ Perform this procedure for both your input and output directories.
-  5. Choose **Save** to save the policy.
+  4. If notifications are already enabled, you're done. Otherwise, continue to the next step.
@@ -118,0 +138 @@ Perform this procedure for both your input and output directories.
+  5. Choose **Edit**.
@@ -119,0 +140 @@ Perform this procedure for both your input and output directories.
+  6. Select **On** and choose **Save changes**.
@@ -122 +142,0 @@ Perform this procedure for both your input and output directories.
-### Configure your Amazon S3 bucket EventBridge setting
@@ -124 +143,0 @@ Perform this procedure for both your input and output directories.
-You need to turn on Amazon EventBridge for your input and output Amazon S3 buckets.
@@ -126 +145 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-###### Turn on EventBridge notifications
+###### Important
@@ -128 +147 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-  1. Sign into the AWS Management Console and open the Amazon S3 console at [https://console.aws.amazon.com/s3/](https://console.aws.amazon.com/s3/) and navigate to your bucket.
+After enabling EventBridge, wait at least 5 minutes before placing files in your S3 bucket. This allows time for the changes to take effect.
@@ -130 +149 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-  2. After you open the detail page for your bucket, choose the **Properties** tab.
+### Managing temporary files and permissions
@@ -132 +151 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-  3. Scroll down to the **Amazon EventBridge** panel. If notifications are off, proceed to the next step. If they are on, you can skip the remainder of this procedure.
+Your output bucket policies require the following permissions:
@@ -134 +153 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-  4. To turn on EventBridge notifications, choose **Edit**.
+  * `s3:GetObject` \- Allows the service to read temporary files
@@ -136 +155 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-  5. Select **On** , and choose **Save changes**.
+  * `s3:DeleteObject` \- Enables cleanup of temporary files
@@ -141 +160 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-###### Note
+###### Important
@@ -143 +162 @@ You need to turn on Amazon EventBridge for your input and output Amazon S3 bucke
-After you enable EventBridge, it takes approximately five minutes for the changes to take effect. Wait at least 5 minutes after enabling EventBridge events before placing your files in an Amazon S3 bucket.
+Without the `s3:DeleteObject` permission:
@@ -145 +164 @@ After you enable EventBridge, it takes approximately five minutes for the change
-### Temporary files and Amazon S3 permissions
+  * Temporary files remain in your S3 bucket and incur storage charges.
@@ -147 +166 @@ After you enable EventBridge, it takes approximately five minutes for the change
-For your output bucket policies, you need to have the `s3:GetObject` and `s3:DeleteObject` permissions. These permissions are required so that B2B Data Interchange read and then remove temporary files that the service uses to transform your EDI documents. 
+  * These files can be up to ten times larger than the input X12 file.
@@ -149 +167,0 @@ For your output bucket policies, you need to have the `s3:GetObject` and `s3:Del
-The service uses `s3:DeleteObject` to delete temporary files, which can be ten times as large as the X12 input file. If your bucket policy doesn't include `s3:DeleteObject`, the service continues to work as expected. However, B2B Data Interchange would not be able to delete these temporary files: they would then remain in Amazon S3 (and incur charges).
@@ -151 +168,0 @@ The service uses `s3:DeleteObject` to delete temporary files, which can be ten t
-The service adds a new prefix to your output directory, `customerOutputDirectory/parsed`, for its use, and `customerOutputDirectory/`tradingPartnerId`/parsed` for use by Amazon S3 (if you have a partnership). These locations are used exclusively for holding temporary files. If your bucket policy includes the `s3:DeleteObject` permission, you should never see these folders. If you don't have that permission, then the temporary files continue to be written and remain in these folders.
@@ -153 +169,0 @@ The service adds a new prefix to your output directory, `customerOutputDirectory
-### Example bucket policies
@@ -155 +171,5 @@ The service adds a new prefix to your output directory, `customerOutputDirectory
-You need to update your Amazon S3 bucket policies to include the appropriate permissions so that the B2B Data Interchange service can access your input documents and store the generated outputs.
+The service uses the following locations for temporary files:
+
+  * `customerOutputDirectory/parsed` \- For service use
+
+  * `customerOutputDirectory/`tradingPartnerId`/parsed` \- For S3 use (when using partnerships)
@@ -157 +176,0 @@ You need to update your Amazon S3 bucket policies to include the appropriate per
-The following are policies copied from the **Create trading capability** page. You can select **View** to view your bucket. Then, from your bucket page, choose **Permissions** > **Bucket policy** > **Edit** , and then paste this policy into the **Policy** field.
@@ -159 +177,0 @@ The following are policies copied from the **Create trading capability** page. Y
-###### Note
@@ -161 +178,0 @@ The following are policies copied from the **Create trading capability** page. Y
-In these examples, replace each `user input placeholder` with your own information.
@@ -163 +180 @@ In these examples, replace each `user input placeholder` with your own informati
-Example Amazon S3 input bucket policy
+### Example policies
@@ -164,0 +182,7 @@ Example Amazon S3 input bucket policy
+Use these example policies to configure permissions for your S3 buckets and AWS KMS keys.
+
+###### Important
+
+Replace all `user input placeholder` values with your own information.
+
+Input bucket policy
@@ -166 +189,0 @@ Example Amazon S3 input bucket policy
-Example Amazon S3 input bucket policy copied from the **Trading capabilities** page.
@@ -201 +224 @@ JSON
-Example Amazon S3 output bucket policy
+Output bucket policy
@@ -204,2 +226,0 @@ Example Amazon S3 output bucket policy
-Example Amazon S3 output bucket policy copied from the **Trading capabilities** page.
-
@@ -241 +262 @@ JSON
-If you have SSE-KMS or DSSE-KMS encryption enabled on your input or output bucket, you need to update the key policy in AWS KMS. You need to add the B2B Data Interchange service principal and the appropriate permissions to the policy. To read more about data protection, see [Data protection in AWS B2B Data Interchange](./data-protection.html). 
+If you use SSE-KMS or DSSE-KMS encryption, you must also configure AWS KMS key policies:
@@ -243 +264 @@ If you have SSE-KMS or DSSE-KMS encryption enabled on your input or output bucke
-###### Note
+###### Important
@@ -245 +266 @@ If you have SSE-KMS or DSSE-KMS encryption enabled on your input or output bucke
-If you are using SSE-KMS or DSSE-KMS encryption, do not use an AWS managed key policy, as they cannot be edited. 
+Don't use AWS managed key policies - they can't be edited. Create a customer managed key instead.
@@ -247 +268 @@ If you are using SSE-KMS or DSSE-KMS encryption, do not use an AWS managed key p
-Example Amazon S3 input AWS KMS key policy
+Input KMS key policy
@@ -250 +271 @@ Example Amazon S3 input AWS KMS key policy
-The following example policy is for use with an encrypted input/source bucket. It includes the permission needed to decrypt an encrypted file.
+Use this policy for encrypted input buckets to allow decryption of files:
@@ -287 +308 @@ JSON
-Example Amazon S3 output AWS KMS key policy
+Output KMS key policy
@@ -290 +311 @@ Example Amazon S3 output AWS KMS key policy
-The following example policy is for use with an encrypted output bucket. It includes the permission needed to encrypt a file for storing into the bucket.
+Use this policy for encrypted output buckets to allow encryption of files:
@@ -327 +348 @@ JSON
-If you are using the same bucket for input and output, you can use either example key policy, and add in the other permission. In this case, the policy is as follows.
+If you use the same bucket for both input and output, use either policy and add the other permission, as shown in this example: