Book Image

Building Serverless Architectures

By : Cagatay Gurturk
Book Image

Building Serverless Architectures

By: Cagatay Gurturk

Overview of this book

Over the past years, all kind of companies from start-ups to giant enterprises started their move to public cloud providers in order to save their costs and reduce the operation effort needed to keep their shops open. Now it is even possible to craft a complex software system consisting of many independent micro-functions that will run only when they are needed without needing to maintain individual servers. The focus of this book is to design serverless architectures, and weigh the advantages and disadvantages of this approach, along with decision factors to consider. You will learn how to design a serverless application, get to know that key points of services that serverless applications are based on, and known issues and solutions. The book addresses key challenges such as how to slice out the core functionality of the software to be distributed in different cloud services and cloud functions. It covers basic and advanced usage of these services, testing and securing the serverless software, automating deployment, and more. By the end of the book, you will be equipped with knowledge of new tools and techniques to keep up with this evolution in the IT industry.
Table of Contents (10 chapters)

Deploying our first Lambda with CloudFormation

In this section, we will create our first template and deploy the stack using our Gradle script. We can start writing our template by creating a text file named cloudformation.template in the root directory of our project:

    $ cd ~/serverlessbook
    $ touch cloudformation.template

In this section, we will be defining three CloudFormation resources:

  • The IAM role
  • A custom IAM policy to be attached to the role created earlier
  • A Lambda function

For the first resource, we can start with IAM Role, which our Lambda function will use for execution. In the first chapter, we briefly looked at what an IAM Role is. Let's assume that our Lambda function will access S3 buckets in our accounts. How we can allow our Lambda function to access S3 buckets as read-only but prevent it from writing to buckets? These permissions are configured...