fix(step-functions):no longer attempt to modify cloudwatch logs permissions for state machines #1090
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Fixes #1089
Description of changes:
We originally attempted to reduce the default permissions assigned by the CDK to a State Machine by limiting the resource by region and account for 3 Cloudwatch actions. Trying to do this via the escape hatch is problematic.
Looking deeper at the changes we were making, Cloudwatch Logs are regional so processes can't write log groups in different regions and accounts anyway - so our IAM modifications provided no tangible benefit. Since they were providing no benefit and were breaking client code, we've just removed them.
This approach is supported by Step Functions documentation - https://docs.aws.amazon.com/step-functions/latest/dg/cw-logs.html#cloudwatch-iam-policy
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.