By: Alex Demitri, Daniel Richardson

Image for post
Image for post

At Edelman Financial Engines, we have a vast array of platforms and servers. Our infrastructure is rather elegant but at the same time complex, making the need for reliable replication paramount. The challenges associated with maintaining an immutable infrastructure, also pose questions of scale and security.

While it is obviously crucial for us to maintain our infrastructure replicable and codified, we also want to

make sure we are able to consistently test and ship security remediations in the fastest and most reliable way possible.

In AWS (or any cloud provider for that matter), it all starts with a strong and secure foundation: the image bakery.


By: Shashank Anumula, Amit Naik

Image for post
Image for post

At Financial Engines, we are big fans of AWS and the “Serverless Paradigm” where we do not have to provision servers, in the form of EC2 instances, in order to get all the benefits of the cloud, such as on-demand scaling and per-call pricing.

DynamoDB is a popular NoSQL database offering from AWS that integrates very nicely in the serverless eco-system. It is a fully managed, auto-scaling, serverless NoSQL Database based on Amazon’s 2007 Dynamo paper [1].
An additional bonus is that it integrates well with AWS Lambda and S3, making DynamoDB the default choice for projects that can be rapidly deployed to production. …


by Ivonne Roberts

Image for post
Image for post

AWS has announced support for SQS triggered events on AWS Lambda. For companies embracing a serverless architecture this opens up new possibilities for event-driven architecture, streamlining batch infrastructure and much more.

Before the feature launched, if you were a serverless shop that needed to process SQS messages, the only option was to use CloudWatch to trigger a Lambda function, that polled for messages and then either fanned out workers or chewed threw batches of SQS messages. While this worked, it was prone to error. A Lambda function can only live for 5 minutes, at which point it could either spin up another Lambda function and pass the torch or simply wait for CloudWatch to trigger another Lambda function. …