# Other deployment options for functionbeat
**URL:** https://discuss.elastic.co/t/other-deployment-options-for-functionbeat/282696
**Category:** Beats
**Tags:** functionbeat
**Created:** [August 27, 2021, 5:16pm UTC](https://discuss.elastic.co/t/other-deployment-options-for-functionbeat/282696 "2021-08-27T17:16:28Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mohsen0](https://discuss.elastic.co/u/mohsen0)
#### Post date: [August 27, 2021, 5:16pm UTC](https://discuss.elastic.co/t/other-deployment-options-for-functionbeat/282696/1 "2021-08-27T17:16:28Z")
Hi
The current deployment method of functionbeat, doesn't support adding AWS resource tags for different deployments.
I saw [Pass AWS tags to resources created by Functionbeat](https://discuss.elastic.co/t/pass-aws-tags-to-resources-created-by-functionbeat/240575)
which went unanswered.
Currently, deployment using the CLI creates a bucket and deploys a cloud formation stack is not again scalable.
if One organization operates on multiple AWS regions, the bucket for logs will be on each region, and there are use cases that not all logs will go into one or two buckets.
it would be nice to have a terraform module to deploy functionbeat which solves many of these problems.
but I am not sure how the ZIP file used by lambda was constructed. I can see CLI removes it from the bucket after cloudformation deployment.
[beats/cli\_manager.go at master · elastic/beats · GitHub](https://github.com/elastic/beats/blob/master/x-pack/functionbeat/manager/aws/cli_manager.go#L112)
do you have any suggestions to add AWS tags to resources? and
make this more scalable for many buckets(running CLI command to install or upgrade is not very ideal)?
Thanks
Mohsen
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 24, 2021, 7:17pm UTC](https://discuss.elastic.co/t/other-deployment-options-for-functionbeat/282696/2 "2021-09-24T19:17:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.