Step Functions

Introduction AWS Step Functions are a powerful way to express long-running, complex workflows comprised of Lambda functions. With Sparta 0.20.2, you can build a State Machine as part of your application. This section walks through the three steps necessary to provision a sample “Roll Die” state machine using a single Lambda function. See SpartaStep for the full source. Lambda Functions The first step is to define the core Lambda function Task that will be our Step function’s core logic. »


AWS Lambda Limitations Lambda is not yet globally available. Please view the Global Infrastructure page for the latest deployment status. There are Lambda Limits that may affect your development It’s not possible to dynamically set HTTP response headers based on the Lambda response body: Similarly, it’s not possible to set proper error response bodies. »


CloudFormation How do I create dynamic resource ARNs? Linking AWS resources together often requires creating dynamic ARN references. This can be achieved by using cloudformation.Join expressions. For instance: import ( gocf "" ) s3SiteBucketAllKeysResourceValue := gocf.Join("", gocf.String("arn:aws:s3:::"), gocf.Ref(s3BucketResourceName), gocf.String("/*")) import ( gocf "" ) AuthorizerURI: gocf.Join("", gocf.String("arn:aws:apigateway:"), gocf.Ref("AWS::Region").String(), gocf.String(":lambda:path/2015-03-31/functions/"), gocf.GetAtt(myAWSLambdaInfo.LogicalResourceName(), "Arn"), gocf.String("/invocations")), See the CloudFormation Fn::GetAtt docs for the set of attributes created by each resource. CloudFormation pseudo-paramters can be included in dynamic expresssions via gocf. »