Functionbeat: Do a better job to handle multi region deployment

[ph]

This was found when working with @dedemorton on the documentation.

--

She created the lambda to watch in the ohio region and pushed the cloudformation template in another region. And we were not able to provide good feedback for that, and the debugging was a bit cumbersome. Also, the only way to define the region is to use environment variables before executing the deploy command.

We should look into the following:

• So maybe we should consider adding an option to the function to define where it should be pushed.

• Indicate on the CLI where we are pushing the lambda.

The issue #8912 will help to provide better errors when we hit a problem with cloudformation but I think we need to look more deeply at the problem.

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[ph]

@jlind23 @nimarezainia I believe this can be close, with the other way to ingest from lambda I don't think we want to allocate time on this.