Deploy SaaS to customer AWS
Deploy your SaaS into a customer's AWS account.
Three ways teams do it
-
Send templates or scripts
The customer's engineers run your Terraform or CloudFormation. Each update is a new handoff, and you see little of what runs.
-
Build your own platform
Cross-account roles, an installer, a release pipeline, and status tracking. Your team builds it, then maintains it for every customer.
-
Use Deployz
The customer approves a connector in their AWS console. Deployz deploys your releases there, and you manage updates from one place.
What it takes with Deployz
See each step- You bring
-
- Your app in a GitHub repository
- A Dockerfile that builds one Linux x86-64 image
- An HTTP health check
- Your customer brings
-
- An AWS account
- Someone who can launch a CloudFormation stack
- Payment for their AWS resources
- Deployz handles
-
- The network, containers, database, cache, storage, and HTTPS
- Release deployment, updates, and rollbacks
- Status for every customer environment
Questions
Security and architectureHow does my customer give Deployz access?
They open your installation link, review the resources and IAM actions, and launch the Deployz connector as a CloudFormation stack in their AWS console. Deployz never asks for AWS access keys.
Does my customer need a Deployz account?
No. Only you need a Deployz account. Your customer needs an AWS account.
Who pays for AWS?
AWS bills the account owner, which is your customer. Deployz fees are separate.
Can the customer remove access?
Yes. The customer deletes the connector stack in their AWS console. Remove the deployment and its retained data first, because after that Deployz cannot change the application.