de8606e40be10398b960283375a3e75423c4cc3f
wiki/info/landscape/amazon-ec2.md
| ... | ... | @@ -514,6 +514,7 @@ Follow these steps to upgrade the AMI: |
| 514 | 514 | * Check the sizes of the mounted partitions by doing `df; swapon -s`. These will come in handy after creating the new AMI in order to tag the new volume snapshots accordingly |
| 515 | 515 | * Update any keys in `/root/.ssh/authorized_keys` and `/home/sailing/.ssh/authorized_keys` |
| 516 | 516 | * Remove created http rewrite entries in `/etc/httpd/conf.d/001-events.conf` |
| 517 | +* Edit /etc/motd to set the current version |
|
| 517 | 518 | * In the EC2 administration console go to the "Instances" tab, select your running instance and from the "Actions" drop-down select "Create Image". Give the image the name "SAP Sailing Analytics App x.y" where "x.y" is the updated version number of the image. Just make sure it's greater than the previous one. If you feel like it, you may provide a short description telling the most important features of the image. |
| 518 | 519 | * Once the image creation has completed, go to the Snapshots list in the "Elastic Block Store" category and name the new snapshots appropriately. Now the information about the device sizes obtained earlier from the `df` and `swapon` commands will help you to identify which snapshot is which. Usually, the three snapshots would be something like AMI Analytics Home x.y, AMI Analytics System x.y and AMI Analytics Swap x.y with "x.y" being the version number matching that of your image. |
| 519 | 520 | * Now you can remove any earlier Sailing Server AMI version and the corresponding snapshots. |