You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.
As a technologist working in a development AWS account that has guardrails implemented via an IAM permissions boundary, I need the CloudFormation templates to provide me with the option to specify the ARN of an IAM permissions boundary policy so that the permissions boundary can be supplied during creation of IAM roles in these templates.
Background
This particular AWS account and development environment provides technologists with freedom to create and manage IAM roles, but that work is subject to the technologist being required to associate an existing IAM permissions boundary during role creation. That permission boundary inhibits technologists from modifying the underlying foundation of their development environment.
The text was updated successfully, but these errors were encountered:
ckamps
added a commit
to ckamps/quickstart-microsoft-pki
that referenced
this issue
Dec 24, 2020
As a technologist working in a development AWS account that has guardrails implemented via an IAM permissions boundary, I need the CloudFormation templates to provide me with the option to specify the ARN of an IAM permissions boundary policy so that the permissions boundary can be supplied during creation of IAM roles in these templates.
Background
This particular AWS account and development environment provides technologists with freedom to create and manage IAM roles, but that work is subject to the technologist being required to associate an existing IAM permissions boundary during role creation. That permission boundary inhibits technologists from modifying the underlying foundation of their development environment.
The text was updated successfully, but these errors were encountered: