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
- Amazon Web Services (AWS)
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.comservice principal, with thests:AssumeRoleandsts:TagSessionactions. See Create IAM role with trust policy required by EKS Pod Identity. During configuration,sfe cloud-identity awsupdates 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 awsdoesn’t configure this method. See IAM roles for service accounts.