Studio Project workflows for Amazon EKS cluster lifecycle, node groups, and add-ons
Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service for running containerized applications on AWS without managing control plane infrastructure. It handles cluster lifecycle, managed node groups, Fargate profiles, add-ons, and identity provider integration for Kubernetes RBAC.
| Asset | Description |
|---|---|
| OpenAPIs/ | Amazon EKS REST API OpenAPI spec — curated -latest plus the full dated spec |
| Studio Projects/Amazon EKS | 25 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Amazon EKS | API version 2017-11-01 |
| Amazon EKS Integration Model | Required to build automation against the OpenAPI spec |
Import the OpenAPI spec from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at the EKS regional API endpoint (e.g. https://eks.<region>.amazonaws.com).
Authentication uses AWS Signature Version 4 — requests are signed with an AWS access key ID and secret access key rather than a static bearer token or API key header:
Authorization: AWS4-HMAC-SHA256 Credential=<access-key-id>/<date>/<region>/eks/aws4_request, SignedHeaders=..., Signature=<computed-signature> Generate an AWS access key ID and secret access key for an IAM principal with eks:* permissions under IAM > Users/Roles > Security credentials.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"hmac": {
"accessKeyId": "<your-aws-access-key-id>",
"secretAccessKey": "<your-aws-secret-access-key>",
"sessionToken": ""
}
},
"server": {
"protocol": "https",
"host": "eks.us-east-1.amazonaws.com",
"base_path": ""
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
amazon_eks-latest.json | latest (curated) | 35 | Trimmed to 35 of 56 upstream operations — see breakdown below |
amazon_eks-2017-11-01.json | 2017-11-01 | 56 | Full spec for the Amazon EKS 2017-11-01 API. |
amazon_eks-latest.jsonActively-maintained spec (x-vendor-api-version: 2017-11-01). Trimmed to 35 of 56 upstream operations: every included operation manages an EKS cluster or one of its direct sub-resources (add-ons, managed node groups, Fargate profiles, identity provider configs, updates, tags, connected-cluster registrations). The 21 upstream operations added since this spec was last reviewed — Access Entries, Access Policies, Pod Identity Associations, EKS Anywhere Subscriptions, and cluster Insights — are not yet reviewed for inclusion; see the full spec if you need one of those areas in the meantime.
Operations included, by category:
amazon_eks-2017-11-01.jsonFull spec for the Amazon EKS 2017-11-01 API (35 operations) — the entire upstream API surface as AWS defines it. See amazon_eks-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Amazon EKS:latest Integration Model (see amazon_eks-latest.json above). The project contains 25 workflows organized into 6 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec.
| Folder | Workflows | Scope |
|---|---|---|
| Clusters | Create, List, Describe, Delete Cluster, Update Cluster Version | Cluster lifecycle |
| Addons | Create, List, Describe, Update, Delete Addon | Add-on management |
| Fargate Profiles | Create, List, Describe, Delete Fargate Profile | Fargate profile management |
| Nodegroups | Create, List, Describe, Delete Nodegroup | Managed node group lifecycle |
| Identity Provider Configs | Associate, List, Describe, Disassociate Identity Provider Config | Kubernetes RBAC identity provider integration |
| Tags | List, Tag, Untag Resource | Tagging management |
| Dependency | Notes |
|---|---|
Amazon EKS:latest Integration Model | Import from amazon_eks-latest.json before importing the project |
Amazon EKS integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Amazon EKS — update the adapter_id value in each workflow task if yours is named differently |