Skip to main content
NetApp Knowledge Base

Creating connector fails with an explicit deny in a permissions boundary

  1. Last updated
    Mar 28, 2024
  2. Save as PDF
Views:
169
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
bluexp
Last Updated:
3/28/2024, 7:32:31 AM

Applies to

  • NetApp BlueXP
  • NetApp Cloud Volume ONTAP (CVO)
  • Amazon Web Service (AWS)
  • Using permissions boundary

Issue

Creating connector fails with error:
Encountered a permissions error performing a tagging operation, please add required tag permissions. Retrying request without including tags. See https://repost.aws/knowledge-center/cloudformation-tagging-permission-error for how to resolve. Resource handler returned message: "User: arn:aws:sts::xxxxxxxxxxxx:assumed-role/<ROLE_NAME>/<CREDENTIALS_NAME> is not authorized to perform: iam:CreateRole on resource: arn:aws:iam::xxxxxxxxxxxx:role/aws-dev-operator with an explicit deny in a permissions boundary (Service: Iam, Status Code: 403, Request ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)"

 

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.