When I opened the AWS Blocks repository this morning (Japan time), the URL had changed.
I have been contributing to aws-devtools-labs/aws-blocks since the public preview started in June, so this was a bit of a surprise.
It moved from aws-devtools-labs to the
awsorganization? And the name is CDK Blocks?
re:Invent is just around the corner, so a lot tends to happen at this time of year.
Judging from the public GitHub Actions logs, the transfer happened shortly before 20:00 UTC on November 18, 2026. A CodeQL job that ran at 19:58 UTC still checked out aws-devtools-labs/aws-blocks, while a Dependabot job at 20:00 UTC already targeted aws/cdk-blocks. That Dependabot job received the response "Repository 'aws/cdk-blocks' is disabled.", which suggests the transfer was still in progress at that moment.
This is not an official AWS announcement. It is a quick write-up of what can be read from the public repository and its pull requests. At the time of writing (November 19, 2026, Japan time), I could not find any official announcement from AWS. The repository has moved and the code has started to be renamed, but the README and the documentation have not been touched yet. Please read this as a report on the very first signs of a rename.
What we know so far
- The repository moved from
aws-devtools-labs/aws-blockstoaws/cdk-blocks. The old URL redirects to the new one. - The product is heading toward the name "CDK Blocks". A pull request from the development team says, "The product is being renamed to CDK Blocks."
- The README and the documentation are still untouched. The README heading is still "AWS Blocks (Preview)" and the name CDK Blocks does not appear in it yet. The documentation is still the "AWS Blocks Developer Guide".
- The npm packages are still
@aws-blocks/*, and no packages under the new names have been published yet. - Pull requests with breaking changes to package names, environment variables, and folder names are concentrated around the time of the transfer.
In short, the rename has only just begun, and any impact on users' code will come with future releases. That is as far as I think we can say right now.
What happened around the transfer
The transfer itself takes a moment, but the rename work inside the repository had started the day before. Here are the related pull requests in UTC.
| Time (UTC) | Change | Status |
|---|---|---|
| 11/17 23:18 | Rename the Kotlin Gradle plugin's extension and tasks to cdkBlocks (#1593) |
Merged |
| 11/18 09:47 | Rename the AWS_BLOCKS_* environment variables to CDK_BLOCKS_* (#1602) |
Merged |
| 11/18 14:24 | PR opened to rename the npm packages to @aws-cdk-blocks/* and the umbrella package to aws-cdk-blocks (#1627) |
In review |
| 11/18 19:58-20:00 | Repository transferred to aws/cdk-blocks
|
|
| 11/18 20:18 | Update CODEOWNERS for the move (#1645) | Merged |
| 11/18 21:41 | Rename .blocks-sandbox to .cdk-blocks-sandbox (#1644) |
Merged |
| 11/18 21:52 | Point the GitHub OIDC trust policy at the new repository name (#1647) | Merged |
There are also #1630, which renames the generated backend folder from aws-blocks/ to cdk-blocks/, and #1607, which renames the hidden local data folder from .blocks to .cdk-blocks. Both are still in review.
On the product name, the description of #1602 includes this sentence:
The product is being renamed to CDK Blocks, so the
AWS_BLOCKS_*environment variables no longer match the name customers see.
So "CDK Blocks" is not a name I guessed from the repository name. It is the name the development team itself uses in its pull requests.
What the aws organization and the CDK name suggest
The destination, the aws organization, is where repositories such as the AWS CDK and the AWS CLI live. The source, aws-devtools-labs, has "labs" in its name, and it gave me the impression of a place for experimental developer tool projects. The project has moved from there to the organization that hosts AWS's major open-source projects.
The CDK in the new name also fits how Blocks works. As I described in a previous post, Blocks runs the same code differently depending on the execution context, and at deploy time it generates CDK constructs.
The rename work also includes changes that tie Blocks more closely to CDK. The description of #1602 says that the opt-out for usage data collection (telemetry) will no longer be a Blocks-specific environment variable but will merge into CDK's own CDK_DISABLE_CLI_TELEMETRY. That change itself is in progress in #1606 (in review at the time of writing).
Putting this together, it seems natural to read this as Blocks being promoted from an experimental project to a member of the CDK family. The move from a labs organization to aws, a name that carries CDK, and the merge of the telemetry setting into CDK all point in the same direction. That said, the README still says "Preview", and public information does not tell us when the preview will end or whether it will become generally available (GA). Whether anything will be announced at re:Invent included, I will wait for an official announcement on its formal positioning.
Changes likely to affect users
At the time of writing, existing projects should not break. The old URL redirects, the latest npm release is from November 2, and the package names are still @aws-blocks/*. The documentation can still be read at the AWS Blocks Developer Guide URL. The badges and links in the README also still point to aws-devtools-labs/aws-blocks.
None of the rename pull requests above have been released to npm yet, including the merged ones. Your project will be affected when they are included in a future release and you upgrade to that version.
The biggest change is probably the npm package rename (#1627). Code that imports from @aws-blocks/blocks will need to be rewritten to use aws-cdk-blocks or @aws-cdk-blocks/*. According to the description of #1627, there are about 1,500 import specifiers to rewrite in the repository alone. The PR also notes that because the umbrella package becomes an unscoped name, tooling in the repository that identified packages by checking whether the name starts with @aws-blocks/ would silently miss the umbrella package, without raising any error. It is worth checking whether your own project handles package names as strings anywhere.
Next is the environment variable change (#1602). AWS_BLOCKS_DISABLE_TEMPLATE_METADATA and AWS_BLOCKS_FRAMEWORK_SINK move to CDK_BLOCKS_*, and the old names are no longer read. There is no fallback to the old names, so if you set them in CI or scripts, you will need to update them along with the release.
If the folder renames (#1630, #1607) land, the structure of generated projects will change as well. How to migrate existing projects is something to check in the release notes once they are merged.
Breaking changes during a preview are nothing unusual. But with this many name-related changes landing together, it would be safer to review the changes (the changesets) more carefully than usual before upgrading to the next release. If you have automated dependency updates enabled, keep an eye out so they are not pulled in without review.
GitHub OIDC is something a redirect does not fix
Among these pull requests, the one likely to matter to anyone who transfers a repository is #1647.
When you transfer a repository, GitHub redirects access from the old URL. Browsing, git clone, and git push all keep working with the old URL.
GitHub Actions authenticating to AWS through OIDC, however, is not covered by the redirect. The token that GitHub issues carries the current repository name, as in repo:aws/cdk-blocks:environment:<env>. The IAM role trust policies in AWS, on the other hand, had the old name pinned, as in repo:aws-devtools-labs/aws-blocks:environment:<env>. Because the names did not match, the step that obtains AWS credentials failed, and according to the description of #1647, E2E tests were blocked on every open pull request.
On top of that, merging the pull request does not fix it by itself. The stack that defines the trust policies is deployed by hand rather than by CI, so someone with the right permissions has to redeploy it to each E2E AWS account, the description says.
When you transfer or rename a repository, you should check the sub condition in your IAM role trust policies at the same time. The redirect makes it easy to miss, and the failures show up in places you usually do not look at during a transfer, such as deployments and E2E tests.
Impact on contributors and forks
GitHub's documentation explains that when a repository is transferred, its issues, pull requests, wiki, stars, and watchers move with it, and forks remain associated with the repository after the transfer.
In fact, the pull requests I had opened, including the ones still in review, moved to aws/cdk-blocks as they were. Contributors who open pull requests from forks probably do not need to stop working because of the transfer itself.
Local clones also keep working with the old URL thanks to the redirect. However, the same documentation strongly recommends updating the remote URL of existing local clones. It also says the redirect is permanently deleted if a repository or fork with the same name is created at the old location. Rather than relying on the redirect, it is safer to switch early.
git remote set-url origin git@github.com:aws/cdk-blocks.git
If you have pull requests that are not merged yet, there are two more things worth keeping in mind.
The first is the cause of CI failures. As #1647 describes, right after the transfer, E2E tests on every open pull request failed at authentication. Until the trust policies are redeployed, a failing E2E run does not necessarily mean your change is the cause.
The second is conflicts with the rename pull requests. #1627 rewrites about 1,500 imports in the repository, so once it is merged, pull requests that touch files containing imports are likely to conflict. The same goes for the folder renames in #1630 and #1607. Once these are merged, you will probably need to bring your branch up to date with the latest main.
Closing thoughts
What looked like a single URL change this morning turned out, once I followed the pull requests, to be part of a coordinated effort: rename work had started the day before, and a fix for CI authentication landed right after the transfer. With CDK in the name and the project now in the aws organization, where Blocks belongs within AWS has become easier to see than before.
Still, what we can see so far is only the beginning of the rename. The README and the documentation are untouched, and there is no official explanation from AWS about the product name or its future. This post covers only what can be read from the repository, so if an official announcement comes out, please treat it as the source of truth.
re:Invent is almost here. As one of the contributors, I am looking forward to seeing what gets announced for CDK Blocks.
Top comments (0)