Leverage native Provisioned Concurrency

[devasur]

As we know AWS has announced a native Keep Warm routine using Provisioned Concurrency - supported through console as well as config. Serverless also has added Yaml support for this feature.

However they fall short in terms of flexible configuration options - such as the ability to control concurrency per schedules.

Since this plugin is flexible can we modify it to leverage the provisionedConcurrency while keeping all the flexibility it offers in scheduling?

  const params = {
    FunctionName: 'MyFunctionName',
    ProvisionedConcurrentExecutions: '5'
  };
  const lambda = new AWS
  lambda.putProvisionedConcurrency(params, function(err, data) {
    if (err) console.log(err, err.stack); // an error occurred
    else     console.log(data);           // successful response
  });
};
`

[juanjoDiaz]

Hi @devasur,
Sorry for the long silence.

I guess that you mean adding that putProvisionedConcurrency to the generated warmup lambda. However, that would be the same as just setting it all the time since at any time we'll be removing the provisioned concurrency. A smarter strategy is needed here.

[khaledosman]

I tried commenting out this plugin usage in favor of provisionedConcurrency however I could see in the serverless dashboard that my functions were still having coldstarts.

I can't tell why, but I don't think provisionedConcurrency via serverless is as reliable so I'm reverting to using this plugin again.