Book Image

Serverless Architectures with AWS

By : Mohit Gupta
Book Image

Serverless Architectures with AWS

By: Mohit Gupta

Overview of this book

Serverless Architecture with AWS begins with an introduction to the serverless model and helps you get started with AWS and Lambda. You'll also get to grips with other capabilities of the AWS Serverless Platform and see how AWS supports enterprise-grade serverless applications with and without Lambda. This book will guide you in deploying your first serverless project and exploring the capabilities of serverless Amazon Athena, an interactive query service that makes it easy to analyze data in Amazon Simple Storage Service (S3 Amazon) using standard SQL. You’ll also learn about AWS Glue, a fully managed ETL service that makes categorizing data easy and cost-effective. You'll study how Amazon Kinesis makes it possible to unleash the potential of real-time data insights and analytics with capabilities such as video streams, data streams, data firehose, and data analytics. Last but not least, you’ll be equipped to combine Amazon Kinesis capabilities with AWS Lambda to create lightweight serverless architectures. By the end of the book, you will be ready to create and run your first serverless application that takes advantage of the high availability, security, performance, and scalability of AWS.
Table of Contents (8 chapters)

Chapter 3: Building and Deploying a Media Application


Solution for Activity 4: Creating an API to Delete the S3 Bucket

  1. Go to the AWS API Gateway console and in the API created in this chapter, create a Delete API.

  2. Configure the incoming headers and path parameters properly in the Method Request and Integration Request sections.

    Your API configuration should look similar to the following screenshot:

    Figure 3.37: The DELETE method execution window

  3. Remember to change the authorization of the Delete method from NONE to AWS_IAM.

  4. Click on the Deploy API.

  5. Test the Delete method using the Test Tool (Ready API). Set content-type as application/xml:

    Figure 3.38: Output showing the bucket getting deleted

You should see the bucket getting deleted in the AWS S3 console.