Deep Dive on Amazon ElastiCache Service as Redis Cluster with Amazon EC2 Instance

GargeeBhatnagar - Jul 21 - - Dev Community

“ I have checked the documents of AWS to get into deep dive on amazon elasticache service as redis cluster with amazon ec2 instance. In terms of cost, need to pay for redis cluster and amazon ec2 instance.”

Amazon ElastiCache is a fully managed Redis OSS and Memcached compatible service that delivers real time, cost optimized performance for modern applications. Elasticache speeds up database and application performance, scaling to hundreds of millions of operations per second with microsecond response time.

ElastiCache offers enhanced security, reliability, scalability and performance when compared to open source alternatives. At the same time, it helps remove the complexity associated with deploying and managing a distributed cache environment. It provides serverless caching and designing your own ElastiCache (Redis OSS) cluster.

In this post, you will experience how to deep dive on amazon elasticache service as redis cluster with amazon ec2 instance. Here I have created an amazon elasticache cluster and ec2 instance.

Architecture Overview

Image description
The architecture diagram shows the overall deployment architecture with data flow, amazon elasticache for redis, ec2 instance.

Solution overview

The blog post consists of the following phases:

  1. Create of Amazon ElastiCache Service as Redis Cluster with Required Configurations
  2. Testing in Redis Cluster Using Amazon EC2 Instance

Phase 1: Create of Amazon ElastiCache Service as Redis Cluster with Required Configurations

  1. Open the console of Amazon elasticache service, create a redis cluster with a design of its own cache option. Choose the demo configuration type for testing purposes with naming the cluster. Choose the option to create a new subnet group with VPC and subnet details. Taking default settings for configuration, create a redis cluster. Once a cluster is created, we can verify the redis cluster nodes and other configurations. After connecting the cluster, we can also view the monitoring metrics.

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Phase 2: Testing in Redis Cluster Using Amazon EC2 Instance

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Image description

Clean-up

Delete of Amazon ElastiCache Redis Cluster and Amazon EC2 Instance.

Pricing

I review the pricing and estimated cost of this example.

Cost of Amazon ElastiCache service = $0.016 per hour for cache.t4g.micro = $(0.016x2) = $0.032

Cost of Amazon Elastic Compute Cloud = $0.0116 per On Demand Linux t2.micro Instance Hour = $(0.0116x1.334) = $0.0154

Total Cost = $0.0474

Summary

In this post, I showed “how to deep dive on amazon elasticache service as redis cluster with amazon ec2 instance”.

For more details on Amazon ElastiCache Service, Checkout Get started Amazon ElastiCache Service, open the Amazon ElastiCache Service console. To learn more, read the Amazon ElastiCache Service documentation.

Thanks for reading!

Connect with me: Linkedin
Image description

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .