Recently we decided to use AWS Amplify for one of the products we’re currently working on.

AWS Amplify promises to provide you with the option to rapidly develop the REST or a GraphQL based backend that’s very well integrated with your frontend development - be it a web application or a mobile app. That’s at least the marketed value proposition.

At Mbanq Cloud we run most of our services on AWS and try to use AWS Lambda as much as possible.

A while ago I’ve been working on the a small npm package that should have helped us to make use of SSM and KMS to manage our system configuration. SSM and KMS play nicely together as the most of the AWS services.

In order to test the newly written npm package, I had to mock the promisified version of the ssm.getParameters(request)

Everyone has its own view on how to organize the routes in a Single-Page Application-we’re not different.

Since we’re using Vue.js in our current project, we’re also using the Vue Router.

Here I would like to describe the approach we took to organize our router and its routes. We will probably change/improve the current state later on but for now I will describe the status quo.