Elasticsearch vs CloudSearch: AWS Cloud Search Choices

Let’s compare AWS-based cloud tools Elasticsearch vs CloudSearch. While both use proven technologies, Elasticsearch is more popular (and open source), and CloudSearch is fully managed.

In part one of this series, we described what search engines are, how they solve the problem of accessing content stretched across large websites, and how Amazon CloudSearch provides a solution for a cloud environment. AWS CloudSearch is certainly a powerful and appealing service from Amazon. However, there are more popular players in the search engine market, and Elasticsearch ranks right behind Solr as the most popular search and analytics engine. We’ll explore the battle of the Amazon search providers: Elasticsearch vs CloudSearch.

Elasticsearch vs CloudSearch: provisioning

Both Elasticsearch and CloudSearch are provided by Amazon as AWS services. However, Elasticsearch is an independent product developed by elastic.co, which means you can set up Elasticsearch independently by downloading and extracting the tar ball, or through a yum/apt-get install.

Amazon CloudSearch, on the other hand, is fully managed by AWS, which, once you choose your instance type, handles the complete provisioning. Users are able to select High-Availability (AZ level), replication, and partitioning options through the AWS Management Console or AWS CLI.

Elasticsearch vs CloudSearch: Upgrading

Elasticsearch is easy to upgrade. The process can be as easy as replacing the lib folder of an older version with a new version.
Updates of Amazon CloudSearch are pushed by AWS, relieving users of the responsibility. However, this might result in delayed upgrades of new releases.

Elasticsearch vs CloudSearch: Data import/export

When existing data need to be searchable, they should be imported to the search engines. In Elasticsearch, there are plugins called “rivers” to push data into a cluster. There are many popular river plugins available such as elasticsearch–river- mongodb, elasticsearch-river-couchdb, Elasticsearch-jdbc. However, for various reasons, river plugins are being deprecated.

Logstash Forwarders, are normally used to push logs from application or database servers to Elasticsearch. This makes them available for searching logs or to plot graphs in Kibana. Recently, Logstash and input_changes plugins have taken center stage to replace rivers as tools to push data to Elasticsearch, too. Some of the recently developed input_changes are couchdb_changes, Twitter, and rabbitmq.

In Amazon CloudSearch, data and documents (in either XML or JSON format) are pushed in batches. Data can also be pushed to S3, with the data path given to index the documents.

Elasticsearch vs CloudSearch: Data and index backup

In Elasticsearch, data is backed up (and restored) using the Snapshot and Restore module. Usually, users are required to define a shared mount path. In the cloud, they can instead opt for Amazon S3, HDFS, or Azure storage. Curator is a tool that acts as a cron job manager that users can set to automate the backup process.

In Amazon CloudSearch, the service itself takes care of the whole backup process, once again sparing users the bother. Unlike Elasticsearch, where users must manually run the restore activity from backed up indexes, CloudSearch does it automatically.

Elasticsearch vs CloudSearch: Security and User Management   

Elasticsearch provides a plugin called shield to handle authentication and authorization. Shield also provides features like encryption, role-based access control, IP filtering, and auditing. However, shield is a licensed product that must be purchased.

You can also integrate your AD server to control access locally.

Amazon CloudSearch provides IAM-based access control.

Elasticsearch vs CloudSearch: Cluster management

In Elasticsearch, adding or deleting nodes within a cluster must be done manually. If the cluster instances are upgraded – i.e. vertical scaling – then you’ll need to run through the setup process from scratch. Old data must be backed up and restored to the new cluster. In the case of horizontal scaling, where servers are added or removed from the cluster, cluster rebalancing and resharding are mandatory. These, too, are manual processes. Users need to be very careful during the process.

Amazon CloudSearch, on the other hand, has built-in scaling and upgrade tools. When a server in a CloudSearch service reaches its threshold, it automatically upgrades to the next larger instance type. And when the capacity goes beyond the largest available instance types, the index is partitioned into multiple instances.

Elasticsearch vs CloudSearch: Monitoring

In Elasticsearch, there are cluster monitoring tools like Marvel which allow a user to send RESTful queries to check cluster health. Another product called Watcher provides an alerting mechanism. These tools are all provided by Elasticsearch itself. Users can, of course, also bring their own monitoring tools, like SPM or the New Relic plugin for Elasticsearch to keep an eye on their clusters.

Amazon CloudSearch is fully integrated with Amazon Cloudwatch, which can monitor metrics like SuccessfulRequests, Searchable Documents, Index Utilization, and Partition Count. Like Watcher in Elasticsearch, AWS Simple Notification Service (SNS) can be integrated with CloudSearch for alerting.

