# Is the S3 Gateway Technically Insufficient **URL:** \ **Category:** Elasticsearch\ **Created:** [February 26, 2013, 2:48pm UTC](https://discuss.elastic.co/t/is-the-s3-gateway-technically-insufficient/10907 "2013-02-26T14:48:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![James\_Cook\_3](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@James\_Cook\_3](https://discuss.elastic.co/u/James_Cook_3)\ **Post date:** [February 26, 2013, 2:48pm UTC](https://discuss.elastic.co/t/is-the-s3-gateway-technically-insufficient/10907/1 "2013-02-26T14:48:28Z")
We have been running several production sites using ES as our primary data store on EC2 and using the S3 gateway for full cluster backup and recovery. The deprecation of S3 and the local storage direction does not work for us. We run EC2 instances with no (miniscule) local FS, high memory and high IO. The reason EBS does not work for us is because we let Amazon Elastic Beanstalk control the creation/destruction of all our instances based on cluster load. We do not manage EBS instances. The S3 gateway has been working perfectly for us, so I ask, _why deprecate the shared gateway solutions_? Are their technical problems with their implementations? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [February 26, 2013, 3:41pm UTC](https://discuss.elastic.co/t/is-the-s3-gateway-technically-insufficient/10907/2 "2013-02-26T15:41:05Z")
It is explained by kimchy here > Jörg -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![James\_Cook\_3](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@James\_Cook\_3](https://discuss.elastic.co/u/James_Cook_3)\ **Post date:** [February 26, 2013, 4:33pm UTC](https://discuss.elastic.co/t/is-the-s3-gateway-technically-insufficient/10907/3 "2013-02-26T16:33:49Z")
Thanks for the link. I guess my problem is the deprecation of a feature like this because of a use case where performance takes priority over infrastructure. While that may suit many (most?) users of ES, we don't have any issues with the performance of ES when using an S3 gateway, and the convenience of using it as a backup is unrivaled compared to an API. So, there is no technical reason for deprecating the S3 gateway, just that the necessary IO to an external storage system carries with it an implication of performance degradation that may impact some use cases? I'm thankful that the shared gateway should be able to be maintained in a separate project, but isn't the option for an integrated data backup solution that survives cluster shutdown important enough to remain for those use cases where ES is the main source of truth. Perhaps kimchy's assertion that using the shared gateway as a backup solution is a misuse of the feature is what I don't fully understand. We embed ES as our only data persistence into a running web application. We run on EC2 instances which are under the control of Elastic Beanstalk. There are no EBS volumes to snapshot. We use S3 gateway to recover after full cluster shutdowns (version upgrades to our software). I agree that this is an unusual way of using ES as most people deploy ES as a server unto itself, but the advantages it gives us in dynamically shrinking and growing our cluster capacity is unrivaled because everything is self contained in the web app. I can run 1 server or 100 servers with the exact same WAR file deployed, and Amazon decides when to tear down or start up new servers solely by monitoring metrics. It's may seem a bit strange but it is also a beautiful thing to watch. Jim Cook [jcook@pykl.com](mailto:jcook@pykl.com) Pykl Studios [http://pykl.com/](http://pykl.com/) (map) [http://goo.gl/maps/ceMDN](http://goo.gl/maps/ceMDN) 147 N High St Gahanna, OH 43230 phone+1 614 398 3636 tollfree+1 855 FOR PYKL skypejcook.pykl im (gtalk) [jcook@pykl.com](mailto:jcook@pykl.com) On Tue, Feb 26, 2013 at 10:41 AM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > It is explained by kimchy here [https://github.com/](https://github.com/)\*\* > elasticsearch/elasticsearch/\*\*issues/2458[https://github.com/elasticsearch/elasticsearch/issues/2458](https://github.com/elasticsearch/elasticsearch/issues/2458) > > Jörg > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit [https://groups.google.com/d/](https://groups.google.com/d/)\*\* > topic/elasticsearch/G\_\*\*WFPEFf0ZY/unsubscribe?hl=en-US[https://groups.google.com/d/topic/elasticsearch/G\_WFPEFf0ZY/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/G_WFPEFf0ZY/unsubscribe?hl=en-US) > \*\*. > To unsubscribe from this group and all its topics, send an email to > elasticsearch+unsubscribe@\*\*[googlegroups.com](http://googlegroups.com)[elasticsearch%2Bunsubscribe@googlegroups.com](mailto:elasticsearch%2Bunsubscribe@googlegroups.com) > . > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > . -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:49am UTC](https://discuss.elastic.co/t/is-the-s3-gateway-technically-insufficient/10907/4 "2017-07-06T02:49:25Z")