run-lambda - run an Artillery test on AWS Lambda

Added inv2.0.0-21
artillery run-lambda [options] <script>


Lambda-specific flags

--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>
Added inv2.0.0-34
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 (Graviton (opens in a new tab)). Legacy x86 may be set with x86_64 Added inv2.0.0-28

Shared flags

The run-lambda command shares many options with the run command:

--output, -oWrite a JSON report to a file
--environment, -eRun the test using the specified environment
--config, -cLoad config section from another file
--scenario-nameRun only the specified scenario Added inv2.0.0-38
--overridesOverride values in the test script dynamically
--target, -tSet or override target URL for the test
--variables, -vSet scenario variables dynamically
--dotenv <path>Set environment variables with a .env file
--quiet, -q
Added inv2.0.10
Run in quiet mode
--insecure, -kTurn off TLS verification. Should not be used in production
--record and --key
Added inv2.0.0-32
Record test run to Artillery Cloud (opens in a new tab). Learn more about recording test runs (opens in a new tab).