Skip to main content
Legacy deployment path — for existing customers only. New Amazon EKS deployments should use the Helm-based path. The Terraform-based path documented here is retained so that customers running existing deployments can continue to operate them and migrate to Helm. To migrate, see Migrate from Terraform to Helm.

​
Overview

This page covers the original Terraform-based Amazon EKS deployment path. It is documented for customers who deployed Poolside before the Helm-based path became the default and who have not yet migrated. In this path, you run Poolside-provided deployment containers and scripts in your AWS account to create and manage the infrastructure, provision Kubernetes resources, and deploy the platform. You can use either local GPU-backed inference or Amazon Bedrock for model inference.

​
Model options

Local GPU inference

Run the platform on Amazon EKS and serve models from GPU-backed inference workloads in your cluster.

Amazon Bedrock

Run the platform on Amazon EKS and use Amazon Bedrock for model inference without local GPU nodes.

​
Deployment management

Poolside provides the deployment bundle, deployment containers, and documentation for this path. You run the installation, update, and removal workflow in your AWS account.

​
Regional availability

You can configure this deployment path in any AWS region that supports the required services. For local GPU inference, the deployment region must support the required GPU instance types and the rest of the AWS platform services that Poolside uses. For Amazon Bedrock, the deployment region must support Amazon Bedrock and the Poolside models you plan to use. For cross-region Amazon Bedrock deployments and data handling considerations, see Amazon Bedrock data privacy.

​
Costs

For a breakdown of AWS infrastructure and inference costs that applies to both the Helm-based and Terraform-based paths, see AWS cost modeling.

​
Security

In this deployment path:
  • Deploying Poolside does not require root access. Follow AWS best practices for securing the root user.
  • Protect AWS resources used by Poolside, such as Amazon S3 and Amazon RDS, with appropriate access controls because they contain sensitive data.
  • Supported AWS deployment modalities encrypt data at rest by default. Poolside uses customer-managed AWS Key Management Service (KMS) keys when provided. Otherwise, it falls back to AWS-managed KMS keys for each service.
  • The deployment stores the secrets and credentials that Poolside requires in AWS Systems Manager Parameter Store. AWS Secrets Manager is not supported for this path, and external credential rotation can disrupt service operation.

​
Backup and recovery

AWS provides infrastructure availability features, but you are responsible for implementing and testing backup and disaster recovery procedures for your deployment. When you plan backup and recovery, pay particular attention to:
  • model artifacts stored in Amazon S3
  • database state in Amazon RDS
  • deployment configuration
  • container images stored in Amazon ECR