# OpenEMR restore on AWS

**URL:** <https://community.open-emr.org/t/openemr-restore-on-aws/22581>\
**Category:** Support\
**Created:** [May 9, 2024, 11:06pm UTC](https://community.open-emr.org/t/openemr-restore-on-aws/22581 "2024-05-09T23:06:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![EFC](https://community.open-emr.org/letter_avatar_proxy/v4/letter/e/848f3c/32.png) [@EFC](https://community.open-emr.org/u/EFC)\
**Post date:** [May 9, 2024, 11:06pm UTC](https://community.open-emr.org/t/openemr-restore-on-aws/22581/1 "2024-05-09T23:06:45Z")

</div>

**Situation**  
I’m running OpenEMR on AWS Cloud and all of the sudden I cant even get to the log in screen. The only message im getting is as follows:

**3.94.131.49** took too long to respond.

**OpenEMR Version**  
I’m unable to access that info. I have been using the same version since around September of 2022

**Browser** :  
I’m using: Google Chrome

**Operating System**  
I’m using: Windows 10 Pro

**Search**  
Did you search the forum for similar questions?

**Logs**  
Did you check the logs?  
Was there anything pertinent in them?  
Please paste them here (surround with three backticks (```) for readability.  
You can also turn on User Debugging under Administration-\>Globals-\>Logging User Debugging Options=\>All

---

<div class="post-metadata">

**Author:** ![Penguin8R](https://community.open-emr.org/user_avatar/community.open-emr.org/penguin8r/32/17192_2.png) [@Penguin8R](https://community.open-emr.org/u/Penguin8R)\
**Post date:** [May 10, 2024, 8:07pm UTC](https://community.open-emr.org/t/openemr-restore-on-aws/22581/2 "2024-05-10T20:07:23Z")

</div>

There won’t be any way to diagnose that from a client session, have to get into the AWS environment and consult error logs, check status of resources like the web server & database, etc.  
It sounds like the web server isn’t responding to your connection request, but that leaves a lot of possibilities as to why. Could be a network issue, could be a traffic filtering problem. If you’re not familiar with AWS resource administration, then you’ll need to get someone who is in order to do the real troubleshooting. There’s many more than one possible way to run a web application like OpenEMR on AWS infrastructure, how it’s architected will determine where the troubleshooting process starts.

---

<div class="post-metadata">

**Author:** ![EFC](https://community.open-emr.org/letter_avatar_proxy/v4/letter/e/848f3c/32.png) [@EFC](https://community.open-emr.org/u/EFC)\
**Post date:** [May 10, 2024, 8:31pm UTC](https://community.open-emr.org/t/openemr-restore-on-aws/22581/3 "2024-05-10T20:31:14Z")

</div>

Well, apparently I made a mistake of terminating the AWS instance instead of stopping it. This means all data was deleted.

The good news is that I have created a .tar backup file. Is there a good step by step tutorial on how to restore it onto a new OpenEMR slate?

---

<div class="post-metadata">

**Author:** ![acu-emr](https://community.open-emr.org/letter_avatar_proxy/v4/letter/a/54ee81/32.png) [@acu-emr](https://community.open-emr.org/u/acu-emr)\
**Post date:** [May 10, 2024, 9:32pm UTC](https://community.open-emr.org/t/openemr-restore-on-aws/22581/4 "2024-05-10T21:32:21Z")

</div>

This may help:

> **[Open EMR Backup and Restore Docker Procedure](https://benmarte.com/blog/openemr-backup-restore/#void)**
>
> One of the most important things in development is disaster recovery, using Open EMR and being HIPAA compliant you must have a solid understanding on how to backup/restore your Open EMR instance because like Murphy says: “Anything that can go wrong...
