I have some exciting news to share with you about the Serverless Step Functions plugin.
One of the main pain points of using the plugin was that you needed to use fully-formed ARNs. We addressed this in v1.18.0 by supporting CloudFormation intrinsic functions
Ref. This makes it possible for you to reference a local function instead.
functions: hello-world: handler: hello-world.handler stepFunctions: stateMachines: myStateMachine: definition: StartAt: HelloWorld States: HelloWorld: Type: Task Resource: Fn::GetAtt: [HelloDashworldLambdaFunction, Arn] End: true
But this is still a leaky abstraction – you have to know how the Serverless framework converts local function names into CloudFormation logical IDs.
Newcomers would often get confused here.
“How did you get the logical ID
I can hardly blame them for not knowing. This is an implementation detail in the Serverless framework, one that you shouldn’t have to care about!
Which is why I’m really happy to tell you that, as of v2.2.0 you can reference local functions using their local names in the state machine definition.
In the above example, when we reference the local function
hello-world we no longer need to use its CloudFormation logical ID
As you can see from the example, it applies when you use either
Fn::GetAtt functions in a
Task state. And it applies to all 3 ways of invoking a Lambda function from a
Enjoy what you’re reading? Subscribe to my newsletter and get more content on AWS and serverless technologies delivered straight to your inbox.
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, design patterns and best practices.
Come learn about operational BEST PRACTICES for AWS Lambda: CI/CD, testing & debugging functions locally, logging, monitoring, distributed tracing, canary deployments, config management, authentication & authorization, VPC, security, error handling, and more.
You can also get 40% off the face price with the code ytcui.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong