wiki/creating-ec2-image-from-scratch.md
... ...
@@ -2,6 +2,8 @@
2 2
3 3
I started out with a clean "Amazon Linux AMI 2015.03 (HVM), SSD Volume Type - ami-a10897d6" image from Amazon and added the existing Swap and Home snapshots as new volumes. The root/system volume I left as is, to start with. This requires having access to a user key that can be selected when launching the image.
4 4
5
+Enable the EPEL repository by issuing `yum-config-manager --enable epel/x86_64`.
6
+
5 7
I then did a `yum update` and added the following packages:
6 8
7 9
- httpd
... ...
@@ -12,6 +14,9 @@ I then did a `yum update` and added the following packages:
12 14
- libstdc++48.i686 (for Android builds)
13 15
- glibc.i686 (for Android builds)
14 16
- libzip.i686 (for Android builds)
17
+ - telnet
18
+ - apachetop
19
+ - goaccess
15 20
16 21
Then I created a mount point /home/sailing and copied the following lines from the /etc/fstab file from an existing SL instance:
17 22
... ...
@@ -78,4 +83,6 @@ This increases the maximum number of open files allowed from the default 1024 to
78 83
79 84
Copied the httpd configuration files `/etc/httpd/conf/httpd.conf`, `/etc/httpd/conf.d/000-macros.conf` and the skeletal `/etc/httpd/conf.d/001-events.conf` from an existing server.
80 85
86
+Copied /etc/logrotate.conf from an existing SL instance so that `/var/log/logrotate-target` is used to rotate logs to.
87
+
81 88
Instead of having the `ANDROID_HOME` environment variable be set in `/etc/profile` as in the old instances, I moved this statement to the `sailing.sh` script in git at `configuration/sailing.sh` and linked to by `/etc/profile.d/sailing.sh`. For old instances this will set the variable redundantly, as they also have it set by a manually adjusted `/etc/profile`, but this shouldn't hurt.
... ...
\ No newline at end of file