The case of the missing bucket notifications A few days ago I was trying to do something quite simple. I wanted to send S3 Put-Events to multiple Lambda functions for processing. This is a pretty common pattern. To implement it you have to use an architecture such as the one you can see in the title image above. This is because S3 has a limit on the event handlers (notification targets) per event type of exactly one.
Dissecting Serverless Stacks (IV)
After we figured out how to implement a
sls command line option to switch between the usual behaviour and a way to conditionally omit IAM in our deployments, we will get deeper into it and build a small hack on how we could hand over all artefacts of our project to somebody who does not even know SLS at all.
Dissecting Serverless Stacks (III)
The third post of this series showed how to make IAM statements an external file, so we can deploy that one but still work with the
sls command. It still involved commenting out things in the configuration, so this post will show how to solve that issue.
Dissecting Serverless Stacks (II)
With the output of the last post of this series, we established the base to be able to deliver a Serverless application independent of its needed IAM privileges. So let’s see how this will work out.
Dissecting Serverless Stacks (I)
This post establishes the base for a small series on how to create Serverless based Lambdas which can be deployed in environments without IAM privileges or where the
sls command cannot be used at all.
Automating ACM Certificate creation with the Serverless Framework Encryption is the basis for secure communication in our modern world. For most web applications this boils down to using HTTPS to encrypt traffic between the client and server. HTTPS or the underlying protocols TLS/SSL rely on Public Key Infrastructure and Encryption to establish the Authenticity of the communication partner. Authenticity in this context means that the client can be sure he is communicating with Google if they access https://google.