Clusters / Template
AWS Self-Hosted K8s Cluster
Deploy a self-hosted Kubernetes cluster on AWS
Overview
Self-hosted Kubernetes on AWS EC2 instances. The `setup` command handles all resource provisioning automatically. Credentials are securely managed by the platform.
- Category
- Clusters
- Source
- clusters/aws/self-hosted/new-vpc.yaml
Prerequisites & dependencies
- Your AWS account id is required. Get it with `aws sts get-caller-identity --query Account --output text`
- You must follow the instruction https://astropulse.io/docs/latest/platform/cluster-pipeline/features/provisioner/self-hosted/aws
No dependencies are listed in the available catalog metadata. This is not a guarantee that none are required.
Source manifest
clusters/aws/self-hosted/new-vpc.yaml
# Self-hosted Kubernetes on AWS (EC2 instances AstroPulse manages)
#
# Before you apply, set up the account once; the setup prints the bucket name:
# astroctl cloud aws selfHosted setup --account-id <YOUR_AWS_ACCOUNT_ID> --region <YOUR_REGION> --cluster-name <YOUR_CLUSTER_NAME>
# astroctl cloud aws selfHosted status --cluster-name <YOUR_CLUSTER_NAME> # check the setup
#
# Apply: astroctl infra k8s apply -f new-vpc.yaml --dry-run, then without --dry-run
# Docs: https://astropulse.io/docs/latest/platform/cluster-pipeline/features/provisioner/self-hosted/aws
apiVersion: platform.astropulse.io/v1
kind: K8sCluster
spec:
clusterName: <YOUR_CLUSTER_NAME>
provider: aws
region: <YOUR_REGION>
provisioner:
type: selfHosted
selfHosted:
accountId: "<YOUR_AWS_ACCOUNT_ID>"
bucketName: "<YOUR_BUCKET_NAME>" # printed by the setup command
# networkId: <YOUR_VPC_ID> # optional: an existing VPC instead of a new one
credentials:
type: Vault
clusterSpec:
controlPlane:
nodeGroup:
name: control-plane
machineTypes:
- t3.medium
dataPlane:
nodeGroups:
- name: workers
minNode: 3
maxNode: 6
instanceType: OnDemand
machineTypes:
- t3.large
labels:
environment: production
Deployment guidance
Go straight to Console to create clusters, deploy applications, and manage supported resources. Templates and CLI commands are optional; not every GitHub manifest has an automatic import path.
Console — start directly
Open Console to create or connect infrastructure and deploy applications without running astroctl or copying this YAML first. This template may still require manual setup.
Open Consoleastroctl
Get your AWS account ID
aws sts get-caller-identity --query Account --output textAutomated setup (handles all resource provisioning)
astroctl cloud aws selfHosted setup --account-id <account-id> --region us-west-2 --cluster-name <YOUR_CLUSTER_NAME>Verify setup completed successfully
astroctl cloud aws selfHosted connect --cluster-name <YOUR_CLUSTER_NAME>Deploy the self-hosted cluster
astroctl infra k8s apply -f clusters/aws/self-hosted/new-vpc.yamlStream cluster creation progress
astroctl infra k8s progress stream <YOUR_CLUSTER_NAME>Check cluster status
astroctl infra k8s get <YOUR_CLUSTER_NAME>Generate kubeconfig for kubectl
astroctl infra k8s set-context <YOUR_CLUSTER_NAME>Delete the cluster
astroctl infra k8s delete <YOUR_CLUSTER_NAME>Review placeholders and permissions before running commands. Nothing executes from this page.
Nova
Prefer to describe the goal? Ask Nova to review this example and help plan supported actions. Access, policy, and approvals still apply.