Registry / devops / berlioz

berlioz

JSON →
library1.0.238jsnpmunverified

Berlioz is a CLI tool and framework for deploying containerized microservices applications to AWS public cloud. It uses a declarative YAML configuration to define application components and automatically provisions AWS resources like DynamoDB, Kinesis, and load balancers. Version 1.0.238 is the latest, with an unspecified release cadence. Key differentiators include automatic service discovery, multi-region support, local deployment simulation with cloud-native resources, and isolated deployments for staging. It targets developers who want to abstract cloud infrastructure complexity.

devops
npm install berlioz
github ↗package ↗homepage ↗
INSTALL
IMPORT
SIG · BERLIOZ
B
berlioz
devopsjavascriptv1.0.238
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

berlioz
✓ npm install berlioz -g
✗ npm install berlioz --save
Berlioz is a CLI tool meant to be installed globally. Using --save is unnecessary and will add it as a local dependency.
berlioz local push-run
✓ berlioz local push-run
✗ berlioz local push run
The command uses a hyphen, not a space between 'push' and 'run'.
berlioz provider create
✓ berlioz provider create --name myaws --kind aws --key <key> --secret <secret>
✗ berlioz provider add --name myaws --kind aws --key <key> --secret <secret>
The correct subcommand is 'create', not 'add'.

Installs Berlioz CLI, clones sample projects, and deploys HelloWorld locally.

npm install berlioz -g && git clone https://github.com/berlioz-the/samples.git && cd samples/01.HelloWorld/v1.basic && berlioz local push-run
Debug
Known issues
gotchaGlobal installation required - Berlioz must be installed globally with -g flag, not as a local project dependency.
fix
Install using `npm install berlioz -g` instead of `npm install berlioz`
affects: *
deprecatedThe berlioz signup command has been deprecated in favor of web-based registration.
fix
Register at https://berlioz.cloud instead of using CLI signup.
affects: >=1.0.200
breakingBerlioz only supports AWS cloud provider; other cloud providers like GCP are not supported.
fix
Use Berlioz solely for AWS deployments. For multi-cloud, consider alternatives like Terraform.
affects: *
gotchaYAML indentation errors in the berlioz.yml file lead to silent failures.
fix
Use a YAML linter and validate configuration with `berlioz validate` before deploying.
affects: *
Errors
Common errors & fixes
Error: Cannot find module 'berlioz'
Berlioz was installed locally instead of globally, or npm global path is not in PATH.
fix
Install globally: `npm install berlioz -g`. Ensure npm global bin directory is in PATH.
RequestExpired: The security token included in the request is expired
AWS credentials (key/secret) used with Berlioz provider have expired.
fix
Generate new AWS access keys and update the provider: `berlioz provider create --name myaws --kind aws --key <new-key> --secret <new-secret>`
Upgrade
Version history
1.0.238latest on npm
Audit
Dependencies
aws-sdkrequiredUsed to interact with AWS services for provisioning and management
dockerrequiredRequired for building and running containers
Agent activity
8 hits · last 30 days
node
6
Amazon
1
Resources
githubhttps://github.com/berlioz-the/berlioz ↗
packageberlioz ↗
homepagehttps://github.com/berlioz-the/berlioz.git#readme ↗
berlioz — npm install berlioz · libregistry