Peter Woodworth

Yeah, this is pretty hardcoded in. Any workarounds to this would be quite a hassle https://github.com/aws/aws-cdk/blob/1d3883a32fd05878ac43d6e236f5b446096f3ed3/packages/%40aws-cdk/aws-events-targets/lib/log-group.ts#L31-L59 I will mark this as a feature request. Thanks for submitting this issue

I am marking this issue as p2, which means that we are unable to work on this immediately. We use +1s to help prioritize our work, and are happy to...

I can reproduce this, thanks for reporting! This is an issue with CloudFormation, I'll submit a ticket to them to see what they say

There's a feature request up internally for this. I don't have an ETA, but it's been supposedly coming soon for a little bit now so hopefully i'll have good news...

The error CloudFormation is throwing here isn't helpful in determining what's actually wrong with the template, so it's hard to say if there's an actual error here. What I think...

It's possible these are separate issues. I'm unable to deploy just a minimal responseheaderspolicy with just a name. I'm reporting to cloudformation to implement better error handling

This _should_ be correct according to AL2022 docs https://docs.aws.amazon.com/linux/al2022/ug/get-started.html#launch-from-cloudformation However, you can see [here](https://docs.aws.amazon.com/linux/al2022/ug/naming-and-versioning.html) that as you say, it's been updated to 5.15 We can fix this pretty easily, all...

Thanks for the contribution @tomfa! We should be able to take a look soon

Hey @nsaman, how exactly are you going about this in your code? Are you making use of the [LambdaInvoke](https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-stepfunctions-tasks.LambdaInvoke.html) construct?

What exactly do you mean by this @nsaman? A snippet of the relevant parts of your code would be helpful