Book Image

Building Serverless Web Applications

By : Diego Zanon
Book Image

Building Serverless Web Applications

By: Diego Zanon

Overview of this book

This book will equip you with the knowledge needed to build your own serverless apps by showing you how to set up different services while making your application scalable, highly available, and efficient. We begin by giving you an idea of what it means to go serverless, exploring the pros and cons of the serverless model and its use cases. Next, you will be introduced to the AWS services that will be used throughout the book, how to estimate costs, and how to set up and use the Serverless Framework. From here, you will start to build an entire serverless project of an online store, beginning with a React SPA frontend hosted on AWS followed by a serverless backend with API Gateway and Lambda functions. You will also learn to access data from a SimpleDB database, secure the application with authentication and authorization, and implement serverless notifications for browsers using AWS IoT. This book will describe how to monitor the performance, efficiency, and errors of your apps and conclude by teaching you how to test and deploy your applications.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Setting up Route 53


Route 53 is a DNS management service. You don't need to use it if you want to expose subdomains, such as www.example.com, however, it is indeed obligatory if you want to serve your website data under a naked domain, such as example.com, hosted on S3 or CloudFront. This is due to the RFC rule: you can't have a CNAME record for your domain root, it must be an A record.

What's the difference? CNAME and A records are both record types that help the DNS system to translate a domain name into an IP address. While CNAME references another domain, an A record references an IP address.

So, if you don't want to use Route 53, you can use your own domain management system, such as GoDaddy, to add a CNAME that will map your www.example.com domain to an S3 endpoint, for example, www.example.com.s3-website-us-east-1.amazonaws.com. This configuration works fine, but you can't do the same for example.com because the IP address of the example.com.s3-website-us-east-1.amazonaws.com domain...