AWS Elasticsearch v/s Elasticsearch on EC2 Comparison

  • Automatically replaces failed nodes
  • Add/remove nodes through an API
  • Manage access rights via IAM
  • Daily snapshots to S3 are included
  • CloudWatch monitoring included
  • On demand equivalent instances are cheaper by ~29%
  • Change more index settings
  • Change more cluster-wide settings
  • Access to all other APIs such as Hot Threads, which is useful for debugging
  • Supports Clusters of more than 20 nodes if required
  • Supports a more comprehensive Elasticsearch monitoring solution
  • m4.large instance, AWS ElasticSearch is 0.151/hr USD for on demand while EC2 is $0.10/hr USD.
  • AWS Elasticsearch service charges $0.135/gb/month for gp2 storage while with EC2 it is $0.10/gb/month.
  • Data-store < 1 TB
  • Small cluster size
  • Low Scaling requirement

--

--

--

Entrepreneur, Programmer, Cricketer, Farmer

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Logstash — Unstructured Multiple Log Lines as one Structured Record

The Manifesto Part 2

Understanding why AWS t2 instances are cheap and their limitations (CPU credit balance)

How to Review Code Like a Seasoned Professional

Fixing Github’s Password Authentication Support Issue with Tokens

Separate keymap repo for QMK

Announcing the Hazelcast Heroes Program

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Parvinder Singh

Parvinder Singh

Entrepreneur, Programmer, Cricketer, Farmer

More from Medium

Sending MongoDB Atlas logs to Logz.io

Collect, parse and store SSO events from CloudTrail using Lambda and S3 bucket — Part 2

Terraform 101 — Part 1/4: History, Workflow and Resource Addressing

AWS Database Authentication with IAM