aws_stepfunctions | aws_logs: codepipeline update failure, invalid logging configuration

[ekeyser]

Describe the bug

I tried adding a logs block to my state machines and everything blew up. I tried the suggestion of prefixing the log group name with /aws/vendedlogs/states/ to no avail. I don't even know what "vendedlogs" means lol.

Resource handler returned message: "Invalid Logging Configuration: The CloudWatch Logs Resource Policy size was exceeded. We suggest prefixing your CloudWatch log group name with /aws/vendedlogs/states/. (Service: AWSStepFunctions; Status Code: 400; Error Code: InvalidLoggingConfiguration; Request ID: c602b89a-0ba3-4d0e-aca9-5bd2568e02e7; Proxy: null)" (RequestToken: , HandlerErrorCode: InvalidRequest)

 logs: {
                     destination: new logs.LogGroup(scope, '/aws/vendedlogs/states/myloggroupname'),
                     level: sfn.LogLevel.ALL,
                     includeExecutionData: true,
                }

Expected Behavior

No update failure.

Current Behavior

Updating the stack resulted in a failure with the above message.

Reproduction Steps

 logs: {
                     destination: new logs.LogGroup(scope, '/aws/vendedlogs/states/myloggroupname'),
                     level: sfn.LogLevel.ALL,
                     includeExecutionData: true,
                }

Possible Solution

No response

Additional Information/Context

I see some closed tickets and reverted PRs with similar error messages but quite frankly I don't know enough to know if they are related. There's mention of custom resources but I don't believe I'm using custom resources.

CDK CLI Version

2.124.0

Framework Version

No response

Node.js Version

v18

OS

Linux

Language

TypeScript

Language Version

5.3.3

Other information

No response

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[ekeyser]

fixed by actually specifying LogGroupName