AWS lightsail high security documentation change
Summary
Added dedicated steps for SSL/TLS certificate regeneration during migration
Security assessment
Explicitly highlights that SSL/TLS certificates must be regenerated after migration. Failure to do so would break HTTPS encryption, leading to man-in-the-middle risks.
Diff
diff --git a/lightsail/latest/userguide/migrate-from-bitnami-to-lightsail-blueprints.md b/lightsail/latest/userguide/migrate-from-bitnami-to-lightsail-blueprints.md index d3213f376..161877fee 100644 --- a//lightsail/latest/userguide/migrate-from-bitnami-to-lightsail-blueprints.md +++ b//lightsail/latest/userguide/migrate-from-bitnami-to-lightsail-blueprints.md @@ -7 +7 @@ -Supported Lightsail blueprintsPrerequisitesStep 1: Back up your application dataStep 2: Create a new Lightsail instance with the Lightsail blueprintStep 3: Configure your new instanceStep 4: Restore your application dataStep 5: Verify the migrationStep 6: Update DNS and networking (if applicable)Step 7: Delete the old instance +Supported Lightsail blueprintsPrerequisitesStep 1: Back up your application dataStep 2: Create a new Lightsail instance with the Lightsail blueprintStep 3: Configure your new instanceStep 4: Restore your application dataStep 5: Verify the migrationStep 6: Transfer the static IP address (if applicable)Step 7: Regenerate SSL/TLS certificates (if applicable)Step 8: Delete the old instance @@ -173 +173 @@ After restoring your data, verify that the application is working correctly: -## Step 6: Update DNS and networking (if applicable) +## Step 6: Transfer the static IP address (if applicable) @@ -181,2 +180,0 @@ If your application uses a custom domain with a static IP already attached to yo - 3. **Re-generate your SSL/TLS certificates** on the new instance, as the certificates from the old instance cannot be transferred. For WordPress, refer to [Enable HTTPS with guided workflow](./amazon-lightsail-enabling-https-on-wordpress.html). - @@ -188 +186,5 @@ If your application uses a custom domain with a static IP already attached to yo -If you did not previously have a static IP attached, attach a new static IP to your new instance first, then update your DNS records to point your domain to the new static IP address. Allow time for DNS propagation before decommissioning the old instance. +If your application uses a custom domain but you did not previously have a static IP attached, attach a new static IP to your new instance first, then update your DNS records to point your domain to the new static IP address. Allow time for DNS propagation before decommissioning the old instance. + +## Step 7: Regenerate SSL/TLS certificates (if applicable) + +The SSL/TLS certificates from your old instance cannot be transferred to the new instance. You must regenerate them on the new instance. For WordPress, refer to [Enable HTTPS with guided workflow](./amazon-lightsail-enabling-https-on-wordpress.html). @@ -190 +192 @@ If you did not previously have a static IP attached, attach a new static IP to y -## Step 7: Delete the old instance +## Step 8: Delete the old instance