<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Lambda on The IT Hollow</title>
    <link>https://theithollow.com/tags/lambda/</link>
    <description>Recent content in Lambda on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 04 Sep 2018 14:00:04 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/lambda/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS Custom Resources</title>
      <link>https://theithollow.com/2018/09/04/aws-custom-resources/</link>
      <pubDate>Tue, 04 Sep 2018 14:00:04 +0000</pubDate>
      <guid>https://theithollow.com/2018/09/04/aws-custom-resources/</guid>
      <description>&lt;p&gt;We love to use AWS CloudFormation to deploy our environments. Its like configuration management for our AWS infrastructure in the sense that we write a desired state as code and apply it to our environment. But sometimes, there are tasks that we want to complete that aren&amp;rsquo;t part of CloudFormation. For instance, what if we wanted to use CloudFormation to deploy a new account which needs to be done through the CLI, or if we need to return some information to our CloudFormation template before deploying it? Luckily for us we can use a Custom Resource to achieve our goals. This post shows how you can use CloudFormation with a Custom Resource to execute a very basic Lambda function as part of a deployment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Step Functions</title>
      <link>https://theithollow.com/2017/01/17/aws-step-functions/</link>
      <pubDate>Tue, 17 Jan 2017 15:01:40 +0000</pubDate>
      <guid>https://theithollow.com/2017/01/17/aws-step-functions/</guid>
      <description>&lt;p&gt;This year at AWS re:Invent Amazon announced a new service called &lt;a href=&#34;https://aws.amazon.com/step-functions/&#34;&gt;Step Functions&lt;/a&gt;. According to AWS, Step Functions is an easy way to coordinate the components of distributed applications and microservices using visual workflows. That pretty much sums it up! When you&amp;rsquo;ve got a series of small microservices that need to be coordinated, it can be tricky to write this code into each lambda function to call the next function. Step Functions gives you a visual editor to manage the calls to multiple Lambda functions to make your life easier. I&amp;rsquo;ve written about this before on the &lt;a href=&#34;https://www.thinkahead.com/blog/visual-orchestration-aws/&#34;&gt;AHEAD blog&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Execute vRO Workflow from AWS Lambda</title>
      <link>https://theithollow.com/2016/07/26/vro_from_aws_lambda/</link>
      <pubDate>Tue, 26 Jul 2016 14:00:15 +0000</pubDate>
      <guid>https://theithollow.com/2016/07/26/vro_from_aws_lambda/</guid>
      <description>&lt;p&gt;The use cases here are open for debate, but you can setup a serverless call to vRealize Orchestrator to execute your custom orchestration tasks. Maybe you&amp;rsquo;re integrating this with an &lt;a href=&#34;http://amzn.to/2a0VHhe&#34;&gt;Amazon IoT button&lt;/a&gt;, or you want voice deployments with &lt;a href=&#34;http://amzn.to/2a0VFG8&#34;&gt;Amazon Echo&lt;/a&gt;, or maybe you&amp;rsquo;re just trying to provide access to your workflows based on a CloudWatch event in Amazon. In any case, it is possible to setup an Amazon Lambda call to execute a vRO workflow. In this post, we&amp;rsquo;ll actually build a Lambda function that executes a vRO workflow that deploys a CentOS virtual machine in vRealize Automation, but the workflow could really be anything you want.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
