# ELK on AWS Fargate

**URL:** <https://discuss.elastic.co/t/elk-on-aws-fargate/153967>\
**Category:** Elasticsearch\
**Created:** [October 25, 2018, 10:28am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967 "2018-10-25T10:28:37Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![musabqamri](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@musabqamri](https://discuss.elastic.co/u/musabqamri)\
**Post date:** [October 25, 2018, 10:28am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/1 "2018-10-25T10:28:37Z")

</div>

is it possible to deploy elk on aws ecs with fargate as launch type not ec2 ?

how would be the node discovery ?

we have discovery plugin for ec2 .. similarly do we have something for fargate ?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 25, 2018, 6:03pm UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/3 "2018-10-25T18:03:04Z")

</div>

AWS tell me that it's possible but I haven't actually tried it, and discovery (and more generally networking) would be one of the obstacles that I'd expect to have to overcome. There is no discovery plugin specifically for Fargate but the `discovery-file` plugin is quite a flexible way to do dynamic discovery so I'd suggest trying that on the dedicated master nodes. Once you've got the master nodes to discover each other, I would try to use Fargate's own DNS-based service discovery to get the data nodes to discover the masters.

Please do let us know how you get on and if you get stuck maybe we can help.

---

<div class="post-metadata">

**Author:** ![musabqamri](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@musabqamri](https://discuss.elastic.co/u/musabqamri)\
**Post date:** [October 26, 2018, 6:31am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/4 "2018-10-26T06:31:44Z")

</div>

Getting this error,

[3]: max virtual memory areas vm.max\_map\_count [65530] is too low, increase to at least [262144]

is there a way to fix it using fargate ?  
[https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-cli-run-prod-mode](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-cli-run-prod-mode) solution provided here needs host which i think is not there on fargate

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 26, 2018, 10:17am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/5 "2018-10-26T10:17:42Z")

</div>

I do not know if this is possible to change in Fargate itself - you will need to seek AWS's help with that. However it looks like in 6.5.0 you will be able to disable `mmapfs` and avoid the corresponding bootstrap check:

> <https://github.com/elastic/elasticsearch/pull/32421>

---

<div class="post-metadata">

**Author:** ![musabqamri](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@musabqamri](https://discuss.elastic.co/u/musabqamri)\
**Post date:** [October 26, 2018, 10:51am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/6 "2018-10-26T10:51:55Z")

</div>

i think 6.5.0 docker image is not yet published [https://www.docker.elastic.co/](https://www.docker.elastic.co/)

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 26, 2018, 11:02am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/7 "2018-10-26T11:02:36Z")

</div>

Yes, 6.5.0 is not yet released.

---

<div class="post-metadata">

**Author:** ![musabqamri](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@musabqamri](https://discuss.elastic.co/u/musabqamri)\
**Post date:** [October 26, 2018, 11:05am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/8 "2018-10-26T11:05:37Z")

</div>

any idea when it will get released ?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 27, 2018, 3:51pm UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/9 "2018-10-27T15:51:21Z")

</div>

The latest release today is 6.4.2 so 6.5.0 will be the the next minor version released, but we unfortunately cannot say when this will happen yet.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [November 15, 2018, 8:42am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/10 "2018-11-15T08:42:31Z")

</div>

@musabqamri just to let you know that [6.5.0 is now released](https://www.elastic.co/blog/elastic-stack-6-5-0-released?elektra=products&storm=main).

---

<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:** [December 13, 2018, 8:42am UTC](https://discuss.elastic.co/t/elk-on-aws-fargate/153967/11 "2018-12-13T08:42:37Z")

</div>

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