AWS amazonq documentation change
Summary
Fixed quotation mark formatting and clarified error message about SSE-KMS key access in S3 connector documentation.
Security assessment
Formatting changes and error message clarification. The SSE-KMS note explains existing security controls rather than introducing new ones or addressing vulnerabilities.
Diff
diff --git a/amazonq/latest/qbusiness-ug/s3-error-codes.md b/amazonq/latest/qbusiness-ug/s3-error-codes.md index 959a0050e..0f3f46399 100644 --- a//amazonq/latest/qbusiness-ug/s3-error-codes.md +++ b//amazonq/latest/qbusiness-ug/s3-error-codes.md @@ -12 +12 @@ S3-5001 | Profile name cannot be null or empty. Try again with a valid profile n -S3-5002 | Default AWS profile was not found. Verify the credentials file and try again. | Configure the AWS profile in the environment using “aws configure” command. +S3-5002 | Default AWS profile was not found. Verify the credentials file and try again. | Configure the AWS profile in the environment using "aws configure" command. @@ -24 +24 @@ S3-5111 | Unable to connect with provided Amazon S3 bucket due to connection tim -S3-5200 | Object was not accessible. Amazon S3 returned following error: | The object might be not accessible. User may receive this error if an object is encrypted using an SSE-KMS key that the profile doesn’t have the access. +S3-5200 | Object was not accessible. Amazon S3 returned following error: | The object might be not accessible. User may receive this error if an object is encrypted using an SSE-KMS key that the profile doesn't have the access.