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
Stack deployment fails at StreamlitAutoScalingTarget with error "Resource handler returned message: "Unable to assume IAM role: arn:aws:iam::942514891246:role/aws-service-role/ecs.application-autoscaling.amazonaws.com/AWSServiceRoleForApplicationAutoScaling_ECSService (Service: ApplicationAutoScaling, Status Code: 400, Request ID: 8e0a21e4-bcba-42dc-9649-a637db947a72)" (RequestToken: cd83145c-37e2-74b0-84d5-5e70b2fcb052, HandlerErrorCode: InvalidRequest)"
The text was updated successfully, but these errors were encountered:
You are encountering an issue where the AWSServiceRoleForApplicationAutoScaling_ECSService role is not present in your AWS account. This role is required for the proper functioning of the application autoscaling feature in the Amazon Elastic Container Service (ECS).
To resolve this issue, we kindly request you to manually create the missing role by following these steps:
Navigate to the AWS Identity and Access Management (IAM) console.
Select "Roles" from the left-hand menu.
Search for the role named "AWSServiceRoleForApplicationAutoScaling_ECSService".
Open the role to trigger creation of the role.
Please delete the failed and completed stacks, and then redeploy the application by following the steps outlined in the README.md file.
We are currently working on an automated solution to address this issue, and the fix will be incorporated into the application soon.
Stack deployment fails at StreamlitAutoScalingTarget with error "Resource handler returned message: "Unable to assume IAM role: arn:aws:iam::942514891246:role/aws-service-role/ecs.application-autoscaling.amazonaws.com/AWSServiceRoleForApplicationAutoScaling_ECSService (Service: ApplicationAutoScaling, Status Code: 400, Request ID: 8e0a21e4-bcba-42dc-9649-a637db947a72)" (RequestToken: cd83145c-37e2-74b0-84d5-5e70b2fcb052, HandlerErrorCode: InvalidRequest)"
The text was updated successfully, but these errors were encountered: