adamtimmins

@sea-erkin do you have an updated snippet for the latest version? Trying what you made but I'm getting errors.

@caffix can we expect an update with proxy implementation in the near future?

> Hi @adamtimmins , thanks for reaching out. It seems like what you are mentioning here is quite similar to the bug described [here](https://github.com/aws/aws-cdk/issues/13310) and [this reasoning](https://github.com/aws/aws-cdk/issues/13310#issuecomment-787410159) and [further explanation](https://github.com/aws/aws-cdk/issues/12323#issuecomment-755505645)...

> It is also possible to patch using the Aspect as follows given that the type of object for the role is a CfnResource and it has a node path...

> @adamtimmins actually above was just an example of getting to the resource you want to "patch" with an Aspect (in this case I assign an IAM path to isolate...

> @adamtimmins I was actually running into the same issue yesterday, even posted a comment here but then deleted it as I found the issue. > > I was applying...

I've managed to isolate where exactly the role is being created. `AWSCDKCfnUtilsProviderCustomResourceProviderRoleFE0EE867 ` and it's corresponding Lambda `AWSCDKCfnUtilsProviderCustomResourceProviderHandlerCF82AA57 ` are created when you reference a certain construct value within `AwsCustomResource`....

Had a back and forth with AWS premium support and was recommended the following solution, which worked for us (thanks Greg!). The solution for us was to use `iam.Role.customize_roles` (https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_iam/Role.html#aws_cdk.aws_iam.Role.customize_roles)...