POST /2015-03-31/functions/{FunctionName}/aliases
Creates an alias for a Lambda function version. Use aliases to provide clients with a function identifier that you can update to invoke a different version.
You can also map an alias to split invocation requests between two versions. Use the RoutingConfig parameter to specify a second version and the percentage of invocation requests that it receives.
Servers
- https://lambda.{region}.amazonaws.com
- https://lambda.{region}.amazonaws.com.cn
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
FunctionName |
String | Yes |
The name of the Lambda function. Name formats
The length constraint applies only to the full ARN. If you specify only the function name, it is limited to 64 characters in length. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
X-Amz-Content-Sha256 |
String | No | |
X-Amz-Credential |
String | No | |
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
X-Amz-Date |
String | No | |
X-Amz-Algorithm |
String | No | |
X-Amz-SignedHeaders |
String | No | |
X-Amz-Security-Token |
String | No | |
X-Amz-Signature |
String | No |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
FunctionVersion |
String | Yes |
The function version that the alias invokes. |
Name |
String | Yes |
The name of the alias. |
RoutingConfig |
Object | No |
The traffic-shifting configuration of a Lambda function alias. |
Description |
String | No |
A description of the alias. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.