Using Istio, a Service Mesh, with Amazon Elastic Kubernetes Service (EKS) - Part 2
This is the second part of the series on Using Istio, a Service Mesh, with Amazon Elastic Kubernetes Service (EKS). The first article discussed what a S...
Dallin Rasmuson
2024-06-04

This is the second part of the series on Using Istio, a Service Mesh, with Amazon Elastic Kubernetes Service (EKS). The first article discussed what a Service Mesh and Istio are, what technologies we will use, the prerequisites and architecture overview, and the configuration and setup process.

In this part two article, we will be working on these tasks.
- Configure access to Amazon EKS Cluster
- Install Istio CLI tool - istioctl
- Run the "configure.sh" script to configure the Flux Repository
- Install Flux to the Amazon EKS Cluster
- Review Addons and Applications managed by Flux
- Discuss the Istio Components and Addons used by Istio.
- Review how Istio works with Applications and Microservices
You can access the code in my GitHub Repository
Configure access to Amazon EKS Cluster
Amazon EKS Cluster details can be extracted from terraform output or by accessing the AWS Console to get the name of the cluster. This following command can be used to update the kubeconfig in your local machine where you run kubectl commands to interact with your EKS Cluster. Navigate to the root of the directory of the GitHub repo and run the following commands:
cd terraform
AWS_REGION=$(terraform output -raw aws_region)
EKS_CLUSTER_NAME=$(terraform output -raw eks_cluster_name)
aws eks --region $AWS_REGION update-kubeconfig --name $EKS_CLUSTER_NAME
Results of configuring kubeconfig.
Install Istio CLI - istioctl
Step 1. Install Istioctl CLI
- For macOS or Linux, follow these instructions using Homebrew
brew install istioctl
- For Windows, using Chocolatey, follow these instructions.
choco install istioctl
- For Windows, using Scoop, follow these instructions.
scoop bucket add main
scoop install main/istioctl
- Install instructions for other methods can be found here.
Step 2. Instructions on how to use istioctl can be found here and here.
Step 3. Verify that istioctl is installed by running the following command.
istioctl version
Step 4. Result of running istioctl.
Configure and Install Flux
Step 1. Configure Variables needed to install Flux
export GITHUB_TOKEN='<REPLACE_WITH_GITHHUB_TOKEN>'
export GITHUB_USER='<REPLACE_WITH_GITHUB_USER>'
export GITHUB_OWNER='<REPLACE_WITH_GITHUB_OWNER>'
export GITHUB_REPO_NAME='<REPLACE_WITH_GITHUB_REPO_NAME>'
Step 2. Configure the Flux Repository by running the "configure.sh" script. The "configure.sh" script updates the various applications with the necessary values to run correctly. Navigate to the root of the directory of the GitHub repo and run the following commands:
cd scripts
./configure.sh
cd ..
Step 3. Results of running the "configure.sh" script.
Step 4. Install Flux on the Amazon EKS Cluster
flux bootstrap github \
--components-extra=image-reflector-controller,image-automation-controller \
--owner=$GITHUB_OWNER \
--repository=$GITHUB_REPO_NAME \
--private=false \
--path=clusters/eks-istio-lab \
--personal
Step 5. Results of installing Flux on the Amazon EKS Cluster.
Managing Flux
Managing Flux is handled by using the Flux CLI. Flux does not come with any Web or UI interface to manage Flux. Please click here if you would like more information on the Flux CLI.
The following are some commands you can use to manage Flux.
flux get all
flux get sources all
Dallin Rasmuson
Solutions Architect
Read More
View all posts
AI/ML
Why Enterprise AI Must Be Application-Led, Not Agent-Led
A deep dive by Todd Bernson, CTO and Chief AI Officer, on why enterprise AI systems should be architected as application-led, deterministic platforms with embedded agentic AI—not fully autonomous agents. This article explains how API-first, governed, multi-channel architectures deliver higher reliability, compliance, scalability, and business value in real-world Fortune-500 environments.

Todd Bernson
2025-12-02

AI/ML
Application-First Agentic AI
Application-first agentic AI is emerging as the only reliable path to real enterprise ROI. In this in-depth analysis, Todd Bernson, CTO & CAIO, breaks down why most generative AI initiatives stall in production—and how disciplined enterprise architecture, deterministic workflows, and narrowly scoped AI agents can finally unlock repeatable business value. Using a real sprint-intelligence system as a case study, the article shows how organizations can combine serverless engineering, structured orchestration, and constrained LLM reasoning to reduce reporting effort, increase trust, eliminate hallucinations, and deliver actionable insights across engineering, operations, compliance, and customer experience.

Todd Bernson
2025-11-28
AI/ML
Why 95% of AI Projects Fail and How to Be Among the 5% That Succeed

Lee Hylton
2025-08-22