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

I have the same issue.

My template:

{
   "AWSTemplateFormatVersion":"2010-09-09",
   "Transform":"AWS::Serverless-2016-10-31",
   "Description":"An AWS Serverless Application that uses the ASP.NET Core framework running in Amazon Lambda.",
   "Parameters":{
      "ShouldCreateBucket":{
         "Type":"String",
         "AllowedValues":[
            "true",
            "false"
         ],
         "Description":"If true then the S3 bucket that will be proxied will be created with the CloudFormation stack."
      },
      "BucketName":{
         "Type":"String",
         "Description":"Name of S3 bucket that will be proxied. If left blank a name will be generated.",
         "MinLength":"0"
      }
   },
   "Conditions":{
      "CreateS3Bucket":{
         "Fn::Equals":[
            {
               "Ref":"ShouldCreateBucket"
            },
            "true"
         ]
      },
      "BucketNameGenerated":{
         "Fn::Equals":[
            {
               "Ref":"BucketName"
            },
            ""
         ]
      }
   },
   "Resources":{
      "AspNetCoreFunction":{
         "Type":"AWS::Serverless::Function",
         "Properties":{
            "Handler":"xxx::xxx.LambdaEntryPoint::FunctionHandlerAsync",
            "Runtime":"dotnetcore3.1",
            "CodeUri":"s3://xxx/xxx/AspNetCoreFunction-CodeUri-637343401555849743-637343401710605189.zip",
            "MemorySize":256,
            "Timeout":30,
            "Role":null,
            "Policies":[
               "AWSLambdaFullAccess"
            ],
            "Environment":{
               "Variables":{
                  "AppS3Bucket":{
                     "Fn::If":[
                        "CreateS3Bucket",
                        {
                           "Ref":"Bucket"
                        },
                        {
                           "Ref":"BucketName"
                        }
                     ]
                  }
               }
            },
            "Events":{
               "ProxyResource":{
                  "Type":"Api",
                  "Properties":{
                     "Path":"/{proxy+}",
                     "Method":"ANY"
                  }
               },
               "RootResource":{
                  "Type":"Api",
                  "Properties":{
                     "Path":"/",
                     "Method":"ANY"
                  }
               }
            }
         }
      },
      "Bucket":{
         "Type":"AWS::S3::Bucket",
         "Condition":"CreateS3Bucket",
         "Properties":{
            "BucketName":{
               "Fn::If":[
                  "BucketNameGenerated",
                  {
                     "Ref":"AWS::NoValue"
                  },
                  {
                     "Ref":"BucketName"
                  }
               ]
            }
         }
      }
   },
   "Outputs":{
      "ApiURL":{
         "Description":"API endpoint URL for Prod environment",
         "Value":{
            "Fn::Sub":"https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Prod/"
         }
      },
      "S3ProxyBucket":{
         "Value":{
            "Fn::If":[
               "CreateS3Bucket",
               {
                  "Ref":"Bucket"
               },
               {
                  "Ref":"BucketName"
               }
            ]
         }
      }
   }
}

Having the same issue for the last a few hours. It was working yesterday with the same template. The thing is, that's a template deploying a DynamoDB table. No lambdas. I just saw this thread and wanted to say that this may be a more general issue unrelated to lambda

Same for me for a template that is unchanged and was working previously, so this looks like a regression.

I'm facing the same issue too. However, the aws health check dashboard does not show any indicators for service disruptions in us-east-1. https://status.aws.amazon.com/ Is everyone seeing this issue in us-east-1?

An older thread of similar issue which was due to aws service being down. https://github.com/aws/serverless-application-model/issues/793

This seems to be fixed now !

Hi @dalton5,

Good morning.

Per comment from @NithuPMTR, please verify if this works now for you and confirm if this issue could be closed.

Thanks,
Ashish

It works for me now.

Yes it works. You can close. thanks

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

same issue again..

same issue again..

I confirm, same issue when trying to deploy app stack to us-east-1 :/

Can confirm as well

Can confirm as well, same issue

Same issue here

Same issue here
us-east-1

Received malformed response from transform AWS::Serverless-2016-10-31

Deploying to us-east-1

Seeing the same issue.

Same here: us-east-1

Same issue here trying to deploy in us-east

same here :(

same here :( us-east-1 as well

same here :( us-east-1 as well

Same here, in us-east-1 as well

Is this issue only appearing in us-east-1 only or in other regions as well ?

same here, us-east-1

@ashishdhingra ^^^

HI @ashishdhingra Same here facing this issue in us-east-1

same here, us-east-1

also experiencing this issue in us-east-1
working in us-east-2 and us-west-2

Is this issue only appearing in us-east-1 only or in other regions as well ?

I've deployed in sa-east and it worked as well

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

facing the same issue when attempting to update/create SAM stack in N.Virginia.
I wish I found this thread earlier as I've already deleted stack thinking that the problem would be solved by recreating it from scratch(

Same here, us-east-1

same here, us-east-1

same here, us-east-1

yeah me too, us-east-1.

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 here, us-east-1

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.

Same issue US-EAST-1 Trying 2.

Successful US-EAST-2. Hallelujah!

Please let us know when the service is restored

Fixed!

Thanks!