HyperShift AWS Provider

Automate AWS-based HyperShift cluster provisioning with STS credentials and VPC configuration.

112|305|Updated Oct 10, 2025

Search Tags:#aws #kubernetes #infrastructure #hypershift #iam-roles #cluster-deployment #sts-credentials

Ready to run

npx skills add https://github.com/openshift-eng/ai-helpers --skill hypershift-aws-provider

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: HyperShift AWS Provider
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/hcp/skills/hcp-create-aws
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill hypershift-aws-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complexity of configuring AWS-specific requirements for HyperShift clusters, handling STS credentials, IAM roles, VPC configuration, and regional best practices automatically.

Core Features & Use Cases

Environment-Aware Configuration: Automatically detects development, production, or cost-optimized requirements from natural language descriptions.
Interactive Parameter Collection: Guides users through all required AWS-specific parameters with smart defaults and validation.
Use Case: When your team needs a highly available production cluster for customer-facing applications, this Skill generates the complete AWS provider command with proper multi-AZ deployment, instance sizing, and security settings.

Quick Start

Use the HyperShift AWS Provider skill to create a development cluster for testing our new microservice on AWS.

Frequently Asked Questions about HyperShift AWS Provider

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

FAQPage Schema

How do I deploy a HyperShift cluster on AWS with STS credentials?▼

HyperShift AWS Provider automates cluster provisioning by handling STS credentials, IAM roles, VPC configuration, and region-aware instance types. Supply --sts-creds, --role-arn, --region, --pull-secret, --release-image, and --base-domain parameters; the Skill validates inputs, applies environment-smart defaults, and generates the complete AWS provider command.

What AWS parameters are required to set up a production HyperShift cluster?▼

Production HyperShift deployment requires --region, --pull-secret, --release-image, --sts-creds, --role-arn, and --base-domain. The Skill guides parameter collection interactively, enforces multi-AZ configuration for high availability, validates VPC CIDR conflicts, and ensures OpenShift pull secrets are available before provisioning.

Can I use HyperShift on AWS for development and cost-optimized scenarios?▼

Yes. HyperShift AWS Provider detects environment requirements—development, production, or cost-optimized—from natural language descriptions and automatically configures appropriate instance sizing, security settings, and deployment topology for each context.

Does HyperShift prevent VPC configuration conflicts when deploying on AWS?▼

Yes. The Skill includes built-in validation to prevent VPC CIDR conflicts and verifies OpenShift pull secrets are available, reducing provisioning errors and ensuring compliance with AWS networking best practices before cluster creation begins.

How does HyperShift handle IAM roles and regional configuration automatically?▼

HyperShift AWS Provider accepts IAM role ARNs and region parameters, then applies environment-aware defaults and validation logic to configure multi-AZ deployment, appropriate instance types per region, and security settings matching development or production requirements.