Skip to content

Releases: aws-samples/sample-developer-environment

v2.0.0 - Self-contained template with CodeCommit and Agent Toolkit for AWS

Choose a tag to compare

@hansmohob hansmohob released this 29 Aug 20:08
69bef87

Highlights

  • Fully self-contained: the EC2 setup script is embedded in the CloudFormation template as an SSM document. One file, no external downloads at boot. Re-run setup any time with aws ssm send-command
  • CodeCommit version control replaces git-remote-s3, with native CodePipeline integration and workspace recovery on instance rebuild
  • Agent Toolkit for AWS built in: the AWS MCP Server and curated AWS skills are configured automatically for Kiro IDE and Kiro CLI
  • Current tooling: AWS CLI v2 via the official installer, code-server 4.135.0, CodePipeline V2, .NET 10, all versions pinned and exposed as CloudFormation parameters
  • Numerous security and reliability fixes, including VPC flow logs delivery, SSM agent permissions, log group lifecycle management, and tightened bucket policies

Breaking changes

  • GitHubBranch parameter removed (the template no longer downloads its setup script from GitHub)
  • UvenvVersion parameter replaced by UvVersion
  • Redeploying with a prefix previously used by v1 may require a one-time cleanup of leftover runtime-created log groups

Upgrading from v1

v1 stacks cannot be updated in place to v2 (source control storage changed). Deploy v2 as a new stack and migrate workspace content via git. The v1 template remains available in the v1.0.0 release and requires GitHubBranch=v1 to deploy.

v1.0.0 - Final external-script release

Choose a tag to compare

@hansmohob hansmohob released this 29 Aug 04:11

This is the final release of the developer environment that bootstraps the EC2 instance by downloading devbox-setup.sh from GitHub at boot time.

Important note for users of this version

The CloudFormation template in this release downloads its setup script from the main branch by default. Since main now contains v2 (which removed devbox-setup.sh), you must set the GitHubBranch parameter to v1 when launching this template. The v1 branch is maintained at this release's commit so the script URL keeps resolving.

What's next

v2 embeds the setup script directly in the CloudFormation template as an AWS Systems Manager document, making the solution fully self-contained with no external downloads at boot.