Surf Viewer on AWS | SurfImaging.ai

Last updated: July 30, 2026 Applies to: Surf Viewer AWS materials

Start with the AWS Quick Start

The fastest path to a working SurfViewer deployment on AWS is the guided Quick Start page. It walks through AWS Marketplace discovery, account setup, Quick Launch, stack deployment, onboarding, ingestion, and opening the viewer.

Open AWS Quick Start Contact Support

Use this page as the stable AWS documentation landing page from offer descriptions, launch materials, and future operator instructions.

About This Page

This page is reserved for current and future AWS deployment guidance for Surf Viewer. It provides a stable URL that can be referenced now and updated later as packaging, onboarding, and operational documentation evolve.

Prerequisites

Use an AWS account that can subscribe in AWS Marketplace and create CloudFormation stacks in the target region, typically us-east-1.
Check your Lambda concurrency quota before deployment:

aws lambda get-account-settings --region us-east-1

Example output showing the problem:

{
  "AccountLimit": {
    "TotalCodeSize": 80530636800,
    "CodeSizeUnzipped": 262144000,
    "CodeSizeZipped": 52428800,
    "ConcurrentExecutions": 10,
    "UnreservedConcurrentExecutions": 10
  },
  "AccountUsage": {
    "TotalCodeSize": 0,
    "FunctionCount": 0
  }
}

If "ConcurrentExecutions": 10, or your current Lambda concurrency limit is less than 200, open an AWS support case and request an increase to 200.
If Amazon SES is still in sandbox mode, open an AWS support case and request production access. State that this is only to avoid receiver verification and that you will not use it for email broadcasting.

Support Boundary

Surf Viewer is intended to run in infrastructure selected and controlled by the customer. Operational steps, access boundaries, and deployment-specific guidance published here may differ by packaging model and release.