Skip to main content
NetApp Knowledge Base

AWS IAM Key Rotation Fails to Propagate to CVO Systems

  1. Last updated
  2. Save as PDF
Views:
22
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
amazon_web_service
Last Updated:

Applies to

  • NetApp Cloud Volumes ONTAP (CVO) in AWS
  • NetApp Console

Issue

After rotating AWS IAM access keys and updating them in the NetApp console, the new credentials were not propagated to underlying Cloud Volumes ONTAP (CVO) systems.

Observed Error Messages:

  • “Could not set the AWS credentials. Verify that the credentials are correct and then try again.”
  • “The security token included in the request is invalid. (Service: AmazonIdentityManagement; StatusCode: 403; ErrorCode: InvalidClientTokenId)”
  • Mediator status degraded or down, seen in Audit logs: 
    DescribeMediatorStatus failed
PlainText
{
  "_failure": "Premature connection close (the server doesn't appear to support request pipelining)"
}
  • EMS log: 
    Calculated DEGRADED status with reason: Failed to establish HTTP connection to the mediator

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

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.