run-lambda - run an Artillery test on AWS Lambda
artillery run-lambda [options] <script>Options
Lambda-specific flags
| Option | Description |
|---|---|
--region <region> | The AWS region to run in (us-east-1, us-west-1, eu-west-1, eu-central-1, ap-south-1, ap-northeast-1) |
--count <num> | Number of load generators to launch. |
--tags <tags> | Comma-separated list of tags in key:value format to tag the test run, for example: --tags team:sre,service:foo. |
--note <text> | Attach a note to a text, for example: --note "This is a spike test for service foo". |
--memory-size <number> | Memory size of the Lambda function in bytes. Default: 4096. |
--lambda-role-arn <role> | ARN of the IAM role to use for the Lambda function. |
--security-group-ids <ids> | Comma-separated list of AWS VPC security group IDs to launch Lambda tasks in. |
--subnet-ids <ids> | Comma-separated list of subnet IDs to use for the Lambda function. |
--architecture <string> | Architecture of the Lambda function. Default: arm64. |
Shared flags
The run-lambda command shares many options with the run command:
| Option | Description |
|---|---|
--output, -o | Write a JSON report to a file |
--environment, -e | Run the test using the specified environment |
--config, -c | Load config section from another file |
--overrides | Override values in the test script dynamically |
--target, -t | Set or override target URL for the test |
--variables, -v | Set scenario variables dynamically |
--dotenv <path> | Set environment variables with a .env file |
--insecure, -k | Turn off TLS verification. Should not be used in production |
--record and --key | Record test run to Artillery Cloud (opens in a new tab). Learn more about recording test runs (opens in a new tab). |