cluster-access

Configure kubeconfig for private EKS cluster access with AWS SSO and IAM roles.

1|Updated Mar 20, 2025
One-click install
npx skills add https://github.com/asanexample/platform --skill cluster-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cluster-access
Source: https://github.com/asanexample/platform/tree/main/.claude/skills/cluster-access
Command: npx skills add https://github.com/asanexample/platform --skill cluster-access

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides instructions on how to gain access to private EKS clusters for kubectl commands, kubeconfig configuration, and troubleshooting connection issues.

Core Features & Use Cases

  • Access EKS Clusters: Obtain kubectl / EKS API access to private platform and preprod clusters.
  • Kubeconfig Configuration: Set up and manage kubeconfig for cluster access.
  • Troubleshooting: Address connection issues such as "Unauthorized", "i/o timeout", and "connection refused".
  • Use Case: When you need to interact with a cluster for administrative tasks, such as checking logs or deploying applications.

Quick Start

Use the cluster-access skill to set up your kubeconfig for accessing the 'platform-use1-eks' cluster.

Frequently Asked Questions about cluster-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure kubeconfig to access a private EKS cluster?

To configure kubeconfig for private EKS cluster access, you must first log in via AWS SSO and assume the appropriate IAM role. This Skill provides instructions to set up kubeconfig for kubectl commands, emphasizing the PlatformAdmin role for cluster-wide access.

What IAM roles do I need for EKS cluster access?

You need AWS SSO login and specific IAM roles for EKS cluster access. The PlatformAdmin role grants cluster-wide access, while the PlatformDeployer role is used for specific operational tasks within the private clusters.

Why does kubectl return Unauthorized or connection refused when accessing EKS?

kubectl returns Unauthorized or connection refused errors when kubeconfig is misconfigured or lacks proper IAM role permissions. This Skill helps troubleshoot these connection issues by verifying AWS SSO login and ensuring the correct PlatformAdmin or PlatformDeployer role is assumed.

How can I access a private EKS cluster when Tailscale is unavailable?

When Tailscale is unavailable, you can access a private EKS cluster by using an SSM tunnel as a fallback method. This Skill includes instructions for establishing this alternative connection route to interact with your cluster.

Can I use kubectl with AWS SSO for preprod EKS clusters?

Yes, you can use kubectl with AWS SSO to access preprod EKS clusters. This Skill guides you through obtaining EKS API access and configuring kubeconfig specifically for preprod and platform-use1-eks environments.