Developer Scratchpad

AWS Appliance notes:

Current appliance ami-0703b67d (posted 2017-11-03 2323 CDT)
Do all testing in us-east-1 (N. Virginia)

Create:

Generate Ubuntu 16.04 instance
login: ubuntu
run Lightsail install sequence (launch.sh -s 0)
utilities/ami-lock.sh
clear authorized keys from users ubuntu *and root*
shutdown
export AMI
force image public

Test:

EC2 *in us-east-1, N. Virginia*
Launch Instance
Community AMIs
Public images: <enter AMI here>
Smallest recommended instance size: t2.small
(normal EC2 launch sequence follows, don't forget security group: ssh, http, https)
wait 3 minutes (just because OpenEMR is up doesn't mean rekey is finished)
hit OpenEMR:80, login with 'admin'/<instance ID 'i-' + hexstring>
verify access to containers per doc
verify backup process functions
verify recovery process functions

Debug:

In EC2 or Lightsail, create a *new* SSH key, one you *won't* mind giving away to a developer so we can get into your instance and try to reproduce issues.
We'll want a copy of /tmp/launch.sh .
If you encounter an issue, remember you can stop the instance or snapshot it until a developer can look at it.

AWS CFN Stack notes

wip-aws-mktplace, so...

cd /root
curl -L https://raw.githubusercontent.com/openemr/openemr-devops/wip-aws-mktplace/stacks/AWS-mktplace/ami-build.sh > bootstrap.sh
chmod a+x bootstrap.sh
./bootstrap.sh -b wip-aws-mktplace
rm bootstrap.sh
/root/openemr-devops/stacks/AWS-mktplace/ami-seal.sh

then create ami, encode into stack document