aws logo

AWS Week In Review: March 26 2018

- Updated March 26, 2018

Here’s your weekly breakdown of all things AWS…

Lambda Debugging Features Added to Browser-based IDE

Anyone that has worked with Lambda’s has felt the pain of debugging when something isn’t working correctly. Debugging in Lambda often feels like the stone age of programming with no good options available. Any deep effort usually devolves into a smattering of print statements and broken dreams.

When AWS’ acquisition of “IDE in the cloud” provider, Cloud9, was announced, we knew that some cool integrations were on the way. When the Cloud9 IDE showed up earlier this year right in the Lambda AWS Console, we knew that this was just the beginning. Now, full-fledged debugging tools like break statements and stack inspection are available to Lambda developers. It looks like this feature may only be available to Python functions for the moment, but it’s only a matter of time before these kind of features are available for other Lambda languages.

Below is a link on how to get started with debugging for your Python Lambda functions:

How to set up debugging for Python Lambda functions

You can also read more on the official announcement at this link:

Read more on Amazon’s Announcements

I think his name was Brainy?

Amazon Polly, AWS’ text-to-speech tool, now supports breathing sounds. It comes in two main flavors. First, you can choose to insert the breathing automatically to give a more natural feel to the speech. The second option is to manually insert breaths like so:

Here’s the markup language to produce that masterpiece:

<amazon:breath></amazon:breath> <amazon:breath></amazon:breath><amazon:breath></amazon:breath><amazon:breath></amazon:breath>


Read More on Amazon’s Announcements

Serverless Hosting Gets an Upgrade with new Lambda@Edge Features

I’ve been closely following Lambda@Edge for some time now. For those that don’t know, Lambda@Edge is this a kind of composite feature that glues together CloudFront, Lambda, S3, among other things. Simply put, this feature gives Engineers the ability to read, process, and even rewrite requests coming in through CloudFront edge locations like a classic Apache Rewrite Rule. Though, it is much more than that. Folks have built some interesting things and have gone as far as removing Nginx/Apache from their stack or even putting together a whole JSON Web Token system.

Now, Amazon has released more features that allow Lambda@Edge to read and respond to more HTTP headers coming through the request. Before this, it really wasn’t possible to serve different content based on these headers without setting up a web or even application servers. Now, this is done with Serverless tooling.

This isn’t a giant leap for Serverless, but it is yet another step in a long line of progression for this model. I’m still not 100% sold on Production-grade Serverless systems. However, I really like what I’m interpreting as a long-term commitment by AWS and other cloud providers. Features like this show that Serverless technologies have a strong future ahead.

Read More on Amazon’s Announcements


Other Notables