Skip to content

Parent Stack Examples

This section contains examples of parent stack configurations that provide shared infrastructure for client applications.

Available Examples

AWS Multi-Region Parent Stack

Complete parent stack with Cloudflare DNS configuration and multi-region AWS setup.

Use Case: Global applications, disaster recovery, multi-region deployment

Configuration: 

# .sc/stacks/devops/server.yaml
schemaVersion: 1.0

templates:
  ecs-fargate-us:
    type: ecs-fargate
    config: &aws-us-config
      credentials: "${auth:aws-us}"
      account: "${auth:aws-us.projectId}"
      region: us-east-1

  ecs-fargate-eu:
    type: ecs-fargate
    config: &aws-eu-config
      credentials: "${auth:aws-eu}"
      account: "${auth:aws-eu.projectId}"
      region: eu-west-1

resources:
  resources:
    production:
      # US East resources
      s3-storage-us:
        type: aws-s3-bucket
        config:
          <<: *aws-us-config
          name: "myapp-prod-storage-us"
          allowOnlyHttps: true
          corsConfig:
            allowedOrigins: ["https://myapp.com"]
            allowedMethods: ["GET", "POST", "PUT"]

      rds-postgres-us:
        type: aws-rds-postgres
        config:
          <<: *aws-us-config
          name: "myapp-prod-db-us"
          instanceClass: "db.r5.xlarge"
          allocateStorage: 100
          engineVersion: "14.9"
          username: "appuser"
          password: "${secret:DB_PASSWORD_US}"
          databaseName: "myapp"

      # EU West resources
      s3-storage-eu:
        type: aws-s3-bucket
        config:
          <<: *aws-eu-config
          name: "myapp-prod-storage-eu"
          allowOnlyHttps: true
          corsConfig:
            allowedOrigins: ["https://myapp.com"]
            allowedMethods: ["GET", "POST", "PUT"]

      rds-postgres-eu:
        type: aws-rds-postgres
        config:
          <<: *aws-eu-config
          name: "myapp-prod-db-eu"
          instanceClass: "db.r5.xlarge"
          allocateStorage: 100
          engineVersion: "14.9"
          username: "appuser"
          password: "${secret:DB_PASSWORD_EU}"
          databaseName: "myapp"

      # MongoDB Atlas with multi-region
      mongodb-atlas:
        type: mongodb-atlas
        config:
          publicKey: "${secret:MONGODB_ATLAS_PUBLIC_KEY}"
          privateKey: "${secret:MONGODB_ATLAS_PRIVATE_KEY}"
          orgId: "${secret:MONGODB_ATLAS_ORG_ID}"
          projectId: "${secret:MONGODB_ATLAS_PROJECT_ID}"
          instanceSize: M30
          region: US_EAST_1
          cloudProvider: AWS
          admins: ["admin@mycompany.com"]
          developers: ["dev@mycompany.com"]
          backup:
            every: 6h
            retention: 168h
          networkConfig:
            allowCidrs: ["10.0.0.0/8"]
            privateLinkEndpoint: true
          extraProviders:
            - name: AWS
              credentials: "${auth:aws-us}"

registrar:
  cloudflare:
    type: cloudflare-registrar
    config:
      credentials: "${secret:CLOUDFLARE_API_TOKEN}"
      accountId: "${secret:CLOUDFLARE_ACCOUNT_ID}"
      zoneName: "myapp.com"
      dnsRecords:
        - name: "@"
          type: A
          value: "203.0.113.10"
          proxied: true
        - name: "api"
          type: CNAME
          value: "us-east-1.elb.amazonaws.com"
          proxied: true
        - name: "api-eu"
          type: CNAME
          value: "eu-west-1.elb.amazonaws.com"
          proxied: true

Features: - Multi-region AWS deployment (US East, EU West) - Cloudflare DNS management with proxying - MongoDB Atlas with cross-region networking - S3 buckets with CORS configuration - RDS PostgreSQL in multiple regions - Private link endpoints for security - Comprehensive backup strategies

GCP Comprehensive Parent Stack

Complete GCP setup with GKE, databases, and Cloudflare domain management.

Use Case: GCP-native applications, Kubernetes workloads, global CDN

Configuration: 

# .sc/stacks/devops/server.yaml
schemaVersion: 1.0

templates:
  gke-autopilot:
    type: gcp-gke-autopilot
    gkeClusterResource: "main-gke-cluster"
    artifactRegistryResource: "main-registry"

resources:
  resources:
    production:
      main-gke-cluster:
        type: gcp-gke-autopilot-cluster
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          location: europe-west3
          gkeMinVersion: "1.33.4-gke.1245000"  # Check: gcloud container get-server-config --location=europe-west3

      main-registry:
        type: gcp-artifact-registry
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          location: europe-west3
          docker:
            immutableTags: true

      postgres-db:
        type: gcp-cloudsql-postgres
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          region: europe-west3
          tier: db-standard-2
          diskSize: 100
          databaseVersion: POSTGRES_14

      redis-cache:
        type: gcp-redis
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          location: europe-west3
          tier: standard
          memorySizeGb: 4

      storage-bucket:
        type: gcp-bucket
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          name: "myapp-prod-storage"
          location: europe-west3

      pubsub-messaging:
        type: gcp-pubsub
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          topics:
            - name: "events"
              labels:
                environment: "production"
          subscriptions:
            - name: "event-processor"
              topic: "events"
              ackDeadlineSec: 60
              exactlyOnceDelivery: true

