Deployment Models Comparison
Serverless Inbox can be deployed in two ways. This document helps you choose the right approach for your situation.
AWS Marketplace coming soon. A one-click Marketplace listing is planned for a future release.
Decision Tree
Section titled “Decision Tree”graph TD Q1{"Are you a<br/>developer or<br/>DevOps engineer?"}
Q1 -->|Yes| Q2{"Want to modify<br/>infrastructure?"} Q1 -->|No, just ops| CF["CloudFormation<br/>(template-only)"]
Q2 -->|Yes| CDK["AWS CDK<br/>(most flexible)"] Q2 -->|No| CF
CDK -->|Clone repo| P2["Full Control<br/>Customizable"] CF -->|Upload template| P3["Template-driven<br/>Repeatable"]Quick Comparison
Section titled “Quick Comparison”| Feature | CDK | CloudFormation |
|---|---|---|
| Complexity | Medium | Medium |
| Control | Full | Full |
| Customization | Excellent | Good |
| Learning Curve | Medium | Low |
| Time to Deploy | 30-45 min | 20-30 min |
| Best For | Developers | Operations |
| Multi-region | Easy | Manual |
| CI/CD Integration | Native | Native |
Option 1: AWS CDK (Developer-Friendly)
Section titled “Option 1: AWS CDK (Developer-Friendly)”Best For
Section titled “Best For”- Developers who want to understand and modify infrastructure
- Teams with CI/CD pipelines
- Projects requiring custom networking or advanced AWS features
- Organizations using Infrastructure-as-Code across multiple projects
What You Get
Section titled “What You Get”- Complete source code in TypeScript
- Full control over every AWS resource
- Can modify and extend the infrastructure
- Integration with your existing CDK stacks
- Version control of infrastructure changes
Prerequisites
Section titled “Prerequisites”- AWS Account with sufficient permissions
- AWS CLI v2
- Node.js 18+
- Git
- ~20 minutes
Next Steps
Section titled “Next Steps”✅ Full infrastructure visibility and control
✅ Easy to modify and test changes
✅ Integrates with team CI/CD workflows
✅ Code review process for infrastructure changes
✅ Reproducible deployments via version control
❌ Requires understanding of CDK
❌ Longer initial setup
❌ More things that can go wrong in dev environment
Option 2: CloudFormation (Template-Only)
Section titled “Option 2: CloudFormation (Template-Only)”Best For
Section titled “Best For”- Operations teams comfortable with AWS templates
- Organizations with CloudFormation policies
- When you want infrastructure control without learning CDK
- Enterprises requiring template auditing and approval
What You Get
Section titled “What You Get”- Pre-built CloudFormation templates (YAML/JSON)
- Upload to AWS CloudFormation console
- Creates identical infrastructure to CDK option
- Repeatable, version-controlled deployments
- Suitable for multi-region and multi-account rollouts
Prerequisites
Section titled “Prerequisites”- AWS Account with sufficient permissions
- AWS CloudFormation console access
- Understanding of CloudFormation basics
- ~15 minutes
How It Works
Section titled “How It Works”- Download CloudFormation template
- Upload to CloudFormation console
- Specify parameters (region, instance sizes, etc.)
- Review and deploy
- Monitor stack creation in console
Next Steps
Section titled “Next Steps”→ Deploy with CloudFormation Tutorial (coming soon)
✅ No coding required
✅ Standard AWS deployment mechanism
✅ Works with enterprise approval workflows
✅ Can be stored in S3 for team access
✅ Familiar to ops teams
❌ Template is read-only (can’t easily customize)
❌ Less flexible than CDK
❌ Harder to debug issues
❌ Changes require uploading new template
Comparison: Real-World Scenario
Section titled “Comparison: Real-World Scenario”Scenario: You’re evaluating Serverless Inbox and need to demo it in a week.
Section titled “Scenario: You’re evaluating Serverless Inbox and need to demo it in a week.”| Approach | Timeline | Effort | Customization |
|---|---|---|---|
| CloudFormation | Day 1 | 1-2 hours | Edit template, redeploy |
| CDK | Day 1-2 | 2-3 hours | Full control, modify code |
Best choice for this scenario: CloudFormation (fastest path to a working system)
Scenario: You’re building a production deployment with custom networking.
Section titled “Scenario: You’re building a production deployment with custom networking.”| Approach | Timeline | Effort | Customization |
|---|
| CloudFormation | Day 2-3 | 3 hours | Can be done but painful | | CDK | Day 1-2 | 4 hours | Easy, version-controlled |
Best choice for this scenario: AWS CDK (flexibility is worth the time)
After Deployment
Section titled “After Deployment”Regardless of which model you choose, next steps are identical:
- Complete Initial Setup - Verify deployment and configure your account
- Configure Email Identity - Add domain and verify with SES
- Manage Administrators - Grant access to colleagues
Still Unsure?
Section titled “Still Unsure?”Ask yourself:
- “Do I need to modify infrastructure later?” → CDK
- “Will ops teams need template auditing?” → CloudFormation
- “I want the fastest path to production” → CloudFormation (~20-30 min)
See Also
Section titled “See Also”- System Architecture - What you’re deploying
- Security Model - Authentication approaches
Last tested: March 2026