In a previous post, I described how I set up a Hugo site on AWS Amplify. One feature missing from this basic site is a contact form. Here, I consider how this can be implemented in an AWS context. A github repo with related content is here. Backend options One…

For a small project I’m working on, I wanted to set up content-oriented site comprising only of static content — Hugo was a natural choice. As I’m experimenting with AWS generally, I had a look at how AWS Amplify could be used to host it. …

In a previous post, I described how the widely use go-swagger module could be used in a Lambda/API Gateway context. A limitation of this solution, imposed by go-swagger is that it only supports Swagger/OpenAPI v2.0 (OpenAPI Specification 2 — OAS2); with OpenAPI v3.0 (OpenAPI Specification 3 — OAS3) support becoming…

AWS provides support for Swagger/OpenAPI defined REST APIs as well as a go runtime; however, it is not entirely clear how best to work with these, especially if you’re used to using go-swagger for go REST APIs in a non-AWS context. Here I describe how the API Gateway, go Lambda…

In a previous post, I described how I used Go on Frontend (FE) and Backend (BE) to create a simple Todo application: the FE was implemented using Vugu, the BE was implemented as Lambda functions on AWS — a secure Swagger defined API was used for FE/BE communication. …

In a previous post, I described how I added Swagger support to my sample Go fullstack application. Here, I describe how that solution was enhanced to provide API security. Adding API security involved a complete frontend rewrite and some reasonably well documented changes to the AWS API Gateway based backend…

In previous posts, I described how I put together a simple todo application which uses Go on the Frontend (FE) and AWS Lambda functions running Go on the Backend (BE). In the previous implementation, the FE-BE communication was done using the standard Go net/http mechanisms — creating a request, calling…

Advances in WebAssembly have made it possible to consider using languages other than Javascript (with node naturally) for so-called Full Stack Development — developing both the backend and frontend components of an application. This has been recognized by Microsoft with their very promising Blazor toolkit but has also been recognized…