Home / Guides

Infrastructure Composer standalone console shutdown: Dec 7, 2026

THE TAKEAWAY

The standalone AWS Infrastructure Composer console at console.aws.amazon.com/composer shuts down on December 7, 2026. AWS has not accepted new customers since October 29, 2026. Existing customers can keep using the standalone console until the shutdown. The same visual authoring experience stays available in the AWS Toolkit for Visual Studio Code. CloudFormation templates and existing stacks are not affected.

Key datesWhat shuts down on December 7, 2026What is not affectedHow to transition to the Toolkit

Last checked against AWS documentation:

Key dates

MilestoneDateWhat AWS says happens
AnnouncementSep 29, 2026AWS announced that the standalone console would end support, and listed Infrastructure Composer among services entering sunset.
New customers blockedOct 29, 2026AWS no longer accepts new customers. Accounts signed up before this date keep access during the transition period.
Standalone console shutdownDec 7, 2026The standalone console at console.aws.amazon.com/composer will no longer be accessible.

What shuts down on December 7, 2026

  • The standalone Infrastructure Composer console ends support and is shut down.
  • The standalone URL console.aws.amazon.com/composer will no longer be accessible after that date.
  • If you only use the web console today, you need to move that work to the AWS Toolkit for Visual Studio Code before December 7, 2026.

What is not affected

  • CloudFormation templates stored in Amazon S3 or on a local file system.
  • Existing CloudFormation stacks, deployments and workflows, which AWS says continue to work normally.
  • The Infrastructure Composer visual authoring experience in the AWS Toolkit for Visual Studio Code. AWS says that integration retains the full experience, with no changes planned at this time. If you already work in the Toolkit, no action is required.
  • There are no customer-facing APIs, SDKs, CLI commands or backend service endpoints to decommission.

How to transition to the Toolkit

AWS recommends moving standalone-console work to the AWS Toolkit for Visual Studio Code, where the same drag-and-drop canvas and code editor remain available locally in your IDE.

  1. Download and install the AWS Toolkit for Visual Studio Code.
  2. Open any CloudFormation or AWS SAM template in VS Code, then choose the Infrastructure Composer button in the upper-right corner of the editor.
  3. Or open the context (right-click) menu on a template file and choose Open with Infrastructure Composer. The Toolkit user guide currently labels this context-menu item Open with App Composer.
  4. Or use the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for AWS Infrastructure Composer.

Changes in other AWS consoles

  • CloudFormation console. Infrastructure Composer was available there as a visual tool for composing and visualizing templates during stack creation and updates. AWS is replacing that embedded experience with an improved visual editor component in the CloudFormation console. Stacks and templates are not affected.
  • Lambda console. The Export to Infrastructure Composer button will be removed. Lambda functions and their configurations are not affected.
  • Step Functions console. The Export to Infrastructure Composer option in the Actions dropdown on the state machine details page will be removed. All other Step Functions console functionality remains available.

If you still have a September 29, 2027 date

AWS's Services in Sunset table previously listed September 29, 2027 as Infrastructure Composer's end of support date, the same 12-month window used for other services announced that day. The table now lists December 7, 2026, which is the date AWS's Infrastructure Composer documentation and the September 29, 2026 service-availability announcement already used for the standalone console. Plan around December 7, 2026.

Sources

FAQ

When does the standalone Infrastructure Composer console shut down?

December 7, 2026, per AWS's Infrastructure Composer end-of-support documentation, the Services in Sunset table, the September 29, 2026 service-availability announcement, and the product page.

Can new accounts still start using the standalone console?

No. AWS stopped accepting new customers on October 29, 2026. Existing customers whose accounts were signed up before that date keep access until December 7, 2026.

Do I need to do anything if I already use Infrastructure Composer in VS Code?

No. AWS says the Toolkit integration continues to work and that no changes are planned for it at this time.

Will my CloudFormation templates or stacks be deleted or stop working?

No. Templates stored in Amazon S3 or on your local file system, and existing CloudFormation stacks, deployments and workflows, are not affected.

What happens to the standalone console URL?

AWS says console.aws.amazon.com/composer will no longer be accessible after December 7, 2026.

Why did some AWS pages list September 29, 2027?

The Services in Sunset table previously listed September 29, 2027, a typical 12-month sunset window. That table now lists December 7, 2026, matching the service documentation and the original announcement for the standalone console.

More guides