search

awslabs / aws-saas-boost

AWS SaaS Boost is a ready-to-use toolset that removes the complexity of successfully running SaaS workloads in the AWS cloud.
Apache License 2.0
959 stars 188 forks source link

onboarding failed shortly after initiation #388

Closed qwudssd closed 1 year ago

qwudssd commented 1 year ago

onboarding tenant process failed shortly after initiation with an error msg in the onboarding-validation log:

Screen Shot 2022-10-24 at 4 24 14 PM

version branch: master

muylucir commented 1 year ago

I had same problem. ECS service quota now change from resource based quota to vcpu based quota until 15 Nov . you can change ECS service quota mode using AWS CLI command below

aws ecs put-account-setting-default --name fargateVCPULimit --value enabled --region <your region>

after change vcpu based quota, you can provision new tenant.

netapp-dhruv-tyagi commented 1 year ago

Facing the same issue. Tried the above mentioned fix, but still seeing the same message:

Quota will be exceeded for service Fargate On-Demand resource count. You are currently consuming 0.0, and Service Quota is 0.0.

qwudssd commented 1 year ago

@muylucir thanks for your reply. but looks like im still having the same issue after running that command

muylucir commented 1 year ago

@qwudssd Is onboarding still a failure? Or do you only see the error message?

qwudssd commented 1 year ago

@muylucir yeah onboarding still failed

muylucir commented 1 year ago

@qwudssd At what stage does the problem occur? Can you provide more information(log, screenshot, etc..)

qwudssd commented 1 year ago

@muylucir the failure still occurred pretty shortly after the initiation with the same error. I'm trying to update my saas-boost with this fix https://github.com/awslabs/aws-saas-boost/pull/390, but there is an error in clouformation saying

Screen Shot 2022-10-26 at 1 19 59 PM

have you encountered this error before?

muylucir commented 1 year ago

@qwudssd I think this is a new problem. The first question you asked me was already solved when you executed the AWS CLI command I told you, and when you applied fix #390. Because if the first problem hadn't been solved, the cloudformation stack wouldn't have even started.

If you are using the main branch now, it may not be stable. If the main purpose is not to test the latest version, I recommend using the stable version of tag v2.0.0 instead of the main branch.

qwudssd commented 1 year ago

@muylucir okay i see. thank you!