# Share your #ElasticStories **URL:** \ **Category:** Elastic Community and Ecosystem\ **Created:** [June 20, 2019, 7:26am UTC](https://discuss.elastic.co/t/share-your-elasticstories/186614 "2019-06-20T07:26:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![livdec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/livdec/32/48419_2.png) [@livdec](https://discuss.elastic.co/u/livdec)\ **Post date:** [June 20, 2019, 7:26am UTC](https://discuss.elastic.co/t/share-your-elasticstories/186614/1 "2019-06-20T07:26:44Z")
Heya Elastic community! We’re constantly amazed by the innovation and imagination our community displays with the Elastic Stack. We’ve seen use cases that we couldn’t have imagined. We showcase them on our [blog](https://www.elastic.co/blog/category/user-stories), [customer page](https://www.elastic.co/use-cases/), and at our [Elastic{ON} Tour](https://www.elastic.co/elasticon/) and [community events](https://www.elastic.co/community/). We do this because sharing these stories exposes new and unimaginable possibilities of what can be accomplished with the Elastic Stack. It’s true, knowledge is power. But a ton of awesome work engineered with the [Elastic Stack](https://www.elastic.co/products/) by our wonderful community of users is going unnoticed by us and our community at large which is what we’d like to change. The [#ElasticStories](https://twitter.com/search?q=%23elasticstories&src=typd) hashtag is an unfiltered venue to share Elastic Stack stories on Twitter regardless of simplicity or complexity. Whether it is a [machine learning](https://www.elastic.co/products/stack/machine-learning), [Logstash](https://www.elastic.co/products/logstash) or [Canvas](https://www.elastic.co/products/stack/canvas) story. An [application search](https://www.elastic.co/solutions/app-search) or [security use case](https://www.elastic.co/solutions/security-analytics) or some insight into how you've implemented [maps](https://www.elastic.co/elastic-maps-service), [cross-cluster replication](https://www.elastic.co/blog/follow-the-leader-an-introduction-to-cross-cluster-replication-in-elasticsearch), or [APM](https://www.elastic.co/solutions/apm). We’d love to hear your Elastic stories! We will retweet some of these astounding #ElasticStories tweets on our [@Elastic](https://twitter.com/elastic) account. What’s more, we plan on featuring select #ElasticStories tweets on the [Elastic blog](https://www.elastic.co/blog/category/user-stories) and in our [Community newsletter](https://www.elastic.co/community/newsletter). If we find a story that is super inspiring, we might post a writeup — by us or perhaps by you — on our website. Read the full blog for further information [here](https://www.elastic.co/blog/share-your-elasticstories). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 20, 2019, 9:33am UTC](https://discuss.elastic.co/t/share-your-elasticstories/186614/2 "2019-06-20T09:33:59Z")
---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 20, 2019, 9:45am UTC](https://discuss.elastic.co/t/share-your-elasticstories/186614/3 "2019-06-20T09:45:58Z")
---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 7:13am UTC](https://discuss.elastic.co/t/share-your-elasticstories/186614/4 "2022-11-04T07:13:06Z")