# Securing connection between Beats and Elastic Cloud
**URL:** https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274
**Category:** Beats
**Tags:** filebeat
**Created:** [July 21, 2021, 2:02pm UTC](https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274 "2021-07-21T14:02:57Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@mi\_uber\_alles](https://discuss.elastic.co/u/mi_uber_alles)
#### Post date: [July 21, 2021, 2:02pm UTC](https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274/1 "2021-07-21T14:02:57Z")
Hi All,
Recently started using Elastic Cloud and it works fine. I have a Filebeat instance in a private network and it sends data to my deployment through the Internet. My question is, is there any way to make this dataflow encrypted? I haven't found anything in the docs or blogs about it. Adding TLS to the `output.elasticsearch` section is well-documented, but if you've added the `cloud.id` option, it all gets skipped, so I'm guessing it's not the solution I seek.
My other guess is that it is encrypted and secure by default, but I couldn't find a confirmation for that.
Can someone please explain me how does it work?
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [July 22, 2021, 10:53am UTC](https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274/2 "2021-07-22T10:53:16Z")
You are right: `cloud.id` is a `https` connection and it's encrypted by default
---
### Author:  [@mi\_uber\_alles](https://discuss.elastic.co/u/mi_uber_alles)
#### Post date: [July 22, 2021, 12:43pm UTC](https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274/3 "2021-07-22T12:43:03Z")
Thank you @Mario_Castro !
Is there any more detailed description of this available other than [this one](https://www.elastic.co/guide/en/cloud/current/ec-cloud-id.html)?
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [July 26, 2021, 8:58pm UTC](https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274/4 "2021-07-26T20:58:10Z")
I'm afraid that no, sorry 😅 I mean if you want to access without using `cloud.id` you do it using `https`, Elastic Cloud won't provide you a `http` url. It would not make sense that if you access using `cloud.id` it's not encrypted then (but I checked the code just to be sure 😄 )
---
### Author:  [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)
#### Post date: [July 27, 2021, 1:25am UTC](https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274/5 "2021-07-27T01:25:48Z")
@mi_uber_alles if u base64 decide the cloud.id, you'll get the connection information including the https url for elasticsearch.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 24, 2021, 3:26am UTC](https://discuss.elastic.co/t/securing-connection-between-beats-and-elastic-cloud/279274/6 "2021-08-24T03:26:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.