Skip to main content
Active

Overview

SG-Infra was created as a cleaner, more maintainable replacement for the infrastructure patterns established in TalentIdPipeline-Infra-CDK. It is the target infrastructure pattern for all new and migrated cloud systems going forward.

Architecture

SG-Infra deployed infrastructure. Box colour shows the deploying stack; dashed grey is owned by TalentIdPipeline-Infra-CDK.
The diagram source is the draw.io file at images/software/developer/estate/infra/sg-infra/architecture.drawio. To change the diagram, edit that source in draw.io, re-export it as PNG to architecture.png in the same folder, and commit both.

Key Facts

What It Provisions

SG-Infra is a TypeScript AWS CDK project that defines dedicated infrastructure for systems that adopt it. It currently provisions:
  • A dedicated, larger and more powerful MongoDB EC2 instance, currently used exclusively by Fleet Management Platform
SG-Infra depends on TalentIdPipeline-Infra-CDK for the VPC and does not define its own network layer. All systems using SG-Infra therefore retain an indirect dependency on TalentIdPipeline-Infra-CDK.

Repositories

Systems That Depend On This

Dependencies

Infrastructure

  • TalentIdPipeline-Infra-CDK: SG-Infra depends on this repo for the VPC. It does not define its own network infrastructure.

Detailed Documentation

Architecture and Deployment Pipeline

The TypeScript CDK app, the GitHub sourced pipeline, the four stacks, and how a change reaches production.

MongoDB Instance and Data Volume

The Dockerised MongoDB, the persistent data volume, TLS, and provisioning.

Backups and Disaster Recovery

Versioned backups, retention, and the recovery picture.

Networking, Dependencies and Configuration Contract

The shared VPC dependency, security groups, and the published config.

Security, Risks and Relationship to the Legacy Pattern

Security posture, remaining risks, and how this improves on the legacy repo.

Notes

  • SG-Infra is the target infrastructure pattern for all future cloud systems. New systems should use this rather than adding to TalentIdPipeline-Infra-CDK.
  • Currently only used by Fleet Management Platform. The goal is to migrate all systems toward this pattern over time, though no migration timeline has been agreed.
  • A future improvement would be to define the VPC within SG-Infra itself, fully decoupling it from the legacy TalentIdPipeline-Infra-CDK repo.
Last modified on June 30, 2026