# Exporting logs to elasticsearch on kubernetes/aws: functionbeat - Cannot retrieve license

**URL:** https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039
**Category:** Beats
**Tags:** functionbeat
**Created:** [January 28, 2019, 7:33pm UTC](https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039 "2019-01-28T19:33:44Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![GAHila](https://avatars.discourse-cdn.com/v4/letter/g/f14d63/32.png) [@GAHila](https://discuss.elastic.co/u/GAHila)
#### Post date: [January 28, 2019, 7:33pm UTC](https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039/1 "2019-01-28T19:33:44Z")

</div>

I have kubernetes running on AWS (EKS) (v.6.3.2 from containers in GCP) and dedicated nodes that run Elasticsearch.

So we want to export Cloudwatch logs there given we have kibana and everything else goes there.

Installed functionbeat and configured the lambda to run within the vpc and it appears that we can contact ES (which internally to VPC has no credentials configured - access is managed by acls) and yet I get the following error. Not sure why it is trying xpack and if there is anyway to disable it. The configuration reference says already that Xpack monitoring is disabled by default. I don't think we have xpack at all installed with ES.

Any idea what could be wrong

> 2019-01-28T18:44:50.849Z DEBUG [elasticsearch] elasticsearch/client.go:689 ES Ping(url=[https://elasticsearch.domain.com:443](https://elasticsearch.domain.com:443))  
> 2019-01-28T18:44:50.857Z DEBUG [elasticsearch] elasticsearch/client.go:712 Ping status code: 200  
> 2019-01-28T18:44:50.857Z INFO elasticsearch/client.go:713 Connected to Elasticsearch version 6.3.2  
> 2019-01-28T18:44:50.857Z DEBUG [elasticsearch] elasticsearch/client.go:731 GET [https://elasticsearch.domain.com:443/\_xpack?human=false](https://elasticsearch.domain.com:443/_xpack?human=false)   
> 2019-01-28T18:44:50.863Z INFO [license-manager] licenser/manager.go:265 Cannot retrieve license, retrying later, error: error from server, response code: 400  
> 2019-01-28T18:44:50.863Z DEBUG [license-manager] licenser/manager.go:274 License is too old, grace time remaining: 44m55.582262758s  
> END RequestId: fdbd99a7-fc75-4810-bcf4-232d6558cc42  
> REPORT RequestId: fdbd99a7-fc75-4810-bcf4-232d6558cc42 Duration: 15012.04 ms Billed Duration: 15000 ms Memory Size: 128 MB Max Memory Used: 62 MB   
> 2019-01-28T18:44:53.969Z fdbd99a7-fc75-4810-bcf4-232d6558cc42 Task timed out after 3.01 seconds

Here is the functionbeat.yml config file:

> functionbeat.provider.aws.deploy\_bucket: "com.domain.functionbeat"
> 
> functionbeat.provider.aws.functions:
> 
> - name: cloudwatch  
> enabled: true  
> type: cloudwatch\_logs
> 
> - name: sqs  
> enabled: false  
> type: sqs
> 
> setup.kibana:
> 
> output.elasticsearch:  
> hosts: ["[https://elasticsearch.domain.com:443](https://elasticsearch.domain.com:443)"]
> 
> processors:
> 
> - add\_host\_metadata: ~
> - add\_cloud\_metadata: ~
> 
> xpack.monitoring.enabled: false
> 
> setup.template.overwrite: true

---

<div class="post-metadata">

### Author: ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)
#### Post date: [January 28, 2019, 7:50pm UTC](https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039/2 "2019-01-28T19:50:16Z")

</div>

> [@GAHila](#):
>
> ady that Xpack monitoring is disabled by default. I don't think we have xpack at all installed with ES.

Hello @GAHila,

You are not doing anything wrong. Currently, Functionbeat requires that the remote endpoint has at least a [basic license](https://www.elastic.co/subscriptions), that license is free and you will get a few more things out of the box from your cluster.

---

<div class="post-metadata">

### Author: ![GAHila](https://avatars.discourse-cdn.com/v4/letter/g/f14d63/32.png) [@GAHila](https://discuss.elastic.co/u/GAHila)
#### Post date: [January 30, 2019, 6:19pm UTC](https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039/4 "2019-01-30T18:19:36Z")

</div>

We got ES 6.5 OSS packages.

I tried to install x-pack and got:

ERROR: X-Pack is not available with the oss distribution; to use X-Pack features use the default distribution

That probably means that with the current version of ES we cannot use functionbeat, right?

---

<div class="post-metadata">

### Author: ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)
#### Post date: [February 7, 2019, 1:04pm UTC](https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039/5 "2019-02-07T13:04:02Z")

</div>

Exactly you will need to install the Elasticsearch non oss packages, I don't think in 6.5 you can install x-pack as a plugin.

---

<div class="post-metadata">

### Author: ![GAHila](https://avatars.discourse-cdn.com/v4/letter/g/f14d63/32.png) [@GAHila](https://discuss.elastic.co/u/GAHila)
#### Post date: [February 15, 2019, 8:48pm UTC](https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039/6 "2019-02-15T20:48:39Z")

</div>

Thank you, it's all clear now!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 15, 2019, 10:48pm UTC](https://discuss.elastic.co/t/exporting-logs-to-elasticsearch-on-kubernetes-aws-functionbeat-cannot-retrieve-license/166039/7 "2019-03-15T22:48:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
