Locally sync and save your project in the Application Composer console
This section provides information on using Application Composer's local sync mode to automatically sync and save your project to your local machine.
We recommend that you use local sync for the following reasons:
You can activate local sync for a new project, or load an existing project with local sync activated.
-
By default, you need to manually save your application template as you design. Use local sync to automatically save your application template to your local machine as you make changes.
-
Local sync manages and automatically syncs your project folders, backup folder, and supported external files to your local machine.
-
When using local sync, you can connect Application Composer with your local IDE to speed up development. To learn more, see Connect the Application Composer console with your local IDE.
What local sync mode saves
Local sync mode automatically syncs and saves the following to your local machine:
-
Application template file – The AWS CloudFormation or AWS Serverless Application Model (AWS SAM) template that contains your infrastructure as code (IaC).
-
Project folders – A general directory structure that organizes your AWS Lambda functions.
-
Backup directory – A backup directory named
.aws-composer, created at the root of your project location. This directory contains a backup copy of your application template file and project folders. -
External files – Supported external files that you can use within Application Composer. To learn more, see Reference external files in Application Composer.
Browser requirements
Local sync mode requires a browser that supports the File System Access API. For more information, see Allow web page access to local files in Application Composer.
Activating local sync mode
Local sync mode is deactivated by default. You can activate Local sync mode through the Application Composer menu.
For instructions on activating local sync and existing loading projects, see the following topics:.
