Say When..

Series of blog posts show progress of updating/adding to EKS Cluster, this post covers adding Kiro under Ai Operations. See below for past posts:

Kiro: Kiro is an agentic coding IDE/service for specs, code, docs, tests, and larger repo-level tasks.

			
=====================
curl -fsSL https://cli.kiro.dev/install | bash
=====================
exec "$SHELL" -l
=====================
kiro-cli --version
=====================
kiro-cli login --use-device-flow
=====================

		

Kiro-CLI Example to utilize:

			
=====================
Analyze this Terraform repository without changing any files or creating any AWS resources.
Explain:
1. The architecture this code deploys.
2. How EKS, VPC, IAM, IRSA, EBS CSI, S3, Thanos, Argo CD, and GitOps connect.
3. Security, reliability, and cost concerns.
4. Any Terraform errors, stale configuration, hard-coded values, or unnecessary resources.
5. The five highest-priority improvements.
You may run only read-only commands such as:
git status
terraform fmt -check
terraform validate
terraform plan
Do not run terraform apply, terraform destroy, git commit, git push, or modify files.
=====================

		

Infra Repo:

From either infra or gitops repo it will provide you a link to click for creation/log-in to your AWS builder ID

			
=====================
Review my IAM and IRSA Terraform code only. Do not modify files. Identify excessive permissions, incorrect trust relationships, and hard-coded account-specific values.
=====================

			
=====================
Review this repository for unnecessary AWS costs. Do not modify files or create resources. Estimate which resources generate costs while the EKS cluster is running.
=====================

			
=====================
Create a dependency map showing the order in which this Terraform code creates the VPC, EKS cluster, IAM roles, EBS CSI driver, Argo CD, and GitOps bootstrap. Do not change files.
=====================

Gitops Repo:

			
=====================
Analyze this Kubernetes GitOps repository without modifying any files.
Review:
1. The Argo CD application hierarchy, sync waves, and dependencies.
2. Helm chart versions and values-file references.
3. Kyverno CEL validating policies and their Audit or Deny actions.
4. NetworkPolicies for DNS, Kubernetes API, Prometheus, Grafana, Loki, Tempo, and Thanos.
5. Resource requests, limits, security contexts, image tags, RBAC, namespaces, and storage.
6. K8sGPT, kube-bench, Popeye, Falco, Trivy Operator, and the monitoring stack.
7. Invalid YAML, duplicate policies, missing manifests, selector mismatches, and configuration drift.
8. The five highest-priority improvements.
You may run only read-only commands. Do not modify files, run kubectl apply, perform an Argo CD sync, commit, or push anything.
=====================

		