Situation
I am trying to deploy OpenEMR Fullstack on AWS but the CloudFormation stack fails because the S3 bucket holding the application package for Beanstalk cannot be accessed (access restricted). I tried to deploy in the Zurich region, Ireland, as well as Frankfurt with the same result.
I am applying this stack: openemr-devops/packages/full_stack at master · openemr/openemr-devops · GitHub
Hi, Waro.
I don’t know why that’s still live but I probably need to delete it – full stack was something we outgrew a while back, and it wouldn’t launch even if you had the template because it relies on MySQL versions Amazon’s long-since retired.
In your shoes I’d consider either of “OpenEMR Standard”, which is just an OpenEMR instance backed by Amazon RDS, or taking a look at GitHub - openemr/host-openemr-on-aws-fargate , which is an Amazon-authored solution for launching OpenEMR with their Cloud Development Kit and covers the same general ground Full Stack did but with a much keener eye toward cutting-edge sensibilities.
Sorry for the confusion!
1 Like
Hi Asher,
That makes sense. Thank you for the insights. I will have a look at the version with Fargate!
One more question. I saw that I need to subscribe to the Marketplace for OpenEMR Standard. Are you describing somewhere how you build the AMI, so I could build it myself, or do I need to take the Marketplace version?
Take a look at openemr-devops/packages/standard/ami at master · openemr/openemr-devops · GitHub – run build, check the output log, then run seal. This is the AMI I submit to Marketplace staff. (The configure script is run after the CloudFormation stack launches the instance, inside the admin’s environment, for final loading of stack details, and you won’t need to adjust it for any sort of vanilla setup.)