L3 Workshop: 'ng' is not recognized as an internal or external command, operable program or batch file

Based on the information available, it appears you're encountering an issue with the Angular CLI (ng command) not being recognized during the AWS Blu Age L3 Workshop automation setup.

This error typically occurs when Angular CLI is either not installed or not properly added to your system's PATH environment variable. Since you're working on the automation project setup in the L3 Workshop, this is likely related to the browser application bundle generation step.

Here are some steps to resolve this issue:

1. Ensure that Node.js and npm are properly installed on your system.

2. Install Angular CLI globally by running:

npm install -g @angular/cli

3. Verify the installation by running:

ng --version

4. If Angular CLI is installed but still not recognized, you may need to add its location to your system's PATH environment variable.

5. After installing Angular CLI, restart your command prompt or IDE to ensure the changes take effect.

6. If you're running the automation through an Ant build in Eclipse (as is common in the L3 Workshop), make sure Eclipse is recognizing the updated PATH environment.

If the issue persists after these steps, you might need to check if there are specific version requirements for Angular CLI in the workshop documentation, as compatibility issues could arise with newer or older versions.
Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
AWS Blu Age L3 workshop -Automation Build Failed | AWS re:Post

The error is clear. your system has run out of disk space. You need to free up space before you can install Angular CLI. Try to clear npm cache

npm cache clean --force
npm cache verify

or use different installation of directory