aws-lambda-dotnet: Failed to create CloudFormation change set: Received malformed response

Hi,

When I publish my aws lambda function I have a final error with this:

Uploading to S3. (Bucket: wtbucketlambda Key: WT-serverless-xxxxxx.template) … Progress: 100% Found existing stack: True CloudFormation change set created … Waiting for change set to be reviewed Failed to create CloudFormation change set: Received malformed response from transform AWS::Serverless-2016-10-31 Failed to publish AWS Serverless application

Do you know how can I fix it?

It’s a big issue because I can’t publish my lambda function

Thanks,

My serverless template:

`{ “AWSTemplateFormatVersion” : “2010-09-09”, “Transform” : “AWS::Serverless-2016-10-31”, “Description” : “Starting template for an AWS Serverless Application.”, “Resources” : { “DefaultFunction” : { “Type” : “AWS::Serverless::Function”, “Properties”: { “Handler”: “not_required_for_custom_runtime”, “Runtime”: “provided”, “CodeUri”: “”, “Description”: “Default function”, “MemorySize”: 256, “Timeout”: 30, “Role”: null, “Policies”: [ “AWSLambdaFullAccess”, “AmazonSSMReadOnlyAccess”, “AWSLambdaVPCAccessExecutionRole” ], “Events”: { “ProxyResource”: { “Type”: “Api”, “Properties”: { “Path”: “/{proxy+}”, “Method”: “ANY” } }, “APIWarmingSchedule”: { “Type”: “Schedule”, “Properties”: { “Schedule”: “rate(5 minutes)”, “Input”: “{ "Resource": "WarmingLambda", "Body": "5" }” } } } } } }, “Outputs” : { “ApiURL” : { “Description” : “API endpoint URL for Prod environment”, “Value” : { “Fn::Sub” : “https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Prod/” } }

} }`

My aws lambda tools default json file

{ “region” : “us-east-1”, “profile” : “wetip”, “s3-bucket” : “wtbucketlambda”, “template” : “serverless.template”, “stack-name” : “WT”, “configuration” : “Release”, “framework” : “netcoreapp2.2”, “msbuild-parameters” : “–self-contained true” }

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 3
  • Comments: 44 (2 by maintainers)

Most upvoted comments

Hi All,

The issue is tracked here https://github.com/aws/aws-lambda-dotnet/issues/765. Looks like there is a service outage for us-east-1 region. Service teams are working on it and the issue should be resolved soon.

Thanks, Ashish

Seeing the same issue.

same issue again…

same here 😦

us-east-1 region is experiencing lots of outages at this moment. we can monitor AWS service health dashboard to check current status of outages/operational issues.

and as for an issue to watch for in relation to our problems here - Kinesis operational issue (Amazon Kinesis Data Streams (N. Virginia):

8:05 AM PST: Kinesis is experiencing increased API errors in the US-EAST-1 Region. This is also causing issues with ACM, Amplify Console, API Gateway, AppStream2, AppSync, Athena, Cloudformation, Cloudtrail, CloudWatch, Cognito, Connect, DynamoDB, EventBridge, IoT Services, Lambda, LEX, Managed Blockchain, Resource Groups, SageMaker, Support Console, and Workspaces.

Same issue here trying to deploy in us-east

Same here: us-east-1

Fixed!

Thanks!

Has same issue for last 2 hours in us-east-1.

Error: Failed to create managed resources: Waiter ChangeSetCreateComplete failed: Waiter encountered a terminal failure state

Tried in us-east-2 and it worked.