Can't deploy multiple times in same AWS account/region about elastic-serverless-forwarder HOT 3 CLOSED

hello @jagomsim

this is unluckily a known problem due to a limitation on the underlying cloudformation template we use to publish the forwarder on the aws serverless application repository.

we have two nested application in the main cloudformation template: one for the macro and one for the effective forwarder application.

the macro takes care of parsing the cloudformation parameters (the various ARNs of the inputs etc etc) and transforming the cloudformation template of the forwarder application to include the relevant source events resources and iam policies for the lambda.

the best solution would be to use an ID of the macro generated uniquely and dynamically from a cloud formation function, like we do for the continuing and the replay queues. while this is possible, it's not possible to use as Name of a Fn::Transform the result of a function (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-transform.html), so even if we generate such an ID we could not reference it in the Fn::Transform.

A workaround is to deploy in a different region

from elastic-serverless-forwarder.

Hello @aspacca, thanks for the quick answer!
Then we would look into deploying in a different region.

from elastic-serverless-forwarder.

@jagomsim you can now use the following method to publish multiple ESF lambdas: https://www.elastic.co/guide/en/observability/current/aws-deploy-elastic-serverless-forwarder.html#aws-serverless-forwarder-direct-deploy

from elastic-serverless-forwarder.