Basic AWS Setup
Basic Setup of Sorry Cypress on AWS
Last updated
Basic Setup of Sorry Cypress on AWS
Last updated
The basic installation is designed to be plug-n-play - it creates the bare minimum of resources to run Sorry Cypress on AWS.
If you are looking for a more comprehensive deployment please process to Advanced AWS Setup
It takes just 5 minutes to deploy full sorry-cypress kit on AWS using AWS Cloud Formation template.
Click the link, follow on-screen instructions
Wait for deloyment to complete
Go to "Output" section of Cloud Formation task to see access URLs
Reconfigure cypress to use DirectorURL from the previous step.
That's it!
Alternatively, use the commands below
The Cloud Formation stack uses AWS Elastic Container Service (ECS) to run sorry-cypress services. The configuration includes networks and Load Balancer for secure and convenient access.
The artifacts created by the stack are:
Dashboard URL - web dashboard access URL
API URL - GraphQL API access URL
S3 Bucket - for storing tests video recordings and screenshots
Cloudwatch log groups for debugging and troubleshooting
StackName (default: "sorry-cypress")
Defines the stack name, also serves a prefix name for all the entities created by the stack. Please keep it short and no special characters as AWS limits service names.
TaskCpu (default: 1024)
TaskMemory (default: 2048)
DirectorPort (default: 8080)
For example, if the access URL created by the stack is http://sorry-cypress-1502240720.us-east-1.elb.amazonaws.com, and DirectorPort=8080 then director service will be available at http://sorry-cypress-1502240720.us-east-1.elb.amazonaws.com:8080
You're only paying for AWS resources. Here's a rough estimator of price / month for using the resources used . The actual usage might be higher (or lower) based on actual usage
S3 + Cloudwatch = varies based on usage
Director URL - this is what you provide when
The amount of CPU units dedicated to running the services. Sorry-cypress uses AWS Fargate as compute platform, and runs all the services as a single task, i.e. those CPU units are shared among all the services. Read more about at
The amount of memory units dedicated to running the services. This resource is also shared between the services and defined at task-level. Read more at ``
The port number for accessing the director service. You'll need to use it as a destination when .
The stack creates to provide access to the underlying services. By default, AWS LB URL points to the web dashboard (on port 80). The director service is available via the same URL but different port.
Fargate pricing based on 35.546 USD (1 vCPU, 2GB RAM) or 17.773 USD (0.5 vCPU, 1GB RAM)
EC2 Application Load Balancer based on 19.35 USD (0.5 GB / hour, 0.5 connections / second)
Too expensive? Try .
