AWS lightsail documentation change
Summary
Updated terminology from Bitnami to Lightsail and vice versa in specific sections, modified service management commands (replaced Bitnami scripts with systemctl for Apache and reverted in other sections), and standardized apostrophe usage in Let's Encrypt references.
Security assessment
The changes involve rebranding (Bitnami/Lightsail terminology swaps) and command syntax updates for service management. No security vulnerabilities, exploits, or weaknesses are mentioned. The modifications don't introduce new security features or address security flaws—they only adjust existing troubleshooting steps for certificate setup failures.
Diff
diff --git a/lightsail/latest/userguide/wordpress-setup-failures.md b/lightsail/latest/userguide/wordpress-setup-failures.md index 88a29296e..216b410b8 100644 --- a//lightsail/latest/userguide/wordpress-setup-failures.md +++ b//lightsail/latest/userguide/wordpress-setup-failures.md @@ -17 +17 @@ From the failure message, choose the **Download the error log** link to download -Bitnami +Lightsail @@ -48 +48 @@ This error can surface if another process is using port 80 while the HTTPS certi -Restart your WordPress instance. Then, run the guided workflow again. Use the following procedure to terminate any running processes on the instance that are running on port 80 if restarting doesn’t resolve the issue. +Restart your WordPress instance. Then, run the guided workflow again. Use the following procedure to terminate any running processes on the instance that are running on port 80 if restarting doesn't resolve the issue. @@ -54 +54 @@ Restart your WordPress instance. Then, run the guided workflow again. Use the fo - 2. Stop the Bitnami process that's running on the instance: + 2. Stop the Apache service that's running on the instance: @@ -56 +56 @@ Restart your WordPress instance. Then, run the guided workflow again. Use the fo - $ sudo /opt/bitnami/ctlscript.sh stop + $ sudo systemctl stop apache2 @@ -58 +58 @@ Restart your WordPress instance. Then, run the guided workflow again. Use the fo -Verify that the Bitnami process is stopped: +Verify that the Apache service is stopped: @@ -60 +60 @@ Verify that the Bitnami process is stopped: - $ sudo /opt/bitnami/ctlscript.sh status + $ sudo systemctl status apache2 @@ -150 +150 @@ In the command, replace `version` with the version of Ubuntu that the repository -One or more of your domains or subdomains has already been used to create 5 certificates within the last week. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let’s Encrypt website_. +One or more of your domains or subdomains has already been used to create 5 certificates within the last week. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let's Encrypt website_. @@ -162 +162 @@ Wait one week (168 hours), and then restart the guided workflow for this domain. -One or more of the domains or subdomains in the request has exceeded the limit of five validations per hour. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let’s Encrypt website_. +One or more of the domains or subdomains in the request has exceeded the limit of five validations per hour. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let's Encrypt website_. @@ -169 +169 @@ Wait one hour and run WordPress setup again. Verify that other validation errors -Lightsail +Bitnami @@ -200 +200 @@ This error can surface if another process is using port 80 while the HTTPS certi -Restart your WordPress instance. Then, run the guided workflow again. Use the following procedure to terminate any running processes on the instance that are running on port 80 if restarting doesn't resolve the issue. +Restart your WordPress instance. Then, run the guided workflow again. Use the following procedure to terminate any running processes on the instance that are running on port 80 if restarting doesn’t resolve the issue. @@ -206 +206 @@ Restart your WordPress instance. Then, run the guided workflow again. Use the fo - 2. Stop the Apache service that's running on the instance: + 2. Stop the Bitnami process that's running on the instance: @@ -208 +208 @@ Restart your WordPress instance. Then, run the guided workflow again. Use the fo - $ sudo systemctl stop apache2 + $ sudo /opt/bitnami/ctlscript.sh stop @@ -210 +210 @@ Restart your WordPress instance. Then, run the guided workflow again. Use the fo -Verify that the Apache service is stopped: +Verify that the Bitnami process is stopped: @@ -212 +212 @@ Verify that the Apache service is stopped: - $ sudo systemctl status apache2 + $ sudo /opt/bitnami/ctlscript.sh status @@ -302 +302 @@ In the command, replace `version` with the version of Ubuntu that the repository -One or more of your domains or subdomains has already been used to create 5 certificates within the last week. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let's Encrypt website_. +One or more of your domains or subdomains has already been used to create 5 certificates within the last week. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let’s Encrypt website_. @@ -314 +314 @@ Wait one week (168 hours), and then restart the guided workflow for this domain. -One or more of the domains or subdomains in the request has exceeded the limit of five validations per hour. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let's Encrypt website_. +One or more of the domains or subdomains in the request has exceeded the limit of five validations per hour. For more information, see [Rate Limits](https://letsencrypt.org/docs/rate-limits/) on the _Let’s Encrypt website_.