Serverless architectures have revolutionized cloud development by minimizing infrastructure management, enhancing scalability, and accelerating application time-to-market. However, these advantages come with organizational challenges such as security, observability, testing, and governance as it builds more services.

Over the past four years, CyberArk, a leading identity security SaaS provider, has successfully scaled its serverless operations. Starting with a core team of ten developers, we have expanded to hundreds while upholding high-quality and best-practice standards. The adoption of self-service serverless blueprints facilitated this expansion.
Serverless blueprints are essential tools platform engineering teams provide to foster the adoption of serverless technology. They streamline the setup and configuration process, integrating testing, Infrastructure as Code (IaC) best practices, and enhanced security and observability into serverless services. Despite these benefits, adopting these blueprints can encounter organizational hurdles. Challenges include developers' resistance, user experience issues, inadequate automation, and insufficient documentation.

In this session, you will learn what constitutes a practical serverless blueprint and use examples from the "AWS Lambda handler cookbook" open-source blueprint. In addition, you will discover strategies to broaden blueprints' acceptance across your organization.

In this session I will provide my experience as an architect in the platform engineering division at CyberArk and an AWS serverless hero.
I will use examples from my open source serverless template which is the open source version of the blueprint we use at CyberArk:
https://github.com/ran-isenberg/aws-lambda-handler-cookbook which has over 450 github starts, 200 clones per month and thousands of views.
People can use the cookbook as a starting point for a serveless blueprint in their organizations.