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

Adding AWS::Logs::LogGroup Resource caused Malformed transform error. #1833

Closed
hollsteinm opened this issue Nov 25, 2020 · 1 comment
Closed

Comments

@hollsteinm
Copy link

hollsteinm commented Nov 25, 2020

As part of a process of cutting costs due to a needless infinite retention of CloudWatch logs, I attempted to add log group resources to add a one week expiration. I followed the steps and warnings in the linked issue comment without success. I also encountered this in another project, that just had the serverless transform by mistake, once I removed it, that cloudformation template worked fine. I currently reverted the changes in this public repo so that the transform would be successful:

https://github.com/TrollPursePublishing/aws-codepipeline-custom-action

That should work as a way to see how to reproduce the issue, as well as the below. As a note, I am also validating the template in a seperate build project using cfn-lint, cloudformation validate, and cfn_nag. I am validating both the project template and the packaged template output.

Steps to reproduce the issue:

  1. Create a AWS::Serverless::Function resource with a name
  2. Create a AWS::Logs::LogGroup resource with the name as !Sub "/aws/lambda/${YOUR_LAMBDA_RESOURCE}"
  3. Deploy the cloudformation template

Observed result:
The stack fails withReceived malformed response from transform AWS::Serverless-2016-10-31

Expected result:
The stack transforms successfully and creates LogGroups for the Lambda functions.

@hollsteinm
Copy link
Author

Closing issue because it looks like us-east-1 is having health issues in AWS that are related to Kinesis but also impacting this transform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant