This helm chart is for a mock application which interacts with AWS, for a demo project about granting AWS IAM roles to Kubernetes Pods using ServiceAccounts and OIDC (OpenID Connect). The application (included under app/) uploads and deletes mock files from an S3 bucket every several seconds, see app/README.md for more information about it.

• AWS S3 bucket - can be created with aws s3 mb s3://your-bucket-name --region your-region.
• AWS IAM role with attached policy granting permissions to act in above bucket - instruction available in AWS documentation.
• AWS EKS cluster with OIDC Identity provider - can be created using the oidc branch from my repository eks-spot-cluster.

• An AWS IAM role (and attached policy) must exist. They define the permitted actions on AWS.
• A Kubernetes ServiceAccount is created and annotated with the IAM role in its metadata. This allows Kubernetes to generate OIDC tokens for AWS.
• The ServiceAccount is attached to a Pod, providing the pod with the permissioned defined in it (sts:AssumeRoleWithWebIdentity).
• An AWS IAM Identity provider (of type OIDC) must exist for the cluster. This allows validation of the OIDC tokens, hence creating a trust relationship between AWS and the Kubernetes cluster.

More info about IAM roles for ServiceAccounts can be found in the AWS documentation.