IAM Permissions
Required AWS IAM permissions for deploying Wraps infrastructure.
View and configure the exact AWS IAM permissions required for Wraps to deploy infrastructure to your account.
Use the CLI to see exactly what permissions are needed for your configuration:
npx @wraps.dev/cli permissionsThe permissions command supports several options to customize the output:
Output the full IAM policy as JSON (ready to paste into AWS Console):
npx @wraps.dev/cli permissions --jsonGet permissions for a specific preset (starter, production, or enterprise):
npx @wraps.dev/cli permissions --preset production --jsonGet permissions for a specific service (email, sms, or cdn):
npx @wraps.dev/cli permissions --service email --jsonThe AWS services required depend on which configuration preset you choose:
Basic email sending with open/click tracking
Full event tracking with email history storage
All features including SMTP credentials and dedicated IP
These permissions enhance functionality but are not required:
Route53
Automatic DNS record management
Alternative: Add DNS records manually to your provider
IAM OIDC Provider
Vercel deployments (OIDC federation)
Alternative: Use AWS access keys instead
Save the IAM policy JSON to a file:
npx @wraps.dev/cli permissions --json > wraps-policy.jsonGo to IAM → Policies in the AWS Console
Click Create Policy
Select the JSON tab
Paste the contents of your policy JSON file
Name it WrapsDeploymentPolicy
Go to IAM → Users (or Roles)
Select your user or role
Click Add permissions → Attach policies
Search for and select WrapsDeploymentPolicy
If you encounter permission errors during deployment:
Wraps provides specific guidance for each permission error
Run wraps permissions --json to get the latest required permissions
AWS Organizations may have Service Control Policies restricting what you can do
Now that permissions are set up, deploy your first service.
Deploy EmailHaving issues? Check common problems and solutions.
Troubleshooting