|AWS Lambda For The Impatient Part 3|
|Written by Nikos Vaggalis|
|Monday, 20 February 2017|
Page 2 of 2
Paws once more showcases its versatility catering for this case also, through Paws::STS, the Perl interface to the AWS Security Token Service.
We'll now use those to fill the corresponding environmental variables from which Paws is going to draw in order to make the call:
Hence, Paws does not just render the calling of an AWS Lambda function easy, but dies it for any AWS service in general. It is just a matter of pinpointing the same named as the service module and go through its documentation to find out how it is called.
Of course, to get to the step of making the actual call, a lot of initial background work has to be done.
It's what we set out to do in this three-part tutorial series, aiming not just at an overview of AWS Lambda's infrastructure, but rather going through the whole set of steps necessary, before we even attempted to make the function's call.
Therefore, we started our exploration with setting up users and roles, policies and permissions, role-based as well as user-based authentication, accessing the lambda through public HTTP endpoints and finally accessing the lambda programmatically by leveraging NodeJs on the server and Perl on the client.
What's more, the AWS free tier makes it pretty easy to get started, so why don't you give it a try?
Paws - Perl AWS SDK Update on SlideShare
AWS Lambda For The Impatient Part 1
AWS Lambda For The Impatient Part 2
To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin.
or email your comment to: firstname.lastname@example.org
|Last Updated ( Tuesday, 21 February 2017 )|