[apigateway] Ability to specify custom cloudwatch role

Take a look there: https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-apigateway/lib/restapi.ts#L505

Class SpecRestApi always invokes configureCloudWatchRole (in case if props.cloudWatchRole missed as well in case if props.cloudWatchRole specified)

https://github.com/aws/aws-cdk/blob/384f9cb5e90dba577a216d04cfc0f85a1fc94714/packages/%40aws-cdk/aws-apigateway/lib/restapi.ts#L394

Method configureCloudWatchRole unconditionally create new role.

As result, props.cloudWatchRole option does not make any sense

Reproduction Steps

new apigateway.LambdaRestApi(.... { cloudWatchRole: <some role>})

What did you expect to happen?

AWS::ApiGateway::Account uses my role

What actually happened?

AWS::ApiGateway::Account uses unconditionally created role from configureCloudWatchRole

Environment

• CLI Version : does not matter
• Framework Version:: 1.61.0
• Node.js Version: does not matter
• OS : does not matter
• Language (Version): TypeScript (3.8.3)

---

This is 🐛 Bug Report

[nija-at]

@alvyn279 - this CfnAccount cloudwatch role area has a few holes here that needs a proper re-think and re-design. We’ve got issues like https://github.com/aws/aws-cdk/issues/7140, https://github.com/aws/aws-cdk/issues/10722 and https://github.com/aws/aws-cdk/issues/10878 in our repo.

I would recommend picking something else up, if you’re looking to contribute to the CDK. On the other hand, the workaround I’ve provided above should work if you’re looking to fix this specific issue.

[github-actions[bot]]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.