AWS lightsail documentation change
Summary
Restructured documentation flow, added domain/DNS considerations, updated Plesk setup steps, expanded security tool descriptions, and added guidance for static IP management.
Security assessment
The changes add documentation about security features like Let's Encrypt SSL certificates, Plesk Firewall, and ModSecurity. However, there's no evidence of addressing a specific security vulnerability or incident.
Diff
diff --git a/lightsail/latest/userguide/set-up-and-configure-plesk-stack-on-lightsail.md b/lightsail/latest/userguide/set-up-and-configure-plesk-stack-on-lightsail.md index 1abeba117..02993e9ea 100644 --- a//lightsail/latest/userguide/set-up-and-configure-plesk-stack-on-lightsail.md +++ b//lightsail/latest/userguide/set-up-and-configure-plesk-stack-on-lightsail.md @@ -5 +5 @@ -Step 1: Create a Plesk instanceStep 2: Sign in to the Plesk User Interface for the first timeStep 3: Read the Plesk documentationStep 4: Attach a static IP address to your Plesk instanceStep 5: Map your domain name to your Plesk instanceStep 6: Purchase a Plesk licenseStep 7: Create a snapshot of your Plesk instance +Considerations for deploying a Plesk hosting stackStep 1: Create a Plesk instanceStep 2: Sign in to the Plesk user interface for the first timeStep 3: Attach a static IP address to your Plesk instanceStep 4: Update your public IP address in PleskStep 5: Add a website to your Plesk instanceStep 6: Map your domain name to your Plesk instanceStep 7: Read the Plesk documentationStep 8: Purchase a Plesk licenseStep 9: Create a snapshot of your Plesk instance @@ -13 +13 @@ Did you know that you can enable automatic snapshots for your instance? With aut -Learn how to create a Plesk instance in Amazon Lightsail, and how to sign in to the Plesk User Interface for the first time by creating a username and password. You will also learn how to how to connect to and configure your Plesk instance after it is up and running. +Learn how to create a Plesk instance in Amazon Lightsail, and how to sign in to the Plesk User Interface for the first time by creating a username and password. You will also learn how to connect to and configure your Plesk instance after it is up and running. @@ -17 +17 @@ Learn how to create a Plesk instance in Amazon Lightsail, and how to sign in to -Instances launched with the **Plesk Hosting Stack on Ubuntu (BYOL)** blueprint have a 30-day trial license. After 30 days, you must purchase a license from Plesk to continue using the Plesk application. +Instances launched with the **Plesk Hosting Stack on Ubuntu (BYOL)** blueprint have a 30-day trial license. After 30 days, you must purchase and install a license from Plesk to continue using the Plesk application. For more information, see Step 8: Purchase a Plesk license. @@ -19 +19 @@ Instances launched with the **Plesk Hosting Stack on Ubuntu (BYOL)** blueprint h -Plesk hosting stacks in Lightsail include the following features. +With Plesk hosting stacks in Lightsail, you can accomplish tasks such as: @@ -21 +21 @@ Plesk hosting stacks in Lightsail include the following features. - * WordPress Toolkit, featuring automation in a graphical user interface + * Automate WordPress site management using WP Toolkit's graphical interface @@ -23 +23 @@ Plesk hosting stacks in Lightsail include the following features. - * Let's Encrypt support for SSL certificates and configuring encrypted (HTTPS) traffic on a single instance + * Secure your site with free SSL certificates and configure HTTPS traffic using Let's Encrypt @@ -25 +25 @@ Plesk hosting stacks in Lightsail include the following features. - * FTP access to transfer files to and from your instance + * Transfer files to and from your instance using FTP @@ -27 +27 @@ Plesk hosting stacks in Lightsail include the following features. - * Docker Proxy Rules + * Monitor and secure your server using web-based tools, including Plesk Firewall, Logs, and ModSecurity @@ -29 +29,16 @@ Plesk hosting stacks in Lightsail include the following features. - * Web-based server management and security tools, including Plesk Firewall, Logs, and ModSecurity + * Route inbound traffic from specific domains to designated container ports using Docker Proxy Rules + + + + +## Considerations for deploying a Plesk hosting stack + +Before you begin deploying your Plesk instance, determine if you need to register a domain for your website and how you want to manage it. You need a registered domain to access your website by a logical name (such as `http://example.com`) rather than by IP address. You also need a DNS name created within your domain to secure connections to your website with a certificate (required for HTTPS traffic). + +Review the following options for domain configuration and management: + + * If you already have a registered domain in Lightsail that you want to use, you can begin the steps in this tutorial. + + * If you have a domain with a different registrar that you prefer to manage your DNS records with, you can begin the steps in this tutorial. Otherwise, you can [transfer management of your domain's DNS records](https://docs.aws.amazon.com/lightsail/latest/userguide/lightsail-how-to-create-dns-entry.html#lightail-change-the-name-servers). This can help you to more efficiently manage all of your compute and DNS resources within Lightsail. + + * If you don't have a domain that you want to use, you can find and register one for your website. For more information on registering a domain with Lightsail, see [Register and manage domains for your website in Lightsail](https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-domain-registration.html). @@ -42 +57,5 @@ Complete the following steps to create a Plesk instance on Lightsail. - 3. Choose the location where you want to create your instance. + 3. Select a location for your instance (an AWS Region and Availability Zone). + +Choose **Change AWS Region and Availability Zone** to create your instance in another location. + + 4. Optionally, you can change the Availability Zone. @@ -44 +63 @@ Complete the following steps to create a Plesk instance on Lightsail. -Choose **Change AWS Region and Availability Zone** to change your instance location. +Choose **Change your Availability Zone**. @@ -46 +65 @@ Choose **Change AWS Region and Availability Zone** to change your instance locat - 4. Under **Apps + OS** , choose **Plesk Hosting Stack on Ubuntu (BYOL)**. + 5. Under **Apps + OS** , choose **Plesk Hosting Stack on Ubuntu (BYOL)**. @@ -48 +67 @@ Choose **Change AWS Region and Availability Zone** to change your instance locat - 5. Choose your instance plan. The $5 USD per month Lightsail plan does not support the Plesk hosting stack. + 6. Choose an available instance plan. @@ -50 +69,5 @@ Choose **Change AWS Region and Availability Zone** to change your instance locat - 6. Enter a name for your instance. +###### Tip + +For optimal website performance, select an instance plan that can accommodate the resource demands of the plugins and extensions that you plan to install. If you later require more compute power, you can [upsize your instance from a snapshot](https://docs.aws.amazon.com/lightsail/latest/userguide/how-to-create-larger-instance-from-snapshot-using-console.html). For more information about the requirements for plugins and extensions, consult the respective vendor's documentation. + + 7. Enter a name for your instance. @@ -62 +85,7 @@ Resource names: - 7. (Optional) Choose **Add new tag** to add a tag to your instance. Repeat this step as needed to add additional tags. For more information on tag usage, see [Tags](./amazon-lightsail-tags.html). + 8. (Optional) Choose **Add new tag** to add a tag to your instance. Repeat this step as needed to add additional tags. For more information on tag usage, such as for billing and resource organization, see [Tags](https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-tags.html). + + * For **Key** , enter a tag key. + + * (Optional) For **Value** , enter a tag value. + + 9. Choose **Create instance**. @@ -64 +92,0 @@ Resource names: - 1. For **Key** , enter a tag key. @@ -66 +93,0 @@ Resource names: - @@ -68 +94,0 @@ Resource names: - 2. (Optional) For **Value** , enter a tag value. @@ -70 +96 @@ Resource names: - +Your instance takes a few minutes to provision and become available after you create it. @@ -72 +98,7 @@ Resource names: - 8. Choose **Create instance**. +###### Tip + +To streamline the initial setup process for Plesk, don't assign a static IP to your instance for now—you'll do this in a later step. If you attach a static IP to your Plesk instance now, you might get a one-time login URL that uses an outdated public IP address. This can occur because your instance might use the public IP address that was assigned initially rather than the static IP address. + +## Step 2: Sign in to the Plesk user interface for the first time + +###### Tip @@ -74 +106 @@ Resource names: -The instance requires a few minutes to provision and become available after you create it. +Keep your Lightsail console and Plesk user interface browser tabs open until you complete this tutorial as you'll be working through multiple steps in each. @@ -75,0 +108 @@ The instance requires a few minutes to provision and become available after you +Use the following procedure to obtain a one-time login URL to access the Plesk user interface as an administrator. This interface is where you'll create and manage your websites. @@ -76,0 +110 @@ The instance requires a few minutes to provision and become available after you +###### To obtain a one-time login URL @@ -77,0 +112 @@ The instance requires a few minutes to provision and become available after you + 1. In the left navigation pane, choose Instances. @@ -79 +114 @@ The instance requires a few minutes to provision and become available after you -If you experience issues after launching your Plesk instance, go to the Plesk support page to see if there are updates that need to be installed on the instance. For more information, see the [Plesk help center](https://support.plesk.com/hc/) and [Plesk Updates](https://docs.plesk.com/en-US/obsidian/administrator-guide/plesk-updates.59215/) in the _Plesk Documentation and Help Portal_. + 2. Choose the name of the Plesk instance that you created. @@ -81 +116 @@ If you experience issues after launching your Plesk instance, go to the Plesk su -## Step 2: Sign in to the Plesk User Interface for the first time + 3. On your instance management page, under the **Connect** tab, choose **Connect using SSH**. @@ -83 +118 @@ If you experience issues after launching your Plesk instance, go to the Plesk su -Use the following procedure to obtain a one-time login URL. You need the one-time login URL to access the Plesk User Interface as an administrator. +###### Note @@ -85 +120 @@ Use the following procedure to obtain a one-time login URL. You need the one-tim - 1. On your instance management page, under the **Connect** tab, choose **Connect using SSH**. +If you attempt to connect too quickly after launching the instance, you might experience a connection or SSH key error. If you see these issues while connecting, wait a few minutes and try again. @@ -87 +122 @@ Use the following procedure to obtain a one-time login URL. You need the one-tim - 2. After you're connected, enter the following command to get the one-time login URL. + 4. After you're connected, enter the following command to get the one-time login URL. @@ -89 +124 @@ Use the following procedure to obtain a one-time login URL. You need the one-tim - sudo plesk login | grep -v internal:8 + sudo plesk login | grep plesk.page @@ -93 +128 @@ You should see a response similar to the following example, which contains the o - https://heuristic-bassi.192-0-2-0.plesk.page/login?secret=ce-e3b0c44298fc1c149afbf4c8996fb92427 + https://heuristic-bassi.192-0-2-0.plesk.page/login?secret=ce-EXAMPLE298fc1c149afbf4c8996fb92427 @@ -95 +130,7 @@ You should see a response similar to the following example, which contains the o -###### Tip +###### Note + +If your public IP address has changed (for example, you assigned a static IP since it was launched), you'll need to modify the returned URL to match your new address to access the login page. + + 5. Select the one-time login URL in the browser-based connection window and copy it. + + 6. Paste the URL in your web browser to access the Plesk login page. @@ -97 +138 @@ You should see a response similar to the following example, which contains the o -If you recently attached a static IP to your Plesk instance, you might get a one-time login URL that uses the old public IP address. Reboot the instance, and then run the above command again to get a one-time login URL that uses the new static, public IP address. + 7. Follow the instructions on the page to create your sign in credentials for Plesk. You should see an option to add your domain to Plesk when you sign in for the first time. @@ -99 +140,6 @@ If you recently attached a static IP to your Plesk instance, you might get a one - 3. Copy and paste the one-time login URL into a web browser. + + + +## Step 3: Attach a static IP address to your Plesk instance + +The default dynamic public IP address attached to your instance changes every time you stop and start the instance. To keep the public IP address from changing, create a static IP address and attach it to your instance. In a later step, you'll map your static IP address to your domain name. With this mapping configured, you don't have to update your domain's DNS records each time you stop and start the instance. @@ -103 +149,3 @@ If you recently attached a static IP to your Plesk instance, you might get a one -You might see a browser warning that your connection is not private, not secure, or that there’s a security risk. This happens because your Plesk instance does not yet have an SSL/TLS certificate applied to it. In the browser window, choose **Advanced** , **Details** , or **More information** to view the options that are available. Then choose to proceed to the website even if it’s not private or secure. +You can only attach one static IP to a Lightsail instance. Static IP addresses are only free when they are attached to an instance. + +###### To attach a static IP and update your public IP address in Plesk @@ -105 +153 @@ You might see a browser warning that your connection is not private, not secure, - 4. Follow the instructions on the page to create your sign in credentials for Plesk. You should see an option to add your domain to Plesk when you sign in for the first time. + 1. Sign in to the Lightsail console at [https://lightsail.aws.amazon.com/](https://lightsail.aws.amazon.com/). @@ -106,0 +155 @@ You might see a browser warning that your connection is not private, not secure, + 2. On the **Instances** home page of the Lightsail console, choose the name of your Plesk instance. @@ -107,0 +157 @@ You might see a browser warning that your connection is not private, not secure, + 3. Under the **Networking** tab, choose **Attach static IP**. @@ -108,0 +159 @@ You might see a browser warning that your connection is not private, not secure, + 4. Create and attach a static IP address. @@ -110 +161 @@ You might see a browser warning that your connection is not private, not secure, -To sign in again later, navigate to `https://`PublicIPAddress`:8443`. Replace `PublicIPAddress` with the public IP address or static IP address of your instance. For example, `https://`192.0.2.0`/:8443`. Then enter the username and password you created earlier to sign in to the Plesk User Interface. + * To create and attach a static IP when none exists in the Region: @@ -112 +163 @@ To sign in again later, navigate to `https://`PublicIPAddress`:8443`. Replace `P -## Step 3: Read the Plesk documentation + 1. Enter a name to identify the static IP. @@ -114 +165 @@ To sign in again later, navigate to `https://`PublicIPAddress`:8443`. Replace `P -Read the Plesk documentation to learn how to administer websites, customize the Plesk User Interface, and more. + 2. Choose **Create and attach**. @@ -116 +167,19 @@ Read the Plesk documentation to learn how to administer websites, customize the -For more information, see the [Getting Started with Managing Websites in Plesk](https://docs.plesk.com/en-US/obsidian/quick-start-guide/read-me-first.74371/) in the _Plesk Documentation and Help Portal_. + 3. Choose **Continue**. + + * To create and attach a new static IP when you already have one in the Region: + + 1. Choose the **Select a static IP** menu to display the available options. + + 2. Choose **Create a new static IP** in the dropdown menu. + + 3. Enter a name to identify the static IP. + + 4. Choose **Create and attach**. + + 5. Choose **Continue**. + + * To use an existing static IP in the Region: + + 1. Choose the **Select a static IP** menu to display the available options. + + 2. Choose an already available static IP in the dropdown menu. @@ -118 +187 @@ For more information, see the [Getting Started with Managing Websites in Plesk]( -## Step 4: Attach a static IP address to your Plesk instance + 3. Choose **Attach**. @@ -120 +188,0 @@ For more information, see the [Getting Started with Managing Websites in Plesk]( -The default dynamic public IP address attached to your instance changes every time you stop and start the instance. You can create a static IP address and attach it to your instance to keep the public IP address from changing. Later, when you use your domain name with your instance, you don’t have to update your domain’s DNS records each time you stop and start the instance. You can attach only one static IP address to each instance. @@ -122 +189,0 @@ The default dynamic public IP address attached to your instance changes every ti -On the instance management page, under the **Networking** tab, choose **Create a static IP** or **Attach static IP** (if you previously created a static IP that you can attach to your instance), then follow the instructions on the page. For more information, see [Create a static IP and attach it to an instance](./lightsail-create-static-ip.html). @@ -124 +190,0 @@ On the instance management page, under the **Networking** tab, choose **Create a - @@ -126 +192 @@ On the instance management page, under the **Networking** tab, choose **Create a