# On ElasticCloud hosted ElasticSearch, 'bucket \ already exist and you don't have permission to access it' **URL:** \ **Category:** Beats\ **Tags:** functionbeat\ **Created:** [June 27, 2019, 6:17pm UTC](https://discuss.elastic.co/t/on-elasticcloud-hosted-elasticsearch-bucket-xxx-already-exist-and-you-dont-have-permission-to-access-it/187899 "2019-06-27T18:17:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Mike\_Zmuda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mike_zmuda/32/48959_2.png) [@Mike\_Zmuda](https://discuss.elastic.co/u/Mike_Zmuda)\ **Post date:** [June 27, 2019, 6:17pm UTC](https://discuss.elastic.co/t/on-elasticcloud-hosted-elasticsearch-bucket-xxx-already-exist-and-you-dont-have-permission-to-access-it/187899/1 "2019-06-27T18:17:42Z")
When attempting to deploy a SQS function with functionbeat, I get the following error: 'Function: sqs, could not deploy, error: bucket 'mybucket' already exist and you don't have permission to access it' Using the AWS CLI I have confirmed I can access this bucket and send files to it. functionbeat.yml: functionbeat.provider.aws.deploy\_bucket: "mybucket" functionbeat.provider.aws.functions: - name: sqs enabled: true type: sqs description: "lambda function for SQS events" triggers: - event\_source\_arn: myarn setup.template.settings: index.number\_of\_shards: 1 setup.kibana: cloud.id: "mycloudid" cloud.auth: "myuser:mypw" output.elasticsearch: hosts: ["localhost:9200"] processors: - add\_host\_metadata: ~ - add\_cloud\_metadata: ~ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 18, 2019, 8:17am UTC](https://discuss.elastic.co/t/on-elasticcloud-hosted-elasticsearch-bucket-xxx-already-exist-and-you-dont-have-permission-to-access-it/187899/2 "2019-07-18T08:17:44Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.