StackState/Agent IAM role: EKS
StackState Self-hosted v4.6.x
Last updated
StackState Self-hosted v4.6.x
Last updated
This page describes StackState version 4.6.
If StackState or the StackState Agent are running within an AWS environment in an EKS cluster instance, an IAM role can be attached to the node-group where the pods stackstate-api, stackstate-server and/or stackstate-cluster-agent are running.
When this role is available on the stackstate-api and stackstate-server pods, the AWS StackPack can be installed with the use-role option for IAM authentication (the AWS Access Key ID and AWS Secret Access Key). The attached role will then be used by the StackState CloudWatch plugin to retrieve metrics from CloudWatch.
When this role is available on the stackstate-cluster-agent pod and the AWS check is configured to run as a cluster check, the AWS check can be configured with the use-role option for IAM authentication.
To set up an IAM role for the AWS StackPack to use, follow the instructions below.
Create a policy that allows the AssumeRole action for the resource arn:aws:iam::*:role/StackStateAwsIntegrationRole. This is the same policy as used for the Agent IAM role on EC2. Take note of the policy name.
Find the node-group that contains nodes running the relevant pod or pods and create a node group role:
For StackState on EKS: stackstate-api and stackstate-server.
For StackState Agent on EKS: stackstate-cluster-agent.
Attach the policy from the first step to the node-group role from the previous step.
