add support for multiple regions

[ravinaik1312]

What does this PR do?

This PR adds support for deploying functionbeat in multiple regions.

Why is it important?

Teams can deploy the functionbeat in multiple regions and

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes [Functionbeat][Lambda] Support multiple regions #16935

Use cases

Screenshots

Logs

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[ravinaik1312]

I have added this change because, as we're appending the function name to the role name, the role name would exceed AWS's limit of 64 characters. I can change the implementation based on the feedback from the maintainers. Other alternative is to add a conditional for creating the role.

Either ways, the 140 character limit for the function name needs to be reduced as we're already appending the function name in the role name.

[kvch]

This is a good point. However, I am bit worried if we change the role name, we might forgot to change this number. Do you mind refactoring it so the length of the pattern depends on the role name prefix? Or at least add a comment to the code about why the max length is 29?

[ravinaik1312]

I was off by one on the limit, it can be 30 instead of 29. I've updated the regex, tests and added a comment on how I got to the number 30.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: kvch commented: jenkins run tests

• Start Time: 2021-01-11T15:27:43.603+0000

• Duration: 24 min 44 sec

Test stats 🧪

Test	Results
Failed	0
Passed	314
Skipped	4
Total	318

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	314
Skipped	4
Total	318

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[elasticmachine]

Pinging @elastic/integrations-services (Team:Services)

[ravinaik1312]

@ph thank you for self-requesting review, let me know if the changes makes sense, happy to discuss alternatives too!

[ph]

@kvch can you give a second pair of eye on this. I think this looks ok, I am a bit worried about the new limit and the impact on existing deployment?

[kvch]

jenkins run tests

[kvch]

Thank you!