The AWS Lambda ARN Client Workload identification method is applicable only to AWS Lambda container deployments. Aembit utilizes the native AWS identifier (Lambda ARN) to identify and distinguish Client Workloads.
Applicable Deployment Type
Section titled “Applicable Deployment Type”This method is suitable for Aembit Edge-based deployments.
Configuration
Section titled “Configuration”Aembit Cloud
Section titled “Aembit Cloud”- Create a new Client Workload.
- Choose AWS Lambda ARN for client identification.
- In the Value field, enter the AWS Lambda ARN. It should be provided in the following format:
arn:aws:lambda:<region>:<account>:function:<lambda function name>
Using Versions
Section titled “Using Versions”When working with AWS Lambda ARN, it’s crucial to understand the two types of ARNs: Qualified ARN and Unqualified ARN. Each serves a specific purpose, and understanding their differences is key. For detailed information, refer to the official AWS Documentation.
Unqualified ARN: Used for the latest version of a Lambda function.
Example:
arn:aws:lambda:aws-region:acct-id:function:helloworld
Qualified ARN: Used for a specific version of a Lambda function or aliases.
Example:
arn:aws:lambda:aws-region:acct-id:function:helloworld:42
If you need to work with a Qualified ARN, you must create a client workload that uses a wildcard to handle multiple versions. For instance:
arn:aws:lambda:aws-region:acct-id:function:helloworld:*
.
Finding the AWS Lambda ARN
Section titled “Finding the AWS Lambda ARN”You can find the list of Lambda functions via the AWS CLI by executing: aws lambda list-functions --region us-east-2
This command will return all the Lambda-related information, including the Lambda ARN, which is available under the FunctionArn
field.