Skip to main content

Upstream Analysis: Innovation Sandbox on AWS

Last Updated: 2026-03-06 Source: co-cddo/innovation-sandbox-on-aws Captured SHA: cf75b87

Executive Summary

The co-cddo fork of Innovation Sandbox on AWS is currently at version v1.1.4 (SHA cf75b87) and is 12 commits behind the upstream aws-solutions/innovation-sandbox-on-aws (SHA 18dce92). The fork contains no source code modifications -- CDDO uses an extension architecture with external satellite services rather than modifying the upstream codebase. The 12 missing upstream commits represent versions v1.1.5 through v1.2.1, including security patches, dependency upgrades, and a feature release (v1.2.0).


Fork Status

PropertyValue
Upstream URLhttps://github.com/aws-solutions/innovation-sandbox-on-aws
Upstream SHA18dce92
Fork SHAcf75b87
Commits Ahead0
Commits Behind12
Checked At2026-03-06
Fork Versionv1.1.4 (2025-12-16)
Upstream Versionv1.2.1

Divergence Diagram


Missing Upstream Changes (v1.1.5 -- v1.2.1)

The 12 commits behind upstream represent six releases: three security patch releases (v1.1.5--v1.1.7), a further patch release (v1.1.8), a feature release (v1.2.0), and a follow-up patch (v1.2.1).

v1.2.1

ChangeDetail
ReleaseNew patch release -- changelog details need investigation

This is the latest upstream tag (SHA 18dce92, branch release/v1.2.1). The specific changes in this release need to be reviewed against the upstream release notes.

v1.2.0

ChangeDetail
ReleaseFeature release (minor version bump) -- changelog details need investigation

As a minor version bump, v1.2.0 likely contains new features or significant changes beyond security patches. This release should be carefully reviewed before merging to understand any new functionality, configuration changes, or breaking changes.

v1.1.8

ChangeDetail
ReleasePatch release -- changelog details need investigation

v1.1.7 (2026-01-20)

ChangeDetail
aws-nuke upgradeUpgraded to v3.63.2, resolves SCP-protected log group deletion issues

This is operationally significant -- the aws-nuke upgrade fixes an issue where account cleanup fails on SCP-protected CloudWatch log groups, which directly affects the NDX sandbox pool account recycling workflow.

v1.1.6 (2026-01-12)

ChangeDetail
@remix-run/routerSecurity upgrade
glib2Security upgrade
libcapSecurity upgrade
python3Security upgrade

v1.1.5 (2026-01-05)

ChangeDetail
qs librarySecurity vulnerability fix

Version History

VersionDateTypeKey Changes
v1.2.1--PatchNeeds investigation
v1.2.0--FeatureMinor version bump -- needs investigation
v1.1.8--PatchNeeds investigation
v1.1.72026-01-20Securityaws-nuke v3.63.2 (SCP log group fix)
v1.1.62026-01-12Security@remix-run/router, glib2, libcap, python3
v1.1.52026-01-05Securityqs library vulnerability
v1.1.42025-12-16Securityaws-nuke CVE-2025-61729, CVE-2025-61727
v1.1.32025-12-10Securityjws, mdast-util-to-hast, curl, glib2, python3
v1.1.22025-11-20Securityjs-yaml, glob
v1.1.12025-11-14Bug fix + SecurityCost report group fix, libcap
v1.1.02025-10-29FeatureLease unfreezing, cost groups, lease assignment, account prioritisation, template visibility
v1.0.52025-10-09Bug fix + SecurityWAF SizeRestrictions fix, expat
v1.0.42025-08-22FeatureCloudFront access logs, eu-central-2 AppConfig layer
v1.0.02025-05-22InitialInitial release

Fork Code Divergence

Assessment: Zero source code divergence.

The co-cddo fork is a clean fork with no modifications to upstream source code. Analysis confirms:

  • No custom branches detected
  • No source file modifications
  • Configuration files (global-config.yaml, nuke-config.yaml) remain at upstream defaults
  • Git remotes correctly configured with both origin (co-cddo) and upstream (aws-solutions)

CDDO Extension Strategy

Rather than modifying the upstream codebase, CDDO extends ISB functionality through external satellite services that integrate via EventBridge:

This approach provides:

  1. Upstream compatibility -- no merge conflicts when pulling upstream changes
  2. Independent release cycles -- satellite services deploy independently
  3. Clean separation of concerns -- UK-specific logic stays outside the upstream codebase
  4. Easy upgrade path -- git merge upstream/main with no conflicts expected

Global Configuration (Deployed)

The ISB deployment uses the following global configuration (from source/infrastructure/lib/components/config/global-config.yaml):

SettingValue
Maintenance Modetrue
Max Budget$50 USD
Require Max Budgettrue
Max Duration168 hours (7 days)
Require Max Durationtrue
Max Leases Per User3 concurrent
Lease Record TTL30 days
Cleanup Failed Attempts to Quarantine3
Cleanup Success Attempts to Finish2

Upstream Solution Architecture

The upstream ISB solution consists of four CloudFormation stacks deployed across up to three AWS accounts:

StackAccountPurpose
AccountPoolOrg Management (955063685555)OU lifecycle, SCP management, account registration
IDCOrg Management or delegatedIAM Identity Center groups, SSO application
DataHub (568672915267)DynamoDB tables, AppConfig configuration profiles
ComputeHub (568672915267)Lambda functions, API Gateway, Step Functions, EventBridge, CloudFront

Key AWS Services Used

  • Frontend: CloudFront + S3 (Vite web application)
  • API: API Gateway + WAF + Lambda (RBAC-based REST API)
  • Data: DynamoDB (accounts, leases, templates) + AppConfig (global/nuke/reporting configs)
  • Events: EventBridge (lifecycle events) + SES (email notifications)
  • Cleanup: Step Functions + CodeBuild + aws-nuke Docker image
  • Auth: IAM Identity Center with SAML 2.0

Upgrade Recommendation

The fork should be updated to v1.2.1 to receive:

  1. New features and improvements (v1.2.0, v1.2.1) -- v1.2.0 is a minor version bump likely containing new features or significant changes. Both releases need changelog investigation before merging to understand any new functionality, configuration changes, or potential breaking changes.

  2. aws-nuke v3.63.2 (v1.1.7) -- fixes SCP-protected log group deletion failures during account cleanup. This directly impacts the NDX pool account recycling workflow and may be the cause of some accounts being stuck in the Quarantine OU.

  3. Patch release (v1.1.8) -- specific changes need investigation.

  4. Security patches (v1.1.5, v1.1.6) -- qs library vulnerability, @remix-run/router, glib2, libcap, python3 upgrades.

Before upgrading, the v1.2.0 release notes should be reviewed to assess whether new features require configuration changes or affect the CDDO satellite services (EventBridge event schemas, API changes, etc.).

The upgrade should be low-risk given zero code divergence. The recommended approach:

cd repos/innovation-sandbox-on-aws
git fetch upstream
git merge upstream/main
# Expected: fast-forward merge, no conflicts

References


Generated from source analysis on 2026-03-06. See 00-repo-inventory.md for full repository inventory.