wiki/info/landscape/creating-ec2-image-for-hudson-from-scratch.md
... ...
@@ -1,6 +1,6 @@
1 1
# Setting up an image for the hudson.sapsailing.com server
2 2
3
-Like when setting up a regular sailing application server instance, start with a fresh Amazon Linux 2 image and create an instance with a 16GB root volume. Use the "Sailing Analytics Server" security group and something like a ``t3.small`` instance type for creating the image. Then, invoke the script
3
+Like when setting up a regular sailing application server instance, start with a fresh Amazon Linux 2 image and create an instance with a 32GB root volume. Use the "Sailing Analytics Server" security group and something like a ``t3.medium`` instance type. Then, invoke the script
4 4
```
5 5
configuration/hudson_instance_setup/setup-hudson-server.sh {external-IP-of-new-instance}
6 6
```
... ...
@@ -10,7 +10,7 @@ The ``/home/hudson/android-sdk-linux`` folder that is later expected to be mount
10 10
11 11
When the script has finished, proceed as follows:
12 12
13
-* make a volume available that holds the ``/home/hudson`` content, including the ``android-sdk-linux`` folder. This can happen, e.g., by creating a snapshot of the existing ``/home/hudson`` volume of the running "Build/Dev/Test" server, or you may search the weekly backup snapshots for the latest version to start with. Make sure to create the volume in the same availability zone (AZ) as your instance is running in.
13
+* make a volume available that holds the ``/home/hudson`` content, including the ``android-sdk-linux`` folder. This can happen, e.g., by creating a snapshot of the existing ``/home/hudson`` volume of the running "Build/Dev/Test" server, or you may search the weekly backup snapshots for the latest version to start with, or you may even stop the running Hudson, unmount and detach the /home/hudson volume and attach/mount on the new instance as long as the new instance runs in the same availability zone (AZ). Make sure to create the volume in the same availability zone (AZ) as your instance is running in.
14 14
* Based on how full the volume already is, consider re-sizing it by creating the volume larger than the snapshot.
15 15
* Attach it.
16 16
* In the instance, as ``root`` user, call ``dmesg``. This will show the new volume that just got attached, as well as its partition names.