aboutsummaryrefslogtreecommitdiff
path: root/terraform/aws_using_ami
Commit message (Collapse)AuthorAge
* Improve the from_port setting in various AWS security groupsHEADmasterChristopher Baines2019-08-28
| | | | Thanks to schmie for looking in to this.
* Add a name for the builder AWS instanceChristopher Baines2019-05-30
|
* Set --max-silent-time for the guix-daemonChristopher Baines2019-05-30
| | | | To avoid builds from hanging forever.
* Add a new AWS backend using Amazon Machine ImagesChristopher Baines2019-05-30
The existing AWS backend uses system containers backed on to the AWS hosted NFS service (EFS). This has some advantages, but also some disadvantages. Using the EFS service allows building a container on one instance, with the state being held on the EFS, and then launching a new instance to run the container. Using EFS also provides persistence, at least beyond individual EC2 instances. However, build performance when using EFS is poor compared with a local store without the overhead of the network latency. Additionally, the startup speed of the container running off EFS is slow compared to local storage. This backend doesn't use EFS, instead the Guix store sits on instance storage. Rather than using a system container for a Mini Environment, an Amazon Machine Image (AMI) is built instead. The fast local storage makes builds faster, and using EBS storage for the Mini Envirnoments as well as not having the overhead of starting Ubuntu, then starting the container also makes startup faster.