AWS lightsail documentation change
Summary
Updated WordPress Multisite guide to replace Bitnami references with Lightsail branding, changed application password retrieval command, replaced domain configuration tool with AWS script, updated images, and renumbered steps.
Security assessment
Changes involve rebranding (Bitnami to Lightsail), command updates (e.g., password retrieval from ~/application_credentials instead of bitnami_application_password), and script replacements (/opt/aws/wordpress/update_multisite_domain.sh instead of Bitnami tools). No security vulnerabilities, patches, or security feature additions are mentioned. Changes are procedural/documentation improvements without security implications.
Diff
diff --git a/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress-multisite.md b/lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress-multisite.md index 5eda43407..be325aaeb 100644 --- a//lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress-multisite.md +++ b//lightsail/latest/userguide/amazon-lightsail-quick-start-guide-wordpress-multisite.md @@ -15 +15 @@ Here are a few steps you should take to get started after your WordPress Multisi -Bitnami +Lightsail @@ -18,5 +18 @@ Bitnami -## Step 1: Read the Bitnami documentation - -Read the Bitnami documentation to learn how to configure your WordPress Multisite instance. For more information, see the [WordPress Multisite Packaged By Bitnami For AWS Cloud](https://docs.bitnami.com/aws/apps/wordpress-multisite/). - -## Step 2: Get the default application password to access the WordPress administration dashboard +## Step 1: Get the default application password to access the WordPress administration dashboard @@ -24 +20 @@ Read the Bitnami documentation to learn how to configure your WordPress Multisit -Complete the following procedure to get the default application password required to access the administration dashboard for your WordPress Multisite website. For more information, see [Getting the application user name and password for your Bitnami instance in Amazon Lightsail](./log-in-to-your-bitnami-application-running-on-amazon-lightsail.html). +Complete the following procedure to get the default application password required to access the administration dashboard for your WordPress Multisite website. @@ -32 +28 @@ Complete the following procedure to get the default application password require - cat $HOME/bitnami_application_password + cat ~/application_credentials @@ -36 +32 @@ You should see a response similar to the following example, which contains the d - + @@ -41 +37 @@ You should see a response similar to the following example, which contains the d -## Step 3: Attach a static IP address to your instance +## Step 2: Attach a static IP address to your instance @@ -61 +57 @@ After the new static IP address is attached to your instance, you must complete - sudo /opt/bitnami/configure_app_domain --domain <StaticIP> + sudo /opt/aws/wordpress/update_multisite_domain.sh <StaticIP> @@ -65,12 +61 @@ After the new static IP address is attached to your instance, you must complete - sudo /opt/bitnami/configure_app_domain --domain 203.0.113.0 - -You should see a response similar to the following example. The WordPress website on your instance should now be aware of the new static IP address. - - - -###### Note - -If that command fails, you might be using an older version of the WordPress Multisite instance. Try running the following commands instead. Replace `<StaticIP>` with the new static IP address of your instance. - - cd /opt/bitnami/apps/wordpress - sudo ./bnconfig --machine_hostname <StaticIP> + sudo /opt/aws/wordpress/update_multisite_domain.sh 203.0.113.0 @@ -78 +63 @@ If that command fails, you might be using an older version of the WordPress Mult -After running those commands, enter the following command to keep the bnconfig tool from automatically running every time the server restarts. +The WordPress website on your instance should now be aware of the new static IP address. @@ -80 +65 @@ After running those commands, enter the following command to keep the bnconfig t - sudo mv bnconfig bnconfig.disabled + @@ -85 +70 @@ After running those commands, enter the following command to keep the bnconfig t -## Step 4: Sign in to the administration dashboard of your WordPress Multisite website +## Step 3: Sign in to the administration dashboard of your WordPress Multisite website @@ -87 +72 @@ After running those commands, enter the following command to keep the bnconfig t -Now that you have the default application password, complete the following procedure to navigate to your WordPress Multisite website's home page, and sign in to the administration dashboard. After you're signed in, you can start customizing your website and making administrative changes. For more information about what you can do in WordPress, see the Step 7: Read the WordPress Multisite documentation and continue configuring your website section later in this guide. +Now that you have the default application password, complete the following procedure to navigate to your WordPress Multisite website's home page, and sign in to the administration dashboard. After you're signed in, you can start customizing your website and making administrative changes. For more information about what you can do in WordPress, see the Step 6: Read the WordPress Multisite documentation and continue configuring your website section later in this guide. @@ -110 +95 @@ The WordPress administration dashboard appears. -## Step 5: Route traffic for your registered domain name to your WordPress Multisite website +## Step 4: Route traffic for your registered domain name to your WordPress Multisite website @@ -124 +109 @@ After your domain name is routing traffic to your instance, you must complete th - sudo /opt/bitnami/configure_app_domain --domain <DomainName> + sudo /opt/aws/wordpress/update_multisite_domain.sh <DomainName> @@ -128,12 +113 @@ After your domain name is routing traffic to your instance, you must complete th - sudo /opt/bitnami/configure_app_domain --domain www.example.com - -You should see a response similar to the following example. The WordPress Multisite software should now be aware of the domain name. - - - -###### Note - -If that command fails, you might be using an older version of the WordPress Multisite instance. Try running the following commands instead. Replace `<DomainName>` with the domain name that is routing traffic to your instance. - - cd /opt/bitnami/apps/wordpress - sudo ./bnconfig --machine_hostname <DomainName> + sudo /opt/aws/wordpress/update_multisite_domain.sh www.example.com @@ -141 +115 @@ If that command fails, you might be using an older version of the WordPress Mult -After running those commands, enter the following command to keep the bnconfig tool from automatically running every time the server restarts. +The WordPress Multisite software should now be aware of the domain name. @@ -143 +117 @@ After running those commands, enter the following command to keep the bnconfig t - sudo mv bnconfig bnconfig.disabled + @@ -148 +122 @@ After running those commands, enter the following command to keep the bnconfig t -If you browse to the domain name that you configured for your instance, you should be redirected to the main blog of your WordPress Multisite website. Next you must decide whether you want to add blogs as domains or as subdomains to your WordPress Multisite website. For more information, continue to the next Step 6: Add blogs as domains or subdomains to your WordPress Multisite website section of this guide. +If you browse to the domain name that you configured for your instance, you should be redirected to the main blog of your WordPress Multisite website. Next you must decide whether you want to add blogs as domains or as subdomains to your WordPress Multisite website. @@ -150 +124 @@ If you browse to the domain name that you configured for your instance, you shou -## Step 6: Add blogs as domains or subdomains to your WordPress Multisite website +## Step 5: Add blogs as domains or subdomains to your WordPress Multisite website @@ -161 +135 @@ WordPress Multisite is designed to host multiple blog websites on one instance o -## Step 7: Read the WordPress Multisite documentation and continue configuring your website +## Step 6: Read the WordPress Multisite documentation and continue configuring your website @@ -165 +139 @@ Read the WordPress Multisite documentation to learn how to administer and custom -## Step 8: Create a snapshot of your instance +## Step 7: Create a snapshot of your instance @@ -175 +149 @@ You can work with snapshots on your instance's management page on the **Snapshot -Lightsail +Bitnami @@ -178 +152 @@ Lightsail -## Step 1: Get the default application password to access the WordPress administration dashboard +## Step 1: Read the Bitnami documentation @@ -180 +154,5 @@ Lightsail -Complete the following procedure to get the default application password required to access the administration dashboard for your WordPress Multisite website. +Read the Bitnami documentation to learn how to configure your WordPress Multisite instance. For more information, see the [WordPress Multisite Packaged By Bitnami For AWS Cloud](https://docs.bitnami.com/aws/apps/wordpress-multisite/). + +## Step 2: Get the default application password to access the WordPress administration dashboard + +Complete the following procedure to get the default application password required to access the administration dashboard for your WordPress Multisite website. For more information, see [Getting the application user name and password for your Bitnami instance in Amazon Lightsail](./log-in-to-your-bitnami-application-running-on-amazon-lightsail.html). @@ -188 +166 @@ Complete the following procedure to get the default application password require - cat ~/application_credentials + cat $HOME/bitnami_application_password @@ -192 +170 @@ You should see a response similar to the following example, which contains the d - + @@ -197 +175 @@ You should see a response similar to the following example, which contains the d -## Step 2: Attach a static IP address to your instance +## Step 3: Attach a static IP address to your instance @@ -217 +195 @@ After the new static IP address is attached to your instance, you must complete - sudo /opt/aws/wordpress/update_multisite_domain.sh <StaticIP> + sudo /opt/bitnami/configure_app_domain --domain <StaticIP> @@ -221 +199 @@ After the new static IP address is attached to your instance, you must complete - sudo /opt/aws/wordpress/update_multisite_domain.sh 203.0.113.0 + sudo /opt/bitnami/configure_app_domain --domain 203.0.113.0 @@ -223 +201 @@ After the new static IP address is attached to your instance, you must complete -The WordPress website on your instance should now be aware of the new static IP address. +You should see a response similar to the following example. The WordPress website on your instance should now be aware of the new static IP address. @@ -225 +203 @@ The WordPress website on your instance should now be aware of the new static IP - + @@ -226,0 +205 @@ The WordPress website on your instance should now be aware of the new static IP +###### Note @@ -227,0 +207 @@ The WordPress website on your instance should now be aware of the new static IP +If that command fails, you might be using an older version of the WordPress Multisite instance. Try running the following commands instead. Replace `<StaticIP>` with the new static IP address of your instance. @@ -228,0 +209,6 @@ The WordPress website on your instance should now be aware of the new static IP + cd /opt/bitnami/apps/wordpress + sudo ./bnconfig --machine_hostname <StaticIP> + +After running those commands, enter the following command to keep the bnconfig tool from automatically running every time the server restarts. + + sudo mv bnconfig bnconfig.disabled @@ -230 +215,0 @@ The WordPress website on your instance should now be aware of the new static IP -## Step 3: Sign in to the administration dashboard of your WordPress Multisite website @@ -232 +217,5 @@ The WordPress website on your instance should now be aware of the new static IP -Now that you have the default application password, complete the following procedure to navigate to your WordPress Multisite website's home page, and sign in to the administration dashboard. After you're signed in, you can start customizing your website and making administrative changes. For more information about what you can do in WordPress, see the Step 6: Read the WordPress Multisite documentation and continue configuring your website section later in this guide. + + +## Step 4: Sign in to the administration dashboard of your WordPress Multisite website + +Now that you have the default application password, complete the following procedure to navigate to your WordPress Multisite website's home page, and sign in to the administration dashboard. After you're signed in, you can start customizing your website and making administrative changes. For more information about what you can do in WordPress, see the Step 7: Read the WordPress Multisite documentation and continue configuring your website section later in this guide. @@ -255 +244 @@ The WordPress administration dashboard appears. -## Step 4: Route traffic for your registered domain name to your WordPress Multisite website +## Step 5: Route traffic for your registered domain name to your WordPress Multisite website @@ -269 +258 @@ After your domain name is routing traffic to your instance, you must complete th - sudo /opt/aws/wordpress/update_multisite_domain.sh <DomainName> + sudo /opt/bitnami/configure_app_domain --domain <DomainName> @@ -273 +262 @@ After your domain name is routing traffic to your instance, you must complete th - sudo /opt/aws/wordpress/update_multisite_domain.sh www.example.com + sudo /opt/bitnami/configure_app_domain --domain www.example.com @@ -275 +264 @@ After your domain name is routing traffic to your instance, you must complete th -The WordPress Multisite software should now be aware of the domain name. +You should see a response similar to the following example. The WordPress Multisite software should now be aware of the domain name. @@ -277 +266,3 @@ The WordPress Multisite software should now be aware of the domain name. - + + +###### Note @@ -278,0 +270 @@ The WordPress Multisite software should now be aware of the domain name. +If that command fails, you might be using an older version of the WordPress Multisite instance. Try running the following commands instead. Replace `<DomainName>` with the domain name that is routing traffic to your instance. @@ -279,0 +272,6 @@ The WordPress Multisite software should now be aware of the domain name. + cd /opt/bitnami/apps/wordpress + sudo ./bnconfig --machine_hostname <DomainName> + +After running those commands, enter the following command to keep the bnconfig tool from automatically running every time the server restarts. + + sudo mv bnconfig bnconfig.disabled @@ -282 +279,0 @@ The WordPress Multisite software should now be aware of the domain name. -If you browse to the domain name that you configured for your instance, you should be redirected to the main blog of your WordPress Multisite website. Next you must decide whether you want to add blogs as domains or as subdomains to your WordPress Multisite website. @@ -284 +281,4 @@ If you browse to the domain name that you configured for your instance, you shou -## Step 5: Add blogs as domains or subdomains to your WordPress Multisite website + +If you browse to the domain name that you configured for your instance, you should be redirected to the main blog of your WordPress Multisite website. Next you must decide whether you want to add blogs as domains or as subdomains to your WordPress Multisite website. For more information, continue to the next Step 6: Add blogs as domains or subdomains to your WordPress Multisite website section of this guide. + +## Step 6: Add blogs as domains or subdomains to your WordPress Multisite website @@ -295 +295 @@ WordPress Multisite is designed to host multiple blog websites on one instance o -## Step 6: Read the WordPress Multisite documentation and continue configuring your website +## Step 7: Read the WordPress Multisite documentation and continue configuring your website @@ -299 +299 @@ Read the WordPress Multisite documentation to learn how to administer and custom -## Step 7: Create a snapshot of your instance +## Step 8: Create a snapshot of your instance