Skip to main content
NetApp Knowledge Base

When rotating cloud credentials the AltaVault generates "access denied" messages as it was not using updated credentials

Views:
129
Visibility:
Public
Votes:
0
Category:
altavault
Specialty:
dp
Last Updated:

Applies to

  • AVA-v
  • AVA-c
  • AVA400
  • AVA800

Issue

  • When a customer tries to rotate cloud credentials the AltaVault generates "access denied" messages indicating that it was not using the updated credentials.
  • System Logs may display the following messages while rotating the cloud credentials on the AltaVault appliance:

rfsd[2254]: [curl.INFO] (2279) (12:46:40.857074): Connection 1 seems to be dead!
rfsd[2254]: [curl.INFO] (2279) (12:46:40.857086): Closing connection 1
rfsd[2254]: [curl.INFO] (2279) (12:46:40.907140): SSL certificate verify ok.
rfsd[2254]: [curl.INFO] (2279) (12:46:40.907218): HEAD /testing/megastore.guid
HTTP/1.1
rfsd[2254]: [curl.INFO] (2279) (12:46:40.923534): HTTP/1.1 403 Server failed to
authenticate the request. Make sure the value of Authorization header is formed
correctly including the signature.
rfsd[2254]: [retry.ERR] (2279) failed request 0 of meta testing / megastore.guid
Knowledgebase
after receiving 0: "HTTP: Forbidden", status=access denied
rfsd[2254]: [megastore_guid.ERR] (2279) Cloud connection check failed: access
denied
mgmtd[1706]: [mgmtd.INFO]: Disconnected from cloud
mgmtd[1706]: [mgmtd.NOTICE]: Configuration saved to database initial

  • Here is an example log entry from an AltaVault using Amazon Web Services (AWS):

rfsd[27059]: [retry.ERR] (27097) failed request 0 of get test-alatavault /
megastore.guid after receiving 0: "InvalidAccessKeyId: The AWS Access Key Id you
provided does not exist in our records.", status=access denied

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device