Lambda script creates a random role with no permissions about artillery

[hassy]

The role is not random, it's the role that AWS Lambda functions running the test will assume. You can see the full definition of what's created here: https://github.com/artilleryio/artillery/blob/main/packages/artillery/lib/platform/aws-lambda/index.js#L489

Artillery should've created a policy attached to that role which allows SQS access: https://github.com/artilleryio/artillery/blob/main/packages/artillery/lib/platform/aws-lambda/index.js#L540

Can you confirm if it's there?

[hassy]

Also did this happen just once, or is it happening repeatedly?

We're looking at similar issue on AWS Fargate right now where the very first run of an Artillery test in an AWS account can fail with a very similar error due to IAM propagation lag. cc @InesNi

[jaxoncreed]

Ah I figured out the problem. Yes, it happened repeatedly. My problem was that I had already created a role named "artilleryio-default-lambda-role" Deleting that role seemingly fixed the problem.

[bernardobridge]

@jaxoncreed I'd also recommend updating to the latest Artillery version (https://github.com/artilleryio/artillery/releases/tag/artillery-2.0.15).

Lambda support received a large refactor with a lot of improvements. Older Lambda versions may not work as intended, as there were some issues we resolved in the update we did.