# Channeling from amazon S3 to ES - speed **URL:** \ **Category:** Elasticsearch\ **Created:** [July 5, 2016, 11:36am UTC](https://discuss.elastic.co/t/channeling-from-amazon-s3-to-es-speed/54725 "2016-07-05T11:36:31Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![lifesthateasy](https://avatars.discourse-cdn.com/v4/letter/l/7993a0/32.png) [@lifesthateasy](https://discuss.elastic.co/u/lifesthateasy)\ **Post date:** [July 5, 2016, 11:36am UTC](https://discuss.elastic.co/t/channeling-from-amazon-s3-to-es-speed/54725/1 "2016-07-05T11:36:31Z")
Hello! I'm currently hosting data on an Amazon S3, and am wondering, which one would be the faster, more efficient solution to get my data to Elasticsearch: Channeling through Amazon's Lambda, or with Logstash? Are there any pros/cons for each option? Thank you! ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [July 5, 2016, 12:39pm UTC](https://discuss.elastic.co/t/channeling-from-amazon-s3-to-es-speed/54725/2 "2016-07-05T12:39:11Z")
Hi @lifesthateasy, without knowing too much about your data or anything else in your setup: This depends on so many factors and guessing won't really help you. I suggest you build a concrete (but maybe stripped down) version of each ingestion pipeline and take real measurements. An obvious disadvantage of Lamba is that this is a proprietary product whereas Logstash is open source (disclaimer: I work for Elastic which also sponsors Logstash development). Daniel ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:38pm UTC](https://discuss.elastic.co/t/channeling-from-amazon-s3-to-es-speed/54725/3 "2017-07-05T22:38:00Z")