Elasticsearch vs CloudSearch: High Availability

As they’re both built for running search engines in the cloud, Elasticsearch and CloudSearch are designed for high availability.
Elasticsearch is built for distributed computing where the cluster grows horizontally. The indexes are split into shards and replication factors provide shard redundancy. Whenever a node fails, the replicated shards are used to replace lost data.

Elasticsearch employs a technique called zen discovery, where all the nodes communicate with each other through an “elected” master. In case the master node fails, another node takes over as master.

A similar architecture is followed in CloudSearch to handle failure and provide HA. CloudSearch also has an optional feature for multi-AZ replication within a single region to provide HA and Availability Zone failover.

Elasticsearch vs CloudSearch: Search and Indexing

In Elasticsearch, searching happens on both index and types using a search API.  The search API also includes Faceting and Filtering for searching data.

In CloudSearch, users create a search domain which includes sub-services to upload documents. A search service provides the means to search indexed data.

In Elasticsearch, many built-in libraries are provided for analyzers, tokenizers, and filters for indexing.
Amazon CloudSearch, on the other hand, provides a much simpler configuration service for all indexing operations and relevance ranking.

Elasticsearch vs CloudSearch: Client Libraries

There are many clients available for Elasticsearch. Official clients are Java API, .NET, Ruby, Groovy, PHP, PERL, Python, and JavaScript. Elasticsearch also supports RESTful APIs.

Amazon CloudSearch supports many SDKs along with RESTful API calls. The most popular SDKs are in Java, Ruby, Python, .Net, PHP, and Node.js.

Elasticsearch vs CloudSearch: Cost

As Elasticsearch requires manual set up, the true cost of deployment must include infrastructure costs, licensing for all non-open source software tools and the OS, and the Elasticsearch binary. This may require a large operational expenditure to cover skilled Elasticsearch admins and a monitoring team.

Amazon CloudSearch is priced according to the search instance size. Here’s an example:
Elasticsearch vs CloudSearch - instance size
With Multi-AZ enabled, the cost of redundant search instances will also be added. If an index is partitioned, the cost of each new search instance in each AZ is also added to the cost.

CloudSearch document batch uploads

Document batch upload costs are $0.10 per 1,000 Batch Upload Requests (the maximum size for each batch is 5 MB).

CloudSearch IndexDocuments requests

Re-indexing is required for indexes when a new field is added to the index. The charge for a re-indexing request is $0.98 per GB of data stored in your search domain.

CloudSearch data transfer

Inbound data transfers are free between Amazon CloudSearch and other AWS Services. There are charges for outbound data transfers:

  • Data transferred between Amazon CloudSearch and AWS services in different regions will be charged as Internet Data Transfers on both sides of the transfer.
  • Traffic sent between Amazon CloudSearch and Amazon EC2 instances in the same region is only billed for the Data Transfer in and out of the Amazon EC2 instances. Standard Amazon EC2 Regional Data Transfer charges apply.
Elasticsearch vs CloudSearch - cost

Elasticsearch vs CloudSearch: Conclusion

Both Elasticsearch and Amazon CloudSearch are built on proven technologies and are the choice of many demanding organizations. Because of its flexibility and active developer community, Elasticsearch is more popular. But Amazon CloudSearch scores when it comes to operational efficiency.

Because of its popularity, AWS provides Elasticsearch as a Service (Amazon Elasticsearch Service) which, in many ways, provides the best of both worlds. Elastic.co also provides Elasticsearch as a cloud service Found.

What do you think? Was this helpful for determining the finer points of each service? Comments welcome and appreciated.

Avatar

Written by

Chandan Patra

Cloud Computing and Big Data professional with 10 years of experience in pre-sales, architecture, design, build and troubleshooting with best engineering practices. Specialities: Cloud Computing - AWS, DevOps(Chef), Hadoop Ecosystem, Storm & Kafka, ELK Stack, NoSQL, Java, Spring, Hibernate, Web Service


Related Posts

Patrick Navarro
Patrick Navarro
— January 22, 2020

Top 5 AWS Salary Report Findings

At the speed the cloud tech space is developing, it can be hard to keep track of everything that’s happening within the AWS ecosystem. Advances in technology prompt smarter functionality and innovative new products, which in turn give rise to new job roles that have a ripple effect on t...

Read more
  • AWS
  • salary
Alisha Reyes
Alisha Reyes
— January 6, 2020

New on Cloud Academy: Red Hat, Agile, OWASP Labs, Amazon SageMaker Lab, Linux Command Line Lab, SQL, Git Labs, Scrum Master, Azure Architects Lab, and Much More

