Making secrets from Key Vault available to your application as environment variables
If you are using Kubernetes to deploy your microservices, at some point you will have to think about how to handle your secrets. With secrets, I mean for example credentials for your data services or certificates that your services need to gain access to other services. You don’t want to hard code secrets in your code because it restricts you in terms of flexibility and it is an anti-pattern to add them to your source control.
In the cloud world of volatile microservices, it is a good practice to inject any kind of config through environment variables according to the…
Experience report from a project with a big industry company
Note: I drafted this post about 3 years ago. I don’t know why I never published it. Some days ago I already published a post with a similar history. As I want to bring my blogging activity back to life I will keep finishing up and publishing older drafts besides writing completely new ones. I didn’t further edit the draft besides removing todo comments and correcting some typos. Just keep in mind that stuff may be out of date and have fun.
I am so happy to see that more and more big companies, which used to have heavyweight processes…
Note: I drafted this post about 3 years ago. I really don’t know why I ever published it. Today I stumbled upon it as I checked what is in my draft folder :). So Without further editing I decided to just publish it. Just keep it mind that stuff may be out of date. Have fun!
In the last few months I got the opportunity to engineer a cloud native application using the Serverless Framework and cloud native AWS services like Lambda, Step Functions and API Gateway.
In this article I want to share my experiences and lessons learned with…
This is the first article in the Azure Functions series. We will start easy, showing how you create your first Azure Function with Visual Studio and C#. In the following blog posts we will dive into more interesting and complex topics.
Prerequisites
There are very less Prerequisites for getting started with this simple Hello World Function. You could use any IDE or editor you want, but we will use Visual Studio to make things easy. So prerequisites are the following:
- .Net Core Framework installed
- Visual Studio installed
- Azure Account
Getting Started
We will directly dive in with the following steps:
- Open Visual Studio
- …
In my first article about chaining Lambda Functions, I showed how you can invoke a Lambda from another Lambda Function by directly invoking it. This time we will decouple it a little bit by using a Message Queue(the Message Queue Service of AWS is called SNS, short for Simple Notification Service) to realize the invocation.
TL;DR
Here you can find a GitHub repository if you want a quick start
Prerequisites
At least for the prerequisites you should check my previous article
Create Lambda Function
Now we are good to go, so lets create a new project using the Serverless Framework
Bootstrap Project
First create a…
In the company I am working for right now, Kanban is the methodology we implement in order to do agile software engineering. The agile management tool, that is used at the moment is Kanbanery and to be honest IMHO it sucks. I don’t want to blame the engineers of Kanbanery here, but the tool simply doesn’t meet my personal demands on an agile project management tool.
As I am in a leading position I will push the replacement of Kanbanery at least for my team. …
If you start coding with the Serverless Framework you will come to a point where you have several Lambda Functions and maybe Step Functions. Anyway you will notice that the size of the deployment artifact soon gets very big. For me it was something about 26MB, which is way to much for some hundred lines of JavaScript Code, right? By the way with my connection at home I was not able to deploy the stuff on AWS anymore because it ran in timeouts.
Luckily I found the serverless optimize plugin which shrank my deployment artifact from about 26MB to something…
In one of my last articles I showed how to chain Lambda Functions which means to invoke one Lambda Function from another one. This time I want to show you how you can invoke a Step Function from a Lambda Function using the Serverless Framework.
A use case for this kind of a setup is if you for example have a Step Function which should be invoked after receiving a request through an AWS API Gateway and want to let’s say validate the requests.
TL;DR
Here you can find a GitHub repository if you want a quick start.
Prerequisites
In this article I want to show how to chain AWS Lambda Functions which basically means calling a Lambda Function from another Lambda Function using the Serverless Framework.
TL;DR
Here you can find a GitHub repository if you want a quick start.
Prerequisites
At least for the prerequisites you should check my previous article.
Create Lambda Function
Now we are good to go, so lets create a new project using the Serverless Framework
Bootstrap Project
First create a project
serverless create --template aws-nodejs --path lambda-chainingMove to the generated project and a dependency to the aws-sdk module
npm install --save aws-sdkPrepare Environment
The Serverless…
In this article I will show you how you can reference a Lambda or a Step Function out of a Lambda Function. You will need that if you want to call a Lambda or Step Function out of a Lambda Function, obviously.
If you have read my last articles, and had a look a the respective GitHub repositories you may have noticed, that already I used each referencing a Lambda Function and a Step Function out of another Lambda Function. Anyway I decided to write a dedicated article about this topic. So this time — in contrast to the last…
Noah Ispas
Software Engineering Magician @dataone. Cloud Native Engineering. Agile Evangelist. DevOps Philosopher. Mindset and Culture first, Process and Technology second
