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

ConflictingDomainExists #396

Closed qwudssd closed 1 year ago

qwudssd commented 1 year ago

Encountered this issue when trying to deploy a tenant. I have three services, one is public and the other two are private. The onboarding process failed for one of the private service with this error appeared in cloudformation

Screen Shot 2022-10-31 at 3 43 44 PM

branch: main

PoeppingT commented 1 year ago

Hi @qwudssd , is this reproducible in your environment? If so, please provide in detail the configurations you have set for your environment, including the tiers, appConfig, and tenant onboardings.

qwudssd commented 1 year ago

Hi @PoeppingT yes i tried to onboard a tenant again just now and then the issue appeared again. Here are the pictures of the tiers, app configs and tenant settings. And only tellread is configured to provision a file system. On the onboarding page, i just noticed that the status of one of the tenants 'tenant' changed from failed to deploying today w/o any changes on the app config or images, not really sure why

Screen Shot 2022-11-02 at 10 16 25 AM Screen Shot 2022-11-02 at 10 05 08 AM Screen Shot 2022-11-02 at 10 13 34 AM Screen Shot 2022-11-02 at 10 14 43 AM Screen Shot 2022-11-02 at 10 15 31 AM Screen Shot 2022-11-02 at 10 15 49 AM Screen Shot 2022-11-02 at 10 16 04 AM Screen Shot 2022-11-02 at 10 16 14 AM
PoeppingT commented 1 year ago

Thanks for the information @qwudssd , I can successfully reproduce the issue. It looks like this is due to each tenant-onboarding-app stack attempting to create a private ServiceDiscoveryNamespace attached to the tenant VPC when only one is allowed. The proper solution for this is to either create the ServiceDiscoveryNamespace in the tenant-onboarding stack or create a custom resource to only create the ServiceDiscoveryNamespace if it does not already exist in the tenant-onboarding-app stack.

Unfortunately there is currently no workaround for this, other than to make one of your private services public. We are working on a fix.

qwudssd commented 1 year ago

okay i see, thank you!