#6240 made lambda execution role names longer, violating maxlength constraint

[russell-dot-js]

This is a Bug Report

Description

• What went wrong?
  Fix IAM policies setup for functions with custom name #6240 made the IAM role names longer by appending "lambdaRole" to the end, violating the length constraint

• What did you expect should have happened?
  IAM role names should be in same format

• What was the config you used?
  Minimal serverless.yml below:

service:
  name: hello-i-am-borke-service

frameworkVersion: '>=1.1.0 <2.0.0'

provider:
  name: aws
  runtime: nodejs8.10

  iamRoleStatements:
    # lambda
    - Effect: Allow
      Action:
        - lambda:InvokeFunction
      Resource:
        - "*"
    
functions:
  borken:
    handler: src/handlers/borken.handle
    timeout: 30
    iamRoleStatementsInherit: true
    iamRoleStatements:
        # sf
        - Effect: "Allow"
          Action:
            - "states:StartExecution"
          Resource:
            - "*"

plugins:
  - serverless-iam-roles-per-function

Run with sls deploy --stage=staging or --stage=production to repro

• What stacktrace or error message from your provider did you see?
  Member must have length less than or equal to 64 (Service: AmazonIdentityManagement; Status Code: 400; Error Code: ValidationError; Request ID: ...).

• Related to:
  BREAKING - [1.3.0] IAM role name is to long if service + stage is more than 37 characters #2856

Additional Data

• framework version >= 1.45.1

[keith-pappyflapps]

Had same issue, had to roll back to 1.38 to resolve

[medikoo]

@russell-dot-js afaik #6240 didn't change anything in how IAM role is named. Also lambdaRole postfix is appended for years already.

Can you share the difference between generated CF stacks that exposes the issue you're describing?