Skip to main content
Create the identity SeekrFlow’s own pods use to reach your cloud services, such as object storage, OpenSearch, and your secret store. It’s separate from the roles you created for Amazon Elastic Kubernetes Service (Amazon EKS), the nodes, and the cluster add-ons. Those roles only let each component do its own work. For every role in a deployment, see Security considerations. You connect this identity to SeekrFlow’s service accounts during configuration.
Skip this page for on-premises deployments. Storage credentials come from a Kubernetes secret, and on-premises deployments don’t use cloud identity.

Choose a method

On Amazon Web Services (AWS), choose one of these methods:

Create the identity

Create an IAM role for SeekrFlow. Attach a permission policy that grants the permissions in this table, with the scope each row lists.In AWS GovCloud (US), ARNs use the aws-us-gov partition, such as arn:aws-us-gov:s3:::<bucket-name>.The role’s trust policy depends on your method:
  • Amazon EKS Pod Identity – Trust the pods.eks.amazonaws.com service principal, with the sts:AssumeRole and sts:TagSession actions. See Create IAM role with trust policy required by EKS Pod Identity. During configuration, sfe cloud-identity aws updates the trust policy and creates a Pod Identity association for each SeekrFlow service account.
  • IAM roles for service accounts – Trust your cluster’s OpenID Connect (OIDC) provider. sfe cloud-identity aws doesn’t configure this method. See IAM roles for service accounts.

Record the values

Note these values. You will enter them when you create the values file.
Last modified on October 16, 2026