KOP EKS Clusters - IAM Service Accounts - Rafay Product Documentation

Overview

IAM Service Accounts

Post cluster provisioning, IAM Service Accounts feature allows to specify IAM policies at pod level, enabling the users to have granular control on pods. Each pod can have different IAM policies based on the required access.

Permission Boundaries for IAM

AWS supports permissions boundaries for IAM entities (users or roles). A permissions boundary allows to use a managed policy to set the maximum permissions that an identity-based policy can grant to an IAM entity. An entity's permissions boundary allows it to perform only the actions that are allowed by both its identity-based policies and its permissions boundaries. For more information, refer Permissions Boundaries.

Create IAM Service Account

Note: Create a new Namespace if no namespace exist

Below is an example of creating a IAM service account for a pod with Amazon S3 Read-Only Access authorization

AWS IAM Policy ARN

To get the AWS IAM Policy ARN from AWS Console, perform the below steps:

Below is an example of Amazon SE Read-Only Access policy that allows only the actions Get and List

AWS IAM Inline Policy Document

Important

Either provide AWS IAM Policy ARNs (or) upload an AWS IAM Inline Policy Document (any one is mandatory). This is to infuse the customized policies to the service accounts

A message indicates the IAM Service Account creation is in progress

View IAM Service Account status

Once the IAM Service Account creation process is initiated, Cloud Formation template will be created to provision the required resources in AWS. To view the status of the service account, perform the below steps:

Successful IAM Service Account

User can view the created IAM Service Account in the Controller

Provisioned Service Accounts

To view the service account created in a cluster, click KUBECTL and enter the command get sa -A