How kevanto/terraform-aws-ps-sso works
This repository provisions infrastructure for running K3s on an EC2 instance. The documented workflow is to configure remote state, run Terraform initialization and apply, then SSH to the instance and retrieve its kubeconfig. The file tree identifies Terraform configuration and setup scripts, but no source excerpts show their resource details or interactions; those relationships are therefore marked unverified where included.
Main entry points: k3s-server.tf K3s EC2 server · k3s-server-script.sh Server setup script · install-helm.sh Helm installation script · backend.tf State backend config
Components 14
Terraform configuration
- State backend config
backend.tf - AWS provider config
provider.tf - Input variables
variables.tf - VPC networking
vpc.tf - K3s EC2 server
k3s-server.tf - Deployment outputs
outputs.tf
Instance setup
- Server setup script
k3s-server-script.sh - Helm installation script
install-helm.sh - K3s cluster
Cluster access
- SSH session
- Kubeconfig
Other components
- Operator
- Terraform CLI
- AWS
Connections 11
- Operator → Terraform CLI: runs init and apply
README.md - Operator → State backend config: sets remote state
README.md - Terraform CLI → K3s EC2 server: provisions
- Terraform CLI → VPC networking: provisions
- Terraform CLI → AWS: deploys to
- K3s EC2 server → Server setup script: runs setup
- Server setup script → K3s cluster: installs
- Operator → SSH session: connects by SSH
README.md - SSH session → Kubeconfig: reads
README.md - K3s cluster → Kubeconfig: provides
README.md - Helm installation script → K3s cluster: configures Helm