Need support for PermissionBoundary property on AWS::IAM::CreateRole actions

[jrykowski-huron]

We've struggled to get the default template to work due to missing PermissionBoundary property. Had to add manually.

It would be good to support a parameter to specify.

Also still facing issue regarding the fact limitCheckStack uses reference to AWS::CloudFormation::Stack in an S3 location and we need to edit that as well to add the PermissionBoundary property.

If anyone has a work around to share, that'd be great! But for future, it'd be good if the template supported use of PermissionBoundary settings.

Without the PB set, we get CloudFormation stack error similar to this:

API: iam:CreateRole User: arn:aws:sts::{accountid}:assumed-role/{role}/jrykowski is not authorized to perform: iam:CreateRole on resource: arn:aws:iam::{accountid}:role/limitmonitor-limitCheckSt-LimitMonitorRole-1M8F2ZHBM59NZ with an explicit deny

[gsingh04]

@jrykowski-huron thanks for submitting the request. If you can open a pull request, it would be very helpful for us to understand the resolution that you are looking for.

[gsingh04]

Closing due to inactivity