4:04 AM MTAStack failed: Error: The stack named MTAStack failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE about medical-transcription-analysis HOT 4 CLOSED

I am trying this solution on my local computer with Ubuntu 20.04 . But it is giving the MTAStack issue which i already mentioned and asked about on disqus.com blog. Can you help me how to resolve this issue? Please note that i updated the CDK and nodejs to latest version like 14.x and 16.x but the problem still exist. Is it an issue of trying this solution on local system? Shall i try it on an EC2 instance, is that necessary? @alexchirayath

from medical-transcription-analysis.

Hey @optimisticwaqar
Thanks for reaching out.
The logs show that the issue is because the table name already exists.

The fix for you is to

• Delete the DynamoDB tables in the region and account you are trying to deploy - Patients, HealthCareProfessionals and Sessions tables
• Redeploy the stack

The reason is because you may have created a deployment already and when the stack was deleted, some resources were retained. The MTA stack originally used to retain data sources (as a way to protect accidental data deletion) and hence S3 buckets and DynamoDB tables were left without being deleted. However, the recent PR #84 now addresses these and by default deletes all resources created as part of the MTA deployments. Let me know if that works

from medical-transcription-analysis.

Hi @alexchirayath, thanks for the quick response and guidance. I will try the proposed fix and will let you know if it work or not.

from medical-transcription-analysis.

Hey @alexchirayath , finally it works :-) thanks for the help and guidance.

from medical-transcription-analysis.