Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customer relationship agent fails to deploy #253

Open
hasanp87 opened this issue Jul 26, 2024 · 1 comment
Open

Customer relationship agent fails to deploy #253

hasanp87 opened this issue Jul 26, 2024 · 1 comment

Comments

@hasanp87
Copy link

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)"

@EashanKaushik
Copy link
Contributor

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:

  1. Navigate to the AWS Identity and Access Management (IAM) console.
  2. Select "Roles" from the left-hand menu.
  3. Search for the role named "AWSServiceRoleForApplicationAutoScaling_ECSService".
  4. 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.

mttanke added a commit that referenced this issue Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants