💡
deploydocs
  • Introduction
  • Going Live: Checklist : CARE
  • CARE: CLOUD DEPLOYMENT OVERVIEW
    • Cloud Infrastructure Diagram
    • Google Cloud deployment
      • Set up the network
      • Set up Databases
      • Create storage buckets
      • Create a GKE cluster
      • Configure GKE workloads
      • Post setup
    • Azure Deployment
    • AWS Deployment
  • CARE: Deploying Technology
  • Tech Overview: CARE
  • Tech Prerequisites: CARE
  • Setting up the server locally
  • Setting up AWS EKS
  • Setting up AWS RDS
  • Build and push docker image
  • Production Environment Variables
  • Deploying the projects on EKS
  • Requirements: AWS
  • Tech Infrastructure: CARE
  • Steps to Deploy: CARE
  • CARE: Deploying Operations
  • Operationalizing CARE in the field
  • Setting up the War-Room
  • Deployment Timeline
  • Ambulance Management System
    • SuperHero Network
  • TeleICU Tech Deployment
    • Setup Nursing Station Desktop
    • BPL Monitor Network Configuration
Powered by GitBook
On this page

Was this helpful?

Export as PDF

Setting up AWS EKS

PreviousSetting up the server locallyNextSetting up AWS RDS

Last updated 4 years ago

Was this helpful?

Deployment on EKS involves quite a few steps to setup. This page provides a link in the bottom to a document that can help in creating the necessary resources on AWS. However, do make sure to read the following once before diving right in as it may contain answers to many queries you may have during the setup:

  • At all times, the region code for the Mumbai services will be ap-south-1. Make sure to choose this to reduce latency in the services.

  • The Step 0 in the article requests to have installed AWS IAM Authenticator. Do note that this will not be "necessary".

  • In Step 1, there has been some changes since the article. Choose "EKS Cluster" as the use case while creating the role. The AmazonEKSServicePolicy is no longer required.

  • In Step 2 and Step 4, you shall not be able to provide the same URL for uploading the template. Instead manually download the template on your system and upload the template where required.

  • In the VPC creation step (Step 2), do provide any valid IP ranges from RFC 1918. Make sure your range does not collide with any other existing VPC.

  • In the Node Group creation step (Step 4), execute aws ssm get-parameter --name /aws/service/eks/optimized-ami/1.16/amazon-linux-2/recommended/image_id --query "Parameter.Value" --output text on your command line replacing 1.16 with your cluster's kubernetes platform version. Use the value of the output as the Node Image ID.

  • Follow the steps until and including Step 4 only.

Click to setup the necessary AWS resources for your EKS deployment.

here