wraps aws doctor if credentials are not resolving correctly.
wraps email init
Deploy email infrastructure (SES, Lambda, DynamoDB, EventBridge) to your AWS account. If infrastructure already exists in the selected region, the CLI will exit early and prompt you to usewraps email upgrade instead.
Hosting provider for your application. Accepted values:
vercel, aws, railway, other. Determines how IAM roles and OIDC are configured.AWS region to deploy infrastructure into (e.g.,
us-east-1). Defaults to your configured AWS region.Domain name to configure as the primary sending domain (e.g.,
yourapp.com).Configuration preset. Accepted values:
starter, production, enterprise, custom.| Preset | Est. cost | Features |
|---|---|---|
starter | ~$0.05/mo | Open/click tracking, bounce suppression |
production | ~$2–5/mo | + Event tracking, 90-day history, reputation metrics |
enterprise | ~$50–100/mo | + Dedicated IP, 1-year history, all event types |
custom | varies | Configure each feature individually |
Skip confirmation prompts and deploy immediately.
Show a plan of all AWS resources that would be created without deploying.
wraps email connect
Connect to an existing SES deployment in your account. Use this when you already have SES infrastructure and want Wraps to manage it.AWS region where the existing SES infrastructure is deployed.
Preview what would be imported or changed without applying.
wraps email status
Display the current state of your email infrastructure — deployed region, configuration, domains, and resource ARNs.AWS account ID to look up. Defaults to the account resolved from your current credentials.
AWS region to inspect.
wraps email check
Run a deliverability audit on a domain. Checks DKIM, SPF, DMARC, MX records, TLS support on mail servers, DNS blacklists, and domain age. Exits with a non-zero code if the grade is below a threshold.Domain to audit (e.g.,
yourapp.com). If omitted, the CLI will prompt for it.Run fewer checks: top blacklists only and fewer DKIM selectors. Faster but less thorough.
Output results as JSON instead of the formatted terminal display.
Show all checks, including those that passed.
Check a specific DKIM selector instead of probing common ones.
Skip all DNS blacklist checks.
Skip MX server TLS (STARTTLS) checks.
DNS query timeout in milliseconds.
wraps email verify
Verify that DNS records (DKIM CNAME, SPF, DMARC) are correctly configured for a domain in SES.Domain to verify.
wraps email config
Apply configuration updates from your local CLI settings to the deployed infrastructure. Use this after modifying presets or email configuration in code.AWS region of the deployment to update.
Skip confirmation prompt.
wraps email upgrade
Add features to an existing deployment without tearing it down. Prompts for which features to enable (tracking, history, dedicated IP, etc.).AWS region of the deployment to upgrade.
Skip confirmation prompt.
Show what resources would be added without applying changes.
wraps email restore
Redeploy infrastructure from saved metadata. Useful for recovering a stack after manual changes or drift.AWS region of the deployment to restore.
Skip confirmation prompt.
Show what would change without applying.
wraps email destroy
Remove all email infrastructure deployed by Wraps from your AWS account. Resources with thewraps-email-* prefix and ManagedBy: wraps-cli tag are deleted.
Skip the confirmation prompt. Do not use in automation without testing first.
AWS region of the deployment to destroy.
Show which resources would be deleted without deleting them.
Email domains
Subcommands for managing sending domains registered in SES.- add
- list
- get-dkim
- verify
- remove
Add a new domain (or subdomain) to SES for sending. Creates a SES identity with DKIM, optionally configures a MAIL FROM subdomain, and offers to create DNS records automatically.
Domain to add.
Email inbound
Subcommands for deploying and managing inbound email receiving (SES receipt rules + S3 + Lambda). Requires outbound email infrastructure to be deployed first.Inbound email is only supported in regions where SES has receiving capability. The CLI will error if you target an unsupported region.
- init
- status
- verify
- test
- destroy
Deploy inbound email infrastructure: S3 bucket for storage, Lambda for processing, SES receipt rules, and DNS records.
AWS region to deploy inbound infrastructure.
Subdomain prefix for the receiving address (e.g.,
inbound → inbound.yourapp.com). Defaults to inbound when --yes is passed.Skip all confirmation prompts.
Show changes without deploying.
