IAM Permissions Not Working in EKS? Here's How to Fix It (With IRSA)

UpdatedMarch 18, 2026

•2 min read•View as Markdown

IAM Permissions Not Working in EKS? Here's How to Fix It (With IRSA)

Anup kafle

Cloud Engineer | AWS Community Builder

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Multi-Tenancy on AWS EKS: Separating Teams with Namespaces and IAM

As your team and projects grow, managing a single EKS cluster can get complicated. You'll likely have different teams like a "Backend Team" and a "Frontend Team" all needing to deploy their applicatio

May 6, 20256 min read

Multi-Tenancy on AWS EKS: Separating Teams with Namespaces and IAM

VPC-Connected AWS Lambdas Are Slower ? Here’s How to Fixed It

Serverless computing with AWS Lambda is one of the most powerful ways to run code in the cloud without managing servers. But when a Lambda function is placed inside a VPC (Virtual Private Cloud) to co

Mar 27, 20256 min read

VPC-Connected AWS Lambdas Are Slower ? Here’s How to Fixed It

Deep Dive & Step-By-Step: Deploying a Flask App to Amazon ECS with GitHub Actions & OpenID Connect

Modern developers want fast CI/CD but without storing long-lived AWS keys.By combining Amazon ECS (Fargate), Amazon ECR, GitHub Actions, and OpenID Connect (OIDC) you can deploy securely and automatic

Feb 3, 20255 min read

Deep Dive & Step-By-Step: Deploying a Flask App to Amazon ECS with GitHub Actions & OpenID Connect

Learn Bash Scripting: A Beginner's Guide

Learn Bash Scripting: A Beginner's Guide Table of Contents Introduction Bash Scripting Basics Variables and User Input Conditional Statements Loops and Iterations Functions Working with Files Scripting Best Practices Conclusion 1. Introdu...

Dec 6, 20245 min read

Anup's Blog

23 posts

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": ["s3:ListBucket"], "Resource": ["arn:aws:s3:::rambunct-app"] }, { "Effect": "Allow", "Action": ["s3:GetObject"], "Resource": ["arn:aws:s3:::rambunct-app/*"] } ] }

eksctl create iamserviceaccount \ --name <serviceaccount-name> \ --namespace <namespace> \ --cluster <cluster-name> \ --region <region> \ --attach-policy-arn arn:aws:iam::<account-id>:policy/<policy-name> \ --approve \ --override-existing-serviceaccounts

Command Palette

Comments

More from this blog

Conclusion