# Functionbeat deployment to s3 bucket fails **URL:** \ **Category:** Beats\ **Tags:** functionbeat\ **Created:** [September 10, 2020, 6:10am UTC](https://discuss.elastic.co/t/functionbeat-deployment-to-s3-bucket-fails/248111 "2020-09-10T06:10:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kristofvb](https://avatars.discourse-cdn.com/v4/letter/k/51bf81/32.png) [@kristofvb](https://discuss.elastic.co/u/kristofvb)\ **Post date:** [September 10, 2020, 6:10am UTC](https://discuss.elastic.co/t/functionbeat-deployment-to-s3-bucket-fails/248111/1 "2020-09-10T06:10:11Z")
It looks like the issue reported in [Unable to deploy functionbeat to s3 bucket](https://discuss.elastic.co/t/unable-to-deploy-functionbeat-to-s3-bucket/171371) and [Function could not deploy, error: bucket 'abc' already exist and you don't have permission to access it](https://discuss.elastic.co/t/function-could-not-deploy-error-bucket-abc-already-exist-and-you-dont-have-permission-to-access-it/184467) is still not solved in functionbeat 7.9.1. Is it planned to be fixed in some upcoming release? Or is there any other way to work around this bug (other than using the provider deploy functionality)? ---
**Author:** ![kristofvb](https://avatars.discourse-cdn.com/v4/letter/k/51bf81/32.png) [@kristofvb](https://discuss.elastic.co/u/kristofvb)\ **Post date:** [September 14, 2020, 12:02pm UTC](https://discuss.elastic.co/t/functionbeat-deployment-to-s3-bucket-fails/248111/2 "2020-09-14T12:02:22Z")
Please ignore. Turns out I didn't have the right permissions as required to deploy functionbeat. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 12, 2020, 2:02pm UTC](https://discuss.elastic.co/t/functionbeat-deployment-to-s3-bucket-fails/248111/3 "2020-10-12T14:02:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.