AWS datasync: Document credential storage via AWS Secrets Manager
Summary
Rewrites the intro to explain that DataSync location credentials (access/secret keys, user name/password, Kerberos keytab, SAS token) are security-sensitive and can be stored using AWS Secrets Manager, and removes the note limiting Secrets Manager integration to object storage and Azure Blob.
Security assessment
The added text explicitly frames location credentials as security-sensitive secrets and documents using AWS Secrets Manager to store them, which is credential-management best-practice guidance. It documents a security feature rather than fixing a specific vulnerability.
Evidence
+DataSync uses [locations](https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-transfer-works.html#sync-locations) to access your storage resources located on premises, in other clouds, or in AWS. Some location types require credentials to authenticate with your storage system. Credential types include an access key and secret key, a user name and password, a Kerberos keytab, or a SAS token. These types of credentials are inherently security-sensitive (must be kept secret), and they are valid until you explicitly revoke then via your authentication management system (e.g. Active Directory, or cloud storage IAM). When you create a DataSync location that requires access credentials for authentication, you can use AWS Secrets Manager (Secrets Manager) to store the secret for your credentials.
Diff
diff --git a/datasync/latest/userguide/location-credentials.md b/datasync/latest/userguide/location-credentials.md index 201e7c8..bdf0be6 100644 --- a//datasync/latest/userguide/location-credentials.md +++ b//datasync/latest/userguide/location-credentials.md @@ -11 +11 @@ Using a service-managed secret encrypted with a default keyUsing a service-manag -###### Note +DataSync uses [locations](https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-transfer-works.html#sync-locations) to access your storage resources located on premises, in other clouds, or in AWS. Some location types require credentials to authenticate with your storage system. Credential types include an access key and secret key, a user name and password, a Kerberos keytab, or a SAS token. These types of credentials are inherently security-sensitive (must be kept secret), and they are valid until you explicitly revoke then via your authentication management system (e.g. Active Directory, or cloud storage IAM). When you create a DataSync location that requires access credentials for authentication, you can use AWS Secrets Manager (Secrets Manager) to store the secret for your credentials. @@ -13,3 +13 @@ Using a service-managed secret encrypted with a default keyUsing a service-manag -Secrets Manager integration is available for object storage and Microsoft Azure Blob Storage. - -DataSync uses [locations](https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-transfer-works.html#sync-locations) to access your storage resources located on premises, in other clouds, or in AWS. Some location types require credentials to authenticate with your storage system. Credential types include an access key and secret key, a user name and password, a Kerberos keytab, or a SAS token. When you create a DataSync location that requires credentials for authentication, you can use AWS Secrets Manager (Secrets Manager) to store the secret for your credentials. The following options are available: +The following options are available :