AWS EKS: Kubernetes, IAM and GitOps
MY ROLEProject lead, cloud architect and platform engineer
As project lead, cloud architect and platform engineer, I built an AWS EKS environment with automated provisioning, workload permissions and network and storage integrations.
EKS provisioning used Terraform or eksctl. An application was connected to Amazon S3.
IAM Roles for Service Accounts controlled workload access. AWS Load Balancer Controller and EBS CSI Driver were deployed and tested for network and storage integration. GitOps was investigated as an extension.
Result: Built an EKS environment with infrastructure automation, workload permissions and network and storage integrations.
Technologies & competencies
Related references
These projects use many of the same technologies and competencies:
AWS: private networks, databases and observability
Cloud Engineering / Client project. As project lead, cloud architect and infrastructure engineer, I built a multi-tier AWS environment with private database connectivity, controlled administration paths and central monitoring.
AWS ECS Fargate: container deployment and CI/CD
Cloud Engineering / Client project. As project lead, cloud developer and DevOps engineer, I implemented automated deployment of a web application on AWS ECS Fargate, including image builds, permissions and release workflows.
Asynchronous processing: RabbitMQ with .NET and SQS/Lambda with Kotlin
ProjectMakers / Internal project. As project lead, software architect and backend developer, I designed and implemented asynchronous integrations using RabbitMQ and .NET, plus additional task processing with Amazon SQS, AWS Lambda and Kotlin.
Apleona · Azure knowledge application and automated AKS deployment
Apleona GmbH / Project phase. As project lead, Azure architect, developer and DevOps engineer, I was responsible for implementing an Azure knowledge application and automating the deployment of containerised workloads for Apleona.