diff --git a/docs/img/aws_backup_link.png b/docs/img/aws_backup_link.png
new file mode 100644
index 000000000..24adac529
Binary files /dev/null and b/docs/img/aws_backup_link.png differ
diff --git a/docs/references/selfhosting.md b/docs/references/selfhosting.md
index c73addbfa..0c75595fa 100644
--- a/docs/references/selfhosting.md
+++ b/docs/references/selfhosting.md
@@ -278,12 +278,14 @@ To upgrade follow these steps closely:
 
 * List the latest backup - `cloudron machine backup list <domain>`
 
-* Make the latest box backup public. This can be done from the AWS S3 console as seen here:
+* Make the latest box backup (files starting with `backup_`) public. This can be done from the AWS S3 console as seen here:
 
   <img src="/docs/img/aws_backup_public.png" class="shadow haze"><br/>
 
 * Copy the new public URL of the latest backup for use as the `--restore-url` below.
 
+  <img src="/docs/img/aws_backup_link.png" class="shadow haze"><br/>
+
 * Create a new Cloudron by following the [installing](/references/selfhosting.html#installing) section.
   When running the setup script, pass in the `--restore-key` and `--restore-url` flags.
   The `--restore-key` is the backup encryption key. It can be displayed with `cloudron machine info`
@@ -296,6 +298,8 @@ $ ssh root@newserverip
 > ./cloudron-setup --domain <domain> --provider <digitalocean|ec2|generic|scaleway> --restore-key <encryptionKey> --restore-url <publicS3Url>
 ```
 
+ * Finally, once you see the newest version being displayed in your Cloudron webinterface, you can safely delete the old server instance.
+
 # Restore
 
 To restore a Cloudron from a specific backup: