AWS Lambda Updates from Re:Invent

At the annual re:Invent, AWS announced several updates to its Function-as-a-Service offering Lambda. These newly announced features evolve around billing, memory capacity, and container image support.

The billing of any AWS service is an essential aspect with regards to TCO. The reduced billing granularity for Lambda function duration from 100ms down to 1ms will mean customers will be billed less for short-running functions. The company announced that the compute duration would be billed in 1ms increments instead of being rounded up to the nearest 100ms increment per invoke. The latter was the billing model since the launch of Lambda in 2014.

Danilo Poccia, a chief evangelist (EMEA) at Amazon Web Services, provide a sample in his blog post on the new 1ms billing granularity:

The Lambda monthly compute charges with the old 100ms rounded up pricing would have been:
60 million invocations* 100ms * 1G memory * $0.0000166667 for every GB-second = $100
With the new 1ms billing granularity, the duration costs are:
60 million invocations * 28ms * 1G memory * $0.0000166667 for every GB-second = $28

#aws lambda #cloud #aws #re:invent

What is GEEK

Buddha Community

AWS Lambda Updates from Re:Invent

AWS Lambda Updates from Re:Invent

At the annual re:Invent, AWS announced several updates to its Function-as-a-Service offering Lambda. These newly announced features evolve around billing, memory capacity, and container image support.

The billing of any AWS service is an essential aspect with regards to TCO. The reduced billing granularity for Lambda function duration from 100ms down to 1ms will mean customers will be billed less for short-running functions. The company announced that the compute duration would be billed in 1ms increments instead of being rounded up to the nearest 100ms increment per invoke. The latter was the billing model since the launch of Lambda in 2014.

Danilo Poccia, a chief evangelist (EMEA) at Amazon Web Services, provide a sample in his blog post on the new 1ms billing granularity:

The Lambda monthly compute charges with the old 100ms rounded up pricing would have been:
60 million invocations* 100ms * 1G memory * $0.0000166667 for every GB-second = $100
With the new 1ms billing granularity, the duration costs are:
60 million invocations * 28ms * 1G memory * $0.0000166667 for every GB-second = $28

#aws lambda #cloud #aws #re:invent

Cross-account access to invoke AWS lambda using AWS CDK

If you are here, you may have a pretty good knowledge of how to use AWS CDK for defining cloud infrastructure in code and provisioning it through AWS. So let’s get started on how to grant permission to your lambda function to access the resources in another AWS account.

Let’s say you have two accounts called Account A and Account B, and you need to give permission to lambda function in Account A (ex: 11111111)to access the resources in Account B(22222222). You can easily do this by assuming an IAM Role in Account B and then uses the returned credentials to invoke AWS resources in Account B.

#acces #account #aws #lambda #aws lambda #aws cdk

Cache secrets using AWS Lambda extensions

What is the AWS Lambda extension?

A month back AWS announced a preview of Lambda Extensions, a new way to easily integrate Lambda with your favorite monitoring, observability, security, and governance tools. Extensions can be published as Lambda layers, there are two types are extension:

  • Internal extensions → Run as part of the runtime process, in-process with your code. Internal extensions enable use cases such as automatically instrumenting code.
  • External extensions → Allow you to run separate processes from the runtime but still within the same execution environment as the Lambda function. External extensions can start before the runtime process and can continue after the runtime shuts down. These extensions run as companion processes to Lambda functions.

#aws #aws-secrets-manager #lambda #aws lambda

Rory  West

Rory West

1619143080

All The Libraries Launched At AWS re:Invent 2020, So Far

At the ongoing annual cloud conference, AWS re:Invent event, the e-commerce giant has been announcing a staggering number of product launches, tools, frameworks, services and more. From AI chips to enterprise applications, the event is covering all the aspects and addressing needs of a developer to build innovative products.

Here is a list of six libraries and tools, in no particular order, that was launched so far at the AWS re:Invent 2020.

SageMaker Distributed Data-Parallel (SDP)

AWS re:Invent 2020 introduced two new distributed training libraries for Amazon SageMaker, one of them is the SageMaker Distributed Data-Parallel (SDP). The libraries are meant to provide integrated methods for the users to quickly train large deep learning models. SageMaker distributed data-parallel extends SageMaker’s training capabilities on deep learning models with near-linear scaling efficiency in order to achieve fast time-to-train with minimal code changes.

#aws #aws libraries #aws re:invent 2020

Rory  West

Rory West

1621752780

Top 10 Quotes By Andy Jassy At AWS re:Invent 2020

The ninth edition of AWS annual event re:Invent has kickstarted on November 30, albeit virtually. This three-week event began with the keynote address from AWS CEO Andy Jassy, where he informed his listeners about making a $46billion revenue run rate as per Q3 2020 and achieving a YoY growth rate of 29% Q3 2019 vs Q3 2020.

His slightly over three-hour address was filled with some of the most important product and services announcements. Apart from these announcements, Jassy also made a few noteworthy remarks. We list some of the most memorable quotes here.

AWS’ Exponential Growth Over Years

Jassy started his keynote, giving an insight into the growth of AWS over the years. Pondering over the relatively slower progress in the initial days, he said, “It took us 123 months a little over 10 yrs to go to a 10 billion dollar business…”

Having said that, Jassy then stated that the growth accelerated with time. He said that it took the company took the next 23 months to reach a 20 billion revenue, 13 months to reach 30 billion, and then only 12 months to reach 40 billion mark.

#aws andy jassy #aws re:invent #aws