Core Concepts

StrictOps orchestrates deployments of your applications to AWS ECS Fargate. This section explains the key entities and how they work together.

Overview

StrictOps uses a hierarchical model:

1. Organizations manage team access and billing
2. Projects group related services and environments
3. Services define what gets deployed (via strictops.yml)
4. Environments separate production from staging/development
5. Integrations connect your AWS account and GitHub repositories
6. Deployments track each release of your application
7. Logs give you visibility into running services

Entity Relationships

Organization
├── AWS Connections (IAM roles for cross-account access)
├── GitHub Installations (GitHub App for repo access)
├── Users & Memberships (team members and roles)
└── Projects
    ├── Services (from strictops.yml)
    ├── Environments (production, staging, etc.)
    ├── Resources (databases, storage, queues, caches)
    └── Deployments
        └── Steps (build, provision, deploy, verify)

Learn More

• Deployments - How deployments work and their lifecycle
• Services - Defining services in strictops.yml
• Environments - Multi-environment deployment support
• Stack Strategies - How environments are grouped into CloudFormation stacks
• Organizations - Team and access management
• Integrations - AWS and GitHub connections
• Logs - Viewing application logs