Repository navigation
Distributed Load Testing on AWS Fargate #3743
Replies: 5 comments 1 reply
|
It would be greatly appreciated if you could tell me whether you can provide me with artilleryio-ecs-worker-role cfn template or not. |
|
Something like this: AWSTemplateFormatVersion: "2010-09-09"
Description: Artillery.io ECS/Fargate worker role (equivalent of createWorkerRole in ecs.js)
Parameters:
TaskRoleName:
Type: String
Default: artilleryio-ecs-worker-role
Description: Name of the IAM role assumed by Artillery ECS worker tasks
Resources:
ArtilleryWorkerPolicy:
Type: AWS::IAM::ManagedPolicy
Properties:
ManagedPolicyName: artilleryio-ecs-worker-policy
Path: /
PolicyDocument:
Version: "2012-10-17"
Statement:
- Effect: Allow
Action:
- ssm:DescribeParameters
Resource: "*"
- Effect: Allow
Action:
- ssm:GetParameters
- ssm:GetParameter
- ssm:PutParameter
- ssm:DeleteParameter
- ssm:DescribeParameters
- ssm:GetParametersByPath
Resource:
- !Sub "arn:${AWS::Partition}:ssm:*:${AWS::AccountId}:parameter/artilleryio/*"
- Effect: Allow
Action:
- ecr:GetAuthorizationToken
Resource: "*"
- Effect: Allow
Action:
- logs:*
Resource:
- !Sub "arn:${AWS::Partition}:logs:*:${AWS::AccountId}:log-group:artilleryio-log-group*:*"
- Effect: Allow
Action:
- sqs:*
Resource:
- !Sub "arn:${AWS::Partition}:sqs:*:${AWS::AccountId}:artilleryio*"
- Effect: Allow
Action:
- s3:*
Resource:
- !Sub "arn:${AWS::Partition}:s3:::artilleryio-test-data-${AWS::AccountId}"
- !Sub "arn:${AWS::Partition}:s3:::artilleryio-test-data-${AWS::AccountId}/*"
- Effect: Allow
Action:
- xray:PutTraceSegments
- xray:PutTelemetryRecords
Resource: "*"
ArtilleryWorkerRole:
Type: AWS::IAM::Role
Properties:
RoleName: !Ref TaskRoleName
Path: /
AssumeRolePolicyDocument:
Version: "2012-10-17"
Statement:
- Effect: Allow
Principal:
Service:
- ecs-tasks.amazonaws.com
- ecs.amazonaws.com
Action: sts:AssumeRole
ManagedPolicyArns:
- !Ref ArtilleryWorkerPolicy
Outputs:
WorkerRoleArn:
Description: ARN of the Artillery worker role (return value of createWorkerRole)
Value: !GetAtt ArtilleryWorkerRole.ArnCaveats are that the above is untested (created by an AI agent from the source code linked above), and is not a supported method of creating that role, so there's no guarantee of compatibility with any future releases of Artillery. |
|
Thanks a lot. I will try it out. |
|
Much progress! I generate a jwt token and set AUTH_HEADER env variable in a workflow step. Authorization header in example.yml reads AUTH_HEADER as below - and then call 2 artillery tests in 2 steps (running the same test script example.yml) : The 1st test works fine .. all http responses 200s ... Do you see anything wrong with what I'm doing?? Thank you so much! |
|
Any thoughts on this? It would be very appreciated!! |
Uh oh!
There was an error while loading. Please reload this page.
Hi
We are trying to run load testing using AWS Fargate. I wonder if you could provide cloudformation template for an IAM role named artilleryio-ecs-worker-role? (ArtilleryDistributedTestingFargateRole role can't create artilleryio-ecs-worker-role due to a company security restriction)
Thanks
Seungchan
All reactions