Hi Everyone,
I ran into an interesting problem where I wanted to trigger AWS lambda from Workfront Fusion which was protected. As far as I can see for now there is an option to create signature but only two are available and there is no AWS4-HMAC-SHA256. Also there are only modules for S3 buckets but none for lambda at the moment.
I appreciate any input. Thank you in advance.
Best regards,
Ivan Bebek
Hi @ivanbebek-ix,
Thank you for your question! Right now, Workfront Fusion doesn’t have a built-in connector for AWS Lambda. Fusion’s HTTP modules also don’t support AWS Signature v4, which is the signing method AWS requires for most API calls.
Options and Workarounds
1) Expose Lambda via API Gateway
You can set up an API Gateway endpoint in AWS to call your Lambda function. API Gateway lets you use simpler authentication methods like an API key, basic auth, or custom headers instead of the AWS Signature v4. Once that’s in place, you can use Fusion’s HTTP module to make requests to the API Gateway endpoint, sending any required payloads and headers.
2) Use an External Automation Platform
Platforms like Zapier, Make, or your own custom middleware can act as a bridge between Fusion and AWS Lambda. These tools can handle the AWS Signature v4 signing process before sending requests to Lambda.
3) Submit a Feature Request
Adobe continues to improve Fusion, so it’s worth submitting a feature request for direct AWS Lambda support or built-in AWS Signature v4 handling. You can do this through the Innovation Lab or your account representative.
- Monica
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.