Porter provisions and manages the underlying infrastructure in your own cloud. During project creation, Porter will prompt you to provision resources in Amazon Web Services (AWS) or Google Cloud Platform (GCP).
For step by step instructions on how to provision infrastructure in each cloud provider, see the links below.
Provisioning on AWS
Provisioning on Google Cloud
As mentioned in the introduction, Porter provisions a Kubernetes cluster in your cloud provider. It is not necessary to know much about the provisioned resources to use Porter, other than a few basic concepts. For those looking for a brief introduction to Kubernetes, we cover these basic concepts in Kubernetes 101.
The cost of your infrastructure varies entirely on the amount of resources you use. By default, clusters provisioned by Porter cost around $300 per month.
What does Porter-provisioned infrastructure consist of?
Broadly speaking, infrastructure provisioned by Porter on AWS includes a VPC, a Network Load Balancer, and an EKS cluster. The EKS cluster consits of three node groups: 2 t3.medium instances for system worklods, 1 t3.large instance for the monitoring workloads, and a t3.xlarge instance for your application workloads that scales based on your usage.
By default, Porter provisions a t3.xlarge instance - this accommodates up to 8 vCPU and RAM. You can switch out the instance type depending on how much resources each of your application requires. Each of your application cannot exceed the amount of resources available on a single instance. For example, if you want to run an application with 4GB memory on AWS, the instance type you select should be larger than the
t3.medium instances because they only have 2 vCPU and 4GB memory.
If you are unsure of which instance type you should select, book a free consultation call with our solution architects.