Skip to main content
Porter provisions and manages infrastructure directly in your own cloud account. This gives you full control over your data and resources while Porter handles the complexity of Kubernetes cluster management.

Supported Cloud Providers

Getting Started

Setting up Porter with your cloud account involves three steps:
1

Connect your cloud account

Provide Porter with credentials to access your cloud provider. Porter uses secure methods like IAM role assumption (AWS), service principals (Azure), or service accounts (GCP) to manage resources without storing static credentials.Connect a cloud account →
2

Create a cluster

Porter provisions a Kubernetes cluster with sensible defaults including networking, load balancers, and node groups. Provisioning takes approximately 30-45 minutes.Create a cluster →
3

Deploy your application

Once your cluster is ready, deploy applications from GitHub or a container registry.Deploy your first app →

What Porter Provisions

Infrastructure provisioned by Porter includes:
ComponentAWSAzureGCP
Virtual NetworkVPCVNetVPC
Load BalancerNetwork Load BalancerAzure Load BalancerCloud Load Balancer
Kubernetes ClusterEKSAKSGKE
Container RegistryECRACRArtifact Registry

Default Node Groups

Porter provisions three node groups by default:
Node GroupPurposeAWSAzureGCP
SystemKubernetes system workloads2× t3.medium2× Standard_B2s2× e2-medium
MonitoringObservability stack1× t3.large1× Standard_B2ms1× e2-standard-2
ApplicationYour workloads1× t3.medium (autoscales)1× Standard_B2s (autoscales)1× e2-medium (autoscales)
On AWS, the application node group uses cost optimization by default, which automatically selects the most cost-effective instance types for your workloads.
The application node group autoscales based on workload demand. All nodes include 50GB of disk storage by default.
You can customize machine types, node counts, and disk sizes after initial provisioning through the Node Groups settings.

FAQ

How much does the underlying infrastructure cost?

The cost varies based on resource usage. By default, clusters provisioned by Porter cost approximately:
ProviderEstimated Monthly Cost
AWS~$225/month
GCP~$253/month
Azure~$165/month
These estimates are for the default cluster configuration. Actual costs vary based on usage, region, and customizations. All infrastructure costs can be covered with cloud credits from AWS, Google Cloud, or Azure.

Can I use my existing cloud credits?

Yes. Porter provisions infrastructure directly in your cloud account, so any credits you have with AWS, GCP, or Azure apply to the resources Porter creates.

What permissions does Porter need?

Porter requires permissions to create and manage Kubernetes clusters, networking resources, and container registries. The setup process varies by provider:
  • AWS: Automatic setup — Porter guides you through creating a CloudFormation stack that provisions the required IAM role with one click
  • Azure: Manual setup required — you’ll need to create a service principal using our setup script or the Azure CLI
  • GCP: Manual setup required — you’ll need to create a service account and download a JSON key file
For detailed permission requirements and setup instructions, see Connecting a Cloud Account.

Can I revoke Porter’s access?

Yes. You can revoke Porter’s access at any time by deleting the IAM role (AWS), service principal (Azure), or service account (GCP). Note that Porter will no longer be able to manage or delete resources after access is revoked.