RudderStack is a customer data pipeline tool for collecting, routing and processing data from your websites, apps, cloud tools, and data warehouse.
More information on RudderStack can be found here.
These Terraform scripts provision an Amazon Elastic Kubernetes Service (AWS EKS) cluster in a new VPC and restrict access to other cloud resources owned by you.
-
Separate VPC
-
Separate Kubernetes cluser
- Region: AWS region to create the VPC.
Please go through variables.tf
for other config variables.
- Install Terraform v0.12.0 or later.
- Open
variables.tf
and checkout the default values for the variables. You can change them if you wish. For example, to change your nodes configuration alter the default values for variablesrudder_node_type
andrudder_disk_size_gb
. - Run
terraform get
. - Run
terraform plan
. - If the plan looks good, run
terraform apply
. This will create all the needed resources on your AWS. - If you would like to use
kubectl
, runexport KUBECONFIG=`pwd`/kubeconfig_rudder-cluster
The Kubernetes cluster created by these terraform scripts is by default accessible by rudder. (You can revoke access by following the instructions given at the end.)
For managed hosting, RudderStack would need to access your AWS cluster. Please share the following to enable RudderStack-managed hosting:
rudder_kubeconfig_rudder-cluster
aws.yml
To revoke RudderStack's access to your kubernetes cluster, follow the following steps
- Remove default values for the variables
map_accounts
andmap_roles
invariables.tf
file. - Run
terraform apply
If you come across any issues while configuring or using these scripts, please feel free to start a conversation on our Slack channel. We will be happy to help you.