- 最新
- 投票最多
- 评论最多
Hi Ohuk2, A permission set not provisioned refers to a permission set that has been created in AWS Identity Center, but not yet associated or applied to any target (such as an AWS account, OU, or user). After you created a Permission Set, and you have attached to it some permission, you need to define which IAM Identity Center Users or Groups can access which Accounts within your Organization with that permissions.
To do so, you should start from "AWS Accounts" under "Multi-account permissions" of the IAM Identity Center menu. Here you have to select the Account(s) where you want to grant the permissions to, then the User(s) or Group(s) you want to give that permissions, and finally the permission set(s) you want to use to assign the intended rights.
Last, but not least: The user and group assignment process might take a few minutes to complete, you have to leave the page open until the process successfully completes.
This create a relationship between Account-User/Group-Permission Set.
After this is done, the User should be able to login to the AWS access portal URL and, once authenticated, see the accounts where he/she can actually work, with the Permission Set(s) you specified.
Did you follow these steps and still the Permission Set is shown as Not Provisioned ?
What Identity Source are you using ? The IAM Identity Center Directory or an External federated IDP ?
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前