Closed babaksd closed 2 years ago
@babaksd - Yes, you can implement this subdomain approach, we did mentioned about this in the documentation in Step3.
If you are interested in understanding how to implement this approach, please refer to EKS SaaS Reference Solution which implemented this subdomain approach.
Hi @ujwalbukka
I'm trying to deploy the solution in AWS but the "serverless-saas-CustomResources" stack creation is stuck, Specifically, the "UpdateTenantStackMap" and "UpdateSettingsTable" events are stuck due to following errors from Cloudwatch:
Unable to import module 'update_settings_table': No module named 'logger' Traceback Unable to import module 'update_settings_table': No module named 'crhelper' Traceback Unable to import module 'update_tenantstackmap_table': No module named 'logger' Traceback Unable to import module 'update_tenantstackmap_table': No module named 'crhelper' Traceback
It seems the Python dependencies are not installed correctly.
May I ask you how can I fix that?
Thanks,
Hi @babaksd - As mentioned in this issue response please make sure you have latest sam cli version.
And please make sure you have met all these pre-requisites
Closing this issue. Please reopen if you still have any issues/questions.
I thought it might be a good idea to manage a custom domain/subdomain name for each new tenant in this reference solution. So each tenant will have its own subdomain to access the SAAS web app.
Thank you!