1. Overview

2. Prerequisites & Dependencies

Ensure the following are set up before starting deployment:

NameCodeRecommended minimumNotes
Fargate On-Demand vCPUL-3032A53830Capacity for the task count you select during deployment plus other applications in the account.
Lambda concurrent executionsL-B99A93841,000Quota request required.

This product has the following dependencies (everything else is AWS-native and private via VPC endpoints where available):

3. CloudFormation Deployment

  1. Subscribe to the product.
  2. Navigate to launch page.
    • AWS Marketplace
    • Manage subscriptions
    • Traverse
    • Launch button
  1. Copy CloudFormation Template S3 URL. The template is in a seller-hosted S3 (URL follows pattern https://traverse-iac.s3.us-west-2.amazonaws.com/<template-name>).
    • On launch page
    • Select ECS in Setup
    • Deployment templates section
    • Copy CloudFormation Template URL
  2. Start CloudFormation stack creation.
    • CloudFormation console in a supported region
    • Create stack with new resources
    • Prepare template: Choose an existing template
    • Specify template: Amazon S3 URL
    • Paste CloudFormation Template S3 URL from Step 3
  3. Create CloudFormation stack.
    • Fill parameters on Specify stack details step
    • Use defaults & confirm acknowledgement that AWS CloudFormation might create IAM resources on Configure stack options step
    • Review inputs then click submit button on Review and create step
    • Deployment is finished when stack status shows CREATE_COMPLETE

Post Deployment OIDC Setup

Follow the exact steps outlined in your provider's documentation. General requirements:

  1. Allowed callback URL: https://<Subdomain>.<your-zone>/oidc/callback/
  2. Allowed sign-out URL: https://<Subdomain>.<your-zone>/
  3. OAuth grant type: authorization code.
  4. OpenID Connect scopes: openid (plus any profile scopes your provider requires, e.g. email).
  5. MCP server (if enabled):
    • Define a resource server / API at https://<Subdomain>.<your-zone>/mcp with a custom scope access (full identifier is https://<Subdomain>.<your-zone>/mcp/access)
    • Enable client registration for MCP clients with the authorization code grant.
    • Activate the custom scope for the application client.

4. Usage

General

Workflows

  1. Borrower entity: search the entities a deal can be created under, or create one.
  2. Deal: create the deal under the entity; rename, close (read-only), cancel, or reopen it from there.
  3. Facilities: add each credit facility to the deal.
  4. Documents: upload files to the deal (one-time upload links, then ingest); validation queues automatically. New files become new versions of a document; a bad version or document can be deleted (remaining versions renumber).
  5. Assign documents to facilities: the correction for a wrong assignment; documents detach and stay on the deal.
  6. Reports: per-version and deal-level reports; findings surface the review results.

Model Context Protocol (MCP) for AI agents

Disabled by default — must be enabled during CloudFormation deployment.

  1. Deploy the stack with Model Context Protocol (MCP) server for AI applications enabled.
  2. AI agents reach Traverse at https://<Subdomain>.<your-zone>/mcp and have the same permissions as their user's browser session.
  3. /mcp is an OAuth resource server against your identity provider: OAuth-capable agents discover it at /.well-known/oauth-protected-resource and sign in through your identity provider.
  4. Review your AI agent vendor's documentation for connecting to a remote MCP server.
  5. The functionality mirrors the app interface, scoped to the user's permissions.

5. IAM Resources

RolePurpose
TaskExecutionRoleECS agent: pull container images, read secrets at task start
TaskRole / WebTaskRoleApplication runtime (worker / web): documents bucket, document KMS key, License Manager checkout, Bedrock invocation, embedding Lambda invocation
TaskRoleFleetControlPolicyLets the app scale the worker fleet from the queue depth
RdsMonitoringRoleRDS Enhanced Monitoring to CloudWatch
EmbeddingLambdaRoleRuns the embedding Lambda: CloudWatch Logs
InfrastructureRoleECS Express Mode service infrastructure (load balancer, networking)
LiveTargetGroupResolverRoleCustom-resource Lambda: attaches the domain certificate to the load balancer listener

6. Keys & Secrets

Key / secretLocationRotation
Aurora master passwordRDS-managed Secrets Manager secretAutomatic (RDS-managed)
OIDC client secretSecrets ManagerRotate in your IdP, then update OIDC Client Secret CloudFormation parameter
Django SECRET_KEYSecrets ManagerNone — rotation signs out all sessions
Secrets Manager KMS keyKMS, automatic annual rotation (enabled)Automatic
Documents KMS keyAWSAutomatic

7. Data

DataLocationEncryptionNotes
Uploaded PDFsDocumentsBucketKMS at rest (stack CMK, or yours)Versioned; access-logged
Extracted text & workflow dataAurora PostgreSQLKMS at rest; TLS in transitStandard Postgres
Job queueAurora PostgreSQL (same database)—-
CredentialsSecrets ManagerKMS CMK-
LogsCloudWatch LogsService default30-day retention

8. Cost

Your Marketplace subscription covers the license. AWS infrastructure is billed separately by AWS and is usage dependent. Prices are AWS list prices for us-west-2 as of November 2026. Costs at deployment time depend on usage.

Baseline Costs (excluding usage charges):

ComponentMonthly
Web tasks — 2 × (1 vCPU / 2 GB)~$72
NAT Gateway~$33
Interface VPC endpoints — Bedrock + Lambda, 2 AZs each~$29
Application load balancer (ECS-managed)~$16
KMS keys (2) + Secrets Manager secrets (2)~$3
  Baseline total~$153

Usage-based Costs:

ComponentList price
Worker task-hour (1 vCPU / 2 GB)~$0.05
Aurora: compute / storage / I/O / backup$0.12 per ACU-hr · $0.10 per GB-mo · $0.20 per 1M I/O · $0.021 per GB-mo
Bedrock gpt-oss-120b (standard tier) — input / output$0.15 / $0.60 per 1M tokens
Embedding Lambda (3,008 MB)$0.20 per 1M invocations + ~$0.00005/s
S3 storage (versioned) / PUT / GET$0.023 per GB-mo · $0.005 per 1k · $0.0004 per 1k
CloudWatch Logs — ingest / store (30-day retention)$0.50 / $0.03 per GB-mo
NAT data processing / VPC endpoint data$0.045 / $0.01 per GB
Internet egress (user downloads)$0.09 per GB (first 10 TB/mo)

9. CloudFormation Deletion

  1. Disable stack termination protection.
    • CloudFormation console
    • Select stack
    • Actions: Disable stack termination protection
  2. Disable Aurora deletion protection.
    • RDS console
    • Select cluster
    • Modify
    • Uncheck Deletion protection (apply immediately)
  3. Delete stack.
    • CloudFormation console
    • Delete stack
    • Deletion is finished when stack status shows DELETE_COMPLETE or is no longer visible in CloudFormation console
  4. Clean up what stack leaves behind (optional).
    • Delete RDS snapshot
    • Empty, then delete S3 buckets
    • Deactivate, then schedule deletion for KMS keys
    • Delete CloudWatch logs

10. Open Source Software

Traverse uses open source software. See the complete notices for its open source dependencies.

11. Support

mark@cornicecredit.com — responses within 1 business day (US Pacific).

Subscription/refund/AWS managed product issues — AWS Marketplace buyer support.

12. Diagrams

I. Architecture
Traverse system diagram: I. Architecture
II. Identity & Access
Traverse system diagram: II. Identity & Access