Happy New Year! We hope you're ready to kick your training in overdrive in 2020 because we have a ton of new content for you. Not only do we have a bunch of new courses, hands-on labs, and lab challenges on AWS, Azure, and Google Cloud, but we also have three new courses on Red Hat, th...

Read more
  • agile
  • AWS
  • Azure
  • Google Cloud Platform
  • Linux
  • OWASP
  • programming
  • red hat
  • scrum
Alisha Reyes
Alisha Reyes
— December 24, 2019

Cloud Academy’s Blog Digest: Azure Best Practices, 6 Reasons You Should Get AWS Certified, Google Cloud Certification Prep, and more

Happy Holidays from Cloud Academy We hope you have a wonderful holiday season filled with family, friends, and plenty of food. Here at Cloud Academy, we are thankful for our amazing customer like you.  Since this time of year can be stressful, we’re sharing a few of our latest article...

Read more
  • AWS
  • azure best practices
  • blog digest
  • Cloud Academy
  • Google Cloud
Avatar
Guy Hummel
— December 12, 2019

Google Cloud Platform Certification: Preparation and Prerequisites

Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2019, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the second consecuti...

Read more
  • AWS
  • Azure
  • Google Cloud Platform
Alisha Reyes
Alisha Reyes
— December 10, 2019

New Lab Challenges: Push Your Skills to the Next Level

Build hands-on experience using real accounts on AWS, Azure, Google Cloud Platform, and more Meaningful cloud skills require more than book knowledge. Hands-on experience is required to translate knowledge into real-world results. We see this time and time again in studies about how pe...

Read more
  • AWS
  • Azure
  • Google Cloud
  • hands-on
  • labs
Alisha Reyes
Alisha Reyes
— December 5, 2019

New on Cloud Academy: AWS Solution Architect Lab Challenge, Azure Hands-on Labs, Foundation Certificate in Cyber Security, and Much More

Now that Thanksgiving is over and the craziness of Black Friday has died down, it's now time for the busiest season of the year. Whether you're a last-minute shopper or you already have your shopping done, the holidays bring so much more excitement than any other time of year. Since our...

Read more
  • AWS
  • AWS solution architect
  • AZ-203
  • Azure
  • cyber security
  • FCCS
  • Foundation Certificate in Cyber Security
  • Google Cloud Platform
  • Kubernetes
Avatar
Cloud Academy Team
— December 4, 2019

Understanding Enterprise Cloud Migration

What is enterprise cloud migration? Cloud migration is about moving your data, applications, and even infrastructure from your on-premises computers or infrastructure to a virtual pool of on-demand, shared resources that offer compute, storage, and network services at scale. Why d...

Read more
  • AWS
  • Azure
  • Data Migration
Wendy Dessler
Wendy Dessler
— November 27, 2019

6 Reasons Why You Should Get an AWS Certification This Year

In the past decade, the rise of cloud computing has been undeniable. Businesses of all sizes are moving their infrastructure and applications to the cloud. This is partly because the cloud allows businesses and their employees to access important information from just about anywhere. ...

Read more
  • AWS
  • Certifications
  • certified
Avatar
Andrea Colangelo
— November 26, 2019

AWS Regions and Availability Zones: The Simplest Explanation You Will Ever Find Around

The basics of AWS Regions and Availability Zones We’re going to treat this article as a sort of AWS 101 — it’ll be a quick primer on AWS Regions and Availability Zones that will be useful for understanding the basics of how AWS infrastructure is organized. We’ll define each section,...

Read more
  • AWS
Avatar
Dzenan Dzevlan
— November 20, 2019

Application Load Balancer vs. Classic Load Balancer

What is an Elastic Load Balancer? This post covers basics of what an Elastic Load Balancer is, and two of its examples: Application Load Balancers and Classic Load Balancers. For additional information — including a comparison that explains Network Load Balancers — check out our post o...

Read more
  • ALB
  • Application Load Balancer
  • AWS
  • Elastic Load Balancer
  • ELB
Albert Qian
Albert Qian
— November 13, 2019

Advantages and Disadvantages of Microservices Architecture

What are microservices? Let's start our discussion by setting a foundation of what microservices are. Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs). ...

Read more
  • AWS
  • Docker
  • Kubernetes
  • Microservices
Nisar Ahmad
Nisar Ahmad
— November 12, 2019

Kubernetes Services: AWS vs. Azure vs. Google Cloud

Kubernetes is a popular open-source container orchestration platform that allows us to deploy and manage multi-container applications at scale. Businesses are rapidly adopting this revolutionary technology to modernize their applications. Cloud service providers — such as Amazon Web Ser...

Read more
  • AWS
  • Azure
  • Google Cloud
  • Kubernetes