Build an AMI - Githubissues

jcf commented 6 years ago

The AMI now includes Clojure and common Clojure tooling (i.e. Boot and Leiningen).

Support for both CodeDeploy and CloudFront are included (although not configured or enabled out of the box), and packages from the AUR can be pulled down and cached in a local repo.

Tasks

[x] Test CodeDeploy starts up on EC2
[ ] Make sure log output reaches CloudWatch (need to create a log group and the associated config)
~Make sure CodeDeploy isn't logging to a file~ #7

jcf commented 6 years ago

I'd consider using something like Ansible to provision these changes in future. Doing everything with a set of Bash scripts is already a little painful, and will only get worse as complexity increases.

jcf commented 6 years ago

I've added the Bash script used elsewhere in production to push journald logs over to CloudWatch, and packaged it up.

It's installed in the AMI I'm building presently (ami-bafcd9c3), and has an associated systemd unit file that you can activate like so:

systemctl start journald-cloud-watch-script

Internally that runs the provided Bash script, which can be found in /usr/bin/tail-journald.

I haven't had time to test out the script so can't say for sure it will work if you provision an EC2 instance via the included Terraform configuration, which can be done like so:

cd terraform
make plan
# Review the output to make sure it's correct.
make apply

Note, Terraform state is only stored locally, although pushing state to S3 is relatively straightforward should you wish to do so. I've destroyed everything via make destroy.

HTH!

juxt / rock

Build an AMI #4

Tasks