CloudFront

In Parts I and II we created a fully functional TiddlyWiki website hosted on AWS. The only thing missing is the secure connection via https. Strictly speaking, it is not required for a Wiki website where all the content is publicly available. The secure connection does improve your site ranking with most popular search engines, though. As discussed below, there are additional costs in running a secure connection website. As a site owner you need to decide if the extra costs are justified.

Lambda@Edge can simplify your application architecture, decrease latency and improve response time. There are a number of appealing use-cases for Lambda@Edge including user authentication using JWT Tokens and signed cookies. In this post I am sharing ideas on how to pass parameters such as URLs, names and ARNs of AWS resources to a Lambda@Edge function when creating them from a CloudFormation or Serverless Application Model template. Like many developers I experienced this problem when I started working with Lambda@Edge.