Keeping the keys to the castle safe

A while back we went along to an Amazon Web Services (AWS) Serverless workshop in London. One of the presenters was discussing how many keys and secrets they regularly find on Github. For those of you who don’t know, these keys really are the keys to the castle and in the wrong hands could cost you a lot of money.

As newbies we were finding keys all over our source code…

First of all you can end up with credentials in a file: aws-lambda-tools-defaults. This is produced as a result of publishing your projects to AWS via the AWS Visual Studio toolkit and because we were storing credentials as environment variables. To stop that we added a credentials class to our c# lambda code. A bit better as we could wrap different keys with compiler pragmas and we added this class to our gitignore file. So, was I sitting there all smug? No, not really, it still felt like too many things to remember….…..

Moving to a microservices architecture on Amazon Web Services (AWS)

In this blog we are going to share our experiences of developing solutions on AWS.

After Premise was started with the aim to provide small business with solutions that had traditionally been restricted to large enterprises, at an affordable price point.

We took a fairly momentous decision to review, top to bottom, our whole application design, development, test and delivery process. Although a young business we felt we needed provide our customers with better, lower cost solutions with a shortened time to market.