You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provision AWS resources with CloudFormation template.
Activate initial account.
Setup test case and execute it.
Failed test with message Failed to run Fargate tasks
Expected behavior
Start to execute test case
Please complete the following information about the solution:
Version: [e.g. v1.1.0]
v3.2.5
Region: [e.g. us-east-1]
ap-northeast-1
Was the solution modified from the version published on this repository?
No
If the answer to the previous question was yes, are the changes available on GitHub?
Have you checked your service quotas for the services this solution uses?
Yes
Were there any errors in the CloudWatch Logs?
Yes. The execution log of AWS Lambda named LoadTesting-DLTLambdaFunctionTaskRunnerXXX outputs error message as follows.
ERROR AccessDeniedException: User: arn:aws:sts::xxxxxxxxx:assumed-role/LoadTesting-DLTLambdaFunctionDLTTestLambdaTaskRole1-NBm9N9xIFI6W/LoadTesting-DLTLambdaFunctionTaskRunnerAAAD9171-18Tw38j9u4Rq is not authorized to perform: ecs:TagResource on resource: arn:aws:ecs:ap-northeast-1:xxxxxxxx:task/LoadTesting/* because no identity-based policy allows the ecs:TagResource action
Screenshots
Additional context
When I add ecs:TagResource action to DLTLambdaFunctionDLTTestLambdaTaskRoleXXX IAM Role, I can start to execute test case.
The text was updated successfully, but these errors were encountered:
We are on top of this. In the meantime to unblock yourself you can go to your account and add ecs:tagResource you can locate your DLTTestLambdaTaskRole from your cloudformation template and add the said action to your TaskLambdaPolicy.
### Changed
- Updated version of chartjs fromv v3.0.0 to v4
- Updated version of react from v17 to v18
- Updated version of react-dom from v17 to v18
- Removed moment.js as the library was in maintenance mode. Replaced with built-in javascript date and time
- Updated Jmeter dependencies and taurus dependencis within the docker image to enhance the security of the docker image
- Updated taurus version from v1.16.27 to v1.16.29
### Fixed
- Bug fix to resolve issue with graph not showing on scheduled tests [#158](#158)
- Bug fix created by changes of the ECS account setting and enabling Tag Resource Authorization as default settings [#162](#162)
- Bug fix to resolve issue with running the tests on OPT-IN regions [#163](#163)
Describe the bug
When running test cases,
Failed to run Fargate tasks
are displayed, and tests are not executed.To Reproduce
Failed to run Fargate tasks
Expected behavior
Please complete the following information about the solution:
LoadTesting-DLTLambdaFunctionTaskRunnerXXX
outputs error message as follows.Screenshots
![failed_to_run](https://private-user-images.githubusercontent.com/1687437/305602349-c4b7fa07-f87e-4d17-a320-79c742b0fb45.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5OTE2MDMsIm5iZiI6MTczOTk5MTMwMywicGF0aCI6Ii8xNjg3NDM3LzMwNTYwMjM0OS1jNGI3ZmEwNy1mODdlLTRkMTctYTMyMC03OWM3NDJiMGZiNDUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTlUMTg1NTAzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NmRkNDJjNWVmYzRmNzJkYzRhMTg4N2FkOWQ5YzMxZjA0MGRiOWZmZDBmM2IyZTJlZWNmMWM0YTMyYzRmMjU4MyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.ckJHgvW6mwe1F7pfC0YD3hUohixAvX0AOjaoUV_f1PU)
Additional context
When I add
ecs:TagResource
action toDLTLambdaFunctionDLTTestLambdaTaskRoleXXX
IAM Role, I can start to execute test case.The text was updated successfully, but these errors were encountered: