The wait is over, re:Invent is around the corner. Just like me, most AWS teams cannot contain their excitement and have started releasing new features. This week leading up to re:Invent, also known as AWS pre:Invent, is all about the new features that didn’t make the keynote. This doesn’t mean they’re not worth mentioning, so let’s run over our top 5 of most heartwarming new features.
- AWS Lambda destinations
- Java 11
- Cloudwatch ServiceLens
- Amazon CDK now available for Java and C#
- Cloudwatch Synthetics
So you’ve been writing reusable code for a while now. Or so you thought. To send your response to a consumer (e.g. SQS), you still had to write code to deliver the message specifically to that consumer. To mitigate this problem, AWS introduced Lambda destinations, a solution to send a lambda result to a consumer without writing application code. These consumers include: Lambda, SNS, SQS standard queue and EventBridge. Besides decoupling a part of your infrastructure, Lambda Destinations are supported in CloudFormation right from the start. (At the time of writing, DestinationConfig was not yet added to the CloudFormation documentation).
Read more about Lambda destinations.
With the release of Java 13 last september, it hit me that the bigger part of my production code is written in Java 8. This isn’t a bad thing, since Java 8 still has a couple years of support, but it got me thinking about why it was still so far behind. One of the major reasons was the lack of Java 11 support for Elastic Beanstalk. For lambda, this was not a problem, as my production lambdas are written in either Nodejs or Python. Well, AWS fixed both “problems” at once with the release of Java 11 support for Beanstalk and Java 11 support for Lambda. So go ahead and start writing those fancy Java 11 applications!
AWS provides a couple ways to monitor your application, wether it’s for logging purposes or application monitoring through AWS X-Ray. Cloudwatch ServiceLens ties these functionalities together to give you a complete overview of your application. Gain insights in your infrastructure health using metrics and logs, and utilize transaction monitoring to get an overview of multiple resources for a deeper dive into your application health.
AWS CloudFormation, one of the most glorious things Amazon has to offer, can be a burden sometimes. Writing your configuration in YAML or JSON can become a giant file that will become hard to read after a while. Some frameworks, like Troposphere and Serverless Framework, are doing a great job at relieving the pain and make resource configuration fun again. So last re:Invent, AWS came up with their own framework, the Cloud Development Kit. A tool for Python or Typescript to help with resource configuration and make the world a better place, who could ask for more? So the Java and C# developers united and asked for more; And AWS delivered, introducing Java and C# support for the CDK.
Read more about CDK for Java and C#.
Discover issues before your users do, wouldn’t that be amazing? AWS promises to bring you one step closer to Utopia with Cloudwatch Synthetics. Cloudwatch Synthetics runs tests on your application endpoints every minute, alerting you when endpoints don’t behave as expected. These tests, also called tasks, can consist of a couple flows, from latency testing to complex flows in your application. Endpoints can range from your REST endpoints to website content, to cover most of your workload before your customers get the chance to break it.