AWS Security ChangesHomeSearch

AWS quicksuite documentation change

Service: quicksuite · 2025-10-13 · Documentation low

File: quicksuite/latest/userguide/s3-integration.md

Summary

Updated documentation to consistently use 'Amazon S3' branding instead of 'S3' throughout the file. Removed specific pricing details from Enterprise subscription description and made minor editorial improvements.

Security assessment

Changes are primarily branding/naming convention updates (S3 → Amazon S3) and editorial improvements. No new security controls, vulnerabilities, or security features were added. Existing security-related content about IAM policies, KMS encryption, and cross-account access remains substantively unchanged.

Diff

diff --git a/quicksuite/latest/userguide/s3-integration.md b/quicksuite/latest/userguide/s3-integration.md
index fc585e009..136408597 100644
--- a//quicksuite/latest/userguide/s3-integration.md
+++ b//quicksuite/latest/userguide/s3-integration.md
@@ -5 +5 @@
-What you can doBefore you beginEnable cross-account access (administrators only)Prepare IAM role and policy setupSet up S3 integrationManage knowledge basesAdding document metadata in Amazon S3Troubleshooting S3 integration issuesLimitations
+What you can doBefore you beginEnable cross-account access (administrators only)Prepare IAM role and policy setupSet up Amazon S3 integrationManage knowledge basesAdding document metadata in Amazon S3Troubleshooting Amazon S3 integration issuesLimitations
@@ -19 +19 @@ Amazon S3 users can ask questions about content stored in their Amazon S3 bucket
-This guide covers S3 data ingestion integration for knowledge base creation. For Amazon S3 action connectors that perform Amazon S3 operations (upload, download, delete files), these must be created through the admin console. For more information, see [Creating AWS service action connectors using the admin console](./creating-action-connectors-admin-console.html).
+This guide covers Amazon S3 data ingestion integration for knowledge base creation. For Amazon S3 action connectors that perform Amazon S3 operations (upload, download, delete files), these must be created through the admin console. For more information, see [Creating AWS service action connectors using the admin console](./creating-action-connectors-admin-console.html).
@@ -23 +23 @@ This guide covers S3 data ingestion integration for knowledge base creation. For
-Before you set up S3 integration, make sure you have the following:
+Before you set up Amazon S3 integration, make sure you have the following:
@@ -29 +29 @@ Before you set up S3 integration, make sure you have the following:
-  * Amazon Quick Suite Enterprise subscription ($40 per user per month or higher).
+  * Amazon Quick Suite Enterprise subscription.
@@ -59 +59 @@ If you need to enable cross-account Amazon S3 access for your organization, comp
-Before setting up the integration in Amazon Quick Suite, prepare your IAM role and policy configuration. S3 integration uses AWS authentication to access your S3 buckets.
+Before setting up the integration in Amazon Quick Suite, prepare your IAM role and policy configuration. Amazon S3 integration uses AWS authentication to access your Amazon S3 buckets.
@@ -63 +63 @@ Before setting up the integration in Amazon Quick Suite, prepare your IAM role a
-Make sure your AWS account has the following minimum permissions for the S3 bucket:
+Make sure your AWS account has the following minimum permissions for the Amazon S3 bucket:
@@ -82 +82 @@ If you're accessing Amazon S3 buckets in a different AWS account, you must confi
-###### To configure S3 bucket permissions for cross-account access
+###### To configure Amazon S3 bucket permissions for cross-account access
@@ -84 +84 @@ If you're accessing Amazon S3 buckets in a different AWS account, you must confi
-  1. Sign in to the AWS Management Console for the account that contains the S3 bucket.
+  1. Sign in to the AWS Management Console for the account that contains the Amazon S3 bucket.
@@ -104 +104 @@ If you're accessing Amazon S3 buckets in a different AWS account, you must confi
-       * `Action` – Array of S3 permissions: s3:GetObject, s3:ListBucket, s3:GetBucketLocation, s3:GetObjectVersion, s3:ListBucketVersions
+       * `Action` – Array of Amazon S3 permissions: s3:GetObject, s3:ListBucket, s3:GetBucketLocation, s3:GetObjectVersion, s3:ListBucketVersions
@@ -106 +106 @@ If you're accessing Amazon S3 buckets in a different AWS account, you must confi
-       * `Resource` – "*" (applies to the current key), the S3 bucket path should look like the following: `"Resource": [ "arn:aws:s3:::bucket_name"]`
+       * `Resource` – "*" (applies to the current key), the Amazon S3 bucket path should look like the following: `"Resource": [ "arn:aws:s3:::bucket_name"]`
@@ -115 +115 @@ If you're accessing Amazon S3 buckets in a different AWS account, you must confi
-If your S3 bucket uses AWS KMS encryption, complete the following steps.
+If your Amazon S3 bucket uses AWS KMS encryption, complete the following steps.
@@ -119 +119 @@ If your S3 bucket uses AWS KMS encryption, complete the following steps.
-  2. Choose the KMS key that is used to encrypt your S3 bucket.
+  2. Choose the KMS key that is used to encrypt your Amazon S3 bucket.
@@ -133 +133 @@ If your S3 bucket uses AWS KMS encryption, complete the following steps.
-     * `Resource` – "*" (applies to the current key), the S3 bucket path should look like the following: `"Resource": [ "arn:aws:s3:::bucket_name"]`
+     * `Resource` – "*" (applies to the current key), the Amazon S3 bucket path should look like the following: `"Resource": [ "arn:aws:s3:::bucket_name"]`
@@ -149 +149 @@ During the integration setup, you will need to:
-## Set up S3 integration
+## Set up Amazon S3 integration
@@ -151 +151 @@ During the integration setup, you will need to:
-After preparing your IAM role and policy configuration, follow these steps to create your S3 integration:
+After preparing your IAM role and policy configuration, follow these steps to create your Amazon S3 integration:
@@ -159 +159 @@ After preparing your IAM role and policy configuration, follow these steps to cr
-     * **Default Account** – Use this option to access S3 buckets in the same AWS account where Amazon Quick Suite is enabled. This option is selected by default.
+     * **Default Account** – Use this option to access Amazon S3 buckets in the same AWS account where Amazon Quick Suite is enabled. This option is selected by default.
@@ -161 +161 @@ After preparing your IAM role and policy configuration, follow these steps to cr
-     * **Other AWS Account** – Use this option to access S3 buckets in a different AWS account.
+     * **Other AWS Account** – Use this option to access Amazon S3 buckets in a different AWS account.
@@ -169 +169 @@ If order for **Other AWS Account** to be used, your adming must enable the featu
-Cross-account S3 access is only supported within the same AWS region.
+Cross-account Amazon S3 access is only supported within the same AWS region.
@@ -171 +171 @@ Cross-account S3 access is only supported within the same AWS region.
-  4. If you selected **Other AWS Account** , enter the AWS account ID that contains the S3 bucket.
+  4. If you selected **Other AWS Account** , enter the AWS account ID that contains the Amazon S3 bucket.
@@ -175 +175 @@ Cross-account S3 access is only supported within the same AWS region.
-     * **Name** \- Descriptive name for your S3 integration.
+     * **Name** \- Descriptive name for your Amazon S3 integration.
@@ -177 +177 @@ Cross-account S3 access is only supported within the same AWS region.
-     * **S3 bucket URL** \- The S3 bucket path containing your documents. Your Amazon S3 bucket should be i the same region as your Amazon Quick Suite region.
+     * **Amazon S3 bucket URL** \- The Amazon S3 bucket path containing your documents. Your Amazon S3 bucket should be i the same region as your Amazon Quick Suite region.
@@ -200 +200 @@ After clicking create, the data sync is started automatically.
-After setting up your S3 integration, you can create and manage knowledge bases from your S3 content.
+After setting up your Amazon S3 integration, you can create and manage knowledge bases from your Amazon S3 content.
@@ -204 +204 @@ After setting up your S3 integration, you can create and manage knowledge bases
-You can modify your existing S3 knowledge bases:
+You can modify your existing Amazon S3 knowledge bases:
@@ -208 +208 @@ You can modify your existing S3 knowledge bases:
-  2. Select your S3 knowledge base from the list.
+  2. Select your Amazon S3 knowledge base from the list.
@@ -219 +219 @@ You can modify your existing S3 knowledge bases:
-You can create multiple knowledge bases from the same S3 integration:
+You can create multiple knowledge bases from the same Amazon S3 integration:
@@ -223 +223 @@ You can create multiple knowledge bases from the same S3 integration:
-  2. Choose your existing S3 integration from the list.
+  2. Choose your existing Amazon S3 integration from the list.
@@ -315 +315 @@ The `_created_at` and `_last_updated_at` metadata fields are ISO 8601 encoded da
-## Troubleshooting S3 integration issues
+## Troubleshooting Amazon S3 integration issues
@@ -317 +317 @@ The `_created_at` and `_last_updated_at` metadata fields are ISO 8601 encoded da
-If you encounter issues connecting to your S3 bucket, review the following common causes and solutions.
+If you encounter issues connecting to your Amazon S3 bucket, review the following common causes and solutions.
@@ -321 +321 @@ If you encounter issues connecting to your S3 bucket, review the following commo
-**Issue:** Your administrator hasn't granted access to use S3 buckets from other AWS accounts in Amazon Quick Suite.
+**Issue:** Your administrator hasn't granted access to use Amazon S3 buckets from other AWS accounts in Amazon Quick Suite.
@@ -327 +327 @@ If you encounter issues connecting to your S3 bucket, review the following commo
-  2. Under **Allow access and autodiscovery for these resources** , choose **Select S3 Bucket** and enable **S3 Buckets You Can Access Across AWS**.
+  2. Under **Allow access and autodiscovery for these resources** , choose **Select Amazon S3 Bucket** and enable **Amazon S3 Buckets You Can Access Across AWS**.
@@ -355 +355 @@ If your admin is only allowing certain buckets to be accessed, check with your a
-**Issue:** Your IAM role or user lacks the necessary permissions to access the S3 bucket.
+**Issue:** Your IAM role or user lacks the necessary permissions to access the Amazon S3 bucket.
@@ -359 +359 @@ If your admin is only allowing certain buckets to be accessed, check with your a
-  * Verify your IAM policy includes the required S3 permissions:
+  * Verify your IAM policy includes the required Amazon S3 permissions:
@@ -382 +382 @@ The ARN `arn:aws:iam::account-id:role/service-role/aws-quicksight-service-role-v
-**Issue:** The S3 bucket is located in a different AWS region than your Amazon Quick Suite account or service.
+**Issue:** The Amazon S3 bucket is located in a different AWS region than your Amazon Quick Suite account or service.
@@ -403 +403 @@ The ARN `arn:aws:iam::account-id:role/service-role/aws-quicksight-service-role-v
-  * **Check S3 Block Public Access settings** \- while these typically don't affect authenticated access, verify they're not interfering with your specific use case.
+  * **Check Amazon S3 Block Public Access settings** \- while these typically don't affect authenticated access, verify they're not interfering with your specific use case.