AWS Setup
Create the IAM role that allows StrictOps to deploy to your AWS account
AWS Setup
StrictOps needs an IAM role in your AWS account to provision infrastructure on your behalf. This role uses an External ID for secure cross-account access — StrictOps never stores your AWS credentials.
Prerequisites
- AWS CLI installed and configured with credentials that have permission to create IAM roles
- Your StrictOps External ID (provided during onboarding)
- Your StrictOps Account ID (provided during onboarding)
Quick Setup
Run one of the following commands in your terminal. The script will:
- Check your AWS credentials
- Download and deploy a CloudFormation template
- Output the Role ARN to paste into StrictOps
Mac / Linux
Windows (PowerShell)
Replace YOUR_EXTERNAL_ID and STRICTOPS_ACCOUNT_ID with the values shown in the StrictOps onboarding flow.
What the script does
The setup script performs these steps:
| Step | Description |
|---|---|
| 1. Verify credentials | Checks that AWS CLI is configured and can authenticate |
| 2. Deploy CloudFormation | Creates a stack with the IAM role and required permissions |
| 3. Output Role ARN | Displays the Role ARN to copy into StrictOps |
Manual Setup
If you prefer to create the role manually or need to customize the permissions:
1. Download the CloudFormation template
2. Deploy the stack
3. Get the Role ARN
IAM Permissions
The IAM role grants StrictOps the minimum permissions needed to:
- ECS: Create and manage ECS clusters, services, and task definitions
- ECR: Create repositories and push container images
- CloudFormation: Deploy and manage infrastructure stacks
- EC2: Create security groups and describe VPCs/subnets
- ELB: Create load balancers and target groups
- CloudWatch Logs: Create log groups and read logs
- IAM: Create task execution roles (scoped to ECS)
You can review the full permissions in the CloudFormation template.
Troubleshooting
"AWS credentials not configured"
Make sure you've run aws configure or set the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.
"Access Denied" errors
Your AWS user/role needs permission to create IAM roles and CloudFormation stacks. Contact your AWS administrator if you don't have these permissions.
Stack already exists
If you've already created the role and need to update it, the script will update the existing stack automatically.
Script Source Code
You can review the scripts before running them: