AWS Marketplace deployment

EvidentSource is distributed through the AWS Marketplace. Subscribing gives you an AMI and a CloudFormation template that deploys the whole runtime into your own AWS account.

What gets deployed

The provided CloudFormation template stands up:

• An ECS service running the EvidentSource container (default: 2 tasks in separate AZs for HA)
• An Application Load Balancer with TLS termination
• An S3 bucket for SlateDB state
• IAM roles scoped to the bucket and minimum required permissions
• CloudWatch log groups and metrics
• Optional: AWS WAF, X-Ray tracing, VPC endpoints

You keep your data in your AWS account. Evident Systems has no access.

Sizing

Tier	vCPU / task	Memory	Typical workload
Small	1	2 GB	<100 TPS, dev/staging
Medium	2	4 GB	~500 TPS
Large	4	8 GB	1000+ TPS

Horizontal scale: increase ECS desired count. Since durable state lives in S3, tasks are stateless — scale-up and scale-down are free operations.

CloudFormation parameters

The Marketplace listing handles subscription and licensing. Once subscribed, the CloudFormation stack parameters cover:

• VPC / subnet configuration (deploy into an existing VPC or let the template create one)
• Domain name + ACM certificate ARN (the ALB’s TLS cert; must be in the same region)
• S3 bucket name (existing or new)
• Desired task count + task size
• Authentication provider config (see Security)

Regions

EvidentSource runs in any AWS region that supports ECS Fargate and S3 (i.e. all commercial regions). The public Sandbox and Designer services are hosted in us-east-2.

Upgrading

Upgrades are a container image version bump in the ECS service. Rolling deploys mean zero downtime for the API surface.

Next

• Operations: containers + S3 — architecture and why it’s this simple.
• Security — auth and authorization configuration.
• Kafka prerequisites — read this only if bridging to external Kafka.