AWS CloudFormation reference
Everything the AWS QuickStart's CloudFormation stack creates in your account.
This page lists what the AWS QuickStart stack creates in your AWS account. For the access it gives Zerve, see What Zerve can access in your AWS account.
Access
The zerve IAM role
Lets Zerve manage the other resources. Usable only by Zerve, with your organization's ID as the external ID.
Compute roles
Separate roles for Lambda, Fargate and SageMaker runs, each with only what that kind of compute needs
A notebook-scoped access role
Limits each block run to its own notebook's data
Networking
If you don't choose an existing VPC, the stack creates:
A VPC
10.192.0.0/16 by default
Subnets
Two public and two private, across two Availability Zones
An internet gateway
For public traffic
NAT gateways
One in each Availability Zone, with fixed IP addresses, so your code's outbound traffic always comes from known addresses
It also creates security groups for block runs, deployments and the setup process.
Storage
An S3 bucket
Holds block outputs, variables and files. Named <prefix>-<your organization ID>. Each notebook's data is kept in its own folder.
Compute and environments
An ECS cluster
Runs container blocks and deployments
A CodeBuild project
Builds environments
ECR container repositories
Store environment images. Untagged images are removed after 14 days.
A log group for builds
Build logs are kept for 90 days
Deployments
Created only if you set a base domain:
An SSL certificate
For your base domain, validated through DNS
A Route 53 hosted zone
For your base domain, unless you provided one
A load balancer
For deployed apps. Internet-facing, HTTPS only (HTTP redirects to HTTPS), and limited to the IP ranges you allow.
API gateways
For deployed APIs and SageMaker model endpoints, each with its own certificate
Deployments get these addresses:
App
<name>.app.<base domain>
API
<name>.api.<base domain>
Model endpoint
<name>.sagemaker.<base domain>
Setup
A setup function
Runs once while the stack is created, and sends Zerve the details it needs: the account, role, region, bucket, networking, NAT gateway IP address, hosted zone and load balancer
What's kept when you delete the stack
Deleting the stack removes most of its resources. These are kept on purpose, so DNS and networking aren't lost by accident:
The Route 53 hosted zone
The main security groups
Delete them yourself if you no longer need them.
Last updated
Was this helpful?