registrar:
  cloudflare:
    type: cloudflare-registrar
    config:
      credentials: "${secret:CLOUDFLARE_API_TOKEN}"
      accountId: "${secret:CLOUDFLARE_ACCOUNT_ID}"
      zoneName: "myapp.com"
      dnsRecords:
        - name: "@"
          type: A
          value: "203.0.113.20"
          proxied: true
        - name: "api"
          type: CNAME
          value: "gcp-lb.myapp.com"
          proxied: true

Features: - GKE Autopilot for managed Kubernetes - Artifact Registry for container images - Cloud SQL PostgreSQL database - Redis for caching and sessions - Cloud Storage for file storage - Pub/Sub for event-driven architecture - Cloudflare integration for global CDN

Hybrid Cloud Parent Stack

Multi-cloud parent stack configuration with AWS and GCP resources.

Use Case: Multi-cloud strategy, vendor diversification, best-of-breed services

Configuration: 

# .sc/stacks/devops/server.yaml
schemaVersion: 1.0

templates:
  aws-compute:
    type: ecs-fargate
    config:
      credentials: "${auth:aws}"
      account: "${auth:aws.projectId}"
      region: us-east-1

  gcp-data:
    type: gcp-gke-autopilot
    gkeClusterResource: "data-cluster"
    artifactRegistryResource: "data-registry"

resources:
  resources:
    production:
      # AWS for compute workloads (using S3 for storage instead of ECS cluster)
      s3-compute-storage:
        type: s3-bucket
        config:
          credentials: "${auth:aws}"
          account: "${auth:aws.projectId}"
          region: us-east-1
          name: "myapp-compute-storage"
          allowOnlyHttps: true

      s3-storage:
        type: s3-bucket
        config:
          credentials: "${auth:aws}"
          account: "${auth:aws.projectId}"
          region: us-east-1
          name: "myapp-hybrid-storage"
          allowOnlyHttps: true

      # GCP for data services
      data-cluster:
        type: gcp-gke-autopilot-cluster
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          location: us-central1
          gkeMinVersion: "1.33.4-gke.1245000"  # Check: gcloud container get-server-config --location=us-central1

      data-registry:
        type: gcp-artifact-registry
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          location: us-central1

      analytics-bucket:
        type: gcp-bucket
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          name: "myapp-analytics-data"
          location: US

Features: - AWS for compute-intensive workloads - GCP for data analytics and processing - Cross-cloud resource sharing - Unified DNS management - Cost optimization through best-of-breed services

Common Parent Stack Patterns

Environment Separation

Client Configuration (client.yaml) - Uses stacks: section: 

# client.yaml
schemaVersion: 1.0
stacks:
  development:
    type: cloud-compose
    parent: myorg/infrastructure
    config:
      min: 1
      max: 3
      uses: [shared-database, shared-storage]
      # Other stack configuration properties...
  staging:
    type: cloud-compose
    parent: myorg/infrastructure
    config:
      min: 2
      max: 10
      uses: [shared-database, shared-storage]
      # Other stack configuration properties...
  production:
    type: cloud-compose
    parent: myorg/infrastructure
    config:
      min: 5
      max: 100
      uses: [shared-database, shared-storage]
      # Other stack configuration properties...

Server Configuration (server.yaml) - Uses resources: section: 

# server.yaml
schemaVersion: 1.0
resources:
  resources:
    production:
      shared-database:
        type: aws-rds-postgres
        config:
          credentials: "${auth:aws}"
          account: "${auth:aws.projectId}"
          region: us-east-1
          name: "shared-prod-db"
          instanceClass: "db.r5.xlarge"
          allocateStorage: 100
          engineVersion: "14.9"
          username: "appuser"
          password: "${secret:DB_PASSWORD}"
          databaseName: "shared"
      shared-storage:
        type: s3-bucket
        config:
          credentials: "${auth:aws}"
          account: "${auth:aws.projectId}"
          region: us-east-1
          name: "shared-prod-storage"
          allowOnlyHttps: true

Shared Resource Configuration

resources:
  resources:
    production:
      shared-database:
        type: aws-rds-postgres
        config:
          credentials: "${auth:aws}"
          account: "${auth:aws.projectId}"
          region: us-east-1
          name: "shared-prod-db"
          instanceClass: "db.r5.2xlarge"
          allocateStorage: 100
          engineVersion: "14.9"
          username: "appuser"
          password: "${secret:DB_PASSWORD}"
          databaseName: "shared"
      shared-cache:
        type: gcp-redis
        config:
          projectId: "${auth:gcloud.projectId}"
          credentials: "${auth:gcloud}"
          location: us-central1
          tier: standard
          memorySizeGb: 4

Deployment Commands

Provision parent stack: 

sc provision -s devops

Update parent stack: 

sc provision -s devops --update

Best Practices

  • Use environment separation for development, staging, and production
  • Implement proper backup strategies for all data stores
  • Configure monitoring and alerting for all shared resources
  • Use least-privilege IAM policies for all service accounts
  • Implement network security with proper VPC and firewall rules
  • Use infrastructure as code for all resource definitions
  • Document resource dependencies and relationships
  • Plan for disaster recovery across regions or clouds
  • Monitor costs and implement cost optimization strategies
  • Use consistent naming conventions across all resources