AWS Security ChangesHomeSearch

AWS b2bi medium security documentation change

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

File: b2bi/latest/userguide/transform-outbound-variations.md

Summary

Updated configuration steps for S3 directories, added validation for S3 setup prerequisites, emphasized security considerations for bucket policies and directory structure

Security assessment

Added explicit validation steps for S3 bucket policies and KMS key policies, emphasized proper directory separation to prevent processing loops. These changes address potential misconfiguration risks that could lead to unauthorized access or unintended data processing.

Diff

diff --git a/b2bi/latest/userguide/transform-outbound-variations.md b/b2bi/latest/userguide/transform-outbound-variations.md
index 18a9748bb..01f27e40b 100644
--- a//b2bi/latest/userguide/transform-outbound-variations.md
+++ b//b2bi/latest/userguide/transform-outbound-variations.md
@@ -168 +168 @@ _Trading capabilities_ contain the information required to build your event-driv
-     * Select an **EDI direction** , either **Inbound** or **Outbound**.
+     * For **EDI direction** , select **Outbound**.
@@ -174 +174 @@ _Trading capabilities_ contain the information required to build your event-driv
-  3. In the **Configure directories** section, you configure both the input and output directories that are used to source and store documents.
+  3. In the **Configure directories** section, you provide full S3 path to both the input and output directories.
@@ -176 +176 @@ _Trading capabilities_ contain the information required to build your event-driv
-     * In the **Input directory** area, enter an Amazon S3 bucket.
+     * You can use **Browse S3** to navigate to your available Amazon S3 buckets, where you can select a bucket (and optionally a prefix) to specify your preferred directories.
@@ -178 +178 @@ _Trading capabilities_ contain the information required to build your event-driv
-     * Choose **Browse S3** to navigate to your available Amazon S3 buckets, where you can select a bucket (and optionally a prefix) to specify your input directory.
+     * You can validate that your S3 buckets setup meets the prerequisites ([Prerequisites for using AWS B2B Data Interchange](./b2bi-prereq.html)) for AWS B2B Data Interchange using **Validate input S3 setup** and **Validate output S3 setup**.
@@ -180,3 +180 @@ _Trading capabilities_ contain the information required to build your event-driv
-###### Note
-
-B2B Data Interchange will create and monitor prefixes in your input directory for input X12 documents (for inbound X12) or for input JSON/XML documents (for generating X12).
+     * You can use **Copy policy** to copy a policy that you can then paste into your input/output directory's bucket policy to provide AWS B2B Data Interchange the necessary access.
@@ -184,7 +182 @@ B2B Data Interchange will create and monitor prefixes in your input directory fo
-     * Choose **Copy policy** to copy a policy that you can then paste into your input directory's bucket policy.
-
-     * Configure your output directory in the **Output directory** area, similarly to how you configured the input directory.
-
-###### Note
-
-B2B Data Interchange will create prefixes in the specified output directory to store the transformed X12 documents (in the case of inbound X12) or storing the generated X12 documents (in the case of outbound X12).
+![An example capability, showing the settings, the associate partnership, input and output directories, and an example tag.](/images/b2bi/latest/userguide/images/capability-example-inbound.png)
@@ -199 +191 @@ B2B Data Interchange will create prefixes in the specified output directory to s
-![An example capability, showing the settings, the associate partnership, input and output directories, attached reference documents, and an example tag.](/images/b2bi/latest/userguide/images/capability-example.png)
+###### Important considerations to avoid failed transformation attempts and unnecessary charges
@@ -201 +193 @@ B2B Data Interchange will create prefixes in the specified output directory to s
-###### Note
+  * B2B Data Interchange monitors all prefixes of your input directory for new files and attempts to transform every file placed in any prefix. Don't place files you don't want transformed into your input directory or its prefixes.
@@ -203 +195 @@ B2B Data Interchange will create prefixes in the specified output directory to s
-  * For your input and output directories, update the bucket policy ([Configure your Amazon S3 bucket policies](./b2bi-prereq.html#bucket-policy-configuration)). If your input or output buckets use SSE-KMS encryption, you also need to update the policy for your AWS KMS key. For details, see [Example bucket policies](./b2bi-prereq.html#bucket-policy-examples).
+  * Don't set your output directory as a subdirectory of your input directory. This configuration causes B2B Data Interchange to attempt processing output files as input files.
@@ -205 +197 @@ B2B Data Interchange will create prefixes in the specified output directory to s
-  * Enable EventBridge notifications for the Amazon S3 buckets used by the trading capability. For details, see ([Configure your Amazon S3 bucket EventBridge setting](./b2bi-prereq.html#bucket-policy-eventbridge)).
+  * B2B Data Interchange will automatically create prefixes in the specified input and output directories. Don't delete or edit these prefixes.