The first time I did this, I used the AWS Marketplace Openemr STANDARD and chose launch cloudformation and then picked your template file … that caused the errors above.
Then I decided to simply go to cloudformation directly with the following parameters:
I simply when to create a cloudformation stack, chose the template file from the post/link above in your message, and then used these parameters:
AdminPassword |
**************** |
EC2KeyPair |
OpenEMRkeyPair |
PatientRecords |
100 |
PracticeStorage |
200 |
RDSInstanceSize |
db.t3.medium |
RDSPassword |
****************** |
UserCidr |
10.0.0.0/16 |
UserSubnetPrivate1 |
10.0.2.0/24 |
UserSubnetPrivate2 |
10.0.4.0/24 |
UserSubnetPublic1 |
10.0.1.0/24 |
UserSubnetPublic2 |
10.0.3.0/24 |
WebserverInstanceSize |
t3.large |
This time, I encountered the following before the stack rollback began due to failure to create the stack:
2022-07-03 23:55:48 UTC-0500 ig
CREATE_FAILED Resource creation cancelled
2022-07-03 23:55:47 UTC-0500 OpenEMRKey
CREATE_FAILED Resource creation cancelled
2022-07-03 23:55:47 UTC-0500 rtTablePublic
CREATE_FAILED Resource creation cancelled
2022-07-03 23:55:47 UTC-0500 rtTablePrivate
CREATE_FAILED Resource creation cancelled
2022-07-03 23:55:47 UTC-0500 PublicSubnet1
CREATE_FAILED Resource creation cancelled
2022-07-03 23:55:47 UTC-0500 PrivateSubnet1
CREATE_FAILED Resource creation cancelled
2022-07-03 23:55:47 UTC-0500 S3Bucket
CREATE_FAILED Resource creation cancelled
2022-07-03 23:55:46 UTC-0500 PublicSubnet1
CREATE_IN_PROGRESS -
2022-07-03 23:55:46 UTC-0500 PrivateSubnet1
CREATE_IN_PROGRESS -
2022-07-03 23:55:46 UTC-0500 PrivateSubnet2
CREATE_FAILED Template error: Fn::Select cannot select nonexistent value at index 1
2022-07-03 23:55:46 UTC-0500 ApplicationSecurityGroup
CREATE_IN_PROGRESS -
2022-07-03 23:55:46 UTC-0500 SysAdminAccessSG
CREATE_IN_PROGRESS -
2022-07-03 23:55:46 UTC-0500 DBSecurityGroup
CREATE_IN_PROGRESS -
2022-07-03 23:55:46 UTC-0500 PublicSubnet2
CREATE_FAILED Template error: Fn::Select cannot select nonexistent value at index 1
2022-07-03 23:55:46 UTC-0500 rtTablePublic
CREATE_IN_PROGRESS -
2022-07-03 23:55:46 UTC-0500 rtTablePrivate
CREATE_IN_PROGRESS -
2022-07-03 23:55:43 UTC-0500 VPC
CREATE_COMPLETE -
2022-07-03 23:55:31 UTC-0500 VPC
CREATE_IN_PROGRESS Resource creation Initiated
2022-07-03 23:55:31 UTC-0500 ig
CREATE_IN_PROGRESS Resource creation Initiated
2022-07-03 23:55:31 UTC-0500 OpenEMRKey
CREATE_IN_PROGRESS Resource creation Initiated
2022-07-03 23:55:30 UTC-0500 S3Bucket
CREATE_IN_PROGRESS Resource creation Initiated
2022-07-03 23:55:29 UTC-0500 S3Bucket
CREATE_IN_PROGRESS -
2022-07-03 23:55:29 UTC-0500 VPC
CREATE_IN_PROGRESS -
2022-07-03 23:55:29 UTC-0500 OpenEMRKey
CREATE_IN_PROGRESS -
2022-07-03 23:55:28 UTC-0500 ig
CREATE_IN_PROGRESS -
2022-07-03 23:55:22 UTC-0500 oe-virginia-610-2022-07-03-2352h
CREATE_IN_PROGRESS User Initiated
I have seen the above error in the past with 6.0.0. The way I got around it was to choose a t2.medium instead of a t3.medium and to make sure that the database version was 5.7.33 in the cloudformation stack file. I don’t have this option here because I cannot choose t2.medium for my ec2. I suppose I could edit the template file to allow t2.medium somehow …
RBL