AWS amazonq documentation change
Summary
Moved 'Known limitations' section to a separate linked page and removed redundant content
Security assessment
The change restructures documentation but doesn't introduce new security content. The removed limitation about S3 bucket region alignment with Amazon Q index is an existing security consideration, but this is a documentation reorganization rather than addressing a new vulnerability.
Diff
diff --git a/amazonq/latest/qbusiness-ug/s3-connector.md b/amazonq/latest/qbusiness-ug/s3-connector.md index 1cfc317a5..a553b8ae2 100644 --- a//amazonq/latest/qbusiness-ug/s3-connector.md +++ b//amazonq/latest/qbusiness-ug/s3-connector.md @@ -5,2 +4,0 @@ -Known limitations - @@ -21 +19 @@ To learn how to create an Amazon S3 bucket, see [Creating a bucket](https://docs - * Known limitations for the Amazon S3 connector + * [Known limitations for the Amazon S3 connector](./s3-limitations.html) @@ -61,9 +58,0 @@ To learn how to create an Amazon S3 bucket, see [Creating a bucket](https://docs -## Known limitations for the Amazon S3 connector - -The Amazon S3 connector has the following known limitations: - - * The [Amazon S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html) bucket must be in the same AWS Region as your Amazon Q index, and your index must have permissions to access the bucket that contains your documents. - - - - @@ -78 +67 @@ IAM role -Overview +Known limitations