AWS

AWS Deployment of Datalogz

Prerequisites

  • Create an AWS sub-account (optional but recommended). This will help to monitor the costs and be more secure, as it will not interfere with production or other workloads running in the existing AWS accounts. If you deploy Datalogz in another sub-account you need to take care of respective network settings to connect your data sources.

  • A Route53 Public Hosted Zone with a Publicly resolvable DNS name. We use this domain to add an entry into it related to Datalogz URL.

  • Create a user with the following IAM permissions:

    • ec2:*

    • iam:*

    • s3:*

    • eks:*

    • cloudwatch:*

    • autoscaling:*

    • vpc:*

    • efs:*

    • resourcegroups:*

    • route53:*

Note: You can either create a new IAM user or enable an existing user with the above permissions. We will use the AWS Credentials of this user to deploy Datalogz within your AWS Account using Terraform. After completion, you can remove these permissions from the user.

Deployment Details

Datalogz deploys into the Customer’s AWS Account within a newly created VPC on EKS using Helm (https://helm.sh/).

What cluster addons do we install in the EKS Cluster?

  1. Nginx Ingress Controller (https://kubernetes.github.io/ingress-nginx/)

  2. Cert Manager (https://cert-manager.io/docs/) External DNS (https://github.com/kubernetes-sigs/external-dns)

  3. EKS Cluster Autoscaler (https://docs.aws.amazon.com/eks/latest/userguide/cluster-autoscaler.html)

  4. EKS Spot Node Termination Handler (https://ec2spotworkshops.com/using_ec2_spot_instances_with_eks/spotworkers/deployhandler.html)

Note: If you already has an EKS Cluster running in their AWS Account, we can work with you to install Datalogz directly into it as well.

Datalogz uses Terraform (https://www.terraform.io/) to deploy and manage all the AWS resources along with using Ansible (https://www.ansible.com/) to install cluster-addons and Datalogz within the EKS Clusters.

AWS Cost Estimate

Note: The mentioned pricing is based on the basic deployment of Datalogz. We use two On-Demand m5.xlarge EC2 machines in the basic deployment. Based on the usage of Datalogz, it can scale up the Frontend microservice thus resulting in an uptick of EC2 costs. There can be additional Data Transfer costs based on usage which are hard to calculate. 80% of AWS cost incurred by Datalogz is due to EKS (Fixed cost per month) and EC2 (Variable cost based on usage). Cost may vary slightly depending on the AWS region.

PreviousVPC (You Host)NextGCP

Last updated