AWS Kubernetes for SAAS Consumers

This article shows how AWS Kubernetes is used to setup SAAS consumers from platform Engineering perspective.

AWS Private link for SAAS Products

In our organization we identified a SAAS tool as an Enterprise Tool. As a Platform engineering team, we need to setup the data plane as a consumer of the SAAS tool. We followed below steps to implement using AWS Kubernetes. It gives high level overview for any team member to understand BTS of platform team

• Provision AWS Account

Provision an AWS Account for the tool. Brainstorm with stakeholders to ensure how many AWS Accounts required for the tool based on the number of environments we will operate like — DEV, SIT, PRE-PROD and PROD.

• VPC and subnet:

Provision VPC (Virtual Private Cloud) and subnet as per organization policy.

• Provision IAM Roles

Provision IAM Roles for Admin Users, Developers and Devops Engineers based on personas of the team.

• Infrastructure as a Code (IAC) Scripts

Create IAC scripts to provision AWS Services like EKS, EBS, S3, etc. for the implementation. We can use terraform or AWS CloudFormation for creation of IAC scripts.

• Automation Scripts

Create Automations scripts to deploy the IAC Scripts created above using tools like Jenkins, GITHUB Actions, etc.

• Private Link

Setup a private link with SAAS Provider. This will ensure we will have a secure connection within AWS Network.

• Availability, Scalability and Isolation

AWS Kubernetes provides dynamic scaling options based on demand. It provides availability by ensuring required number of pods are running. Namespace in Kubernetes provides Isolation for application.

• Setup Monitoring

Setup monitoring using SRE tools based on organization preference like Datadog, Grafana Dashboards, Splunk, etc.