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” }

[ashishdhingra]

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

[itshari]

Seeing the same issue.