Artillery with AWS Fargate IAM Role & Policy #3345
samhunter1
started this conversation in
Artillery
Replies: 1 comment 1 reply
-
The relevant code is here: https://github.com/artilleryio/artillery/blob/main/packages/artillery/lib/platform/aws-ecs/ecs.js#L126-L131 The code tries to look up the role by name to see if it exists, and only continues to try to create a new role if the lookup fails. Can you try rerunning the Artillery command with |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
The Fargate section of the Artillery docs mentions this:
"(Optional) An IAM role named
artilleryio-ecs-worker-role
for Fargate tasks that execute the test. If a role with that name already exists, Artillery will use it instead of creating it."When trying to execute my Artillery tests via Fargate I get this error:
EntityAlreadyExists: Role with name artilleryio-ecs-worker-role already exists. Code: EntityAlreadyExists
This contradicts the documentation and when I delete the artilleryio-ecs-worker role it trips up on a policy as well:
EntityAlreadyExists: A policy called artilleryio-ecs-worker-policy already exists. Duplicate names are not allowed. Code: EntityAlreadyExists
Just wondering if this is a known bug or if there is anyway for Artillery to use the role and policy on AWS.
Thanks and I appreciate any help.
Beta Was this translation helpful? Give feedback.
All reactions