We’ve spent most of the last month on implementing EKS. Surprisingly, we’re always solving the same concerns no matter what project we’re working on. Here’s couple of tips for your EKS clusters! Skip kube2iam, go directly with IAM Roles for Service Accounts Kube2iam is amazing tool. I really like it and it helped me with granular control access in couple of projects. However, there’s a better solution that is supported out of the box: IAM roles for services accounts.

As you might already know, security is not something that a specialized department should be responsible for. Instead, we all should bear in mind that security matters and build secure solutions from the very beginning. Today we’re gonna talk about some practices in the world of containerized apps and Kubernetess. So let’s say we have some best practices for the containerized workloads. But how to enforce that? We’ll tell you right away.

GitLab-CI/CD is a great and powerful product for CI/CD pipelines. Hosted gitlab.com solution offers shared runners and some usage minutes based on your paid plan (even if the free tier). Though you might want to run your own runner in your private or public cloud. I will show how to run GitLab runner on AWS using terraform, Elastic Kubernetes Service and GitLab kubernetes integration.

Are you using EKS managed worker pools? If you don’t have any specific reasons for not using them, you should. It saves tons of time plus it boosts the “managed Kubernetes” feeling. However, this pretty new offering did not cover one specific use case: cluster with no Internet access.