Skip to main content

​
Introduction

Poolside has two main deployment modalities:
  • Amazon EC2
  • Amazon Bedrock
This guide explains how to subscribe to Poolside across Amazon Web Services (AWS) deployment options. For assistance during this process, contact your Account Manager.

​
Amazon EC2

To subscribe on Amazon EC2, work with your Account Manager to ensure your AWS account is unblocked on the AWS Marketplace listing page. Then go to Poolside AWS Subscription.
You must be signed in to an AWS account to access the Poolside AWS Subscription page.
On the Poolside AWS Subscription page, click Subscribe and follow the instructions. The subscription can take a few minutes to process. Contact Poolside for installation scripts and deployment support. Poolside automatically sends metering information to AWS Marketplace. During setup, it configures the following environment variables: 
FORGE_TELEMETRY_USAGE_PUBLISHER_TYPES=log,s3,marketplace
FORGE_TELEMETRY_USAGE_MARKETPLACE_PRODUCT_CODE=dbh6vjyv8ukoypnc6w1tqejtp
Metering only accounts for the number of output tokens. For example, if you send 7000 input tokens and the model generates 500 output tokens, you are charged 500 tokens times the model unit price.

​
Amazon GovCloud for EC2-based deployments

To subscribe to Poolside in AWS GovCloud, navigate to Poolside AWS Subscription from your linked commercial account and follow the same process as in the public AWS Marketplace.
You must be signed in to an AWS account to access the Poolside AWS Subscription page.
After you have subscribed, follow the same process as in the public AWS Marketplace to install Poolside. For compliance reasons, AWS does not allow metering information to flow from AWS GovCloud accounts into AWS Marketplace. As a result, you must send monthly metering information to AWS by using the Metering API. For example: 
GET /admin/aws-metering?month=2025-03&aws_account_id=93xxxxxx21 (with Authorization header)
Use the AWS account ID (aws_account_id) associated with your Marketplace subscription, not your AWS GovCloud account ID (account_id).
This returns a response that you must send to your AWS Account Manager. The Account Manager then reports the data to the AWS Marketplace service team. Repeat this process every month or automate it.

​
Amazon Bedrock

To deploy on Amazon Bedrock, work with your Account Manager to ensure your account is unblocked in the listing. Then go to the Amazon Bedrock model catalog, select your Point and Malibu models, and follow the instructions. After you accept the terms, contact your Poolside point of contact. They provide installation scripts and deployment support. After installation, Poolside immediately starts tracking your output tokens and sending them to AWS Bedrock.

​
Marketplace metric collection

The Poolside Platform Core API service publishes metrics to the AWS Marketplace Metering Service API. For more information, see Using the AWS Marketplace Metering API in the AWS documentation. The Poolside Platform pushes metrics every hour, or when a Poolside Core API container stops.

​
Health monitoring

Use Container Insights to monitor the EKS cluster and its nodes. For more information, see Amazon EKS and Kubernetes Container Insights metrics in the AWS documentation. Work with your Poolside representative to explore configuring alarms and alerts using tools such as Amazon CloudWatch.

​
AWS infrastructure costs

To view only Poolside-related costs in your monthly AWS bill, use AWS Cost Explorer with AWS cost allocation tags. In the AWS Billing and Cost Management console, you can enable AWS cost allocation tags. This lets you filter by a specific tag and see only the costs associated with that tag. For Poolside, enable cost allocation tags for a tag applied during your infrastructure setup.
If you are using Amazon Bedrock for inference, this does not include those costs.
After you create and apply user-defined tags to your resources, tag keys can take up to 24 hours to appear on the cost allocation tags page and up to another 24 hours to activate. After activation, you can filter AWS Cost Explorer by that tag. For more information, see Using user-defined cost allocation tags in the AWS documentation.