Guides
Automate Deployments
Set up automated deployments with SST Console
This guide walks you through setting up automated deployments for your Agentic Team OS applications using SST Console.
Overview
Agentic Team OS uses SST’s auto-deployment feature to automatically deploy your applications when you push changes to specific branches. The setup process involves:
- Connecting your AWS accounts
- Linking your GitHub repositories
- Configuring deployment environments
- Setting up branch-based deployments
1. Add AWS Accounts
-
Create SST Console Account
- Visit console.sst.dev
- Sign up with your work email
- Create a new workspace for your organization
-
Connect AWS Account
- Go to Workspace Settings > AWS Accounts
- Click “Add AWS Account”
- Create the CloudFormation stack in us-east-1
- Wait for account connection to complete
-
Verify Connection
- Check that your SST apps are detected
- Verify access to all regions
- Ensure proper IAM role setup
2. Link GitHub Repositories
-
Install GitHub App
- Go to App Settings > Autodeploy
- Click “Connect GitHub”
- Install SST Console GitHub App
- Select repositories to connect
-
Configure Repository Access
- Choose between all repositories or select repositories
- Grant necessary permissions
3. Configure Deployment Environments
-
Set Up Environments
-
Add Environment Variables
- Navigate to App Settings > Autodeploy
- Add environment for each stage:
-
Configure Stage Patterns
- Set up production environment for
main
branch - Configure staging for
develop
branch - Add preview environments for PRs using
pr-*
pattern
- Set up production environment for
4. Trigger Deployments
-
Push to Repository
-
Monitor Deployments
- Visit SST Console > Your App > Autodeploy
- Check deployment status and logs
- Verify environment variables
- Monitor build progress
-
Set Up Notifications
- Configure Slack notifications
- Set up email alerts
- Enable deployment status updates
Best Practices
-
Branch Protection
- Enable branch protection rules
- Require pull request reviews
- Set up status checks
-
Environment Management
- Use stage-specific configurations
- Secure sensitive environment variables
- Implement proper access controls
-
Monitoring
- Set up deployment alerts
- Monitor build times
- Track deployment success rates
Was this page helpful?