Posts

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.

In Part I and Part II of this post we created AWS infrastructure required for hosting a TiddlyWiki website and added a custom domain name. The instructions are applicable to any other static site whether a blog, personal website, portfolio or a picture gallery.

In the previous post we created a TiddlyWiki site hosted on AWS S3. We have a fully functional website, but there are several things we would like to improve. First, the address of the site is long and hard to remember. Then, updating content by uploading a new version of your website using AWS web console is somewhat tedious. Finally, our website is not secure since it does not support the https protocol.

This is Part I of the series of posts on hosting static websites with Amazon Web Services. In this post I am going to walk you through the steps required to host your own TiddlyWiki website on Amazon Web Services. You don’t need to have any previous experience with AWS or install special software. We’ll get your site up and running in less than 20 minutes using just the browser.

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.