AWS datasync documentation change
Summary
Updated CustomSecretConfig description to specify IAM role instead of KMS key for secret access
Security assessment
This change clarifies that CustomSecretConfig uses IAM roles for secret access rather than KMS keys. This is a documentation correction/update about security feature implementation but doesn't indicate a security issue was fixed.
Diff
diff --git a/datasync/latest/userguide/API_UpdateLocationObjectStorage.md b/datasync/latest/userguide/API_UpdateLocationObjectStorage.md index 12da53277..a32d76c5f 100644 --- a//datasync/latest/userguide/API_UpdateLocationObjectStorage.md +++ b//datasync/latest/userguide/API_UpdateLocationObjectStorage.md @@ -86 +86 @@ Required: No -Specifies configuration information for a customer-managed secret, such as an authentication token or set of credentials that DataSync uses to access a specific transfer location, and a customer-managed AWS KMS key. +Specifies configuration information for a customer-managed secret, such as an authentication token or set of credentials that DataSync uses to access a specific transfer location, and a customer-managed AWS Identity and Access Management (IAM) role that provides access to the secret.