(aws-codepipelines-actions): Cannot set region on LambdaInvokeAction

[jhoscar1]

What is the problem?

LambdaInvokeAction does not accept region as a parameter. I have a CodePipeline that needs to invoke a function in a different region. I was hitting errors due to the LambdaInvokeAction assuming the region is the same as the CodePipeline, but it worked when I manually set the region in the action configuration in the AWS console. According to the documentation this property can be defined in Cloudformation so it’s not clear why it’s not supported in CDK. I noticed that LambdaInvokeActionProps extends the CommonActionProps interface rather than the ActionProperties interface which does include the region field.

Reproduction Steps

Created a Codepipeline stack in us-west-2 with a stage containing a LambdaInvokeAction that needed to invoke a function in us-east-1.

What did you expect to happen?

I expected to be able to define the region for the action to invoke the lambda.

What actually happened?

The action had a region of us-west-2 and I could only change the region manually in the console.

CDK CLI Version

1.108.0

Framework Version

No response

Node.js Version

14.16.1

OS

Mac OS Big Sur (11.6)

Language

Typescript

Language Version

4.5.2

Other information

No response

[ryparker]

PR: #18229

[skinny85]

Thanks for opening the issue @jhoscar1. Can you show the CDK code you are using to create your Lambda invoke CodePipeline Action?

Thanks,
Adam

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[jhoscar1]

@skinny85 will post when back at work on Monday. Commenting to prevent auto close

[jhoscar1]

Here's a simplified version of the code we're running to create the action:

export class CodePipelineStack extends cdk.Stack {
  public readonly devPipelineOutput: cdk.CfnOutput;
​
  constructor(scope: cdk.Construct, id: string, props: CodePipelineStackProps) {
    super(scope, id, props);
​
    const appNameLambda = lambda.Function.fromFunctionAttributes(this, "AppNameLambda", {
      functionArn: cdk.Arn.format(
        { service: "lambda", resource: "function:AppName", account: "[**DIFFERENT ACCOUNT THAN PIPELINE**]" },
        cdk.Stack.of(this)
      ),
    });
​
    const lambdaInvokeAction = new codepipeline_actions.LambdaInvokeAction({
      actionName: "AppNameInvoke",
      lambda: appNameLambda,
      userParameters: {
        param1: "value",
      },
      role: iam.Role.fromRoleArn(
        this,
        "crossAccountRole",
        "arn:aws:iam::[**SAME ACCOUNT AS LAMBDA**]:role/app-name-cross-account-invoke"
      ),
    });
​
    const devPipeline = new codepipeline.Pipeline(this, "DevPipeline", {
      stages: [
        {
          stageName: "FetchDynamicValues",
          actions: [lambdaInvokeAction],
        },
      ],
    });
​
    this.devPipelineOutput = new cdk.CfnOutput(this, "DevPipelineOutput", {
      value: devPipeline.pipelineName,
    });
  }
}

[skinny85]

Yep, I see the problem. We need to pass the region from the ARN here.

I'll prepare a PR fixing this.

[github-actions]

⚠️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.