Serverless-application-model: Template error: IAM role stack-Lambda-XXXXX doesn't exist

[yvele]

I have a very strange error when deploying basic Lambda function using SAM.

The strange thing is that it worked this morning and the exact same code fails this afternoon 🤔

Template error: IAM role stack-LambdaFunction-XXXXX doesn't exist

My Lambda is quite basic, I'm in region eu-east-1

AWSTemplateFormatVersion: 2010-09-09
Transform: AWS::Serverless-2016-10-31

Resources:
  LambdaFunction:
    Type: AWS::Serverless::Function
    Properties:
      Handler     : main.handle
      Runtime     : nodejs8.10
      MemorySize  : 2048
      CodeUri     : ./dist

This is strange because we can see that the role has been successfully created just before:

[yvele]

Looks like with the exact same code if we keep trying to deploy it succeeded once.. 🤔

Edit: Oh.. it keeps failing/succeeding randomly

[thomasklinger1234]

Same here.

18:26:22 UTC+0200 | CREATE_FAILED | AWS::Lambda::Function | MyFunction | Template error: IAM role bcm-api-MyFunction-LM95D3GKBBWL doesn't exist
-- | -- | -- | -- | --

Code:

AWSTemplateFormatVersion: 2010-09-09

Transform: "AWS::Serverless-2016-10-31"

Description: |
  https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md

Globals:
  Function:
    Runtime: python3.6
    MemorySize: 128
    Timeout: 10
    CodeUri: .

Resources:
  MyFunction:
    Type: AWS::Serverless::Function
    Properties:
      Handler: index.run
      Description: ""
      Policies:
        - AWSLambdaExecute
        - 
          Version: 2012-10-17
          Statement:
            - 
              Effect: Allow
              Action:
                - "*"
              Resource:
                - "*"

[yvele]

Looks like an AWS internal server error 🤔

[yvele]

Nothing special in https://status.aws.amazon.com/ or in my AWS personal health dashboard

Edit: Twitter https://twitter.com/mryvele/status/1055499725825368064 ?

[th3g3ntl3men]

I am having the same issue as well. It started last night for me.

[keetonian]

We're looking into it. Thank you for posting!

[yvele]

Thanks for the quick response, we will wait for tomorrow for deployment 😉

[th3g3ntl3men]

^ ditto

[yvele]

This just appears in AWS Personal Health Dashboard

IAM operational issue

Increased API Latencies

9:59 AM PDT We are investigating an increased latency on administrative APIs. Create, Delete, List, Get, and Update API actions may be impacted in multiple regions. Other AWS services whose features require IAM roles will also be impacted. User authentications and authorizations are not impacted.

10:40 AM PDT We continue to investigate increased latency on administrative APIs. Create, Delete, List, Get, and Update API actions may be impacted in multiple regions. Other AWS services like AWS CloudFormation and AWS Lambda that use IAM roles may also be impacted. User authentications and authorizations are not impacted.

11:31 AM PDT We have identified the root cause and are working towards a resolution for increased latency on administrative APIs. Create, Delete, List, Get, and Update API actions may be impacted in multiple regions. Other AWS services like AWS CloudFormation and AWS Lambda that use IAM roles may also be impacted. User authentications and authorizations are not impacted.

[yvele]

12:40 PM PDT We are seeing improvement in the latency for administrative APIs (Create, Delete, List, Get, and Update). We are continuing to work towards a full resolution. User authentications and authorizations are not impacted.

12:57 PM PDT Between 08:28 AM and 12:31 PM PDT, we experienced increased latency on administrative APIs. Create, Delete, List, Get, and Update API actions were impacted in multiple regions. User authentications and authorizations were not impacted. The issue has been resolved, and the service is operating normally.

Looks like it has been resolved 😉

[subodhkarwa]

Are we facing a similar issue in the past hour ? (GMT 9.00 am to 10.am )

[omoore28]

I'm seeing this right now... INCREDIBLY frustrating.

Can't deploy any of our stacks with IAM roles. We could previously.