AWS access key error during Copy and Sync setup with StorageGRID as target

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 16

Visibility:: not set

Votes:: 0

Category:: netapp_console

Specialty:: ds_cs

Last Updated:

Applies to

NetApp Console
Copy & Sync
StorageGRID as target

Issue

After updating expired credentials and updating the connection string for a Copy and Sync relationship (Azure Data Lake Gen2 source to StorageGRID S3 target), the following error is encountered:

invalidaccesskeyid: The AWS AccessKeyId you provided does not exist in our records.

Cause

The error is returned by the StorageGRID S3 endpoint, not by Azure. When updating the relationship, the system attempts to validate S3 credentials for the StorageGRID target.
If the S3 access key and secret key cached by the data broker are expired or stale, or if the connection string is malformed (e.g., using an endpoint such as table.core.windows.net instead of blob.core.windows.net or dfs.core.windows.net), StorageGRID rejects the request with an “invalidaccesskeyid” error.

Solution

Re-create the Copy and Sync relationship using a fresh and valid S3 access key and secret key for the StorageGRID target.
Ensure that the connection string for the Azure Data Lake Gen2 source uses the correct endpoint (typically blob.core.windows.net or dfs.core.windows.net for ADLS Gen2, not table.core.windows.net).
Setting up the relationship anew clears any cached credentials and forces the data broker to use the updated, valid keys.

Partner Notes

partnerNotes_text

Additional Information

additionalInformation_text

Internal Notes

internalNotes_text