Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(constructs): fix log group name bug for step functions #166

Merged
merged 4 commits into from
Dec 15, 2023

Conversation

krokoko
Copy link
Collaborator

@krokoko krokoko commented Dec 15, 2023

When tearing down/re-deploying a stack using the constructs, the user can face an issue where

"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: ccf12a8e-30f5-4cc5-a4a2-627850477782; Proxy: null)" (RequestToken: 1a8e1d6a-162b-df56-7e6c-b04d222b7765, HandlerErrorCode: InvalidRequest)". 

This is related to an issue in IH where a log delivery policy is created (AWSLogDeliveryWrite*) and data are cumulated without being properly cleared. One way to workaround the issue is to prefix the name of the log group however that api is not exposed yet through CDK.

There is a great solution proposed by @biffgaut and implemented in the aws-solutions-constructs which we replicate here.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

@krokoko krokoko marked this pull request as ready for review December 15, 2023 01:27
@krokoko krokoko requested a review from a team as a code owner December 15, 2023 01:27
@krokoko krokoko merged commit d8b3cca into awslabs:main Dec 15, 2023
17 checks passed
@krokoko krokoko deleted the fix/step_fn_logs branch December 15, 2023 01:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants