(lambda): Not able to provision concurrency for the current version of a lambda

[tmhung88]

Not able to provision concurrency for the current version of a lambda

Reproduction Steps

I have a simple stack below to configure provisioned concurrency for a lambda

export class LambdaAutoScalingStack extends cdk.Stack {
    constructor(scope: cdk.App, id: string) {
        super(scope, id);

        new lambda.Function(this, 'lambda1', {
            code: new lambda.InlineCode('exports.handler = async () => { console.log(\'hello world\'); };'),
            handler: 'index.handler',
            runtime: lambda.Runtime.NODEJS_10_X,
            currentVersionOptions: {
                provisionedConcurrentExecutions: 3
            }
        })

    }
}

What did you expect to happen?

The lambda should have concurrency provisioned as 3

What actually happened?

No concurrency was provisioned

Environment

• CDK CLI Version : 1.94.1
• Framework Version: 1.94.1
• Node.js Version: v14.15.4
• OS : Windows
• Language (Version): TypeScript (3.9.7)

---

This is 🐛 Bug Report

[nija-at]

Hi @tmhung88 -

Can you check what the CloudFormation template contains against the resource type AWS::Lambda::Version?
It should contain the ProvisionedConcurrencyConfig section.

If that is present, you can also run the get-provisioned-concurrency-config from the CLI and check whether that's configured.

Could you try these out and report back?

[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.

[tmhung88]

Will set aside some time tomorrow to try again.

[tmhung88]

@nija-at I don't see any ProvisionedConcurrencyConfig, or Lambda version in the the template.json.

Attached the template json
tmh-provisioned-lambda-stack.template.json.txt

[nija-at]

Hi @tmhung88 -

currentVersionOptions take effect only when the currentVersion getter is called.

You will need to modify your code as -

const fn = new lambda.Function(...);
fn.currentVersion;

The last line actually creates the currentVersion.

[tmhung88]

Hi @tmhung88 -

currentVersionOptions take effect only when the currentVersion getter is called.

You will need to modify your code as -

const fn = new lambda.Function(...);
fn.currentVersion;

The last line actually creates the currentVersion.

Thanks. I confirm the provision is done when fn.currentVersion is called.

// The getter call is quite unexpected. It'd be great if the constructor lambdas.Function invokes this getter, or hide this detail from developers.

[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.

[ffxsam]

@rix0rrr Are there any plans to fix this issue?