1. Overview
- One CloudFormation stack in your AWS account — using your own domain and identity provider.
- No data leaves your account — it remains entirely in your private cloud and AWS managed services.
- Licensing is handled by AWS License Manager using your Marketplace subscription.
- This product is supported in us-east-1, us-east-2, and us-west-2 only - deployments outside these supported regions fail.
- Future versions ship as a new CloudFormation template + container image; schema migrations run automatically at boot.
2. Prerequisites & Dependencies
Ensure the following are set up before starting deployment:
- OIDC identity provider: register a confidential application (client ID + client secret).
- Subdomain: a Route 53 public hosted zone in the deployment account.
- Service Quotas: the defaults deploy on any new AWS account. The following quotas are recommended for optimal performance: request increases in the AWS Service Quotas console.
| Name | Code | Recommended minimum | Notes |
|---|---|---|---|
| Fargate On-Demand vCPU | L-3032A538 | 30 | Capacity for the task count you select during deployment plus other applications in the account. |
| Lambda concurrent executions | L-B99A9384 | 1,000 | Quota request required. |
This product has the following dependencies (everything else is AWS-native and private via VPC endpoints where available):
- Your OIDC identity provider: required at login; must be reachable from the VPC (via NAT).
- AWS License Manager: required at boot + every 15 minutes (AWS-native, via NAT).
3. CloudFormation Deployment
- Subscribe to the product.
- Navigate to launch page.
- AWS Marketplace
- Manage subscriptions
- Traverse
- Launch button
- 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
- 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
- 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:
- Allowed callback URL: https://<Subdomain>.<your-zone>/oidc/callback/
- Allowed sign-out URL: https://<Subdomain>.<your-zone>/
- OAuth grant type: authorization code.
- OpenID Connect scopes: openid (plus any profile scopes your provider requires, e.g. email).
- 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
- Health: GET /health/ returns {"status": "ok"} when the service is up (liveness only).
- Monitoring: ECS console (service/task state, scaling), RDS console (Aurora Enhanced Monitoring), CloudWatch Logs (app, worker, Lambda).
- Names: an entity name can never be reused; a deal name can't be reused under the same entity; facility names can be reused after deletion.
- Bulk upload caps: 25 files · 25 MB/file · 128 MB/batch · 1,000 pages/document. Multiple bulk uploads can process concurrently.
- Sessions: 1 hour cookie; identity-token renewal every 15 minutes of activity.
Workflows
- Borrower entity: search the entities a deal can be created under, or create one.
- Deal: create the deal under the entity; rename, close (read-only), cancel, or reopen it from there.
- Facilities: add each credit facility to the deal.
- 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).
- Assign documents to facilities: the correction for a wrong assignment; documents detach and stay on the deal.
- 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.
- Deploy the stack with Model Context Protocol (MCP) server for AI applications enabled.
- AI agents reach Traverse at https://<Subdomain>.<your-zone>/mcp and have the same permissions as their user's browser session.
- /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.
- Review your AI agent vendor's documentation for connecting to a remote MCP server.
- The functionality mirrors the app interface, scoped to the user's permissions.
5. IAM Resources
| Role | Purpose |
|---|---|
| TaskExecutionRole | ECS agent: pull container images, read secrets at task start |
| TaskRole / WebTaskRole | Application runtime (worker / web): documents bucket, document KMS key, License Manager checkout, Bedrock invocation, embedding Lambda invocation |
| TaskRoleFleetControlPolicy | Lets the app scale the worker fleet from the queue depth |
| RdsMonitoringRole | RDS Enhanced Monitoring to CloudWatch |
| EmbeddingLambdaRole | Runs the embedding Lambda: CloudWatch Logs |
| InfrastructureRole | ECS Express Mode service infrastructure (load balancer, networking) |
| LiveTargetGroupResolverRole | Custom-resource Lambda: attaches the domain certificate to the load balancer listener |
6. Keys & Secrets
| Key / secret | Location | Rotation |
|---|---|---|
| Aurora master password | RDS-managed Secrets Manager secret | Automatic (RDS-managed) |
| OIDC client secret | Secrets Manager | Rotate in your IdP, then update OIDC Client Secret CloudFormation parameter |
| Django SECRET_KEY | Secrets Manager | None — rotation signs out all sessions |
| Secrets Manager KMS key | KMS, automatic annual rotation (enabled) | Automatic |
| Documents KMS key | AWS | Automatic |
7. Data
| Data | Location | Encryption | Notes |
|---|---|---|---|
| Uploaded PDFs | DocumentsBucket | KMS at rest (stack CMK, or yours) | Versioned; access-logged |
| Extracted text & workflow data | Aurora PostgreSQL | KMS at rest; TLS in transit | Standard Postgres |
| Job queue | Aurora PostgreSQL (same database) | — | - |
| Credentials | Secrets Manager | KMS CMK | - |
| Logs | CloudWatch Logs | Service default | 30-day retention |
- Backups: Aurora automated backups, 7-day retention, point-in-time recovery; final snapshot on stack delete.
- Recovery: restore via the RDS console; documents recover from S3 version history.
- No lifecycle rule — by design: the system never deletes uploaded documents; retention expiry is your decision.
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):
| Component | Monthly |
|---|---|
| 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:
| Component | List 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
- Disable stack termination protection.
- CloudFormation console
- Select stack
- Actions: Disable stack termination protection
- Disable Aurora deletion protection.
- RDS console
- Select cluster
- Modify
- Uncheck Deletion protection (apply immediately)
- Delete stack.
- CloudFormation console
- Delete stack
- Deletion is finished when stack status shows DELETE_COMPLETE or is no longer visible in CloudFormation console
- 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.