OSLS (Open-Source Serverless) Framework, currently at version 3.63.2, is a community-maintained, open-source fork of the Serverless Framework v3. It acts as a drop-in replacement for users who cannot or choose not to upgrade to Serverless Framework v4. The project primarily focuses on supporting AWS Lambda deployments, offering up-to-date compatibility with new AWS runtimes and bug fixes. It distinguishes itself by being lighter and faster than the original v3, having removed enterprise features (like Serverless Dashboard and Components), auto-updating, and unused dependencies. Maintained by the Bref community, its release cadence involves frequent patch and minor updates to ensure continued compatibility and security. It supports various languages including Node.js, TypeScript, Python, Go, and Java, leveraging an approachable YAML syntax for defining serverless applications and their infrastructure.
npm install oslsVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to install OSLS globally, define a basic AWS Lambda function with an API Gateway endpoint using `serverless.yml`, deploy it, invoke it, and then remove the deployed resources.
Migrate to Serverless Framework v4 if these features are critical to your workflow, or explore third-party monitoring and management solutions for your serverless applications.
Refactor your application to use standard Serverless Framework resources, cloud provider-native constructs (e.g., CloudFormation), or alternative infrastructure-as-code tools.
Ensure OSLS is installed globally using `npm install -g osls`. Always invoke commands directly via `serverless <command>` after global installation.
Users targeting other cloud providers (e.g., Azure, Google Cloud, Apache OpenWhisk) should use the original Serverless Framework v4 or provider-specific serverless deployment tools.
Install OSLS globally using `npm install -g osls`.
Configure your AWS credentials using `serverless config credentials --provider aws --key YOUR_AWS_ACCESS_KEY_ID --secret YOUR_AWS_SECRET_ACCESS_KEY`, or ensure environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`) or a valid AWS profile are set.
Review the `serverless.yml` file at the specified line and column for incorrect spacing or tabs. YAML requires strict indentation using spaces.
No dependency data recorded yet.