diff --git a/docs/guides/kubernetes/deploy-lke-cluster-using-pulumi/index.md b/docs/guides/kubernetes/deploy-lke-cluster-using-pulumi/index.md index 0684d1d23d4..bf838148413 100644 --- a/docs/guides/kubernetes/deploy-lke-cluster-using-pulumi/index.md +++ b/docs/guides/kubernetes/deploy-lke-cluster-using-pulumi/index.md @@ -35,7 +35,7 @@ This guide walks you through the steps needed to deploy a Kubernetes cluster usi ## Create your Pulumi Infrastructure Code -Create Pulumi infrastructure code that define the resources needed to create a Kubernetes cluster. You can create a minimal Pulumi project containing your [resources](https://www.pulumi.com/docs/concepts/resources/), a [stack](https://www.pulumi.com/docs/concepts/stack/) which is an instance of your Pulumi program, and the [configuration values](https://www.pulumi.com/docs/concepts/config/) for your stack. Setting up your Pulumi project in this way allows you to reuse your Pulumi program to deploy more Kubernetes clusters, if desired, by way of additional stacks. +Create Pulumi infrastructure code that define the resources needed to create a Kubernetes cluster. You can create a minimal Pulumi project containing your [resources](https://www.pulumi.com/docs/concepts/resources/), a [stack](https://www.pulumi.com/docs/concepts/stack/) which is an instance of your Pulumi program, and the [configuration values](https://www.pulumi.com/docs/concepts/config/) for your stack. Setting up your Pulumi project in this way lets you reuse your Pulumi program to deploy more Kubernetes clusters, if desired, by way of additional stacks. ### Create your Pulumi project @@ -260,7 +260,7 @@ Now that all your Pulumi configuration is ready, you can deploy your Kubernetes Now that your Kubernetes cluster is deployed, you can use kubectl to connect to it and begin defining your workload. Access your cluster's kubeconfig and use it to connect to your cluster with kubectl. -1. Use Pulumi to access your cluster's kubeconfig, decode its contents, and save them to a file. Pulumi returns a [base64](https://en.wikipedia.org/wiki/Base64) encoded string (a useful format for automated pipelines) representing your kubeconfig. Replace `lke-cluster-config.yaml` with your preferred file name. +1. Use Pulumi to access your cluster's kubeconfig, decode its contents, and save them to a file. Pulumi returns a [base64](https://en.wikipedia.org/wiki/Base64) encoded string (a useful format for automated pipelines) representing your kubeconfig. Replace `lke-cluster-config.yaml` with your preferred filename. ```command export KUBE_VAR=`pulumi stack output kubeconfig --show-secrets` && echo $KUBE_VAR | base64 -di > lke-cluster-config.yaml diff --git a/docs/guides/kubernetes/deploy-lke-cluster-using-terraform/index.md b/docs/guides/kubernetes/deploy-lke-cluster-using-terraform/index.md index f40898b1011..54de671107d 100644 --- a/docs/guides/kubernetes/deploy-lke-cluster-using-terraform/index.md +++ b/docs/guides/kubernetes/deploy-lke-cluster-using-terraform/index.md @@ -123,7 +123,7 @@ Terraform defines the elements of your Linode infrastructure inside of configura This file contains your cluster’s main configuration arguments and output variables. In this example, you make use of Terraform’s input variables so that your `main.tf` configuration can be easily reused across different clusters. - Variables and their values will be created in separate files later on in this guide. Using separate files for variable declaration allows you to avoid hard-coding values into your resources. This strategy can help you reuse, share, and version control your Terraform configurations. + Variables and their values will be created in separate files later on in this guide. Using separate files for variable declaration lets you avoid hard-coding values into your resources. This strategy can help you reuse, share, and version control your Terraform configurations. This configuration file uses the Linode provider to create a Kubernetes cluster. All arguments within the `linode_lke_cluster.foobar` resource are required, except for `tags`. The `pool` argument accepts a list of pool objects. In order to read their input variable values, the configuration file makes use of Terraform's [dynamic blocks](https://www.terraform.io/docs/configuration/expressions.html#dynamic-blocks). Finally, [output values](https://www.terraform.io/docs/configuration/outputs.html) are declared in order to capture your cluster's attribute values that will be returned to Terraform after creating your cluster. diff --git a/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/index.md b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/index.md index 21993b23d14..70f770da49b 100644 --- a/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/index.md +++ b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/index.md @@ -282,7 +282,7 @@ Next, you need to determine which partition your root file system is installed o ### Transfer the System to a New Ext4 Disk -This next step involves making changes to your disks and configuration profiles, which then allows you to transfer your data to a *ext4* formatted disk. +This next step involves making changes to your disks and configuration profiles, which then lets you transfer your data to a *ext4* formatted disk. 1. In the Cloud Manager, navigate to the **Storage** tab. From here, you can delete the *Installer* disk and create two additional disks. @@ -346,4 +346,4 @@ You now should have a Linux system that's compatible with the Linode Platform. F ## Save the System as a Custom Image -If you wish to save a copy of this system to quickly deploy later, you may want to use Linode's Custom Image feature. This allows you to create a Compute Instance based on this system without needing to go through this guide again. See [Capture an Image](/docs/products/tools/images/guides/capture-an-image/) for instructions on creating the image. \ No newline at end of file +If you wish to save a copy of this system to quickly deploy later, you may want to use Linode's Custom Image feature. This lets you create a Compute Instance based on this system without needing to go through this guide again. See [Capture an Image](/docs/products/tools/images/guides/capture-an-image/) for instructions on creating the image. \ No newline at end of file diff --git a/docs/products/_index.md b/docs/products/_index.md index a93de688287..b651ec6ae3b 100644 --- a/docs/products/_index.md +++ b/docs/products/_index.md @@ -2,7 +2,7 @@ title = "All Products" linkTitle = "Products" title_meta = "Linode Product Documentation" -description = "Get started using the Cloud Manager, CLI, and API to deploy Linode services and manage your account." +description = "Get started using Cloud Manager, CLI, and API to deploy Linode services and manage your account." [[cascade]] weightAge = 0 diff --git a/docs/products/compute/compute-instances/_index.md b/docs/products/compute/compute-instances/_index.md index f284854dbab..c5b80b54308 100644 --- a/docs/products/compute/compute-instances/_index.md +++ b/docs/products/compute/compute-instances/_index.md @@ -36,7 +36,7 @@ In addition to the resources allocated to each available plan (outlined above), - Dedicated IPv4 and IPv6 addresses (additional addresses available on request) - Deploy using the many available [Linux Distributions](https://www.linode.com/distributions/), [Marketplace Apps](https://www.linode.com/marketplace/), or Community [StackScripts](https://www.linode.com/products/stackscripts/) - Direct console access through [Lish](/docs/products/compute/compute-instances/guides/lish/) -- Provisioning and management through the [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) +- Provisioning and management through [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) - [Multi-queue NIC](/docs/products/compute/compute-instances/guides/multiqueue-nic/) support on plans with 2 or more vCPU cores. \**If a service is not active for the entire month, the amount of network transfer allowance is prorated based on the number of hours the service is active.* @@ -50,7 +50,7 @@ Linode bundles the following services with all Compute Instances: - Seamless firewall management with [Cloud Firewalls](https://www.linode.com/products/cloud-firewall/) - Private Layer 2 networks with [VLANs](https://www.linode.com/products/vlan/) - Physical placement of your Compute Instances in a data center with [Placement Groups](/docs/products/compute/compute-instances/guides/placement-groups/) -- Metrics and monitoring through the [Cloud Manager](https://www.linode.com/products/monitoring/) and [Longview](/docs/products/tools/longview/) (free plan) +- Metrics and monitoring through [Cloud Manager](https://www.linode.com/products/monitoring/) and [Longview](/docs/products/tools/longview/) (free plan) - Reusable deployment scripts through [StackScripts](https://www.linode.com/products/stackscripts/) ## Complementary Paid Services diff --git a/docs/products/compute/compute-instances/developers/index.md b/docs/products/compute/compute-instances/developers/index.md index bebe515ff79..517d75f4232 100644 --- a/docs/products/compute/compute-instances/developers/index.md +++ b/docs/products/compute/compute-instances/developers/index.md @@ -16,12 +16,12 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage Linode Instances](/docs/products/tools/cli/guides/linode-instances/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage Linode Instances](/docs/products/tools/cli/guides/linode-instances/). ## Third Party Tools & Integrations **Terraform**: Terraform is an Infrastructure-as-code tool that includes management features for various types of Linode resources. Use Linode’s [official Terraform Provider](https://registry.terraform.io/providers/linode/linode/latest/docs) to [provision Linode Environments](/docs/guides/how-to-build-your-infrastructure-using-terraform-and-linode/). To learn more about Terraform see our documentation library’s [Terraform section](/docs/applications/configuration-management/terraform/). -**Pulumi**: Pulumi is a development tool that allows you to write computer programs which deploy cloud resources. With [Pulumi’s Linode integration](https://github.com/pulumi/pulumi-linode), you can manage your Linode resources in several programming languages, like JavaScript, Go, Python, and TypeScript. Pulumi manages your resources in the same way as Linode's API or CLI. See [Pulumi’s documentation](https://www.pulumi.com/docs/intro/cloud-providers/linode/) to get started. +**Pulumi**: Pulumi is a development tool that lets you write computer programs which deploy cloud resources. With [Pulumi’s Linode integration](https://github.com/pulumi/pulumi-linode), you can manage your Linode resources in several programming languages, like JavaScript, Go, Python, and TypeScript. Pulumi manages your resources in the same way as Linode's API or CLI. See [Pulumi’s documentation](https://www.pulumi.com/docs/intro/cloud-providers/linode/) to get started. - [Getting Started with Pulumi](/docs/guides/deploy-in-code-with-pulumi/) diff --git a/docs/products/compute/compute-instances/faqs/_index.md b/docs/products/compute/compute-instances/faqs/_index.md index 3aeaa3ab585..6ec47a522cb 100644 --- a/docs/products/compute/compute-instances/faqs/_index.md +++ b/docs/products/compute/compute-instances/faqs/_index.md @@ -53,7 +53,7 @@ First, you might want to give the [Linode Backup Service](http://www.linode.com/ - [Introduction to Rsync](/docs/guides/introduction-to-rsync/): Using `rsync` to mirror files to another server. - [Using Rdiff-backup with SSHFS](/docs/guides/using-rdiff-backup-with-sshfs/): An easy approach to using the `rdiff-backup` utility to maintain differential backups. -- [Cloning a Disk](/docs/products/compute/compute-instances/guides/clone-instance/#clone-to-an-existing-compute-instance): Creating an exact copy of a disk in the Cloud Manager. +- [Cloning a Disk](/docs/products/compute/compute-instances/guides/clone-instance/#clone-to-an-existing-compute-instance): Creating an exact copy of a disk in Cloud Manager. - [Copying a Disk Over SSH](/docs/products/compute/compute-instances/guides/copy-a-disk-image-over-ssh/): How to download an exact binary image of your Compute Instance's disk over SSH. ## How can I install software on my Compute Instance? @@ -62,17 +62,17 @@ Please refer to our guide on [Linux package management](/docs/guides/linux-packa ## How do I add another IP address? -You may add an [additional public IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#adding-an-ip-address) from the **Networking** tab for each Compute Instance in the Cloud Manager. After you've added a new IP address, you must [configure static networking](/docs/products/compute/compute-instances/guides/manual-network-configuration/) or enable [Network Helper](/docs/products/compute/compute-instances/guides/network-helper/#individual-compute-instance-setting) and reboot your instance before it can be used. +You may add an [additional public IP address](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#adding-an-ip-address) from the **Networking** tab for each Compute Instance in Cloud Manager. After you've added a new IP address, you must [configure static networking](/docs/products/compute/compute-instances/guides/manual-network-configuration/) or enable [Network Helper](/docs/products/compute/compute-instances/guides/network-helper/#individual-compute-instance-setting) and reboot your instance before it can be used. {{< note >}} -We require technical justification for the issuance of new IP addresses; you may need to open a ticket from the [Support Tickets](https://cloud.linode.com/support/tickets) section of the Cloud Manager explaining the reason for the new IP. +We require technical justification for the issuance of new IP addresses; you may need to open a ticket from the [Support Tickets](https://cloud.linode.com/support/tickets) section of Cloud Manager explaining the reason for the new IP. {{< /note >}} -If you'd like to take advantage of our private networking feature, you may add a private IP to your Compute Instance from the **Networking** tab for each instance in the Cloud Manager. Private IP addresses are not publicly accessible, although they are accessible from other Compute Instances in the same data center. Although we take measures to prevent others from intercepting your private IP traffic, you may still wish to configure a firewall to allow access from only the Compute Instances that you operate. +If you'd like to take advantage of our private networking feature, you may add a private IP to your Compute Instance from the **Networking** tab for each instance in Cloud Manager. Private IP addresses are not publicly accessible, although they are accessible from other Compute Instances in the same data center. Although we take measures to prevent others from intercepting your private IP traffic, you may still wish to configure a firewall to allow access from only the Compute Instances that you operate. ## How do I set the reverse DNS for an IP address? -To [set rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/), you can use the **More Options** ellipsis next to your Compute Instance's IPv4 address from the **Networking** tab in the Cloud Manager. Please note that the value you specify needs to match an A record or CNAME in DNS pointing to your Compute Instance's IP address. It may take up to 48 hours for reverse DNS updates to take effect. +To [set rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/), you can use the **More Options** ellipsis next to your Compute Instance's IPv4 address from the **Networking** tab in Cloud Manager. Please note that the value you specify needs to match an A record or CNAME in DNS pointing to your Compute Instance's IP address. It may take up to 48 hours for reverse DNS updates to take effect. ## Why does my Compute Instance keep crashing? @@ -82,11 +82,11 @@ If an application is crashing, be sure to check its error logs. These are typica ## Why is my connection to my Compute Instance slow or broken? -First, check to be sure that the service (SSH, HTTP, etc.) you're trying to access is running. If your Compute Instance runs a firewall, [check your firewall rules](/docs/guides/control-network-traffic-with-iptables/#view-your-current-iptables-rules) to ensure that you're allowing traffic to the desired destination. If this doesn't help, generate [MTR reports](/docs/guides/diagnosing-network-issues-with-mtr/) to and from your Compute Instance, and [submit them](/docs/products/platform/get-started/guides/support/#contact-customer-support) via the [Support Tickets](https://cloud.linode.com/support/tickets) section in the Cloud Manager. You may need to use [Lish](/docs/products/compute/compute-instances/guides/lish/) if you're having problems reaching your Compute Instance via normal networking. +First, check to be sure that the service (SSH, HTTP, etc.) you're trying to access is running. If your Compute Instance runs a firewall, [check your firewall rules](/docs/guides/control-network-traffic-with-iptables/#view-your-current-iptables-rules) to ensure that you're allowing traffic to the desired destination. If this doesn't help, generate [MTR reports](/docs/guides/diagnosing-network-issues-with-mtr/) to and from your Compute Instance, and [submit them](/docs/products/platform/get-started/guides/support/#contact-customer-support) via the [Support Tickets](https://cloud.linode.com/support/tickets) section in Cloud Manager. You may need to use [Lish](/docs/products/compute/compute-instances/guides/lish/) if you're having problems reaching your Compute Instance via normal networking. ## How can I upgrade or downgrade my Compute Instance? -You can change your Compute Instance's plan by using the Resize feature in the Cloud manager. If you're downgrading, please make sure you've resized your disk images to fit within your desired plan's disk space allocation before issuing the resize job. For instructions, refer to our guide on [Resizing a Compute Instance](/docs/products/compute/compute-instances/guides/resize/). +You can change your Compute Instance's plan by using the Resize feature in Cloud Manager. If you're downgrading, please make sure you've resized your disk images to fit within your desired plan's disk space allocation before issuing the resize job. For instructions, refer to our guide on [Resizing a Compute Instance](/docs/products/compute/compute-instances/guides/resize/). ## How can I test downloads speeds from different data centers? @@ -94,7 +94,7 @@ You may use our [speed test](http://www.linode.com/speedtest/) page to check lat ## Can I transfer my Compute Instance to another data center? -Yes. Any time you'd like to transfer your Compute Instance, you can proceed with a migration from the **Disks/Configs** tab for any instance within the [Cloud Manager](https://cloud.linode.com). For more information, see our [Data Center Migration Guide](/docs/products/compute/compute-instances/guides/migrate-to-different-dc/). +Yes. Any time you'd like to transfer your Compute Instance, you can proceed with a migration from the **Disks/Configs** tab for any instance within [Cloud Manager](https://cloud.linode.com). For more information, see our [Data Center Migration Guide](/docs/products/compute/compute-instances/guides/migrate-to-different-dc/). A migration will result in some changes that will be displayed in a caution message for your review before officially beginning the migration process. Your disks and configuration profiles will move with your Compute Instance, although your IP addresses will need to change. We strongly recommend reviewing this caution message carefully before proceeding for a list of all changes that you can expect. @@ -110,4 +110,4 @@ For those just getting started with Linux systems, we've created a series of gui ## Where can I get help with something not covered here? -We always recommend consulting our excellent [user community](https://www.linode.com/community/questions/) first when faced with a question that doesn't seem to be addressed in our documentation. There is also an active community of users available to help on [IRC](https://www.linode.com/chat). If you get stuck you may also open a [support](https://www.linode.com/contact) ticket from the "Get Help" sidebar in the Cloud Manager. \ No newline at end of file +We always recommend consulting our excellent [user community](https://www.linode.com/community/questions/) first when faced with a question that doesn't seem to be addressed in our documentation. There is also an active community of users available to help on [IRC](https://www.linode.com/chat). If you get stuck you may also open a [support](https://www.linode.com/contact) ticket from the "Get Help" sidebar in Cloud Manager. \ No newline at end of file diff --git a/docs/products/compute/compute-instances/get-started/index.md b/docs/products/compute/compute-instances/get-started/index.md index 1497e3b3024..6476aba52c5 100644 --- a/docs/products/compute/compute-instances/get-started/index.md +++ b/docs/products/compute/compute-instances/get-started/index.md @@ -12,7 +12,7 @@ Compute Instances (cloud-based virtual machines) are the foundational infrastruc ## Create a Compute Instance -Compute Instances can be deployed using the Cloud Manager, the Linode API, or the Linode CLI. For instructions on deploying one through the Cloud Manager, see the following guides: +Compute Instances can be deployed using Cloud Manager, the Linode API, or the Linode CLI. For instructions on deploying one through Cloud Manager, see the following guides: - [Create a Compute Instance](/docs/products/compute/compute-instances/guides/create/) - [Choosing a Compute Instance Type and Plan](/docs/products/compute/compute-instances/plans/choosing-a-plan/) @@ -23,9 +23,9 @@ Consider deploying an app from the [Linode Marketplace](https://www.linode.com/m ## Connect to the Instance -After the Compute Instance is finished provisioning and has fully booted up, you can connect to it through the built-in Lish Console in the Cloud Manager (or via the SSH Lish Gateway) or SSH directly to your new system. +After the Compute Instance is finished provisioning and has fully booted up, you can connect to it through the built-in Lish Console in Cloud Manager (or via the SSH Lish Gateway) or SSH directly to your new system. -- **Weblish (via the Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). +- **Weblish (via Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). - **SSH:** Copy the command from the *SSH Access* field that is available in Cloud Manager under the **Access** section on the Compute Instance's detail page. Paste the command into your local computer's terminal. The command should look similar to the following, only with the IP address of your newly created instance. diff --git a/docs/products/compute/compute-instances/guides/clone-instance/index.md b/docs/products/compute/compute-instances/guides/clone-instance/index.md index 8227669c0cb..3fd5c7e9aeb 100644 --- a/docs/products/compute/compute-instances/guides/clone-instance/index.md +++ b/docs/products/compute/compute-instances/guides/clone-instance/index.md @@ -9,7 +9,7 @@ tags: ["linode platform","cloud manager"] aliases: ['/migrate-to-linode/disk-images/clone-your-linode/','/platform/disk-images/clone-your-linode/','/platform/disk-images/clone-your-linode-classic-manager/','/guides/clone-your-linode/'] --- -Linode's cloning feature allows you to duplicate a Compute Instance's disks (and configuration profiles) to a new or existing instance. +Linode's cloning feature lets you duplicate a Compute Instance's disks (and configuration profiles) to a new or existing instance. ## Clone to a New Compute Instance @@ -19,7 +19,7 @@ This process copies all disks and configuration profiles to a newly created Comp Before continuing, you should power off the instance you want to clone. This helps prevent data corruption. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click the **Create** dropdown menu on the top left and select **Linode**. @@ -53,9 +53,9 @@ The new instance's IP address will be different than the original instance. If d ## Clone to an Existing Compute Instance -This process allows you to select specific disks or configuration profiles and duplicate them to an existing Compute Instance. When cloning a configuration profile, all disks assigned to that profile are also cloned. +This process lets you select specific disks or configuration profiles and duplicate them to an existing Compute Instance. When cloning a configuration profile, all disks assigned to that profile are also cloned. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select the **Linodes** link in the left sidebar menu. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select the **Linodes** link in the left sidebar menu. 1. Locate the Compute Instance you wish to clone and click its corresponding label, which displays the instance's detail page. @@ -71,7 +71,7 @@ This process allows you to select specific disks or configuration profiles and d 1. A **Clone** form appears with either the **Disks** or **Configuration Profiles** tab displayed, depending on the previous step. From here, select the exact disks and configuration profiles you wish to clone. When a configuration profile is selected, all disks assigned to it (through **Block Device Assignments**) are also selected. - ![The Clone form in the Cloud Manager](clone-disk.png) + ![The Clone form in Cloud Manager](clone-disk.png) 1. In the **Destination** dropdown menu, select the destination Compute Instance. diff --git a/docs/products/compute/compute-instances/guides/compute-migrations/index.md b/docs/products/compute/compute-instances/guides/compute-migrations/index.md index fd8dc7c8187..c551c170fce 100644 --- a/docs/products/compute/compute-instances/guides/compute-migrations/index.md +++ b/docs/products/compute/compute-instances/guides/compute-migrations/index.md @@ -7,7 +7,7 @@ keywords: ['migrate','migration','host'] tags: ["linode platform","cloud manager"] --- -A migration occurs when a Compute Instance is moved from one physical host machine to another. This can happen within the same data center or across data centers. Migrations across data centers can be configured by customers in the Cloud Manager. All other types of migrations must be configured by a Linode or Akamai administrator. +A migration occurs when a Compute Instance is moved from one physical host machine to another. This can happen within the same data center or across data centers. Migrations across data centers can be configured by customers in Cloud Manager. All other types of migrations must be configured by a Linode or Akamai administrator. ## Types of Migrations @@ -70,13 +70,13 @@ In order for a live migration to occur, a host compatible with the host your ins - This applies to warm migrations initiated by customers, including warm migrations taking place during the warm resize process. - This also applies if you are running a custom distribution (i.e. Windows) or unsupported disk image that is not configured for ACPI shutdowns. - If a Linode or Akamai administrator cancels the warm migration. -- If the sources Linode stops responding, is shut down prior to the cross-host sync, or if the process is disturbed in any way. +- If the sources Linode stops responding, is shut down before the cross-host sync, or if the process is disturbed in any way. ### What should I do if my warm migration fails? -- If your warm migration fails to complete after an early initiation is triggered via the Cloud Manager, the Support team is notified. There are two options that are used at the discretion of the Support team. +- If your warm migration fails to complete after an early initiation is triggered via Cloud Manager, the Support team is notified. There are two options that are used at the discretion of the Support team. - A new warm migration can be configured to be performed at a scheduled time. - - A cold migration can be configured. You can then initiate the cold migration via the Cloud Manager or allow it to proceed as otherwise scheduled. + - A cold migration can be configured. You can then initiate the cold migration via Cloud Manager or allow it to proceed as otherwise scheduled. ### What should I do if my warm resize fails? diff --git a/docs/products/compute/compute-instances/guides/configuration-profiles/index.md b/docs/products/compute/compute-instances/guides/configuration-profiles/index.md index 1b39ef37ff0..124f00c4e54 100644 --- a/docs/products/compute/compute-instances/guides/configuration-profiles/index.md +++ b/docs/products/compute/compute-instances/guides/configuration-profiles/index.md @@ -14,9 +14,9 @@ A **configuration profile** functions as a boot loader for a Compute Instance. I ## View Configuration Profiles -The configuration profiles for a Compute Instance can be viewed and managed from the [Cloud Manager](https://cloud.linode.com). +The configuration profiles for a Compute Instance can be viewed and managed from [Cloud Manager](https://cloud.linode.com). -1. Log in to the [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. +1. Log in to [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. 1. Navigate to the **Configurations** tab to view the configuration profiles on a Compute Instance. @@ -81,9 +81,9 @@ When adding or editing a configuration profile on a Compute Instance, the follow ## Create a Configuration Profile -Making a new configuration profile allows you to create a new and separate boot configuration for your system. You can specify boot settings and disks to mount. Here's how to create a new configuration profile: +Making a new configuration profile lets you create a new and separate boot configuration for your system. You can specify boot settings and disks to mount. Here's how to create a new configuration profile: -1. Within the [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). +1. Within [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). 1. Select the **Add a Configuration** link. The **Add Configuration** form appears: @@ -99,7 +99,7 @@ Making a new configuration profile allows you to create a new and separate boot You can edit existing configuration profiles to change boot settings, set other disks to mount, and more. Here's how to edit a configuration profile: -1. Within the [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). +1. Within [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). 1. Within the **Configurations** table, locate the configuration profile you wish to modify and click the corresponding **Edit** button, which may also appear within the **ellipsis** menu. This displays the **Edit Configuration** form. @@ -111,9 +111,9 @@ The changes to the configuration profile have been saved. You may need to reboot ## Boot from a Configuration Profile -You can create and store many different configuration profiles in the Cloud Manager, but you can only boot your Compute Instance from one configuration profile at a time. Here's how to select a configuration profile and boot your instance from it: +You can create and store many different configuration profiles in Cloud Manager, but you can only boot your Compute Instance from one configuration profile at a time. Here's how to select a configuration profile and boot your instance from it: -1. Within the [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). +1. Within [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). 1. Within the **Configurations** table, locate the configuration profile you wish to modify and click the corresponding **Boot** button, which may also appear within the **ellipsis** menu. @@ -127,7 +127,7 @@ You have successfully selected and booted your Compute Instance from a configura When a Compute Instance is powered on or rebooted, it uses the settings stored within a configuration profile. You can determine which configuration profile was used by looking at the event history. Events are visible within the **Activity Feed** tab for a particular Compute Instance or within the main [Events](https://cloud.linode.com/events) page for the account. -1. Log in to the [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. +1. Log in to [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. 1. Navigate to the **Activity Feed** tab to view all events for the instance. @@ -143,9 +143,9 @@ A configuration profile, along with any attached disks, can be duplicated to any ## Delete a Configuration Profile -You can remove a configuration profile from the Cloud Manager at any time. Here's how: +You can remove a configuration profile from Cloud Manager at any time. Here's how: -1. Within the [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). +1. Within [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](#view-configuration-profiles). 1. Within the **Configurations** table, locate the configuration profile you wish to modify and click the corresponding **Delete** button, which may also appear within the **ellipsis** menu. diff --git a/docs/products/compute/compute-instances/guides/configure-rdns/index.md b/docs/products/compute/compute-instances/guides/configure-rdns/index.md index 48ba0dc2058..606d1e38bce 100644 --- a/docs/products/compute/compute-instances/guides/configure-rdns/index.md +++ b/docs/products/compute/compute-instances/guides/configure-rdns/index.md @@ -24,7 +24,7 @@ First, decide the FQDN (full qualified domain name) you wish to use as your rDNS Before setting the rDNS value for your Compute Instance's IP address, you must first add an *A Record* on your domain's DNS provider that maps your full domain (including subdomain) to the IP. To do this, log in to whichever service you use to manage your domain's DNS records. This may be the Linode [DNS Manager](/docs/products/networking/dns-manager/), your domain's registrar, or a third-party DNS service. The instructions below assume you are using Linode's DNS Manager, though most DNS services work in a similar fashion. -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the main navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the main navigation menu. 1. Within the list of domains that appears, click the **Edit** link corresponding with the domain you wish to use for rDNS. If your domain is not listed, you may be using a different DNS service. @@ -37,7 +37,7 @@ See our [Introduction to DNS Records](/docs/guides/dns-overview/) and [Common DN ## Setting Reverse DNS -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and click on the **Linodes** link in the sidebar to access a list of all your Compute Instances. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and click on the **Linodes** link in the sidebar to access a list of all your Compute Instances. 1. Select the Compute Instance whose reverse DNS you would like to set up and navigate to the **Network** tab. diff --git a/docs/products/compute/compute-instances/guides/copy-a-disk-image-over-ssh/index.md b/docs/products/compute/compute-instances/guides/copy-a-disk-image-over-ssh/index.md index 0de520d59ee..21b83f5c5f5 100644 --- a/docs/products/compute/compute-instances/guides/copy-a-disk-image-over-ssh/index.md +++ b/docs/products/compute/compute-instances/guides/copy-a-disk-image-over-ssh/index.md @@ -108,7 +108,7 @@ In some cases, it is necessary to upload your disk image to a new server. For ex 1. Once you've created a Compute Instance with enough disk space available to accommodate your disk image, prepare the new instance to receive this image. This is completed by first deleting the primary disk created by default, and keeping the swap disk. A swap disk typically starts at 256 MB or 512 MB in size, but can be larger or smaller depending upon your needs. -1. Access your Compute Instance through the Cloud Manager. Click the **Storage** tab to navigate to the *Disks* section. +1. Access your Compute Instance through Cloud Manager. Click the **Storage** tab to navigate to the *Disks* section. 1. On the following page in the **Disks** menu, select the ellipsis next to any primary disks you are replacing and select **Delete**. diff --git a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md index 0063189cfb7..b98a222ef92 100644 --- a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md +++ b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md @@ -22,7 +22,7 @@ You need to prepare the *receiving* Linode before initiating the transfer. First ### Creating a New Receiving Linode -1. Log in to the [Cloud Manager](https://cloud.linode.com) with the username and password you created when signing up. +1. Log in to [Cloud Manager](https://cloud.linode.com) with the username and password you created when signing up. 1. Click **Create** at the top of the page and select **Linode**. @@ -34,7 +34,7 @@ You need to prepare the *receiving* Linode before initiating the transfer. First 1. Select a Linode plan. -1. Give the Linode a label. This is a name to help you easily identify it within the Cloud Manager's Dashboard. If desired, assign a tag to the Linode in the **Add Tags** field. +1. Give the Linode a label. This is a name to help you easily identify it within Cloud Manager's Dashboard. If desired, assign a tag to the Linode in the **Add Tags** field. 1. Skip the **Root Password** and **SSH Keys** fields, as they are disabled when creating an empty Linode. diff --git a/docs/products/compute/compute-instances/guides/create/index.md b/docs/products/compute/compute-instances/guides/create/index.md index 09b80a18904..767f58cc370 100644 --- a/docs/products/compute/compute-instances/guides/create/index.md +++ b/docs/products/compute/compute-instances/guides/create/index.md @@ -8,9 +8,9 @@ keywords: ["getting started", "deploy", "linode", "linux"] aliases: ['/guides/creating-a-compute-instance/','/products/compute/dedicated-cpu/guides/deploy/'] --- -This guide walks you through creating a Compute Instance (also frequently called a *Linode*) through the Cloud Manager. Whether this is your first time using Linode or if you're a long time user, you should carefully consider each step in the process to make sure you're getting the most of your Linode services. +This guide walks you through creating a Compute Instance (also frequently called a *Linode*) through Cloud Manager. Whether this is your first time using Linode or if you're a long time user, you should carefully consider each step in the process to make sure you're getting the most of your Linode services. -- [Open the Create Form in the Cloud Manager](#open-the-create-form-in-the-cloud-manager) +- [Open the Create Form in Cloud Manager](#open-the-create-form-in-cloud-manager) - [Choose a Distribution, App, or Image](#choose-a-distribution-app-or-image) - [Select a Region](#select-a-region) - [Choose an Instance Type and Plan](#choose-an-instance-type-and-plan) @@ -25,11 +25,11 @@ This guide walks you through creating a Compute Instance (also frequently called - [Deploy the Instance](#deploy-the-instance) - [Getting Started After Deployment](#getting-started-after-deployment) -## Open the Create Form in the Cloud Manager +## Open the Create Form in Cloud Manager -Log in to the [Cloud Manager](https://cloud.linode.com/), click the **Create** dropdown menu on the top bar, and select *Linode*. This opens the **Create Linode** form. +Log in to [Cloud Manager](https://cloud.linode.com/), click the **Create** dropdown menu on the top bar, and select *Linode*. This opens the **Create Linode** form. -![Open Create form in the Cloud Manager](create-instance-create.jpg) +![Open Create form in Cloud Manager](create-instance-create.jpg) ## Choose a Distribution, App, or Image @@ -37,7 +37,7 @@ Log in to the [Cloud Manager](https://cloud.linode.com/), click the **Create** d One of the first steps to deploy a Compute Instance is to decide *what* you actually wish to deploy. You're able to select a Linux distribution for a barebones install, a Marketplace App with your desired software, and a few other options. -- **Distributions:** Select from any [supported Linux distribution](https://www.linode.com/distributions/). This option allows you to start with a stable Linux operating system and build your own software stack from scratch. Popular distributions include the latest LTS releases of Ubuntu, Debian, CentOS Stream, RHEL-derivitates (such AlmaLinux and Rocky Linux), and more. Each distribution comes with its own set of preinstalled software and commands. See [Choosing a Linux Distribution](/docs/products/compute/compute-instances/guides/distributions/) for a full list of distributions. +- **Distributions:** Select from any [supported Linux distribution](https://www.linode.com/distributions/). This option lets you start with a stable Linux operating system and build your own software stack from scratch. Popular distributions include the latest LTS releases of Ubuntu, Debian, CentOS Stream, RHEL-derivitates (such AlmaLinux and Rocky Linux), and more. Each distribution comes with its own set of preinstalled software and commands. See [Choosing a Linux Distribution](/docs/products/compute/compute-instances/guides/distributions/) for a full list of distributions. - **Marketplace**: Select from the many [Apps](https://www.linode.com/marketplace/apps/) currently featured in the [Linode Marketplace](https://www.linode.com/marketplace/). This installs and configures your desired software, allowing you to start using your applications right away. Popular apps include [Wordpress](https://www.linode.com/marketplace/apps/linode/wordpress/), [WooCommerce](https://www.linode.com/marketplace/apps/linode/woocommerce/), [LEMP](https://www.linode.com/marketplace/apps/linode/lemp/), [cPanel](https://www.linode.com/marketplace/apps/cpanel/cpanel/), [Plesk](https://www.linode.com/marketplace/apps/plesk/plesk/), and [Nextcloud](https://www.linode.com/marketplace/apps/linode/nextcloud/). See [How to Use Linode's Marketplace Apps](/docs/products/tools/marketplace/get-started/). @@ -93,7 +93,7 @@ You can resize to a different plan size or instance type at any time. This means {{% content "password-requirements-shortguide" %}} -- **SSH Keys:** Add any SSH Keys to the root user account on the server. This enables you to log in through SSH without needing a password. SSH keys are created as a pair: a *private key* stored on your local computer and a *public key* that you can upload to remote systems and services. Since you only share your public key and your private key is kept safe and secure, this is a much more secure method for authentication than passwords. Learn more about uploading SSH keys through the Cloud Manager on the [Manage SSH Keys](/docs/products/platform/accounts/guides/manage-ssh-keys/) guide. +- **SSH Keys:** Add any SSH Keys to the root user account on the server. This enables you to log in through SSH without needing a password. SSH keys are created as a pair: a *private key* stored on your local computer and a *public key* that you can upload to remote systems and services. Since you only share your public key and your private key is kept safe and secure, this is a much more secure method for authentication than passwords. Learn more about uploading SSH keys through Cloud Manager on the [Manage SSH Keys](/docs/products/platform/accounts/guides/manage-ssh-keys/) guide. ## Assign to a VPC (Optional) {#assign-to-a-vpc} @@ -103,7 +103,7 @@ Consider using a [VPC](/docs/products/networking/vpc/) (Virtual Private Network) - **Select VPC:** To assign this instance to a VPC, select the VPC from the **Assign VPC** dropdown menu. If you do not yet have a VPC in the selected data center, click the **Create a VPC** button and follow the instructions on the [Create a VPC](/docs/products/networking/vpc/guides/create/) guide. -- **Select Subnet:** An instance can be assigned to a single subnet, which allows you to further segment traffic and services within a VPC. Select the desired subnet within the **Subnet** dropdown menu. +- **Select Subnet:** An instance can be assigned to a single subnet, which lets you further segment traffic and services within a VPC. Select the desired subnet within the **Subnet** dropdown menu. - **Auto-Assign IPv4 address:** By default, an IPv4 address will be automatically generated for the instance on the subnet’s defined CIDR range. If you want to manually assign an IP address, uncheck the **Auto-assign a VPC IPv4 address for this Linode** option and enter your custom IPv4 address. This address must still be within the subnet’s IP range. @@ -117,7 +117,7 @@ For additional information and considerations, review the [Assign (and Remove) S ![Screenshot of the Assign Cloud Firewall section](create-instance-cloud-firewall.jpg) -To protect your new Compute Instance from unwanted traffic, consider using a [Cloud Firewall](/docs/products/networking/cloud-firewall/). This allows you to cascade firewall rules across multiple services and manage those rules within the Cloud Manager, Linode CLI, and Linode API. +To protect your new Compute Instance from unwanted traffic, consider using a [Cloud Firewall](/docs/products/networking/cloud-firewall/). This lets you cascade firewall rules across multiple services and manage those rules within Cloud Manager, Linode CLI, and Linode API. To assign your instance to a Cloud Firewall, select the firewall from the **Assign Firewall** dropdown menu. If you do not have a firewall or wish to create a new one, click the **Create Firewall** link and follow the instructions within the [Create a Cloud Firewall](/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/) guide. You can always skip this step and assign a firewall at a later time by following the instructions in the [Apply Firewall Rules to a Service](/docs/products/networking/cloud-firewall/guides/apply-to-service/) guide. @@ -147,7 +147,7 @@ The following features and services can be configured during the Compute Instanc - **Add the Backups service:** Safeguard your data with Linode’s Backups service, enabling automatic backups of the disks on your Compute Instances. Up to four backups are stored as part of this service, including automated daily, weekly, and biweekly backups in addition to a manual backup snapshot. See [Backups](/docs/products/storage/backups/) to learn more and view pricing. -- **Add a private IP:** A private IP gives you access to the data center's private network. This enables you to communicate with other Compute Instances with private IPs in the same region without using a public IPv4 address. Private IPs are needed to configure your instance as a NodeBalancer backend. The private IP feature requires a _Public Internet_ network interface. As such, Compute Instances configured with both VPCs _and_ a private IP address are configured with the _VPC_ network interface on `eth0` and the _Public Internet_ interface on `eth1`. +- **Add a private IP:** A private IP gives you access to the data center's private network. This enables you to communicate with other Compute Instances with private IPs in the same region without using a public IPv4 address. Private IPs are needed to configure your instance as a NodeBalancer back end. The private IP feature requires a _Public Internet_ network interface. As such, Compute Instances configured with both VPCs _and_ a private IP address are configured with the _VPC_ network interface on `eth0` and the _Public Internet_ interface on `eth1`. {{< note type="warning" title="Consider using a VPC instead of the private IP address feature" isCollapsible=true >}} Private IP addresses are accessible by any other instance in the same data center, provided that instance also has a private IP. To further isolate your instance, consider using a VPC instead. Review [these differences](/docs/products/networking/vpc/#difference-between-private-network-options-vpcs-vlans-and-private-ips) to learn more. diff --git a/docs/products/compute/compute-instances/guides/disks-and-storage/index.md b/docs/products/compute/compute-instances/guides/disks-and-storage/index.md index 9086828096d..f0ea4adca0a 100644 --- a/docs/products/compute/compute-instances/guides/disks-and-storage/index.md +++ b/docs/products/compute/compute-instances/guides/disks-and-storage/index.md @@ -15,19 +15,19 @@ Every Compute Instance is equipped with persistent storage, the amount of which ### Disks -The storage space on a Compute Instance can be allocated to individual *disks*. Disks are be used to store any data, including the operating system, applications, and files. Most instances are deployed with two disks. A large primary disk is used to store the Linux distribution, software, and data. There's also a much smaller swap disk, which is used in the event that your instance runs out of memory. +The storage space on a Compute Instance can be allocated to individual *disks*. Disks are be used to store any data, including the operating system, applications, and files. Most instances are deployed with two disks. A large primary disk is used to store the Linux distribution, software, and data. There's also a much smaller swap disk, which is used if your instance runs out of memory. While two disks may be the default, a Compute Instance can be configured to have many more disks. These additional disks can serve a variety of purposes, including dedicated file storage or switching between entirely different Linux distributions. When multiple disks are added, [configuration profiles](/docs/products/compute/compute-instances/guides/configuration-profiles/) are used to determine the disks that are accessible when the instance is powered on, as well as which of those disks serves as the primary root disk. ### Add Additional Storage -The local storage capacity of a Compute Instance can only be increased by upgrading to a larger plan. This allows you to increase the size of existing disks or add additional disks. [Block Storage](/docs/products/storage/block-storage/) Volumes can also be used to add additional storage, though these Volumes are separate from a Compute Instance's local disks and, for some use cases, may be less performant. +The local storage capacity of a Compute Instance can only be increased by upgrading to a larger plan. This lets you increase the size of existing disks or add additional disks. [Block Storage](/docs/products/storage/block-storage/) Volumes can also be used to add additional storage, though these Volumes are separate from a Compute Instance's local disks and, for some use cases, may be less performant. ## View Disks -A Compute Instance's total storage space and disks can be viewed and managed from the [Cloud Manager](https://cloud.linode.com). +A Compute Instance's total storage space and disks can be viewed and managed from [Cloud Manager](https://cloud.linode.com). -1. Log in to the [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. +1. Log in to [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. 1. Look within the **Summary** section of the instance's dashboard to view the total storage. @@ -67,7 +67,7 @@ If you wish to deploy an Image to a new disk, see the [Deploy an Image to a Disk **Empty disks:** An empty disk can store additional data, be used as a swap disk, or it can be used to manually [install a custom distribution](/docs/products/compute/compute-instances/guides/install-a-custom-distribution/). When creating an empty disk, select the desired *Filesystem*. In most cases, it's recommended to use the *ext4* filesystem. This ensures compatibility with our Backups service. If needed, *ext3* and *raw* disks are also available. If creating a swap disk, select the *swap* option. - **Images:** Selecting an Image allows you to deploy a [Distribution Image](https://www.linode.com/distributions/), a [Custom Image](/docs/products/tools/images/), or a Recovery Image to the new disk. When creating a disk based on an Image, select the *Image*, *Root Password*, and optionally add *SSH Keys*. + **Images:** Selecting an Image lets you deploy a [Distribution Image](https://www.linode.com/distributions/), a [Custom Image](/docs/products/tools/images/), or a Recovery Image to the new disk. When creating a disk based on an Image, select the *Image*, *Root Password*, and optionally add *SSH Keys*. 1. Once an option is chosen, complete the remaining fields in the form. Enter the *Label* and the *Size* for the new disk. The *maximum size* of the disk is pre-populated and based on the Compute Instance's remaining storage allocation, though a smaller size can be entered if desired. @@ -80,7 +80,7 @@ Once a disk has been created, you will need to modify the existing configuration The size of a Compute Instance's disk can be increased or decreased as needed. When resizing, it's important to keep the following restrictions in mind: - The **maximum size** of a disk is equal to the current size of the disk and the remaining unallocated storage space on the Compute Instance. The maximum size is displayed underneath the **Size** field when resizing the disk. -- The **minimum size** of a disk is equal to the current disk usage within the filesystem. This number is not displayed in the Cloud Manager. To determine how much space the files on the disk are using, run the command `df -h` within the Compute Instance's command line (through [SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) or [Lish](/docs/products/compute/compute-instances/guides/lish/)). +- The **minimum size** of a disk is equal to the current disk usage within the filesystem. This number is not displayed in Cloud Manager. To determine how much space the files on the disk are using, run the command `df -h` within the Compute Instance's command line (through [SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) or [Lish](/docs/products/compute/compute-instances/guides/lish/)). - **Raw disks** can only be resized to a larger disk. - Disks with **custom partitions** cannot be resized. diff --git a/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md b/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md index 7b25060c1ef..c6daa5ef1cd 100644 --- a/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md +++ b/docs/products/compute/compute-instances/guides/failover-bgp-frr/index.md @@ -17,7 +17,7 @@ This guide covers using the open source [FRRouting (FRR)](http://docs.frrouting. ## Before You Begin -Prior to following this guide, ensure the following has been done on each Compute Instance used within your IP failover strategy. +Before following this guide, ensure the following has been done on each Compute Instance used within your IP failover strategy. 1. Read through the [Configuring Failover on a Compute Instance](/docs/products/compute/compute-instances/guides/failover/) guide to learn more about how failover is implemented within Linode Compute. diff --git a/docs/products/compute/compute-instances/guides/failover-legacy-keepalived/index.md b/docs/products/compute/compute-instances/guides/failover-legacy-keepalived/index.md index f2adad6e622..d82dd9945c5 100644 --- a/docs/products/compute/compute-instances/guides/failover-legacy-keepalived/index.md +++ b/docs/products/compute/compute-instances/guides/failover-legacy-keepalived/index.md @@ -112,9 +112,9 @@ When configuring keepalived, there are quite a few options that can be modified - **vrrp_instance:** The VRRP instance definition block. Set this to whatever you'd like to call this block. To help with identification, this should be the same value across all Compute Instances that will share the specified IP address. - **state:** Set this to `MASTER` if the IP address is natively assigned to this Compute Instance. When configuring it as a secondary failover server, use `BACKUP`. -- **interface:** Set this to whichever Network Interface the IP address is using or should use. To find the interface, log in to the [Cloud Manager](https://cloud.linode.com/), click on the **Linodes** link on the left menu, select your Compute Instance, navigate to the **Configurations** tab and review the **Network Interfaces** column for your active configuration profile. For public IP addresses the interface is typically `eth0` and for vlan addresses the interface is likely `eth1`. +- **interface:** Set this to whichever Network Interface the IP address is using or should use. To find the interface, log in to [Cloud Manager](https://cloud.linode.com/), click on the **Linodes** link on the left menu, select your Compute Instance, navigate to the **Configurations** tab and review the **Network Interfaces** column for your active configuration profile. For public IP addresses the interface is typically `eth0` and for vlan addresses the interface is likely `eth1`. - ![The Configuration tab in the Cloud Manager](ip-failover-keepalived-ethernet-configuration.png) + ![The Configuration tab in Cloud Manager](ip-failover-keepalived-ethernet-configuration.png) - **priority:** When multiple secondary Compute Instances are configured for IP failover, this sets the order in which they will be used. - **auth_pass:** Set the password used by keepalived for failover synchronization. This should be used across all Compute Instances that will share the specified IP address. diff --git a/docs/products/compute/compute-instances/guides/failover/index.md b/docs/products/compute/compute-instances/guides/failover/index.md index 68175b54d05..a5e825fd593 100644 --- a/docs/products/compute/compute-instances/guides/failover/index.md +++ b/docs/products/compute/compute-instances/guides/failover/index.md @@ -80,7 +80,7 @@ To configure failover, complete each section that follows. ### 1. Create and Share the Shared IP Address -1. Log in to the [Cloud Manager](https://cloud.linode.com/). +1. Log in to [Cloud Manager](https://cloud.linode.com/). 1. Determine which two Compute Instances are to be used within your failover setup. They both must be located in the same data center. If you need to, create those Compute Instances now and allow them to fully boot up. diff --git a/docs/products/compute/compute-instances/guides/glish/index.md b/docs/products/compute/compute-instances/guides/glish/index.md index bc7270ba433..812bdc598eb 100644 --- a/docs/products/compute/compute-instances/guides/glish/index.md +++ b/docs/products/compute/compute-instances/guides/glish/index.md @@ -10,7 +10,7 @@ image: using-linode-glish-title.jpg aliases: ['/platform/manager/using-the-linode-graphical-shell-glish-classic-manager/','/networking/using-the-graphic-shell-glish/','/networking/using-the-linode-graphical-shell-glish/','/platform/manager/using-the-linode-graphical-shell-glish/','/platform/using-the-linode-graphical-shell-glish/','/networking/use-the-graphic-shell-glish/','/guides/using-the-linode-graphical-shell-glish/','/guides/glish/'] --- -Glish is the graphical version of [Lish](/docs/products/compute/compute-instances/guides/lish/) (the Linode Shell). It allows you to run a desktop environment on your Compute Instance and access it through the Cloud Manager. +Glish is the graphical version of [Lish](/docs/products/compute/compute-instances/guides/lish/) (the Linode Shell). It lets you run a desktop environment on your Compute Instance and access it through Cloud Manager. {{< note >}} Linode distribution images do not have any desktop environments pre-installed. While this guide provides instructions for installing Xfce on Debian, you can use any other desktop environment and distribution. Popular desktop environments on Linux include Gnome, KDE, MATE, and Xfce. @@ -52,13 +52,13 @@ The instructions below install Xfce4 and LightDM on Debian 11. You are not limit sudo apt install xfce4 xfce4-goodies dbus-x11 firefox-esr ``` -1. Install a display manager, which provides a graphical login screen. This allows you to log in as your desired user and with your preferred desktop environment. There are many display managers available, including [LightDM](https://wiki.debian.org/LightDM), [GDM](https://wiki.debian.org/GDM) (Gnome Desktop Manager), [SDDM](https://wiki.debian.org/SDDM), and [Ly](https://github.com/fairyglade/ly). This guide uses LightDM. +1. Install a display manager, which provides a graphical login screen. This lets you log in as your desired user and with your preferred desktop environment. There are many display managers available, including [LightDM](https://wiki.debian.org/LightDM), [GDM](https://wiki.debian.org/GDM) (Gnome Desktop Manager), [SDDM](https://wiki.debian.org/SDDM), and [Ly](https://github.com/fairyglade/ly). This guide uses LightDM. ```command sudo install lightdm ``` -1. Set your new display manager as the system default. The command below opens up a prompt that allows you to select your preference from all display manager's that are currently installed. +1. Set your new display manager as the system default. The command below opens up a prompt that lets you select your preference from all display manager's that are currently installed. ```command sudo dpkg-reconfigure lightdm @@ -66,7 +66,7 @@ The instructions below install Xfce4 and LightDM on Debian 11. You are not limit ## Access Glish and the Linux Desktop -1. Log in to the [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select your desired Compute Instance from the list. +1. Log in to [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select your desired Compute Instance from the list. 1. To open the console, click on the **Launch Console** button in the top right corner of the summary page. diff --git a/docs/products/compute/compute-instances/guides/ifupdown/index.md b/docs/products/compute/compute-instances/guides/ifupdown/index.md index c9d3909e79f..79d824be338 100644 --- a/docs/products/compute/compute-instances/guides/ifupdown/index.md +++ b/docs/products/compute/compute-instances/guides/ifupdown/index.md @@ -47,7 +47,7 @@ iface eth0 inet static ## Configuring IP Addresses Manually -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make a note of the following pieces of information or keep this page accessible so you can reference it later. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make a note of the following pieces of information or keep this page accessible so you can reference it later. - Public IPv4 address(es) and the associated IPv4 gateway - Private IPv4 address (if one has been added) diff --git a/docs/products/compute/compute-instances/guides/install-nvidia-cuda/index.md b/docs/products/compute/compute-instances/guides/install-nvidia-cuda/index.md index 444277134aa..e661a7e6e37 100644 --- a/docs/products/compute/compute-instances/guides/install-nvidia-cuda/index.md +++ b/docs/products/compute/compute-instances/guides/install-nvidia-cuda/index.md @@ -9,7 +9,7 @@ aliases: ['/products/compute/gpu/guides/install-nvidia-drivers-with-cuda/','/pro To take advantage of the powerful parallel processing capabilities offered by GPU instances equipped with NVIDIA Quadro RTX cards, you first need to install NVIDIA's CUDA Toolkit. This guide walks you through deploying a GPU instance and installing the CUDA Toolkit. -1. Deploy a GPU Compute Instance using the [Cloud Manager](https://cloud.linode.com/), the Linode CLI, or the Linode API. It's recommended to follow the instructions within the following guides: +1. Deploy a GPU Compute Instance using [Cloud Manager](https://cloud.linode.com/), the Linode CLI, or the Linode API. It's recommended to follow the instructions within the following guides: - [Getting Started with Linode](/docs/products/platform/get-started/) - [Securing Your Server](/docs/products/compute/compute-instances/guides/set-up-and-secure/) diff --git a/docs/products/compute/compute-instances/guides/ip-sharing-atlanta/index.md b/docs/products/compute/compute-instances/guides/ip-sharing-atlanta/index.md index 4138af2193b..65fc554a82f 100644 --- a/docs/products/compute/compute-instances/guides/ip-sharing-atlanta/index.md +++ b/docs/products/compute/compute-instances/guides/ip-sharing-atlanta/index.md @@ -20,7 +20,7 @@ This guide discusses a temporary workaround specific to the Atlanta data center. ## Before You Begin -1. Prior to beginning the process outlined in this guide, make sure that you have received an IPv4 address(es) from Linode Support to use as your Elastic IP(s). To request an additional IPv4 address, [open a new support ticket from the Cloud Manager](/docs/products/platform/get-started/guides/support/#contact-customer-support). +1. Before beginning the process outlined in this guide, make sure that you have received an IPv4 address(es) from Linode Support to use as your Elastic IP(s). To request an additional IPv4 address, [open a new support ticket from Cloud Manager](/docs/products/platform/get-started/guides/support/#contact-customer-support). 1. Ensure you have set the [hostname](/docs/products/compute/compute-instances/guides/set-up-and-secure/#configure-a-custom-hostname) and have updated the [hosts file](/docs/products/compute/compute-instances/guides/set-up-and-secure/#update-your-systems-hosts-file) on your Compute Instances. diff --git a/docs/products/compute/compute-instances/guides/ipv6/index.md b/docs/products/compute/compute-instances/guides/ipv6/index.md index 23c8068a42b..44dbe00bc7d 100644 --- a/docs/products/compute/compute-instances/guides/ipv6/index.md +++ b/docs/products/compute/compute-instances/guides/ipv6/index.md @@ -1,6 +1,6 @@ --- title: "An Overview of IPv6 on Linode" -description: "This guide is a brief overview of IPv6 support on Linode, including how to find your IPv6 address, requesting additional IPs, and managing IPs via the Cloud Manager." +description: "This guide is a brief overview of IPv6 support on Linode, including how to find your IPv6 address, requesting additional IPs, and managing IPs via Cloud Manager." published: 2011-05-03 modified: 2024-07-08 keywords: ["ipv6 networking", "IP configuration"] @@ -29,9 +29,9 @@ ip6tables -A FORWARD -p icmpv6 -j ACCEPT ## How to Find Your IPv6 Address -You can find your Compute Instance's IPv6 address using the Cloud Manager or the `ip` tool with the Linux Terminal. +You can find your Compute Instance's IPv6 address using Cloud Manager or the `ip` tool with the Linux Terminal. -### Using the Cloud Manager +### Using Cloud Manager See the [Viewing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#viewing-ip-addresses) section of the Managing IP Addresses guide. diff --git a/docs/products/compute/compute-instances/guides/lassie-shutdown-watchdog/index.md b/docs/products/compute/compute-instances/guides/lassie-shutdown-watchdog/index.md index 83aed4a19f3..79f260a0251 100644 --- a/docs/products/compute/compute-instances/guides/lassie-shutdown-watchdog/index.md +++ b/docs/products/compute/compute-instances/guides/lassie-shutdown-watchdog/index.md @@ -12,7 +12,7 @@ Linode Compute Instances have a featured called *Lassie* (Linode Autonomous Syst ## Shutdown Recovery Behavior -The Shutdown Watchdog feature detects when a Compute Instance is powered off and checks if that directive came from the Linode platform (such as the Cloud Manager or Linode API). If the power off command *did not* originate from the Linode platform, the shutdown is considered unexpected and the Compute Instance is automatically powered back on. +The Shutdown Watchdog feature detects when a Compute Instance is powered off and checks if that directive came from the Linode platform (such as Cloud Manager or Linode API). If the power off command *did not* originate from the Linode platform, the shutdown is considered unexpected and the Compute Instance is automatically powered back on. {{< note >}} Shutdown Watchdog can power back on a Compute Instance up to 5 times within a 15 minute period. If there is a recurring issue that is causing 6 or more shutdowns within this time period, the instance remains powered off until it is manually powered back on. This is to prevent endless reboot loops if there is an issue with the internal software of a Compute Instance. @@ -22,7 +22,7 @@ Shutdown Watchdog can power back on a Compute Instance up to 5 times within a 15 By default, Shutdown Watchdog is enabled on all new Compute Instances. If you wish to disable or re-enable this feature, follow the instructions below: -1. Log in to the [Cloud Manager](https://cloud.linode.com) and navigate to the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and navigate to the **Linodes** link in the sidebar. 1. Select the Linode Compute Instance that you wish to modify. 1. Navigate to the **Settings** tab. 1. Scroll down to the section labeled **Shutdown Watchdog**. @@ -33,7 +33,7 @@ By default, Shutdown Watchdog is enabled on all new Compute Instances. If you wi ## Reasons for an Unexpected Shutdown -An *unexpected shutdown* is when a Compute Instance powers off without receiving a power off command from the Linode platform (such as one issued by a user in the Cloud Manager or API). In general, this is caused within a Compute Instance's internal system or software configuration. The following list includes potential reasons for these unexpected shutdowns. +An *unexpected shutdown* is when a Compute Instance powers off without receiving a power off command from the Linode platform (such as one issued by a user in Cloud Manager or API). In general, this is caused within a Compute Instance's internal system or software configuration. The following list includes potential reasons for these unexpected shutdowns. - **A user issues the [**shutdown command**](https://man7.org/linux/man-pages/man8/shutdown.8.html)** in the shell environment of a Compute Instance. In Linux, a system can be powered off by entering the `shutdown` command (or other similar commands) in the system's terminal. Since Linode has no knowledge of internal commands issued on a Compute Instance, it is considered an unexpected shutdown. diff --git a/docs/products/compute/compute-instances/guides/lish/index.md b/docs/products/compute/compute-instances/guides/lish/index.md index 60386927006..188f458cfa5 100644 --- a/docs/products/compute/compute-instances/guides/lish/index.md +++ b/docs/products/compute/compute-instances/guides/lish/index.md @@ -16,15 +16,15 @@ The **Lish Console**, also called the *Linode Shell*, provides direct console ac There are two ways to access Lish. You can use a terminal application to connect to a *Lish SSH gateway*, or you can log in to the [Linode Cloud Manager](https://cloud.linode.com) and use the Lish console in your web browser. This section explains both methods. -### Through the Cloud Manager (Weblish) +### Through Cloud Manager (Weblish) -You can connect to Lish using a web browser. This is useful when you don't have access to a terminal application, or if you just need quick and easy console access from the Cloud Manager. +You can connect to Lish using a web browser. This is useful when you don't have access to a terminal application, or if you just need quick and easy console access from Cloud Manager. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click on the **Linodes** link in the sidebar and select the desired Compute Instance. -1. Click on the **Launch LISH Console** link in the top right-hand corner of the Cloud Manager. +1. Click on the **Launch LISH Console** link in the top right-hand corner of Cloud Manager. ![Launch the Lish Console](launch-console-button.png) @@ -57,7 +57,7 @@ If you have [Third Party Authentication](/docs/products/platform/accounts/guides ``` {{< note >}} - Users who have been granted "Access" rights on a particular Compute Instance will have access to its Lish console via the gateway. Linodes that a user can't access in the Cloud Manager won’t show up in the Lish list. For more information about creating user accounts and configuring permissions, see [Accounts and Passwords](/docs/products/platform/accounts/guides/manage-users/). + Users who have been granted "Access" rights on a particular Compute Instance will have access to its Lish console via the gateway. Linodes that a user can't access in Cloud Manager won’t show up in the Lish list. For more information about creating user accounts and configuring permissions, see [Accounts and Passwords](/docs/products/platform/accounts/guides/manage-users/). {{< /note >}} 1. Verify that the Lish SSH gateway's fingerprint is valid by verifying the Terminal's output against the list of our [Lish Gateway Fingerprints](#lish-gateways). Once verified, enter *yes* to proceed. @@ -78,7 +78,7 @@ If you have [Third Party Authentication](/docs/products/platform/accounts/guides Once you have removed the cached IP address, you can again attempt to SSH into the Lish gateway. {{}} -1. Enter the password you use to log in to the Cloud Manager. You are now at the Lish shell. A list of your Compute Instances appears, as shown below: +1. Enter the password you use to log in to Cloud Manager. You are now at the Lish shell. A list of your Compute Instances appears, as shown below: ```output Linodes located in this data center: @@ -90,7 +90,7 @@ If you have [Third Party Authentication](/docs/products/platform/accounts/guides ``` {{< note >}} - You can add a public SSH key for Lish in the Cloud Manager to automatically connect to Lish without a password. See [this section](#add-your-public-key) for more information. + You can add a public SSH key for Lish in Cloud Manager to automatically connect to Lish without a password. See [this section](#add-your-public-key) for more information. {{< /note >}} 1. At the Lish command prompt, type a Compute Instance's name from the list. For example, typing `linode241706` will connect you to the screen console session for that Instance. @@ -103,7 +103,7 @@ After you log in, you'll have console access to your Compute Instance. You'll be If you don't want to enter your password every time you connect to Lish, or if you have [Third Party Authentication](/docs/products/platform/accounts/guides/third-party-authentication/) enabled on your account, you can add your public SSH key to the Linode Cloud Manager. If you haven't yet created SSH keys, please see our [Public Key Authentication with SSH](/docs/guides/use-public-key-authentication-with-ssh/) guide for more information. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click on the profile icon in the top right hand corner of the Manager and select **LISH Console Settings**. @@ -111,7 +111,7 @@ If you don't want to enter your password every time you connect to Lish, or if y ![Add your public ssh key](lish-add-public-key.png) -1. Click the **Save** button. Your Lish key will be saved in the Cloud Manager. +1. Click the **Save** button. Your Lish key will be saved in Cloud Manager. Now you can log in to any of the Lish gateway boxes without having to type your password. @@ -119,7 +119,7 @@ If you wish to disable Lish access for users without keys, use the **Authenticat ## Lish Commands -The Lish shell provides access to many functions which are otherwise only accessible via the Cloud Manager web-based administration tool. Enter the `help` command to see a full list of available commands. The output provides an introduction to Lish functionality: +The Lish shell provides access to many functions which are otherwise only accessible via Cloud Manager. Enter the `help` command to see a full list of available commands. The output provides an introduction to Lish functionality: ```output kill - kill stuck screen sessions diff --git a/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md b/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md index bbf599dbd59..1a5dae0ddf9 100644 --- a/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md +++ b/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md @@ -1,6 +1,6 @@ --- title: "Managing IP Addresses on a Compute Instance" -description: "Instructions on viewing, adding, deleting, transferring IP addresses for Linode Compute Instances using the Cloud Manager" +description: "Instructions on viewing, adding, deleting, transferring IP addresses for Linode Compute Instances using Cloud Manager" og_description: "Learn how to manage IP addresses on a Linode Compute Instance" published: 2016-08-23 modified: 2024-07-26 @@ -9,11 +9,11 @@ tags: ["linode platform","cloud manager","networking"] aliases: ['/platform/manager/remote-access-classic-manager/','/platform/manager/remote-access/','/remote-access/','/networking/remote-access/', '/guides/remote-access/','/guides/managing-ip-addresses/','/products/tools/cloud-manager/guides/cloud-delete-ip/','/guides/find-your-linodes-ip-address/'] --- -Each Linode Compute Instance is equipped with several IP addresses, which may enable it to be accessible over the public Internet and other Linode services or accessible just to other Compute Instances within a VPC. This guide covers how to manage these IP addresses (including viewing, adding, removing, transferring, or sharing them) through the Cloud Manager. +Each Linode Compute Instance is equipped with several IP addresses, which may enable it to be accessible over the public Internet and other Linode services or accessible just to other Compute Instances within a VPC. This guide covers how to manage these IP addresses (including viewing, adding, removing, transferring, or sharing them) through Cloud Manager. ## Viewing IP Addresses -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. 1. Click on your Linode Compute Instance from the list to view more details. @@ -63,7 +63,7 @@ In most cases, a VPC is the better option for true network isolation than either Follow the instructions below to add an public IPv4, private IPv4, or IPv6 range to your Compute Instance. By default, up to one /64 and /56 range can be added per customer per data center. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. 1. Click on your Linode Compute Instance from the list and navigate to the **Network** tab. 1. Click the **Add an IP Address** button under the *IP Address* section. This displays the *Add an IP Address* panel. @@ -93,7 +93,7 @@ To change the rDNS value on an IP address, follow the instructions within the [C ## Deleting an IP Address -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. 1. Click on your Linode Compute Instance from the list and navigate to the **Network** tab. 1. Select the **Delete** menu option for the IP address you'd like to remove @@ -107,13 +107,13 @@ To change the rDNS value on an IP address, follow the instructions within the [C ## Transferring IP Addresses -If you have two Compute Instances in the same data center, you can use the *IP transfer* feature to move or swap their IP addresses. This feature is especially useful when replacing one Compute Instance with another. It allows you to quickly move the IP addresses to the new Instance without needing to manually adjust DNS records with the new addresses. +If you have two Compute Instances in the same data center, you can use the *IP transfer* feature to move or swap their IP addresses. This feature is especially useful when replacing one Compute Instance with another. It lets you quickly move the IP addresses to the new Instance without needing to manually adjust DNS records with the new addresses. {{< note >}} This process only transfers IPv4 addresses and IPv6 ranges, not IPv6 SLAAC addresses. See [Transferring an IPv6 SLAAC Address](#transferring-an-ipv6-slaac-address) below for a workaround. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. 1. Click on your Linode Compute Instance from the list and navigate to the **Network** tab. @@ -126,7 +126,7 @@ This process only transfers IPv4 addresses and IPv6 ranges, not IPv6 SLAAC addre - **Move To:** moves the IP address to another Compute Instance. When choosing this option, select the destination Compute Instance in the next dropdown menu that appears. If you are moving a public IPv4 address, there needs to be at least one remaining public IPv4 address on the source Compute Instance. - **Swap With:** swaps the IP addresses of two Compute Instances. When choosing this option, select the destination Compute Instance in the next dropdown menu that appears. Then select the IP address (belonging to the destination Compute Instance) you would like to swap with the originally selected IP address. - ![The IP Transfer menu in the Cloud Manager](remote_access_ip_transfer.png) + ![The IP Transfer menu in Cloud Manager](remote_access_ip_transfer.png) {{< note >}} The *IP Transfer* form only displays Compute Instances hosted in the same data center as the current Instance. @@ -155,7 +155,7 @@ IPv6 SLAAC addresses are not able to be transferred between Compute Instances. I ## Configuring IP Sharing -*IP Sharing* is a feature that enables two Compute Instances to be assigned the same IP address for the purpose of configuring failover. Within a typical failover setup, traffic on the shared IP address is routed to the primary instance. In the event that instance fails or goes down, traffic is automatically re-routed to the secondary instance. While IP Sharing can be configured in the Cloud Manager, failover must be manually configured within the internal system of both Compute Instances. See [Configuring IP Failover](/docs/products/compute/compute-instances/guides/failover/) to learn more about configuring failover. +*IP Sharing* is a feature that enables two Compute Instances to be assigned the same IP address for the purpose of configuring failover. Within a typical failover setup, traffic on the shared IP address is routed to the primary instance. In the event that instance fails or goes down, traffic is automatically re-routed to the secondary instance. While IP Sharing can be configured in Cloud Manager, failover must be manually configured within the internal system of both Compute Instances. See [Configuring IP Failover](/docs/products/compute/compute-instances/guides/failover/) to learn more about configuring failover. {{< note >}} Not all data centers currently support IP Sharing. Additionally, some data centers only support IPv4 sharing, while others also support IPv6 routed ranges (/64 and /56). To determine if IP Sharing is supported in a particular data center, see [Configuring IP Failover > IP Sharing Availability](/docs/products/compute/compute-instances/guides/failover/#ip-sharing-availability). @@ -165,9 +165,9 @@ Not all data centers currently support IP Sharing. Additionally, some data cente When IP Sharing is enabled for an IP address, all connectivity to that IP address is immediately lost *until* it is configured on [Lelastic](/docs/products/compute/compute-instances/guides/failover/#install-and-configure-lelastic), [FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/), or another routing software. This is not an issue when adding a new IP address, but should be considered if you are enabling IP Sharing on an existing IP address that is actively being used. {{< /note >}} -To learn how to enable IP Sharing within the Cloud Manager, review the following steps. +To learn how to enable IP Sharing within Cloud Manager, review the following steps. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. 1. Determine which two Compute Instances are to be used within your failover setup. They both must be located in the same data center. Make sure the IP address you wish to share has been added to one of those instances. If not, add it now. See [Adding an IP Address](#adding-an-ip-address). @@ -186,19 +186,19 @@ To learn how to enable IP Sharing within the Cloud Manager, review the following 1. Click **Save** to enable IP Sharing. -1. After enabling IP Sharing in the Cloud Manager, the next step is to configure a failover service (such as FRR, lelastic, or Keepalived) within the internal system on each Compute Instance. For more information, see our guide on [Configuring IP Failover](/docs/products/compute/compute-instances/guides/failover/). +1. After enabling IP Sharing in Cloud Manager, the next step is to configure a failover service (such as FRR, lelastic, or Keepalived) within the internal system on each Compute Instance. For more information, see our guide on [Configuring IP Failover](/docs/products/compute/compute-instances/guides/failover/). ## Viewing the DNS Resolvers' IP Addresses Each data center has its own set of DNS resolvers, which are accessed through both IPv4 or IPv6 addresses. To view the DNS resolvers, follow the instructions below. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the sidebar. 1. Click on your Linode Compute Instance from the list to view more details. 1. Navigate to the **Network** tab and review the **DNS Resolvers** list, which should appear to the right of (or below) the network transfer graph. - ![Screenshot of the DNS resolvers in the Cloud Manager](dns-resolvers.png) + ![Screenshot of the DNS resolvers in Cloud Manager](dns-resolvers.png) ## Confirming IP Addresses are Correctly Configured diff --git a/docs/products/compute/compute-instances/guides/manage-the-kernel/index.md b/docs/products/compute/compute-instances/guides/manage-the-kernel/index.md index 93081c36d7b..657c1d6e307 100644 --- a/docs/products/compute/compute-instances/guides/manage-the-kernel/index.md +++ b/docs/products/compute/compute-instances/guides/manage-the-kernel/index.md @@ -37,15 +37,15 @@ There are may ways you can determine which kernel version is installed on your L The kernel version should be a string that's similar to `5.4.0-80-generic`. In this example, the kernel ends with `generic`, which is common in Ubuntu systems to designate that this is an upstream kernel. If the kernel ends with something similar to `linode123`, a Linode kernel is being used and the string matches the precise Linode kernel release. -## View and Modify the Kernel in the Cloud Manager +## View and Modify the Kernel in Cloud Manager -You can use the Cloud Manager to view the type of kernel you are using. If you are using a Linode kernel (not an upstream kernel), you can also view the kernel version. +You can use Cloud Manager to view the type of kernel you are using. If you are using a Linode kernel (not an upstream kernel), you can also view the kernel version. {{< note >}} These instructions may not accurately reflect the actual kernel version installed. This is especially true if the Compute Instance hasn't been rebooted in a while or wasn't rebooted after a change to the instance's Configuration. To determine the actual kernel version installed on your system, see [Determining Which Kernel Is Installed](#determining-which-kernel-is-installed). {{< /note >}} -1. Navigate to your Compute Instance in the [Cloud Manager](https://cloud.linode.com) and click the **Configuration** tab. +1. Navigate to your Compute Instance in [Cloud Manager](https://cloud.linode.com) and click the **Configuration** tab. 1. Find your current *Configuration* and click the corresponding **Edit** link. This may be located within the **More Options Ellipses** dropdown menu. @@ -53,11 +53,11 @@ These instructions may not accurately reflect the actual kernel version installe 1. Review the **Kernel** dropdown menu selection. - - **Latest 64 bit** and **Latest 32 bit**: Uses one of the latest 64-bit or 32-bit Linode kernels at the time the Compute Instance boots/reboots, depending on which option you selected. Since new kernel releases are rolled out over a short time period, the actual kernel used by your system may be one or two releases behind. This setting was the default for most distributions prior to August 2018. + - **Latest 64 bit** and **Latest 32 bit**: Uses one of the latest 64-bit or 32-bit Linode kernels at the time the Compute Instance boots/reboots, depending on which option you selected. Since new kernel releases are rolled out over a short time period, the actual kernel used by your system may be one or two releases behind. This setting was the default for most distributions before August 2018. - **Direct Disk**: Instead of a Linux Kernel, this uses the MBR (Master Boot Record) of the primary disk*. - **GRUB 2**: Uses the upstream distribution-supplied kernel that's installed on the primary disk. If a custom kernel has been installed instead, that is used instead. **This is the most common option and has been the default for most new Compute Instances created after August 2018.** - **GRUB (Legacy)**: Uses the upstream distribution-supplied kernel that's installed on the primary disk*. This should only be used on older Linux distributions that have Grub (not Grub 2) installed, like CentOS 6. - - **Specific Linode Kernel**: Allows you to specify the exact Linode kernel to use. Since this kernel is maintained regardless of reboots or system updates, it may be preferred in some use cases. + - **Specific Linode Kernel**: Lets you specify the exact Linode kernel to use. Since this kernel is maintained regardless of reboots or system updates, it may be preferred in some use cases. *\*Primary disk: the disk assigned as the "Root Device" within the instance's Configuration Profile.* @@ -74,7 +74,7 @@ Provided a newer kernel is available, you should be able to either manually (or Follow these steps if the Compute Instance is using a Linode kernel: - **Latest 64-bit or 32-bit kernel**: Rebooting the Compute Instance automatically updates the kernel used within your system to one of the latest Linode kernel release. Since new kernel releases are rolled out over a short time period, the actual kernel used by your system may be one or two releases behind. -- **Specific kernel version** (ex: `5.12.2-x86_64-linode144`): To update your kernel, follow the instructions within the [Viewing and Modifying the Kernel in the Cloud Manager](#viewing-and-modifying-the-kernel-in-the-cloud-manager) section. When selecting the kernel in the instance's Configuration Profile, chose your desired kernel version (or select `Latest 64 bit`), save the changes, and reboot your Compute Instance. +- **Specific kernel version** (ex: `5.12.2-x86_64-linode144`): To update your kernel, follow the instructions within the [Viewing and Modifying the Kernel in Cloud Manager](#viewing-and-modifying-the-kernel-in-cloud-manager) section. When selecting the kernel in the instance's Configuration Profile, chose your desired kernel version (or select `Latest 64 bit`), save the changes, and reboot your Compute Instance. ### Update the Upstream Kernel @@ -144,7 +144,7 @@ Once completed, the disks should be read by GRUB2 correctly. ### SELinux -In older systems created prior to August 2018, CentOS 7 and Fedora ship with [SELinux](/docs/guides/a-beginners-guide-to-selinux-on-centos-7/) running in enforcing mode by default. When switching from the Linode kernel to the upstream kernel, SELinux may need to relabel your filesystem at boot. When the relabeling completes, the Compute Instance will shut down. If you have [Lassie](/docs/products/compute/compute-instances/guides/lassie-shutdown-watchdog/) enabled, the instance will automatically boot back up following the shut down. If you do not have Lassie enabled, you will need to manually reboot from the Cloud Manager. +In older systems created before August 2018, CentOS 7 and Fedora ship with [SELinux](/docs/guides/a-beginners-guide-to-selinux-on-centos-7/) running in enforcing mode by default. When switching from the Linode kernel to the upstream kernel, SELinux may need to relabel your filesystem at boot. When the relabeling completes, the Compute Instance will shut down. If you have [Lassie](/docs/products/compute/compute-instances/guides/lassie-shutdown-watchdog/) enabled, the instance will automatically boot back up following the shut down. If you do not have Lassie enabled, you will need to manually reboot from Cloud Manager. ![SELinux filesystem relabel](selinux-filesystem-relabel.png "SELinux filesystem relabel") diff --git a/docs/products/compute/compute-instances/guides/metadata-cloud-config/index.md b/docs/products/compute/compute-instances/guides/metadata-cloud-config/index.md index 26a207a7eb4..b473543cda1 100644 --- a/docs/products/compute/compute-instances/guides/metadata-cloud-config/index.md +++ b/docs/products/compute/compute-instances/guides/metadata-cloud-config/index.md @@ -14,7 +14,7 @@ Cloud-config data is written using the YAML syntax, a commonly used data seriali ## Cloud-Config Modules -A cloud-config file must contain `#cloud-config` as the first line. Following that, you can utilize the keys provided by any of the cloud-init modules. Review the remaining sections of this guide for a list of common modules and how to configure them. For a full list of modules/keys, review [cloud-init Module Reference](https://cloudinit.readthedocs.io/en/latest/reference/modules.html). +A cloud-config file must contain `#cloud-config` as the first line. Following that, you can use the keys provided by any of the cloud-init modules. Review the remaining sections of this guide for a list of common modules and how to configure them. For a full list of modules/keys, review [cloud-init Module Reference](https://cloudinit.readthedocs.io/en/latest/reference/modules.html). ## Create a New User and Restrict Root Access diff --git a/docs/products/compute/compute-instances/guides/metadata/index.md b/docs/products/compute/compute-instances/guides/metadata/index.md index f84f9f07099..c6d65f5bf88 100644 --- a/docs/products/compute/compute-instances/guides/metadata/index.md +++ b/docs/products/compute/compute-instances/guides/metadata/index.md @@ -10,14 +10,14 @@ When deploying Compute Instances, it's almost always necessary to perform additi ## Overview -Linode's Metadata service provides a convenient method to automate software configuration when deploying a Compute Instance. It is an API that's accessible only from within a provisioned Compute Instance and provides relevant metadata to that instance. The Metadata service is designed to be consumed by [cloud-init](https://cloudinit.readthedocs.io/en/latest/), an industry standard software that automates cloud instance initialization. This allows you to use the same tool across multiple cloud providers, enabling a pathway for provisioning your systems as part of a multi-cloud infrastructure strategy. +Linode's Metadata service provides a convenient method to automate software configuration when deploying a Compute Instance. It is an API that's accessible only from within a provisioned Compute Instance and provides relevant metadata to that instance. The Metadata service is designed to be consumed by [cloud-init](https://cloudinit.readthedocs.io/en/latest/), an industry standard software that automates cloud instance initialization. This lets you use the same tool across multiple cloud providers, enabling a pathway for provisioning your systems as part of a multi-cloud infrastructure strategy. The Metadata service provides both *instance data* and optional *user data*, both of which are explained below: - **Instance data:** The instance data includes information about the Compute Instance, including its label, plan size, region, host identifier, and more. -- **User data:** User data is one of the most powerful features of the Metadata service and allows you to define your desired system configuration, including creating users, installing software, configuring settings, and more. User data is supplied by the user when deploying, rebuilding, or cloning a Compute Instance. This user data can be written as a cloud-config file, or it can be any script that can be executed on the target distribution image, such as a bash script. +- **User data:** User data is one of the most powerful features of the Metadata service and lets you define your desired system configuration, including creating users, installing software, configuring settings, and more. User data is supplied by the user when deploying, rebuilding, or cloning a Compute Instance. This user data can be written as a cloud-config file, or it can be any script that can be executed on the target distribution image, such as a bash script. - User data can be submitted directly in the Cloud Manager, Linode CLI, or Linode API. It's also often programmatically provided through IaC (Infrastructure as Code) provisioning tools like [Terraform](/docs/guides/how-to-build-your-infrastructure-using-terraform-and-linode/). + User data can be submitted directly in Cloud Manager, Linode CLI, or Linode API. It's also often programmatically provided through IaC (Infrastructure as Code) provisioning tools like [Terraform](/docs/guides/how-to-build-your-infrastructure-using-terraform-and-linode/). When a Compute Instance first boots up, cloud-init runs locally on the system, accesses the metadata, and then configures your system using that metadata. @@ -33,7 +33,7 @@ Akamai's Metadata service is available in select data centers. Additionally, use - **Distributions:** Ubuntu 22.04 LTS, Ubuntu 20.04 LTS, Debian 11 -When selecting a distribution in the Cloud Manager, the following icon designates distributions that fully support the Metadata service: +When selecting a distribution in Cloud Manager, the following icon designates distributions that fully support the Metadata service: ![Screenshot showing icon that indicates user data and cloud-init support for a distribution](cloud-init-supported-image.png) @@ -47,13 +47,13 @@ The Metadata service is always active, so there's no need to enable it. User dat {{< tabs >}} {{< tab "Cloud Manager" >}} -1. Navigate to the **Linodes** page in the [Cloud Manager](http://cloud.linode.com) and click the **Create Linode** button. This opens the **Create Linode** form. +1. Navigate to the **Linodes** page in [Cloud Manager](http://cloud.linode.com) and click the **Create Linode** button. This opens the **Create Linode** form. 1. Fill out the form with your desired settings. Be sure to select one of the supported distribution images and data centers. 1. Expand the *Add User Data* section and enter your user data into the **User Data** field. - ![Screenshot of the Add User Data section in the Cloud Manager](user-data-section.png) + ![Screenshot of the Add User Data section in Cloud Manager](user-data-section.png) If you are unfamiliar with cloud-init, you can review the [Cloud-Config Usage and Examples](/docs/products/compute/compute-instances/guides/metadata-cloud-config/) guide for help creating a cloud-config file. @@ -145,7 +145,7 @@ base64 --wrap=0 [file] ## Modify Cloud-Init Configuration and Save a Custom Image {#modify-cloud-init} -Our supported distribution images have cloud-init pre-installed and configured to interact with our Metadata service. Beyond submitting user data, you are not able to adjust cloud-init settings directly through the Cloud Manager, Linode CLI, or Linode API. If you do wish to deploy Compute Instances using a modified cloud-init configuration, you can use our [Images](/docs/products/tools/images/) service. +Our supported distribution images have cloud-init pre-installed and configured to interact with our Metadata service. Beyond submitting user data, you are not able to adjust cloud-init settings directly through Cloud Manager, Linode CLI, or Linode API. If you do wish to deploy Compute Instances using a modified cloud-init configuration, you can use our [Images](/docs/products/tools/images/) service. 1. Deploy a new Compute Instance using your preferred supported distribution image. 1. Log in to that instance using SSH or Lish and then modify the cloud-init configuration files (or add your own). These files are typically located in the `/etc/cloud/` folder. @@ -222,7 +222,7 @@ If you are not able to access your system through SSH, you can use [Lish](/docs/ ### Run the `cloud-init` Command -The `cloud-init` command-line tool can be used to gather more information or perform certain actions. Here are some commands you can utilize to help troubleshoot cloud-init. +The `cloud-init` command-line tool can be used to gather more information or perform certain actions. Here are some commands you can use to help troubleshoot cloud-init. - `cloud-init status --long`: This provides information about the status of cloud-init. You will notice different output depending on if it is actively running or if has run in the past. See [cloud-init status](https://cloudinit.readthedocs.io/en/latest/reference/cli.html#status). - `cloud-init query v1` and `cloud-init query userdata`: This outputs either the instance data or the user data provided by the Metadata service. Other metadata is also exposed by entering a different query key. See [cloud-init query](https://cloudinit.readthedocs.io/en/latest/reference/cli.html#query). \ No newline at end of file diff --git a/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md b/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md index e1229a64e91..2c6dfb7d18f 100644 --- a/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md +++ b/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md @@ -1,6 +1,6 @@ --- title: Migrate to a New Data Center -description: "Learn how to migrate a Compute Instance across data centers using the Cloud Manager." +description: "Learn how to migrate a Compute Instance across data centers using Cloud Manager." keywords: ["choose", "help", "migration", "data center"] tags: ["linode platform","cloud manager"] modified: 2024-05-09 @@ -18,9 +18,9 @@ Review the [Choosing a Data Center](/docs/products/platform/get-started/guides/c ## Before You Begin -Various changes applied by the migration can impact your instance's configuration and the devices connected to it. They can all be seen in a caution message before proceeding with your migration within the Cloud Manager. Here are some changes you should be aware of: +Various changes applied by the migration can impact your instance's configuration and the devices connected to it. They can all be seen in a caution message before proceeding with your migration within Cloud Manager. Here are some changes you should be aware of: -- **IP addresses are not transferrable** They aren't migrated to the new data center with your Compute Instance. Akamai issues a new IPv4 and IPv6 address for your instance, and you can access them once the migration completes. When your instance enters the migration queue, new IP addresses are reserved and you can see them in your instance's **Networking** detail page. See the [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide to learn how to access Networking information in the Cloud Manager. +- **IP addresses are not transferrable** They aren't migrated to the new data center with your Compute Instance. Akamai issues a new IPv4 and IPv6 address for your instance, and you can access them once the migration completes. When your instance enters the migration queue, new IP addresses are reserved and you can see them in your instance's **Networking** detail page. See the [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide to learn how to access Networking information in Cloud Manager. - **DNS records need to be updated**. You need to update DNS records with the new IP address once migrated. If you're hosting your DNS with us, this can be done through the [DNS Manager](/docs/products/networking/dns-manager/), while [rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) can be configured directly on each Compute Instance's Networking detail page. @@ -42,7 +42,7 @@ Various changes applied by the migration can impact your instance's configuratio ## Migrate to a New Data Center -1. Log in to the [Cloud Manager](https://www.cloud.linode.com) and click on the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click on the **Linodes** link in the sidebar. 1. Locate the Compute Instance within the **Linodes** table, click the corresponding **More Options** ellipsis menu, and select *Migrate* to open the **Migrate Linode** form. diff --git a/docs/products/compute/compute-instances/guides/monitor-and-maintain/index.md b/docs/products/compute/compute-instances/guides/monitor-and-maintain/index.md index c477c9388a5..74ffc3140f4 100644 --- a/docs/products/compute/compute-instances/guides/monitor-and-maintain/index.md +++ b/docs/products/compute/compute-instances/guides/monitor-and-maintain/index.md @@ -59,7 +59,7 @@ To turn Lassie on and off, see the [Recover from Unexpected Shutdowns with Lassi ## Manage Logs -Important events that occur on your system — things like login attempts or services being restarted — are recorded in your server's *logs*. Similar to car maintenance records and completed tax forms, which provide a paper trail in the event of a problem or discrepancy, log files keep track of system events. You might review logs when troubleshooting errors, tracking usage, or investigating unusual behavior on your system. +Important events that occur on your system — things like login attempts or services being restarted — are recorded in your server's *logs*. Similar to car maintenance records and completed tax forms, which provide a paper trail if a problem or discrepancy occurs, log files keep track of system events. You might review logs when troubleshooting errors, tracking usage, or investigating unusual behavior on your system. ### Rotate Logs @@ -96,9 +96,9 @@ There are ways to automate the installation of software updates, but this is not ### Apply Kernel Updates -When you first sign up for Linode and create a Compute Instance, the Cloud Manager automatically creates a [configuration profile](/docs/products/compute/compute-instances/guides/configuration-profiles/) that uses either the distribution's system kernel (in most cases) or uses the latest available Linode-supplied kernel. +When you first sign up for Linode and create a Compute Instance, Cloud Manager automatically creates a [configuration profile](/docs/products/compute/compute-instances/guides/configuration-profiles/) that uses either the distribution's system kernel (in most cases) or uses the latest available Linode-supplied kernel. -If your system is using a Linode-supplied kernel, it's important to know that we [update the kernels](http://www.linode.com/kernels/) as necessary and make them available in the Cloud Manager. In most cases, new kernels are automatically selected and, once a new kernel is released, all you have to do is reboot your Compute Instance to start using it. +If your system is using a Linode-supplied kernel, it's important to know that we [update the kernels](http://www.linode.com/kernels/) as necessary and make them available in Cloud Manager. In most cases, new kernels are automatically selected and, once a new kernel is released, all you have to do is reboot your Compute Instance to start using it. To check for a new kernel and start using it on your Compute Instance: @@ -114,7 +114,7 @@ To check for a new kernel and start using it on your Compute Instance: Linux version 4.15.12-x86_64-linode105 (maker@build.linode.com) (gcc version 4.9.2 (Debian 4.9.2-10+deb8u1)) #1 SMP Thu Mar 22 02:13:40 UTC 2018 ``` -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click the **Linodes** link in the sidebar. 1. Select your Compute Instance. The instance's details page appears. 1. Select the active configuration profile by clicking the **Edit** link, as shown below. diff --git a/docs/products/compute/compute-instances/guides/multiqueue-nic/index.md b/docs/products/compute/compute-instances/guides/multiqueue-nic/index.md index 254dfcaf2f1..1647813303f 100644 --- a/docs/products/compute/compute-instances/guides/multiqueue-nic/index.md +++ b/docs/products/compute/compute-instances/guides/multiqueue-nic/index.md @@ -15,13 +15,13 @@ aliases: ['/guides/multiqueue-nic/'] Multi-queue NICs (network interface cards) are supported on all Compute Instances that have 2 or more CPU cores (vCPUs). This feature provides multiple receive (RX) and transmit (TX) queues, assigns them to different network interrupts, and balances them over multiple vCPUs. Historically, this traffic was all handled by a single vCPU core. Depending on the server's workload and network traffic, multi-queue can dramatically enhance network performance. -**For most Compute Instances deployed after June 2nd, 2021, no action is needed to enable multi-queue NICs**. If your Compute Instance was deployed prior to that date, a reboot may be required. On older Linux distributions, such as Debian 8 and 9, multi-queue NICs needs to be manually enabled by following the instructions within this guide. +**For most Compute Instances deployed after June 2nd, 2021, no action is needed to enable multi-queue NICs**. If your Compute Instance was deployed before that date, a reboot may be required. On older Linux distributions, such as Debian 8 and 9, multi-queue NICs needs to be manually enabled by following the instructions within this guide. ## Determining if Multi-Queue is Enabled Check if multi-queue is already enabled on your network devices by using the [ethtool](https://en.wikipedia.org/wiki/Ethtool) command-line tool. -1. Review the number of CPU cores (vCPUs) available on your Compute Instance by finding your plan within the [Linode Pricing](https://www.linode.com/pricing/) page or by logging in to the [Cloud Manager](https://cloud.linode.com/), selecting your Compute Instance, and reviewing the *CPU Cores* value under **Summary**. +1. Review the number of CPU cores (vCPUs) available on your Compute Instance by finding your plan within the [Linode Pricing](https://www.linode.com/pricing/) page or by logging in to [Cloud Manager](https://cloud.linode.com/), selecting your Compute Instance, and reviewing the *CPU Cores* value under **Summary**. 1. Log in to your Compute Instance through [Lish](/docs/products/compute/compute-instances/guides/lish/) or [SSH](/docs/guides/connect-to-server-over-ssh/). @@ -68,7 +68,7 @@ Check if multi-queue is already enabled on your network devices by using the [et If multi-queue is not enabled and a reboot did not automatically enable it, you can manually enable this feature through the following instructions. -1. Review the number of vCPU cores available on your Compute Instance by finding your plan within the [Linode Pricing](https://www.linode.com/pricing/) page or by logging in to the [Cloud Manager](https://cloud.linode.com/), selecting your Compute Instance, and reviewing the *CPU Cores* value under **Summary**. +1. Review the number of vCPU cores available on your Compute Instance by finding your plan within the [Linode Pricing](https://www.linode.com/pricing/) page or by logging in to [Cloud Manager](https://cloud.linode.com/), selecting your Compute Instance, and reviewing the *CPU Cores* value under **Summary**. 1. Run the following command to enable multiple queues, replacing *[cpu-count]* with the number of vCPUs on your Compute Instance. diff --git a/docs/products/compute/compute-instances/guides/netplan/index.md b/docs/products/compute/compute-instances/guides/netplan/index.md index 3729342dd68..f95c9e399d0 100644 --- a/docs/products/compute/compute-instances/guides/netplan/index.md +++ b/docs/products/compute/compute-instances/guides/netplan/index.md @@ -61,7 +61,7 @@ Learn more about the full extent of Netplan's YAML configuration options in the ## Configuring IP Addresses Manually -1. Log in to the [Cloud Manager](https://cloud.linode.com/), and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) for assistance. Make a note of the following pieces of information or keep this page accessible so you can reference it later. +1. Log in to [Cloud Manager](https://cloud.linode.com/), and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) for assistance. Make a note of the following pieces of information or keep this page accessible so you can reference it later. - Public IPv4 address(es) and the associated IPv4 gateway @@ -89,7 +89,7 @@ Learn more about the full extent of Netplan's YAML configuration options in the sudo nano /etc/netplan/01-netcfg.yaml ``` -1. Once you've edited the configuration file to fit your needs, you need to generate matching backend configurations and apply the changes. To do so, run the follow Netplan commands: +1. Once you've edited the configuration file to fit your needs, you need to generate matching back-end configurations and apply the changes. To do so, run the follow Netplan commands: ```command sudo netplan generate @@ -137,7 +137,7 @@ The default Netplan configuration file shows how to enable DHCP on an interface. ``` {{< note type="warning" >}} -When using DHCP, the IPv4 address configured on your system may change if you add or remove IPv4 addresses on this instance from the Cloud Manager, Linode CLI, or Linode API. If this happens, any tool or system using the original IPv4 address is no longer able to connect. +When using DHCP, the IPv4 address configured on your system may change if you add or remove IPv4 addresses on this instance from Cloud Manager, Linode CLI, or Linode API. If this happens, any tool or system using the original IPv4 address is no longer able to connect. {{< /note >}} ## Configuring Additional IPv4 Addresses diff --git a/docs/products/compute/compute-instances/guides/network-helper/index.md b/docs/products/compute/compute-instances/guides/network-helper/index.md index cb75d93c25b..cc3d1d3490d 100644 --- a/docs/products/compute/compute-instances/guides/network-helper/index.md +++ b/docs/products/compute/compute-instances/guides/network-helper/index.md @@ -51,7 +51,7 @@ Network Helper can be enabled or disabled for each Compute Instance. There is al The global Network Helper setting enables or disables Network Helper on *new* Compute Instances. Existing Compute Instances are not affected by any changes to this global setting. When Network Helper is enabled globally, all *new* Compute Instances are created with Network Helper enabled by default. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Account** link on the left sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Account** link on the left sidebar. 1. Navigate to the **Settings** tab and scroll down to the *Network Helper* section. diff --git a/docs/products/compute/compute-instances/guides/network-infrastructure-upgrades/index.md b/docs/products/compute/compute-instances/guides/network-infrastructure-upgrades/index.md index f02793f4156..6a9bc446972 100644 --- a/docs/products/compute/compute-instances/guides/network-infrastructure-upgrades/index.md +++ b/docs/products/compute/compute-instances/guides/network-infrastructure-upgrades/index.md @@ -13,7 +13,7 @@ For most customers, these upgrades are performed seamlessly behind the scenes. F ## What's New? -- **IP Sharing (IP failover) availability:** The IP Sharing feature, as it exists prior to these upgrades, enables IP failover for public IPv4 addresses in select data centers. After the upgrades have been completed, this feature will be expanded to all data centers and will also support IPv6 routed ranges (/64 and /56). See our [Configuring IP Failover on a Compute Instance](/docs/products/compute/compute-instances/guides/failover/) guide to learn more about configuring IP failover. +- **IP Sharing (IP failover) availability:** The IP Sharing feature, as it exists before these upgrades, enables IP failover for public IPv4 addresses in select data centers. After the upgrades have been completed, this feature will be expanded to all data centers and will also support IPv6 routed ranges (/64 and /56). See our [Configuring IP Failover on a Compute Instance](/docs/products/compute/compute-instances/guides/failover/) guide to learn more about configuring IP failover. - **VLAN availability:** [VLANs](/docs/products/networking/vlans/), which enable private layer 2 networking, will be launched across all data centers soon after the network upgrades have occurred. diff --git a/docs/products/compute/compute-instances/guides/networkmanager/index.md b/docs/products/compute/compute-instances/guides/networkmanager/index.md index bdfbe1f110d..6bc35f8233f 100644 --- a/docs/products/compute/compute-instances/guides/networkmanager/index.md +++ b/docs/products/compute/compute-instances/guides/networkmanager/index.md @@ -53,7 +53,7 @@ PREFIX0=24 ## Configuring IP Addresses Manually -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make a note of the following pieces of information or keep this page accessible so you can reference it later. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make a note of the following pieces of information or keep this page accessible so you can reference it later. - Public IPv4 address(es) and the associated IPv4 gateway - Private IPv4 address (if one has been added) diff --git a/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md b/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md index af8e3bea544..c7f0b8c8ccb 100644 --- a/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md +++ b/docs/products/compute/compute-instances/guides/rescue-and-rebuild/index.md @@ -1,6 +1,6 @@ --- title: Rescue and Rebuild -description: 'Learn how to rescue and rebuild a Compute Instance by using the recovery tools available in the Cloud Manager.' +description: 'Learn how to rescue and rebuild a Compute Instance by using the recovery tools available in Cloud Manager.' published: 2012-05-31 modified: 2023-09-07 keywords: ["rescue", "rebuild"] @@ -9,7 +9,7 @@ image: rescue-rebuild.jpg aliases: ['/troubleshooting/rescue-and-rebuild-classic-manager/','/troubleshooting/rescue-and-rebuild/','/rescue-and-rebuild/','/troubleshooting/finnix-rescue-mode/','/guides/rescue-and-rebuild/'] --- -Even the best system administrators may need to deal with unplanned events in the operation of their services. The Cloud Manager provides recovery tools that you can leverage if you are having trouble connecting to one of the Compute Instances, and this guide describes those tools: +Even the best system administrators may need to deal with unplanned events in the operation of their services. Cloud Manager provides recovery tools that you can leverage if you are having trouble connecting to one of the Compute Instances, and this guide describes those tools: - You can boot your Compute Instance into [*Rescue Mode*](#rescuing) to perform system recovery tasks and transfer data off the disks, if necessary. @@ -39,7 +39,7 @@ While this guide outlines the recovery tools that Linode makes available to you, ### Rescue Mode Overview -To access Rescue Mode, you need to [reboot your Compute Instance](#booting-into-rescue-mode) from the Cloud Manager and then connect through [Lish](#connecting-to-a-linode-running-in-rescue-mode) or [SSH](#starting-ssh). After you connect, you can [perform a check on your filesystem](#performing-a-file-system-check) if you suspect that it is corrupted. If you need access to a certain software package to troubleshoot the system, you can [install it](#installing-packages). +To access Rescue Mode, you need to [reboot your Compute Instance](#booting-into-rescue-mode) from Cloud Manager and then connect through [Lish](#connecting-to-a-linode-running-in-rescue-mode) or [SSH](#starting-ssh). After you connect, you can [perform a check on your filesystem](#performing-a-file-system-check) if you suspect that it is corrupted. If you need access to a certain software package to troubleshoot the system, you can [install it](#installing-packages). Disks are not mounted by default and need to be [mounted manually](#mounting-disks) before you can access your files. After you mount the primary filesystem, you can [*change root*](#change-root) to have Rescue Mode emulate normal Linux distribution. @@ -47,7 +47,7 @@ Disks are not mounted by default and need to be [mounted manually](#mounting-dis To boot a Compute Instance into Rescue Mode, follow the instructions below. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click the **Linodes** link in the sidebar: @@ -90,7 +90,7 @@ To boot a Compute Instance into Rescue Mode, follow the instructions below. By default, Rescue Mode's Finnix environment does not accept SSH connections. To access the Compute Instance when it's running in Rescue Mode, connect to it through the *Lish* console. {{< note >}} -It is possible to enable SSH for Rescue Mode by manually starting the SSH daemon. Using SSH can provide a better experience and allows you to copy files off of the server. Review the [Starting SSH](#starting-ssh) section for instructions. You need to use Lish at least once in order to start SSH. +It is possible to enable SSH for Rescue Mode by manually starting the SSH daemon. Using SSH can provide a better experience and lets you copy files off of the server. Review the [Starting SSH](#starting-ssh) section for instructions. You need to use Lish at least once in order to start SSH. {{< /note >}} To connect with Lish: @@ -197,7 +197,7 @@ You can use the `e2fsck` system utility (short for "ext file system check") to c Press **enter** to automatically attempt to fix the problems. - After the filesystem check completes, any problems detected should be fixed. Try rebooting the Compute Instance from the Cloud Manager. If `e2fsck` fixed the issues, the instance should boot normally. + After the filesystem check completes, any problems detected should be fixed. Try rebooting the Compute Instance from Cloud Manager. If `e2fsck` fixed the issues, the instance should boot normally. ### Installing Packages @@ -265,7 +265,7 @@ If you would like to mount or unmount additional disks on your system, repeat th *Changing root* is the process of changing your working root directory. When you change root (abbreviated as *chroot*) to your root disk, you are able to run commands as though you are logged in to that system. -Chroot allows you to change user passwords, remove/install packages, and do other system maintenance and recovery tasks in your Compute Instance's normal Linux environment. +Chroot lets you change user passwords, remove/install packages, and do other system maintenance and recovery tasks in your Compute Instance's normal Linux environment. 1. Create a new directory for your disk: @@ -280,7 +280,7 @@ Chroot allows you to change user passwords, remove/install packages, and do othe ``` {{< note >}} - If you mounted your disk without using the `exec` option prior to reviewing this section, include the `remount` option in your `mount` command: + If you mounted your disk without using the `exec` option before reviewing this section, include the `remount` option in your `mount` command: ```command mount -o remount,exec,barrier=0 /dev/sda /media/sda @@ -331,7 +331,7 @@ If you can't rescue and resolve issues on an existing disk, you likely need to r - If you are subscribed to the [Backup Service](https://www.linode.com/backups), you can [restore from an existing backup](#restoring-from-a-linode-backup) and return the Compute Instance to a previous state. -- If you aren't subscribed to the Backup Service, you can copy files off an existing disk and then [use the Rebuild feature](#use-the-rebuild-feature) of the Cloud Manager to erase everything and start over again from scratch. +- If you aren't subscribed to the Backup Service, you can copy files off an existing disk and then [use the Rebuild feature](#use-the-rebuild-feature) of Cloud Manager to erase everything and start over again from scratch. - If you have a backup system other than the Backup Service in place, you can [rebuild your Compute Instance](#use-the-rebuild-feature) and then restore the data from that backup service. The methods for restoring data varies by the kind of backup system that you use. @@ -349,11 +349,11 @@ If you created backups with an application other than Linode's Backup Service, r ### Use the Rebuild Feature -The Cloud Manager provides a *Rebuild* feature performs the following two actions: +Cloud Manager provides a *Rebuild* feature performs the following two actions: 1. The current disks are removed. -1. A new set of disks is provisioned from one of the Cloud Manager's built-in Linux images, or from one of the [saved images](/docs/products/tools/images/). +1. A new set of disks is provisioned from one of Cloud Manager's built-in Linux images, or from one of the [saved images](/docs/products/tools/images/). {{< note type="alert" >}} If you use the Rebuild feature, the data from the disks that are deleted are not retrievable. You may [back up your data manually](/docs/guides/backing-up-your-data/) or [create a snapshot through Linode's Backup Service](/docs/products/storage/backups/guides/take-a-snapshot/) to preserve data before using the Rebuild feature. @@ -369,7 +369,7 @@ To use the Rebuild feature: 1. If you need to copy files from existing disk to another location before rebuilding, you can [start SSH](#starting-ssh) under Rescue Mode and then use an [SFTP client](/docs/tools-reference/file-transfer/) to copy files to your computer, another server, or somewhere else. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click on the **Linodes** link in the sidebar: @@ -379,7 +379,7 @@ To use the Rebuild feature: ![Cloud Manager Linodes page - rebuild option highlighted](cloud-manager-linodes-rebuild.png) -1. Complete the Rebuild form. Select an image or StackScript to deploy and enter a root password. Optionally, select one or more SSH keys (if you have not added any SSH Keys via the Cloud Manager, this option does not appear). +1. Complete the Rebuild form. Select an image or StackScript to deploy and enter a root password. Optionally, select one or more SSH keys (if you have not added any SSH Keys via Cloud Manager, this option does not appear). {{% content "password-requirements-shortguide" %}} diff --git a/docs/products/compute/compute-instances/guides/reset-root-password/index.md b/docs/products/compute/compute-instances/guides/reset-root-password/index.md index b18469a8057..e0383b3d2de 100644 --- a/docs/products/compute/compute-instances/guides/reset-root-password/index.md +++ b/docs/products/compute/compute-instances/guides/reset-root-password/index.md @@ -10,7 +10,7 @@ aliases: ['/quick-answers/linode-platform/reset-the-root-password-on-your-linode All Compute Instances deployed using one of Linode's [official distribution images](/docs/products/compute/compute-instances/guides/distributions/) provide the ability to reset the root password on the system. This is useful if you ever lock yourself out of your instance's root account or are simply rotating your password for security. Follow the instructions below to reset your root password: -1. Log in to the [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. +1. Log in to [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar, and select a Compute Instance from the list. 1. Click the **Power Off** button in the upper right of the Compute Instance's dashboard or within the **ellipsis** menu. Wait until the Compute Instance has been fully powered off before continuing to the next step. diff --git a/docs/products/compute/compute-instances/guides/resize/index.md b/docs/products/compute/compute-instances/guides/resize/index.md index d7bcfd5d3cc..506d2058911 100644 --- a/docs/products/compute/compute-instances/guides/resize/index.md +++ b/docs/products/compute/compute-instances/guides/resize/index.md @@ -32,15 +32,15 @@ You have two resize options to choose from: **warm** and **cold**. Each refer to - **Warm resize**. Your compute instance remains up during the migration and it's rebooted once the migration completes. So, make sure your instance is powered on for this resize. If you see a warning message about an inability to power down your compute instance, try the resize again using the cold resize option. There is less downtime during a warm resize than a cold resize. -- **Cold resize**. This shuts down your compute instance, migrates it to a new host, and restores it to its booted state prior to the resize process. +- **Cold resize**. This shuts down your compute instance, migrates it to a new host, and restores it to its booted state before the resize process. ## Resize a compute instance -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select **Linodes**. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select **Linodes**. 2. In the list of compute instances, find the one you want to resize, click the corresponding **...**, and select **Resize**. The **Resize Linode** panel is displayed. - ![The Resize Linode panel in the Cloud Manager](resize-linode-plan.jpg) + ![The Resize Linode panel in Cloud Manager](resize-linode-plan.jpg) 3. Select the plan you want: diff --git a/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md b/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md index 3838a92c22d..a6d53570d1a 100644 --- a/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md +++ b/docs/products/compute/compute-instances/guides/set-up-and-secure/index.md @@ -16,7 +16,7 @@ After you have successfully created a Compute Instance, there are a few initial While this guide is optional, it walks you through best practices and covers important steps to secure your server. It is recommended that you follow these instructions when deploying a new Compute Instance. Some guides within our library assume that you have performed these steps, such as setting your hostname and updating your software. {{< /note >}} -1. [View your Instance in the Cloud Manager](#view-your-instance-in-the-cloud-manager) +1. [View your Instance in Cloud Manager](#view-your-instance-in-the-cloud-manager) 1. [Connect to the Instance](#connect-to-the-instance) 1. [Perform System Updates](#perform-system-updates) 1. [Set the Timezone](#set-the-timezone) @@ -34,9 +34,9 @@ If you haven't done so already, review the following guides to learn more about - [Creating a Compute Instance](/docs/products/compute/compute-instances/guides/create/) - [Linode Beginner's Guide](/docs/products/compute/compute-instances/faqs/) -## View your Instance in the Cloud Manager +## View your Instance in Cloud Manager -Log in to the [Cloud Manager](https://cloud.linode.com/), click the **Linodes** link in the left menu, and select your Compute Instance from the list. This opens the details page for that instance, which allows you to view key information and further configure it to meet your needs. +Log in to [Cloud Manager](https://cloud.linode.com/), click the **Linodes** link in the left menu, and select your Compute Instance from the list. This opens the details page for that instance, which lets you view key information and further configure it to meet your needs. ![Details page in Cloud Manager](create-instance-details.png) @@ -44,7 +44,7 @@ Log in to the [Cloud Manager](https://cloud.linode.com/), click the **Linodes** Once the Compute Instance has been created and has finished booting up, you can connect to it. Connecting to your instance is usually done through the SSH (Secure Shell) protocol, though you can use the [Lish Console](/docs/products/compute/compute-instances/guides/lish/) to bypass SSH and connect directly to your instance. The Lish Console can be accessed through a web browser (Weblish) or via SSH on the command line. -- **Weblish (via the Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). +- **Weblish (via Cloud Manager):** Click the **Launch LISH Console** link at the top right corner of the Compute Instance's detail page. See [Using the Lish Console > Through a Browser](/docs/products/compute/compute-instances/guides/lish/#through-the-cloud-manager-weblish). - **SSH:** Copy the command from the *SSH Access* field under the **Access** section on the Compute Instance's detail page (see screenshot above) and paste it into your local computer's terminal. The command should look similar to the following, only with the IP address of your newly created instance. @@ -363,7 +363,7 @@ To protect your user account with public key authentication, you first need to c - **macOS:** `/Users/username/.ssh/` - **Windows:** `C:\Users\Username\.ssh\` - Since SSH keys are generated as a private and public key pair, there should be two files for each SSH key. They have similar file names, with the public key using a `.pub` extension and the private key using no extension. While SSH keys can have custom file names, many people generate them using their default names. These default file names start with `id_` followed by the type of key, such as `id_rsa`, `id_ed25519`, and `id_ecdsa`. See example private and public key file names below: + Since SSH keys are generated as a private and public key pair, there should be two files for each SSH key. They have similar filenames, with the public key using a `.pub` extension and the private key using no extension. While SSH keys can have custom filenames, many people generate them using their default names. These default filenames start with `id_` followed by the type of key, such as `id_rsa`, `id_ed25519`, and `id_ecdsa`. See example private and public key filenames below: - **Private key:** `id_ed25519` - **Public key:** `id_ed25519.pub` @@ -524,9 +524,9 @@ Using a *firewall* to block unwanted inbound traffic to your Compute Instance pr - [nftables](/docs/guides/how-to-use-nftables/) or its predecessor, [iptables](/docs/guides/control-network-traffic-with-iptables/), is the controller for netfilter, the Linux kernel's packet filtering framework. One of these utilities is included in most Linux distributions by default. -- [firewalld](/docs/guides/introduction-to-firewalld-on-centos/) is a firewall management tool that serves as a frontend to nftables or iptables. It is preinstalled on the RHEL family of distributions (and others), including CentOS, AlmaLinux, Rocky Linux, Fedora, and openSUSE Leap. +- [firewalld](/docs/guides/introduction-to-firewalld-on-centos/) is a firewall management tool that serves as a front end to nftables or iptables. It is preinstalled on the RHEL family of distributions (and others), including CentOS, AlmaLinux, Rocky Linux, Fedora, and openSUSE Leap. -- [UFW](/docs/guides/configure-firewall-with-ufw/) is another firewall management tool that operates as a frontend to nftables or iptables. It is used by default on Ubuntu and is also available on other Debian-based distributions. +- [UFW](/docs/guides/configure-firewall-with-ufw/) is another firewall management tool that operates as a front end to nftables or iptables. It is used by default on Ubuntu and is also available on other Debian-based distributions. ## Common Lockout Recovery Steps diff --git a/docs/products/compute/compute-instances/guides/systemd-networkd/index.md b/docs/products/compute/compute-instances/guides/systemd-networkd/index.md index da58de57aeb..09def22694d 100644 --- a/docs/products/compute/compute-instances/guides/systemd-networkd/index.md +++ b/docs/products/compute/compute-instances/guides/systemd-networkd/index.md @@ -11,7 +11,7 @@ aliases: ['/guides/systemd-networkd/'] The [systemd-networkd](https://wiki.archlinux.org/title/systemd-networkd) tool is a newer tool developed as part of systemd. Arch and modern versions of Ubuntu (17.10 and above) currently use systemd-networkd as their default network configuration software. {{< note >}} -By default, Linode's Network Helper tool manages networking in Ubuntu using systemd-networkd. Ubuntu also has utility called Netplan that serves as a frontend for configuring either systemd-networkd or NetworkManager. To use Netplan instead, review the [Network Configuration Using Netplan](/docs/products/compute/compute-instances/guides/netplan/) guide. +By default, Linode's Network Helper tool manages networking in Ubuntu using systemd-networkd. Ubuntu also has utility called Netplan that serves as a front end for configuring either systemd-networkd or NetworkManager. To use Netplan instead, review the [Network Configuration Using Netplan](/docs/products/compute/compute-instances/guides/netplan/) guide. {{< /note >}} {{< note >}} @@ -49,7 +49,7 @@ Address=192.0.2.123/24 - [**Name**](https://www.freedesktop.org/software/systemd/man/systemd.network.html#Name=): `eth0`, the default interface configured for the public internet on most Compute Instances. When using a VLAN, the public internet interface may be configured differently. -- [**DHCP**](https://www.freedesktop.org/software/systemd/man/systemd.network.html#DHCP=): `no`, which disables DHCP and allows you to statically define the main IPv4 address in later fields. +- [**DHCP**](https://www.freedesktop.org/software/systemd/man/systemd.network.html#DHCP=): `no`, which disables DHCP and lets you statically define the main IPv4 address in later fields. - [**DNS**](https://www.freedesktop.org/software/systemd/man/systemd.network.html#DNS=): A list of IP addresses that map to Linode's DNS resolvers. The IP addresses provided in this example are placeholders and do not function. @@ -63,7 +63,7 @@ Address=192.0.2.123/24 ## Configuring IP Addresses Manually -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make a note of the following pieces of information or keep this page accessible so you can reference it later. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and review your Compute Instance's IP addresses. See [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make a note of the following pieces of information or keep this page accessible so you can reference it later. - Public IPv4 address(es) and the associated IPv4 gateway - Private IPv4 address (if one has been added) diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md index 5bf437abb04..c4336a12364 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-connection-issues/index.md @@ -11,7 +11,7 @@ aliases: ['/troubleshooting/troubleshooting-basic-connection-issues/','/guides/t This guide presents troubleshooting strategies for Compute Instances that are unresponsive to any network access. One reason that an instance may be unresponsive is if you recently performed a distribution upgrade or other broad software updates to your system, as those changes can lead to unexpected problems for your core system components. -Similarly, your server may be unresponsive after maintenance was applied by Linode to your server's host (frequently, this is correlated with software/distribution upgrades performed on your deployment prior to the host's maintenance). This guide is designed as a useful resource for either of these scenarios. If you need to troubleshoot memory and networking, read our guide on [Troubleshooting Memory and Networking Issues](/docs/products/compute/compute-instances/guides/troubleshooting-memory-issues/). +Similarly, your server may be unresponsive after maintenance was applied by Linode to your server's host (frequently, this is correlated with software/distribution upgrades performed on your deployment before the host's maintenance). This guide is designed as a useful resource for either of these scenarios. If you need to troubleshoot memory and networking, read our guide on [Troubleshooting Memory and Networking Issues](/docs/products/compute/compute-instances/guides/troubleshooting-memory-issues/). If you can [ping](/docs/guides/linux-system-administration-basics/#the-ping-command) your Compute Instance, but you cannot access SSH or other services, this guide will not assist with troubleshooting those services. Instead, refer to the [Troubleshooting SSH](/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/) or [Troubleshooting Web Servers, Databases, and Other Services](/docs/products/compute/compute-instances/guides/troubleshooting-services/) guides. @@ -43,11 +43,11 @@ Review the installation instructions in Linode's [Diagnosing Network Issues with ## Is your Compute Instance Running? -Log in to the [Cloud Manager](https://cloud.linode.com/) and inspect the Compute Instance's dashboard. If the instance is powered off, turn it on. +Log in to [Cloud Manager](https://cloud.linode.com/) and inspect the Compute Instance's dashboard. If the instance is powered off, turn it on. ### Inspect the Lish Console -If the Compute Instance is listed as running in the Cloud Manager, or after you boot it from the Manager, open the Lish console and look for a login prompt. If a login prompt exists, try logging in with your root user credentials (or any other Linux user credentials that you previously created on the server). +If the Compute Instance is listed as running in Cloud Manager, or after you boot it from the Manager, open the Lish console and look for a login prompt. If a login prompt exists, try logging in with your root user credentials (or any other Linux user credentials that you previously created on the server). {{< note >}} The root user is available in Lish even if root user login is disabled in your SSH configuration. @@ -129,7 +129,7 @@ mtr -rwbzc 100 -i 0.2 -rw 198.51.100.0 Once you have generated this report, compare it with the following example scenarios. {{< note >}} -If you are located in China, and the output of your MTR report shows *high packet loss* or an *improperly configured router*, then your IP address may have been blacklisted by the GFW (Great Firewall of China). Linode is not able to change your IP address if it has been blacklisted by the GFW. If you have this issue, review this [community post](https://www.linode.com/community/questions/17192/ssh-refused) for troubleshooting help. +If you are located in China, and the output of your MTR report shows *high packet loss* or an *improperly configured router*, then your IP address may have been blocked (added to a blocklist) by the GFW (Great Firewall of China). Linode is not able to change your IP address if it has been blocked by the GFW. If you have this issue, review this [community post](https://www.linode.com/community/questions/17192/ssh-refused) for troubleshooting help. {{< /note >}} - **High Packet Loss** @@ -383,7 +383,7 @@ sudo ip6tables -L # displays IPv6 rules ``` {{< note >}} -Your deployment may be running FirewallD or UFW, which are frontend software packages used to more easily manage your iptables rules. Run these commands to find out if you are running either package: +Your deployment may be running FirewallD or UFW, which are front-end software packages used to more easily manage your iptables rules. Run these commands to find out if you are running either package: ```command sudo ufw status diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md index 84bbd972943..6d186f087e6 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-firewall-issues/index.md @@ -29,7 +29,7 @@ When using Lish, you can log in to your Compute Instance with the `root` user, e Ensure that your Compute Instance is powered on and running. -1. Log into the [Cloud Manager](https://cloud.linode.com/) and navigate to the Compute Instance listing page. +1. Log into [Cloud Manager](https://cloud.linode.com/) and navigate to the Compute Instance listing page. 1. Verify your Compute Instance's displayed status to determine if it's running or offline. If it your instance is offline, use the **more options** ellipsis to power it on. @@ -61,7 +61,7 @@ If you are using Cloud Firewalls, then it's important to verify which Cloud Fire ## Checking Firewall Rules with UFW -*Uncomplicated Firewall (UFW)* is an [iptables](/docs/guides/control-network-traffic-with-iptables/) frontend that is designed for ease-of-use. See our [How to Configure a Firewall with UFW](/docs/guides/configure-firewall-with-ufw/) for a deeper dive into UFW. +*Uncomplicated Firewall (UFW)* is an [iptables](/docs/guides/control-network-traffic-with-iptables/) front end that is designed for ease-of-use. See our [How to Configure a Firewall with UFW](/docs/guides/configure-firewall-with-ufw/) for a deeper dive into UFW. {{< note >}} All steps in this section are performed on your Compute Instance. [Connect to your Compute Instance via SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) or using [Lish](/docs/products/compute/compute-instances/guides/lish/). @@ -102,7 +102,7 @@ sudo ufw delete allow 80 ## Checking Firewall Rules with FirewallD -*firewalld* is the default firewall tool for CentOS and Fedora. While also a frontend for iptables like UFW, firewalld has some unique features, like configuration sets and zones. +*firewalld* is the default firewall tool for CentOS and Fedora. While also a front end for iptables like UFW, firewalld has some unique features, like configuration sets and zones. {{< note >}} All steps in this section are performed on your Compute Instance. [Connect to your Compute Instance via SSH](/docs/products/compute/compute-instances/guides/set-up-and-secure/#connect-to-the-instance) or using [Lish](/docs/products/compute/compute-instances/guides/lish/). diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-general-issues/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-general-issues/index.md index c49e4a999bd..01c20ecc4e9 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-general-issues/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-general-issues/index.md @@ -105,7 +105,7 @@ sudo systemd restart apache2 The applications on your Compute Instance require a certain amount of physical memory to function correctly. If all of the available physical memory is consumed, your system could slow down, display out of memory errors, or become unresponsive. Here's how to tell if your instance is out of memory: -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click the **Linodes** link in the sidebar to view a list of all your Compute Instance. 1. Select a Compute Instance to view its dashboard. 1. Click on the **Launch Console** link in the upper-right hand corner to launch the LISH Console. The LISH console window appears. If memory errors are displayed in the LISH console, stop some running services to free up memory or [upgrade to a larger plan](/docs/products/compute/compute-instances/guides/resize/). @@ -159,7 +159,7 @@ Telnet and FTP are disabled on your Compute Instance by default, and we strongly ### System User/Root Password -If you've forgotten the password for the root user on your Compute Instance, you can follow the steps for [resetting your root password](/docs/products/compute/compute-instances/guides/reset-root-password/) from the Cloud Manager. +If you've forgotten the password for the root user on your Compute Instance, you can follow the steps for [resetting your root password](/docs/products/compute/compute-instances/guides/reset-root-password/) from Cloud Manager. Once you have access to your Compute Instance as the root user, you can reset the password for any additional system users with the `passwd` command. The example resets the password for the `username` user: @@ -177,17 +177,17 @@ If you've followed these steps, but you're still having trouble accessing your a ## Cloud Manager is Displaying "Incorrect" Information -Use the following checklist if the Cloud Manager is displaying "incorrect" information. +Use the following checklist if Cloud Manager is displaying "incorrect" information. ### Did You Recently Change your Account? -If you recently created a new account, resized an existing Compute Instance, or added extra bandwidth, the bandwidth displayed in the Cloud Manager will be prorated for the amount of time left in the current billing cycle. For example, if you create an account on the 15th day of the month, the Manager will indicate that your account has been allocated half of the plan's bandwidth for the current month. This information is an accurate representation of the bandwidth available for the rest of the billing period. When then next billing period starts, the Manager will indicate that all of the plan's bandwidth is available. View the [Billing and Payments](/docs/products/platform/billing/) guide for more information. +If you recently created a new account, resized an existing Compute Instance, or added extra bandwidth, the bandwidth displayed in Cloud Manager will be prorated for the amount of time left in the current billing cycle. For example, if you create an account on the 15th day of the month, the Manager will indicate that your account has been allocated half of the plan's bandwidth for the current month. This information is an accurate representation of the bandwidth available for the rest of the billing period. When then next billing period starts, the Manager will indicate that all of the plan's bandwidth is available. View the [Billing and Payments](/docs/products/platform/billing/) guide for more information. ### Did You Add Additional Storage? -If you recently upgraded your plan, your Compute Instance won't be able to take advantage of the additional space until you resize the disk. You can use the Cloud Manager to verify if there's additional storage space available for disks: +If you recently upgraded your plan, your Compute Instance won't be able to take advantage of the additional space until you resize the disk. You can use Cloud Manager to verify if there's additional storage space available for disks: -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click the **Linodes** link in the sidebar to view a list of your Compute Instances. 1. Select a Compute Instance and the **Storage** tab. 1. Compare the total available disk space with the **Size** Column in the **Disks** table. If you have free storage space, you can allocate that space to your existing disks, or create new disks as needed. diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-services/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-services/index.md index 2313ea7c3e9..831cfcfc6c5 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-services/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-services/index.md @@ -88,7 +88,7 @@ sudo ip6tables -L # displays IPv6 rules ``` {{< note >}} -Your deployment may be running FirewallD or UFW, which are frontends used to more easily manage your iptables rules. Run these commands to find out if you are running either package: +Your deployment may be running FirewallD or UFW, which are front ends used to more easily manage your iptables rules. Run these commands to find out if you are running either package: ```command sudo ufw status @@ -206,7 +206,7 @@ df -h ``` {{< note >}} -This reported disk usage is not the same as the reported storage usage in the Cloud Manager. The storage usage in the Cloud Manager refers to how much of the disk space you pay for is allocated to your Compute Instance's disks. The output of `df -h` shows how full those disks are. +This reported disk usage is not the same as the reported storage usage in Cloud Manager. The storage usage in Cloud Manager refers to how much of the disk space you pay for is allocated to your Compute Instance's disks. The output of `df -h` shows how full those disks are. {{< /note >}} You have several options for resolving disk space issues: diff --git a/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md b/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md index 6b7df7c2d21..195b9009cbc 100644 --- a/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md +++ b/docs/products/compute/compute-instances/guides/troubleshooting-ssh-issues/index.md @@ -172,7 +172,7 @@ sudo ip6tables-save # displays IPv6 rules ``` {{< note >}} -Your deployment may be running FirewallD or UFW, which are frontends used to more easily manage your iptables rules. Run these commands to find out if you are running either package: +Your deployment may be running FirewallD or UFW, which are front ends used to more easily manage your iptables rules. Run these commands to find out if you are running either package: ```command sudo ufw status diff --git a/docs/products/compute/compute-instances/plans/choosing-a-plan/index.md b/docs/products/compute/compute-instances/plans/choosing-a-plan/index.md index c8d0b9529f2..cef2e4efc35 100644 --- a/docs/products/compute/compute-instances/plans/choosing-a-plan/index.md +++ b/docs/products/compute/compute-instances/plans/choosing-a-plan/index.md @@ -10,7 +10,7 @@ tags: ["linode platform"] aliases: ['/platform/how-to-choose-a-linode-plan/','/guides/how-to-choose-a-linode-plan/','/guides/choosing-a-compute-instance-plan/'] --- -Linode offers multiple Compute Instance types, each of which can be equipped with various amounts of resources. This allows you to create a Compute Instance tailored to the requirements of your application or workload. For example, some applications may need to store a lot of data but require less processing power. Others may need more memory than CPU. Some may be especially CPU-intensive and require more computing power. +Linode offers multiple Compute Instance types, each of which can be equipped with various amounts of resources. This lets you create a Compute Instance tailored to the requirements of your application or workload. For example, some applications may need to store a lot of data but require less processing power. Others may need more memory than CPU. Some may be especially CPU-intensive and require more computing power. This guide provides you with the information needed to select the most appropriate instance, helping you sort through all of Linode's offerings and land on the right one for the job. diff --git a/docs/products/compute/compute-instances/plans/comparing-shared-and-dedicated-cpus/index.md b/docs/products/compute/compute-instances/plans/comparing-shared-and-dedicated-cpus/index.md index 3ea0c42968a..2a78631b9ff 100644 --- a/docs/products/compute/compute-instances/plans/comparing-shared-and-dedicated-cpus/index.md +++ b/docs/products/compute/compute-instances/plans/comparing-shared-and-dedicated-cpus/index.md @@ -91,9 +91,9 @@ It's important to keep in mind that while some steal won't usually have a notice ## Viewing CPU Usage Graphs -By default, the Cloud Manager will log a history of resource usage and plot CPU data to a graph. We recommend observing CPU usage in the Cloud Manager if you're unsure of upgrading to a Dedicated CPU, because it will have the most amount of data pertaining to the lifetime of your instance. By looking at your CPU graph, you'll be empowered to make a value based judgement on any possible upgrade you may need. +By default, Cloud Manager will log a history of resource usage and plot CPU data to a graph. We recommend observing CPU usage in Cloud Manager if you're unsure of upgrading to a Dedicated CPU, because it will have the most amount of data pertaining to the lifetime of your instance. By looking at your CPU graph, you'll be empowered to make a value based judgement on any possible upgrade you may need. -1. To investigate CPU usage on the Cloud Manager, log in and click on the Linodes sidebar menu. +1. To investigate CPU usage on Cloud Manager, log in and click on the Linodes sidebar menu. 1. Select the instance you'd like to inspect further. @@ -101,7 +101,7 @@ By default, the Cloud Manager will log a history of resource usage and plot CPU Generally, when observing the CPU graph, good candidates for an upgrade to a Dedicated CPU will have high and often relatively steady CPU usage. That being said, this does not necessarily need to be constant and may have high peaks that reflect a possibility for improvement with a Dedicated CPU. -![Dedicated CPU Candidate Graph](cpuusagethrottle.png "Create a Dedicated CPU instance in the Cloud Manager") +![Dedicated CPU Candidate Graph](cpuusagethrottle.png "Create a Dedicated CPU instance in Cloud Manager") ## What If I Need More Specialized Resources? diff --git a/docs/products/compute/compute-instances/plans/dedicated-cpu/index.md b/docs/products/compute/compute-instances/plans/dedicated-cpu/index.md index 6ddc312e490..1be038d5083 100644 --- a/docs/products/compute/compute-instances/plans/dedicated-cpu/index.md +++ b/docs/products/compute/compute-instances/plans/dedicated-cpu/index.md @@ -14,7 +14,7 @@ Dedicated CPU Compute Instances are virtual machines that provide you with dedic ## Dedicated Competition-Free Resources -A Dedicated CPU Compute Instance provides entire vCPU cores accessible only to you. Because the vCPU cores are not shared, no other Compute Instances can utilize them. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This allows you to run workloads that require full-duty work (100% CPU all day, every day) at peak performance. +A Dedicated CPU Compute Instance provides entire vCPU cores accessible only to you. Because the vCPU cores are not shared, no other Compute Instances can utilize them. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This lets you run workloads that require full-duty work (100% CPU all day, every day) at peak performance. ## Upgrading from a Shared CPU Instance diff --git a/docs/products/compute/compute-instances/plans/gpu/index.md b/docs/products/compute/compute-instances/plans/gpu/index.md index f5eb13c624e..b4fe958137a 100644 --- a/docs/products/compute/compute-instances/plans/gpu/index.md +++ b/docs/products/compute/compute-instances/plans/gpu/index.md @@ -25,7 +25,7 @@ If one GPU card isn’t enough for your projected workloads, Akamai Cloud Comput ## Dedicated Competition-Free Resources -A GPU Compute Instance's vCPU cores are dedicated, not shared, and accessible only to you. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This allows you to run workloads that require full-duty work (100% CPU all day, every day) at peak performance. +A GPU Compute Instance's vCPU cores are dedicated, not shared, and accessible only to you. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This lets you run workloads that require full-duty work (100% CPU all day, every day) at peak performance. ## Recommended Workloads @@ -134,7 +134,7 @@ Video Encoding is the process of taking a video file's original source format an ### General Purpose Computing using CUDA -CUDA (Compute Unified Device Architecture) is a parallel computing platform and API that allows you to interact more directly with the GPU for general purpose computing. In practice, this means that a developer can write code in C, C++, or many other supported languages utilizing their GPU to create their own tools and programs. +CUDA (Compute Unified Device Architecture) is a parallel computing platform and API that lets you interact more directly with the GPU for general purpose computing. In practice, this means that a developer can write code in C, C++, or many other supported languages utilizing their GPU to create their own tools and programs. If you're interested in using CUDA on your GPU Compute Instance, see the following resources: diff --git a/docs/products/compute/compute-instances/plans/high-memory/index.md b/docs/products/compute/compute-instances/plans/high-memory/index.md index 8e69a6cb296..a4d7b8a865f 100644 --- a/docs/products/compute/compute-instances/plans/high-memory/index.md +++ b/docs/products/compute/compute-instances/plans/high-memory/index.md @@ -21,7 +21,7 @@ Run queries on large data volumes. High memory Linodes make it possible to proce ## Dedicated Competition-Free Resources -A High Memory Instance provides entire vCPU cores accessible only to you. Because the vCPU cores are not shared, no other Compute Instances can utilize them. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This allows you to run workloads that require full-duty work (100% CPU all day, every day) at peak performance. +A High Memory Instance provides entire vCPU cores accessible only to you. Because the vCPU cores are not shared, no other Compute Instances can utilize them. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This lets you run workloads that require full-duty work (100% CPU all day, every day) at peak performance. ## Recommended Workloads diff --git a/docs/products/compute/compute-instances/plans/premium/index.md b/docs/products/compute/compute-instances/plans/premium/index.md index 90b3d5f78ed..cc07efee0ca 100644 --- a/docs/products/compute/compute-instances/plans/premium/index.md +++ b/docs/products/compute/compute-instances/plans/premium/index.md @@ -20,7 +20,7 @@ The key differentiator for Premium instances is its guaranteed minimum hardware ## Dedicated Competition-Free Resources -CPU cores on a Premium instance are accessible only to that instance (not other instances on the same hardware). Because the vCPU cores are not shared, no other Compute Instances can utilize them. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This allows you to run workloads that require full-duty work (100% CPU all day, every day) at peak performance. +CPU cores on a Premium instance are accessible only to that instance (not other instances on the same hardware). Because the vCPU cores are not shared, no other Compute Instances can utilize them. Your instance never has to wait for another process, enabling your software to run at peak speed and efficiency. This lets you run workloads that require full-duty work (100% CPU all day, every day) at peak performance. ## Recommended Workloads diff --git a/docs/products/compute/kubernetes/_index.md b/docs/products/compute/kubernetes/_index.md index 7a3565ba166..83a2de086b9 100644 --- a/docs/products/compute/kubernetes/_index.md +++ b/docs/products/compute/kubernetes/_index.md @@ -36,4 +36,4 @@ The basic control plane infrastructure on LKE clusters is provided at no additio - Compute Instance plans supported: Dedicated CPU, Shared CPU, High Memory, and Premium CPU (excluding the 512 GB size for both Dedicated CPU and Premium CPU). See the [Pricing](https://www.linode.com/pricing/) page for the compute resources included in each plan. - 40 Gbps inbound network bandwidth - Free inbound network transfer -- Provisioning and management through the [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) \ No newline at end of file +- Provisioning and management through [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) \ No newline at end of file diff --git a/docs/products/compute/kubernetes/developers/index.md b/docs/products/compute/kubernetes/developers/index.md index c9c8c15e5c5..298bfbf55ea 100644 --- a/docs/products/compute/kubernetes/developers/index.md +++ b/docs/products/compute/kubernetes/developers/index.md @@ -16,7 +16,7 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage LKE clusters](/docs/products/tools/cli/guides/linode-kubernetes-engine/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage LKE clusters](/docs/products/tools/cli/guides/linode-kubernetes-engine/). ## Third Party Tools & Integrations diff --git a/docs/products/compute/kubernetes/get-started/index.md b/docs/products/compute/kubernetes/get-started/index.md index 41488fb69f5..a7add9d527b 100644 --- a/docs/products/compute/kubernetes/get-started/index.md +++ b/docs/products/compute/kubernetes/get-started/index.md @@ -53,7 +53,7 @@ Visit the [Kubernetes documentation](https://kubernetes.io/docs/tasks/tools/inst 1. The **Create a Kubernetes Cluster** page appears. At the top of the page, you are required to select the following options: - - In the **Cluster Label** field, provide a name for your cluster. The name must be unique between all of the clusters on your account. This name is how you identify your cluster in the Cloud Manager’s Dashboard. + - In the **Cluster Label** field, provide a name for your cluster. The name must be unique between all of the clusters on your account. This name is how you identify your cluster in Cloud Manager’s Dashboard. - From the **Region** dropdown menu, select the **Region** where you would like your cluster to reside. @@ -63,7 +63,7 @@ Visit the [Kubernetes documentation](https://kubernetes.io/docs/tasks/tools/inst 1. Once you're satisfied with the number of nodes in a node pool, select **Add** to include it in your configuration. If you decide that you need more or fewer hardware resources after you deploy your cluster, you can always [edit your Node Pool](#edit-or-remove-existing-node-pools). -1. Once a pool has been added to your configuration, it is listed in the **Cluster Summary** on the right-hand side of the Cloud Manager detailing your cluster's hardware resources and monthly cost. Additional pools can be added before finalizing the cluster creation process by repeating the previous step for each additional pool. +1. Once a pool has been added to your configuration, it is listed in the **Cluster Summary** on the right-hand side of Cloud Manager detailing your cluster's hardware resources and monthly cost. Additional pools can be added before finalizing the cluster creation process by repeating the previous step for each additional pool. 1. When you are satisfied with the configuration of your cluster, click the **Create Cluster** button on the right hand side of the screen. Your cluster's detail page appears, and your Node Pools are listed on this page. From this page, you can [edit your existing Node Pools](#edit-or-remove-existing-node-pools), [access your Kubeconfig file](#access-and-download-your-kubeconfig), and view an overview of your cluster's resource details. diff --git a/docs/products/compute/kubernetes/guides/create-cluster/index.md b/docs/products/compute/kubernetes/guides/create-cluster/index.md index 91830a858e5..cbe1abc29b5 100644 --- a/docs/products/compute/kubernetes/guides/create-cluster/index.md +++ b/docs/products/compute/kubernetes/guides/create-cluster/index.md @@ -6,9 +6,9 @@ aliases: ['/products/compute/kubernetes/guides/create-lke-cluster/'] tags: ["managed hosting"] --- -This guide walks you through creating an LKE (Linode Kubernetes Engine) cluster through the Cloud Manager. +This guide walks you through creating an LKE (Linode Kubernetes Engine) cluster through Cloud Manager. -1. [Open the Create Kubernetes Cluster Form in the Cloud Manager](#open-the-create-kubernetes-cluster-form-in-the-cloud-manager) +1. [Open the Create Kubernetes Cluster Form in Cloud Manager](#open-the-create-kubernetes-cluster-form-in-cloud-manager) 1. [Set the Label](#set-the-label) 1. [Select a Region](#select-a-region) 1. [Choose a Kubernetes Version](#choose-a-kubernetes-version) @@ -16,13 +16,13 @@ This guide walks you through creating an LKE (Linode Kubernetes Engine) cluster 1. [Optionally Enable High Availability](#optionally-enable-high-availability) 1. [Deploy the Cluster](#deploy-the-cluster) -## Open the Create Kubernetes Cluster Form in the Cloud Manager +## Open the Create Kubernetes Cluster Form in Cloud Manager -Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Kubernetes** from the left navigation menu. Click the **Create Cluster** button. This opens the *[Kubernetes Create Cluster](https://cloud.linode.com/kubernetes/create)* form. +Log in to [Cloud Manager](https://cloud.linode.com/) and select **Kubernetes** from the left navigation menu. Click the **Create Cluster** button. This opens the *[Kubernetes Create Cluster](https://cloud.linode.com/kubernetes/create)* form. ## Set the Label -Within the **Cluster Label** field, enter the label you wish to use. This label allows you to identify it from within the Cloud Manager, Linode CLI, and Linode API. The label must be alphanumeric, between 3 and 32 characters, and unique from other cluster labels on your account. +Within the **Cluster Label** field, enter the label you wish to use. This label lets you identify it from within Cloud Manager, Linode CLI, and Linode API. The label must be alphanumeric, between 3 and 32 characters, and unique from other cluster labels on your account. ## Select a Region diff --git a/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md b/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md index 9165d5e257d..8c0ae49616f 100644 --- a/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md +++ b/docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md @@ -13,7 +13,7 @@ tags: ["kubernetes"] An LKE cluster can be deployed in one of several ways: -- Via the [Cloud Manager](/docs/products/compute/kubernetes/guides/create-cluster/) +- Via [Cloud Manager](/docs/products/compute/kubernetes/guides/create-cluster/) - With the Linode API (as presented in this guide) - With the [Linode CLI](/docs/products/tools/cli/get-started/) @@ -27,7 +27,7 @@ These Linode-provided interfaces can be used to create, delete, and update the s The [Kubernetes API](/docs/guides/beginners-guide-to-kubernetes-part-1-introduction/#kubernetes-api) and [kubectl](/docs/guides/beginners-guide-to-kubernetes-part-1-introduction/#kubectl) are the primary ways you interact with your LKE cluster once it's been created. These tools can be used to configure, deploy, inspect, and secure your Kubernetes workloads, deploy applications, create services, configure storage and networking, and define controllers. {{< note >}} -The Linode API and the Kubernetes API are two separate interfaces, and both are mentioned in this article. The Linode API allows you to manipulate your Linode infrastructure, while the Kubernetes API allows you to manage the software objects running in your cluster. +The Linode API and the Kubernetes API are two separate interfaces, and both are mentioned in this article. The Linode API lets you manipulate your Linode infrastructure, while the Kubernetes API lets you manage the software objects running in your cluster. {{< /note >}} ## In this Guide @@ -169,7 +169,7 @@ To communicate with your LKE cluster, kubectl requires a copy of your cluster's ``` {{< note >}} - You can also access a decoded version of your kubeconfig file in the [Cloud Manager](/docs/products/compute/kubernetes/guides/kubectl/). + You can also access a decoded version of your kubeconfig file in [Cloud Manager](/docs/products/compute/kubernetes/guides/kubectl/). {{< /note >}} 1. View all nodes in your LKE cluster using kubectl: @@ -334,7 +334,7 @@ curl -H "Authorization: Bearer $TOKEN" \ https://api.linode.com/v4/linode/instances/13841932 ``` -Although you have access to your cluster's nodes, it is recommended that you only interact with your nodes via the Linode's LKE interfaces (like the LKE endpoints in Linode's API, or the Kubernetes section in the Cloud Manager), or via the Kubernetes API and kubectl. +Although you have access to your cluster's nodes, it is recommended that you only interact with your nodes via the Linode's LKE interfaces (like the LKE endpoints in Linode's API, or the Kubernetes section in Cloud Manager), or via the Kubernetes API and kubectl. {{< /note >}} ## Modify your LKE Cluster diff --git a/docs/products/compute/kubernetes/guides/high-availability-control-plane/index.md b/docs/products/compute/kubernetes/guides/high-availability-control-plane/index.md index 5aec9c2b30a..586ca759f07 100644 --- a/docs/products/compute/kubernetes/guides/high-availability-control-plane/index.md +++ b/docs/products/compute/kubernetes/guides/high-availability-control-plane/index.md @@ -51,7 +51,7 @@ The upgrade process may take several minutes to complete, as nodes are replaced High Availability can be added to pre-existing clusters at any given time through the cluster's **Summary Page**. -1. To reach the summary page for the cluster, navigate first to the [Kubernetes section of the Cloud Manager](https://cloud.linode.com/kubernetes/clusters). +1. To reach the summary page for the cluster, navigate first to the [Kubernetes section of Cloud Manager](https://cloud.linode.com/kubernetes/clusters). 1. Select the Cluster by label that you would like to enable HA for. The summary page for the cluster appears. diff --git a/docs/products/compute/kubernetes/guides/kubectl/index.md b/docs/products/compute/kubernetes/guides/kubectl/index.md index 605d622bc44..1d43cafb8dd 100644 --- a/docs/products/compute/kubernetes/guides/kubectl/index.md +++ b/docs/products/compute/kubernetes/guides/kubectl/index.md @@ -13,7 +13,7 @@ You need to install the kubectl client to your computer before proceeding. Follo ## Connect to a Cluster with kubectl -After you've created your LKE cluster using the Cloud Manager, you can begin interacting with and managing your cluster. You connect to it using the kubectl client on your computer. To configure kubectl, download your cluster's *kubeconfig* file. +After you've created your LKE cluster using Cloud Manager, you can begin interacting with and managing your cluster. You connect to it using the kubectl client on your computer. To configure kubectl, download your cluster's *kubeconfig* file. ### Access and Download your kubeconfig diff --git a/docs/products/compute/kubernetes/guides/kubernetes-dashboard/index.md b/docs/products/compute/kubernetes/guides/kubernetes-dashboard/index.md index 80dbaa8916d..f93d345822f 100644 --- a/docs/products/compute/kubernetes/guides/kubernetes-dashboard/index.md +++ b/docs/products/compute/kubernetes/guides/kubernetes-dashboard/index.md @@ -17,13 +17,13 @@ While providing an easy way to monitor a Kubernetes cluster and perform health c The Linode Kubernetes Engine currently installs the Kubernetes Dashboard by default, and can be accessed through the [Kubernetes Dashboard Link](#accessing-the-cluster-dashboard) found for each cluster in the Linode Cloud Manager. -This guide will be a step-by-step introduction to accessing the Kubernetes Dashboard on LKE through the unique link found in the Cloud Manager or the Linode API. Additionally information will provide basic insight into navigating the Kubernetes Dashboard, as well as provide an example for creating and editing resources directly through the dashboard. +This guide will be a step-by-step introduction to accessing the Kubernetes Dashboard on LKE through the unique link found in Cloud Manager or the Linode API. Additionally information will provide basic insight into navigating the Kubernetes Dashboard, as well as provide an example for creating and editing resources directly through the dashboard. ## Accessing the Cluster Dashboard -The Cluster Dashboard can be found at the top of the Cluster's [details page](/docs/products/compute/kubernetes/guides/manage-clusters/). The steps for reaching the dashboard from the Cloud Manager are as follows: +The Cluster Dashboard can be found at the top of the Cluster's [details page](/docs/products/compute/kubernetes/guides/manage-clusters/). The steps for reaching the dashboard from Cloud Manager's are as follows: -1. Click the Kubernetes link in the Cloud Manager sidebar menu. The Kubernetes listing page appears and you see all of your clusters listed. +1. Click the Kubernetes link in Cloud Manager's sidebar menu. The Kubernetes listing page appears and you see all of your clusters listed. 1. Select the cluster that you would like to reach the Kubernetes Dashboard for. The Kubernetes cluster’s details page appears. diff --git a/docs/products/compute/kubernetes/guides/load-balancing/index.md b/docs/products/compute/kubernetes/guides/load-balancing/index.md index 9ca042b63ec..8fbe9efb8e9 100644 --- a/docs/products/compute/kubernetes/guides/load-balancing/index.md +++ b/docs/products/compute/kubernetes/guides/load-balancing/index.md @@ -153,7 +153,7 @@ This section describes how to set up TLS termination on your Linode NodeBalancer #### Generating a TLS type Secret -Kubernetes allows you to store sensitive information in a Secret object for use within your cluster. This is useful for storing things like passwords and API tokens. In this section, you will create a Kubernetes secret to store Transport Layer Security (TLS) certificates and keys that you will then use to configure TLS termination on your Linode NodeBalancers. +Kubernetes lets you store sensitive information in a Secret object for use within your cluster. This is useful for storing things like passwords and API tokens. In this section, you will create a Kubernetes secret to store Transport Layer Security (TLS) certificates and keys that you will then use to configure TLS termination on your Linode NodeBalancers. In the context of the Linode CCM, Secrets are useful for storing Transport Layer Security (TLS) certificates and keys. The `linode-loadbalancer-tls` annotation requires TLS certificates and keys to be stored as Kubernetes Secrets with the type `tls`. Follow the steps in this section to create a Kubernetes TLS Secret. @@ -236,7 +236,7 @@ metadata: ### Configuring Session Affinity for Cluster Pods -`kube-proxy` will always attempt to proxy traffic to a random backend Pod. To direct traffic to the same Pod, you can use the `sessionAffinity` mechanism. When set to `clientIP`, `sessionAffinity` will ensure that all traffic from the same IP will be directed to the same Pod. You can add the example lines to a Service configuration file to +`kube-proxy` will always attempt to proxy traffic to a random back-end Pod. To direct traffic to the same Pod, you can use the `sessionAffinity` mechanism. When set to `clientIP`, `sessionAffinity` will ensure that all traffic from the same IP will be directed to the same Pod. You can add the example lines to a Service configuration file to ```file spec: @@ -251,7 +251,7 @@ spec: ## Removing Linode NodeBalancers from your Kubernetes Cluster -To delete a NodeBalancer and the Service that it represents, you can use the Service manifest file you used to create the NodeBalancer. Simply use the `delete` command and supply your file name with the `f` flag: +To delete a NodeBalancer and the Service that it represents, you can use the Service manifest file you used to create the NodeBalancer. Simply use the `delete` command and supply your filename with the `f` flag: ```command kubectl delete -f example-service.yaml diff --git a/docs/products/compute/kubernetes/guides/manage-clusters/index.md b/docs/products/compute/kubernetes/guides/manage-clusters/index.md index ecfc43c7240..a179d71bbd5 100644 --- a/docs/products/compute/kubernetes/guides/manage-clusters/index.md +++ b/docs/products/compute/kubernetes/guides/manage-clusters/index.md @@ -8,7 +8,7 @@ aliases: ['/products/compute/kubernetes/guides/delete-cluster/'] ## View Kubernetes Clusters -Log in to the [Cloud Manager](https://cloud.linode.com) and select Kubernetes from the left menu. If any LKE clusters exist on your account, they are listed on this page. +Log in to [Cloud Manager](https://cloud.linode.com) and select Kubernetes from the left menu. If any LKE clusters exist on your account, they are listed on this page. ![Screenshot of the Kubernetes listing page in Cloud Manager](view-clusters.png) @@ -26,22 +26,22 @@ To create a new Kubernetes cluster within LKE, follow the instructions within th ## Review and Edit a Cluster -Navigate to the **Kubernetes** page in the Cloud Manager and select the cluster you wish to edit. See [View Kubernetes Clusters](#view-kubernetes-clusters). +Navigate to the **Kubernetes** page in Cloud Manager and select the cluster you wish to edit. See [View Kubernetes Clusters](#view-kubernetes-clusters). -![Screenshot of a Kubernetes cluster entry in the Cloud Manager](select-cluster.png) +![Screenshot of a Kubernetes cluster entry in Cloud Manager](select-cluster.png) This displays the details page for the selected cluster. From here, you can view the summary section (which includes the Kubernetes version, region, cost, and combined computing resources) as well as the following details: - **Kubernetes API Endpoint** -- **Kubeconfig:** Download, view, and reset the Kubeconfig configuration file. This file outlines the configuration of your cluster and allows you to connect to it. +- **Kubeconfig:** Download, view, and reset the Kubeconfig configuration file. This file outlines the configuration of your cluster and lets you connect to it. There are also links to view the Kubernetes dashboard, upgrade the cluster to high availability, delete the cluster, and more. From here, you can also add, remove, recycle, and resize node pools (see [Manage Node Pools](/docs/products/compute/kubernetes/guides/manage-node-pools/)). -![Screenshot of a Kubernetes cluster detail page in the Cloud Manager](view-cluster-details-page.png) +![Screenshot of a Kubernetes cluster detail page in Cloud Manager](view-cluster-details-page.png) ## Delete a Cluster -1. Navigate to the **Kubernetes** page in the Cloud Manager and select the cluster you wish to delete. See [View Kubernetes Clusters](#view-kubernetes-clusters). +1. Navigate to the **Kubernetes** page in Cloud Manager and select the cluster you wish to delete. See [View Kubernetes Clusters](#view-kubernetes-clusters). 1. Within the summary and details section, click the **Delete Cluster** button. diff --git a/docs/products/compute/kubernetes/guides/manage-node-pools/index.md b/docs/products/compute/kubernetes/guides/manage-node-pools/index.md index 188519a2b3a..d283a634b0e 100644 --- a/docs/products/compute/kubernetes/guides/manage-node-pools/index.md +++ b/docs/products/compute/kubernetes/guides/manage-node-pools/index.md @@ -11,23 +11,23 @@ This guide covers managing the node pools on your cluster, including adding and ## View Node Pools -1. Log in to the [Cloud Manager](http://cloud.linode.com), click **Kubernetes** in the left menu, and select the cluster you wish to view. See [Manage Kubernetes Clusters](/docs/products/compute/kubernetes/guides/manage-clusters/). +1. Log in to [Cloud Manager](http://cloud.linode.com), click **Kubernetes** in the left menu, and select the cluster you wish to view. See [Manage Kubernetes Clusters](/docs/products/compute/kubernetes/guides/manage-clusters/). 1. Scroll down to the **Node Pools** section. This lists all node pools for your cluster and their associated nodes. - ![Screenshot of the Node Pools section of a cluster in the Cloud Manager](view-node-pools.png) + ![Screenshot of the Node Pools section of a cluster in Cloud Manager](view-node-pools.png) ## Add a Node Pool Additional node pools can be added to host different applications or services within the same Kubernetes cluster. Since each node pool can be assigned its own virtual machine (Compute Instance) plan, separating applications into node pools can boost efficiency and allow each application to only be assigned the resources it needs. -1. Navigate to the **Kubernetes** page in the Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). +1. Navigate to the **Kubernetes** page in Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). 1. Within the **Node Pool** section, click the **Add a Node Pool** button. 1. In the side panel that opens, locate the plan type you wish to use for your first node pool. Currently, the available plan types for LKE worker nodes include [Shared CPU](/docs/products/compute/compute-instances/plans/choosing-a-plan/#shared-cpu-instances), [Dedicated CPU](/docs/products/compute/compute-instances/plans/choosing-a-plan/#dedicated-cpu-instances), and [High Memory](/docs/products/compute/compute-instances/plans/choosing-a-plan/#high-memory-instances). 1 GB Shared CPU Compute Instances Nanodes (also known as *nanodes*) are not available. - ![Screenshot of the Add Node Pool panel in the Cloud Manager](add-node-pool.png) + ![Screenshot of the Add Node Pool panel in Cloud Manager](add-node-pool.png) 1. In the corresponding field, enter the number of worker nodes that you wish to be included in the node pool. @@ -37,13 +37,13 @@ Additional node pools can be added to host different applications or services wi Node pools can be resized manually or automatically (through auto-scaling). Both of these processes allow you to increase or decrease the *number of worker nodes*. The instructions below cover manually resizing a pool. -1. Navigate to the **Kubernetes** page in the Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). +1. Navigate to the **Kubernetes** page in Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). 1. Within the **Node Pool** section, locate the node pool you wish to resize and click the **Resize Pool** button. 1. In the side panel that opens, enter the new number of nodes you wish to have in the pool. As the number is adjusted, the total cost of your new resources are displayed. To accept these changes, select the `Save Changes` button to continue. - ![Screenshot of the resize node pool panel in the Cloud Manager](resize-node-pool.png) + ![Screenshot of the resize node pool panel in Cloud Manager](resize-node-pool.png) {{< note type="warning" >}} Shrinking a node pool results in the deletion of some associated Compute Instances. Any local storage on these instances (such as `hostPath` and `emptyDir` volumes, or "local" PersistentVolumes) is erased. @@ -57,7 +57,7 @@ Many production applications benefit from increasing or decreasing infrastructur - If Pods are able to be scheduled on less nodes than are currently available in the node pool, nodes are drained and removed automatically. Pods on drained nodes are immediately rescheduled on pre-existing nodes. -1. Navigate to the **Kubernetes** page in the Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). +1. Navigate to the **Kubernetes** page in Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). 1. Within the **Node Pool** section, locate the node pool you wish to modify and click the **Autoscale Pool** button. A popup form appears with settings for autoscaling the node pool. @@ -81,7 +81,7 @@ The LKE Autoscaler will not automatically increase or decrease the size of the n Recycling a worker node deletes the corresponding Compute Instance and deploys a new one. This is used when upgrading minor versions of Kubernetes or when debugging a node. You can recycle an individual node, recycle all nodes in a node pool, or recycle all nodes within a cluster. When recycling multiple nodes, each node is recycled on a rolling basis so that only a single node is down at any time. -1. Navigate to the **Kubernetes** page in the Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). +1. Navigate to the **Kubernetes** page in Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). 1. Within the **Node Pool** section, select the button corresponding with the recycle operation you wish to perform: @@ -101,7 +101,7 @@ Recycling a worker node deletes the corresponding Compute Instance and deploys a If you no longer need to use a node pool, you can remove it from the cluster. This deletes all corresponding Compute Instance. If you instead wish to decrease the number of nodes in a node pool, see [Resize a Node Pool](#resize-a-node-pool) -1. Navigate to the **Kubernetes** page in the Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). +1. Navigate to the **Kubernetes** page in Cloud Manager and select the cluster you wish to edit. See [View Node Pools](#view-node-pools). 1. Within the **Node Pool** section, locate the node pool you wish to delete and click the **Delete Pool** button. diff --git a/docs/products/compute/kubernetes/guides/rotate-kubernetes-secrets/index.md b/docs/products/compute/kubernetes/guides/rotate-kubernetes-secrets/index.md index 47132b6ca81..148b816f016 100644 --- a/docs/products/compute/kubernetes/guides/rotate-kubernetes-secrets/index.md +++ b/docs/products/compute/kubernetes/guides/rotate-kubernetes-secrets/index.md @@ -86,7 +86,7 @@ In order to expedite secret recreation after deletion and regain access to your ``` {{< /note >}} -1. If you choose to download your new kubeconfig via the Cloud Manager, you will need to reconfigure your kubeconfig by saving the file path to your `$KUBECONFIG` environment variable. Replace {{< placeholder "~/Downloads/kubeconfig.yaml" >}} with the file path for your new kubeconfig file: +1. If you choose to download your new kubeconfig via Cloud Manager, you will need to reconfigure your kubeconfig by saving the file path to your `$KUBECONFIG` environment variable. Replace {{< placeholder "~/Downloads/kubeconfig.yaml" >}} with the file path for your new kubeconfig file: ```command export KUBECONFIG={{< placeholder "~/Downloads/kubeconfig.yaml" >}} diff --git a/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md b/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md index fb3e3ebdcef..4845102e304 100644 --- a/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md +++ b/docs/products/compute/kubernetes/guides/upgrade-kubernetes-version/index.md @@ -28,7 +28,7 @@ When a Kubernetes version upgrade is initiated on an LKE cluster (including both After the initial upgrade, existing worker nodes need to also be upgraded to the newer Kubernetes version. This typically requires a few extra steps. This guide outlines three options for upgrading these existing nodes, including recycling all worker nodes, performing an in-place upgrade, and performing an out-of-place upgrade. Each of these options is discussed in the [Upgrade Worker Nodes](#upgrade-worker-nodes) section. {{< note type="warning">}} -Existing worker nodes are *automatically upgraded* when initiating the upgrade in the Cloud Manager if **Recycle All Nodes** is selected during the upgrade process. This can also be triggered manually by using the recycle all nodes feature in the Cloud Manager, Linode CLI, and Linode API. This recycles all nodes on a rolling basis so that only a single node is down at any time. Since this means there is one less worker node during the upgrade process, it can affect performance and might not be preferred for production applications. +Existing worker nodes are *automatically upgraded* when initiating the upgrade in Cloud Manager if **Recycle All Nodes** is selected during the upgrade process. This can also be triggered manually by using the recycle all nodes feature in Cloud Manager, Linode CLI, and Linode API. This recycles all nodes on a rolling basis so that only a single node is down at any time. Since this means there is one less worker node during the upgrade process, it can affect performance and might not be preferred for production applications. It is strongly recommended that steps are taken to ensure that there is enough space on all nodes to accommodate for this temporary shift in resources. If a cluster of three nodes cannot briefly support the resources demands of an application using only two nodes, then the upgrade process may result in unintended application downtime. To overcome this, you can temporarily add additional worker nodes and perform either an *in-place* or *out-of-place* upgrade to avoid any performance impact. For more details on these approaches, see [Upgrade Worker Nodes](#upgrade-worker-nodes). {{< /note >}} @@ -59,7 +59,7 @@ One way to identify breaking changes and compatibility issues with Kubernetes up {{< tabs >}} {{< tab "Cloud Manager" >}} -Navigate to the **Kubernetes** page in the [Cloud Manager](http://cloud.linode.com) to see a list of all LKE clusters on your account (see [Manage Kubernetes Clusters](/docs/products/compute/kubernetes/guides/manage-clusters/)). +Navigate to the **Kubernetes** page in [Cloud Manager](http://cloud.linode.com) to see a list of all LKE clusters on your account (see [Manage Kubernetes Clusters](/docs/products/compute/kubernetes/guides/manage-clusters/)). ![Check Kubernetes Version](lke-version.png) @@ -132,7 +132,7 @@ Once you are ready to perform an upgrade, you can start the upgrade process. Thi {{< tabs >}} {{< tab "Cloud Manager" >}} -1. Navigate to the **Kubernetes** page in the [Cloud Manager](http://cloud.linode.com) to see a list of all LKE clusters on your account (see [Manage Kubernetes Clusters](/docs/products/compute/kubernetes/guides/manage-clusters/)). +1. Navigate to the **Kubernetes** page in [Cloud Manager](http://cloud.linode.com) to see a list of all LKE clusters on your account (see [Manage Kubernetes Clusters](/docs/products/compute/kubernetes/guides/manage-clusters/)). 1. Locate the cluster you wish to upgrade and click the corresponding **Upgrade** button in the *Version* column. This button only appears if there is an available upgrade for that cluster. @@ -259,7 +259,7 @@ This recycles each worker node on a rolling basis so that only one node is down {{< tabs >}} {{< tab "Cloud Manager" >}} -On the details page of your LKE cluster in the Cloud Manager, click the **Recycle All Nodes** button. See [Recycle Nodes](/docs/products/compute/kubernetes/guides/manage-node-pools/#recycle-nodes) for more details. +On the details page of your LKE cluster in Cloud Manager, click the **Recycle All Nodes** button. See [Recycle Nodes](/docs/products/compute/kubernetes/guides/manage-node-pools/#recycle-nodes) for more details. {{< /tab >}} {{< tab "Linode CLI" >}} Run the command below, replacing *[cluster-id]* with the ID of your cluster. @@ -292,7 +292,7 @@ For more details, review the API request sample on the [Cluster Nodes Recycle AP {{< tabs >}} {{< tab "Cloud Manager" >}} - Locate the node pool on the details page of your LKE cluster in the Cloud Manager. Click the corresponding **Resize Pool** button. Increase the size of the node pool by 1. For example, if you have 3 nodes in the pool, increase that value to 4. For additional instructions, see [Resize a Node Pool](/docs/products/compute/kubernetes/guides/manage-node-pools/#resize-a-node-pool). + Locate the node pool on the details page of your LKE cluster in Cloud Manager. Click the corresponding **Resize Pool** button. Increase the size of the node pool by 1. For example, if you have 3 nodes in the pool, increase that value to 4. For additional instructions, see [Resize a Node Pool](/docs/products/compute/kubernetes/guides/manage-node-pools/#resize-a-node-pool). If you are also using the autoscale feature, increase the minimum and maximum nodes by 1. This can be done by clicking the corresponding **Autoscale Pool** button and adjusting the minimum and maximum values. For more details, see [Autoscale](/docs/products/compute/kubernetes/guides/manage-node-pools/#autoscale-automatically-resize-node-pools). {{< /tab >}} @@ -359,7 +359,7 @@ For more details, review the API request sample on the [Cluster Nodes Recycle AP {{< tabs >}} {{< tab "Cloud Manager" >}} - Locate the node pool on the details page of your LKE cluster in the Cloud Manager. Next to the node that has just been drained, click the corresponding **Recycle** button as outlined in [Recycle Nodes](/docs/products/compute/kubernetes/guides/manage-node-pools/#recycle-nodes). + Locate the node pool on the details page of your LKE cluster in Cloud Manager. Next to the node that has just been drained, click the corresponding **Recycle** button as outlined in [Recycle Nodes](/docs/products/compute/kubernetes/guides/manage-node-pools/#recycle-nodes). {{< /tab >}} {{< tab "Linode CLI" >}} Run the command below, replacing *[cluster-id]* with the ID of your cluster and *[node-id]* with the ID of the node. @@ -386,7 +386,7 @@ For more details, review the API request sample on the [Cluster Nodes Recycle AP 1. Repeat steps 2 through 4 for each worker node until *all but the last* worker nodes are using the newer Kubernetes version. For the last worker node, repeat steps 2 and 3 to cordon and drain that node - but do not recycle it as that will cause workloads to land back on that node. Instead, continue with the step below to delete it. -1. Remove the additional worker node that was added during this upgrade process. This can be accomplished by resizing your cluster back to your original value to use one less worker node. The last worker node that was created, which was the one you have not yet recycled, is removed during the resize. Then, if you previously adjusted the Autoscale Pool, adjust the values back to what they were prior to the upgrade. +1. Remove the additional worker node that was added during this upgrade process. This can be accomplished by resizing your cluster back to your original value to use one less worker node. The last worker node that was created, which was the one you have not yet recycled, is removed during the resize. Then, if you previously adjusted the Autoscale Pool, adjust the values back to what they were before the upgrade. {{< tabs >}} {{< tab "Cloud Manager" >}} @@ -444,14 +444,14 @@ For more details, review the API request sample on the [Cluster Nodes Recycle AP *This process temporarily creates an additional node pool (with multiple worker nodes). This minimizes the time the upgrade may take (compared with an in-place upgrade) but increases the cost impact. This is recommended for larger production applications.* {{< note >}} -These instructions cover deleting the old node pool after all nodes have been fully drained. This allows you to fallback to the existing nodes should the need arise. Alternatively, you can delete each node after it has been successfully drained, which reduces the overall cost impact of the upgrade. +These instructions cover deleting the old node pool after all nodes have been fully drained. This lets you fallback to the existing nodes should the need arise. Alternatively, you can delete each node after it has been successfully drained, which reduces the overall cost impact of the upgrade. {{< /note >}} 1. Create a new pool with the same Compute Instance plans and number of nodes as your existing pool. {{< tabs >}} {{< tab "Cloud Manager" >}} - Within the **Node Pools** section on the details page of your LKE cluster in the Cloud Manager, click the **Add a Node Pool** button. In the prompt that appears, enter the plan type, plan size, and the number of nodes to match the existing node pool. See [Add a Node Pool](/docs/products/compute/kubernetes/guides/manage-node-pools/#add-a-node-pool). + Within the **Node Pools** section on the details page of your LKE cluster in Cloud Manager, click the **Add a Node Pool** button. In the prompt that appears, enter the plan type, plan size, and the number of nodes to match the existing node pool. See [Add a Node Pool](/docs/products/compute/kubernetes/guides/manage-node-pools/#add-a-node-pool). {{< /tab >}} {{< tab "Linode CLI" >}} Run the command below, replacing the following values as needed. If you are not using the autoscale feature, remove the last 3 options (starting with *autoscaler*) from the command. @@ -518,7 +518,7 @@ These instructions cover deleting the old node pool after all nodes have been fu {{< tabs >}} {{< tab "Cloud Manager" >}} - Locate the original node pool on the details page of your LKE cluster in the Cloud Manager. Click the corresponding **Delete Pool** button as outlined in [Remove a Node Pool](/docs/products/compute/kubernetes/guides/manage-node-pools/#remove-a-node-pool). + Locate the original node pool on the details page of your LKE cluster in Cloud Manager. Click the corresponding **Delete Pool** button as outlined in [Remove a Node Pool](/docs/products/compute/kubernetes/guides/manage-node-pools/#remove-a-node-pool). {{< /tab >}} {{< tab "Linode CLI" >}} Run the command below, replacing *[cluster-id]* with the ID of your cluster and *[pool-id]* with the ID of the original node pool. diff --git a/docs/products/databases/managed-databases/_index.md b/docs/products/databases/managed-databases/_index.md index 6d2b642b476..35b46cfb767 100644 --- a/docs/products/databases/managed-databases/_index.md +++ b/docs/products/databases/managed-databases/_index.md @@ -44,7 +44,7 @@ See [Choosing a Database Engine and Plan](/docs/products/databases/managed-datab ## Recommended Workloads -- Any production application that utilizes a database, especially one with high-traffic or one that stores critical data. +- Any production application that uses a database, especially one with high-traffic or one that stores critical data. - Medium to high traffic websites using WordPress, CraftCMS, Drupal, or other database-enabled application. - E-commerce sites - Organizations that don't want to commit IT resources towards managing a database cluster. @@ -81,7 +81,7 @@ In addition to the resources allocated to each available plan (outlined above), - 100% SSD (Solid State Disk) storage - 40 Gbps inbound network bandwidth - Free inbound network transfer -- Provisioning and management through the [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) +- Provisioning and management through [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) ## Limits and Considerations diff --git a/docs/products/databases/managed-databases/developers/index.md b/docs/products/databases/managed-databases/developers/index.md index 75fdbe4f4a4..af5915839e3 100644 --- a/docs/products/databases/managed-databases/developers/index.md +++ b/docs/products/databases/managed-databases/developers/index.md @@ -15,4 +15,4 @@ Linode’s API v4 provides the ability to programmatically manage the full range ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to [use and install the Linode CLI](/docs/products/tools/cli/get-started/) to get started. \ No newline at end of file +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to [use and install the Linode CLI](/docs/products/tools/cli/get-started/) to get started. \ No newline at end of file diff --git a/docs/products/databases/managed-databases/get-started/index.md b/docs/products/databases/managed-databases/get-started/index.md index 13d067a8527..fa89f0d81dc 100644 --- a/docs/products/databases/managed-databases/get-started/index.md +++ b/docs/products/databases/managed-databases/get-started/index.md @@ -13,7 +13,7 @@ Linode's Managed Database service is a convenient and reliable way to host your ## Create a Managed Database -A Managed Database can be deployed using the Cloud Manager, the Linode API, or the Linode CLI. For instructions on deploying it through the Cloud Manager, see the following guide: +A Managed Database can be deployed using Cloud Manager, the Linode API, or the Linode CLI. For instructions on deploying it through Cloud Manager, see the following guide: - [Create a Managed Database](/docs/products/databases/managed-databases/guides/create-database/) - [Choosing a Database Engine and Plan](/docs/products/databases/managed-databases/guides/database-engines/) @@ -32,4 +32,4 @@ If you are replacing an existing database with Linode's Managed Database service ## Integrate the Database into an Application -While its possible to add data directly to a database using CLI or GUI tools, it's much more common to integrate the database into an existing application. For instance, you can use the database with any web stack that utilizes your chosen database engine (DBMS) such as [LEMP](/docs/guides/web-servers/lemp/) / [LAMP](/docs/guides/web-servers/lamp/) for MySQL and MERN / [MEAN](/docs/guides/mean-stack-tutorial/) for MongoDB. When using a Managed Database, you can forgo installing the database locally on the system and instead use the credentials and connection details for your Managed Database. The instructions for connecting to a remote database vary by application. For example, here's a guide for WordPress: [Configure WordPress to use a Remote Database](/docs/guides/configure-wordpress-remote-database/). \ No newline at end of file +While its possible to add data directly to a database using CLI or GUI tools, it's much more common to integrate the database into an existing application. For instance, you can use the database with any web stack that uses your chosen database engine (DBMS) such as [LEMP](/docs/guides/web-servers/lemp/) / [LAMP](/docs/guides/web-servers/lamp/) for MySQL and MERN / [MEAN](/docs/guides/mean-stack-tutorial/) for MongoDB. When using a Managed Database, you can forgo installing the database locally on the system and instead use the credentials and connection details for your Managed Database. The instructions for connecting to a remote database vary by application. For example, here's a guide for WordPress: [Configure WordPress to use a Remote Database](/docs/guides/configure-wordpress-remote-database/). \ No newline at end of file diff --git a/docs/products/databases/managed-databases/guides/create-database/index.md b/docs/products/databases/managed-databases/guides/create-database/index.md index eb436519ea3..6e24b07cbd8 100644 --- a/docs/products/databases/managed-databases/guides/create-database/index.md +++ b/docs/products/databases/managed-databases/guides/create-database/index.md @@ -1,15 +1,15 @@ --- title: "Create a Managed Database" -description: "A walkthough on creating a Managed Database through the Cloud Manager" +description: "A walkthough on creating a Managed Database through Cloud Manager" published: 2022-06-06 modified: 2022-08-09 --- {{% content "dbass-eos" %}} -This guide walks you through creating a Linode Managed Database through the Cloud Manager. +This guide walks you through creating a Linode Managed Database through Cloud Manager. -1. [Open the Create Database Cluster Form in the Cloud Manager](#open-the-create-database-cluster-form-in-the-cloud-manager) +1. [Open the Create Database Cluster Form in Cloud Manager](#open-the-create-database-cluster-form-in-cloud-manager) 1. [Set the Label](#set-the-label) 1. [Select the Database Engine](#select-the-database-engine) 1. [Select a Region](#select-a-region) @@ -18,9 +18,9 @@ This guide walks you through creating a Linode Managed Database through the Clou 1. [Add Access Controls](#add-access-controls) 1. [Deploy the Managed Database](#deploy-the-managed-database) -## Open the Create Database Cluster Form in the Cloud Manager +## Open the Create Database Cluster Form in Cloud Manager -Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. Click the **Create Database Cluster** button. This opens the *[Create Database Cluster](https://cloud.linode.com/databases/create)* page. +Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. Click the **Create Database Cluster** button. This opens the *[Create Database Cluster](https://cloud.linode.com/databases/create)* page. ## Set the Label @@ -67,4 +67,4 @@ If you are testing the connection from your local machine, you may also wish to ## Deploy the Managed Database -Once you have completed the form, click the **Create Database Cluster** button to start deploying your new database cluster. It takes approximately 15 to 30 minutes to fully provision the cluster. You can track the status by reviewing the *Status* column within the list of [Database Clusters](https://cloud.linode.com/databases) in the Cloud Manager. \ No newline at end of file +Once you have completed the form, click the **Create Database Cluster** button to start deploying your new database cluster. It takes approximately 15 to 30 minutes to fully provision the cluster. You can track the status by reviewing the *Status* column within the list of [Database Clusters](https://cloud.linode.com/databases) in Cloud Manager. \ No newline at end of file diff --git a/docs/products/databases/managed-databases/guides/manage-access-controls/index.md b/docs/products/databases/managed-databases/guides/manage-access-controls/index.md index 3f57ab6e86d..0790b9c5de9 100644 --- a/docs/products/databases/managed-databases/guides/manage-access-controls/index.md +++ b/docs/products/databases/managed-databases/guides/manage-access-controls/index.md @@ -9,7 +9,7 @@ Each Managed Database cluster has its own access control list, which allows spec ## View Access Controls -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select your Managed Database from the list. This opens the detail page for that database cluster. diff --git a/docs/products/databases/managed-databases/guides/manage-backups/index.md b/docs/products/databases/managed-databases/guides/manage-backups/index.md index 6bd2fa49a64..2567db4ad35 100644 --- a/docs/products/databases/managed-databases/guides/manage-backups/index.md +++ b/docs/products/databases/managed-databases/guides/manage-backups/index.md @@ -11,13 +11,13 @@ Each Managed Database includes daily backups of your data, taken on a 24 hour ca ## View Managed Backups -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select your Managed Database from the list. This opens the detail page for that database cluster. 1. Navigate to the **Backups** tab. A list of your available backups are displayed, organized by the date they were created. -![Screenshot of all available managed backups in the Cloud Manager](available-managed-backups.png) +![Screenshot of all available managed backups in Cloud Manager](available-managed-backups.png) ## Restore Managed Backups diff --git a/docs/products/databases/managed-databases/guides/mongodb-connect/index.md b/docs/products/databases/managed-databases/guides/mongodb-connect/index.md index 101d4f40593..d60854afce5 100644 --- a/docs/products/databases/managed-databases/guides/mongodb-connect/index.md +++ b/docs/products/databases/managed-databases/guides/mongodb-connect/index.md @@ -13,7 +13,7 @@ To connect to a MongoDB Managed Database, you need to know a few important detai ## View Connection Details -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select your Managed Database from the list. This opens the detail page for that database cluster. @@ -26,7 +26,7 @@ The *Connection Details* section contains information and credentials needed for - **Replica set:** The name of the replica set. This is only relevant for multi-node high availability clusters and does not appear for standalone (single node) databases. - **SSL:** This field is set to `ENABLED`, which means that it is required to use an encrypted TLS/SSL connection. -Under the *Connection Details* section, there is a **Download CA Certificate** link, which allows you to download the CA (Certificate Authority) certificate. This certificate file can be used if you wish to verify the CA certificate when connecting to the database. +Under the *Connection Details* section, there is a **Download CA Certificate** link, which lets you download the CA (Certificate Authority) certificate. This certificate file can be used if you wish to verify the CA certificate when connecting to the database. ## Connect Using the MongoDB Shell (CLI) diff --git a/docs/products/databases/managed-databases/guides/mysql-connect/index.md b/docs/products/databases/managed-databases/guides/mysql-connect/index.md index 8c2fb8159d5..1913e04c337 100644 --- a/docs/products/databases/managed-databases/guides/mysql-connect/index.md +++ b/docs/products/databases/managed-databases/guides/mysql-connect/index.md @@ -11,7 +11,7 @@ To connect to a MySQL Managed Database, you need to know a few important details ## View Connection Details -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select your Managed Database from the list. This opens the detail page for that database cluster. @@ -24,7 +24,7 @@ The *Connection Details* section contains information and credentials needed for - **Port:** The default port for your database is `3306`. - **SSL:** This field is set to `ENABLED`, which means that it is required to use an encrypted TLS/SSL connection. -Under the *Connection Details* section, there is a **Download CA Certificate** link, which allows you to download the CA (Certificate Authority) certificate. This certificate file can be used if you wish to verify the CA certificate when connecting to the database. +Under the *Connection Details* section, there is a **Download CA Certificate** link, which lets you download the CA (Certificate Authority) certificate. This certificate file can be used if you wish to verify the CA certificate when connecting to the database. ## Connect Using MySQL (CLI) @@ -74,7 +74,7 @@ The MySQL Workbench provides a graphical interface for connecting to MySQL datab ![The Parameters tab in MySQL Workbench](mysql-workbench-connection-parameters.png) -1. Under the *SSL* tab, set **Use SSL** to *Require*. You may also use *Required and Verify CA* if you wish to verify the CA (Certificate Authority) certificate each time you connect. If you choose this option, download the CA certificate from the Cloud Manager and set the **SSL CA File** field to point to that downloaded file. +1. Under the *SSL* tab, set **Use SSL** to *Require*. You may also use *Required and Verify CA* if you wish to verify the CA (Certificate Authority) certificate each time you connect. If you choose this option, download the CA certificate from Cloud Manager and set the **SSL CA File** field to point to that downloaded file. ![The SSL tab in MySQL Workbench](mysql-workbench-connection-ssl.png) diff --git a/docs/products/databases/managed-databases/guides/postgresql-connect/index.md b/docs/products/databases/managed-databases/guides/postgresql-connect/index.md index 512487e932a..0eac69d8b20 100644 --- a/docs/products/databases/managed-databases/guides/postgresql-connect/index.md +++ b/docs/products/databases/managed-databases/guides/postgresql-connect/index.md @@ -11,7 +11,7 @@ To connect to a PostgreSQL Managed Database, you need to know a few important de ## View Connection Details -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select your PostgreSQL Managed Database from the list. This opens the detail page for that database cluster. @@ -27,7 +27,7 @@ The *Connection Details* section contains information and credentials needed for - **Port:** The default port for your database is `5432`. - **SSL:** This field is set to `ENABLED`, which means that it is required to use an encrypted TLS/SSL connection. -Under the *Connection Details* section, there is a **Download CA Certificate** link, which allows you to download the CA (Certificate Authority) certificate. This certificate file can be used if you wish to verify the CA certificate when connecting to the database. +Under the *Connection Details* section, there is a **Download CA Certificate** link, which lets you download the CA (Certificate Authority) certificate. This certificate file can be used if you wish to verify the CA certificate when connecting to the database. ## Connect Using psql (CLI) @@ -96,7 +96,7 @@ pgAdmin is an open-source application that provides you with a graphical interfa 1. Download and install pgAdmin from the [pgAdmin Downloads](https://www.pgadmin.org/download/) page, making sure to select the appropriate file for your local operating system. -1. The first time the application runs, you are prompted to configure a master password that is used to unlock any saved passwords for database servers you may configure. +1. The first time the application runs, you are prompted to configure a primary password (also called *master password*) that is used to unlock any saved passwords for database servers you may configure. 1. Next, you are prompted to register a server (configuring a connection to a server). If you do not see this screen, click Object > Register > Server from the main menu. @@ -108,7 +108,7 @@ pgAdmin is an open-source application that provides you with a graphical interfa ![Screenshot of the Connection tab within the Register Server form](pgadmin-register-server-connection.png) -1. Under the *SSL* tab, you can leave **SSL Mode** as *Prefer* or explicitly set it to *Require*. You may also set it to *Verify-CA* if you wish to verify the CA (Certificate Authority) certificate each time you connect. If you choose this option, download the CA certificate from the Cloud Manager and set the **Root Certificate** field to point to that downloaded file. +1. Under the *SSL* tab, you can leave **SSL Mode** as *Prefer* or explicitly set it to *Require*. You may also set it to *Verify-CA* if you wish to verify the CA (Certificate Authority) certificate each time you connect. If you choose this option, download the CA certificate from Cloud Manager and set the **Root Certificate** field to point to that downloaded file. 1. Once all the settings have been appropriately configured, click the **Save** button to save the settings and attempt to connect. diff --git a/docs/products/databases/managed-databases/guides/postgresql-migrate/index.md b/docs/products/databases/managed-databases/guides/postgresql-migrate/index.md index 256fb672969..ac3ae0ce078 100644 --- a/docs/products/databases/managed-databases/guides/postgresql-migrate/index.md +++ b/docs/products/databases/managed-databases/guides/postgresql-migrate/index.md @@ -63,7 +63,7 @@ Once you've successfully backed up the source database, you can import your data ``` {{< note type="alert" >}} - Using `DROP DATABASE` command results in the deletion of any data stored on that database. If you are replacing an existing database and would like to avoid data loss, make sure you have a backup containing any data you would like to retain prior to running the command. + Using `DROP DATABASE` command results in the deletion of any data stored on that database. If you are replacing an existing database and would like to avoid data loss, make sure you have a backup containing any data you would like to retain before running the command. {{< /note >}} 1. **Import your database file** to your newly created database. diff --git a/docs/products/databases/managed-databases/guides/reset-root-password/index.md b/docs/products/databases/managed-databases/guides/reset-root-password/index.md index 071cc842dac..564e8d8d728 100644 --- a/docs/products/databases/managed-databases/guides/reset-root-password/index.md +++ b/docs/products/databases/managed-databases/guides/reset-root-password/index.md @@ -5,13 +5,13 @@ description: "Learn how to reset the root password on a Linode Managed Database. {{% content "dbass-eos" %}} -If you need to reset the root password on your Managed Database, you can do so through the Cloud Manager. This process assigns a new randomly generated password to the `linroot` user. This is helpful when someone should no longer have access to that user or if you believe your password may have been compromised. +If you need to reset the root password on your Managed Database, you can do so through Cloud Manager. This process assigns a new randomly generated password to the `linroot` user. This is helpful when someone should no longer have access to that user or if you believe your password may have been compromised. {{< note type="alert" >}} Resetting the root password will prevent you from restoring all previously taken backups. Ensure that you have offsite backups available if needed. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select your Managed Database from the list. This opens the detail page for that database cluster. diff --git a/docs/products/databases/managed-databases/guides/updates-and-maintenance/index.md b/docs/products/databases/managed-databases/guides/updates-and-maintenance/index.md index 00f0ad9b3b9..6a9e8410026 100644 --- a/docs/products/databases/managed-databases/guides/updates-and-maintenance/index.md +++ b/docs/products/databases/managed-databases/guides/updates-and-maintenance/index.md @@ -1,6 +1,6 @@ --- title: "Automatic Updates and Maintenance Windows" -description: "Managed databases are automatically updated on a weekly or monthly basis. Learn how to manage these maintenance windows in the Cloud Manager" +description: "Managed databases are automatically updated on a weekly or monthly basis. Learn how to manage these maintenance windows in Cloud Manager" modified: 2023-02-10 date: 2022-04-15 --- @@ -19,7 +19,7 @@ If your database cluster is configured with a single node, the cluster will expe ## View and Modify the Maintenance Window -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select your Managed Database from the list. This opens the detail page for that database cluster. @@ -27,7 +27,7 @@ If your database cluster is configured with a single node, the cluster will expe 1. In the *Maintenance Window* section, you can view the day of the week the maintenance occurs, the time of day it starts, and if maintenance is performed on a weekly or monthly basis. - ![Screenshot of the Maintenance Window in the Cloud Manager](maintenance-window.png) + ![Screenshot of the Maintenance Window in Cloud Manager](maintenance-window.png) - **Day of Week:** The day of the week that the maintenance will occur. The default is *Sunday*. - **Time of Day (UTC):** The time of day (in UTC) the maintenance window will start. The default is *20:00 UTC (8 PM)*. The maintenance window lasts for 3 hours. diff --git a/docs/products/databases/managed-databases/guides/upscale-database/index.md b/docs/products/databases/managed-databases/guides/upscale-database/index.md index ddf3d4a983e..c66953b7a5b 100644 --- a/docs/products/databases/managed-databases/guides/upscale-database/index.md +++ b/docs/products/databases/managed-databases/guides/upscale-database/index.md @@ -13,7 +13,7 @@ This operation causes downtime for the resized node clusters. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Databases** from the left navigation menu. 1. Select a database cluster from the list. diff --git a/docs/products/databases/managed-databases/guides/use-cases/index.md b/docs/products/databases/managed-databases/guides/use-cases/index.md index a215c3a42b6..5f007d50ed8 100644 --- a/docs/products/databases/managed-databases/guides/use-cases/index.md +++ b/docs/products/databases/managed-databases/guides/use-cases/index.md @@ -9,11 +9,11 @@ Managed Databases is Linode's own Database-as-a-Service (DBaaS) platform. These ## Cost Reduction -Hosting your own database on-premise (or on your own custom cloud architecture) can require you to dedicate a significant budget and lots of IT resources towards its implementation and operation. Offloading this to a dedicated DBaaS solution like Managed Databases has the potential to significantly lower the cost and reduce the complexity. This allows you to focus on your business - not your computing infrastructure. +Hosting your own database on-premise (or on your own custom cloud architecture) can require you to dedicate a significant budget and lots of IT resources towards its implementation and operation. Offloading this to a dedicated DBaaS solution like Managed Databases has the potential to significantly lower the cost and reduce the complexity. This lets you focus on your business - not your computing infrastructure. ## Rapid Deployment -It's often necessary to create short-lived databases quickly and securely. You may want to do this for development, disaster recovery (discussed below), ephemeral applications, traffic management, and much more. Managed Databases makes this process incredibly efficient, allowing you to create databases quickly using the Cloud Manager or programmatically through the Linode API. +It's often necessary to create short-lived databases quickly and securely. You may want to do this for development, disaster recovery (discussed below), ephemeral applications, traffic management, and much more. Managed Databases makes this process incredibly efficient, allowing you to create databases quickly using Cloud Manager or programmatically through the Linode API. ## Disaster Recovery diff --git a/docs/products/networking/cloud-firewall/_index.md b/docs/products/networking/cloud-firewall/_index.md index b81ddcfabfc..1ed089318d3 100644 --- a/docs/products/networking/cloud-firewall/_index.md +++ b/docs/products/networking/cloud-firewall/_index.md @@ -37,7 +37,7 @@ Cloud Firewalls are available at no charge across [all regions](https://www.lino - Cloud Firewalls are **compatible with Linode Compute Instances and NodeBalancers**. They are not currently directly supported on other Linode services, such as Object Storage. - A Cloud Firewall can be attached to multiple services (Compute Instances or NodeBalancers), but a service can only be attached to one *active* (enabled) Cloud Firewall at a time. - A Cloud Firewall’s inbound and outbound rules are applied to Compute Instances, but only inbound rules are applied to NodeBalancers. -- When used in conjunction with NodeBalancers, a Cloud Firewall’s inbound rules only apply to the NodeBalancer's public IP, not the IPs of the backend nodes. This means you may also want to add individual backend nodes to a Cloud Firewall to protect any additional exposed IP addresses. +- When used in conjunction with NodeBalancers, a Cloud Firewall’s inbound rules only apply to the NodeBalancer's public IP, not the IPs of the back-end nodes. This means you may also want to add individual back-end nodes to a Cloud Firewall to protect any additional exposed IP addresses. - Cloud Firewall rules are applied to traffic over the public and private network but are not applied to traffic over a private [VLAN](/docs/products/networking/vlans/). - A maximum of **25 rules** can be added to each Cloud Firewall (both Inbound and Outbound rules combined). - A maximum of **255 IP addresses (and ranges)** can be added to each Cloud Firewall rule. diff --git a/docs/products/networking/cloud-firewall/developers/index.md b/docs/products/networking/cloud-firewall/developers/index.md index 28e8386a399..dfac759bba9 100644 --- a/docs/products/networking/cloud-firewall/developers/index.md +++ b/docs/products/networking/cloud-firewall/developers/index.md @@ -25,4 +25,4 @@ The Cloud Firewall endpoints: ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. [Learn how to use the Linode CLI](/docs/products/tools/cli/get-started/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. [Learn how to use the Linode CLI](/docs/products/tools/cli/get-started/). diff --git a/docs/products/networking/cloud-firewall/get-started/index.md b/docs/products/networking/cloud-firewall/get-started/index.md index 25ccc777a0c..14ded3cfbd7 100644 --- a/docs/products/networking/cloud-firewall/get-started/index.md +++ b/docs/products/networking/cloud-firewall/get-started/index.md @@ -14,7 +14,7 @@ Linode’s free Cloud Firewall service can be used to create, configure, and add ## Create a Cloud Firewall -There are two main options to consider when deciding how to protect your Linode Compute Instances: installing firewall software on your system or using Linode's Cloud Firewall service. While both are robust solutions, a major benefit to using Cloud Firewalls is the ease of configuration. Cloud Firewalls can be created and managed through the Cloud Manager, Linode CLI, or Linode API. +There are two main options to consider when deciding how to protect your Linode Compute Instances: installing firewall software on your system or using Linode's Cloud Firewall service. While both are robust solutions, a major benefit to using Cloud Firewalls is the ease of configuration. Cloud Firewalls can be created and managed through Cloud Manager, Linode CLI, or Linode API. - [Create a Cloud Firewall](/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/) diff --git a/docs/products/networking/cloud-firewall/guides/comparing-firewalls/index.md b/docs/products/networking/cloud-firewall/guides/comparing-firewalls/index.md index cc1dcab0e85..4a6cf6da825 100644 --- a/docs/products/networking/cloud-firewall/guides/comparing-firewalls/index.md +++ b/docs/products/networking/cloud-firewall/guides/comparing-firewalls/index.md @@ -27,9 +27,9 @@ Linode’s free Cloud Firewall service is a powerful firewall solution that oper - Users wanting to configure inbound firewall rules for NodeBalancers. {{< note >}} -If you choose to manage inbound firewall rules for NodeBalancers using Cloud Firewalls, you still need to protect any backend nodes (Compute Instances) configured to the NodeBalancer. The Cloud Firewall only filters incoming traffic to the NodeBalancer’s public IP and not the IPs of the individual instances unless they are also added to the Cloud Firewall. +If you choose to manage inbound firewall rules for NodeBalancers using Cloud Firewalls, you still need to protect any back-end nodes (Compute Instances) configured to the NodeBalancer. The Cloud Firewall only filters incoming traffic to the NodeBalancer’s public IP and not the IPs of the individual instances unless they are also added to the Cloud Firewall. -You can protect your backend nodes by either assigning the individual nodes to a Cloud Firewall (the same as your NodeBalancer or a new one) or by manually configuring firewalls internally on the instances themselves. +You can protect your back-end nodes by either assigning the individual nodes to a Cloud Firewall (the same as your NodeBalancer or a new one) or by manually configuring firewalls internally on the instances themselves. {{< /note >}} ## Firewall Software @@ -52,9 +52,9 @@ The standard firewall software available on most modern Linux distributions is * When deciding on which firewall solution to use, consider your unique needs and the requirements for your application. -- **Familiarity:** A major reason you may decide to use one option over another is your own comfort level with the tools and interfaces need to configure each firewall. If you're more familiar with Linode's own tooling (such as the Cloud Manager or CLI), the Cloud Firewall service may be easier for you to quickly configure. If you're more familiar with nftables or front-end software like *UFW*, you may want to stick to your existing tools and workflow. Consider your entire team's familiarity with the tooling, not just yours. +- **Familiarity:** A major reason you may decide to use one option over another is your own comfort level with the tools and interfaces need to configure each firewall. If you're more familiar with Linode's own tooling (such as Cloud Manager or CLI), the Cloud Firewall service may be easier for you to quickly configure. If you're more familiar with nftables or front-end software like *UFW*, you may want to stick to your existing tools and workflow. Consider your entire team's familiarity with the tooling, not just yours. -- **Configuration options:** While each solution is quite robust, using *nftables* allows for the creation of the most complex rules and provides absolute control of the firewall. That said, Cloud Firewalls are generally easier to configure and can be applied to multiple Linode services. This allows you to quickly add or modify firewall rules across multiple Compute Instances simultaneously. +- **Configuration options:** While each solution is quite robust, using *nftables* allows for the creation of the most complex rules and provides absolute control of the firewall. That said, Cloud Firewalls are generally easier to configure and can be applied to multiple Linode services. This lets you quickly add or modify firewall rules across multiple Compute Instances simultaneously. - **Automation possibilities:** Some Linux software products already integrate directly with nftables and can automatically create firewall rules. Perhaps the most commonly used example of this is [*fail2ban*](https://www.fail2ban.org/wiki/index.php/Main_Page), which can automatically create firewall rules to permanently or temporarily ban suspicious traffic. If you are configuring your own software, you may find it easier to integrate with the Linode API and use Cloud Firewalls instead of integrating directly with software-based firewalls. diff --git a/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/index.md b/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/index.md index 3fe568fc31e..32c177b9bb9 100644 --- a/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/index.md +++ b/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/index.md @@ -5,7 +5,7 @@ modified: 2023-11-01 aliases: ['/products/networking/cloud-firewall/guides/add-firewall/'] --- -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Firewalls** from the navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Firewalls** from the navigation menu. 1. From the **Firewalls** listing page, click on the **Create Firewall** link. @@ -23,7 +23,7 @@ aliases: ['/products/networking/cloud-firewall/guides/add-firewall/'] ![Click on the Create button to create your Firewall.](create-firewall.jpg "Click on the Create button to create your Firewall.") {{< note >}} -If you add a Cloud Firewall to a NodeBalancer, the inbound rules only apply to NodeBalancer’s public IP address and not the IPs of the backend nodes (Compute Instances) assigned to the NodeBalancer. This means that the IPs of the backend nodes may still be exposed to the public internet. As a best practice, you can protect the IPs of the individual Compute Instances by: +If you add a Cloud Firewall to a NodeBalancer, the inbound rules only apply to NodeBalancer’s public IP address and not the IPs of the back-end nodes (Compute Instances) assigned to the NodeBalancer. This means that the IPs of the back-end nodes may still be exposed to the public internet. As a best practice, you can protect the IPs of the individual Compute Instances by: - Adding the individual instances to the same Cloud Firewall as the NodeBalancer - Adding the individual instances to a new Cloud Firewall - Manually configuring internal firewall rules on the instances diff --git a/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/index.md b/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/index.md index 9431f0dca82..b1e90b10557 100644 --- a/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/index.md +++ b/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/index.md @@ -22,7 +22,7 @@ The Linode Cloud Manager provides a list of *predefined rules* that you can add ## View Rules -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Firewalls** from the navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Firewalls** from the navigation menu. 1. From the **Firewalls** listing page, click on the Cloud Firewall that you would like to view or modify. @@ -30,7 +30,7 @@ Rules are separated into *Inbound* and *Outbound* rule sections. ## Add a Rule -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Firewalls** from the navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Firewalls** from the navigation menu. 1. From the **Firewalls** listing page, click on the Firewall that you would like to add new rules to. This takes you to the Firewall's **Rules** page. diff --git a/docs/products/networking/dns-manager/_index.md b/docs/products/networking/dns-manager/_index.md index 626a89127c1..a1e088e1299 100644 --- a/docs/products/networking/dns-manager/_index.md +++ b/docs/products/networking/dns-manager/_index.md @@ -13,7 +13,7 @@ cascade: aliases: ['/dns-manager/','/platform/manager/dns-manager/','/networking/dns/dns-manager/','/platform/manager/dns-manager-new-manager/','/networking/dns/dns-manager-overview/','/platform/manager/dns-manager-classic-manager/','/guides/dns-manager/'] --- -The *Domains* section of the [Cloud Manager](https://cloud.linode.com/domains) is a comprehensive DNS management interface, referred to as the Linode DNS Manager. Within the DNS Manager, you can add your registered domain names and manage DNS records for each of them. +The *Domains* section of [Cloud Manager](https://cloud.linode.com/domains) is a comprehensive DNS management interface, referred to as the Linode DNS Manager. Within the DNS Manager, you can add your registered domain names and manage DNS records for each of them. ## High Availability @@ -21,7 +21,7 @@ Linode's DNS service is anycasted to over 250 locations (*PoPs*) around the worl ## Flexible Configuration -In addition to supporting a wide range of DNS record types, the Linode DNS Manager offers even more flexibility through AXFR transfers and zone types (*primary* and *secondary*). These two features work together so you can create a DNS configuration that works for your own application. Using Linode as the *primary* DNS Manager is the most common option and allows you to manage DNS records directly on the Linode platform. Operating as a *secondary* DNS provider, you can mange your DNS records within other services or tools (like cPanel) but still host them on Linode, taking advantage of the reliability and high availability of our platform. +In addition to supporting a wide range of DNS record types, the Linode DNS Manager offers even more flexibility through AXFR transfers and zone types (*primary* and *secondary*). These two features work together so you can create a DNS configuration that works for your own application. Using Linode as the *primary* DNS Manager is the most common option and lets you manage DNS records directly on the Linode platform. Operating as a *secondary* DNS provider, you can mange your DNS records within other services or tools (like cPanel) but still host them on Linode, taking advantage of the reliability and high availability of our platform. ## Pricing and Availability diff --git a/docs/products/networking/dns-manager/developers/index.md b/docs/products/networking/dns-manager/developers/index.md index 2aa8ce4a632..2adf07891d3 100644 --- a/docs/products/networking/dns-manager/developers/index.md +++ b/docs/products/networking/dns-manager/developers/index.md @@ -14,4 +14,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage Domains](/docs/products/tools/cli/guides/domains/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage Domains](/docs/products/tools/cli/guides/domains/). diff --git a/docs/products/networking/dns-manager/get-started/index.md b/docs/products/networking/dns-manager/get-started/index.md index 08bcbb8b83c..5b4fb91d434 100644 --- a/docs/products/networking/dns-manager/get-started/index.md +++ b/docs/products/networking/dns-manager/get-started/index.md @@ -7,7 +7,7 @@ tab_group_main: weight: 20 --- -Linode's DNS Manager enables users to manage DNS records for each of their domains directly within the tools they already use: like the Cloud Manager, Linode CLI, or Linode API. It supports most common DNS record types, including A, AAAA (quad A), CNAME, MX, TXT, NS, SOA, SRV, and CAA. Follow this guide to learn how to start using the DNS Manager. +Linode's DNS Manager enables users to manage DNS records for each of their domains directly within the tools they already use: like Cloud Manager, Linode CLI, or Linode API. It supports most common DNS record types, including A, AAAA (quad A), CNAME, MX, TXT, NS, SOA, SRV, and CAA. Follow this guide to learn how to start using the DNS Manager. 1. [Register the Domain](#register-the-domain) 1. [Create the Domain Zone](#create-the-domain-zone) @@ -26,7 +26,7 @@ Determine what domain name you wish to use and, if you haven't done so already, A *domain zone* (also called a [DNS zone](https://en.wikipedia.org/wiki/DNS_zone)) is a collection of DNS records for a particular domain. For full instructions on creating a domain zone, see [Create a Domain](/docs/products/networking/dns-manager/guides/create-domain/). -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the left navigation menu. Click the **Create Domain** button. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the left navigation menu. Click the **Create Domain** button. 1. Select either **Primary** or **Secondary** as the zone type. This changes some of the form options below it. diff --git a/docs/products/networking/dns-manager/guides/common-dns-configurations/index.md b/docs/products/networking/dns-manager/guides/common-dns-configurations/index.md index e92afbb126a..4b872ff052c 100644 --- a/docs/products/networking/dns-manager/guides/common-dns-configurations/index.md +++ b/docs/products/networking/dns-manager/guides/common-dns-configurations/index.md @@ -16,7 +16,7 @@ The most common DNS configuration is a single domain name on a single Linode. Fo ![The SOA record is set to "example-site-demo.com". The NS records are set to "ns1.linode.com" through "ns5.linode.com", inclusive. The MX record is set to "mail.example-site-demo.com". There are A records for [blank], which is the primary domain, and the "mail" and "www" subdomains. They are all set to the same IP.](common-dns-set-up-a-domain.png) {{< note >}} -The Domains section of the Cloud Manager can automatically add all of these records when you create a domain. For instructions, see the *Add a Domain* section of the [DNS Manager](/docs/products/networking/dns-manager/) guide. +The Domains section of Cloud Manager can automatically add all of these records when you create a domain. For instructions, see the *Add a Domain* section of the [DNS Manager](/docs/products/networking/dns-manager/) guide. {{< /note >}} ## Configure Subdomains @@ -39,7 +39,7 @@ The Domains section of the Cloud Manager can automatically add all of these reco ## Host Multiple Domains on a Single Server -To host multiple domain names on a single server, create a separate domain entry for each domain name as shown below. When creating the new domain entry, we recommend that you allow the Domains section of the Cloud Manager to automatically [insert basic records](/docs/products/networking/dns-manager/guides/create-domain/#pre-populate-dns-records). At a minimum, you'll need an A record for each domain name pointing to the server's IP address. +To host multiple domain names on a single server, create a separate domain entry for each domain name as shown below. When creating the new domain entry, we recommend that you allow the Domains section of Cloud Manager to automatically [insert basic records](/docs/products/networking/dns-manager/guides/create-domain/#pre-populate-dns-records). At a minimum, you'll need an A record for each domain name pointing to the server's IP address. ![This page shows the Domains page with three different domain zones listed.](common-dns-multiple-domains-one-server.png) diff --git a/docs/products/networking/dns-manager/guides/create-domain/index.md b/docs/products/networking/dns-manager/guides/create-domain/index.md index 1286e394121..51e62966e35 100644 --- a/docs/products/networking/dns-manager/guides/create-domain/index.md +++ b/docs/products/networking/dns-manager/guides/create-domain/index.md @@ -8,9 +8,9 @@ tags: ["linode platform","cloud manager"] aliases: ['/products/networking/dns-manager/guides/add-domains/'] --- -This guide walks you through how to create a domain through the Cloud Manager. Adding a domain only takes a few steps. Here's an outline on how to create a domain using Cloud Manager. +This guide walks you through how to create a domain through Cloud Manager. Adding a domain only takes a few steps. Here's an outline on how to create a domain using Cloud Manager. -1. [Open the Create Domain Form in the Cloud Manager](#open-the-create-domain-form-in-the-cloud-manager) +1. [Open the Create Domain Form in Cloud Manager](#open-the-create-domain-form-in-cloud-manager) 1. [Select the Zone Type](#select-the-zone-type) 1. [Enter the Domain and SOA Contact](#enter-the-domain-and-soa-contact) 1. [Pre-populate DNS Records](#pre-populate-dns-records) @@ -19,9 +19,9 @@ This guide walks you through how to create a domain through the Cloud Manager. A After you’ve figured out how to create domains, you’ll never need to call IT support for help again. Let’s look at each step in more detail. -## Open the Create Domain Form in the Cloud Manager +## Open the Create Domain Form in Cloud Manager -Figuring out how to create a domain starts with getting into the system. Log in to the [Cloud Manager](https://cloud.linode.com/) and choose **Domains** from the left navigation menu. Click the **Create Domain** button. This opens the [Domain Create](https://cloud.linode.com/domains/create) form. +Figuring out how to create a domain starts with getting into the system. Log in to [Cloud Manager](https://cloud.linode.com/) and choose **Domains** from the left navigation menu. Click the **Create Domain** button. This opens the [Domain Create](https://cloud.linode.com/domains/create) form. ## Select the Zone Type @@ -38,7 +38,7 @@ Within the **SOA Email Address** field, enter the email address for the domain a ## Pre-populate DNS Records -The **Insert Default Records** dropdown field allows you to pre-populate DNS records with the IP addresses corresponding to one of your Compute Instances or NodeBalancers. If you already know the Compute Instance or NodeBalancer you'd like to use with your domain, this adds the basic DNS records (A, AAAA, and MX) for that service automatically. +The **Insert Default Records** dropdown field lets you pre-populate DNS records with the IP addresses corresponding to one of your Compute Instances or NodeBalancers. If you already know the Compute Instance or NodeBalancer you'd like to use with your domain, this adds the basic DNS records (A, AAAA, and MX) for that service automatically. - **Do not insert default records for me.** No DNS records are automatically created. - **Insert default records from one of my Lindoes.** Select one of your Compute Instances and DNS records are automatically created using the IPv4 and IPv6 addresses for that instance. diff --git a/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md b/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md index de56d246bfd..57766bcacea 100644 --- a/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md +++ b/docs/products/networking/dns-manager/guides/incoming-dns-zone-transfers/index.md @@ -9,8 +9,8 @@ tags: ["linode platform","cloud manager"] Linode supports importing DNS records from external DNS providers in one of two ways: -- [**Import a DNS zone**](#import-a-dns-zone): Initiate a one-time transfer from an external DNS service. *This allows you to migrate to Linode and manage your DNS records from the DNS Manager.* -- [**Operate as a *secondary* read-only DNS service**](#operate-as-a-secondary-read-only-dns-service): Get notified of (or periodically check for) DNS changes from an external DNS service and automatically update the zone file with those changes. *This allows you to manage your DNS records in an external DNS service but take advantage of Linode's reliable and geographically distributed DNS platform.* +- [**Import a DNS zone**](#import-a-dns-zone): Initiate a one-time transfer from an external DNS service. *This lets you migrate to Linode and manage your DNS records from the DNS Manager.* +- [**Operate as a *secondary* read-only DNS service**](#operate-as-a-secondary-read-only-dns-service): Get notified of (or periodically check for) DNS changes from an external DNS service and automatically update the zone file with those changes. *This lets you manage your DNS records in an external DNS service but take advantage of Linode's reliable and geographically distributed DNS platform.* ## Before You Begin @@ -35,7 +35,7 @@ This section walks you through the first option, importing a DNS zone. This meth 2600:3c00::5f ``` -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the left navigation menu. Click the **Import a Zone** button. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the left navigation menu. Click the **Import a Zone** button. 1. In the **Domain** field, enter the domain name you wish to import. @@ -47,7 +47,7 @@ This section walks you through the first option, importing a DNS zone. This meth ## Operate as a Secondary Read-Only DNS Service -Using Linode's DNS Manager as a *secondary* DNS service allows you to manage your DNS records elsewhere but still take advantage of Linode's reliable and distributed platform. Chose this option if your existing DNS provider: +Using Linode's DNS Manager as a *secondary* DNS service lets you manage your DNS records elsewhere but still take advantage of Linode's reliable and distributed platform. Chose this option if your existing DNS provider: - does not offer secondary name server, - is not equipped to handle large amounts of DNS traffic, @@ -71,10 +71,10 @@ As part of this, a common reason for using Linode's DNS Manager as a secondary D ``` {{< note type="alert" >}} - On February 7th, 2023, the IP address `65.19.178.10` will be retired and replaced with `45.79.109.10`. Both IPs will respond to inbound requests until the cutover date. Outbound requests will only originate from the old IP address (`65.19.178.10`) until the cutover date. Please update your firewall rules and DNS server configurations to add the new IP address (`45.79.109.10`) prior to the cutover. + On February 7th, 2023, the IP address `65.19.178.10` will be retired and replaced with `45.79.109.10`. Both IPs will respond to inbound requests until the cutover date. Outbound requests will only originate from the old IP address (`65.19.178.10`) until the cutover date. Please update your firewall rules and DNS server configurations to add the new IP address (`45.79.109.10`) before the cutover. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the left navigation menu. Click the **Create Domain** button. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Domains** from the left navigation menu. Click the **Create Domain** button. 1. Select **Secondary** as the zone type. This changes some of the form options below it. diff --git a/docs/products/networking/dns-manager/guides/manage-dns-records/index.md b/docs/products/networking/dns-manager/guides/manage-dns-records/index.md index 9e5d002d48f..e1eaf3805dd 100644 --- a/docs/products/networking/dns-manager/guides/manage-dns-records/index.md +++ b/docs/products/networking/dns-manager/guides/manage-dns-records/index.md @@ -10,7 +10,7 @@ aliases: ['/products/networking/dns-manager/guides/add-dns-records/','/products/ ## View DNS Records -Log in to the [Cloud Manager](https://cloud.linode.com), select *Domains* from the left menu, and click on the domain you wish to view. +Log in to [Cloud Manager](https://cloud.linode.com), select *Domains* from the left menu, and click on the domain you wish to view. ![Screenshot of the Domains listing page in Cloud Manager](view-dns.png) @@ -18,9 +18,9 @@ This opens up a page that lists all DNS records for the domain. Records for each ## Add or Edit a DNS Record -After a domain has been created, you're able to add DNS records. Each type of DNS record is used for a different purpose. The applications that utilize your domain determine which DNS records you need to add. +After a domain has been created, you're able to add DNS records. Each type of DNS record is used for a different purpose. The applications that use your domain determine which DNS records you need to add. -1. View the DNS Records for your domain in the Cloud Manager. See [View DNS Records](#view-dns-records). +1. View the DNS Records for your domain in Cloud Manager. See [View DNS Records](#view-dns-records). 1. Locate the section for the record type you want to add or edit. To add a new record, click corresponding **Add a Record** button. To edit a record, locate the record in the list and click the corresponding **Edit** button. Both of these actions open up a similar form. @@ -52,7 +52,7 @@ New DNS records may take up to 24 hours to propagate throughout the internet, al ## Delete a DNS Record -1. View the DNS Records for your domain in the Cloud Manager. See [View DNS Records](#view-dns-records). +1. View the DNS Records for your domain in Cloud Manager. See [View DNS Records](#view-dns-records). 1. Locate the section for the record type you want to remove, find the record in the list, and click the corresponding **Delete** button. diff --git a/docs/products/networking/dns-manager/guides/manage-domains/index.md b/docs/products/networking/dns-manager/guides/manage-domains/index.md index 5a3cff4e75d..4dd633a76b2 100644 --- a/docs/products/networking/dns-manager/guides/manage-domains/index.md +++ b/docs/products/networking/dns-manager/guides/manage-domains/index.md @@ -10,7 +10,7 @@ aliases: ['/docs/products/networking/dns-manager/guides/remove-domains/'] ## View Domains -Log in to the [Cloud Manager](https://cloud.linode.com) and select *Domains* from the left menu. If any domains have already been added, they are listed on this page. +Log in to [Cloud Manager](https://cloud.linode.com) and select *Domains* from the left menu. If any domains have already been added, they are listed on this page. ![Screenshot of the Domains listing page in Cloud Manager](view-domains.png) @@ -26,7 +26,7 @@ To add a domain to your account, follow the instructions within the [Create a Do This section covers viewing and editing the details of the domain itself. If you wish to view and edit DNS records, see [Manage DNS Records](/docs/products/networking/dns-manager/guides/manage-dns-records/). {{< /note >}} -1. Navigate to the **Domains** page in the Cloud Manager. See [View Domains](#view-domains). +1. Navigate to the **Domains** page in Cloud Manager. See [View Domains](#view-domains). 1. Locate the domain you wish to view or edit. Click on the corresponding **Edit** link. @@ -43,11 +43,11 @@ This section covers viewing and editing the details of the domain itself. If you ## Clone a Domain -The *Clone* feature allows you to copy DNS records from an existing domain in your Linode account to a new domain. If you've already set up DNS records for one of the services you host on your Linode account, this is a good way to quickly assign another domain to that same service. +The *Clone* feature lets you copy DNS records from an existing domain in your Linode account to a new domain. If you've already set up DNS records for one of the services you host on your Linode account, this is a good way to quickly assign another domain to that same service. Here's how to clone DNS records for an existing domain: -1. Navigate to the **Domains** page in the Cloud Manager. See [View Domains](#view-domains). +1. Navigate to the **Domains** page in Cloud Manager. See [View Domains](#view-domains). 1. Click on the **more options ellipsis** corresponding to the domain whose DNS records you would like to clone and select **Clone** from the menu. @@ -59,7 +59,7 @@ Here's how to clone DNS records for an existing domain: When a domain is added to your account, it is *enabled* by default. This means that the domain is active and accessible through Linode's name servers. Disabling a domain causes it to no longer be accessible on our name servers. To change this setting, follow the instructions below. -1. Navigate to the **Domains** page in the Cloud Manager. See [View Domains](#view-domains). +1. Navigate to the **Domains** page in Cloud Manager. See [View Domains](#view-domains). 1. Locate the domain you wish to disable or enable. Click on the corresponding **Disable** (or **Enable**) link. @@ -79,7 +79,7 @@ Before deleting your domain from Linode, consider if you wish to continue using - **If you no longer wish to use this domain:** Remove Linode's name servers from your domain's registrar. *If the entries are not deleted, someone could use your domain on Linode's DNS Manager without your permission.* {{< /note >}} -1. Navigate to the **Domains** page in the Cloud Manager. See [View Domains](#view-domains). +1. Navigate to the **Domains** page in Cloud Manager. See [View Domains](#view-domains). 1. Locate the domain you wish to remove and click on the corresponding **Delete** button. To see this option, you may need to select the *ellipsis* menu. diff --git a/docs/products/networking/dns-manager/guides/outgoing-dns-zone-transfers/index.md b/docs/products/networking/dns-manager/guides/outgoing-dns-zone-transfers/index.md index 3c2fbce2a80..572a2472b55 100644 --- a/docs/products/networking/dns-manager/guides/outgoing-dns-zone-transfers/index.md +++ b/docs/products/networking/dns-manager/guides/outgoing-dns-zone-transfers/index.md @@ -8,7 +8,7 @@ tags: ["linode platform","cloud manager"] aliases: ['/products/networking/dns-manager/guides/transfer-domain-zones/'] --- -When a domain zone is created within Linode's DNS Manager, you can select if it will operate as a *primary* or a read-only *secondary* zone (see [Select the Zone Type](/docs/products/networking/dns-manager/guides/create-domain/#select-the-zone-type)). Selecting *primary* allows you to edit the DNS records directly within the DNS Manager and is the most common choice. +When a domain zone is created within Linode's DNS Manager, you can select if it will operate as a *primary* or a read-only *secondary* zone (see [Select the Zone Type](/docs/products/networking/dns-manager/guides/create-domain/#select-the-zone-type)). Selecting *primary* lets you edit the DNS records directly within the DNS Manager and is the most common choice. If you have configured your domain zone as *primary*, you can designate external DNS name servers as *secondaries*. The DNS Manager will then send a NOTIFY request to those name servers when you make any DNS changes. The external name server should then respond back with an AXFR query, which triggers Linode to send an AXFR response with the updated DNS zone. This guide covers the configuration needed to perform outgoing DNS zone transfers, including updating your SOA record. @@ -36,12 +36,12 @@ To facilitate quick updates, Linode immediately sends the external name servers ``` {{< note type="alert" >}} -On February 7th, 2023, the IP address `65.19.178.10` will be retired and replaced with `45.79.109.10`. Both IPs will respond to inbound requests until the cutover date. Outbound requests will only originate from the old IP address (`65.19.178.10`) until the cutover date. Please update your firewall rules and DNS server configurations to add the new IP address (`45.79.109.10`) prior to the cutover. +On February 7th, 2023, the IP address `65.19.178.10` will be retired and replaced with `45.79.109.10`. Both IPs will respond to inbound requests until the cutover date. Outbound requests will only originate from the old IP address (`65.19.178.10`) until the cutover date. Please update your firewall rules and DNS server configurations to add the new IP address (`45.79.109.10`) before the cutover. {{< /note >}} ## Add Secondary Name Servers -1. Log in to the [Cloud Manager](https://cloud.linode.com), select *Domains* from the left menu, and click on the domain you wish to update. +1. Log in to [Cloud Manager](https://cloud.linode.com), select *Domains* from the left menu, and click on the domain you wish to update. 1. Locate the **SOA Record** section and click **Edit**. This action may appear within the corresponding **ellipsis** menu. diff --git a/docs/products/networking/dns-manager/guides/srv-record/index.md b/docs/products/networking/dns-manager/guides/srv-record/index.md index 42f0c0400c4..9f73d43bd4b 100644 --- a/docs/products/networking/dns-manager/guides/srv-record/index.md +++ b/docs/products/networking/dns-manager/guides/srv-record/index.md @@ -8,7 +8,7 @@ tags: ["linode platform"] ## SRV Record Overview -An **SRV** (*service*) record provides the target hostname and port for a given service. This allows you to direct traffic for specific services to a server other than what is specified in corresponding DNS records. SRV records are required for some protocols, such as XMPP and SIP. +An **SRV** (*service*) record provides the target hostname and port for a given service. This lets you direct traffic for specific services to a server other than what is specified in corresponding DNS records. SRV records are required for some protocols, such as XMPP and SIP. ## Properties diff --git a/docs/products/networking/dns-manager/guides/troubleshooting-dns/index.md b/docs/products/networking/dns-manager/guides/troubleshooting-dns/index.md index 58e5553f458..2bb6468d6d9 100644 --- a/docs/products/networking/dns-manager/guides/troubleshooting-dns/index.md +++ b/docs/products/networking/dns-manager/guides/troubleshooting-dns/index.md @@ -12,7 +12,7 @@ Having problems with your DNS records? This guide to help get your DNS settings ## Before You Begin -The *Domains* section of the [Linode Cloud Manager](https://cloud.linode.com/domains) is a comprehensive DNS management interface that allows you to add DNS records for all of your domain names. For an introduction to DNS Manager including setting up DNS records, see the [DNS Manager](/docs/products/networking/dns-manager/) guide. +The *Domains* section of the [Linode Cloud Manager](https://cloud.linode.com/domains) is a comprehensive DNS management interface that lets you add DNS records for all of your domain names. For an introduction to DNS Manager including setting up DNS records, see the [DNS Manager](/docs/products/networking/dns-manager/) guide. {{< note >}} Linode's DNS service employs [Cloudflare](https://cloudflare.com) to provide denial of service (DDoS) mitigation, load balancing, and increased geographic distribution for our [name servers](/docs/guides/dns-overview/#name-servers). These factors make our service reliable, fast, and a great choice for your DNS needs. diff --git a/docs/products/networking/nodebalancers/_index.md b/docs/products/networking/nodebalancers/_index.md index e579c845a26..2733d12d8a9 100644 --- a/docs/products/networking/nodebalancers/_index.md +++ b/docs/products/networking/nodebalancers/_index.md @@ -13,7 +13,7 @@ cascade: aliases: ['/platform/nodebalancer/','/nodebalancers/','/guides/platform/nodebalancer/'] --- -**NodeBalancers** are managed *load balancers as a service (LBaaS)*, making load balancing accessible and easy to configure on the Linode Platform. They intelligently distribute incoming requests to multiple backend Compute Instances, so that there's no single point of failure. This enables high availability, horizontal scaling, and A/B testing on any application hosted with Linode. +**NodeBalancers** are managed *load balancers as a service (LBaaS)*, making load balancing accessible and easy to configure on the Linode Platform. They intelligently distribute incoming requests to multiple back-end Compute Instances, so that there's no single point of failure. This enables high availability, horizontal scaling, and A/B testing on any application hosted with Linode. ## High Availability @@ -21,21 +21,21 @@ In a typical single machine configuration, issues with the machine may cause the ## Horizontal Scaling -There are two main ways to scale an application to increase the performance and capacity within your applications. *Vertical scaling* increases or decreases the resources on the existing machines. This is achieved by [resizing](/docs/products/compute/compute-instances/guides/resize/) your Compute Instances. *Horizontal scaling* adds or removes machines that are identically configured to serve your application or perform a certain task. This is commonly accomplished through a load balancing solution, like NodeBalancers. Horizontal scaling can be much more flexible and allows you to scale as needed without taking down your site while upgrading or downgrading. +There are two main ways to scale an application to increase the performance and capacity within your applications. *Vertical scaling* increases or decreases the resources on the existing machines. This is achieved by [resizing](/docs/products/compute/compute-instances/guides/resize/) your Compute Instances. *Horizontal scaling* adds or removes machines that are identically configured to serve your application or perform a certain task. This is commonly accomplished through a load balancing solution, like NodeBalancers. Horizontal scaling can be much more flexible and lets you scale as needed without taking down your site while upgrading or downgrading. ## Additional Features -- **Firewall Security:** [Cloud Firewall](/docs/products/networking/cloud-firewall/) provides enhanced security by allowing you to control who can access your NodeBalancer. The optional Cloud Firewall sits between your NodeBalancer and the internet to filter out unwanted network traffic before it reaches your NodeBalancer. When used in conjunction with NodeBalancers, a Cloud Firewall’s inbound rules only apply to the NodeBalancer’s public IP, not the IPs of the backend nodes. This means you may also want to add individual backend nodes to a Cloud Firewall to protect any additional exposed IP addresses. +- **Firewall Security:** [Cloud Firewall](/docs/products/networking/cloud-firewall/) provides enhanced security by allowing you to control who can access your NodeBalancer. The optional Cloud Firewall sits between your NodeBalancer and the internet to filter out unwanted network traffic before it reaches your NodeBalancer. When used in conjunction with NodeBalancers, a Cloud Firewall’s inbound rules only apply to the NodeBalancer’s public IP, not the IPs of the back-end nodes. This means you may also want to add individual back-end nodes to a Cloud Firewall to protect any additional exposed IP addresses. - **Managed:** NodeBalancers take the infrastructure management out of load balancing. They are designed to be maintenance free after initial configuration. -- **Sticky Sessions:** NodeBalancers can route subsequent requests to the same backend, so all application sessions work correctly. +- **Sticky Sessions:** NodeBalancers can route subsequent requests to the same back end, so all application sessions work correctly. -- **Health Checks:** Traffic is only routed to healthy backends. Passive health checks happen on every request. You can configure active health checks based on your application or service. +- **Health Checks:** Traffic is only routed to healthy back ends. Passive health checks happen on every request. You can configure active health checks based on your application or service. -- **SSL Termination:** NodeBalancers can terminate SSL traffic on your behalf and expose the requester’s IP through the backend. This is done using configurable rulesets that give you the power to fine-tune admissible traffic. +- **SSL Termination:** NodeBalancers can terminate SSL traffic on your behalf and expose the requester’s IP through the back end. This is done using configurable rulesets that give you the power to fine-tune admissible traffic. -- **Throttling:** Prevent potential abuse (and preserve resources on your backends) by setting a client connection throttle on the NodeBalancer. +- **Throttling:** Prevent potential abuse (and preserve resources on your back ends) by setting a client connection throttle on the NodeBalancer. - **Multi-Port:** NodeBalancers support balancing traffic to multiple network ports. Several services can be load balanced with a single NodeBalancer. @@ -60,7 +60,7 @@ Cloud Firewall is available at no additional charge to customers. ## Technical Specifications - Managed cloud-based load balancing service -- Dynamically routes traffic over any ports to configurable backend Compute Instances +- Dynamically routes traffic over any ports to configurable back-end Compute Instances - Highly available with built-in redundancy - Up to 10,000 concurrent connections - Supports TCP-based (layer 4) load balancing (UDP traffic is not supported) @@ -68,28 +68,28 @@ Cloud Firewall is available at no additional charge to customers. - Supports both SSL termination (using the HTTPS protocol mode) and SSL pass-through (using the TCP protocol mode) - Equipped with both public IPv4 and IPv6 addresses - Supports inbound Cloud Firewall rules such as IPv4 and IPv6 access control lists (ACLs) to *Accept* or *Drop* ingress traffic. -- Fully customizable health checks to ensure traffic lands on a functioning backend +- Fully customizable health checks to ensure traffic lands on a functioning back end - 40 Gbps inbound network bandwidth - Free inbound network transfer - Outbound network transfer usage is counted towards the account-wide [monthly network transfer pool](/docs/products/platform/get-started/guides/network-transfer/) -- Provisioning and management through the [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) +- Provisioning and management through [Cloud Manager](https://cloud.linode.com/), [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) ## Limits and Considerations - **Maximum number of concurrent connections:** NodeBalancers each support up to 10,000 concurrent connections. If your application needs to support more than that, [contact support](https://www.linode.com/support/) to determine additional options or consider using multiple NodeBalancers behind a DNS load balancing solution such as [Round-Robin DNS](/docs/guides/setting-up-round-robin-dns/). - **Connections per second:** There are no defined rate limits for the number of connections over a given time period, though certain modes are more performant. A port configured in **TCP** mode allows for the most number of connections. A port configured in **HTTPS** mode is the most resource intensive and accommodates fewer connections. - **IP addresses:** A public IPv4 address and IPv6 address are configured on each NodeBalancer. Additional addresses are not available. -- **Private network:** Communication with backend Linodes occurs over a data center's private network. As such, backend Linodes must be located within the same data center as the NodeBalancer. +- **Private network:** Communication with back-end Linodes occurs over a data center's private network. As such, back-end Linodes must be located within the same data center as the NodeBalancer. - **HTTP support:** HTTP/1.1 (HTTP/2 support is not yet available). - **Network transfer:** *Outbound transfer* usage is counted towards the account-wide [monthly network transfer pool](/docs/products/platform/get-started/guides/network-transfer/). This pool is the combined total of the network transfer allowance of each Linode on the account. Both *Incoming transfer* and transfer over the private network are provided at no cost. -- **TLS termination:** When using a NodeBalancer with an application that requires HTTPS, you can either terminate the TLS connection on the NodeBalancer (**HTTPS** mode) or on the backend Linodes (**TCP** mode). When terminating TLS connections directly on the NodeBalancer, there are a few key considerations: +- **TLS termination:** When using a NodeBalancer with an application that requires HTTPS, you can either terminate the TLS connection on the NodeBalancer (**HTTPS** mode) or on the back-end Linodes (**TCP** mode). When terminating TLS connections directly on the NodeBalancer, there are a few key considerations: - **TLS protocols:** TLS v1.2 and v1.3 are supported in **HTTPS** mode. - - While operating in **HTTPS** mode, internal traffic sent to the backend Linodes will be unencrypted. + - While operating in **HTTPS** mode, internal traffic sent to the back-end Linodes will be unencrypted. - For applications that require a very high connection rate or otherwise need to overcome the above considerations present in **HTTPS** mode, consider operating in **TCP** mode and terminating TLS on the backend Linodes. + For applications that require a very high connection rate or otherwise need to overcome the above considerations present in **HTTPS** mode, consider operating in **TCP** mode and terminating TLS on the back-end Linodes. - **Cloud Firewall support:** When a Cloud Firewall is assigned to a NodeBalancer, the firewall only looks at incoming requests, this means that only inbound Cloud Firewall rules apply and outbound rules are not applicable. {{< note >}} - A service (Linode) can be accessed from other interfaces (not just the NodeBalancer). To filter traffic from other interfaces, backend Linodes require their own firewalls. + A service (Linode) can be accessed from other interfaces (not just the NodeBalancer). To filter traffic from other interfaces, back-end Linodes require their own firewalls. {{< /note >}} \ No newline at end of file diff --git a/docs/products/networking/nodebalancers/developers/index.md b/docs/products/networking/nodebalancers/developers/index.md index 6aa76e628eb..768d3fa2410 100644 --- a/docs/products/networking/nodebalancers/developers/index.md +++ b/docs/products/networking/nodebalancers/developers/index.md @@ -16,7 +16,7 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage NodeBalancers](/docs/products/tools/cli/guides/nodebalancers/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage NodeBalancers](/docs/products/tools/cli/guides/nodebalancers/). ## Linode Cloud Controller Manager @@ -28,6 +28,6 @@ The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the L **Terraform**: Terraform is an Infrastructure-as-code tool that includes management features for various types of Linode resources. Use Linode’s [official Terraform Provider](https://registry.terraform.io/providers/linode/linode/latest/docs) to [Create a NodeBalancer with Terraform](/docs/guides/create-a-nodebalancer-with-terraform/). To learn more about Terraform see our documentation library’s [Terraform section](/docs/applications/configuration-management/terraform/). -**Pulumi**: Pulumi is a development tool that allows you to write computer programs which deploy cloud resources. With [Pulumi’s Linode integration](https://github.com/pulumi/pulumi-linode), you can manage your Linode resources in several programming languages, like JavaScript, Go, Python, and TypeScript. Pulumi manages your resources in the same way as Linode's API or CLI. See [Pulumi’s documentation](https://www.pulumi.com/docs/intro/cloud-providers/linode/) to get started. +**Pulumi**: Pulumi is a development tool that lets you write computer programs which deploy cloud resources. With [Pulumi’s Linode integration](https://github.com/pulumi/pulumi-linode), you can manage your Linode resources in several programming languages, like JavaScript, Go, Python, and TypeScript. Pulumi manages your resources in the same way as Linode's API or CLI. See [Pulumi’s documentation](https://www.pulumi.com/docs/intro/cloud-providers/linode/) to get started. - [Create and Configure a NodeBalancer with Pulumi](/docs/guides/deploy-in-code-with-pulumi/#create-and-configure-a-nodebalancer) diff --git a/docs/products/networking/nodebalancers/get-started/index.md b/docs/products/networking/nodebalancers/get-started/index.md index 6d66167b0d2..2b513a032ea 100644 --- a/docs/products/networking/nodebalancers/get-started/index.md +++ b/docs/products/networking/nodebalancers/get-started/index.md @@ -24,7 +24,7 @@ To start using a NodeBalancer and benefiting from load balancing, your applicati {{% content "dbass-eos" %}} -In some simple applications, the servers that store your application's code can also store its files and databases. For more complex applications, you may want to consider designating separate application servers, file servers, and database servers. The application servers (where the web server software and application code resides) operate as the backends to the NodeBalancer. The file servers and database servers can be built on cloud-based solutions (like Managed Databases) or self-hosted software on Compute Instances. +In some simple applications, the servers that store your application's code can also store its files and databases. For more complex applications, you may want to consider designating separate application servers, file servers, and database servers. The application servers (where the web server software and application code resides) operate as the back ends to the NodeBalancer. The file servers and database servers can be built on cloud-based solutions (like Managed Databases) or self-hosted software on Compute Instances. For advice on load balancing and high availability, review the following resources: @@ -34,7 +34,7 @@ For advice on load balancing and high availability, review the following resourc ## Create the NodeBalancer -If you are using a Cloud Firewall with this NodeBalancer, have the name of the firewall available. To see a listing of available firewalls, log in to the [Cloud Manager](https://cloud.linode.com) and select **Firewalls** from the navigation menu. If the firewall doesn't exist yet, [Create a Cloud Firewall](/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/) and [Add Firewall Rules](/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/). +If you are using a Cloud Firewall with this NodeBalancer, have the name of the firewall available. To see a listing of available firewalls, log in to [Cloud Manager](https://cloud.linode.com) and select **Firewalls** from the navigation menu. If the firewall doesn't exist yet, [Create a Cloud Firewall](/docs/products/networking/cloud-firewall/guides/create-a-cloud-firewall/) and [Add Firewall Rules](/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/). Once your application has been deployed on multiple Compute Instances, you are ready to create the NodeBalancer. Simple instructions have been provided below. For complete instructions, see the [Create a NodeBalancer](/docs/products/networking/nodebalancers/guides/create/) guide. @@ -60,7 +60,7 @@ Once your application has been deployed on multiple Compute Instances, you are r By default, a new Cloud Firewall accepts all inbound and outbound connections. Only inbound firewall rules apply to NodeBalancers, see [Cloud Firewall Inbound Rules for NodeBalancer](/docs/products/networking/nodebalancers/guides/create/#cloud-firewall-inbound-rules-for-nodebalancer). Custom rules can be added as needed in the Firewall application. See [Add New Cloud Firewall Rules](/docs/products/networking/cloud-firewall/guides/manage-firewall-rules/). {{< /note >}} -5. Within the *NodeBalancer Settings* area, there is a single configuration block with sections for configuring the port, defining health checks, and attaching backend nodes. Additional ports can be added using the **Add another Configuration** button. +5. Within the *NodeBalancer Settings* area, there is a single configuration block with sections for configuring the port, defining health checks, and attaching back-end nodes. Additional ports can be added using the **Add another Configuration** button. {{< note >}} The following recommended parameters can be used for deploying a website. For other applications or to learn more about these settings, see the [Configuration Options](/docs/products/networking/nodebalancers/guides/configure/) guide. @@ -68,20 +68,20 @@ Once your application has been deployed on multiple Compute Instances, you are r - **Port:** For load balancing a website, configure two ports: port 80 and port 443. Each of these ports can be configured separately. See [Configuration Options > Port](/docs/products/networking/nodebalancers/guides/configure/#port). - - **Protocol:** Most applications can benefit from using the *TCP* protocol. This option is more flexible, supports HTTP/2, and maintains encrypted connections to the backend Compute Instances. If you intend to manage and terminate the TLS certificate on the NodeBalancer, use *HTTP* for port 80 and *HTTPS* for port 443. See [Configuration Options > Protocol](/docs/products/networking/nodebalancers/guides/configure/#protocol). + - **Protocol:** Most applications can benefit from using the *TCP* protocol. This option is more flexible, supports HTTP/2, and maintains encrypted connections to the back-end Compute Instances. If you intend to manage and terminate the TLS certificate on the NodeBalancer, use *HTTP* for port 80 and *HTTPS* for port 443. See [Configuration Options > Protocol](/docs/products/networking/nodebalancers/guides/configure/#protocol). - - **Algorithm:** This controls how new connections are allocated across backend nodes. Selecting *Round Robin* can be helpful when testing (in conjunction with no session stickiness). Otherwise, *Least Connections* can help evenly distribute the load for production applications. See [Configuration Options > Algorithm](/docs/products/networking/nodebalancers/guides/configure/#algorithm). + - **Algorithm:** This controls how new connections are allocated across back-end nodes. Selecting *Round Robin* can be helpful when testing (in conjunction with no session stickiness). Otherwise, *Least Connections* can help evenly distribute the load for production applications. See [Configuration Options > Algorithm](/docs/products/networking/nodebalancers/guides/configure/#algorithm). - - **Session Stickiness:** This controls how subsequent requests from the same client are routed when selecting a backend node. For testing, consider selecting *None*. Otherwise, *Table* can be used for any protocol and *HTTP Cookie* can be used for *HTTP* and *HTTPS*. See [Configuration Options > Session Stickiness](/docs/products/networking/nodebalancers/guides/configure/#session-stickiness). + - **Session Stickiness:** This controls how subsequent requests from the same client are routed when selecting a back-end node. For testing, consider selecting *None*. Otherwise, *Table* can be used for any protocol and *HTTP Cookie* can be used for *HTTP* and *HTTPS*. See [Configuration Options > Session Stickiness](/docs/products/networking/nodebalancers/guides/configure/#session-stickiness). - - **Health Checks:** NodeBalancers have both *active* and *passive* health checks available. These health checks help take unresponsive or problematic backend Compute Instances out of the rotation so that no connections are routed to them. These settings can be left at the default for most applications. Review [Configuration Options > Health Checks](/docs/products/networking/nodebalancers/guides/configure/#health-checks) for additional information. + - **Health Checks:** NodeBalancers have both *active* and *passive* health checks available. These health checks help take unresponsive or problematic back-end Compute Instances out of the rotation so that no connections are routed to them. These settings can be left at the default for most applications. Review [Configuration Options > Health Checks](/docs/products/networking/nodebalancers/guides/configure/#health-checks) for additional information. - - **Backend Nodes:** Each Compute Instance for your application should be added as a *backend node* to the NodeBalancer. These Compute Instances need to be located in the same data center as your NodeBalancer and have private IP addresses assigned to them. Set a **Label** for each instance, select the corresponding **IP address** from the dropdown menu, and enter the **Port** that the application is using on that instance. See [Backend Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/). + - **Back-end nodes:** Each Compute Instance for your application should be added as a *back-end node* to the NodeBalancer. These Compute Instances need to be located in the same data center as your NodeBalancer and have private IP addresses assigned to them. Set a **Label** for each instance, select the corresponding **IP address** from the dropdown menu, and enter the **Port** that the application is using on that instance. See [Back-end Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/). - For most web applications that have the *inbound* ports 80 and 443 configured using the *TCP* protocol, you can set the backend nodes to use the same ports. If you are using the *HTTPS* protocol, TLS termination happens on the NodeBalancer and your Compute Instances should only need to listen on port 80 (unencrypted). If that's the case, backend nodes for both *inbound* ports can be configured to use port 80. + For most web applications that have the *inbound* ports 80 and 443 configured using the *TCP* protocol, you can set the back-end nodes to use the same ports. If you are using the *HTTPS* protocol, TLS termination happens on the NodeBalancer and your Compute Instances should only need to listen on port 80 (unencrypted). If that's the case, back-end nodes for both *inbound* ports can be configured to use port 80. 1. Review the summary and click the **Create NodeBalancer** button to provision your new NodeBalancer. ## Update the DNS -After deploying your NodeBalancer and putting your application behind the NodeBalancer, the application can now be accessed using the NodeBalancer's public IPv4 and IPv6 addresses. Since most public-facing applications utilize domain names, you need to update any associated DNS records. The *A* record should use the NodeBalancer's IPv4 address and the *AAAA* record (if you're using one) should use the NodeBalancer's IPv6 address. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/#review-and-edit-a-nodebalancer) to view your NodeBalancer's IP addresses. For help changing the DNS records, consult your DNS provider's documentation. If you are using Linode's DNS Manager, see [Edit DNS Records](/docs/products/networking/dns-manager/guides/manage-dns-records/). Keep in mind that DNS changes can take up to 24 hours to fully propagate, though that typically happens much faster. \ No newline at end of file +After deploying your NodeBalancer and putting your application behind the NodeBalancer, the application can now be accessed using the NodeBalancer's public IPv4 and IPv6 addresses. Since most public-facing applications use domain names, you need to update any associated DNS records. The *A* record should use the NodeBalancer's IPv4 address and the *AAAA* record (if you're using one) should use the NodeBalancer's IPv6 address. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/#review-and-edit-a-nodebalancer) to view your NodeBalancer's IP addresses. For help changing the DNS records, consult your DNS provider's documentation. If you are using Linode's DNS Manager, see [Edit DNS Records](/docs/products/networking/dns-manager/guides/manage-dns-records/). Keep in mind that DNS changes can take up to 24 hours to fully propagate, though that typically happens much faster. \ No newline at end of file diff --git a/docs/products/networking/nodebalancers/guides/_index.md b/docs/products/networking/nodebalancers/guides/_index.md index 2a87e786e74..cc8bba6904b 100644 --- a/docs/products/networking/nodebalancers/guides/_index.md +++ b/docs/products/networking/nodebalancers/guides/_index.md @@ -19,13 +19,13 @@ tab_group_main: - [Configuration Options](/docs/products/networking/nodebalancers/guides/configure/): Edit the port configurations on a NodeBalancer. -- [Backend Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/): Manage the settings for backend nodes. +- [Back-end Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/): Manage the settings for back-end nodes. - [Available Protocols](/docs/products/networking/nodebalancers/guides/protocols/): A list of protocols supported by NodeBalancers - [TLS/SSL Termination](/docs/products/networking/nodebalancers/guides/ssl-termination/): Instructions on configuring TLS/SSL certificates on a NodeBalancer. -- [Client IP Address Pass-through](/docs/products/networking/nodebalancers/guides/client-ip/): Learn the methods of retaining client connection details and passing them to backend nodes on a NodeBalancer. +- [Client IP Address Pass-through](/docs/products/networking/nodebalancers/guides/client-ip/): Learn the methods of retaining client connection details and passing them to back-end nodes on a NodeBalancer. - [Proxy Protocol](/docs/products/networking/nodebalancers/guides/proxy-protocol/): Obtain information about a client when using the TCP protocol. diff --git a/docs/products/networking/nodebalancers/guides/backends/index.md b/docs/products/networking/nodebalancers/guides/backends/index.md index ba520f6be88..5908d8e0f8b 100644 --- a/docs/products/networking/nodebalancers/guides/backends/index.md +++ b/docs/products/networking/nodebalancers/guides/backends/index.md @@ -1,73 +1,73 @@ --- -title: "Backend Nodes (Compute Instances)" -description: "Instructions for adding and configuring backend nodes on a NodeBalancer" +title: "Back-end Nodes (Compute Instances)" +description: "Instructions for adding and configuring back-end nodes on a NodeBalancer" published: 2022-10-07 --- -Load balancers work by distributing traffic to a pool of servers. For NodeBalancers, these servers are Linode Compute Instances and they are configured as *backend nodes*. Each Compute Instance operating as a backend node needs to be located within the same data center as the NodeBalancer and be assigned a private IPv4 address. See [Managing IP addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#adding-an-ip-address) for instructions on adding a private IP address to an existing Compute Instance. +Load balancers work by distributing traffic to a pool of servers. For NodeBalancers, these servers are Linode Compute Instances and they are configured as *back-end nodes*. Each Compute Instance operating as a back-end node needs to be located within the same data center as the NodeBalancer and be assigned a private IPv4 address. See [Managing IP addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#adding-an-ip-address) for instructions on adding a private IP address to an existing Compute Instance. {{< note >}} -While only a single backend node is required, *at least* two backends need to be configured to make use of load balancing functionality. +While only a single back-end node is required, *at least* two back ends need to be configured to make use of load balancing functionality. {{< /note >}} -## Add, Edit, and Remove Backend Nodes +## Add, Edit, and Remove Back-end Nodes -Backend nodes can be defined through a NodeBalancer's [Configurations](/docs/products/networking/nodebalancers/guides/configure/), which contain all the settings and parameters for a particular *inbound* port. +Back-end nodes can be defined through a NodeBalancer's [Configurations](/docs/products/networking/nodebalancers/guides/configure/), which contain all the settings and parameters for a particular *inbound* port. -1. Log in to the [Cloud Manager](http://cloud.linode.com), click **NodeBalancers** in the left menu, and select the NodeBalancer you wish to edit. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/). +1. Log in to [Cloud Manager](http://cloud.linode.com), click **NodeBalancers** in the left menu, and select the NodeBalancer you wish to edit. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/). 1. Navigate to the **Configurations** tab. This displays a list of all ports that have been configured. 1. Open the port configuration you wish to edit or create a new one by clicking the **Add Another Configuration** button. -1. Scroll down to the *Backend Nodes* section to see a list of backends that have already been added. +1. Scroll down to the *Back-end Nodes* section to see a list of back ends that have already been added. - - Adjust any of the existing fields to edit the backend. - - Click the **Add a Node** button to add a new backend. - - Click the **Remove** link to remove the backend. + - Adjust any of the existing fields to edit the back end. + - Click the **Add a Node** button to add a new back end. + - Click the **Remove** link to remove the back end. 1. Click the **Save** button to save the configuration. {{< note >}} -Removing a backend from the NodeBalancer configuration does not delete the associated Compute Instance. It only removes that instance from operating as a backend for this particular NodeBalancer. +Removing a back end from the NodeBalancer configuration does not delete the associated Compute Instance. It only removes that instance from operating as a back end for this particular NodeBalancer. {{< /note >}} -## Backend Configuration Options +## Back end Configuration Options -Each backend node contains the following configuration parameters. +Each back-end node contains the following configuration parameters. -- **Label**: Sets a label to identify the backend. While any label can be used, it's common to use the label of the associated Compute Instance. -- **IP Address**: Select the private IPv4 address of the Compute Instance you wish to use as the backend. This field has a dropdown list of all Compute Instances within the same region as the NodeBalancer that have a private IPv4 address assigned. -- **Port**: Identifies the port that the NodeBalancer should use when sending traffic to the backend. This should be the port that the application is listening on within this backend Compute Instance. -- **Weight**: Sets the priority of the backend. Backends with a higher weight are allocated more connections than backends with a lower weight. -- **Mode**: Determines if the backend accepts or rejects traffic and in what circumstances. See [Mode](#mode). +- **Label**: Sets a label to identify the back end. While any label can be used, it's common to use the label of the associated Compute Instance. +- **IP Address**: Select the private IPv4 address of the Compute Instance you wish to use as the back end. This field has a dropdown list of all Compute Instances within the same region as the NodeBalancer that have a private IPv4 address assigned. +- **Port**: Identifies the port that the NodeBalancer should use when sending traffic to the back end. This should be the port that the application is listening on within this back-end Compute Instance. +- **Weight**: Sets the priority of the back end. Back ends with a higher weight are allocated more connections than back ends with a lower weight. +- **Mode**: Determines if the back end accepts or rejects traffic and in what circumstances. See [Mode](#mode). ## Mode -By default, all backends are allocated traffic according to the configuration settings of the NodeBalancer, provided the backends have a status of *up*. To change this behavior, use the **Mode** setting to modify how a backend accepts or rejects traffic. +By default, all back ends are allocated traffic according to the configuration settings of the NodeBalancer, provided the back ends have a status of *up*. To change this behavior, use the **Mode** setting to modify how a back end accepts or rejects traffic. - **Accept**: Accept incoming connections -- **Reject**: Reject new incoming connections and discontinue health checks on this backend. Existing connections remain active, but session stickiness is not respected. Useful for taking the backend out of rotation to perform maintenance or decommission it. -- **Drain**: Only accept connections from clients whose session stickiness points to this backend. Use *in advance* of taking a backend out of rotation for maintenance or decommissioning to gradually drain connections. -- **Backup**: Only accept connections if all other backends are down. Useful if you use frontend caching servers, such as Varnish, and want to direct traffic to the origin servers if the caching servers are down. +- **Reject**: Reject new incoming connections and discontinue health checks on this back end. Existing connections remain active, but session stickiness is not respected. Useful for taking the back end out of rotation to perform maintenance or decommission it. +- **Drain**: Only accept connections from clients whose session stickiness points to this back end. Use *in advance* of taking a back end out of rotation for maintenance or decommissioning to gradually drain connections. +- **Backup**: Only accept connections if all other back ends are down. Useful if you use front-end caching servers, such as Varnish, and want to direct traffic to the origin servers if the caching servers are down. {{< note >}} Changes made to the Mode field are applied within 60 seconds. {{< /note >}} -## Understand the Status of a Backend Node +## Understand the Status of a Back-end Node -Each backend node has a status of *up* or *down*. +Each back-end node has a status of *up* or *down*. -- **Up**: The backend is healthy and should be kept in rotation, provided that the [Mode](#mode) is allowing traffic. -- **Down**: The backend is *unhealthy* and taken out of rotation. This means that a health check has failed or the **Mode** has been set to *Reject*. +- **Up**: The back end is healthy and should be kept in rotation, provided that the [Mode](#mode) is allowing traffic. +- **Down**: The back end is *unhealthy* and taken out of rotation. This means that a health check has failed or the **Mode** has been set to *Reject*. ## Configure Compute Instances -When adding a Compute Instance as a *Backend Node* to a NodeBalancer, you must also ensure that it has been properly configured for your application. As part of this, review the following: +When adding a Compute Instance as a *Back-end Node* to a NodeBalancer, you must also ensure that it has been properly configured for your application. As part of this, review the following: - Install all required software on the Compute Instance. - Verify that any required data has been properly replicated on each Compute Instance. There are many different methods of ensuring data is properly replicated between multiple servers, including [rsync](https://linux.die.net/man/1/rsync), [Gluster](https://www.gluster.org/), [Galera](https://galeracluster.com/), or CI/CD tooling. -- Verify that each instance accepts traffic over the port specified in the backend's configuration and is not blocking addresses from the NodeBalancer's private IP address range: `192.168.255.0/24`. \ No newline at end of file +- Verify that each instance accepts traffic over the port specified in the back end's configuration and is not blocking addresses from the NodeBalancer's private IP address range: `192.168.255.0/24`. \ No newline at end of file diff --git a/docs/products/networking/nodebalancers/guides/client-ip/index.md b/docs/products/networking/nodebalancers/guides/client-ip/index.md index 564a0b4446a..f9b2a85a4d4 100644 --- a/docs/products/networking/nodebalancers/guides/client-ip/index.md +++ b/docs/products/networking/nodebalancers/guides/client-ip/index.md @@ -1,12 +1,12 @@ --- title: "Client's IP Address Pass-through" -description: "Learn the methods of retaining client connection details and passing them to backend nodes on a NodeBalancer" +description: "Learn the methods of retaining client connection details and passing them to back-end nodes on a NodeBalancer" published: 2022-10-07 --- -In some applications, it's helpful (or required) to know the IP address where the request originally came from, referred to as the client IP. When a NodeBalancer routes traffic to a backend node, the originating IP address becomes the NodeBalancer's private IP address. This means that the client IP's address is not visible in the location that the application might typically check. To overcome this, there are a few ways to pass the client's IP address to the backend nodes. The method you select depends on the protocol the NodeBalancer's port is using. +In some applications, it's helpful (or required) to know the IP address where the request originally came from, referred to as the client IP. When a NodeBalancer routes traffic to a back-end node, the originating IP address becomes the NodeBalancer's private IP address. This means that the client IP's address is not visible in the location that the application might typically check. To overcome this, there are a few ways to pass the client's IP address to the back-end nodes. The method you select depends on the protocol the NodeBalancer's port is using. -- **Proxy Protocol**: This method works for the TCP protocol, provided the backend application also supports it. See [Proxy Protocol](/docs/products/networking/nodebalancers/guides/proxy-protocol/). +- **Proxy Protocol**: This method works for the TCP protocol, provided the back-end application also supports it. See [Proxy Protocol](/docs/products/networking/nodebalancers/guides/proxy-protocol/). - **HTTP Headers:** This method works for the HTTP and HTTPS protocols and is discussed below. ## HTTP Headers (Using HTTP or HTTPS Protocols) diff --git a/docs/products/networking/nodebalancers/guides/configure/index.md b/docs/products/networking/nodebalancers/guides/configure/index.md index 32232d55800..eaf505c9aee 100644 --- a/docs/products/networking/nodebalancers/guides/configure/index.md +++ b/docs/products/networking/nodebalancers/guides/configure/index.md @@ -7,17 +7,17 @@ tags: ["linode platform","networking"] aliases: ['/nodebalancers/reference/','/platform/nodebalancer/nodebalancer-reference-guide-new-manager/','/platform/nodebalancer/nodebalancer-reference-guide/','/linode-platform/nodebalancer-reference/','/platform/nodebalancer/nodebalancer-reference-guide-classic-manager/','/guides/nodebalancer-reference-guide/'] --- -NodeBalancers, and load balancers in general, operate by taking inbound traffic over certain ports and distributing that traffic to pre-defined backend instances. For NodeBalancers, the settings that accommodate this behavior are all stored within *Configurations*. Each configuration specifies the inbound port, the protocol, the load balancing algorithm, health checks, and the backend nodes. This guide covers how to add or edit these configurations as well as the options that are available. +NodeBalancers, and load balancers in general, operate by taking inbound traffic over certain ports and distributing that traffic to pre-defined back-end instances. For NodeBalancers, the settings that accommodate this behavior are all stored within *Configurations*. Each configuration specifies the inbound port, the protocol, the load balancing algorithm, health checks, and the back-end nodes. This guide covers how to add or edit these configurations as well as the options that are available. ## Add or Edit Configurations -Each configuration is assigned a single inbound port. Follow the instructions below to add or edit a configuration. If your application requires multiple inbound ports, create one configuration for *each* port you wish to use. This provides a great amount of flexibility, allowing each port to have its own distinct configuration settings and backend nodes. +Each configuration is assigned a single inbound port. Follow the instructions below to add or edit a configuration. If your application requires multiple inbound ports, create one configuration for *each* port you wish to use. This provides a great amount of flexibility, allowing each port to have its own distinct configuration settings and back-end nodes. -1. Log in to the [Cloud Manager](http://cloud.linode.com), click **NodeBalancers** in the left menu, and select the NodeBalancer you wish to edit. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/). +1. Log in to [Cloud Manager](http://cloud.linode.com), click **NodeBalancers** in the left menu, and select the NodeBalancer you wish to edit. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/). 1. Navigate to the **Configurations** tab. This displays a list of all ports that have been configured. - ![Screenshot of a NodeBalancer's Configuration in the Cloud Manager](nodebalancer-configurations.png) + ![Screenshot of a NodeBalancer's Configuration in Cloud Manager](nodebalancer-configurations.png) 1. Open the port configuration you wish to edit or create a new one by clicking the **Add Another Configuration** button. @@ -31,19 +31,19 @@ This is the *inbound* port that the NodeBalancer is listening on. This can be an The protocol can be set to either TCP, HTTP, or HTTPS. While a brief description of each is provided below, review [Available Protocols](/docs/products/networking/nodebalancers/guides/protocols/) for more complete information. -- **TCP**: Supports most application-layer protocols, including HTTP and HTTPS. This should be selected when you want to enable layer 4 load balancing, use TLS/SSL pass-through, use HTTP/2.0 or higher, balance non-HTTP services, or make use of [Proxy Protocol](#proxy-protocol). Since the NodeBalancer serves as a pass-through for these TCP packets, any encrypted traffic is preserved and must be decrypted on the backend nodes. +- **TCP**: Supports most application-layer protocols, including HTTP and HTTPS. This should be selected when you want to enable layer 4 load balancing, use TLS/SSL pass-through, use HTTP/2.0 or higher, balance non-HTTP services, or make use of [Proxy Protocol](#proxy-protocol). Since the NodeBalancer serves as a pass-through for these TCP packets, any encrypted traffic is preserved and must be decrypted on the back-end nodes. -- **HTTP:** Unencrypted web traffic using HTTP/1.1. This terminates the HTTP request on the NodeBalancer, allowing the NodeBalancer to create a new HTTP request to the backend machines. This can be used when serving most standard web applications, especially if you intend on configuring the NodeBalancer to use HTTPS mode with TLS/SSL termination. +- **HTTP:** Unencrypted web traffic using HTTP/1.1. This terminates the HTTP request on the NodeBalancer, allowing the NodeBalancer to create a new HTTP request to the back-end machines. This can be used when serving most standard web applications, especially if you intend on configuring the NodeBalancer to use HTTPS mode with TLS/SSL termination. -- **HTTPS:** Encrypted web traffic using HTTP/1.1. Since this terminates the request on the NodeBalancer, it also terminates the TLS/SSL connection to decrypt the traffic. Use this if you wish to configure TLS/SSL certificates on the NodeBalancer and not on individual backend nodes. +- **HTTPS:** Encrypted web traffic using HTTP/1.1. Since this terminates the request on the NodeBalancer, it also terminates the TLS/SSL connection to decrypt the traffic. Use this if you wish to configure TLS/SSL certificates on the NodeBalancer and not on individual back-end nodes. {{< note type="warning" noTitle=true >}} - When using the **HTTPS** protocol setting, all traffic is decrypted on the NodeBalancer. Traffic between the NodeBalancer and the backend nodes is sent over the private data center network, is not encrypted, and uses the HTTP protocol. + When using the **HTTPS** protocol setting, all traffic is decrypted on the NodeBalancer. Traffic between the NodeBalancer and the back-end nodes is sent over the private data center network, is not encrypted, and uses the HTTP protocol. {{< /note >}} ### Proxy Protocol -When selecting *TCP* as the protocol, **Proxy Protocol** can be enabled to send client information to backend nodes. Backend nodes must also have Proxy Protocol enabled on supported applications to receive this information. There are two available versions of Proxy Protocol, **v1** and **v2**: +When selecting *TCP* as the protocol, **Proxy Protocol** can be enabled to send client information to back-end nodes. Back-end nodes must also have Proxy Protocol enabled on supported applications to receive this information. There are two available versions of Proxy Protocol, **v1** and **v2**: - **v1**: Proxy Protocol v1 adds a human readable string to all requests. - **v2**: Proxy Protocol v2 adds a more efficient binary data header to all requests. @@ -52,29 +52,29 @@ For more information, see the [Using Proxy Protocol with NodeBalancers](/docs/pr ### Algorithm -The *algorithm* controls how *new connections* are allocated across the backend nodes. +The *algorithm* controls how *new connections* are allocated across the back-end nodes. -- **Round Robin**: Allocates connections in a weighted circular order across the backends. +- **Round Robin**: Allocates connections in a weighted circular order across the back ends. -- **Least Connections**: Tracks each backend's connection count and allocates new connections to the one with the least connections. +- **Least Connections**: Tracks each back end's connection count and allocates new connections to the one with the least connections. -- **Source IP**: Modulates the client's IP to allocate them to the same backend on subsequent requests. This works so long as the set of backend nodes doesn't change, however the **Session Stickiness** setting (below) does affect this behavior. +- **Source IP**: Modulates the client's IP to allocate them to the same back end on subsequent requests. This works so long as the set of back-end nodes doesn't change, however the **Session Stickiness** setting (below) does affect this behavior. ### Session Stickiness -This controls how subsequent requests from the same client are routed when selecting a backend node. It allows a NodeBalancer to maintain a client session to the same backend. +This controls how subsequent requests from the same client are routed when selecting a back-end node. It allows a NodeBalancer to maintain a client session to the same back end. - **None**: No session information is saved and requests are routed in only accordance with the *algorithm* (see [Algorithm](#algorithm) above). -- **Table**: This preserves the initial backend selected for an IP address by the chosen algorithm. Subsequent requests by the same client are routed to that backend, when possible. This map is stored within the NodeBalancer and expires after 30 minutes from when it was added. If a backend node goes offline, entries in the table for that backend are removed. When a client sends a new request, it is then rerouted to another backend node (in accordance with the chosen algorithm) and a new entry is created in the table. +- **Table**: This preserves the initial back end selected for an IP address by the chosen algorithm. Subsequent requests by the same client are routed to that back end, when possible. This map is stored within the NodeBalancer and expires after 30 minutes from when it was added. If a back-end node goes offline, entries in the table for that back end are removed. When a client sends a new request, it is then rerouted to another back-end node (in accordance with the chosen algorithm) and a new entry is created in the table. -- **HTTP Cookie**: *Requires the configuration protocol be set to HTTP or HTTPS.* The NodeBalancer stores a cookie (named `NB_SRVID`) on the client that identifies the backend where the client is initially routed to. Subsequent requests by the same client are routed to that backend, when possible. If a backend node goes offline, the request is rerouted to another backend node (in accordance with the chosen algorithm) and the cookie is rewritten with the new backend identifier. +- **HTTP Cookie**: *Requires the configuration protocol be set to HTTP or HTTPS.* The NodeBalancer stores a cookie (named `NB_SRVID`) on the client that identifies the back end where the client is initially routed to. Subsequent requests by the same client are routed to that back end, when possible. If a back-end node goes offline, the request is rerouted to another back-end node (in accordance with the chosen algorithm) and the cookie is rewritten with the new back-end identifier. {{< note >}} The client must have cookies enabled. If the client has disabled cookies or deletes cookies, session persistence is not preserved and each new request is routed in accordance with the chosen algorithm. {{< /note >}} -If session persistence is required or desired for the application, it is recommended to utilize both the *Source IP* algorithm in combination with either *Table* or *HTTP Cookie* session stickiness. +If session persistence is required or desired for the application, it is recommended to use both the *Source IP* algorithm in combination with either *Table* or *HTTP Cookie* session stickiness. ### TLS/SSL Certificate and Private Key @@ -84,22 +84,22 @@ When the *HTTPS* protocol is selected, the **Certificate** and **Private Key** f - **Private Key**: The passphraseless private key that is associated with the certificate file. -A certificate can be obtained for your domain by using [certbot](https://certbot.eff.org/) or by purchasing one through a trusted certificate authority. See [TLS/SSL Termination](/docs/products/networking/nodebalancers/guides/ssl-termination/) for more details on obtaining a certificate and configuring both the NodeBalancer and backend nodes. +A certificate can be obtained for your domain by using [certbot](https://certbot.eff.org/) or by purchasing one through a trusted certificate authority. See [TLS/SSL Termination](/docs/products/networking/nodebalancers/guides/ssl-termination/) for more details on obtaining a certificate and configuring both the NodeBalancer and back-end nodes. {{< note >}} -If you wish to use TLS/SSL pass-through and terminate the HTTPS connection on the backend nodes, select the **TCP** protocol instead of **HTTPS**. +If you wish to use TLS/SSL pass-through and terminate the HTTPS connection on the back-end nodes, select the **TCP** protocol instead of **HTTPS**. {{< /note >}} ## Health Checks -NodeBalancers perform both passive and active health checks against the backend nodes. Backends that are not responsive are marked as *down* and taken out of rotation. +NodeBalancers perform both passive and active health checks against the back-end nodes. Back ends that are not responsive are marked as *down* and taken out of rotation. ### Active Health Checks -*Active* health checks proactively query the backend nodes by performing TCP connections or making HTTP requests. To enable an active health check, choose from one of the following types: +*Active* health checks proactively query the back-end nodes by performing TCP connections or making HTTP requests. To enable an active health check, choose from one of the following types: -- **TCP Connection**: Requires a successful TCP handshake with a backend node. -- **HTTP Valid Status**: Performs an HTTP request on the provided path and requires a 2xx or 3xx response from the backend node. +- **TCP Connection**: Requires a successful TCP handshake with a back-end node. +- **HTTP Valid Status**: Performs an HTTP request on the provided path and requires a 2xx or 3xx response from the back-end node. - **HTTP Body Regex**: Performs an HTTP request on the provided path and requires the provided PCRE regular expression matches against the request's result body. Additionally, configure the following settings to adjust the frequency and number of attempts: @@ -110,8 +110,8 @@ Additionally, configure the following settings to adjust the frequency and numbe ### Passive Health Checks -The **passive checks** setting controls if passive health checks are enabled. When enabled, the NodeBalancer monitors all requests sent to backend nodes. If the request times out, returns a 5xx response code (excluding 501 and 505), or otherwise fails to connect, the backend is marked as *down* and taken out of rotation. +The **passive checks** setting controls if passive health checks are enabled. When enabled, the NodeBalancer monitors all requests sent to back-end nodes. If the request times out, returns a 5xx response code (excluding 501 and 505), or otherwise fails to connect, the back end is marked as *down* and taken out of rotation. -## Backend Nodes (Compute Instances) +## Back-end Nodes (Compute Instances) -Load balancers work by distributing traffic to a pool of servers. For NodeBalancers, these servers are Linode Compute Instances and they are configured as *backend nodes*. For information on configuring backend nodes, see the [Configure Backend Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/) guide. \ No newline at end of file +Load balancers work by distributing traffic to a pool of servers. For NodeBalancers, these servers are Linode Compute Instances and they are configured as *back-end nodes*. For information on configuring back-end nodes, see the [Configure Back-end Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/) guide. \ No newline at end of file diff --git a/docs/products/networking/nodebalancers/guides/create/index.md b/docs/products/networking/nodebalancers/guides/create/index.md index f7b48d0e7eb..413e451a678 100644 --- a/docs/products/networking/nodebalancers/guides/create/index.md +++ b/docs/products/networking/nodebalancers/guides/create/index.md @@ -5,20 +5,20 @@ published: 2022-10-07 modified: 2023-02-06 --- -This guide walks you through creating a NodeBalancer through the Cloud Manager. +This guide walks you through creating a NodeBalancer through Cloud Manager. -1. [Open the Create NodeBalancer Form in the Cloud Manager](#open-the-create-nodebalancer-form-in-the-cloud-manager) +1. [Open the Create NodeBalancer Form in Cloud Manager](#open-the-create-nodebalancer-form-in-cloud-manager) 1. [Set the Label](#set-the-label) 1. [Select a Region](#select-a-region) 1. [Assign a Cloud Firewall](#assign-a-cloud-firewall-optional) 1. [Add and Configure Ports](#add-and-configure-ports) 1. [Set Up Health Checks for Each Port](#set-up-health-checks-for-each-port) -1. [Add Backend Nodes to Each Port](#add-backend-nodes-to-each-port) +1. [Add Back-end Nodes to Each Port](#add-backend-nodes-to-each-port) 1. [Deploy the NodeBalancer](#deploy-the-nodebalancer) -## Open the Create NodeBalancer Form in the Cloud Manager +## Open the Create NodeBalancer Form in Cloud Manager -Log in to the [Cloud Manager](https://cloud.linode.com/) and select **NodeBalancers** from the left navigation menu. Click the **Create NodeBalancer** button. This opens the *[NodeBalancer Create](https://cloud.linode.com/nodebalancers/create)* form. +Log in to [Cloud Manager](https://cloud.linode.com/) and select **NodeBalancers** from the left navigation menu. Click the **Create NodeBalancer** button. This opens the *[NodeBalancer Create](https://cloud.linode.com/nodebalancers/create)* form. ## Set the Label @@ -58,23 +58,23 @@ By default, a new Cloud Firewall accepts all inbound and outbound connections. O ### Cloud Firewall Inbound Rules for NodeBalancer - Inbound rules limit incoming network connections to the NodeBalancer based on the port(s) and sources you configure. -- The NodeBalancer accepts traffic and routes traffic on an internal network to backend targets. For this reason, only inbound firewall rules apply to NodeBalancer. +- The NodeBalancer accepts traffic and routes traffic on an internal network to back end targets. For this reason, only inbound firewall rules apply to NodeBalancer. - Inbound firewall rules such as IPv4 and IPv6 access control lists (ACLs) can be configured to *Accept* or *Drop* ingress traffic to the NodeBalancer. - NodeBalancers can accept TCP connections on all ports. When you add an inbound rule for a NodeBalancer in Cloud Firewall, select TCP as the transport layer protocol. UDP, ICMP, and IPENCAP are not currently supported on NodeBalancers. -- The firewall is in front of the NodeBalancer and the assigned backend nodes. When both the NodeBalancer and its backend nodes have firewalls, the NodeBalancers inbound firewall rules are applied to incoming requests first, before the requests reach the backend nodes. -- A backend node server (Linode) can have multiple IP addresses. The NodeBalancer firewall only controls inbound traffic to the backend nodes IPs that are assigned to the NodeBalancer. A service (Linode) can be accessed from any interface (not just the NodeBalancer). To filter traffic from other interfaces, backend Linodes require their own firewalls. +- The firewall is in front of the NodeBalancer and the assigned back-end nodes. When both the NodeBalancer and its back-end nodes have firewalls, the NodeBalancers inbound firewall rules are applied to incoming requests first, before the requests reach the back-end nodes. +- A back-end node server (Linode) can have multiple IP addresses. The NodeBalancer firewall only controls inbound traffic to the back-end nodes IPs that are assigned to the NodeBalancer. A service (Linode) can be accessed from any interface (not just the NodeBalancer). To filter traffic from other interfaces, back-end Linodes require their own firewalls. ![Figure of traffic going through firewall and NodeBalancer and traffic bypassing firewall and NodeBalancer](nb-firewall.jpg) ## Add and Configure Ports -To start load balancing traffic, you need to define which ports the NodeBalancer should listen to and how the incoming traffic should be routed to the backend nodes. These ports can be configured within the **NodeBalancer Settings** area. By default, a single port configuration is visible in this area. Additional ports can be added by clicking the **Add Another Configuration** button. See [Configuration Options](/docs/products/networking/nodebalancers/guides/configure/) for more details regarding each of these settings. +To start load balancing traffic, you need to define which ports the NodeBalancer should listen to and how the incoming traffic should be routed to the back-end nodes. These ports can be configured within the **NodeBalancer Settings** area. By default, a single port configuration is visible in this area. Additional ports can be added by clicking the **Add Another Configuration** button. See [Configuration Options](/docs/products/networking/nodebalancers/guides/configure/) for more details regarding each of these settings. - **Port:** Enter the *inbound* port the NodeBalancer should listen to. This can be any port from 1 through 65534 and should align with the port the client connects to. See [Configuration Options > Port](/docs/products/networking/nodebalancers/guides/configure/#port). - **Protocol:** Select *TCP*, *HTTP*, or *HTTPS*. For many applications, using *TCP* offers the most flexibility and allows for TLS pass through. Using *HTTP* and *HTTPS* offers some additional NodeBalancer options and allows for TLS termination. See [Configuration Options > Protocol](/docs/products/networking/nodebalancers/guides/configure/#protocol). -- **Proxy Protocol:** *Only visible when the *TCP* protocol is selected.* Used for sending the client IP address to the backend nodes. See [Configuration Options > Proxy Protocol](/docs/products/networking/nodebalancers/guides/configure/#proxy-protocol). -- **Algorithm:** Controls how new connections are allocated across backend nodes. See [Configuration Options > Algorithm](/docs/products/networking/nodebalancers/guides/configure/#algorithm). -- **Session Stickiness:** Controls how subsequent requests from the same client are routed when selecting a backend node. See [Configuration Options > Session Stickiness](/docs/products/networking/nodebalancers/guides/configure/#session-stickiness). +- **Proxy Protocol:** *Only visible when the *TCP* protocol is selected.* Used for sending the client IP address to the back-end nodes. See [Configuration Options > Proxy Protocol](/docs/products/networking/nodebalancers/guides/configure/#proxy-protocol). +- **Algorithm:** Controls how new connections are allocated across back-end nodes. See [Configuration Options > Algorithm](/docs/products/networking/nodebalancers/guides/configure/#algorithm). +- **Session Stickiness:** Controls how subsequent requests from the same client are routed when selecting a back-end node. See [Configuration Options > Session Stickiness](/docs/products/networking/nodebalancers/guides/configure/#session-stickiness). {{< note >}} For most web applications, it's common to configure two ports: port *80* and port *443*. @@ -82,15 +82,15 @@ For most web applications, it's common to configure two ports: port *80* and por ## Set Up Health Checks for Each Port -Each port can optionally be configured with health checks. These health checks either proactively query the backend nodes (*active*) or monitor the existing traffic to backend nodes (*passive*). If a health check determines that the backends aren't responsive or are encountering another issue, they can be marked as *down* and taken out of rotation. +Each port can optionally be configured with health checks. These health checks either proactively query the back-end nodes (*active*) or monitor the existing traffic to back-end nodes (*passive*). If a health check determines that the back ends aren't responsive or are encountering another issue, they can be marked as *down* and taken out of rotation. -- **Active Health Checks:** Active health checks proactively query the backend nodes by performing TCP connections or making HTTP requests. See [Configuration Options > Active Health Checks](/docs/products/networking/nodebalancers/guides/configure/#active-health-checks). +- **Active Health Checks:** Active health checks proactively query the back-end nodes by performing TCP connections or making HTTP requests. See [Configuration Options > Active Health Checks](/docs/products/networking/nodebalancers/guides/configure/#active-health-checks). -- **Passive Checks:** Passive health checks monitor requests sent to the backend nodes and look for any issues. See [Configuration Options > Passive Health Checks](/docs/products/networking/nodebalancers/guides/configure/#passive-health-checks). +- **Passive Checks:** Passive health checks monitor requests sent to the back-end nodes and look for any issues. See [Configuration Options > Passive Health Checks](/docs/products/networking/nodebalancers/guides/configure/#passive-health-checks). -## Add Backend Nodes to Each Port +## Add Back-end Nodes to Each Port -Load balancers work by distributing traffic to a pool of servers. For NodeBalancers, these servers are Linode Compute Instances and they are configured as *backend nodes*. Within the **Backend Nodes** area of the creation form, add each Compute Instance you intend on using with this NodeBalancer, making sure to select the correct private IP address for the NodeBalancer and the port that the application is using. For information on configuring backend nodes, see the [Configure Backend Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/) guide. +Load balancers work by distributing traffic to a pool of servers. For NodeBalancers, these servers are Linode Compute Instances and they are configured as *back-end nodes*. Within the **Back-end Nodes** area of the creation form, add each Compute Instance you intend on using with this NodeBalancer, making sure to select the correct private IP address for the NodeBalancer and the port that the application is using. For information on configuring back-end nodes, see the [Configure Back-end Nodes (Compute Instances)](/docs/products/networking/nodebalancers/guides/backends/) guide. ## Deploy the NodeBalancer diff --git a/docs/products/networking/nodebalancers/guides/load-balancing/index.md b/docs/products/networking/nodebalancers/guides/load-balancing/index.md index a834f31d3af..656461678d3 100644 --- a/docs/products/networking/nodebalancers/guides/load-balancing/index.md +++ b/docs/products/networking/nodebalancers/guides/load-balancing/index.md @@ -7,7 +7,7 @@ tags: ["linode platform","networking"] aliases: ['/platform/nodebalancer/what-are-nodebalancers/','/guides/what-are-nodebalancers/'] --- -Load balancing allows you to distribute incoming network traffic across multiple servers so that no one server takes on all the demand. This allows high traffic sites and applications to field a large number of users without performance degradation. It also allows you to scale a site or application by adding more servers as your need grows, or remove them if your need diminishes. +Load balancing lets you distribute incoming network traffic across multiple servers so that no one server takes on all the demand. This allows high traffic sites and applications to field a large number of users without performance degradation. It also lets you scale a site or application by adding more servers as your need grows, or remove them if your need diminishes. Linode offers load balancers as a service (LBaaS) called NodeBalancers. NodeBalancers are built for high availability and designed to be maintenance free after initial configuration. @@ -15,7 +15,7 @@ This guide provides a high-level overview of NodeBalancers. To set-up a NodeBala ## Overview -A NodeBalancer is assigned its own public IP address where it will listen for incoming connections. Then, using configurable rules, it routes the connection to one backend node (out of one or more). A NodeBalancer allows the incoming traffic load to your application to be spread over any number of Linodes. +A NodeBalancer is assigned its own public IP address where it will listen for incoming connections. Then, using configurable rules, it routes the connection to one back-end node (out of one or more). A NodeBalancer allows the incoming traffic load to your application to be spread over any number of Linodes. ### A Non-Load Balanced Configuration @@ -27,7 +27,7 @@ In a standard non-load balanced configuration, traffic comes into a server direc ![Single Web Server Flow With NodeBalancer](singleWebServerNodeBalancer.png) -When using a load balancer, like a NodeBalancer, traffic comes to the site through the load balancer first. It's then managed before reaching the Linode. In addition to balancing traffic load, NodeBalancers also offer features like [SSL termination](https://en.wikipedia.org/wiki/TLS_termination_proxy). NodeBalancers alleviate this burden from the server allowing them to be faster at other tasks, like serving pages. Therefore, even with only one server on the backend, having a NodeBalancer in front of your server can be an advantage. +When using a load balancer, like a NodeBalancer, traffic comes to the site through the load balancer first. It's then managed before reaching the Linode. In addition to balancing traffic load, NodeBalancers also offer features like [SSL termination](https://en.wikipedia.org/wiki/TLS_termination_proxy). NodeBalancers alleviate this burden from the server allowing them to be faster at other tasks, like serving pages. Therefore, even with only one server on the back end, having a NodeBalancer in front of your server can be an advantage. ### A Highly Available Load Balanced Configuration @@ -36,6 +36,6 @@ When using a load balancer, like a NodeBalancer, traffic comes to the site throu The optimal solution for a highly available site or application is to have multiple Linodes behind a NodeBalancer. Now when traffic comes into the NodeBalancer it can be routed to any one of the Linodes available. - [Health checks](/docs/products/networking/nodebalancers/guides/configure/#health-checks) are performed to make sure that requests are only routed to healthy Linodes. -- Backend Linodes can be added or removed seamlessly without end users noticing any downtime. -- Client requests can be routed to the same backend Linode through [sticky sessions](/docs/products/networking/nodebalancers/guides/configure/#session-stickiness). -- [Cloud Firewall](/docs/products/networking/cloud-firewall/) provides enhanced security by allowing you to control who can access your NodeBalancer. The optional Cloud Firewall sits between your NodeBalancer and the internet to filter out unwanted network traffic before it reaches your NodeBalancer. When used in conjunction with NodeBalancers, a Cloud Firewall’s inbound rules only apply to the NodeBalancer’s public IP, not the IPs of the backend nodes. This means you may also want to add individual backend nodes to a Cloud Firewall to protect any additional exposed IP addresses. \ No newline at end of file +- Back-end Linodes can be added or removed seamlessly without end users noticing any downtime. +- Client requests can be routed to the same back-end Linode through [sticky sessions](/docs/products/networking/nodebalancers/guides/configure/#session-stickiness). +- [Cloud Firewall](/docs/products/networking/cloud-firewall/) provides enhanced security by allowing you to control who can access your NodeBalancer. The optional Cloud Firewall sits between your NodeBalancer and the internet to filter out unwanted network traffic before it reaches your NodeBalancer. When used in conjunction with NodeBalancers, a Cloud Firewall’s inbound rules only apply to the NodeBalancer’s public IP, not the IPs of the back-end nodes. This means you may also want to add individual back-end nodes to a Cloud Firewall to protect any additional exposed IP addresses. \ No newline at end of file diff --git a/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md b/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md index 96d5a6e0393..0c991fd3574 100644 --- a/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md +++ b/docs/products/networking/nodebalancers/guides/manage-nodebalancers-with-linode-api/index.md @@ -73,9 +73,9 @@ NodeBalancers are created without any configuration profiles attached. Each prof For more information about configuration options, see our [NodeBalancer Reference Guide](/docs/products/networking/nodebalancers/guides/configure/). {{< /note >}} -## Add Backend Compute Instances +## Add Back-end Compute Instances -Even with a working configuration profile, the NodeBalancer isn't doing anything yet, since it has no backends connected to it. Repeat the steps in this section for each backend you would like to add; usually you will want at least two. +Even with a working configuration profile, the NodeBalancer isn't doing anything yet, since it has no back ends connected to it. Repeat the steps in this section for each back end you would like to add; usually you will want at least two. ### Create Compute Instances @@ -128,11 +128,11 @@ Even with a working configuration profile, the NodeBalancer isn't doing anything -H "Authorization: Bearer $TOKEN" ``` -### Add Backends to the NodeBalancer +### Add Back ends to the NodeBalancer -Add the new Compute Instances as backends to the NodeBalancer. +Add the new Compute Instances as back ends to the NodeBalancer. -1. Add configuration options for each backend. Substitute the private IP address of the Compute Instance into the `address` field and give each backend a unique label. +1. Add configuration options for each back end. Substitute the private IP address of the Compute Instance into the `address` field and give each back end a unique label. ```file {title="add-node.json" lang="json"} { @@ -141,7 +141,7 @@ Add the new Compute Instances as backends to the NodeBalancer. } ``` -1. Use the `/nodes` endpoint to add these backends: +1. Use the `/nodes` endpoint to add these back ends: ```command curl https://api.linode.com/v4/nodebalancers/$NODEBALANCER_ID/configs/$CONFIG_ID \ @@ -150,11 +150,11 @@ Add the new Compute Instances as backends to the NodeBalancer. -X POST -d @add-node.json ``` -1. Repeat this process for each additional backend. +1. Repeat this process for each additional back end. -## Check Backend Status +## Check Back-end Status -Check the status of the two backend nodes: +Check the status of the two back-end nodes: ```command curl https://api.linode.com/v4/nodebalancers/$NODEBALANCER_ID/configs/$CONFIG_ID \ @@ -170,13 +170,13 @@ curl https://api.linode.com/v4/nodebalancers/$NODEBALANCER_ID/configs/$CONFIG_ID . . . ``` -Both backends are down because there is no process for the NodeBalancer to connect to on the designated port. As a demonstration, a basic install of NGINX will listen on port 80 automatically. SSH into each Compute Instance and install NGINX: +Both back ends are down because there is no process for the NodeBalancer to connect to on the designated port. As a demonstration, a basic install of NGINX will listen on port 80 automatically. SSH into each Compute Instance and install NGINX: ```command apt update && apt upgrade && apt install nginx ``` -If you check the NodeBalancer config again, it should report that both backends are now up. You can also navigate to the NodeBalancer's public IP address in a browser; the default NGINX landing page should be displayed. +If you check the NodeBalancer config again, it should report that both back ends are now up. You can also navigate to the NodeBalancer's public IP address in a browser; the default NGINX landing page should be displayed. ## Configure HTTPS diff --git a/docs/products/networking/nodebalancers/guides/manage/index.md b/docs/products/networking/nodebalancers/guides/manage/index.md index 416d690fa3c..6dfe1a6eb15 100644 --- a/docs/products/networking/nodebalancers/guides/manage/index.md +++ b/docs/products/networking/nodebalancers/guides/manage/index.md @@ -6,13 +6,13 @@ published: 2022-10-07 ## View NodeBalancers -Log in to the [Cloud Manager](https://cloud.linode.com) and select NodeBalancers from the left menu. If any NodeBalancers exist on your account, they are listed on this page. +Log in to [Cloud Manager](https://cloud.linode.com) and select NodeBalancers from the left menu. If any NodeBalancers exist on your account, they are listed on this page. ![Screenshot of the NodeBalancer listing page in Cloud Manager](nodebalancer-view-list.png) Each NodeBalancer in the matrix is displayed alongside the following details: -- **Backend Status:** The number of backend machines that are available and accepting connections (*up*) or have been removed from the rotation and are not accepting connections (*down*). +- **Back-end Status:** The number of back-end machines that are available and accepting connections (*up*) or have been removed from the rotation and are not accepting connections (*down*). - **Transferred:** The amount of network transfer consumed by the inbound traffic to the NodeBalancer. - **Ports:** A list of the ports that have been configured on the NodeBalancer. - **IP Address:** The NodeBalancer's IPv4 address. @@ -24,23 +24,23 @@ To create a NodeBalancer, follow the instructions within the [Create a NodeBalan ## Review and Edit a NodeBalancer -Navigate to the **NodeBalancer** page in the Cloud Manager and select the NodeBalancer you wish to edit. See [View NodeBalancers](#view-nodebalancers). +Navigate to the **NodeBalancer** page in Cloud Manager and select the NodeBalancer you wish to edit. See [View NodeBalancers](#view-nodebalancers). -![Screenshot of a NodeBalancer entry in the Cloud Manager](nodebalancer-edit.png) +![Screenshot of a NodeBalancer entry in Cloud Manager](nodebalancer-edit.png) This displays the details and settings for the selected NodeBalancer. -![Screenshot of a NodeBalancer entry in the Cloud Manager](nodebalancer-summary.png) +![Screenshot of a NodeBalancer entry in Cloud Manager](nodebalancer-summary.png) From here, the following pages are available: -- **Summary:** View important details and graphs. This includes viewing the IP addresses, the Cloud Firewall if a firewall is assigned, the ports, the status of the backends, and graphs for both the number of connections and network traffic. +- **Summary:** View important details and graphs. This includes viewing the IP addresses, the Cloud Firewall if a firewall is assigned, the ports, the status of the back ends, and graphs for both the number of connections and network traffic. - **Configurations:** This lists each port configured for the NodeBalancer, with the ability to edit the settings for the existing port or add a new port. See [Configuration Options](/docs/products/networking/nodebalancers/guides/configure/) for more information on each of these settings. - **Settings:** Displays additional settings for the NodeBalancer, including the label, firewall and connection throttle setting. ## Delete a NodeBalancer -1. Navigate to the **NodeBalancer** page in the Cloud Manager and select the NodeBalancer you wish to edit. +1. Navigate to the **NodeBalancer** page in Cloud Manager and select the NodeBalancer you wish to edit. 1. Navigate to the **Settings** tab, scroll to the *Delete NodeBalancer* section, and click **Delete**. @@ -58,7 +58,7 @@ After the NodeBalancer is created, you can add a firewall, select a different fi ### Unassign the Firewall -1. Navigate to the **NodeBalancer** page in the Cloud Manager and select the NodeBalancer that has the firewall you wish to unassign. +1. Navigate to the **NodeBalancer** page in Cloud Manager and select the NodeBalancer that has the firewall you wish to unassign. 1. Navigate to the **Settings** tab. In the *Firewall* section, click **Unassign**. diff --git a/docs/products/networking/nodebalancers/guides/protocols/index.md b/docs/products/networking/nodebalancers/guides/protocols/index.md index a30d76f967d..a8a970a9f20 100644 --- a/docs/products/networking/nodebalancers/guides/protocols/index.md +++ b/docs/products/networking/nodebalancers/guides/protocols/index.md @@ -4,7 +4,7 @@ description: "Learn about each of the protocols that are available on NodeBalanc published: 2022-10-07 --- -Each port configured on a NodeBalancer must use one of the following available protocols. The protocol that's selected can determine the performance of your NodeBalancer, the settings available to you, and how to configure the backend machines. +Each port configured on a NodeBalancer must use one of the following available protocols. The protocol that's selected can determine the performance of your NodeBalancer, the settings available to you, and how to configure the back-end machines. - [TCP](#tcp) - [HTTP](#http) @@ -12,7 +12,7 @@ Each port configured on a NodeBalancer must use one of the following available p ## TCP -This mode acts as a TCP pass-through by forwarding all TCP requests to the backend machines. As such, it provides the most flexibility when compared to other protocol choices. Since it has the least amount of overhead, it is also more performant and +This mode acts as a TCP pass-through by forwarding all TCP requests to the back-end machines. As such, it provides the most flexibility when compared to other protocol choices. Since it has the least amount of overhead, it is also more performant and can service a high number of connections per second. The TCP protocol operates on the transport layer and supports any higher-layer protocol built on top of TCP/IP. - Supports HTTP, HTTPS, SSH, SMTP, FTP, DNS, and other application layer protocols @@ -21,7 +21,7 @@ can service a high number of connections per second. The TCP protocol operates o ## HTTP -When the HTTP protocol is selected, the HTTP request is terminated on the NodeBalancer and a new request is sent to the backend machines. While this does add some overhead, it enables features like HTTP cookie session stickiness. +When the HTTP protocol is selected, the HTTP request is terminated on the NodeBalancer and a new request is sent to the back-end machines. While this does add some overhead, it enables features like HTTP cookie session stickiness. - Supports HTTP/1.1 (not HTTP/2 or higher) - Supports the HTTP Cookie session stickiness method (in addition to other methods) @@ -31,10 +31,10 @@ When the HTTP protocol is selected, the HTTP request is terminated on the NodeBa ## HTTPS -HTTPS protocol contains the same functionality and support as the HTTP protocol, but requests between the client's machine and the NodeBalancer are encrypted using the TLS (or SSL) protocol. Since encrypted HTTPS requests are terminated on the NodeBalancer, you must add your TLS/SSL certificate to the NodeBalancer itself (instead of your backend machines). Once the HTTPS request is decrypted, the NodeBalancer sends unencrypted HTTP requests to the backend machines. +HTTPS protocol contains the same functionality and support as the HTTP protocol, but requests between the client's machine and the NodeBalancer are encrypted using the TLS (or SSL) protocol. Since encrypted HTTPS requests are terminated on the NodeBalancer, you must add your TLS/SSL certificate to the NodeBalancer itself (instead of your back-end machines). Once the HTTPS request is decrypted, the NodeBalancer sends unencrypted HTTP requests to the back-end machines. - Same core functionality as [HTTP](#http) - Supports TLS v1.2 and v1.3 - Requires a compatible TLS/SSL certificate and the associated private key -- HTTPS requests are terminated and decrypted on the NodeBalancer and traffic to the backend machines is *not* encrypted. +- HTTPS requests are terminated and decrypted on the NodeBalancer and traffic to the back-end machines is *not* encrypted. - Has the most overhead of all the protocol options, which means that it is less performant and accommodates fewer connections per second. \ No newline at end of file diff --git a/docs/products/networking/nodebalancers/guides/proxy-protocol/index.md b/docs/products/networking/nodebalancers/guides/proxy-protocol/index.md index c810e071b3b..425340f1918 100644 --- a/docs/products/networking/nodebalancers/guides/proxy-protocol/index.md +++ b/docs/products/networking/nodebalancers/guides/proxy-protocol/index.md @@ -1,6 +1,6 @@ --- title: Using Proxy Protocol with NodeBalancers -description: "Learn how to enable and use Proxy Protocol on your NodeBalancer to send client connection details to the backend nodes." +description: "Learn how to enable and use Proxy Protocol on your NodeBalancer to send client connection details to the back-end nodes." published: 2022-10-07 keywords: ["nodebalancers", "nodebalancer", "load balancers", "load balancer", "load balancing", "high availability", "ha", "proxy protocol", "proxy"] tags: ["cloud manager","linode platform","networking","web applications"] @@ -8,16 +8,16 @@ image: ProxyProtocol_NodeBalancers.png aliases: ['/platform/nodebalancer/nodebalancer-proxypass-configuration/','/guides/nodebalancer-proxypass-configuration/'] --- -When a Linode NodeBalancer passes a request from a client to a backend Node, information regarding the original client is not included by default. While this is fine for many environments, your applications may require original client information such as IP address or port. For these cases, Linode NodeBalancers support **Proxy Protocol** for TCP connections so that you can pass client information to backend Nodes. +When a Linode NodeBalancer passes a request from a client to a back-end node, information regarding the original client is not included by default. While this is fine for many environments, your applications may require original client information such as IP address or port. For these cases, Linode NodeBalancers support **Proxy Protocol** for TCP connections so that you can pass client information to back-end nodes. ## What is Proxy Protocol -Proxy Protocol is an internet protocol for various high availability and load balancing solutions to carry information about a client directly to backend servers. +Proxy Protocol is an internet protocol for various high availability and load balancing solutions to carry information about a client directly to back-end servers. -When selecting **TCP** as your NodeBalancer protocol, you can enable **Proxy Protocol** to add a header containing client information to backend Nodes. +When selecting **TCP** as your NodeBalancer protocol, you can enable **Proxy Protocol** to add a header containing client information to back-end nodes. {{< note >}} -[Backend Nodes](#configure-backend-node-proxy-protocol) must also have Proxy Protocol enabled on supported applications to receive the client information header. +[Back-end Nodes](#configure-backend-node-proxy-protocol) must also have Proxy Protocol enabled on supported applications to receive the client information header. Additional configuration options may need to be enabled on the application or service to accommodate traffic between the node and the NodeBalancer, including allowing IPv6 and/or IPv4 traffic, and enabling traffic on all necessary ports. {{< /note >}} @@ -44,13 +44,13 @@ More information on **v1** and **v2** is available in the [Proxy Protocol Specif ## Configure Proxy Protocol -In order to make use of Proxy Protocol, it needs to be configured on the NodeBalancer as well as each backend node Compute Instance. +In order to make use of Proxy Protocol, it needs to be configured on the NodeBalancer as well as each back-end node Compute Instance. ### Configure the NodeBalancer To enable Proxy Protocol for your NodeBalancer, follow the instructions below. -1. Log in to the [Cloud Manager](http://cloud.linode.com), click **NodeBalancers** in the left menu, and select the NodeBalancer you wish to edit. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/). +1. Log in to [Cloud Manager](http://cloud.linode.com), click **NodeBalancers** in the left menu, and select the NodeBalancer you wish to edit. See [Manage NodeBalancers](/docs/products/networking/nodebalancers/guides/manage/). 1. Navigate to the **Configurations** tab and open the port configuration you wish to edit. @@ -58,9 +58,9 @@ To enable Proxy Protocol for your NodeBalancer, follow the instructions below. 1. Click the **Save** button on the bottom of the page to Save your changes. -### Configure the Backend Nodes +### Configure the Back-end Nodes -Once Proxy Protocol is configured for your NodeBalancer, ensure that it is also enabled for the receiving software on your backend Nodes. You can find a list of compatible software in the [Proxy Protocol documentation](https://www.haproxy.com/blog/haproxy/proxy-protocol/). Here are links to guidance for enabling Proxy Protocol for common software: +Once Proxy Protocol is configured for your NodeBalancer, ensure that it is also enabled for the receiving software on your back-end Nodes. You can find a list of compatible software in the [Proxy Protocol documentation](https://www.haproxy.com/blog/haproxy/proxy-protocol/). Here are links to guidance for enabling Proxy Protocol for common software: - [NGINX](https://docs.nginx.com/nginx/admin-guide/load-balancer/using-proxy-protocol/) - [Apache](https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html) diff --git a/docs/products/networking/nodebalancers/guides/ssl-termination/index.md b/docs/products/networking/nodebalancers/guides/ssl-termination/index.md index c08f531573a..8b7c2902a91 100644 --- a/docs/products/networking/nodebalancers/guides/ssl-termination/index.md +++ b/docs/products/networking/nodebalancers/guides/ssl-termination/index.md @@ -19,7 +19,7 @@ Throughout this guide we will offer several suggested values for specific config - When first configuring back-end Linodes, you should set them up according to the instructions in our [Getting Started](/docs/products/platform/get-started/) guide. In addition, we recommend that you implement security precautions. For assistance with this, please see our guide on [Securing Your Server](/docs/products/compute/compute-instances/guides/set-up-and-secure/) -- Generate an [SSL certificate](/docs/guides/security/ssl/) for your domain name that supports TLS version 1.2 or later. This can be done through any Certificate Authority, including Let's Encrypt using the [Certbot](https://certbot.eff.org/) tool. Since Certbot cannot run directly on the NodeBalancer, run the following command on any Linode to generate the certificate (after following [Certbot's installation instructions](https://certbot.eff.org/instructions)). This allows you to manually verify ownership by updating a DNS record on your domain: +- Generate an [SSL certificate](/docs/guides/security/ssl/) for your domain name that supports TLS version 1.2 or later. This can be done through any Certificate Authority, including Let's Encrypt using the [Certbot](https://certbot.eff.org/) tool. Since Certbot cannot run directly on the NodeBalancer, run the following command on any Linode to generate the certificate (after following [Certbot's installation instructions](https://certbot.eff.org/instructions)). This lets you manually verify ownership by updating a DNS record on your domain: ```command sudo certbot certonly --key-type rsa --manual --preferred-challenges dns @@ -32,7 +32,7 @@ Throughout this guide we will offer several suggested values for specific config - [LAMP Stack](/docs/guides/web-servers/lamp/) - [LEMP Stack](/docs/guides/web-servers/lemp/) -- In addition, this guide assumes that you have already deployed a NodeBalancer and have configured it with two or more back-end Linodes that make connections on port 80/HTTP. We recommend that you first verify that your NodeBalancer is configured correctly, prior to introducing the complexities of an encrypted connection over SSL. If you would like assistance with setting up a basic NodeBalancer configuration, please review the following documentation: +- In addition, this guide assumes that you have already deployed a NodeBalancer and have configured it with two or more back-end Linodes that make connections on port 80/HTTP. We recommend that you first verify that your NodeBalancer is configured correctly, before introducing the complexities of an encrypted connection over SSL. If you would like assistance with setting up a basic NodeBalancer configuration, please review the following documentation: - [Getting Started with NodeBalancers](/docs/products/networking/nodebalancers/get-started/) - [NodeBalancer Reference Guide](/docs/products/networking/nodebalancers/guides/configure/) @@ -81,7 +81,7 @@ If your NodeBalancer must support users accessing your application with older br !RC4:HIGH:!aNULL:!MD5 ``` -However, bear in mind that by gaining backwards compatibility, your NodeBalancer will use weaker SSL/TLS cipher suites. For all other implementations, the default **Recommended** cipher suite option should be used, which includes: +However, bear in mind that by gaining backward compatibility, your NodeBalancer will use weaker SSL/TLS cipher suites. For all other implementations, the default **Recommended** cipher suite option should be used, which includes: ```command ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA @@ -200,7 +200,7 @@ openssl dhparam -out dhparams.pem 2048 ## Tips for Troubleshooting -- If you have difficulty getting the redirect to work properly or would like to see detailed information about how your SSL certificate is configured, you may wish to utilize the [Qualys online SSL Server Test](https://www.ssllabs.com/ssltest/) +- If you have difficulty getting the redirect to work properly or would like to see detailed information about how your SSL certificate is configured, you may wish to use the [Qualys online SSL Server Test](https://www.ssllabs.com/ssltest/) - Every time you make changes to your web server's document root file or other configuration files, be sure to reload the server: diff --git a/docs/products/networking/vlans/_index.md b/docs/products/networking/vlans/_index.md index 98cf42f9096..ce217fd7ba5 100644 --- a/docs/products/networking/vlans/_index.md +++ b/docs/products/networking/vlans/_index.md @@ -25,7 +25,7 @@ A VLAN creates a truly private network and communication is isolated to just the ### Simple Configuration -Use the Cloud Manager to create a VLAN and assign Compute Instances. Create up to 10 VLANs per data center and assign each Compute Instance to up to 3 VLANs. +Use Cloud Manager to create a VLAN and assign Compute Instances. Create up to 10 VLANs per data center and assign each Compute Instance to up to 3 VLANs. ### Reduce Network Transfer Costs diff --git a/docs/products/networking/vlans/developers/index.md b/docs/products/networking/vlans/developers/index.md index f2a62e16a1d..a44d18a472b 100644 --- a/docs/products/networking/vlans/developers/index.md +++ b/docs/products/networking/vlans/developers/index.md @@ -16,4 +16,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage your Linode resources](/docs/products/tools/cli/get-started/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage your Linode resources](/docs/products/tools/cli/get-started/). diff --git a/docs/products/networking/vlans/guides/_index.md b/docs/products/networking/vlans/guides/_index.md index 8312b66d08f..854855ccf08 100644 --- a/docs/products/networking/vlans/guides/_index.md +++ b/docs/products/networking/vlans/guides/_index.md @@ -8,9 +8,9 @@ tab_group_main: ## Basics -- [Use Cases](/docs/products/networking/vlans/guides/use-cases/): Learn how VLANs can be utilized by exploring some common scenarios. +- [Use Cases](/docs/products/networking/vlans/guides/use-cases/): Learn how VLANs can be used by exploring some common scenarios. -- [Getting Started with VLANs](/docs/products/networking/vlans/get-started/): An introduction to VLANs, including how to create and administer them within the Cloud Manager. +- [Getting Started with VLANs](/docs/products/networking/vlans/get-started/): An introduction to VLANs, including how to create and administer them within Cloud Manager. - [Attach a VLAN to a Compute Instance](/docs/products/networking/vlans/guides/attach-to-compute-instance/): Learn how to create a VLAN and attach it to a new or existing Compute Instance. diff --git a/docs/products/networking/vlans/guides/attach-to-compute-instance/index.md b/docs/products/networking/vlans/guides/attach-to-compute-instance/index.md index aabe6bd3de2..d31c9bc7343 100644 --- a/docs/products/networking/vlans/guides/attach-to-compute-instance/index.md +++ b/docs/products/networking/vlans/guides/attach-to-compute-instance/index.md @@ -4,16 +4,16 @@ description: "Learn how to create a VLAN and attach it to a new or existing Comp modified: 2022-08-23 --- -Within the Cloud Manager, VLANs are created and managed only by attaching them to Linode Compute Instances. They are not managed independently. You can attach a VLAN when creating a new Compute Instance or when editing an existing instance. +Within Cloud Manager, VLANs are created and managed only by attaching them to Linode Compute Instances. They are not managed independently. You can attach a VLAN when creating a new Compute Instance or when editing an existing instance. - [Attaching a VLAN When Creating a Compute Instance](#attaching-a-vlan-when-creating-a-compute-instance) - [Attaching a VLAN to an Existing Compute Instance](#attaching-a-vlan-to-an-existing-compute-instance) -This guide covers implementing both of these methods using the Cloud Manager. While VLANs can also be created and administered through the API and CLI, that's beyond the scope of this guide. +This guide covers implementing both of these methods using Cloud Manager. While VLANs can also be created and administered through the API and CLI, that's beyond the scope of this guide. ## Attaching a VLAN When Creating a Compute Instance -1. On the top left of the [Cloud Manager](https://cloud.linode.com/dashboard), click **Create** and select **Linode**. +1. On the top left of [Cloud Manager](https://cloud.linode.com/dashboard), click **Create** and select **Linode**. ![Create a new Compute Instance](create-new-linode.png) @@ -40,7 +40,7 @@ By default, the public IP address (and, if added, the private IP address) of the ## Attaching a VLAN to an Existing Compute Instance -1. Within the [Cloud Manager](https://www.cloud.linode.com), click the **Linodes** link in the sidebar and select a Compute Instance. +1. Within [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar and select a Compute Instance. 1. Navigate to the **Configurations** tab for that Compute Instance. diff --git a/docs/products/networking/vlans/guides/manage-vlans-using-linode-api/index.md b/docs/products/networking/vlans/guides/manage-vlans-using-linode-api/index.md index ffde9002736..237d7fdced7 100644 --- a/docs/products/networking/vlans/guides/manage-vlans-using-linode-api/index.md +++ b/docs/products/networking/vlans/guides/manage-vlans-using-linode-api/index.md @@ -133,7 +133,7 @@ An `image` must be specified to set interfaces when creating a new Linode. You can attach a VLAN to an existing Linode by either creating a new configuration profile or updating an existing configuration profile for the Linode. In either case, the Linode must be rebooted to allow Network Helper to automatically adjust the necessary network configuration files on the Linode. -The Linode's ID is required to utilize these methods. Use the Linodes List ([GET /linode/instances](/docs/api/linode-instances/#linodes-list)) endpoint to retrieve the IDs of each of your Linodes. To view the Disk IDs of a Linode, use the Disks List ([GET /linode/instances/{linodeId}/disks](/docs/api/linode-instances/#disks-list)) endpoint. +The Linode's ID is required to use these methods. Use the Linodes List ([GET /linode/instances](/docs/api/linode-instances/#linodes-list)) endpoint to retrieve the IDs of each of your Linodes. To view the Disk IDs of a Linode, use the Disks List ([GET /linode/instances/{linodeId}/disks](/docs/api/linode-instances/#disks-list)) endpoint. ### Creating a Configuration Profile diff --git a/docs/products/networking/vlans/guides/manually-configuring-a-vlan/index.md b/docs/products/networking/vlans/guides/manually-configuring-a-vlan/index.md index aef665d03a8..7c3ccc746bd 100644 --- a/docs/products/networking/vlans/guides/manually-configuring-a-vlan/index.md +++ b/docs/products/networking/vlans/guides/manually-configuring-a-vlan/index.md @@ -11,7 +11,7 @@ This guide is for users that have disabled Network Helper on their Compute Insta ## Ubuntu 18.04 and Later -Ubuntu Server 18.04 and later versions use Netplan to configure networking, with systemd-networkd operating as the backend. Network configuration files for each interface are located in `/etc/systemd/network/`: +Ubuntu Server 18.04 and later versions use Netplan to configure networking, with systemd-networkd operating as the back end. Network configuration files for each interface are located in `/etc/systemd/network/`: - **eth0**: `/etc/systemd/network/05-eth0.network` - **eth1**: `/etc/systemd/network/05-eth1.network` diff --git a/docs/products/networking/vlans/guides/remove-a-compute-instance/index.md b/docs/products/networking/vlans/guides/remove-a-compute-instance/index.md index d82d217bd0b..b5afa7829bf 100644 --- a/docs/products/networking/vlans/guides/remove-a-compute-instance/index.md +++ b/docs/products/networking/vlans/guides/remove-a-compute-instance/index.md @@ -6,7 +6,7 @@ aliases: ['/products/networking/vlans/guides/detach-a-linode-from-your-vlan/'] If you no longer wish to include a particular Compute Instance within a VLAN's private network, the VLAN can be detached by editing that instance's [Configuration Profile](/docs/products/compute/compute-instances/guides/configuration-profiles/#edit-a-configuration-profile). -1. Within the [Cloud Manager](https://www.cloud.linode.com), click the **Linodes** link in the sidebar and select a Compute Instance. +1. Within [Cloud Manager](https://cloud.linode.com), click the **Linodes** link in the sidebar and select a Compute Instance. 1. Navigate to the **Configurations** tab for that Compute Instance. diff --git a/docs/products/networking/vpc/_index.md b/docs/products/networking/vpc/_index.md index a63fe394af0..c6e2691fa91 100644 --- a/docs/products/networking/vpc/_index.md +++ b/docs/products/networking/vpc/_index.md @@ -25,7 +25,7 @@ Networking packets sent over a VPC are walled off from the public internet --- a ## Segment Traffic Into Separate Subnets -Instead of assigning a single IPv4 range for the entire VPC, Akamai's VPC design allows users to configure multiple RFC1918 ranges through the use of subnets. This has the benefit of segmenting services into distinct networks and can be useful when migrating or combining existing networking environments so that there are no changes to routing or static IPs. These subnets can isolate various functionality of an application (such as separating public frontend services from private backend services) or separate out a production environment from staging or development. +Instead of assigning a single IPv4 range for the entire VPC, Akamai's VPC design allows users to configure multiple RFC1918 ranges through the use of subnets. This has the benefit of segmenting services into distinct networks and can be useful when migrating or combining existing networking environments so that there are no changes to routing or static IPs. These subnets can isolate various functionality of an application (such as separating public front-end services from private back-end services) or separate out a production environment from staging or development. Routing between subnets on a VPC is configured automatically. By default, all Compute Instances on a VPC can communicate with any other instance on that VPC, regardless of which subnet the other instance is assigned to use. diff --git a/docs/products/networking/vpc/developers/index.md b/docs/products/networking/vpc/developers/index.md index 210e2c5e731..50c72081b8a 100644 --- a/docs/products/networking/vpc/developers/index.md +++ b/docs/products/networking/vpc/developers/index.md @@ -9,4 +9,4 @@ tab_group_main: ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage your Linode resources](/docs/products/tools/cli/get-started/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage your Linode resources](/docs/products/tools/cli/get-started/). diff --git a/docs/products/networking/vpc/get-started/index.md b/docs/products/networking/vpc/get-started/index.md index ea74b4ce308..496fbd40dff 100644 --- a/docs/products/networking/vpc/get-started/index.md +++ b/docs/products/networking/vpc/get-started/index.md @@ -15,7 +15,7 @@ Consider your application's requirements and determine how your application shou ## Create a VPC -Once you've determined that a VPC is needed, you can create it directly in the Cloud Manager using the Create VPC form or by deploying a new Compute Instance and entering a new VPC. During this process, you'll need to define the following parameters: +Once you've determined that a VPC is needed, you can create it directly in Cloud Manager using the Create VPC form or by deploying a new Compute Instance and entering a new VPC. During this process, you'll need to define the following parameters: - **Region:** The data center where the VPC is deployed. Since VPCs are region-specific, only Compute Instances within that region can join the VPC. - **Label:** A string to identify the VPC. This should be unique to your account. diff --git a/docs/products/networking/vpc/guides/_index.md b/docs/products/networking/vpc/guides/_index.md index 61b47e995ae..0aa8190c906 100644 --- a/docs/products/networking/vpc/guides/_index.md +++ b/docs/products/networking/vpc/guides/_index.md @@ -10,9 +10,9 @@ tab_group_main: ## Basics -- [Getting Started with VPCs](/docs/products/networking/vpc/get-started/): An introduction to VPCs, including how to create and administer them within the Cloud Manager. +- [Getting Started with VPCs](/docs/products/networking/vpc/get-started/): An introduction to VPCs, including how to create and administer them within Cloud Manager. -- [Create a VPC](/docs/products/networking/vpc/guides/create/): Outlines how to create a VPC using the Cloud Manager, Linode CLI, and Linode API. +- [Create a VPC](/docs/products/networking/vpc/guides/create/): Outlines how to create a VPC using Cloud Manager, Linode CLI, and Linode API. - [Manage VPCs](/docs/products/networking/vpc/guides/manage-vpcs/): Instructions on viewing, editing, and deleting VPCs. diff --git a/docs/products/networking/vpc/guides/assign-services/index.md b/docs/products/networking/vpc/guides/assign-services/index.md index 74e6b3ef1d4..26d5ae5e9ad 100644 --- a/docs/products/networking/vpc/guides/assign-services/index.md +++ b/docs/products/networking/vpc/guides/assign-services/index.md @@ -47,7 +47,7 @@ When creating a new Compute Instance, you have the option to assign it to an exi If a Compute Instance is created with a VPC, the VPC is automatically enabled on the `eth0` network interface. No other network interfaces are configured. An exception to that is if the Compute Instance is also configured with a **Private IP** address (which is not recommended). In this case, the `eth1` network interface is configured as _Public Internet_. -![Screenshot of the VPC section of the Create Linode screen in the Cloud Manager](create-instance-vpc.jpg) +![Screenshot of the VPC section of the Create Linode screen in Cloud Manager](create-instance-vpc.jpg) ## Use the VPC Management Workflows to Assign an Existing Compute Instance {#assign-existing-instance-with-vpc-management-workflows} @@ -75,7 +75,7 @@ Every Compute Instance can have up to three network interfaces (Public, VPC, and If you wish for an instance to be configured on a VPC, the _VPC_ option needs to be selected on at least one interface. In most cases, a VPC should be configured on the first network interface (`eth0`). Configuring a VPC on other interfaces prevent the instance from communicating with other subnets in the same VPC. For more details regarding configuring network interfaces, review the [Configuration Profile Settings](/docs/products/compute/compute-instances/guides/configuration-profiles/#settings). -1. Within the [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](/docs/products/compute/compute-instances/guides/configuration-profiles/#view-configuration-profiles). +1. Within [Cloud Manager](https://cloud.linode.com), view the Configuration Profiles for your desired Compute Instance. See [View Configuration Profiles](/docs/products/compute/compute-instances/guides/configuration-profiles/#view-configuration-profiles). 1. Within the **Configurations** table, locate the configuration profile you wish to modify and click the corresponding **Edit** button, which may also appear within the **ellipsis** menu. This displays the **Edit Configuration** form. In most cases, there should be only one configuration profile. @@ -87,7 +87,7 @@ If you wish for an instance to be configured on a VPC, the _VPC_ option needs to - **VPC:** To assign this instance to a VPC, select the VPC from the **VPC** dropdown menu. If you do not yet have a VPC in the selected data center, click the **Create a VPC** button and follow the instructions on the [Create a VPC](/docs/products/networking/vpc/guides/create/) guide. - - **Subnet:** An instance can be assigned to a single subnet, which allows you to further segment traffic and services within a VPC. Select the desired subnet within the **Subnet** dropdown menu. + - **Subnet:** An instance can be assigned to a single subnet, which lets you further segment traffic and services within a VPC. Select the desired subnet within the **Subnet** dropdown menu. - **Auto-Assign IPv4 address:** By default, an IPv4 address will be automatically generated for the instance on the subnet’s defined CIDR range. If you want to manually assign an IP address, uncheck the **Auto-assign a VPC IPv4 address for this Linode** option and enter your custom IPv4 address. This address must still be within the subnet’s IP range. diff --git a/docs/products/networking/vpc/guides/create/index.md b/docs/products/networking/vpc/guides/create/index.md index 8ad97dba434..17913e65781 100644 --- a/docs/products/networking/vpc/guides/create/index.md +++ b/docs/products/networking/vpc/guides/create/index.md @@ -6,7 +6,7 @@ published: 2024-01-09 keywords: ["getting started", "deploy", "linode", "linux"] --- -This guide walks you through creating a VPC through the Cloud Manager, Linode CLI, and Linode API. +This guide walks you through creating a VPC through Cloud Manager, Linode CLI, and Linode API. 1. [Get Started](#get-started) 1. [Set the Basic Parameters](#set-the-basic-parameters) @@ -16,11 +16,11 @@ This guide walks you through creating a VPC through the Cloud Manager, Linode CL ## Get Started -Open the Create Form in the Cloud Manager or start entering your Linode CLI or Linode API command. +Open the Create Form in Cloud Manager or start entering your Linode CLI or Linode API command. {{< tabs >}} {{< tab "Cloud Manager" >}} -Log in to the [Cloud Manager](https://cloud.linode.com/), click the **Create** dropdown menu on the top bar, and select *VPC*. This opens the **Create VPC** form. +Log in to [Cloud Manager](https://cloud.linode.com/), click the **Create** dropdown menu on the top bar, and select *VPC*. This opens the **Create VPC** form. {{< /tab >}} {{< tab "Linode CLI" >}} Within your terminal, paste the command provided below. If you do not have the Linode CLI, review the [Install and Configure the Linode CLI](/docs/products/tools/cli/guides/install/) guide. **Before submitting the request, read through the rest of this document.** @@ -110,7 +110,7 @@ For each additional subnet you wish to create, press the **Add Another Subnet** ## Deploy the VPC -Once all fields have been entered, you can click the **Create VPC** button in the Cloud Manager or run the Linode CLI or Linode API command. If you are using the Cloud Manager, you are taken to the VPC's details page where you can view and edit the VPC and its subnets. +Once all fields have been entered, you can click the **Create VPC** button in Cloud Manager or run the Linode CLI or Linode API command. If you are using Cloud Manager, you are taken to the VPC's details page where you can view and edit the VPC and its subnets. ## Next Steps diff --git a/docs/products/networking/vpc/guides/manage-vpcs/index.md b/docs/products/networking/vpc/guides/manage-vpcs/index.md index 636b93a20b2..2f982b092eb 100644 --- a/docs/products/networking/vpc/guides/manage-vpcs/index.md +++ b/docs/products/networking/vpc/guides/manage-vpcs/index.md @@ -6,17 +6,17 @@ published: 2024-01-30 ## View VPCs -Log in to the [Cloud Manager](https://cloud.linode.com/) and select **VPC** in the sidebar. If any VPCs exist on your account, they are listed on this page. +Log in to [Cloud Manager](https://cloud.linode.com/) and select **VPC** in the sidebar. If any VPCs exist on your account, they are listed on this page. -![Screenshot of the VPC page in the Cloud Manager](vpc-list.jpg) +![Screenshot of the VPC page in Cloud Manager](vpc-list.jpg) Each VPC is listed along with the region it is located within, its ID, the number of subnets, and the number of Compute Instances that are assigned. ## Review and Edit a VPC -Navigate to the **VPCs** page in the Cloud Manager and locate the VPC you wish to edit. See [View VPCs](#view-vpcs). Click the name of the VPC to be taken to its details page. +Navigate to the **VPCs** page in Cloud Manager and locate the VPC you wish to edit. See [View VPCs](#view-vpcs). Click the name of the VPC to be taken to its details page. -![Screenshot of the VPC summary in the Cloud Manager](vpc-details.jpg) +![Screenshot of the VPC summary in Cloud Manager](vpc-details.jpg) This displays the summary of the VPC along with a list of subnets within the VPC. To edit the VPC label or description, click the **Edit** button within the *Summary* section. The data center assignment cannot be changed. Once a VPC has been created, you cannot move it to a different data center. diff --git a/docs/products/networking/vpc/guides/subnets/index.md b/docs/products/networking/vpc/guides/subnets/index.md index 92b94b3a48c..3c292afb76a 100644 --- a/docs/products/networking/vpc/guides/subnets/index.md +++ b/docs/products/networking/vpc/guides/subnets/index.md @@ -4,7 +4,7 @@ description: "Learn how to view, edit, and delete subnets within Akamai's VPC so published: 2024-01-30 --- -A VPC contains one or more _subnets_, which are networks within the VPC whose services all share the same IPv4 CIDR range. Just like VPCs, subnets are restricted to a single data center. Multiple subnets can be added to isolate services that are used for certain functionality of an application (like frontend and backend services) or can segment a VPC and its attached services into different environments (such as development, staging, and production). +A VPC contains one or more _subnets_, which are networks within the VPC whose services all share the same IPv4 CIDR range. Just like VPCs, subnets are restricted to a single data center. Multiple subnets can be added to isolate services that are used for certain functionality of an application (like front end and back-end services) or can segment a VPC and its attached services into different environments (such as development, staging, and production). ## Subnet Components @@ -31,7 +31,7 @@ When defining an IPv4 range for a subnet, use a CIDR block within the [RFC1918]( ## View Subnets -1. View the [VPCs](https://cloud.linode.com/vpcs) page in the Cloud Manager. See [View VPCs](/docs/products/networking/vpc/guides/manage-vpcs/#view-vpcs). +1. View the [VPCs](https://cloud.linode.com/vpcs) page in Cloud Manager. See [View VPCs](/docs/products/networking/vpc/guides/manage-vpcs/#view-vpcs). 1. Locate and click the name of the VPC you wish to inspect. This displays the details page for that VPC. diff --git a/docs/products/platform/accounts/developers/index.md b/docs/products/platform/accounts/developers/index.md index ed9691aea7b..a3fdd6c81fd 100644 --- a/docs/products/platform/accounts/developers/index.md +++ b/docs/products/platform/accounts/developers/index.md @@ -31,4 +31,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [manage your account](/docs/products/tools/cli/guides/account/) +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [manage your account](/docs/products/tools/cli/guides/account/) diff --git a/docs/products/platform/accounts/guides/2fa/index.md b/docs/products/platform/accounts/guides/2fa/index.md index 902feb321aa..59536f37b4b 100644 --- a/docs/products/platform/accounts/guides/2fa/index.md +++ b/docs/products/platform/accounts/guides/2fa/index.md @@ -46,7 +46,7 @@ There are quite a few free (and paid) third-party authenticator applications ava Enable two-factor authentication to start using it with your Cloud Manager account. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click your username in the top right of the screen and select **Login & Authentication**. @@ -66,9 +66,9 @@ Enable two-factor authentication to start using it with your Cloud Manager accou 1. Open the app for your preferred 2FA provider on your smartphone or desktop. For help choosing a provider, see [Choosing a 2FA Provider](#choosing-a-2fa-provider). -1. The next step is to configure the app to automatically generate OTP tokens for use with Cloud Manager's 2FA feature. The process varies depending on the app you are using. Within most dedicated authenticator apps, you can add an account. For password managers, edit or add a Cloud Manager login entry and add a one-time passcode (1Password), two-factor code (Keeper), or the equivalent field within your app. Then either scan the Cloud Manager's 2FA QR code or manually enter the secret key (also called a setup key or code). On mobile devices, you can use your phone's camera to scan the QR code. Desktop applications instead can typically scan the QR through their own custom screen capture tool. If you need further help, you can consult the documentation for your 2FA provider. +1. The next step is to configure the app to automatically generate OTP tokens for use with Cloud Manager's 2FA feature. The process varies depending on the app you are using. Within most dedicated authenticator apps, you can add an account. For password managers, edit or add a Cloud Manager login entry and add a one-time passcode (1Password), two-factor code (Keeper), or the equivalent field within your app. Then either scan Cloud Manager's 2FA QR code or manually enter the secret key (also called a setup key or code). On mobile devices, you can use your phone's camera to scan the QR code. Desktop applications instead can typically scan the QR through their own custom screen capture tool. If you need further help, you can consult the documentation for your 2FA provider. -1. Once 2FA has been configured in your 2FA provider, a time-sensitive OTP token is generated. This token refreshes every 30 seconds. Copy this token and, within the Cloud Manager, paste it to the **Token** field and click **Confirm Token**. +1. Once 2FA has been configured in your 2FA provider, a time-sensitive OTP token is generated. This token refreshes every 30 seconds. Copy this token and, within Cloud Manager, paste it to the **Token** field and click **Confirm Token**. ![Enter the 2FA token](confirm-2fa-token.png) @@ -76,15 +76,15 @@ Enable two-factor authentication to start using it with your Cloud Manager accou ## Logging in When 2FA Is Enabled -If 2FA is enabled on your account, you must enter the OTP generated by your 2FA provider when you log in to the Cloud Manager. +If 2FA is enabled on your account, you must enter the OTP generated by your 2FA provider when you log in to Cloud Manager. -1. Open the [Cloud Manager](https://cloud.linode.com) in your web browser. If you are not already logged in, the Login page appears. +1. Open [Cloud Manager](https://cloud.linode.com) in your web browser. If you are not already logged in, the Login page appears. 1. Enter your username and password and click **Log in**. If you wish, you can also select *Trust this device for 30 days* to stay logged in for 30 days. If 2FA is enabled on your account, a form appears requesting your OTP token or scratch code. 1. Open the authenticator app you are using to manage your 2FA and OTP tokens. Within this app, open the Linode Cloud Manager account or login entry to view the time-sensitive OTP code. -1. Enter your OTP token into the **Token** field in the Cloud Manager and then click the **Verify** button. Provided the token is correct, you are successfully logged in. +1. Enter your OTP token into the **Token** field in Cloud Manager and then click the **Verify** button. Provided the token is correct, you are successfully logged in. ![Screenshot of the 2FA entry form](login-with-2fa.png) @@ -94,9 +94,9 @@ If 2FA is enabled on your account, you must enter the OTP generated by your 2FA ## Switching to a New Device or 2FA Provider -If you need to switch your 2FA provider or change the device in use by your two-factor authenticator app, you can do so within the Cloud Manager. To successfully log in to the Cloud Manager, you must have access to your original 2FA provider or device. If you've lost your device or otherwise don't have access, see the [Recovery Procedure](#recovery-procedure) below. +If you need to switch your 2FA provider or change the device in use by your two-factor authenticator app, you can do so within Cloud Manager. To successfully log in to Cloud Manager, you must have access to your original 2FA provider or device. If you've lost your device or otherwise don't have access, see the [Recovery Procedure](#recovery-procedure) below. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Navigate to the Login & Authentication page of your profile by clicking on your **username** in the top right of the screen. Select **Login & Authentication** from the dropdown menu. @@ -110,7 +110,7 @@ If you need to switch your 2FA provider or change the device in use by your two- You can disable two-factor authentication for your Cloud Manager account at any time. Here's how: -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Navigate to the Login & Authentication page of your profile by clicking on your **username** in the top right of the screen. Select **Login & Authentication** from the dropdown menu. @@ -122,7 +122,7 @@ You have successfully disabled the two-factor authentication feature for your Li ## Recovery Procedure -If you lose access to your 2FA provider, you can still log in using the scratch code that was generated when you first enabled 2FA. If you do not have that scratch code, you will be unable to log in to the Cloud Manager and will need to contact the Customer Support team to request 2FA removal. See the instructions below for specific recovery steps. +If you lose access to your 2FA provider, you can still log in using the scratch code that was generated when you first enabled 2FA. If you do not have that scratch code, you will be unable to log in to Cloud Manager and will need to contact the Customer Support team to request 2FA removal. See the instructions below for specific recovery steps. - [With Scratch Code](#with-scratch-code) - [With Security Questions](#with-security-questions) diff --git a/docs/products/platform/accounts/guides/cancel-account/index.md b/docs/products/platform/accounts/guides/cancel-account/index.md index ed730c2853e..8722603adba 100644 --- a/docs/products/platform/accounts/guides/cancel-account/index.md +++ b/docs/products/platform/accounts/guides/cancel-account/index.md @@ -1,7 +1,7 @@ --- title: Cancel Your Account title_meta: "How to Cancel an Account on the Linode Platform" -description: "Learn how to cancel a Linode account through the Cloud Manager." +description: "Learn how to cancel a Linode account through Cloud Manager." published: 2021-06-25 modified: 2023-03-02 tags: ["linode platform","cloud manager"] @@ -10,7 +10,7 @@ aliases: ['/guides/how-to-cancel-your-account/','/quick-answers/linode-platform/ A Linode account enables you to deploy and use services on the Linode Platform. If you no longer wish to use the Linode Platform, you can cancel your account at any time. When you cancel your account, any past due balance and uninvoiced balance remaining on your account is immediately charged to the default payment method on file, minus any remaining account credits. -You do not have to cancel your account to prevent recurring charges. Instead, you can remove all services from your account via the Cloud Manager, Linode API, or Linode CLI. This allows you to retain your Linode account if you intend to use it in the future. See [Removing Services](/docs/products/platform/billing/guides/stop-billing/) for more information. +You do not have to cancel your account to prevent recurring charges. Instead, you can remove all services from your account via Cloud Manager, Linode API, or Linode CLI. This lets you retain your Linode account if you intend to use it in the future. See [Removing Services](/docs/products/platform/billing/guides/stop-billing/) for more information. {{< note >}} Linode provides a 7-day guarantee for all paid services. If you cancel your account within the first 7 days, you are likely eligible to receive a full refund for any service charges paid with a valid payment method (not with an account credit or promotional code). To request this refund, enter a note in the cancellation form or email support@linode.com with your request. @@ -23,4 +23,4 @@ Linode provides a 7-day guarantee for all paid services. If you cancel your acco 1. A confirmation form appears. Enter your Linode username in the first field and optionally enter any comments you'd like to leave in the second field. Any refund requests can be entered here as well. See the [Refunds](/docs/products/platform/billing/#refunds) section of the Billing guide. 1. Click the **Close Account** button to complete your account cancellation. Any past due balance and uninvoiced balance is immediately charged to the credit card on file for your account. After that, you will receive no further charges from Linode regarding this account. -After following these instructions, all of your services are immediately marked for deletion and your account is immediately cancelled. You are no longer able to log in through the Cloud Manager. \ No newline at end of file +After following these instructions, all of your services are immediately marked for deletion and your account is immediately cancelled. You are no longer able to log in through Cloud Manager. \ No newline at end of file diff --git a/docs/products/platform/accounts/guides/change-user-email/index.md b/docs/products/platform/accounts/guides/change-user-email/index.md index b19c136b4b5..94d17420aa0 100644 --- a/docs/products/platform/accounts/guides/change-user-email/index.md +++ b/docs/products/platform/accounts/guides/change-user-email/index.md @@ -19,7 +19,7 @@ See [Update Billing Contact Information](/docs/products/platform/billing/guides/ ## Modify User Account Email -Use the **Users & Grants** page to modify the email address associated with a user account. The email addresses listed on this page receive IP whitelist warnings, password reset messages, and support tickets for services that their associated users have permission to access. Users with limited account access can also receive invoices and receipts if granted access to that information. +Use the **Users & Grants** page to modify the email address associated with a user account. The email addresses listed on this page receive password reset messages and support tickets for services that their associated users have permission to access. Users with limited account access can also receive invoices and receipts if granted access to that information. {{< note >}} Only full account access users can receive threshold notification emails. @@ -39,5 +39,5 @@ Here's how to change a user's email from the **Users & Grants** page: The user's email address is now updated. {{< note >}} -If you do not have full account access, you can view your user profile settings and update your email address by clicking on your username at the top of the Cloud Manager screen and selecting **Display**. +If you do not have full account access, you can view your user profile settings and update your email address by clicking on your username at the top of Cloud Manager and selecting **Display**. {{< /note >}} \ No newline at end of file diff --git a/docs/products/platform/accounts/guides/manage-api-tokens/index.md b/docs/products/platform/accounts/guides/manage-api-tokens/index.md index 4de0206bda6..772e94c001d 100644 --- a/docs/products/platform/accounts/guides/manage-api-tokens/index.md +++ b/docs/products/platform/accounts/guides/manage-api-tokens/index.md @@ -7,7 +7,7 @@ published: 12-06-2022 ## View Personal Access Tokens -1. Log in to the [Cloud Manager](https://cloud.linode.com) +1. Log in to [Cloud Manager](https://cloud.linode.com) 1. Click on your username at the top of the screen and select **API Tokens** under the *My Profile* section. @@ -15,7 +15,7 @@ published: 12-06-2022 This displays the **API Tokens** tab on the **My Profile** page. -![Screenshot of personal access tokens in the Cloud Manager](view-personal-access-tokens.png) +![Screenshot of personal access tokens in Cloud Manager](view-personal-access-tokens.png) Any personal access tokens you have previously created on your Linode account are listed here. Alongside each token is the date it was created, the date it expires, and links to view the scopes, rename the token, or revoke the token. @@ -23,13 +23,13 @@ Any personal access tokens you have previously created on your Linode account ar Whenever you need to authorize API access to an application or service, you should create a new personal access token. This token should only allow the level of access needed by the application. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and navigate to the API Tokens page of the My Profile section. See [View Personal Access Tokens](#view-personal-access-tokens). +1. Log in to [Cloud Manager](https://cloud.linode.com) and navigate to the API Tokens page of the My Profile section. See [View Personal Access Tokens](#view-personal-access-tokens). 1. Click the **Create a Personal Access Token** button to display the *Add Personal Access Token* panel. ![Screenshot of the Add Personal Access Token form](create-token.png) -1. Enter a **Label** for this new token. Choose a label that allows you to identify the token and understand its intended use. +1. Enter a **Label** for this new token. Choose a label that lets you identify the token and understand its intended use. 1. In the **Expiry** field dropdown menu, select a timeline for when the new token expires. You can optionally allow this token to never expire. *This cannot be changed once the token is created.* @@ -43,7 +43,7 @@ Whenever you need to authorize API access to an application or service, you shou If you wish to decommission a token or think it may have been compromised, you can revoke access. Once revoked, any application using this token will no longer be authorized to access your account through the Linode API. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and navigate to the API Tokens page of the My Profile section. See [View Personal Access Tokens](#view-personal-access-tokens). +1. Log in to [Cloud Manager](https://cloud.linode.com) and navigate to the API Tokens page of the My Profile section. See [View Personal Access Tokens](#view-personal-access-tokens). 1. Find the token you wish to revoke and click the corresponding **Revoke** button, which may be visible within the ***more options ellipsis*** menu. diff --git a/docs/products/platform/accounts/guides/manage-ssh-keys/index.md b/docs/products/platform/accounts/guides/manage-ssh-keys/index.md index 87f4fa4188a..87d82a21124 100644 --- a/docs/products/platform/accounts/guides/manage-ssh-keys/index.md +++ b/docs/products/platform/accounts/guides/manage-ssh-keys/index.md @@ -1,18 +1,18 @@ --- title: "Manage SSH Keys" -description: "Learn how to view, upload, and remove your public SSH keys in the Cloud Manager." +description: "Learn how to view, upload, and remove your public SSH keys in Cloud Manager." published: 2022-03-18 modified: 2023-05-22 aliases: ['/products/tools/cloud-manager/guides/manage-ssh-keys/'] --- -When creating a Compute Instance, you have the opportunity to select one or more SSH keys, which are added to the root user account of the new instance. This allows you to login over SSH using your associated private key instead of the root password. +When creating a Compute Instance, you have the opportunity to select one or more SSH keys, which are added to the root user account of the new instance. This lets you login over SSH using your associated private key instead of the root password. -These SSH keys are stored within your Linode account and can be easily accessed from the Cloud Manager. This guide walks you through how to view, add, and remove your account's SSH keys. For instructions on selecting an SSH key when deploying a Compute Instance see [Creating a Compute Instance > Create a Password and Add SSH Keys](/docs/products/compute/compute-instances/guides/create/#create-a-password-and-add-ssh-keys). +These SSH keys are stored within your Linode account and can be easily accessed from Cloud Manager. This guide walks you through how to view, add, and remove your account's SSH keys. For instructions on selecting an SSH key when deploying a Compute Instance see [Creating a Compute Instance > Create a Password and Add SSH Keys](/docs/products/compute/compute-instances/guides/create/#create-a-password-and-add-ssh-keys). ## View SSH Keys -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click on your username on the top right and select **SSH Keys** in the dropdown menu that appears: @@ -30,7 +30,7 @@ Add a public SSH key to your Linode user account so that you can easily install The following SSH key formats are supported: **ssh-rsa**, **ssh-dss**, **ecdsa-sha2-nistp**, **ssh-ed25519**, and **sk-ecdsa-sha2-nistp256** (an Akamai-specific format). {{< /note >}} -1. Access the **SSH Keys** page in the Cloud Manager. See [View SSH Keys](#view-ssh-keys) above. +1. Access the **SSH Keys** page in Cloud Manager. See [View SSH Keys](#view-ssh-keys) above. 1. Click the **Add an SSH Key** button. @@ -54,9 +54,9 @@ The following SSH key formats are supported: **ssh-rsa**, **ssh-dss**, **ecdsa-s ## Remove a Public Key -If you no longer wish to deploy *new* Compute Instances with a certain SSH key, you can remove it from the Cloud Manager. When doing so, the SSH key is *not removed* from any existing Compute Instances that may have used it. +If you no longer wish to deploy *new* Compute Instances with a certain SSH key, you can remove it from Cloud Manager. When doing so, the SSH key is *not removed* from any existing Compute Instances that may have used it. -1. Access the **SSH Keys** page in the Cloud Manager. See [View SSH Keys](#view-ssh-keys) above. +1. Access the **SSH Keys** page in Cloud Manager. See [View SSH Keys](#view-ssh-keys) above. 1. Within the list that appears, locate the public key you wish to remove. Then, click the corresponding **Delete** link. diff --git a/docs/products/platform/accounts/guides/manage-users/index.md b/docs/products/platform/accounts/guides/manage-users/index.md index aa3a4af6877..93fea21d7ec 100644 --- a/docs/products/platform/accounts/guides/manage-users/index.md +++ b/docs/products/platform/accounts/guides/manage-users/index.md @@ -13,11 +13,11 @@ A single user was automatically created for your account when you signed up for ## View All Users -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select **Account** from the sidebar menu. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select **Account** from the sidebar menu. 1. Navigate to the **Users & Grants** tab to display all users on the account. *Your user account must have full unrestricted access to view this page.* -![Screenshot of Users and Grants page in the Cloud Manager](view-users.png) +![Screenshot of Users and Grants page in Cloud Manager](view-users.png) Each user is listed in the table along with its username, email address, and the level of account access (*full* or *limited*). @@ -25,7 +25,7 @@ Each user is listed in the table along with its username, email address, and the To provide another person with access to your Linode account, you can create another user. Each user can be created with full unrestricted access or limited restricted access. For more details on user permissions, see [Set User Permissions](/docs/products/platform/accounts/guides/user-permissions/). -1. Navigate to the **Users & Grants** page in the Cloud Manager. See [View All Users](#view-all-users). +1. Navigate to the **Users & Grants** page in Cloud Manager. See [View All Users](#view-all-users). 1. Click the **Add a User** button to open the new user panel. @@ -51,7 +51,7 @@ In a couple minutes, you'll receive an email message with any Linode Cloud Manag You can permanently remove a user account from the Linode Cloud Manager. Here's how: -1. Navigate to the **Users & Grants** page in the Cloud Manager. See [View All Users](#view-all-users). +1. Navigate to the **Users & Grants** page in Cloud Manager. See [View All Users](#view-all-users). 1. Click the **Delete** link for the desired user. A warning appears asking you to confirm that you want to delete the user. 1. Click **Delete** in the warning to confirm deletion. @@ -61,7 +61,7 @@ The user is removed and is no longer able to access the Linode Cloud Manager. You can update a username, including your own, from the Linode Cloud Manager. -1. Navigate to the **Users & Grants** page in the Cloud Manager. See [View All Users](#view-all-users). +1. Navigate to the **Users & Grants** page in Cloud Manager. See [View All Users](#view-all-users). 1. Locate the user in the list and click on their **User Profile** link. 1. Enter a new username in the **Username** field. diff --git a/docs/products/platform/accounts/guides/service-transfers/index.md b/docs/products/platform/accounts/guides/service-transfers/index.md index d9c2c681264..58ffa8b38be 100644 --- a/docs/products/platform/accounts/guides/service-transfers/index.md +++ b/docs/products/platform/accounts/guides/service-transfers/index.md @@ -63,7 +63,7 @@ Each Compute Instance that you wish to transfer must have a unique label that is {{< /note >}} {{< note type="alert" >}} - DNS records that are associated with requested services will not be transferred or updated. Please ensure that associated DNS records have been updated or communicated to the recipient prior to the transfer. + DNS records that are associated with requested services will not be transferred or updated. Please ensure that associated DNS records have been updated or communicated to the recipient before the transfer. {{< /note >}} {{< note type="alert" >}} @@ -97,7 +97,7 @@ Each Compute Instance that you wish to transfer must have a unique label that is 1. In the **Receive a Service Transfer** field, enter the Service Transfer token you have received from the sender and click the **Review Details** button. - ![Review the summary of Linode services to be transferred prior to accepting.](receive-transfer.png "Review the summary of Linode services to be transferred prior to accepting.") + ![Review the summary of Linode services to be transferred before accepting.](receive-transfer.png "Review the summary of Linode services to be transferred before accepting.") 1. If the services are eligible for transfer, you are prompted to confirm responsibility for billing associated with those services. Billing begins for the receiving account after the transfer has been completed. Confirm billing responsibility and click **Accept Transfer** to begin transfer of services to your account. A confirmation email is sent to both the sending and receiving accounts. diff --git a/docs/products/platform/accounts/guides/third-party-authentication/index.md b/docs/products/platform/accounts/guides/third-party-authentication/index.md index 8e5eb1b0ed7..ec011619c55 100644 --- a/docs/products/platform/accounts/guides/third-party-authentication/index.md +++ b/docs/products/platform/accounts/guides/third-party-authentication/index.md @@ -10,7 +10,7 @@ image: enable-tpa-hero.png aliases: ['/platform/manager/third-party-authentication/','/guides/third-party-authentication/'] --- -Cloud Manager supports third-party authentication (TPA). This allows you to log in to Cloud Manager with another provider's login credentials. +Cloud Manager supports third-party authentication (TPA). This lets you log in to Cloud Manager with another provider's login credentials. {{< note >}} Enabling TPA disables two-factor authentication (2FA) on your user account. You should enable 2FA with the TPA provider with which you choose to authenticate to Cloud Manager. @@ -44,7 +44,7 @@ Separate from your selected login provider, you can also log in to Cloud Manager ## Disabling Third-Party Authentication -1. Log in to the [Cloud Manager](https://cloud.linode.com) using your TPA credentials. +1. Log in to [Cloud Manager](https://cloud.linode.com) using your TPA credentials. 1. Navigate to the Login & Authentication page of your profile by clicking on your **username** in the top right of the screen. Select **Login & Authentication** from the dropdown menu. diff --git a/docs/products/platform/accounts/guides/user-permissions/index.md b/docs/products/platform/accounts/guides/user-permissions/index.md index 4fa448604ab..a4f72565c34 100644 --- a/docs/products/platform/accounts/guides/user-permissions/index.md +++ b/docs/products/platform/accounts/guides/user-permissions/index.md @@ -10,18 +10,18 @@ tags: ["linode platform","users","user permissions"] Each user on an account can be given individualized permissions that provides unrestricted access to an account or limits their access to specific information or services. For example, you could give your core team members full unrestricted access, grant your accounts payable team access only to view and modify billing details, and limit an outside developer to only access specific Compute Instances or other services. {{< note >}} -The permissions discussed within this guide apply to accessing the Linode platform through the Cloud Manager, Linode API, and Linode CLI. If you wish to only provide someone with direct access to the internal system of a Compute Instance (or revoke their access), that can be accomplished through limited user accounts within your operating system. See [Create an Account for a Developer to Work on Your Compute Instance](/docs/products/platform/get-started/guides/developer-access/). +The permissions discussed within this guide apply to accessing the Linode platform through Cloud Manager, Linode API, and Linode CLI. If you wish to only provide someone with direct access to the internal system of a Compute Instance (or revoke their access), that can be accomplished through limited user accounts within your operating system. See [Create an Account for a Developer to Work on Your Compute Instance](/docs/products/platform/get-started/guides/developer-access/). {{< /note >}} ## View and Set Permissions for a User -You can view and edit permissions for a user directly in the Cloud Manager by following the instructions below. +You can view and edit permissions for a user directly in Cloud Manager by following the instructions below. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Account** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Account** link in the sidebar. 1. Navigate to the **Users & Grants** tab, which displays a list of existing users for the account. - ![Screenshot of the Users & Grants tab in the Cloud Manager](list-of-users.png) + ![Screenshot of the Users & Grants tab in Cloud Manager](list-of-users.png) 1. Locate the user for which you wish to view or modify permissions and click the corresponding **User Permissions** link. @@ -66,5 +66,5 @@ This section provides various levels of access to view or modify billing informa A user can be granted individual permissions to each instance of a service, such as Linode Compute Instances, Block Storage Volumes, NodeBalancers, and more. Unlike **Global Permissions**, **Specific Permissions** apply to individual resources -- not the service as a whole. - **None**: The user cannot view or otherwise interact with the selected resource. -- **Read Only**: The user can view the resource and all of its associated information typically visible within the Cloud Manager, however they cannot otherwise interact with it. +- **Read Only**: The user can view the resource and all of its associated information typically visible within Cloud Manager, however they cannot otherwise interact with it. - **Read-Write**: The user has full access to the selected resource and can make any changes that only an administrator is otherwise able to. This includes resource deletion, cloning, and all other applicable edits. The user also receives an email notification when a ticket is created or updated for this resource. \ No newline at end of file diff --git a/docs/products/platform/accounts/guides/user-security-controls/index.md b/docs/products/platform/accounts/guides/user-security-controls/index.md index 35199c877ea..93190d78717 100644 --- a/docs/products/platform/accounts/guides/user-security-controls/index.md +++ b/docs/products/platform/accounts/guides/user-security-controls/index.md @@ -32,7 +32,7 @@ You can configure three security questions on your user account. Security questi ### Configuring Security Questions. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and navigate to the [Login & Authentication](https://cloud.linode.com/profile/auth) page of your user profile. To do this, click on your username in the top right of the Cloud Manager and select **Login & Authentication** from the dropdown menu. +1. Log in to [Cloud Manager](https://cloud.linode.com) and navigate to the [Login & Authentication](https://cloud.linode.com/profile/auth) page of your user profile. To do this, click on your username in the top right of Cloud Manager and select **Login & Authentication** from the dropdown menu. 1. Scroll down to **Security Questions** under the **Security Settings** section. Here, you can view the security questions available to you or, if you've already configured them, see the questions you have selected. @@ -58,7 +58,7 @@ Standard carrier messaging fees apply for each SMS message. ### Adding a Verified Phone Number -1. Log in to [Cloud Manager](https://cloud.linode.com) and navigate to the [Login & Authentication](https://cloud.linode.com/profile/auth) page of your user profile. To do this, click on your username in the top right of the Cloud Manager and select **Login & Authentication** from the dropdown menu. +1. Log in to [Cloud Manager](https://cloud.linode.com) and navigate to the [Login & Authentication](https://cloud.linode.com/profile/auth) page of your user profile. To do this, click on your username in the top right of Cloud Manager and select **Login & Authentication** from the dropdown menu. 1. Scroll down to **Phone Verification** under the **Security Settings** section. Here, you can view, add, and remove your verified phone number. @@ -72,7 +72,7 @@ Standard carrier messaging fees apply for each SMS message. ## Multiple User Accounts -Organizations that require multiple individuals to access the same customer account should create separate *user accounts* for each individual. Once you've created a user account, you can assign permissions to restrict access to certain services and areas of the Cloud Manager. This is useful for providing all team members access to a single customer account, allowing a billing department to view invoices and billing details, or granting access to outside developers. For more information, see our guide on [Accounts and Passwords](/docs/products/platform/accounts/guides/manage-users/). +Organizations that require multiple individuals to access the same customer account should create separate *user accounts* for each individual. Once you've created a user account, you can assign permissions to restrict access to certain services and areas of Cloud Manager. This is useful for providing all team members access to a single customer account, allowing a billing department to view invoices and billing details, or granting access to outside developers. For more information, see our guide on [Accounts and Passwords](/docs/products/platform/accounts/guides/manage-users/). ## Single sign-on (SSO) with Akamai Control Center diff --git a/docs/products/platform/billing/_index.md b/docs/products/platform/billing/_index.md index f161e90b54d..73fb8eb3803 100644 --- a/docs/products/platform/billing/_index.md +++ b/docs/products/platform/billing/_index.md @@ -13,7 +13,7 @@ aliases: ['/products/tools/billing/','/platform/billing-and-support/prepaid-bill tags: ["linode platform"] --- -Linode strives to provide transparent and uncomplicated pricing structures and billing policies. As a supplement to our [Pricing](https://www.linode.com/pricing/) page, read through this guide to understand how we bill for services and how you can pay for these services. For instructions on how to manage your billing in the Cloud Manager, see the [Manage Billing in Cloud Manager](/docs/products/platform/billing/guides/) guide. If you have a question that isn't answered in either of these guides, don't hesitate to [contact Support](https://www.linode.com/support/). +Linode strives to provide transparent and uncomplicated pricing structures and billing policies. As a supplement to our [Pricing](https://www.linode.com/pricing/) page, read through this guide to understand how we bill for services and how you can pay for these services. For instructions on how to manage your billing in Cloud Manager, see the [Manage Billing in Cloud Manager](/docs/products/platform/billing/guides/) guide. If you have a question that isn't answered in either of these guides, don't hesitate to [contact Support](https://www.linode.com/support/). ## Understand How Billing Works @@ -21,7 +21,7 @@ Linode uses a hybrid hourly billing model that is simple and flexible. It enable - Every paid service offered by Linode has a predictable monthly rate (also called the monthly cap) in addition to a flexible hourly rate. -- When a service is added, charges accrue on the account at the hourly rate up to the monthly cap. These *accrued charges* are displayed on the **Billing Info** tab within the Account page of the Cloud Manager\*. Usage is always rounded up to the nearest hour. +- When a service is added, charges accrue on the account at the hourly rate up to the monthly cap. These *accrued charges* are displayed on the **Billing Info** tab within the Account page of Cloud Manager\*. Usage is always rounded up to the nearest hour. - Linode uses a monthly billing cycle. An invoice is automatically generated on the first day of each month and includes the previous month's usage. @@ -35,7 +35,7 @@ Here are a few examples of common billing scenarios you might encounter. For the #### A Service is Present on an Account for the *Entire* Month -You create the Compute Instance prior to the start of the month and it remains on your account for the entire month. Calculating the service fees at the hourly rate for 720 hours (again, assuming a 30 day month), the total would have come to $38.88. Since this exceeds the monthly cap for this service, you are instead charged the predictable $36 monthly rate. +You create the Compute Instance before the start of the month and it remains on your account for the entire month. Calculating the service fees at the hourly rate for 720 hours (again, assuming a 30 day month), the total would have come to $38.88. Since this exceeds the monthly cap for this service, you are instead charged the predictable $36 monthly rate. #### A Service is Present on an Account for *Almost* the Entire Month @@ -47,7 +47,7 @@ You created the Compute Instance mid-way through the month and deleted it exactl #### A Service is Resized During the Billing Cycle -Resizing a service, such as a Compute Instance, effectively creates a new billable service. Each of these billable services will appear as separate line items on your monthly invoice. For instance, you create a 4GB Compute Instance prior to the start of the month and resize it to an 8GB Compute Instance mid-way through the month. Your invoice will have two services as separate line items corresponding with the two different Compute Instance sizes that existed on your account during the billing cycle. Each line item will reflect the hourly rate for the time the service was active (up to the monthly cap). +Resizing a service, such as a Compute Instance, effectively creates a new billable service. Each of these billable services will appear as separate line items on your monthly invoice. For instance, you create a 4GB Compute Instance before the start of the month and resize it to an 8GB Compute Instance mid-way through the month. Your invoice will have two services as separate line items corresponding with the two different Compute Instance sizes that existed on your account during the billing cycle. Each line item will reflect the hourly rate for the time the service was active (up to the monthly cap). {{< note type=warning >}} If a service is resized to a new plan and then resized back to the original plan all in a single billing cycle, there will be 3 billable services. The combined hourly rate for these services may exceed the monthly cap of the original service plan. diff --git a/docs/products/platform/billing/developers/index.md b/docs/products/platform/billing/developers/index.md index 5f04cb1be93..aedf4b9bf8d 100644 --- a/docs/products/platform/billing/developers/index.md +++ b/docs/products/platform/billing/developers/index.md @@ -32,4 +32,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [manage your account](/docs/products/tools/cli/guides/account/) +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [manage your account](/docs/products/tools/cli/guides/account/) diff --git a/docs/products/platform/billing/faqs/_index.md b/docs/products/platform/billing/faqs/_index.md index 0cfde0f8ca1..d77d69249ed 100644 --- a/docs/products/platform/billing/faqs/_index.md +++ b/docs/products/platform/billing/faqs/_index.md @@ -16,7 +16,7 @@ You are charged for any service present on an account, even if it is powered off Each bill, including mid-month bills, is available to view as an itemized invoice. These invoices contain a detailed breakdown of your charges. Each service that was present on the account at any point during the billing cycle is listed on the invoice, alongside the amount of time the service was active, the hourly rate, and the total charge for that service. -All invoices are listed in the Billing & Payment History section of the Cloud Manager. See [Viewing Invoices and Payments](/docs/products/platform/billing/guides/view-history/) for instructions. A copy of each invoice is also emailed to all users on the account with read and write billing access. +All invoices are listed in the Billing & Payment History section of Cloud Manager. See [Viewing Invoices and Payments](/docs/products/platform/billing/guides/view-history/) for instructions. A copy of each invoice is also emailed to all users on the account with read and write billing access. ## I deleted a service earlier this month. Why was I just charged for it now? @@ -24,7 +24,7 @@ Invoices are generated at the beginning of every month and include fees for serv ## Where can I view amount of credit available on my account? -Promotional credits from a promo code are visible on the [Billing Info](https://cloud.linode.com/account/billing) page of the Cloud Manager. This credit is listed under the **Promotions** section that is only visible *if a promo code has been applied to your account*. Other types of account credits are displayed on the same page under the **Account Balance section**. A balance that is green indicates the amount of credit on the account. A balance that is red indicates the amount currently past due. +Promotional credits from a promo code are visible on the [Billing Info](https://cloud.linode.com/account/billing) page of Cloud Manager. This credit is listed under the **Promotions** section that is only visible *if a promo code has been applied to your account*. Other types of account credits are displayed on the same page under the **Account Balance section**. A balance that is green indicates the amount of credit on the account. A balance that is red indicates the amount currently past due. ## Will my current credit cover my next invoice? @@ -44,7 +44,7 @@ If your account exceeds its billing threshold (also called the *credit limit*), ## Can I make a payment in advance? -Yes. At any time, you can make a payment on your account. If the payment is greater than any past due amount, it gets stored as a positive account balance. This balance is automatically applied to future invoices. You can estimate your end of month costs using our [Pricing](https://www.linode.com/pricing/) page and view your account balance from the Billing Info page of the Cloud Manager. See [Making a One-Time Payment](/docs/products/platform/billing/guides/make-a-payment/). +Yes. At any time, you can make a payment on your account. If the payment is greater than any past due amount, it gets stored as a positive account balance. This balance is automatically applied to future invoices. You can estimate your end of month costs using our [Pricing](https://www.linode.com/pricing/) page and view your account balance from the Billing Info page of Cloud Manager. See [Making a One-Time Payment](/docs/products/platform/billing/guides/make-a-payment/). ## What are Linode’s currently accepted payment methods? @@ -56,7 +56,7 @@ A card can be declined for many different reasons. Banks often do not pass along ## How do I remove a credit card from my account? -You can manage your payment methods, including credit cards, from the Cloud Manager. To learn how to remove a credit card, see [Remove a Payment Method](/docs/products/platform/billing/guides/payment-methods/#remove-a-payment-method). Keep in mind you must have at least one valid payment method on file. If you are attempting to delete your only payment method, you must add a new payment method first. +You can manage your payment methods, including credit cards, from Cloud Manager. To learn how to remove a credit card, see [Remove a Payment Method](/docs/products/platform/billing/guides/payment-methods/#remove-a-payment-method). Keep in mind you must have at least one valid payment method on file. If you are attempting to delete your only payment method, you must add a new payment method first. ## Can I make a payment in another currency? diff --git a/docs/products/platform/billing/guides/access-billing/index.md b/docs/products/platform/billing/guides/access-billing/index.md index 9b4c56b3d87..94071450267 100644 --- a/docs/products/platform/billing/guides/access-billing/index.md +++ b/docs/products/platform/billing/guides/access-billing/index.md @@ -5,9 +5,9 @@ published: 2022-11-17 aliases: ['/products/tools/cloud-manager/guides/cloud-credits/'] --- -Most information and settings pertaining to billing are located within the [Billing Info](https://cloud.linode.com/account/billing) page of the Cloud Manager. Follow the instructions below to access this page: +Most information and settings pertaining to billing are located within the [Billing Info](https://cloud.linode.com/account/billing) page of Cloud Manager. Follow the instructions below to access this page: -1. Log in to the [Cloud Manager](https://cloud.linode.com) on a user account with one of the following permissions. See [Setting User Permissions](/docs/products/platform/accounts/guides/user-permissions/) for more details. +1. Log in to [Cloud Manager](https://cloud.linode.com) on a user account with one of the following permissions. See [Setting User Permissions](/docs/products/platform/accounts/guides/user-permissions/) for more details. - **Full account access** (unrestricted). - Restricted user with *Read-Write* permissions under **Billing Access**. Users with *Read Only* permissions are able to see most billing information but they are not able to make changes. diff --git a/docs/products/platform/billing/guides/make-a-payment/index.md b/docs/products/platform/billing/guides/make-a-payment/index.md index 5e5b1fe40ab..818a4aace3d 100644 --- a/docs/products/platform/billing/guides/make-a-payment/index.md +++ b/docs/products/platform/billing/guides/make-a-payment/index.md @@ -14,13 +14,13 @@ If you wish to pay in advance, follow the instructions within the [Make a One-Ti You can manually add funds to your account at any time. Manual payments can be used to pay an outstanding balance or prepay for future services. -1. Navigate to the **Billing Info** page in the [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). +1. Navigate to the **Billing Info** page in [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). 1. Click the **Make a Payment** button on the top right of the page, which opens the **Make a Payment** panel. 1. Enter the amount of money you would like to add to your account in the **Payment Amount** field. For your reference, the current balance on the account is displayed above this field. 1. **To pay with a saved payment method:** Select the saved payment method you wish to use in the **Payment methods** section and click the **Pay now** button. - **To pay with PayPal:** Click the **PayPal** button towards the bottom of the panel. This will open up PayPal's own payment form, where you can log in to your PayPal account and select your payment method. Once finished, you will be returned to the Cloud Manager. + **To pay with PayPal:** Click the **PayPal** button towards the bottom of the panel. This will open up PayPal's own payment form, where you can log in to your PayPal account and select your payment method. Once finished, you will be returned to Cloud Manager. - **To pay with an new Google Pay account or method:** Click the **Google Pay** button towards the bottom of the panel. This will open up Google's own payment form where you can log in to your Google account and select your payment method. Once finished, you will be returned to the Cloud Manager. + **To pay with an new Google Pay account or method:** Click the **Google Pay** button towards the bottom of the panel. This will open up Google's own payment form where you can log in to your Google account and select your payment method. Once finished, you will be returned to Cloud Manager. The payment may take a few minutes to be applied to your account. diff --git a/docs/products/platform/billing/guides/payment-methods/index.md b/docs/products/platform/billing/guides/payment-methods/index.md index eff73649bad..a4160c9b4e2 100644 --- a/docs/products/platform/billing/guides/payment-methods/index.md +++ b/docs/products/platform/billing/guides/payment-methods/index.md @@ -11,7 +11,7 @@ published: 2022-11-17 - **Google Pay:** Pay using a credit card, debit card, or PayPal through your Google Pay account. Paying with your Google Pay balance or any associated bank accounts are not supported at this time. {{< note >}} - To add a PayPal account to your Google Pay account, you currently must do so through the [Google Play Store](https://play.google.com/store/paymentmethods). PayPal cannot currently be added through the Google Pay website or mobile apps. When adding PayPal through Google Pay, it appears as a Discover Card within the Cloud Manager and the Linode API. + To add a PayPal account to your Google Pay account, you currently must do so through the [Google Play Store](https://play.google.com/store/paymentmethods). PayPal cannot currently be added through the Google Pay website or mobile apps. When adding PayPal through Google Pay, it appears as a Discover Card within Cloud Manager and the Linode API. {{< /note >}} - **PayPal:** Pay using your PayPal balance, a credit (or debit) card, or bank account through your PayPal account. @@ -22,9 +22,9 @@ See [Adding a New Payment Method](/docs/products/platform/billing/guides/payment ## Add a New Payment Method -New payment methods can be added to an account through the Cloud Manager. Up to **6 payment methods** can be active on an account at any given time, including multiple credit cards, Google Pay methods, and PayPal methods. +New payment methods can be added to an account through Cloud Manager. Up to **6 payment methods** can be active on an account at any given time, including multiple credit cards, Google Pay methods, and PayPal methods. -1. Navigate to the **Billing Info** page in the [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). +1. Navigate to the **Billing Info** page in [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). 1. If adding a credit card directly (not through Google Pay or PayPal), it must match the account's billing contact information and address. Review the **Billing Contact** section and edit it as necessary (see [Update Billing Contact Information](/docs/products/platform/billing/guides/update-billing-contact-info/)). @@ -40,11 +40,11 @@ New payment methods can be added to an account through the Cloud Manager. Up to A $1.00 authorization hold may be placed on your credit card by your banking institution when our payment processor tests the validity of the card. This is normal behavior and does not result in a charge on your card. {{< /note >}} - **To pay with Google Pay:** Click the **Google Pay** icon/button to open Google's own Google Pay form. Log in to your Google account and select the payment method you wish to use. Press **continue** (or otherwise complete the form) to be taken back to the Cloud Manager. + **To pay with Google Pay:** Click the **Google Pay** icon/button to open Google's own Google Pay form. Log in to your Google account and select the payment method you wish to use. Press **continue** (or otherwise complete the form) to be taken back to Cloud Manager. ![Button to add Google Pay](add-method-google-pay.png) - **To pay with PayPal:** Click the **PayPal** icon/button to open PayPal's own form. Log in to your PayPal account and select the credit card or bank account you wish to use. Optionally check or uncheck the **Use balance first** option to use any PayPal balance before the selected credit card or bank account. Press **Save and Continue** (or otherwise complete the form) to be taken back to the Cloud Manager. + **To pay with PayPal:** Click the **PayPal** icon/button to open PayPal's own form. Log in to your PayPal account and select the credit card or bank account you wish to use. Optionally check or uncheck the **Use balance first** option to use any PayPal balance before the selected credit card or bank account. Press **Save and Continue** (or otherwise complete the form) to be taken back to Cloud Manager. ![Button to add PayPal](add-method-paypal.png) @@ -58,7 +58,7 @@ This process does not immediately charge any past due balance on the account to To delete a payment method from your account, follow the instructions below. -1. Navigate to the **Billing Info** page in the [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). +1. Navigate to the **Billing Info** page in [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). 1. Under the **Payment Methods** section, locate the payment method you wish to remove. 1. Click the corresponding ellipsis menu and select **Delete** from the dropdown menu. If the payment method is the default payment method on the account, the **Delete** button will be disabled and you will first need to change the default method. @@ -68,7 +68,7 @@ To delete a payment method from your account, follow the instructions below. When an invoice is generated, the amount of that invoice (as well as any past due balance) will be charged to the *default* payment method on the account. The default payment method can be viewed and changed by following the instructions below. -1. Navigate to the **Billing Info** page in the [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). +1. Navigate to the **Billing Info** page in [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). 1. Under the **Payment Methods** section, the payment method currently used by default has a label of *default* (located to the right of the last 4 digits and expiration date). 1. To change the default payment method, click the ellipsis menu next to the payment method you wish to use and select **Make Default** from the dropdown menu. diff --git a/docs/products/platform/billing/guides/promo-code/index.md b/docs/products/platform/billing/guides/promo-code/index.md index 169c5ac2711..e67bb72604c 100644 --- a/docs/products/platform/billing/guides/promo-code/index.md +++ b/docs/products/platform/billing/guides/promo-code/index.md @@ -4,7 +4,7 @@ description: "Instructions on adding a promo code to your Linode account." published: 2022-11-17 --- -A *promo code* adds a positive credit to an account, allowing you to pay for services using that credit. You're able to add a promo code when signing up for an account. If you already signed up but haven't entered a promo code, you may be able to do so from the Cloud Manager. To add a promo code to an existing account, certain conditions must be met: +A *promo code* adds a positive credit to an account, allowing you to pay for services using that credit. You're able to add a promo code when signing up for an account. If you already signed up but haven't entered a promo code, you may be able to do so from Cloud Manager. To add a promo code to an existing account, certain conditions must be met: - The account must be less than 90 days old. - There must not be a negative balance on the account. @@ -13,7 +13,7 @@ A *promo code* adds a positive credit to an account, allowing you to pay for ser If those conditions are met, you can add a promo code by following these instructions: -1. Navigate to the **Billing Info** page in the [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). +1. Navigate to the **Billing Info** page in [Cloud Manager](https://cloud.linode.com/account/billing) (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). 1. Under the **Account Balance** section, click the *Add a promo code* link. diff --git a/docs/products/platform/billing/guides/referral-program/index.md b/docs/products/platform/billing/guides/referral-program/index.md index 644c86cb36f..5f51cda21e0 100644 --- a/docs/products/platform/billing/guides/referral-program/index.md +++ b/docs/products/platform/billing/guides/referral-program/index.md @@ -14,7 +14,7 @@ To learn more about this program, visit the [Referral Program](https://www.linod ### Find Your Referral Link -To activate the referral program and obtain a referral link, you must spend at least $25 with Linode, not including any promotional credits added to your account. Once activated, your referral link (including your unique referral code) can be viewed within the Cloud Manager. +To activate the referral program and obtain a referral link, you must spend at least $25 with Linode, not including any promotional credits added to your account. Once activated, your referral link (including your unique referral code) can be viewed within Cloud Manager. 1. Log in to the [Linode Cloud Manager](https://cloud.linode.com). 1. Select the **My Profile** link by clicking on your username at the top of the page. diff --git a/docs/products/platform/billing/guides/stop-billing/index.md b/docs/products/platform/billing/guides/stop-billing/index.md index 388c29b58fc..6dc2cebbf08 100644 --- a/docs/products/platform/billing/guides/stop-billing/index.md +++ b/docs/products/platform/billing/guides/stop-billing/index.md @@ -10,7 +10,7 @@ To prevent additional charges from accruing and stop further billing, you can re Linode services are provided without a contract or commitment. This means that you can remove them from your account at any time. Here are instructions for removing a Compute Instance: -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select **Linodes** from the sidebar menu. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select **Linodes** from the sidebar menu. 1. Locate the Compute Instance you wish to delete. 1. Expand the corresponding **more options ellipsis** menu and click **Delete**. 1. Select **Delete Linode** in the confirmation box that appears. diff --git a/docs/products/platform/billing/guides/tax-information/index.md b/docs/products/platform/billing/guides/tax-information/index.md index 89c345830d6..a05676e44bf 100644 --- a/docs/products/platform/billing/guides/tax-information/index.md +++ b/docs/products/platform/billing/guides/tax-information/index.md @@ -11,7 +11,7 @@ tags: ["linode platform"] Some countries, states, and regions require us by law to collect taxes. As such, customers located in these locations are charged the appropriate tax rate for any taxable services billed to their account. The taxes that Linode collects are listed on customer invoices (see the [Viewing Invoices and Payments](/docs/products/platform/billing/guides/view-history/) section of our Cloud Manager Billing guide). {{< note >}} -Pricing and service fees posted publicly, such as our [Pricing](https://www.linode.com/pricing/) page and listed in the Cloud Manager, do not include taxes. +Pricing and service fees posted publicly, such as our [Pricing](https://www.linode.com/pricing/) page and listed in Cloud Manager, do not include taxes. {{< /note >}} ## List of Countries and Tax Rates @@ -129,14 +129,14 @@ For eligible tax-exempt users in most countries, you can add your VAT or GST tax For users within the **United States** and **Canada**, you need to submit both your tax ID and state tax exemption or reseller's certificate via [Support Ticket](https://www.linode.com/support/) rather than adding your tax ID to your Linode account. This must happen before you are eligible to become exempt. Once approved, your tax ID will be added to your account by our team. Note that registered Canadian businesses may become exempt from PST sales tax but will always be billed for GST, HST, and QST sales tax. {{< note type="alert" >}} -If you are located in one of the countries that require taxes on our services, you are still liable for those taxes. Adding your tax ID does not exempt you from your liability to pay any taxes that have been mandated by your country for our services. Instead, this allows you to settle your taxes directly with your government's tax agency. +If you are located in one of the countries that require taxes on our services, you are still liable for those taxes. Adding your tax ID does not exempt you from your liability to pay any taxes that have been mandated by your country for our services. Instead, this lets you settle your taxes directly with your government's tax agency. {{< /note >}} ### Adding a Tax ID To add (or update) your account with a tax ID, follow the instructions below. A tax ID can also be added to an account during the signup process. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Navigate to the **Account** link in the sidebar. @@ -154,7 +154,7 @@ Your tax location is determined by the contact information you provided during s ### How can I change my tax location? -You may update your tax location by navigating to the **Account** page in the [Cloud Manager](https://cloud.linode.com) and then expanding the **Update Contact Information** panel. +You may update your tax location by navigating to the **Account** page in [Cloud Manager](https://cloud.linode.com) and then expanding the **Update Contact Information** panel. ### My business is tax exempt. How can I stop further taxes from being charged to my Linode account? diff --git a/docs/products/platform/billing/guides/view-history/index.md b/docs/products/platform/billing/guides/view-history/index.md index dd6e8303295..439755e7a2e 100644 --- a/docs/products/platform/billing/guides/view-history/index.md +++ b/docs/products/platform/billing/guides/view-history/index.md @@ -6,9 +6,9 @@ modified: 2023-09-21 aliases: ['/products/tools/cloud-manager/guides/cloud-invoices/'] --- -All of your billing history, including previous invoices and payments, is accessible within the [Cloud Manager](https://cloud.linode.com/account/billing) on the **Billing & Payment History** section within the **Billing Info** page (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). By default, all transactions (both invoices and payments) from the last *6 months* are displayed. To customize this, use the dropdown menus on the top right of this section. +All of your billing history, including previous invoices and payments, is accessible within [Cloud Manager](https://cloud.linode.com/account/billing) on the **Billing & Payment History** section within the **Billing Info** page (see [Accessing Billing Information](/docs/products/platform/billing/guides/access-billing/)). By default, all transactions (both invoices and payments) from the last *6 months* are displayed. To customize this, use the dropdown menus on the top right of this section. -![Viewing Billing & Payment History in the Cloud Manager](view-invoices.png) +![Viewing Billing & Payment History in Cloud Manager](view-invoices.png) **To view an itemized invoice,** find the invoice row on the list and click the corresponding invoice number. This opens up a new page that displays each service that was active during the billing period, along with the additional details listed below: @@ -24,4 +24,4 @@ All of your billing history, including previous invoices and payments, is access ## Downloading Invoices (PDF and CSV) -An invoice or payment can be downloaded as either a PDF or a CSV file. To do this, open the invoice within the Cloud Manager and select either the **Download CSV** or **Download PDF** button. \ No newline at end of file +An invoice or payment can be downloaded as either a PDF or a CSV file. To do this, open the invoice within Cloud Manager and select either the **Download CSV** or **Download PDF** button. \ No newline at end of file diff --git a/docs/products/platform/get-started/_index.md b/docs/products/platform/get-started/_index.md index 3167072a05d..bfdaf9699dd 100644 --- a/docs/products/platform/get-started/_index.md +++ b/docs/products/platform/get-started/_index.md @@ -17,10 +17,10 @@ show_on_rss_feed: false image: getting-started.jpg --- -Our goal at Linode is to make cloud computing simple, accessible, and affordable. To this end, the Linode platform offers a variety of user-friendly cloud solutions, all of which have clear and predictable [pricing](https://www.linode.com/pricing/) and can be managed using an intuitive browser-based interface (the [Cloud Manager](https://www.linode.com/products/cloud-manager/)), the command line (the [Linode CLI](https://www.linode.com/products/cli/)), or programmatically through an API (the [Linode API](https://www.linode.com/products/linode-api/)). This guide covers signing up for a Linode account, accessing the Cloud Manager, creating your first services, and understanding how billing works. +Our goal at Linode is to make cloud computing simple, accessible, and affordable. To this end, the Linode platform offers a variety of user-friendly cloud solutions, all of which have clear and predictable [pricing](https://www.linode.com/pricing/) and can be managed using an intuitive browser-based interface ([Cloud Manager](https://www.linode.com/products/cloud-manager/)), the command line (the [Linode CLI](https://www.linode.com/products/cli/)), or programmatically through an API (the [Linode API](https://www.linode.com/products/linode-api/)). This guide covers signing up for a Linode account, accessing Cloud Manager, creating your first services, and understanding how billing works. 1. [Sign Up for an Account](#sign-up-for-an-account) -1. [Navigate the Cloud Manager](#navigate-the-cloud-manager) +1. [Navigate Cloud Manager](#navigate-the-cloud-manager) 1. [Create Your First Compute Instance](#create-your-first-compute-instance) 1. [Create Additional Services](#create-additional-services) 1. [Understand Billing](#understand-billing) @@ -46,7 +46,7 @@ First, you need to create a Linode account to start using our services. If you a 1. Within the **Billing** section, select your payment method and enter your billing address details. Linode accepts credit/debit cards and PayPal on sign up. See the [Billing and Payments](/docs/products/platform/billing/#payments) guide to learn more about each of these methods. You must also accept the [Master Services Agreement](https://www.linode.com/legal-msa/). -1. Most accounts are activated instantly and you can start adding services right away. A small number of accounts may require manual review prior to activation. +1. Most accounts are activated instantly and you can start adding services right away. A small number of accounts may require manual review before activation. {{% content "email-warning-shortguide" %}} @@ -56,7 +56,7 @@ Once your account has been created, consider **enabling 2FA** to prevent unautho You can log in to Cloud Manager using your [Akamai Control Center](https://control.akamai.com/) account, provided your user email address is identical within both systems. To use this feature, select **Akamai Control Center** as the provider when logging in to Cloud Manager. You are automatically logged in to the Cloud Manager user that matches the email for the currently logged in Control Center user. If multiple Cloud Manager users match this email address, you can select which user to log in as. For more details, see [Single sign-on (SSO) with Akamai Control Center](/docs/products/platform/accounts/guides/user-security-controls/#single-sign-on-sso-with-akamai-control-center). {{< /note >}} -## Navigate the Cloud Manager +## Navigate Cloud Manager Linode's [Cloud Manager](https://cloud.linode.com/) is the primary gateway to our platform. It enables you to manage your account, view your bills, add services, and much more. Here are some of the main sections you might want to look through: @@ -66,7 +66,7 @@ Linode's [Cloud Manager](https://cloud.linode.com/) is the primary gateway to ou - [Help & Support](https://cloud.linode.com/support): Search through our guides, find answers on the Community Site, or open a ticket to reach our 24/7 award-winning [Support Team](https://www.linode.com/support-experience/). -For a full overview of the Cloud Manager and its core features, see the [Overview of the Cloud Manager](/docs/products/tools/cloud-manager/guides/an-overview-of-the-cloud-manager/) guide. +For a full overview of Cloud Manager and its core features, see the [Overview of Cloud Manager](/docs/products/tools/cloud-manager/guides/an-overview-of-the-cloud-manager/) guide. ## Create Your First Compute Instance @@ -111,7 +111,7 @@ In addition to [Compute Instances](#create-your-first-compute-instance), Linode Linode services are billed to your primary payment method at the end of each month (or when your accrued charges reach your billing limit). This means you can continuously add, modify, and remove services throughout the month. After the month is over, you receive an invoice for *the hourly usage of each service **up to the monthly cap***. In effect, billing is *post-paid* and *pro-rated*. See the below resources for more billing information and detailed hourly and monthly pricing. Note that plans and prices may vary by region. - [Billing and Payments](/docs/products/platform/billing/) -- [Managing Billing in the Cloud Manager](/docs/products/platform/billing/guides/) +- [Managing Billing in Cloud Manager](/docs/products/platform/billing/guides/) - [Linode Price List](https://www.linode.com/pricing/) Keep in mind that charges will accrue for any active service, even if it is powered off or otherwise not in use. This includes Compute Instances that have been powered off as well as any service you might have added to the account but are not using. diff --git a/docs/products/platform/get-started/guides/automating-deployment/index.md b/docs/products/platform/get-started/guides/automating-deployment/index.md index 7ac2911f8d2..63adcd40e1b 100644 --- a/docs/products/platform/get-started/guides/automating-deployment/index.md +++ b/docs/products/platform/get-started/guides/automating-deployment/index.md @@ -87,7 +87,7 @@ Golden disks are capable of handling automated server builds for most individual - [Use Salt States to Create LAMP Stack and Fail2ban Across Salt minions](/docs/guides/use-salt-states-to-create-lamp-stack-and-fail2ban-across-salt-minions/) - [Configure and Use Salt Cloud and Cloud Maps to Provision Systems](/docs/guides/configure-and-use-salt-cloud-and-cloud-maps-to-provision-systems/) -- **Terraform:** Terraform by HashiCorp is an orchestration tool that allows you to represent your Compute Instances and other resources with declarative code inside configuration files, instead of manually creating those resources via the Cloud Manager or API. This practice is referred to as Infrastructure as Code, and Terraform is a popular example of this methodology. +- **Terraform:** Terraform by HashiCorp is an orchestration tool that lets you represent your Compute Instances and other resources with declarative code inside configuration files, instead of manually creating those resources via Cloud Manager or API. This practice is referred to as Infrastructure as Code, and Terraform is a popular example of this methodology. - [A Beginner's Guide to Terraform](/docs/guides/beginners-guide-to-terraform/) - [Introduction to HashiCorp Configuration Language (HCL)](/docs/guides/introduction-to-hcl/) diff --git a/docs/products/platform/get-started/guides/beta-for-new-data-centers/index.md b/docs/products/platform/get-started/guides/beta-for-new-data-centers/index.md index deedae6572d..a1978688265 100644 --- a/docs/products/platform/get-started/guides/beta-for-new-data-centers/index.md +++ b/docs/products/platform/get-started/guides/beta-for-new-data-centers/index.md @@ -37,7 +37,7 @@ You must be enrolled in the beta to select a beta data center when deploying ser ## Pricing -Services utilized as part of the beta are free to users. Once the beta period ends for a particular data center, you will start accruing charges for any services that are still deployed to that region. You will receive an email notifying you of the billing start date as we transition each data center to general availability. +Services used as part of the beta are free to users. Once the beta period ends for a particular data center, you will start accruing charges for any services that are still deployed to that region. You will receive an email notifying you of the billing start date as we transition each data center to general availability. ## Product Availability diff --git a/docs/products/platform/get-started/guides/developer-access/index.md b/docs/products/platform/get-started/guides/developer-access/index.md index 463fbebc50e..394e1f04720 100644 --- a/docs/products/platform/get-started/guides/developer-access/index.md +++ b/docs/products/platform/get-started/guides/developer-access/index.md @@ -12,7 +12,7 @@ One of the most powerful features of Linode's unmanaged service is the amount of ## What to Keep Track of when Hiring a Developer -When you hire someone to work on your Linode, there are a variety of ways to grant access to your Linode account, the Compute Instances on it, and the system and applications on those instances. Recording which of these credentials you've shared is important in the event that you need to end your contract with your developer. +When you hire someone to work on your Linode, there are a variety of ways to grant access to your Linode account, the Compute Instances on it, and the system and applications on those instances. Recording which of these credentials you've shared is important if you need to end your contract with your developer. This guide explains and answers some of the most frequently asked questions about account access. The sections are separated in order of granularity, starting with service-level access at the top, and working towards application-specific access. @@ -24,11 +24,11 @@ The following sections include commands that show how to manipulate credentials ## Cloud Manager Access -Access to the Cloud Manager provides high-level methods for controlling your Compute Instances and Linode billing, including but not limited to: powering Compute Instances down, powering them on, removing services, and adding services. The Cloud Manager does not have interfaces for manipulating the files and software on your systems--instead, that access is governed by service-specific credentials outlined in the next sections. +Access to Cloud Manager provides high-level methods for controlling your Compute Instances and Linode billing, including but not limited to: powering Compute Instances down, powering them on, removing services, and adding services. Cloud Manager does not have interfaces for manipulating the files and software on your systems--instead, that access is governed by service-specific credentials outlined in the next sections. ### Who Has Access to My Linode Account? -Log in to the Cloud Manager and navigate to the [**Users and Permissions**](https://cloud.linode.com/account/users) section of the **Account** tab. You may be prompted to reauthenticate your password. This section will display all of your Linode account's users. +Log in to Cloud Manager and navigate to the [**Users and Permissions**](https://cloud.linode.com/account/users) section of the **Account** tab. You may be prompted to reauthenticate your password. This section will display all of your Linode account's users. If you're not sure whether you're logged in as the account administrator, look for a `No` in the **Restricted** column of your username's row in the User Manager. @@ -47,9 +47,9 @@ Useful *Global Grants* for a limited access user might include the ability to: ### Revoke a User's Access to the Linode Account -1. If you suspect that the user may have access to the Cloud Manager password, [change that first](/docs/products/platform/accounts/guides/reset-user-password/). +1. If you suspect that the user may have access to their Cloud Manager password, [change that first](/docs/products/platform/accounts/guides/reset-user-password/). -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and click [**Users and Permissions**](https://cloud.linode.com/account/users) in the **Account** tab. You may be prompted to reauthenticate your password. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and click [**Users and Permissions**](https://cloud.linode.com/account/users) in the **Account** tab. You may be prompted to reauthenticate your password. 1. Locate the user in the Username column, and click the three dots and select **Delete** to remove the user. Click **Delete** to confirm deletion. diff --git a/docs/products/platform/get-started/guides/network-transfer/index.md b/docs/products/platform/get-started/guides/network-transfer/index.md index f03a46a4964..1bc64990215 100644 --- a/docs/products/platform/get-started/guides/network-transfer/index.md +++ b/docs/products/platform/get-started/guides/network-transfer/index.md @@ -68,11 +68,11 @@ If traffic for an individual service exceeds the network transfer amount specifi ## Monitoring Network Transfer Usage -We recommend that you monitor your network transfer usage throughout the month to ensure that your services aren't consuming more network transfer than expected. You can check your network usage for your current billing cycle via the Cloud Manager or the Linode CLI. +We recommend that you monitor your network transfer usage throughout the month to ensure that your services aren't consuming more network transfer than expected. You can check your network usage for your current billing cycle via Cloud Manager or the Linode CLI. ### Cloud Manager -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Under the list of the Linode Compute Instances, NodeBalancers, or Object Storage Buckets, a short notice is displayed with the percentage of monthly network transfer pool that has been used. diff --git a/docs/products/platform/get-started/guides/resell-services/index.md b/docs/products/platform/get-started/guides/resell-services/index.md index f9e3261b304..55a699f6f64 100644 --- a/docs/products/platform/get-started/guides/resell-services/index.md +++ b/docs/products/platform/get-started/guides/resell-services/index.md @@ -50,7 +50,7 @@ The best way to resell Linode services is through the use of the Linode API. The ### Limited Cloud Manager Users -If a reseller wants to be able to give reseller customers access to parts of the Cloud Manager without developing a new user interface, they can create a limited Manager *user* in the Cloud Manager. A user is a set of credentials that can access your Linode account, and your Linode account can have multiple users. A user can be restricted to have a limited set of permissions, such as only being able to access certain Linodes and not having access to your billing information. To create a limited user in the Cloud Manager, review the [Users and Permissions](/docs/products/platform/accounts/guides/manage-users/#add-a-user) section of the Accounts and Passwords guide. +If a reseller wants to be able to give reseller customers access to parts of Cloud Manager without developing a new user interface, they can create a limited Manager *user* in Cloud Manager. A user is a set of credentials that can access your Linode account, and your Linode account can have multiple users. A user can be restricted to have a limited set of permissions, such as only being able to access certain Linodes and not having access to your billing information. To create a limited user in Cloud Manager, review the [Users and Permissions](/docs/products/platform/accounts/guides/manage-users/#add-a-user) section of the Accounts and Passwords guide. {{< note >}} Cloud Manager users are not related to the Linux users you may separately configure on Compute Instances. If you need to revoke a customer's account access, you should remove access to both their Cloud Manager users and their Linux users. Read the [Linux Users and Groups](/docs/guides/linux-users-and-groups/) guide for more information on this subject. @@ -58,7 +58,7 @@ Cloud Manager users are not related to the Linux users you may separately config ### Limited Linux User Accounts -A reseller might provide a customer with limited access to a Compute Instance by creating an account for them at the operating system level. This provides the customer with access to their server, without access to the features of the Linode API or the Cloud Manager. For a hosting reseller that offers access to a pre-defined Linux environment, this is often a good solution. Read the [Linux Users and Groups](/docs/guides/linux-users-and-groups/) guide for more information on this subject. You may also want to limit users' access to the filesystem with [SFTP jails](/docs/guides/limiting-access-with-sftp-jails-on-debian-and-ubuntu/). +A reseller might provide a customer with limited access to a Compute Instance by creating an account for them at the operating system level. This provides the customer with access to their server, without access to the features of the Linode API or Cloud Manager. For a hosting reseller that offers access to a pre-defined Linux environment, this is often a good solution. Read the [Linux Users and Groups](/docs/guides/linux-users-and-groups/) guide for more information on this subject. You may also want to limit users' access to the filesystem with [SFTP jails](/docs/guides/limiting-access-with-sftp-jails-on-debian-and-ubuntu/). ## Frequently Asked Questions diff --git a/docs/products/platform/get-started/guides/support/index.md b/docs/products/platform/get-started/guides/support/index.md index 25441bd433a..86ab9c3c7b8 100644 --- a/docs/products/platform/get-started/guides/support/index.md +++ b/docs/products/platform/get-started/guides/support/index.md @@ -97,13 +97,13 @@ Live support from our dedicated Customer Support Team is available 24 hours a da When contacting the Customer Support Team through a support ticket, you are automatically authenticated to your user account. If you instead send an inquiry through an email or call the dedicated support line, you will need to authenticate to an account before the support representative is able to disclose any account-specific information. {{< /note >}} -- **Support ticket:** Support tickets are the primary method for contacting the Customer Support Team. Tickets can be created, viewed, and managed through the Cloud Manager, though you can also use the [Linode CLI](/docs/products/tools/cli/guides/support-tickets/) and [Linode API](/docs/api/support/) if preferred. For help creating a ticket, see the [Create and Manage Support Tickets](#create-and-manage-support-tickets) section below. +- **Support ticket:** Support tickets are the primary method for contacting the Customer Support Team. Tickets can be created, viewed, and managed through Cloud Manager, though you can also use the [Linode CLI](/docs/products/tools/cli/guides/support-tickets/) and [Linode API](/docs/api/support/) if preferred. For help creating a ticket, see the [Create and Manage Support Tickets](#create-and-manage-support-tickets) section below. - **Phone call:** The dedicated support phone line can provide real-time support to English language speakers. If your inquiry concerns a specific account, please be prepared to authenticate to that account through a support ticket, a one-time passcode (sent to the account's phone number or email address), or alternative means. If your call is diverted to voicemail, please leave a detailed message explaining your problem. Your call will be returned as quickly as possible. - +1 (609) 380-7100 - +1 (855) 454-6633 (North America toll-free) -- **E-mail:** Whenever possible, it is recommended to create a support ticket. However, general questions that are *not account-specific* can be sent to *support@linode.com*. If your inquiry is account-specific and you are not able to log in to the Cloud Manager, fill out the [can't log in form](https://www.linode.com/support/contact/). +- **E-mail:** Whenever possible, it is recommended to create a support ticket. However, general questions that are *not account-specific* can be sent to *support@linode.com*. If your inquiry is account-specific and you are not able to log in to Cloud Manager, fill out the [can't log in form](https://www.linode.com/support/contact/). To help us give you the best possible answer when contacting the Support Team, consider the following advice. @@ -112,13 +112,13 @@ To help us give you the best possible answer when contacting the Support Team, c ## Create and Manage Support Tickets -All Tickets can be created, viewed, and managed on the [Support Tickets](https://cloud.linode.com/support/tickets) page in the Cloud Manager. +All Tickets can be created, viewed, and managed on the [Support Tickets](https://cloud.linode.com/support/tickets) page in Cloud Manager. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select **Help & Support** from the sidebar menu. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select **Help & Support** from the sidebar menu. 1. Under the **Other Ways to Get Help** section, select **Customer Support**. -![Screenshot of the Support Tickets page in the Cloud Manager](support-tickets.png) +![Screenshot of the Support Tickets page in Cloud Manager](support-tickets.png) This screen lists all open tickets by default. For a list of past tickets, navigate to the **Closed Tickets** tab. Click on a specific ticket to open that ticket, view the history, and to reply. diff --git a/docs/products/services/managed/_index.md b/docs/products/services/managed/_index.md index 386c2d89384..681a2dc36e6 100644 --- a/docs/products/services/managed/_index.md +++ b/docs/products/services/managed/_index.md @@ -26,7 +26,7 @@ Linode Managed applies to all Compute Instances on an account **except** for nod - **Included Services and Software:** The following services and software applications are included at no additional charge to Linode Managed customers - [cPanel](https://cpanel.net/): A cPanel license is included for each Compute Instance on your Linode account. Each license automatically scales to accommodate the number of [cPanel accounts](https://support.cpanel.net/hc/en-us/articles/1500004931582-What-is-an-Account/) you've configured within the cPanel installation. - - [Backups](/docs/products/storage/backups/): The Backup service is added to each Compute Instance on your account for no extra charge. This service automatically backs up the Compute Instance each day and allows you to restore from the most recent daily backup, weekly backup, and biweekly backup. See [Get Started with Backups](/docs/products/storage/backups/get-started/) for more information on backup restore points. + - [Backups](/docs/products/storage/backups/): The Backup service is added to each Compute Instance on your account for no extra charge. This service automatically backs up the Compute Instance each day and lets you restore from the most recent daily backup, weekly backup, and biweekly backup. See [Get Started with Backups](/docs/products/storage/backups/get-started/) for more information on backup restore points. - [Longview Pro](/docs/products/tools/longview/): Longview is our own metric service designed to help you keep track of your Compute Instances' performance. Whereas the free version of Longview is limited to collecting data at 5 minute intervals and storing only 12 hours worth of historical data, Longview Pro dramatically increases the data collection intervals and retains this data for longer: - 1 minute resolution for the past 24 hours - 5 minute resolution for the past week diff --git a/docs/products/services/managed/developers/index.md b/docs/products/services/managed/developers/index.md index 65c1d07dfaa..f8815217c66 100644 --- a/docs/products/services/managed/developers/index.md +++ b/docs/products/services/managed/developers/index.md @@ -17,4 +17,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. \ No newline at end of file +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. \ No newline at end of file diff --git a/docs/products/services/managed/get-started/index.md b/docs/products/services/managed/get-started/index.md index eeea7adcb08..1467b86b146 100644 --- a/docs/products/services/managed/get-started/index.md +++ b/docs/products/services/managed/get-started/index.md @@ -19,7 +19,7 @@ Follow the instructions below to sign up for Managed Services. This is an account-wide setting. Enabling Managed Services will result in additional charges *for each* Compute Instance on your account. If you would like to only enable this for some instances and not others, you will need to create a separate account and transfer any services you do (or do not) want to have managed. See [Transferring Ownership of Linode Services with Service Transfers](/docs/products/platform/accounts/guides/service-transfers/). {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Account** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Account** link in the sidebar. 1. Navigate to the **Settings** tab and click the **Add Linode Managed** button at the bottom of this page. diff --git a/docs/products/services/managed/guides/cancel/index.md b/docs/products/services/managed/guides/cancel/index.md index 858f8c3e5af..2a793dd4429 100644 --- a/docs/products/services/managed/guides/cancel/index.md +++ b/docs/products/services/managed/guides/cancel/index.md @@ -13,5 +13,5 @@ If you no longer need Linode's Managed Services offering, you can cancel it by [ - **cPanel:** When the service is cancelled, any cPanel licenses acquired through Managed Services are also revoked. If you still wish to use cPanel, you can purchase licenses directly through the [cPanel website](https://cpanel.net/pricing/). {{< note >}} -There is not currently a self-service option for cancelling Managed Services in the Cloud Manager, Linode CLI, or Linode API. You will need to contact the Support team to do so. +There is not currently a self-service option for cancelling Managed Services in Cloud Manager, Linode CLI, or Linode API. You will need to contact the Support team to do so. {{< /note >}} \ No newline at end of file diff --git a/docs/products/services/managed/guides/contacts/index.md b/docs/products/services/managed/guides/contacts/index.md index e32dd257b7b..4e65c81ae04 100644 --- a/docs/products/services/managed/guides/contacts/index.md +++ b/docs/products/services/managed/guides/contacts/index.md @@ -13,11 +13,11 @@ You can optionally attach up to two phone numbers to your contacts, a primary nu ## Add or Edit a Contact -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. 1. Navigate to the **Contacts** tab. Click on the **Add a Contact** link to add a new contact. If you wish to edit an existing contact instead, locate that contact in the list and click the corresponding **Edit** button. - ![Screenshot of the Managed Services Contacts page in the Cloud Manager](managed-contacts.png) + ![Screenshot of the Managed Services Contacts page in Cloud Manager](managed-contacts.png) 1. In the form that appears, enter the details for this contact. diff --git a/docs/products/services/managed/guides/credentials/index.md b/docs/products/services/managed/guides/credentials/index.md index df7e6bb2a2a..77fa8fc5c76 100644 --- a/docs/products/services/managed/guides/credentials/index.md +++ b/docs/products/services/managed/guides/credentials/index.md @@ -13,17 +13,17 @@ All credentials are securely stored in our encrypted database. ## View Credentials -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. 1. Navigate to the **Credentials** tab. A list of all your current credentials is displayed. From here, you can add new credentials or edit existing credentials. - ![Screenshot of credentials for Managed Services in the Cloud Manager](managed-credentials.png) + ![Screenshot of credentials for Managed Services in Cloud Manager](managed-credentials.png) Alongside each credential is a *Last Decrypted* field. This displays the timestamp for when the credential was last decrypted by our Support team. ## Add a Credential -1. Navigate to the **Credentials** tab for Managed Services in the Cloud Manager. See [View Credentials](#view-credentials). +1. Navigate to the **Credentials** tab for Managed Services in Cloud Manager. See [View Credentials](#view-credentials). 1. Click the **Add Credentials** button. @@ -39,7 +39,7 @@ All credentials are securely stored in our encrypted database. ## Edit a Credential -1. Navigate to the **Credentials** tab for Managed Services in the Cloud Manager. See [View Credentials](#view-credentials). +1. Navigate to the **Credentials** tab for Managed Services in Cloud Manager. See [View Credentials](#view-credentials). 1. Locate the credential you wish to edit and click the corresponding **Edit** button. diff --git a/docs/products/services/managed/guides/service-monitors/index.md b/docs/products/services/managed/guides/service-monitors/index.md index c6b968562ab..754a3580e59 100644 --- a/docs/products/services/managed/guides/service-monitors/index.md +++ b/docs/products/services/managed/guides/service-monitors/index.md @@ -10,11 +10,11 @@ Managed Services monitors the *services* running on your Compute Instances. Sett ## View Service Monitors -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. 1. Navigate to the **Monitors** tab. A list of all your current monitors is displayed. From here, you can add new monitors or edit existing ones. - ![Screenshot of the Monitors tab under Managed Services in the Cloud Manager](managed-monitors-list.png) + ![Screenshot of the Monitors tab under Managed Services in Cloud Manager](managed-monitors-list.png) Each monitor is listed along side its status and the resource it is checking. @@ -40,7 +40,7 @@ Each monitor can be configured with the following settings, which are available ## Add a Service Monitor -1. Navigate to the **Monitors** tab for Managed Services in the Cloud Manager. See [View Service Monitors](#view-service-monitors). +1. Navigate to the **Monitors** tab for Managed Services in Cloud Manager. See [View Service Monitors](#view-service-monitors). 1. Click the **Add Monitor** button. @@ -50,7 +50,7 @@ Each monitor can be configured with the following settings, which are available ## Edit a Service Monitor -1. Navigate to the **Monitors** tab for Managed Services in the Cloud Manager. See [View Service Monitors](#view-service-monitors). +1. Navigate to the **Monitors** tab for Managed Services in Cloud Manager. See [View Service Monitors](#view-service-monitors). 1. Locate the service monitor you wish to modify and click the corresponding **Edit** button. @@ -60,7 +60,7 @@ Each monitor can be configured with the following settings, which are available When a service monitor is created, it is automatically enabled. However, you may need to temporarily disable the monitor. For instance, when you are performing maintenance on the monitored resource or on the entire Compute Instance, you likely do not want the service monitor performing checks as it will alert your team (and the Support team) when the check fails. In this event, follow the instructions below to disable the monitor and then re-enable it once the maintenance is complete. -1. Navigate to the **Monitors** tab for Managed Services in the Cloud Manager. See [View Service Monitors](#view-service-monitors). +1. Navigate to the **Monitors** tab for Managed Services in Cloud Manager. See [View Service Monitors](#view-service-monitors). 1. Locate the service monitor you wish to modify and click the corresponding **Enable** or **Disable** button. This button may be within the expandable **more options ellipsis menu**. @@ -70,7 +70,7 @@ When a service monitor is created, it is automatically enabled. However, you may If you decide to remove or stop using a monitored service on your Compute Instance, you should also remove the service monitor from your account. If you do not, you will continue to receive notifications when the service fails to contact the specified resource. -1. Navigate to the **Monitors** tab for Managed Services in the Cloud Manager. See [View Service Monitors](#view-service-monitors). +1. Navigate to the **Monitors** tab for Managed Services in Cloud Manager. See [View Service Monitors](#view-service-monitors). 1. Locate the service monitor you wish to modify and click the corresponding **Delete** button. This button may be within the expandable **more options ellipsis menu**. diff --git a/docs/products/services/managed/guides/ssh-access/index.md b/docs/products/services/managed/guides/ssh-access/index.md index 5f803a88ee5..2fb55c8a9d3 100644 --- a/docs/products/services/managed/guides/ssh-access/index.md +++ b/docs/products/services/managed/guides/ssh-access/index.md @@ -19,11 +19,11 @@ If you do not wish to use this public key, you can also configure credentials in Linode generates a unique public/private keypair for your account when Managed Services is enabled. The public key is accessible on your account so that you can add it to each Compute Instance. The private key is then used by the Support Team to access your system whenever an issue requires investigation. You can locate your public key through the following steps: -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. 1. Navigate to the **SSH Access** tab. Your public key is displayed at the top of this tab. - ![A screenshot of an account's public key in the Cloud Manager](managed-public-key.png) + ![A screenshot of an account's public key in Cloud Manager](managed-public-key.png) 1. Hover over the public key box to view the full public key. To copy it, click the **Copy to clipboard** button. @@ -104,7 +104,7 @@ Modifying these SSH access settings for a Compute Instance **does not change** a Follow the steps below to edit the SSH access settings for each Compute Instance. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Managed** link in the sidebar. 1. Navigate to the **SSH Access** tab and scroll down to view a list of Compute Instances on your account. diff --git a/docs/products/storage/backups/_index.md b/docs/products/storage/backups/_index.md index 127c08d23b2..e3bedb28703 100644 --- a/docs/products/storage/backups/_index.md +++ b/docs/products/storage/backups/_index.md @@ -44,7 +44,7 @@ The Backup service does not keep automated backups older than 14 days, though th - Compatible with all Linode Compute Instances, provided their disks contain unencrypted ext3 or ext4 file systems - File-based backup solution, meaning it operates at the file level and not the block level - Backups are stored on separate dedicated hardware within the same data center -- Can be managed through the [Cloud Manager](https://cloud.linode.com/), the [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) +- Can be managed through [Cloud Manager](https://cloud.linode.com/), the [Linode CLI](https://www.linode.com/products/cli/), or programmatically through the [Linode API](https://www.linode.com/products/linode-api/) ## Part of a Multi-Tiered Backup Strategy diff --git a/docs/products/storage/backups/developers/index.md b/docs/products/storage/backups/developers/index.md index ed4b1ff03cc..8999f2b95e1 100644 --- a/docs/products/storage/backups/developers/index.md +++ b/docs/products/storage/backups/developers/index.md @@ -25,4 +25,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. diff --git a/docs/products/storage/backups/faqs/_index.md b/docs/products/storage/backups/faqs/_index.md index 9df63070e7b..37b40e128c8 100644 --- a/docs/products/storage/backups/faqs/_index.md +++ b/docs/products/storage/backups/faqs/_index.md @@ -15,7 +15,7 @@ If you require additional manual backups of your data, consider using [alternati ## Can I use the Backup service to backup Block Storage Volumes? -No, the Backup service does not take backups of Block Storage volumes, even if a volume is attached to a Compute Instance. If you wish to create a backup of your volume, consider cloning your volume or using [alternative methods of backing up your data](/docs/guides/backing-up-your-data/). Cloning a volume creates a new Block Storage volume of the same size and copies over all existing data. To clone your volume, navigate to the Volumes page in the Cloud Manager, open the ellipsis menu of the corresponding Volume you wish to clone, and select the **Clone** link. +No, the Backup service does not take backups of Block Storage volumes, even if a volume is attached to a Compute Instance. If you wish to create a backup of your volume, consider cloning your volume or using [alternative methods of backing up your data](/docs/guides/backing-up-your-data/). Cloning a volume creates a new Block Storage volume of the same size and copies over all existing data. To clone your volume, navigate to the Volumes page in Cloud Manager, open the ellipsis menu of the corresponding Volume you wish to clone, and select the **Clone** link. ![Screenshot of the Clone link for a Block Storage volume](clone-volume.png) diff --git a/docs/products/storage/backups/get-started/index.md b/docs/products/storage/backups/get-started/index.md index 30edfbf5f0c..d78df239ffb 100644 --- a/docs/products/storage/backups/get-started/index.md +++ b/docs/products/storage/backups/get-started/index.md @@ -12,7 +12,7 @@ aliases: ['/products/storage/backups/guides/manage/'] The Backup service can be enabled on existing Compute Instances by following the instructions below: -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. From the **Linodes** page, select the Linode you want to back up. @@ -31,9 +31,9 @@ Once enabled, the Backup service will store up to four backups, three of which a - **Biweekly** *(Between 8 and 14 days old)* - **Manual Snapshot** *(A user-initiated snapshot that stays the same until another snapshot is initiated)* -These backups can be managed in the Cloud Manager under the **Backups** tab for your Compute Instance. +These backups can be managed in Cloud Manager under the **Backups** tab for your Compute Instance. -![The list of Backups in the Cloud Manager](manage-backups.png) +![The list of Backups in Cloud Manager](manage-backups.png) This page also provides a few other options, detailed below: diff --git a/docs/products/storage/backups/guides/_index.md b/docs/products/storage/backups/guides/_index.md index b14cfaa8a5f..e8a5d16ca97 100644 --- a/docs/products/storage/backups/guides/_index.md +++ b/docs/products/storage/backups/guides/_index.md @@ -12,7 +12,7 @@ tab_group_main: These introductory guides help get you up and running with Linode's Backup Service. -- [Enable the Backup Service](/docs/products/storage/backups/guides/enable/): Use the Cloud Manager to enable the Backup Service. +- [Enable the Backup Service](/docs/products/storage/backups/guides/enable/): Use Cloud Manager to enable the Backup Service. - [Schedule Backups](/docs/products/storage/backups/guides/schedule/): Configure when automatic backups are initiated. @@ -22,7 +22,7 @@ These introductory guides help get you up and running with Linode's Backup Servi - [Restore a Backup to an Existing Compute Instance](/docs/products/storage/backups/guides/restore-to-an-existing-instance/): Restore a backup to an existing Compute Instance. -- [Cancel the Backup Service](/docs/products/storage/backups/guides/cancel/): Cancel the Backups Service through the Cloud Manager. +- [Cancel the Backup Service](/docs/products/storage/backups/guides/cancel/): Cancel the Backups Service through Cloud Manager. ## Going Further diff --git a/docs/products/storage/backups/guides/enable/index.md b/docs/products/storage/backups/guides/enable/index.md index 7fbb0529a3b..a03cde9f4fb 100644 --- a/docs/products/storage/backups/guides/enable/index.md +++ b/docs/products/storage/backups/guides/enable/index.md @@ -9,7 +9,7 @@ The Backups service can be individually enabled on an existing Compute Instances ## Enable the Backups Service on an Existing Compute Instance -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. From the **Linodes** page, select the Linode you want to back up. @@ -27,7 +27,7 @@ The Linode Backup Service is now enabled for the selected Linode. You can automatically enroll all new Linodes in the Backup Service. -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Click the **Account** link in the sidebar, then select the **Settings** tab. diff --git a/docs/products/storage/backups/guides/restore-to-an-existing-instance/index.md b/docs/products/storage/backups/guides/restore-to-an-existing-instance/index.md index 61b98ca57a7..0ee50ce94f2 100644 --- a/docs/products/storage/backups/guides/restore-to-an-existing-instance/index.md +++ b/docs/products/storage/backups/guides/restore-to-an-existing-instance/index.md @@ -40,7 +40,7 @@ This process restores *all data* that was stored on the disk at the time the bac If you are attempting to restore a disk to the same Compute Instance the backup was created from, the restoration process will not delete the original disk for you. Manually delete the original disk to make room for the backup, if desired. {{< /note >}} -1. Once your backup has been restored, you can optionally power up or restart your Compute Instance using that backup. To do so, navigate to the target Compute Instance in the Cloud Manager, go to the **Configurations** tab, locate the configuration profile created during the restore process, and click the corresponding **Boot** button. For full instructions, review [Manage Configuration Profiles on a Compute Instance > Boot from a Configuration Profile](/docs/products/compute/compute-instances/guides/configuration-profiles/#boot-from-a-configuration-profile). +1. Once your backup has been restored, you can optionally power up or restart your Compute Instance using that backup. To do so, navigate to the target Compute Instance in Cloud Manager, go to the **Configurations** tab, locate the configuration profile created during the restore process, and click the corresponding **Boot** button. For full instructions, review [Manage Configuration Profiles on a Compute Instance > Boot from a Configuration Profile](/docs/products/compute/compute-instances/guides/configuration-profiles/#boot-from-a-configuration-profile). {{< note type="warning" title="Warning: UUID Collisions">}} When you restore a backup, the restored disk is assigned the same [UUID](https://en.wikipedia.org/wiki/Universally_unique_identifier) as the original disk. In most cases, this is acceptable and does not cause issues. However, if you attempt to mount both the original disk and the corresponding restore disk at the same time (by assigning them both to devices in your Configuration Profile's **Block Device Assignment**), you will encounter a UUID "collision". diff --git a/docs/products/storage/backups/guides/take-a-snapshot/index.md b/docs/products/storage/backups/guides/take-a-snapshot/index.md index 51b5cfe3e45..c6a7aeac9ef 100644 --- a/docs/products/storage/backups/guides/take-a-snapshot/index.md +++ b/docs/products/storage/backups/guides/take-a-snapshot/index.md @@ -4,7 +4,7 @@ description: "How to use the Backups Service to take a manual backup of a Linode published: 2021-11-12 --- -As part of the Backups service, you can store a manual backup of your Compute Instance through the *manual snapshot* feature. This can be useful to save a restore point before a major system upgrade or prior to significant changes to software or configuration within your Compute Instance. +As part of the Backups service, you can store a manual backup of your Compute Instance through the *manual snapshot* feature. This can be useful to save a restore point before a major system upgrade or before significant changes to software or configuration within your Compute Instance. {{< note >}} The manual snapshot feature is part of the paid Backups service and, as such, the Backups service must be enabled. See [Enable Backups](/docs/products/storage/backups/guides/enable/). @@ -14,7 +14,7 @@ The manual snapshot feature is part of the paid Backups service and, as such, th Only a *single* manual snapshot can be stored for a Compute Instance. Taking a new snapshot overwrites any previously saved manual snapshot. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the left navigation menu. +1. Log in to [Cloud Manager](https://cloud.linode.com) and click the **Linodes** link in the left navigation menu. 1. On the **Linodes** page, select the Linode Compute Instance from the list. @@ -22,7 +22,7 @@ Only a *single* manual snapshot can be stored for a Compute Instance. Taking a n 1. Under **Manual Snapshot**, enter a label for this new snapshot and click **Take Snapshot**. - ![Screenshot of the Manual Snapshot section within the Cloud Manager](backups-manual-snapshot.png) + ![Screenshot of the Manual Snapshot section within Cloud Manager](backups-manual-snapshot.png) 1. A pop-up box is displayed confirming that you intend to take a new manual snapshot and that any previous snapshot will be overwritten. Click **Take Snapshot** to proceed. diff --git a/docs/products/storage/block-storage/developers/index.md b/docs/products/storage/block-storage/developers/index.md index 71eac5cbdf9..b42ec465ac1 100644 --- a/docs/products/storage/block-storage/developers/index.md +++ b/docs/products/storage/block-storage/developers/index.md @@ -16,7 +16,7 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage Block Storage Volumes](/docs/products/tools/cli/guides/block-storage-volumes/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to use the Linode CLI to [create and manage Block Storage Volumes](/docs/products/tools/cli/guides/block-storage-volumes/). ## Linode Tools @@ -32,4 +32,4 @@ The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the L **Terraform**: Terraform is an Infrastructure-as-code tool that includes management features for various types of Linode resources. Use Linode’s [official Terraform Provider](https://www.terraform.io/docs/providers/linode/r/volume.html) to create and manage Block Storage Volumes. To learn more about Terraform see our documentation library’s [Terraform section](/docs/applications/configuration-management/terraform/). -**Pulumi**: Pulumi is a development tool that allows you to write computer programs which deploy cloud resources. With [Pulumi’s Linode integration](https://github.com/pulumi/pulumi-linode), you can manage your Linode resources in several programming languages, like JavaScript, Go, Python, and TypeScript. Pulumi manages your resources in the same way as Linode's API or CLI. See [Pulumi’s documentation](https://www.pulumi.com/docs/intro/cloud-providers/linode/) to get started. +**Pulumi**: Pulumi is a development tool that lets you write computer programs which deploy cloud resources. With [Pulumi’s Linode integration](https://github.com/pulumi/pulumi-linode), you can manage your Linode resources in several programming languages, like JavaScript, Go, Python, and TypeScript. Pulumi manages your resources in the same way as Linode's API or CLI. See [Pulumi’s documentation](https://www.pulumi.com/docs/intro/cloud-providers/linode/) to get started. diff --git a/docs/products/storage/block-storage/guides/attach-and-detach/index.md b/docs/products/storage/block-storage/guides/attach-and-detach/index.md index 89e288fd481..e5557602730 100644 --- a/docs/products/storage/block-storage/guides/attach-and-detach/index.md +++ b/docs/products/storage/block-storage/guides/attach-and-detach/index.md @@ -11,7 +11,7 @@ Each Volume can to be attached to a single Compute Instance within the same data Learn how to attach an existing Block Storage Volume to a Compute Instance using these steps: -1. Log in to the [Cloud Manager](https://cloud.linode.com/linodes) and click on the **Volumes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/linodes) and click on the **Volumes** link in the sidebar. 1. Locate the desired Volume within the list, click the **more options ellipsis** dropdown menu, and select **Attach**. @@ -25,7 +25,7 @@ Learn how to attach an existing Block Storage Volume to a Compute Instance using {{< /note >}} {{< note >}} - If your Compute Instance was deployed prior to August 24th, 2021 and hasn't been rebooted since your data center was upgraded to NVMe Block Storage, you may need to reboot the instance for it to properly work with a Block Storage Volume. + If your Compute Instance was deployed before August 24th, 2021 and hasn't been rebooted since your data center was upgraded to NVMe Block Storage, you may need to reboot the instance for it to properly work with a Block Storage Volume. {{< /note >}} 1. Click the **Save** button to attach the Volume. @@ -40,7 +40,7 @@ Learn how to attach an existing Block Storage Volume to a Compute Instance using Follow these steps to safely detach a Block Storage Volume from a Compute Instance. A Volume should be detached before it is reattached to a different instance. -1. Log in to the [Cloud Manager](https://cloud.linode.com/linodes) and click on the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/linodes) and click on the **Linodes** link in the sidebar. 1. Select the Compute Instance that the Volume is currently attached to. @@ -60,4 +60,4 @@ Follow these steps to safely detach a Block Storage Volume from a Compute Instan 1. A confirmation screen appears and explains that the Volume will be detached from the Compute Instance. Click **Detach** to confirm. -Detached Volumes still exist on your account and, as such, you are still billed for the Volume as normal. It can be viewed and deleted within the **Volumes** listing page in the Cloud Manager. See [View, Add, and Delete Volumes](/docs/products/storage/block-storage/guides/manage-volumes/). \ No newline at end of file +Detached Volumes still exist on your account and, as such, you are still billed for the Volume as normal. It can be viewed and deleted within the **Volumes** listing page in Cloud Manager. See [View, Add, and Delete Volumes](/docs/products/storage/block-storage/guides/manage-volumes/). \ No newline at end of file diff --git a/docs/products/storage/block-storage/guides/boot-from-a-volume/index.md b/docs/products/storage/block-storage/guides/boot-from-a-volume/index.md index c0c05b3bb1f..d913575a303 100644 --- a/docs/products/storage/block-storage/guides/boot-from-a-volume/index.md +++ b/docs/products/storage/block-storage/guides/boot-from-a-volume/index.md @@ -10,7 +10,7 @@ aliases: ['/platform/block-storage/boot-from-block-storage-volume/','/guides/boo image: block-storage-title-graphic.png --- -Linode’s Block Storage service allows you to attach additional storage volumes to your Compute Instances. In addition to storing files and media, you can also use a Volume as a boot disk. This can provide a low-cost way to maintain an image that can be quickly attached to a Compute Instance and booted up when needed. +Linode’s Block Storage service lets you attach additional storage volumes to your Compute Instances. In addition to storing files and media, you can also use a Volume as a boot disk. This can provide a low-cost way to maintain an image that can be quickly attached to a Compute Instance and booted up when needed. This guide outlines the steps needed to boot your Compute Instance from a Block Storage Volume. These steps include creating a new Volume, copying the primary disk to that new Volume, and configuring the instance to boot from that Volume. The process may be reversed in order to restore the primary disk from the Volume. diff --git a/docs/products/storage/block-storage/guides/configure-volume/index.md b/docs/products/storage/block-storage/guides/configure-volume/index.md index c962268a262..10eba78f959 100644 --- a/docs/products/storage/block-storage/guides/configure-volume/index.md +++ b/docs/products/storage/block-storage/guides/configure-volume/index.md @@ -4,9 +4,9 @@ description: "Learn how to create a file system on a Block Storage Volume and mo modified: 2022-08-24 --- -Once a Block Storage Volume has been attached to a Compute Instance, you need to perform a few additional steps before you can start using it. These steps include creating a file system (if you're configuring a new Volume) and mounting the Volume to your Compute Instance's system. To make configuration easier, all the necessary commands can be viewed directly in the Cloud Manager. +Once a Block Storage Volume has been attached to a Compute Instance, you need to perform a few additional steps before you can start using it. These steps include creating a file system (if you're configuring a new Volume) and mounting the Volume to your Compute Instance's system. To make configuration easier, all the necessary commands can be viewed directly in Cloud Manager. -1. Log in to the [Cloud Manager](https://cloud.linode.com/linodes) and click on the **Volumes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/linodes) and click on the **Volumes** link in the sidebar. 1. Locate the desired Volume within the list and click the **Show Config** link, which may appear within the **more options ellipsis** dropdown menu. diff --git a/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md b/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md index dca0af94466..445cbbd6568 100644 --- a/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md +++ b/docs/products/storage/block-storage/guides/manage-block-storage-with-linode-api/index.md @@ -11,7 +11,7 @@ tags: ["linode platform"] aliases: ['/platform/api/create-block-storage-volumes-with-the-linode-api/','/guides/create-block-storage-volumes-with-the-linode-api/','/products/tools/api/guides/block-storage/'] --- -The Linode API allows you to create, delete, attach, detach, clone, and resize Block Storage Volumes. +The Linode API lets you create, delete, attach, detach, clone, and resize Block Storage Volumes. ## Before You Begin diff --git a/docs/products/storage/block-storage/guides/manage-volumes/index.md b/docs/products/storage/block-storage/guides/manage-volumes/index.md index 0403de27ccd..57215bb5606 100644 --- a/docs/products/storage/block-storage/guides/manage-volumes/index.md +++ b/docs/products/storage/block-storage/guides/manage-volumes/index.md @@ -7,20 +7,20 @@ aliases: ['/products/storage/block-storage/guides/add-volume/','/products/storag What is block storage? Block Storage is a scalable, high-speed, and fault tolerant network storage service used to add additional storage capacity to a Linode Compute Instance. -The Block Storage cloud service allows you to create Volumes, which can be attached to Compute Instances and used to easily store your data. This guide covers how to view, add, manage, and delete Block Storage Volumes. +The Block Storage cloud service lets you create Volumes, which can be attached to Compute Instances and used to easily store your data. This guide covers how to view, add, manage, and delete Block Storage Volumes. ## View Volumes ### View All Volumes -Log in to the [Cloud Manager](https://cloud.linode.com/volumes) and click the **Volumes** link in the sidebar. All Block Storage Volumes on your account are listed here, including their region, size, and their attachment status. +Log in to [Cloud Manager](https://cloud.linode.com/volumes) and click the **Volumes** link in the sidebar. All Block Storage Volumes on your account are listed here, including their region, size, and their attachment status. ![View all Volumes on an account](view-all-volumes.png) ### View Block Storage Volumes Attached to a Specific Compute Instance -1. Log in to the [Cloud Manager](https://cloud.linode.com/linodes) and click the **Linodes** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/linodes) and click the **Linodes** link in the sidebar. 1. Select the Compute Instance for which you'd like to view all attached Volumes. The detail page for that instance should appear. @@ -31,10 +31,10 @@ Log in to the [Cloud Manager](https://cloud.linode.com/volumes) and click the ** ## Add Volumes {{< note >}} -If your Compute Instance was deployed prior to August 24th, 2021 and hasn't been rebooted since your data center was upgraded to NVMe Block Storage, you may need to reboot the instance for it to properly work with a Block Storage Volume. +If your Compute Instance was deployed before August 24th, 2021 and hasn't been rebooted since your data center was upgraded to NVMe Block Storage, you may need to reboot the instance for it to properly work with a Block Storage Volume. {{< /note >}} -1. Navigate to the **Volumes** page in the Cloud Manager. Alternatively, if you know which Compute Instance you wish to attach the new Volume to, navigate to the **Storage** tab for that instance. See [View Volumes](#view-volumes). +1. Navigate to the **Volumes** page in Cloud Manager. Alternatively, if you know which Compute Instance you wish to attach the new Volume to, navigate to the **Storage** tab for that instance. See [View Volumes](#view-volumes). 1. Click the **Create Volume** button to open the creation form. This form may have slightly different options, depending on the page you were on in the previous step. If creating a Volume directly from a Compute Instance's Storage tab, select the **Create and Attach Volume** option to create a new Volume. @@ -61,7 +61,7 @@ If your Compute Instance was deployed prior to August 24th, 2021 and hasn't been Once a Block Storage Volume has been deleted, the data contained on that Volume will be permanently erased. This action cannot be reversed, so it’s always best to verify or backup the data in the block storage volume beforehand. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com/linodes). +1. Log in to [Cloud Manager](https://cloud.linode.com/linodes). 1. If the Volume is attached to a Compute Instance, power off that instance and detach the Volume. To do so, follow the instructions within the [Detach the Volume](/docs/products/storage/block-storage/guides/attach-and-detach/#detach-a-volume) guide. diff --git a/docs/products/storage/block-storage/guides/nvme-upgrade/index.md b/docs/products/storage/block-storage/guides/nvme-upgrade/index.md index 3747c12643b..884f8731803 100644 --- a/docs/products/storage/block-storage/guides/nvme-upgrade/index.md +++ b/docs/products/storage/block-storage/guides/nvme-upgrade/index.md @@ -16,9 +16,9 @@ To learn more about Block Storage, visit the [Block Storage Overview](/docs/prod ## Upgrading a Volume to NVMe Block Storage -Existing Volumes can be upgraded to NVMe soon after NVMe Block Storage has been deployed within a data center. Once NVMe upgrades are available, our team will schedule a migration for each eligible Volume on your account. You will receive a notification detailing the Volumes scheduled to be upgraded along with their migration schedule. You can view your scheduled upgrades on the [Account > Maintenance](https://cloud.linode.com/account/maintenance/) page of the Cloud Manager under the *Volumes* section. You can also choose to immediately enter the upgrade queue *after* the migration has been scheduled by following the instructions below: +Existing Volumes can be upgraded to NVMe soon after NVMe Block Storage has been deployed within a data center. Once NVMe upgrades are available, our team will schedule a migration for each eligible Volume on your account. You will receive a notification detailing the Volumes scheduled to be upgraded along with their migration schedule. You can view your scheduled upgrades on the [Account > Maintenance](https://cloud.linode.com/account/maintenance/) page of Cloud Manager under the *Volumes* section. You can also choose to immediately enter the upgrade queue *after* the migration has been scheduled by following the instructions below: -1. Log in to the Cloud Manager and navigate to the [Volumes](https://cloud.linode.com/volumes) page. +1. Log in to Cloud Manager and navigate to the [Volumes](https://cloud.linode.com/volumes) page. 1. Click the **Upgrade to NVMe** button next to the Volume you wish to upgrade. If this button does not appear next to your desired *non-NVMe* Volume, the Volume is not yet eligible for an upgrade. diff --git a/docs/products/storage/block-storage/guides/resize-volume/index.md b/docs/products/storage/block-storage/guides/resize-volume/index.md index b3d50167fad..fee447b2625 100644 --- a/docs/products/storage/block-storage/guides/resize-volume/index.md +++ b/docs/products/storage/block-storage/guides/resize-volume/index.md @@ -10,7 +10,7 @@ At any time after the Block Storage Volume has been created, it can be increased At this time, the size of Volumes are only able to be increased (not decreased). To decrease the size of your Volume, you will need to create a new Volume at your preferred size, attach it to a Compute Instance, copy over your data, and remove the original Volume. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com/linodes). +1. Log in to [Cloud Manager](https://cloud.linode.com/linodes). 1. If the Volume is attached to a Compute Instance, power off that instance. @@ -20,7 +20,7 @@ At this time, the size of Volumes are only able to be increased (not decreased). 1. Enter the new Volume size. The minimum size is the current size of the Volume and maximum is 10,240 GB. Then click **Submit**. -1. Click **Resize Volume** to start the resize. Once the resize has been completed, you will receive a notification in the Cloud Manager. +1. Click **Resize Volume** to start the resize. Once the resize has been completed, you will receive a notification in Cloud Manager. 1. After the Volume is resized, power back on your Compute Instance. diff --git a/docs/products/storage/block-storage/guides/use-cases/index.md b/docs/products/storage/block-storage/guides/use-cases/index.md index 77647a92431..a824a756c88 100644 --- a/docs/products/storage/block-storage/guides/use-cases/index.md +++ b/docs/products/storage/block-storage/guides/use-cases/index.md @@ -24,7 +24,7 @@ A Block Storage Volume augments the raw storage capacity of a cloud instance, wh While the health and uptime of Linode Block Storage is closely monitored by Linode Support, we still recommend [making separate backups](/docs/guides/backing-up-your-data/) of your Volumes. {{< /note >}} -Because Volumes are directly connected to an instance, their I/O speeds are much faster than those of an alternative storage solution like Object Storage. As well, the nature of Block Storage allows you to read and write small parts of your data, which means that you can incrementally update your files. This is in contrast to Object Storage, which requires a full re-upload of a file to update it. +Because Volumes are directly connected to an instance, their I/O speeds are much faster than those of an alternative storage solution like Object Storage. As well, the nature of Block Storage lets you read and write small parts of your data, which means that you can incrementally update your files. This is in contrast to Object Storage, which requires a full re-upload of a file to update it. Some aspects of Block Storage lead to natural limitations. In particular, a Volume needs to be attached to a cloud instance for its data to be accessible. In comparison, a file stored in Object Storage can be downloaded by any internet connected client at any time. @@ -64,7 +64,7 @@ For more information on using Plex with a Block Storage Volume, see our [Using a ### Ephemeral Storage -Various stages of the software development lifecycle can create large amounts of temporary data, such as buffers, builds, and cache and session data. While this data might only exist for a short period of time, it requires and utilizes storage space. Creating a Block Storage Volume just for ephemeral data is a good use case for times when the storage supplied with your instance is not enough, or for when you need extra space for a short period of time. +Various stages of the software development lifecycle can create large amounts of temporary data, such as buffers, builds, and cache and session data. While this data might only exist for a short period of time, it requires and uses storage space. Creating a Block Storage Volume just for ephemeral data is a good use case for times when the storage supplied with your instance is not enough, or for when you need extra space for a short period of time. ### Data Backups diff --git a/docs/products/storage/object-storage/_index.md b/docs/products/storage/object-storage/_index.md index 4d306632f1b..70c6db88b60 100644 --- a/docs/products/storage/object-storage/_index.md +++ b/docs/products/storage/object-storage/_index.md @@ -1,7 +1,7 @@ --- title: Object Storage title_meta: "Object Storage Product Documentation" -description: "Linode Object Storage is S3-compatible, doesn't require a Linode, and allows you to host static sites." +description: "Linode Object Storage is S3-compatible, doesn't require a Linode, and lets you host static sites." modified: 2024-04-07 tab_group_main: is_root: true diff --git a/docs/products/storage/object-storage/developers/index.md b/docs/products/storage/object-storage/developers/index.md index 2e5f775eb3b..f914853beac 100644 --- a/docs/products/storage/object-storage/developers/index.md +++ b/docs/products/storage/object-storage/developers/index.md @@ -14,4 +14,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. [Learn how to use the Linode CLI](/docs/products/tools/cli/guides/object-storage/). +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. [Learn how to use the Linode CLI](/docs/products/tools/cli/guides/object-storage/). diff --git a/docs/products/storage/object-storage/get-started/index.md b/docs/products/storage/object-storage/get-started/index.md index 6e8dd8f03b0..3bd99bd0f3e 100644 --- a/docs/products/storage/object-storage/get-started/index.md +++ b/docs/products/storage/object-storage/get-started/index.md @@ -39,7 +39,7 @@ Billing for Object Storage starts when it is enabled on your account, **regardle ## Create a Bucket -The Cloud Manager provides a web interface for creating buckets. To create a bucket: +Cloud Manager provides a web interface for creating buckets. To create a bucket: 1. If you have not already, log in to the [Linode Cloud Manager](https://cloud.linode.com). diff --git a/docs/products/storage/object-storage/guides/_index.md b/docs/products/storage/object-storage/guides/_index.md index 843f92bc730..592e723cf44 100644 --- a/docs/products/storage/object-storage/guides/_index.md +++ b/docs/products/storage/object-storage/guides/_index.md @@ -9,17 +9,17 @@ tags: ["education","media"] ## Basics -- [Create and Manage Buckets](/docs/products/storage/object-storage/guides/manage-buckets/): Buckets are the primary containers within Object Storage. Learn how to view, create, and delete buckets through the Cloud Manager. +- [Create and Manage Buckets](/docs/products/storage/object-storage/guides/manage-buckets/): Buckets are the primary containers within Object Storage. Learn how to view, create, and delete buckets through Cloud Manager. -- [Upload and Manage Files (Objects)](/docs/products/storage/object-storage/guides/manage-files/): Learn how to view, upload, download, and delete objects through the Cloud Manager. +- [Upload and Manage Files (Objects)](/docs/products/storage/object-storage/guides/manage-files/): Learn how to view, upload, download, and delete objects through Cloud Manager. -- [Manage Access Keys](/docs/products/storage/object-storage/guides/access-keys/): Access keys enable you to access Object Storage through other tools and your own applications. Learn how to generate and manage these in the Cloud Manager. +- [Manage Access Keys](/docs/products/storage/object-storage/guides/access-keys/): Access keys enable you to access Object Storage through other tools and your own applications. Learn how to generate and manage these in Cloud Manager. - [Access Buckets and Files through URLs](/docs/products/storage/object-storage/guides/urls/): Every bucket and file can be accessed by a unique URL. Learn how to obtain these URLs. - [Configure a Custom Domain (with a TLS/SSL Certificate)](/docs/products/storage/object-storage/guides/custom-domain/): Linode's Object Storage supports accessing buckets and objects through a custom domain. Learn how to configure a custom domain with a TLS/SSL certificate. -- [Cancel Object Storage](/docs/products/storage/object-storage/guides/cancel/): Learn how to cancel the Object Storage service from the Cloud Manager. +- [Cancel Object Storage](/docs/products/storage/object-storage/guides/cancel/): Learn how to cancel the Object Storage service from Cloud Manager. - [Object Storage Use Cases](/docs/products/storage/object-storage/guides/use-cases/): Information on the benefits and common use cases of Linode's Object Storage service. diff --git a/docs/products/storage/object-storage/guides/access-keys/index.md b/docs/products/storage/object-storage/guides/access-keys/index.md index b627fefa979..22371cf94cf 100644 --- a/docs/products/storage/object-storage/guides/access-keys/index.md +++ b/docs/products/storage/object-storage/guides/access-keys/index.md @@ -13,11 +13,11 @@ When an access key is generated, a corresponding *secret key* is also created. T ## View Access Keys -1. Log in to the [Cloud Manager](https://cloud.linode.com). +1. Log in to [Cloud Manager](https://cloud.linode.com). 1. Select the **Object Storage** link in the sidebar and navigate to the **Access Keys** tab. -![Viewing a list of access keys in the Cloud Manager](view-access-keys.jpg) +![Viewing a list of access keys in Cloud Manager](view-access-keys.jpg) This page displays a list of all the access keys added to your Object Storage account. It also shows the S3 endpoint hostname. The S3 endpoint hostname is different for each region and is displayed when the you create an access key. @@ -28,23 +28,23 @@ From here, you can create a new access key. You can also click the ellipsis to: ## Create an Access Key -To use Object Storage with any compatible client or command-line tool, you'll need to generate an Access Key. This can be done directly in the Cloud Manager. +To use Object Storage with any compatible client or command-line tool, you'll need to generate an Access Key. This can be done directly in Cloud Manager. -1. Navigate to the **Access Keys** page in the Cloud Manager (see [View Access Keys](#view-access-keys)). +1. Navigate to the **Access Keys** page in Cloud Manager (see [View Access Keys](#view-access-keys)). 1. Click the **Create Access Key** button, which displays the **Create Access Key** panel. -1. Enter a label for the access key. This label is how you reference the access key in the Cloud Manager and any S3 compatible client. +1. Enter a label for the access key. This label is how you reference the access key in Cloud Manager and any S3 compatible client. 1. Select at least one Region. You can select multiple regions for your access key. -1. Toggle the **Limited Access** switch if you wish to only provide access to certain buckets. This allows you to limit the permissions for the new access key on a per-bucket level. See [Access Key Permissions](#permissions) for more details. +1. Toggle the **Limited Access** switch if you wish to only provide access to certain buckets. This lets you limit the permissions for the new access key on a per-bucket level. See [Access Key Permissions](#permissions) for more details. ![The limited access switch](create-access-key.jpg) -1. Click the **Create Access Key** button to create the access key. A dialog box appears that displays the new access key and its secret key. While the access key is always visible within the Cloud Manager, its corresponding secrete key is only visible once and cannot be retrieved again after this window is closed. Store this secret key somewhere secure, such as a password manager. +1. Click the **Create Access Key** button to create the access key. A dialog box appears that displays the new access key and its secret key. While the access key is always visible within Cloud Manager, its corresponding secrete key is only visible once and cannot be retrieved again after this window is closed. Store this secret key somewhere secure, such as a password manager. - ![The access key and secret key displayed within the Cloud Manager](secret-key.jpg) + ![The access key and secret key displayed within Cloud Manager](secret-key.jpg) You now have the credentials needed to connect to Object Storage. @@ -52,7 +52,7 @@ You now have the credentials needed to connect to Object Storage. Revoking an access key removes it from your account and no longer provides access to applications that may have used it. You may wish to do this when decommissioning an application, ending a project with a third party developer, or any other situation where an access key is no longer needed. -1. Navigate to the **Access Keys** page in the Cloud Manager (see [View Access Keys](#view-access-keys)). +1. Navigate to the **Access Keys** page in Cloud Manager (see [View Access Keys](#view-access-keys)). 1. Locate the access key you wish to remove and click the corresponding **Revoke** button. diff --git a/docs/products/storage/object-storage/guides/acls/index.md b/docs/products/storage/object-storage/guides/acls/index.md index 1d06b65d7e8..5b43c979b9c 100644 --- a/docs/products/storage/object-storage/guides/acls/index.md +++ b/docs/products/storage/object-storage/guides/acls/index.md @@ -6,9 +6,9 @@ modified: 2022-03-11 aliases: ['/platform/object-storage/how-to-use-object-storage-acls-and-bucket-policies/', '/guides/how-to-use-object-storage-acls-and-bucket-policies/'] --- -Access Control Lists (ACLs) are a method of defining access to Object Storage resources. You can apply ACLs to both buckets and objects, giving users access and controlling their permission level. There are two generalized modes of access: setting buckets and/or objects to be private or public. A few other more granular settings are also available; the [Cloud Manager](#granular-permissions-for-cloud-manager) and [s3cmd](#granular-permissions-for-s3cmd) sections provide information on these respective settings. +Access Control Lists (ACLs) are a method of defining access to Object Storage resources. You can apply ACLs to both buckets and objects, giving users access and controlling their permission level. There are two generalized modes of access: setting buckets and/or objects to be private or public. A few other more granular settings are also available; [Cloud Manager](#granular-permissions-for-cloud-manager) and [s3cmd](#granular-permissions-for-s3cmd) sections provide information on these respective settings. -## ACLs in the Cloud Manager +## ACLs in Cloud Manager ### Granular Permissions for Cloud Manager @@ -25,7 +25,7 @@ Access Control Lists (ACLs) are a method of defining access to Object Storage re ### Bucket Level ACLs in Cloud Manager {{< note >}} -Existing buckets and any new bucket created in the Cloud Manager have a default ACL permission setting of Private. +Existing buckets and any new bucket created in Cloud Manager have a default ACL permission setting of Private. {{< /note >}} 1. If you have not already, log in to the [Linode Cloud Manager](https://cloud.linode.com). @@ -59,7 +59,7 @@ Existing buckets and any new bucket created in the Cloud Manager have a default ### Object Level ACLs in Cloud Manager {{< note >}} -Existing objects and any new objects created in the Cloud Manager have a default ACL permission setting of Private. +Existing objects and any new objects created in Cloud Manager have a default ACL permission setting of Private. {{< /note >}} 1. If you have not already, log in to the [Linode Cloud Manager](https://cloud.linode.com). @@ -147,7 +147,7 @@ The owner of the bucket always has the `full_control` permission. {{< /note >}} {{< note >}} -If you set an ACL that does not map to an ACL in the Cloud Manager, the Cloud Manager displays this as `Custom`. +If you set an ACL that does not map to an ACL in Cloud Manager, Cloud Manager displays this as `Custom`. ![Custom ACL Setting Displayed in Cloud Manager](acl-s3cmd-custom-setting-cloud-manager.png "Custom ACL Setting Displayed in Cloud Manager") {{< /note >}} \ No newline at end of file diff --git a/docs/products/storage/object-storage/guides/aws-sdk-for-php/index.md b/docs/products/storage/object-storage/guides/aws-sdk-for-php/index.md index 187c658a031..6a19d36f8c9 100644 --- a/docs/products/storage/object-storage/guides/aws-sdk-for-php/index.md +++ b/docs/products/storage/object-storage/guides/aws-sdk-for-php/index.md @@ -27,7 +27,7 @@ See [AWS SDK for PHP Docs > Installing the SDK](https://docs.aws.amazon.com/sdk- To access Object Storage buckets and objects, you'll first need to configure your credentials and initialize the S3 client session. -1. Generate an access key and secret key for Object Storage through the Cloud Manager by following the [Managing Access Keys](/docs/products/storage/object-storage/guides/access-keys/) guide. +1. Generate an access key and secret key for Object Storage through Cloud Manager by following the [Managing Access Keys](/docs/products/storage/object-storage/guides/access-keys/) guide. 2. Add the following code to your PHP script, replacing `[access-key]` and `[secret-key]` with the values generated in the previous step. Also replace `[cluster-url]` with the cluster URL corresponding to the data center your buckets are located within (listed on the [Access Buckets and Files through URLs](/docs/products/storage/object-storage/guides/urls/) page). diff --git a/docs/products/storage/object-storage/guides/aws-sdk-for-python/index.md b/docs/products/storage/object-storage/guides/aws-sdk-for-python/index.md index 3881ce34355..18e71e91b9f 100644 --- a/docs/products/storage/object-storage/guides/aws-sdk-for-python/index.md +++ b/docs/products/storage/object-storage/guides/aws-sdk-for-python/index.md @@ -26,7 +26,7 @@ See [Boto3 Docs > Quickstart](https://boto3.amazonaws.com/v1/documentation/api/l To access Object Storage buckets and objects, you'll first need to configure your credentials and initialize the S3 client session. -1. Generate an access key and secret key for Object Storage through the Cloud Manager by following the [Managing Access Keys](/docs/products/storage/object-storage/guides/access-keys/) guide. +1. Generate an access key and secret key for Object Storage through Cloud Manager by following the [Managing Access Keys](/docs/products/storage/object-storage/guides/access-keys/) guide. 2. Add the following code to your python script, replacing `[access-key]` and `[secret-key]` with the values generated in the previous step. Also replace `[cluster-url]` with the cluster URL corresponding to the data center your buckets are located within (listed on the [Access Buckets and Files through URLs](/docs/products/storage/object-storage/guides/urls/) page). diff --git a/docs/products/storage/object-storage/guides/bucket-policies/index.md b/docs/products/storage/object-storage/guides/bucket-policies/index.md index f56c2781455..5aadda60e08 100644 --- a/docs/products/storage/object-storage/guides/bucket-policies/index.md +++ b/docs/products/storage/object-storage/guides/bucket-policies/index.md @@ -79,7 +79,7 @@ A policy is applied to Object Storage **resources**, such as buckets and objects ] {{< note type="alert" >}} -While a resource can target the bucket itself (by removing the `/*` in the first example), this can cause the bucket to become inaccessible to the Cloud Manager, API, and CLI. +While a resource can target the bucket itself (by removing the `/*` in the first example), this can cause the bucket to become inaccessible to Cloud Manager, API, and CLI. {{< /note >}} ## Bucket Policy Examples diff --git a/docs/products/storage/object-storage/guides/cancel/index.md b/docs/products/storage/object-storage/guides/cancel/index.md index 283c2d7d0e9..f3ceb361f1b 100644 --- a/docs/products/storage/object-storage/guides/cancel/index.md +++ b/docs/products/storage/object-storage/guides/cancel/index.md @@ -3,13 +3,13 @@ title: Cancel Object Storage description: "How to cancel the Linode Object Storage service." --- -The following steps outline how to cancel the Object Storage service from the Cloud Manager. +The following steps outline how to cancel the Object Storage service from Cloud Manager. {{< note type="alert" >}} Cancelling Object Storage deletes all objects and buckets from your account. Consider downloading any important files before continuing. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com/), select **Account** from the left menu, and navigate to the **Settings** tab. +1. Log in to [Cloud Manager](https://cloud.linode.com/), select **Account** from the left menu, and navigate to the **Settings** tab. 1. Find the section labeled *Object Storage* and click the **Cancel Object Storage** button. diff --git a/docs/products/storage/object-storage/guides/custom-domain/index.md b/docs/products/storage/object-storage/guides/custom-domain/index.md index 4422877460c..55a4f25360d 100644 --- a/docs/products/storage/object-storage/guides/custom-domain/index.md +++ b/docs/products/storage/object-storage/guides/custom-domain/index.md @@ -8,7 +8,7 @@ tags: ["linode platform","cloud manager"] aliases: ['/platform/object-storage/enable-ssl-for-object-storage/','/guides/enable-ssl-for-object-storage/'] --- -Linode's Object Storage service supports both shared and custom domain names. By default, files can be accessed through secured (HTTPS) URLs within the shared domain *\*.linodeobjects.com*. If you prefer, you can use a custom domain, such as a subdomain of *\*.example.com*. This guide walks you through the configuration of a custom domain and adding a TLS certificate to secure that custom domain. When configuring Linode services, this guide uses the Cloud Manager, though the [Linode CLI](/docs/products/tools/cli/get-started/) and the [Linode API](/docs/api/object-storage/) can be used instead. +Linode's Object Storage service supports both shared and custom domain names. By default, files can be accessed through secured (HTTPS) URLs within the shared domain *\*.linodeobjects.com*. If you prefer, you can use a custom domain, such as a subdomain of *\*.example.com*. This guide walks you through the configuration of a custom domain and adding a TLS certificate to secure that custom domain. When configuring Linode services, this guide uses Cloud Manager, though the [Linode CLI](/docs/products/tools/cli/get-started/) and the [Linode API](/docs/api/object-storage/) can be used instead. ## Before you Begin @@ -69,7 +69,7 @@ You can view the saved certificate using whichever plaintext file viewer or edit To upload your new SSL certificate to an Object Storage Bucket: -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. 1. Open the bucket you wish to use and navigate to the **SSL/TLS** tab. This opens the *SSL/TLS Certificate* page. diff --git a/docs/products/storage/object-storage/guides/cyberduck/index.md b/docs/products/storage/object-storage/guides/cyberduck/index.md index 422e179de9c..5d3ced83a57 100644 --- a/docs/products/storage/object-storage/guides/cyberduck/index.md +++ b/docs/products/storage/object-storage/guides/cyberduck/index.md @@ -46,7 +46,7 @@ Once the connection is successful, a list appears of all the buckets that your a ![Main Cyberduck view of buckets](cyberduck-view.png) {{< note >}} -To create additional buckets, use the Cloud Manager, Linode CLI, s3cmd, or s4cmd. Cyberduck is not able to create new buckets. +To create additional buckets, use Cloud Manager, Linode CLI, s3cmd, or s4cmd. Cyberduck is not able to create new buckets. {{< /note >}} ## Upload and Manage Files diff --git a/docs/products/storage/object-storage/guides/grafana-loki/index.md b/docs/products/storage/object-storage/guides/grafana-loki/index.md index df4ceb21c19..96e650cb224 100644 --- a/docs/products/storage/object-storage/guides/grafana-loki/index.md +++ b/docs/products/storage/object-storage/guides/grafana-loki/index.md @@ -7,7 +7,7 @@ Grafana Loki is a log aggregation and visualization system for cloud-native envi ## Before you start -[Grafana Loki](https://grafana.com/docs/loki/latest/configure/) can integrate with Linode Object Storage as a backend storage solution using the S3 protocol and S3 storage configuration. +[Grafana Loki](https://grafana.com/docs/loki/latest/configure/) can integrate with Linode Object Storage as a back-end storage solution using the S3 protocol and S3 storage configuration. Before you apply the Best Practices to your configuration, review these basic concepts to understand the Loki caching and storage workflow. @@ -24,15 +24,15 @@ Before you apply the Best Practices to your configuration, review these basic co ### Caching During Writing -- During ingestion, chunks may be cached in Memcached immediately after they are written to the backend storage such as, Linode Object Store. -- This proactive caching ensures that recently ingested log data is available for querying. It also avoids the latency that occurs when fetching it from the backend storage. -- Loki manages the indexes and chunks separately even though it may use the same backend storage for both. +- During ingestion, chunks may be cached in Memcached immediately after they are written to the back-end storage such as, Linode Object Store. +- This proactive caching ensures that recently ingested log data is available for querying. It also avoids the latency that occurs when fetching it from the back-end storage. +- Loki manages the indexes and chunks separately even though it may use the same back-end storage for both. ### Caching During Reading - When a query occurs the query engine checks Memcached for the required chunks. - If the query finds the chunks in the cache, it retrieves the chunks directly from Memcached. This results in low-latency query responses. -- Loki fetches chunks that are not present in the cache or chunks evicted due to caching policies from the backend storage. +- Loki fetches chunks that are not present in the cache or chunks evicted due to caching policies from the back-end storage. ### Eviction and Management @@ -56,7 +56,7 @@ You should understand your Loki workload type and evaluate whether it’s single In addition to providing data isolation, the multi-tenancy model allows for horizontal scalability and storage load sharding per tenant. Consider this example to understand the impact of the multi-tenancy workload type. A configuration with one tenant and one bucket only supports 750 mixed RPS for your entire workload. This means that if you have an aggregated workload of 10K queries per second across all your Grafana graphs with a cache configuration that yields a 90% hit ratio: -- ~1K of the requests will land on the backend Object Storage bucket. +- ~1K of the requests will land on the back-end Object Storage bucket. - With one tenant and one bucket, your workload will already exceed the rate limit for the bucket. Alternatively, a configuration with two tenants and two buckets, one each for the org/division/workload type, gets twice the RPS and the workload is unlikely to be rate limited. @@ -92,7 +92,7 @@ To learn more you can read the [Grafana Cloud blog post](https://grafana.com/blo ## Loki Storage Configuration -The `s3_storage_config` block configures the connection to the Linode S3 Object Storage backend. +The `s3_storage_config` block configures the connection to the Linode S3 Object Storage back end. ![Screenshot of the chunk options](loki-storage-config.png) The `bucketnames` storage config parameter allows the Loki tenant workloads to specify more than one bucket. This enables sharding of log data chunks across multiple buckets. It’s highly recommended that you configure more than one bucket, and possibly many depending on the load. This helps with scalability and load balancing since rate limits are enforced at the bucket level. diff --git a/docs/products/storage/object-storage/guides/linode-cli/index.md b/docs/products/storage/object-storage/guides/linode-cli/index.md index 676949eeeb6..7921a0f92aa 100644 --- a/docs/products/storage/object-storage/guides/linode-cli/index.md +++ b/docs/products/storage/object-storage/guides/linode-cli/index.md @@ -4,7 +4,7 @@ description: "Learn how to use the Linode CLI to manage Linode's own Object Stor modified: 2023-06-27 --- -The Linode Command Line Interface (CLI) is a command line utility that allows you complete control over the Linode account. For interacting with Object Storage, there are two separate commands within the Linode CLI. +The Linode Command Line Interface (CLI) is a command line utility that gives you complete control over the Linode account. For interacting with Object Storage, there are two separate commands within the Linode CLI. - `linode object-storage [command]`: This resource provides access to managing Object Storage on a Linode account. - `linode obj [command]`: With the Object Storage plugin, you can also create and remove buckets, upload objects, and more. @@ -103,7 +103,7 @@ If the bucket has objects in it, you can not delete it from the Linode CLI immed ## Create a Signed URL with the CLI -Creating a **signed URL** allows you to create a link to objects with limited permissions and a time limit to access them. To create a signed URL on a preexisting object with the CLI, use the following syntax: +Creating a **signed URL** lets you create a link to objects with limited permissions and a time limit to access them. To create a signed URL on a preexisting object with the CLI, use the following syntax: ```command linode-cli obj signurl my-example-bucket example.txt +300 diff --git a/docs/products/storage/object-storage/guides/manage-buckets/index.md b/docs/products/storage/object-storage/guides/manage-buckets/index.md index d4f4faaefc8..f50758c6a07 100644 --- a/docs/products/storage/object-storage/guides/manage-buckets/index.md +++ b/docs/products/storage/object-storage/guides/manage-buckets/index.md @@ -1,16 +1,16 @@ --- title: "Create and Manage Buckets" -description: "Learn how to view, create, and delete Object Storage buckets through the Cloud Manager." +description: "Learn how to view, create, and delete Object Storage buckets through Cloud Manager." published: 2022-02-07 modified: 2022-03-04 aliases: ['/products/storage/object-storage/guides/create-bucket/','/products/storage/object-storage/guides/delete-bucket/'] --- -Buckets are the primary containers within Object Storage. Each bucket stores your files (objects) and allows you to access or share those files. +Buckets are the primary containers within Object Storage. Each bucket stores your files (objects) and lets you access or share those files. ## View Buckets -Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. If you currently have buckets on your account, they are listed on this page, along with their URL, region, size, and the number of objects (files) they contain. +Log in to [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. If you currently have buckets on your account, they are listed on this page, along with their URL, region, size, and the number of objects (files) they contain. ![](bucket-list.png) @@ -18,9 +18,9 @@ You can also view your bucket through the [Linode CLI](/docs/products/storage/ob ## Create a Bucket -One of the first steps to using Object Storage is to create a bucket. Here's how to create a bucket using the Cloud Manager, though you can also use the [Linode CLI](/docs/products/storage/object-storage/guides/linode-cli/#create-a-bucket-with-the-cli), [s3cmd](/docs/products/storage/object-storage/guides/s3cmd/#create-a-bucket), and [s4cmd](/docs/products/storage/object-storage/guides/s4cmd/#create-a-bucket). +One of the first steps to using Object Storage is to create a bucket. Here's how to create a bucket using Cloud Manager, though you can also use the [Linode CLI](/docs/products/storage/object-storage/guides/linode-cli/#create-a-bucket-with-the-cli), [s3cmd](/docs/products/storage/object-storage/guides/s3cmd/#create-a-bucket), and [s4cmd](/docs/products/storage/object-storage/guides/s4cmd/#create-a-bucket). -1. Navigate to the **Object Storage** page in the Cloud Manager (see [View Buckets](#view-buckets)). +1. Navigate to the **Object Storage** page in Cloud Manager (see [View Buckets](#view-buckets)). 1. Click the **Create Bucket** button to open the *Create Bucket* panel. If you have not created an access key or a bucket on this account, you are prompted to enable Object Storage. @@ -47,15 +47,15 @@ You are now ready to [upload files to the bucket](/docs/products/storage/object- ## Delete a Bucket -Follow these steps to delete an Object Storage bucket from the Cloud Manager. You can also use the [Linode CLI](/docs/products/storage/object-storage/guides/linode-cli/), [s3cmd](/docs/products/storage/object-storage/guides/s3cmd/#delete-a-bucket), and [s4cmd](/docs/products/storage/object-storage/guides/s4cmd/#delete-a-bucket). +Follow these steps to delete an Object Storage bucket from Cloud Manager. You can also use the [Linode CLI](/docs/products/storage/object-storage/guides/linode-cli/), [s3cmd](/docs/products/storage/object-storage/guides/s3cmd/#delete-a-bucket), and [s4cmd](/docs/products/storage/object-storage/guides/s4cmd/#delete-a-bucket). {{< note >}} -Only empty buckets are able to be deleted through the Cloud Manager. To delete objects, see [Delete a File/Object](/docs/products/storage/object-storage/guides/manage-files/#delete-a-file). Alternatively, you can use the following S3cmd command, which deletes a non-empty bucket. See [S3cmd > Delete a Bucket](/docs/products/storage/object-storage/guides/s3cmd/#delete-a-bucket) for more details. +Only empty buckets are able to be deleted through Cloud Manager. To delete objects, see [Delete a File/Object](/docs/products/storage/object-storage/guides/manage-files/#delete-a-file). Alternatively, you can use the following S3cmd command, which deletes a non-empty bucket. See [S3cmd > Delete a Bucket](/docs/products/storage/object-storage/guides/s3cmd/#delete-a-bucket) for more details. s3cmd rb -r -f s3://example-bucket/ {{< /note >}} -1. Navigate to the **Object Storage** page in the Cloud Manager (see [View Buckets](#view-buckets)). +1. Navigate to the **Object Storage** page in Cloud Manager (see [View Buckets](#view-buckets)). 1. Locate the bucket you wish to delete and click the corresponding **Delete** button. diff --git a/docs/products/storage/object-storage/guides/manage-files/index.md b/docs/products/storage/object-storage/guides/manage-files/index.md index 6482f7677a5..d21e91961e7 100644 --- a/docs/products/storage/object-storage/guides/manage-files/index.md +++ b/docs/products/storage/object-storage/guides/manage-files/index.md @@ -4,11 +4,11 @@ description: "" aliases: ['/products/storage/object-storage/guides/upload-objects/','/products/storage/object-storage/guides/delete-objects/','/products/storage/object-storage/guides/view-objects/'] --- -The primary function of Object Storage is to allow you to host files, also called objects. This guide walks you through using the Cloud Manager to view, upload, download, and delete files. +The primary function of Object Storage is to allow you to host files, also called objects. This guide walks you through using Cloud Manager to view, upload, download, and delete files. ## View Files Stored within a Bucket -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. 1. Locate the bucket you wish to view and click its label/name to open it. @@ -20,11 +20,11 @@ The primary function of Object Storage is to allow you to host files, also calle ## Upload Files -Follow these steps to upload objects to a bucket using the Cloud Manager: +Follow these steps to upload objects to a bucket using Cloud Manager: {{% content "object-storage-character-warning-shortguide" %}} -1. Navigate to the **Bucket** page in the Cloud Manager (see [View Files](#view-files-stored-within-a-bucket)). +1. Navigate to the **Bucket** page in Cloud Manager (see [View Files](#view-files-stored-within-a-bucket)). 1. Files can be uploaded through either the dragging and dropping them into the file upload pane or by browsing for the files. @@ -44,7 +44,7 @@ Follow these steps to upload objects to a bucket using the Cloud Manager: ## Download a File -1. Navigate to the **Bucket** page in the Cloud Manager (see [View Files](#view-files-stored-within-a-bucket)). +1. Navigate to the **Bucket** page in Cloud Manager (see [View Files](#view-files-stored-within-a-bucket)). 1. Locate the file you wish to download and click the **Download** button. @@ -54,9 +54,9 @@ Follow these steps to upload objects to a bucket using the Cloud Manager: ## Delete a File -Follow these steps to delete objects in a bucket from the Cloud Manager: +Follow these steps to delete objects in a bucket from Cloud Manager: -1. Navigate to the **Bucket** page in the Cloud Manager (see [View Files](#view-files-stored-within-a-bucket)). +1. Navigate to the **Bucket** page in Cloud Manager (see [View Files](#view-files-stored-within-a-bucket)). 1. Locate the file you wish to delete and click the **Delete** button. diff --git a/docs/products/storage/object-storage/guides/s3cmd/index.md b/docs/products/storage/object-storage/guides/s3cmd/index.md index f411049a46c..a4c639dc57b 100644 --- a/docs/products/storage/object-storage/guides/s3cmd/index.md +++ b/docs/products/storage/object-storage/guides/s3cmd/index.md @@ -209,7 +209,7 @@ s3://example-bucket/ (bucket): ## Create a Signed URL with S3cmd -Creating a **signed URL** allows you to create a link to objects with limited permissions and a time limit to access them. To create a signed URL on a preexisting object with s3cmd, use the following syntax: +Creating a **signed URL** lets you create a link to objects with limited permissions and a time limit to access them. To create a signed URL on a preexisting object with s3cmd, use the following syntax: ```command s3cmd signurl s3://my-example-bucket/example.txt +300 @@ -246,7 +246,7 @@ For more information on hosting a static website with Object Storage, read our [ ## Syncing Files and Directories -While you can utilize the `put` command to upload entire directories, the `sync` command may offer more desirable behavior. `sync` identifies which files have been added or modified and only uploads those files. This can be especially useful when maintaining large amounts of files, such as the contents of a static site. +While you can use the `put` command to upload entire directories, the `sync` command may offer more desirable behavior. `sync` identifies which files have been added or modified and only uploads those files. This can be especially useful when maintaining large amounts of files, such as the contents of a static site. **Command:** `s3cmd sync [local-path] s3://[bucket-label]/[path]`, replacing *[local-path]* with the path to the folder you wish to upload, *[bucket-label]* with the label for your bucket, and *[path]* with the remote path you wish to target for the upload. diff --git a/docs/products/storage/object-storage/guides/urls/index.md b/docs/products/storage/object-storage/guides/urls/index.md index d05cdb33dbc..05382ec00b0 100644 --- a/docs/products/storage/object-storage/guides/urls/index.md +++ b/docs/products/storage/object-storage/guides/urls/index.md @@ -9,7 +9,7 @@ tags: ["linode platform"] aliases: ['/platform/object-storage/how-to-access-objects-with-linode-object-storage/','/guides/how-to-access-objects-with-linode-object-storage/','/products/storage/object-storage/guides/access-objects/'] --- -Linode's Object Storage service gives each bucket and file a unique URL. This URL is managed through the shared domain *\*.linodeobjects.com* and your files are encrypted through the use of HTTPS. By default, files are only visible by you (the owner) through the Cloud Manager or through other tools and applications using an access key with permissions to read (or read/write) the bucket. +Linode's Object Storage service gives each bucket and file a unique URL. This URL is managed through the shared domain *\*.linodeobjects.com* and your files are encrypted through the use of HTTPS. By default, files are only visible by you (the owner) through Cloud Manager or through other tools and applications using an access key with permissions to read (or read/write) the bucket. You're also able to make these files accessible to anyone through their URLs by setting up ACLs so the files are public. This makes Object Storage great for sharing and storing unstructured data like images, documents, archives, streaming media assets, and file backups, and the amount of data you store can range from small collections of files up to massive libraries of information. @@ -59,11 +59,11 @@ For example, a bucket labeled *example-bucket* within the Atlanta data center wo https://example-bucket.us-southeast-1.linodeobjects.com -### View a Bucket's URL through the Cloud Manager +### View a Bucket's URL through Cloud Manager -You can build this URL manually or you can view the bucket URL through the Cloud Manager (as shown below) or a tool like [Cyberduck](/docs/products/storage/object-storage/guides/cyberduck/#obtain-the-url-of-a-file) +You can build this URL manually or you can view the bucket URL through Cloud Manager (as shown below) or a tool like [Cyberduck](/docs/products/storage/object-storage/guides/cyberduck/#obtain-the-url-of-a-file) -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. 1. Locate the bucket you wish to use. The URL for the bucket is printed underneath the bucket label/name. @@ -83,11 +83,11 @@ For example, a file named *example-file.txt* stored on a bucket labeled *example https://example-bucket.us-southeast-1.linodeobjects.com/example-file.txt -### View a File's URL through the Cloud Manager +### View a File's URL through Cloud Manager -You can build this URL manually or you can view the file URL through the Cloud Manager (as shown below) or a tool like [Cyberduck](/docs/products/storage/object-storage/guides/cyberduck/#obtain-the-url-of-a-file) +You can build this URL manually or you can view the file URL through Cloud Manager (as shown below) or a tool like [Cyberduck](/docs/products/storage/object-storage/guides/cyberduck/#obtain-the-url-of-a-file) -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Object Storage** from the left menu. 1. Locate the bucket you wish to view and click its label/name to open it. diff --git a/docs/products/storage/object-storage/guides/versioning/index.md b/docs/products/storage/object-storage/guides/versioning/index.md index 19d99a444a9..8a94d364690 100644 --- a/docs/products/storage/object-storage/guides/versioning/index.md +++ b/docs/products/storage/object-storage/guides/versioning/index.md @@ -15,7 +15,7 @@ Every version of an object counts towards the monthly billable storage quota. Wh ## Using Versioning within Linode's Object Storage Service -While versioning is natively supported within our Object Storage service, none of our first party tooling (such as the Cloud Manager, the Linode CLI, or the Linode API) can manage this feature. Currently, object versioning can only be enabled, disabled, and otherwise managed through third party tools like Cyberduck and the AWS CLI. +While versioning is natively supported within our Object Storage service, none of our first party tooling (such as Cloud Manager, the Linode CLI, or the Linode API) can manage this feature. Currently, object versioning can only be enabled, disabled, and otherwise managed through third party tools like Cyberduck and the AWS CLI. ## Enable Versioning @@ -62,7 +62,7 @@ Now that versioning is enabled, you can test this feature by uploading an exampl This is version 1. -1. Now, upload that file through any tool you wish to use, including the Cloud Manager, Cyberduck, S3cmd, or the AWS CLI. +1. Now, upload that file through any tool you wish to use, including Cloud Manager, Cyberduck, S3cmd, or the AWS CLI. 1. On your local machine, edit that same text file. In our example, we'll edit it to use the following contents: diff --git a/docs/products/tools/api/_index.md b/docs/products/tools/api/_index.md index 93f7e8e5fe7..c6d4908a996 100644 --- a/docs/products/tools/api/_index.md +++ b/docs/products/tools/api/_index.md @@ -1,7 +1,7 @@ --- title: Linode API title_meta: "Linode API Product Documentation" -description: "The Linode API allows you to build the apps you want and programmitically manage your account. It offers secure authentication and third-party integrations and plugins." +description: "The Linode API lets you build the apps you want and programmitically manage your account. It offers secure authentication and third-party integrations and plugins." published: 2020-09-11 modified: 2022-12-06 tab_group_main: diff --git a/docs/products/tools/api/developers/index.md b/docs/products/tools/api/developers/index.md index c3a1ed87b07..e24ed2013f1 100644 --- a/docs/products/tools/api/developers/index.md +++ b/docs/products/tools/api/developers/index.md @@ -14,7 +14,7 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. ## Linode Developed/Supported Tools @@ -40,7 +40,7 @@ The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the L - [Ansible linode_v4 module](https://docs.ansible.com/ansible/latest/modules/linode_v4_module.html): Ansible includes a "linode_v4" module for automating Linode instance provisioning by [Luke Murphy](https://github.com/lwm). -- [Kubernetes External-DNS](https://github.com/kubernetes-incubator/external-dns/blob/master/docs/tutorials/linode.md): External-DNS is a Kubernetes Incubator project that assigns DNS names to Service and Ingress resources in Kubernetes Clusters. Linode DNS Manager is a supported backend. +- [Kubernetes External-DNS](https://github.com/kubernetes-incubator/external-dns/blob/master/docs/tutorials/linode.md): External-DNS is a Kubernetes Incubator project that assigns DNS names to Service and Ingress resources in Kubernetes Clusters. Linode DNS Manager is a supported back end. - [terraform-provider-acme](https://www.terraform.io/docs/providers/acme/dns_providers/linode.html): The Automated Certificate Management Environment (ACME) provider for Terraform can be used to configure Let's Encrypt, Boulder, and other ACME CAs using Linode's DNS Manager. diff --git a/docs/products/tools/api/get-started/index.md b/docs/products/tools/api/get-started/index.md index e1e93a66b50..14c1f98f91a 100644 --- a/docs/products/tools/api/get-started/index.md +++ b/docs/products/tools/api/get-started/index.md @@ -10,7 +10,7 @@ aliases: ['/products/tools/linode-api/get-started/','/platform/api/getting-start tags: ["managed hosting"] --- -The Linode API allows you to automate any task that can be performed by the Cloud Manager. This includes creating and managing all of our products (like Compute Instances and Firewalls), your customer account (like adding new users or viewing invoices), and even creating support tickets. As an example of an API call, the command below deploys a new 2GB Compute Instance in the Newark data center using the Debian 11 image. +The Linode API lets you automate any task that can be performed by Cloud Manager. This includes creating and managing all of our products (like Compute Instances and Firewalls), your customer account (like adding new users or viewing invoices), and even creating support tickets. As an example of an API call, the command below deploys a new 2GB Compute Instance in the Newark data center using the Debian 11 image. ```command curl -X POST https://api.linode.com/v4/linode/instances \ @@ -40,7 +40,7 @@ If you are building an application which needs to authenticate multiple users (f For full instructions on creating and managing personal access tokens, see [Manage Personal Access Tokens](/docs/products/tools/api/guides/manage-api-tokens/#create-an-api-token). -1. Log in to the Cloud Manager. +1. Log in to Cloud Manager. 1. Click on your username at the top of the screen and select **My Profile**. @@ -48,7 +48,7 @@ For full instructions on creating and managing personal access tokens, see [Mana 1. Click on **Create Personal Access Token** and choose the access rights you want users authenticated with the new token to have. -1. When you have finished, click **Create** to generate an API token string. Copy the token and save it in a secure location. **You will not be able to view the token through the Cloud Manager after closing the popup.** +1. When you have finished, click **Create** to generate an API token string. Copy the token and save it in a secure location. **You will not be able to view the token through Cloud Manager after closing the popup.** ## Authenticate Requests diff --git a/docs/products/tools/cli/_index.md b/docs/products/tools/cli/_index.md index 317963e2a18..8d20e483b90 100644 --- a/docs/products/tools/cli/_index.md +++ b/docs/products/tools/cli/_index.md @@ -1,7 +1,7 @@ --- title: Linode CLI title_meta: "Linode CLI Product Documentation" -description: "The Linode CLI allows you to accelerate common tasks with customizable output and easy scripting." +description: "The Linode CLI lets you accelerate common tasks with customizable output and easy scripting." tab_group_main: is_root: true title: Overview @@ -11,7 +11,7 @@ cascade: product_description: "Access the entire Linode platform from the command line, easily adding, removing, or modifying services." --- -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the [Linode API](/docs/products/tools/api/), which gives you the ability to manage your Linode account from the command line. Almost any task that can be done through the Cloud Manager can also be performed through the CLI. +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the [Linode API](/docs/products/tools/api/), which gives you the ability to manage your Linode account from the command line. Almost any task that can be done through Cloud Manager can also be performed through the CLI. ## Features diff --git a/docs/products/tools/cli/guides/cli-v3/index.md b/docs/products/tools/cli/guides/cli-v3/index.md index 793c6e0b6c6..31793e6a27c 100644 --- a/docs/products/tools/cli/guides/cli-v3/index.md +++ b/docs/products/tools/cli/guides/cli-v3/index.md @@ -247,7 +247,7 @@ linode options --api-key SampleKey123456... The default Linode CLI user is stored in the `.linodecli/config` file. -To set up the API for additional Linode users, you can run the `linode configure` command again, supplying a different username. Configuration files for additional users are stored with the file name pattern `.linodecli/config_user1`, with **user1** being replaced by the actual username. +To set up the API for additional Linode users, you can run the `linode configure` command again, supplying a different username. Configuration files for additional users are stored with the filename pattern `.linodecli/config_user1`, with **user1** being replaced by the actual username. To invoke the CLI with a particular username, use the `-u user1` option, with **user1** being your actual username, at the end of the command. @@ -288,7 +288,7 @@ If you do something via the CLI that costs money (creating a Linode, upgrading a ### Linodes -The Linode CLI allows you to spin up new Linodes, issue reboots, upgrade plan sizes, and more. +The Linode CLI lets you spin up new Linodes, issue reboots, upgrade plan sizes, and more. Listing Linodes: @@ -439,7 +439,7 @@ man linode-domain ### NodeBalancers -The Linode CLI allows you to manage your [NodeBalancers](/docs/products/networking/nodebalancers/) from the command line. +The Linode CLI lets you manage your [NodeBalancers](/docs/products/networking/nodebalancers/) from the command line. Listing NodeBalancers: @@ -473,7 +473,7 @@ man linode-nodebalancer ### StackScripts -The Linode CLI allows you to create and show StackScripts, and more. +The Linode CLI lets you create and show StackScripts, and more. Creating a StackScript: @@ -497,7 +497,7 @@ man linode-stackscript ### Account -The CLI allows you to view your account billing details at a glance. Run the following command: +The CLI lets you view your account billing details at a glance. Run the following command: ```command linode account show diff --git a/docs/products/tools/cli/guides/install/index.md b/docs/products/tools/cli/guides/install/index.md index 495d3058168..2fabd1d2326 100644 --- a/docs/products/tools/cli/guides/install/index.md +++ b/docs/products/tools/cli/guides/install/index.md @@ -72,7 +72,7 @@ To configure the CLI without any interactive prompts, you can set the token thro export LINODE_CLI_TOKEN="[token]" ``` -This allows you to bypass the initial configuration. If this variable is unset, the Linode CLI will stop working until it is set again or until the CLI is reconfigured through the interactive prompts. +This lets you bypass the initial configuration. If this variable is unset, the Linode CLI will stop working until it is set again or until the CLI is reconfigured through the interactive prompts. ## Install Python 3 and pip3 diff --git a/docs/products/tools/cli/guides/manage-multiple-accounts/index.md b/docs/products/tools/cli/guides/manage-multiple-accounts/index.md index 6dd9b7a5c46..669c2c9d81d 100644 --- a/docs/products/tools/cli/guides/manage-multiple-accounts/index.md +++ b/docs/products/tools/cli/guides/manage-multiple-accounts/index.md @@ -4,7 +4,7 @@ description: "How to use the Linode CLI to manage multiple Linode accounts." published: 2022-12-06 --- -The Linode CLI can be configured to run commands from multiple users on separate Linode Accounts. This allows you to control multiple accounts, all through the same system, using the Linode CLI. Once multiple users are configured, you can execute commands as a particular user or set a specific user as the default. +The Linode CLI can be configured to run commands from multiple users on separate Linode Accounts. This lets you control multiple accounts, all through the same system, using the Linode CLI. Once multiple users are configured, you can execute commands as a particular user or set a specific user as the default. ## Configure an Additional User diff --git a/docs/products/tools/cloud-manager/developers/index.md b/docs/products/tools/cloud-manager/developers/index.md index 5043c4da54f..bf6b9370a7e 100644 --- a/docs/products/tools/cloud-manager/developers/index.md +++ b/docs/products/tools/cloud-manager/developers/index.md @@ -13,4 +13,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line, similar to Cloud Manager. \ No newline at end of file +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line, similar to Cloud Manager. \ No newline at end of file diff --git a/docs/products/tools/cloud-manager/guides/events-and-activity-feeds/index.md b/docs/products/tools/cloud-manager/guides/events-and-activity-feeds/index.md index a5088545c61..02abd0299de 100644 --- a/docs/products/tools/cloud-manager/guides/events-and-activity-feeds/index.md +++ b/docs/products/tools/cloud-manager/guides/events-and-activity-feeds/index.md @@ -21,7 +21,7 @@ Events are only shown to a logged in user if that event is within the scope of t Events for all services and account functions can be viewed in Cloud Manager, either through the Events panel or the [Events](https://cloud.linode.com/events) page. -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and press the notification bell on the top right of the page. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and press the notification bell on the top right of the page. ![The notification bell icon on Cloud Manager](cloud-manager-notification-bell.png) @@ -35,7 +35,7 @@ Events for all services and account functions can be viewed in Cloud Manager, ei A Linode's Activity Feed is similar to the Account's [Events](#events) page. However, this is a filtered list of events only relevant to the specific Linode. Follow the instructions below to access a Linode's Activity Feed. -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select **Linodes** from the sidebar menu. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select **Linodes** from the sidebar menu. 1. Locate the Linode you wish to see events for and click on the Linode's label. @@ -53,7 +53,7 @@ Each time an event occurs, you can automatically receive an email notifying you Only unrestricted users can receive threshold notification emails. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and click the user dropdown menu on the top right of the page. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and click the user dropdown menu on the top right of the page. ![The username dropdown link on Cloud Manager](cloud-manager-user-dropdown.png) diff --git a/docs/products/tools/cloud-manager/guides/overview-of-cloud-manager/index.md b/docs/products/tools/cloud-manager/guides/overview-of-cloud-manager/index.md index fdc6d74dc3b..a4772ae2311 100644 --- a/docs/products/tools/cloud-manager/guides/overview-of-cloud-manager/index.md +++ b/docs/products/tools/cloud-manager/guides/overview-of-cloud-manager/index.md @@ -22,7 +22,7 @@ This guide provides an overview of the features and services available in Cloud ## Linodes -The Linodes section of Cloud Manager allows you to create and manage your Linodes. Each Linode instance in Cloud Manager includes: +The Linodes section of Cloud Manager lets you create and manage your Linodes. Each Linode instance in Cloud Manager includes: - [Summary information](/docs/products/compute/compute-instances/guides/monitor-and-maintain/#cloud-manager) about your Linode, like CPU usage, IPv4 and [IPv6 traffic](/docs/products/compute/compute-instances/guides/ipv6/), and Disk IO - Access to any of your Linode's attached Volumes and the ability to [create a Volume](/docs/products/storage/block-storage/guides/manage-volumes/) @@ -50,7 +50,7 @@ Linode's [NodeBalancers service](https://www.linode.com/products/nodebalancers/) ## Domains (DNS Manager) -The DNS Manager allows you to control and manage your domains. You can access the DNS Manager by navigating to the **Domains** link in Cloud Manager's sidebar. +The DNS Manager lets you control and manage your domains. You can access the DNS Manager by navigating to the **Domains** link in Cloud Manager's sidebar. ![Cloud Manager Domains](classic-to-cloud-cloud-manager-domains.png "Cloud Manager Domains") @@ -86,13 +86,13 @@ To get started using StackScripts in Cloud Manager, see the [Automate Deployment ## Images -The Images section of Cloud Manager gives you access to Linode Images which allow you to take snapshots of your disks, and then deploy them to any Linode under your account. This can be useful for bootstrapping a master image for a large deployment, or retaining a disk for a configuration that you may not need running, but wish to return to in the future. +The Images section of Cloud Manager gives you access to Linode Images which allow you to take snapshots of your disks, and then deploy them to any Linode under your account. This can be useful for bootstrapping an image for a large deployment, or retaining a disk for a configuration that you may not need running, but wish to return to in the future. To get started using Images with Cloud Manager, see [Linode Images](/docs/products/tools/images/). ## Account (Management and Billing) -The **Account** section of Cloud Manager allows you to manage your account's billing information and users, and to configure various account-wide settings. +The **Account** section of Cloud Manager lets you manage your account's billing information and users, and to configure various account-wide settings. You can manage the following account and billing settings in the Account section of Cloud Manager: @@ -152,7 +152,7 @@ Cloud Manager provides a way to set your preferred UI theme, including a light t 1. Navigate to your profile by clicking on your username and select **My Settings**. -1. Within the **Theme** section, select your preferred theme from the available options: *Light*, *Dark*, or *System*. Once a selection is made, the Cloud Manager interface immediately switches to that theme. +1. Within the **Theme** section, select your preferred theme from the available options: *Light*, *Dark*, or *System*. Once a selection is made, Cloud Manager's interface immediately switches to that theme. ### Set the Timezone diff --git a/docs/products/tools/images/developers/index.md b/docs/products/tools/images/developers/index.md index b20c5caf90e..01b3cc99555 100644 --- a/docs/products/tools/images/developers/index.md +++ b/docs/products/tools/images/developers/index.md @@ -13,4 +13,4 @@ Linode’s API v4 provides the ability to programmatically manage the full range ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to [use and install the Linode CLI](/docs/products/tools/cli/get-started/) to get started. \ No newline at end of file +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to [use and install the Linode CLI](/docs/products/tools/cli/get-started/) to get started. \ No newline at end of file diff --git a/docs/products/tools/images/get-started/index.md b/docs/products/tools/images/get-started/index.md index ed11ecf6407..aa63aafb52f 100644 --- a/docs/products/tools/images/get-started/index.md +++ b/docs/products/tools/images/get-started/index.md @@ -6,7 +6,7 @@ tab_group_main: weight: 20 --- -All Images stored on your Account are visible from the main **Images** page within the Cloud Manager. Images are divided between two tables: *Custom Images* and *Recovery Images*. +All Images stored on your Account are visible from the main **Images** page within Cloud Manager. Images are divided between two tables: *Custom Images* and *Recovery Images*. - **Custom Images:** Images that are manually created by a user on the account. These Images were either captured from an existing Compute Instance's disk or uploaded from an image file. Custom Images do not expire and remain on the account until they are manually deleted. @@ -14,14 +14,14 @@ All Images stored on your Account are visible from the main **Images** page with ## Creating an Image -Within the **Images** page of the Cloud Manager, click **Create Image**. +Within the **Images** page of Cloud Manager, click **Create Image**. - To capture an Image from an existing Compute Instances's disk, complete the form under the **Capture Image** tab. See [Capture an Image](/docs/products/tools/images/guides/capture-an-image/) for full instructions. - To upload an Image using an image file, complete the form under the **Upload Image** tab. See [Upload an Image](/docs/products/tools/images/guides/upload-an-image/) for full instructions. ## Deploying and Managing Existing Images -To take action on an Image, locate the Image within the **Images** page of the Cloud Manager and click the corresponding **ellipsis** options menu. From here, there are a few actions that can be initiated: +To take action on an Image, locate the Image within the **Images** page of Cloud Manager and click the corresponding **ellipsis** options menu. From here, there are a few actions that can be initiated: - **Edit:** Change the *Label* and *Description* for the Image. - **Deploy to a New Compute Instance:** Create a new Compute Instance using the Image. See [Deploy an Image to a New Compute Instance](/docs/products/tools/images/guides/deploy-image-to-new-linode/). diff --git a/docs/products/tools/images/guides/capture-an-image/index.md b/docs/products/tools/images/guides/capture-an-image/index.md index a5c797eb850..932745343a7 100644 --- a/docs/products/tools/images/guides/capture-an-image/index.md +++ b/docs/products/tools/images/guides/capture-an-image/index.md @@ -14,13 +14,13 @@ When capturing an image file from an existing Linode Compute Instance, keep the - **The disk must be formatted using ext3/ext4 filesystems.** Images cannot be created if you are using raw disks or disks that have been formatted using custom filesystems. CoreOS disk images are in RAW format. Images made from CoreOS disks can't be used to deploy new Linodes. -- **Power off Linode to avoid database corruption.** If your Linode is running any active databases, it's recommended to power off the Linode down prior to creating the image. Creating an image that includes a running database can cause corruption or data loss in the imaged copy of the database. +- **Power off Linode to avoid database corruption.** If your Linode is running any active databases, it's recommended to power off the Linode down before creating the image. Creating an image that includes a running database can cause corruption or data loss in the imaged copy of the database. - **Only the selected disk is saved to the Image.** The Image is comprised only of the disk selected during the creation process. The Image does not store other aspects of the Linode, such as Configuration Profiles, Block Storage Volumes, IP Addresses, and other Linode-based settings. -## Capturing an Image through the Cloud Manager +## Capturing an Image through Cloud Manager -1. Log in to the Cloud Manager and open the **[Capture Image](https://cloud.linode.com/images/create/disk)** form by navigating to the **Images** page, clicking the **Create Image** button, and staying on the **Capture Image** tab. +1. Log in to Cloud Manager and open the **[Capture Image](https://cloud.linode.com/images/create/disk)** form by navigating to the **Images** page, clicking the **Create Image** button, and staying on the **Capture Image** tab. 1. Select your *Linode* and *Disk* from their respective dropdown lists and type in an optional *Label* and *Description* for the Image. If no *Label* is entered, the label for the disk will be used. When selecting a Linode and Disk, keep in mind any limitations that may prevent the Image from creating successfully. diff --git a/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md b/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md index d2bacd2d4fa..c9580f46eb3 100644 --- a/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md +++ b/docs/products/tools/images/guides/deploy-image-to-existing-linode/index.md @@ -15,7 +15,7 @@ There are two methods to deploy an Image to an existing Compute Instance: A common method of deploying an Image is to rebuild an existing Compute Instance with your desired Image. This deletes all data and disks on that Instance and creates new disks for the selected Image. Use this method only if you no longer need the data that's stored on the Instance. -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and navigate to the **Images** page. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and navigate to the **Images** page. 1. Locate the Image you wish to deploy and click the corresponding **ellipsis** options menu. Select **Rebuild an Existing Linode**. @@ -23,7 +23,7 @@ A common method of deploying an Image is to rebuild an existing Compute Instance 1. Within the **Restore from Image** panel that appears, select the Compute Instance to use and click the **Restore Image** button. - ![The 'Restore from Image' panel in the Cloud Manager](restore-from-image-panel.png) + ![The 'Restore from Image' panel in Cloud Manager](restore-from-image-panel.png) 1. You are redirected to the dashboard page for that Linode and the **Rebuild** form is displayed with the chosen Image preselected. Complete the remainder of this form, making sure to select your desired **Root Password**, and any other options that may be needed. See [Rescue and Rebuild → Rebuilding](/docs/products/compute/compute-instances/guides/rescue-and-rebuild/#rebuilding) for full instructions on rebuilding a Linode. @@ -33,9 +33,9 @@ A common method of deploying an Image is to rebuild an existing Compute Instance If you instead wish to retain the data on your Compute Instance, you can add a disk with your desired Image to that Instance. This is useful if you wish to have multiple bootable configurations and only need to access one at a time. -1. Log in to the [Cloud Manager](https://cloud.linode.com/), click the **[Linodes](https://cloud.linode.com/linodes)** link in the sidebar, and select a Compute Instance from the list. +1. Log in to [Cloud Manager](https://cloud.linode.com/), click the **[Linodes](https://cloud.linode.com/linodes)** link in the sidebar, and select a Compute Instance from the list. -1. **Create a disk with the Image**. Follow the instructions to [create a disk](/docs/products/compute/compute-instances/guides/disks-and-storage/#create-a-disk) using the [Cloud Manager](https://cloud.linode.com/). Keep the following considerations in mind: +1. **Create a disk with the Image**. Follow the instructions to [create a disk](/docs/products/compute/compute-instances/guides/disks-and-storage/#create-a-disk) using [Cloud Manager](https://cloud.linode.com/). Keep the following considerations in mind: - Confirm there is enough unallocated storage space to accommodate the new disk for the desired Image. If you aren't sure of the size of the Image, open the **[Images](https://cloud.linode.com/images)** page, find the Image within the list, and view the *Size* column. - When creating the disk, select the **Create from Image** option and select the Image you wish to deploy. diff --git a/docs/products/tools/images/guides/deploy-image-to-new-linode/index.md b/docs/products/tools/images/guides/deploy-image-to-new-linode/index.md index f2f6eb639da..df89d92a46d 100644 --- a/docs/products/tools/images/guides/deploy-image-to-new-linode/index.md +++ b/docs/products/tools/images/guides/deploy-image-to-new-linode/index.md @@ -4,7 +4,7 @@ description: "Learn how to create a new Compute Instance from a Custom or Recove modified: 2022-07-12 --- -1. Log in to the Cloud Manager and navigate to the **Images** page. +1. Log in to Cloud Manager and navigate to the **Images** page. 1. On this page, locate the Image you wish to deploy and click the corresponding **ellipsis** options menu. Select **Deploy to a New Linode**. diff --git a/docs/products/tools/images/guides/upload-an-image/index.md b/docs/products/tools/images/guides/upload-an-image/index.md index e92c6f7fc43..e17b4607e2b 100644 --- a/docs/products/tools/images/guides/upload-an-image/index.md +++ b/docs/products/tools/images/guides/upload-an-image/index.md @@ -35,7 +35,7 @@ If you do intend on creating a custom image file to upload, here are a few metho After the image file has been created, it needs to be compressed using the gzip utility. -- **Linux and macOS**: Run the following command, replacing *[file.img.gz]* with the file name of your image. See [Archiving and Compressing files with GNU Tar and GNU Zip](/docs/guides/archiving-and-compressing-files-with-gnu-tar-and-gnu-zip/) for additional information on gzip. +- **Linux and macOS**: Run the following command, replacing *[file.img.gz]* with the filename of your image. See [Archiving and Compressing files with GNU Tar and GNU Zip](/docs/guides/archiving-and-compressing-files-with-gnu-tar-and-gnu-zip/) for additional information on gzip. gzip [file.img] @@ -43,21 +43,21 @@ After the image file has been created, it needs to be compressed using the gzip #### Determining the Uncompressed File Size -Knowing the *uncompressed* size of an image file is helpful for planning the storage requirements of Linodes deployed using that image. This information also ensures you stay within the [limits of the Images service](/docs/products/tools/images/guides/upload-an-image/#requirements-and-considerations). The best way to determine the uncompressed size of a gzip archive is to uncompress that archive and then examine its file size. Alternatively, use the zcat utility by run the following command, replacing *[file.img.gz]* with the file name of your image. +Knowing the *uncompressed* size of an image file is helpful for planning the storage requirements of Linodes deployed using that image. This information also ensures you stay within the [limits of the Images service](/docs/products/tools/images/guides/upload-an-image/#requirements-and-considerations). The best way to determine the uncompressed size of a gzip archive is to uncompress that archive and then examine its file size. Alternatively, use the zcat utility by run the following command, replacing *[file.img.gz]* with the filename of your image. zcat [file.img.gz] | wc -c -## Uploading an Image File through the Cloud Manager +## Uploading an Image File through Cloud Manager Once you have obtained a compatible image file that meets all the requirements, upload it through the **Upload Image** Cloud Manager form. After it's uploaded, you can then deploy Linodes using that Custom Image. -1. Log in to the Cloud Manager and open the **[Upload Image](https://cloud.linode.com/images/create/upload)** form by navigating to the **Images** page, clicking the **Create Image** button, and selecting the **Upload Image** tab. +1. Log in to Cloud Manager and open the **[Upload Image](https://cloud.linode.com/images/create/upload)** form by navigating to the **Images** page, clicking the **Create Image** button, and selecting the **Upload Image** tab. 1. Type in the *Label* of the new Image along with an optional *Description*. Select the *Region* you would like the Image to be created within. Since Images can be deployed to any data center (regardless of where they are located), it's recommended that you select the one closest to you geographically for the fastest upload speed. 1. Specify the image file you'd like to use by either dragging the file into the designated area or by clicking the **Browse Files** button and selecting the file. The filename will appear along with a progress bar indicating the percentage completed for the file upload. -1. Once the image file has been successfully uploaded, the Custom Image is created and the Cloud Manager will redirect you to the main Images page. Here, you should see the new Custom Image listed along with a status of *Pending Upload*. Once the Custom Image is ready to be deployed, the status will change to *Ready*. +1. Once the image file has been successfully uploaded, the Custom Image is created and Cloud Manager will redirect you to the main Images page. Here, you should see the new Custom Image listed along with a status of *Pending Upload*. Once the Custom Image is ready to be deployed, the status will change to *Ready*. ![Image status](images-upload-status.png "Image status") diff --git a/docs/products/tools/images/resources/index.md b/docs/products/tools/images/resources/index.md index 6a4e1d472ea..f4c644570e5 100644 --- a/docs/products/tools/images/resources/index.md +++ b/docs/products/tools/images/resources/index.md @@ -26,7 +26,7 @@ Some of the community posts that answer questions related to custom images: - [How do I restore a deleted Linode?](https://www.linode.com/community/questions/17441/how-do-i-restore-a-deleted-linode) -- [Unable to create an image of my disk from the Cloud Manager interface](https://www.linode.com/community/questions/17929/unable-to-create-an-image-of-my-disk-from-the-cloud-manager-interface) +- [Unable to create an image of my disk from Cloud Manager's interface](https://www.linode.com/community/questions/17929/unable-to-create-an-image-of-my-disk-from-the-cloud-manager-interface) - [Is there a way to duplicate my current Linode?](https://www.linode.com/community/questions/20100/is-there-a-way-to-duplicate-my-current-linode) diff --git a/docs/products/tools/longview/developers/index.md b/docs/products/tools/longview/developers/index.md index a9bf8cc88b7..73a3f1d94dc 100644 --- a/docs/products/tools/longview/developers/index.md +++ b/docs/products/tools/longview/developers/index.md @@ -14,4 +14,4 @@ Linode’s API v4 provides the ability to programmatically manage the full range ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. Learn how to [use and install the Linode CLI](/docs/products/tools/cli/get-started/) to get started. \ No newline at end of file +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. Learn how to [use and install the Linode CLI](/docs/products/tools/cli/get-started/) to get started. \ No newline at end of file diff --git a/docs/products/tools/longview/get-started/index.md b/docs/products/tools/longview/get-started/index.md index 30049448117..1679dba2f08 100644 --- a/docs/products/tools/longview/get-started/index.md +++ b/docs/products/tools/longview/get-started/index.md @@ -18,7 +18,7 @@ To start using Longview to capture metrics from a Linux server, you need to crea ## Create a Longview Client {#create-client} -1. Log in to the [Cloud Manager](https://cloud.linode.com/dashboard) and click on the **Longview** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/dashboard) and click on the **Longview** link in the sidebar. 1. On the Longview Clients page, click on the **Add a Client** link on the top right-hand corner. This creates a Longview Client instance. @@ -28,7 +28,7 @@ To start using Longview to capture metrics from a Linux server, you need to crea The displayed `curl` command is used in the next section to install the Longview agent on the desired Linux system. The long string appended to the url `https://lv.linode.com/` is your Longview Client instance's GUID (globally unique identifier). {{< /note >}} - ![Screenshot of a new Longview client in the Cloud Manager](longview-waiting.png) + ![Screenshot of a new Longview client in Cloud Manager](longview-waiting.png) ## SSH into the Compute Instance {#ssh} @@ -206,10 +206,10 @@ sudo systemctl start longview ## View Longview Client Statistics {#view-statistics} -Switch back to the Cloud Manager's Longview Clients page in your browser and verify that system information and metrics have started to appear. To learn more about the metrics available on Longview, see [Understanding Longview Metrics](/docs/products/tools/longview/guides/metrics/). +Switch back to Cloud Manager's Longview Clients page in your browser and verify that system information and metrics have started to appear. To learn more about the metrics available on Longview, see [Understanding Longview Metrics](/docs/products/tools/longview/guides/metrics/). -![Screenshot of a Longview Client in the Cloud Manager](longview-data.png) +![Screenshot of a Longview Client in Cloud Manager](longview-data.png) {{< note >}} -It can take several minutes for data to load and display in the Cloud Manager. +It can take several minutes for data to load and display in Cloud Manager. {{< /note >}} \ No newline at end of file diff --git a/docs/products/tools/longview/guides/apache/index.md b/docs/products/tools/longview/guides/apache/index.md index c008f2d36d8..a553cbadbab 100644 --- a/docs/products/tools/longview/guides/apache/index.md +++ b/docs/products/tools/longview/guides/apache/index.md @@ -14,7 +14,7 @@ relations: - distribution: Apache --- -In addition to capturing general system metrics, Longview can also be used to capture metrics for Apache. The Apache tab appears in the Cloud Manager when Longview detects that you have Apache installed on your system. It can help you keep track of Apache's settings, workers and requests, system resource consumption, and other information. +In addition to capturing general system metrics, Longview can also be used to capture metrics for Apache. The Apache tab appears in Cloud Manager when Longview detects that you have Apache installed on your system. It can help you keep track of Apache's settings, workers and requests, system resource consumption, and other information. {{< note >}} In order to use Longview to capture data for Apache, you must have the Longview Agent successfully installed on the system you wish to monitor. See [Create a Longview Client and Install the Longview Agent](/docs/products/tools/longview/get-started/). @@ -25,7 +25,7 @@ In order to use Longview to capture data for Apache, you must have the Longview This guide covers using Longview with Apache and includes the following topics: - [Configuring Longview for Apache](#configure-longview). -- [Interacting with the Apache data provided by Longview in the Cloud Manager](#view-metrics). +- [Interacting with the Apache data provided by Longview in Cloud Manager](#view-metrics). - [Troubleshooting Longview for Apache](#troubleshooting). ## Configure Longview for Apache {#configure-longview} @@ -57,7 +57,7 @@ If Apache is installed and running when you install the Longview agent, Longview Found Apache status page at http://127.0.0.1/server-status?auto specified in /etc/linode/longview.d/Apache.conf ``` - Once you see this successful message, the Longview should automatically start collecting Apache data. Refresh Longview in the Cloud Manager to start viewing your Apache stats for your Longview Client instance. + Once you see this successful message, the Longview should automatically start collecting Apache data. Refresh Longview in Cloud Manager to start viewing your Apache stats for your Longview Client instance. If you receive a failure message or the popup shown below, you should visit the [Troubleshooting](#troubleshooting) section at the end of this article. @@ -142,7 +142,7 @@ You should now be able to see Longview data for Apache. If that's not the case, ## View Apache Metrics {#view-metrics} -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select the **Longview** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select the **Longview** link in the sidebar. 1. Locate the Longview Client you have configured for Apache and click the corresponding **View details** link. @@ -229,7 +229,7 @@ If you choose: update-rc.d: using dependency based boot sequencing ``` - Refresh the Longview Apache tab in the Cloud Manager to verify that it's working now. + Refresh the Longview Apache tab in Cloud Manager to verify that it's working now. If instead you receive a failure message, such as: @@ -282,7 +282,7 @@ To fix this, follow these steps: location http://localhost/whm-server-status?auto ``` -1. Longview is designed to check the default location automatically. If you use the default location shown above, you should be done. Refresh the Longview in the Cloud Manager to verify that it's working now. +1. Longview is designed to check the default location automatically. If you use the default location shown above, you should be done. Refresh the Longview in Cloud Manager to verify that it's working now. 1. If you're not using the default location, you need to create a new file, `/etc/linode/longview.d/Apache.conf`, and set the `location` variable to match what you set in the Apache configuration file: @@ -304,7 +304,7 @@ To fix this, follow these steps: sudo service longview restart ``` -1. Refresh the Longview in the Cloud Manager to verify that it's working now. +1. Refresh the Longview in Cloud Manager to verify that it's working now. ### The Apache Status Page Doesn't Look Right @@ -333,7 +333,7 @@ To resolve this issue, follow these steps: sudo systemctl restart longview ``` -1. Refresh the Longview in the Cloud Manager to verify that it's working now. +1. Refresh the Longview in Cloud Manager to verify that it's working now. ### Missing Graphs: Enable ExtendedStatus diff --git a/docs/products/tools/longview/guides/change-plan/index.md b/docs/products/tools/longview/guides/change-plan/index.md index 0cdafae442f..83687fda3af 100644 --- a/docs/products/tools/longview/guides/change-plan/index.md +++ b/docs/products/tools/longview/guides/change-plan/index.md @@ -12,7 +12,7 @@ Currently, it is not possible to have both *Longview Free* and *Longview Pro* cl To change your plan level or to view all available Longview Pro plans, follow these steps: -1. Log in to the [Cloud Manager](https://cloud.linode.com/dashboard) and click on the **Longview** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/dashboard) and click on the **Longview** link in the sidebar. 1. Viewing the Longview Clients listing page, click on the **Plan Details** tab. @@ -20,7 +20,7 @@ To change your plan level or to view all available Longview Pro plans, follow th 1. If you would like to change your current plan, select your preferred plan and click on the **Change Plan** button. You will see the page update to denote your current Longview plan. -![Screenshot of the Longview Plan Details screen in the Cloud Manager](longview-change-plan.png) +![Screenshot of the Longview Plan Details screen in Cloud Manager](longview-change-plan.png) {{< note type="warning" >}} If you change your plan, your Longview Client data will temporarily be in a transitional state. Any irregularities in your displayed Longview data will clear up shortly. diff --git a/docs/products/tools/longview/guides/metrics/index.md b/docs/products/tools/longview/guides/metrics/index.md index 64017a886d4..22a906a4db6 100644 --- a/docs/products/tools/longview/guides/metrics/index.md +++ b/docs/products/tools/longview/guides/metrics/index.md @@ -10,7 +10,7 @@ This guide provides an overview of the data and graphs available to you after su ## Access your Longview Client Metrics -1. To view a Longview Client's detailed graphs and metrics, log in to the [Cloud Manager](https://cloud.linode.com/) and click on the **Longview** link in the sidebar. +1. To view a Longview Client's detailed graphs and metrics, log in to [Cloud Manager](https://cloud.linode.com/) and click on the **Longview** link in the sidebar. 1. On the Longview Clients listing page, click on the **View Details** button corresponding to the client whose system statistics you'd like to view. This displays the information and metrics for the corresponding system. From here, you can select from the following tabs to view specific metrics: @@ -38,9 +38,9 @@ The graphs only show data captured *after* the Longview Agent was installed on t ## View Data Points on Graphs -When viewing graphs in the Cloud Manager, you can hover over data points in the x-axis to view specific metrics for that data point. +When viewing graphs in Cloud Manager, you can hover over data points in the x-axis to view specific metrics for that data point. -![Screenshot of a data point on a graph in the Cloud Manager](longview-metrics-graph-data-point.png) +![Screenshot of a data point on a graph in Cloud Manager](longview-metrics-graph-data-point.png) ## Overview diff --git a/docs/products/tools/longview/guides/mysql/index.md b/docs/products/tools/longview/guides/mysql/index.md index 78c5df44ed3..88a20174caf 100644 --- a/docs/products/tools/longview/guides/mysql/index.md +++ b/docs/products/tools/longview/guides/mysql/index.md @@ -15,7 +15,7 @@ relations: --- -In addition to capturing general system metrics, Longview can also be used to capture metrics for MySQL. The MySQL tab appears in the Cloud Manager when Longview detects that you have MySQL installed on your system. It can help you keep track of MySQL's queries, system resource consumption, and other information. +In addition to capturing general system metrics, Longview can also be used to capture metrics for MySQL. The MySQL tab appears in Cloud Manager when Longview detects that you have MySQL installed on your system. It can help you keep track of MySQL's queries, system resource consumption, and other information. {{< note >}} In order to use Longview to capture data for MySQL, you must have the Longview Agent successfully installed on the system you wish to monitor. See [Create a Longview Client and Install the Longview Agent](/docs/products/tools/longview/get-started/). @@ -26,7 +26,7 @@ In order to use Longview to capture data for MySQL, you must have the Longview A This guide covers using Longview with MySQL and includes the following topics: - [Configuring Longview for MySQL](#configure-longview). -- [Interacting with the MySQL data provided by Longview in the Cloud Manager](#view-metrics). +- [Interacting with the MySQL data provided by Longview in Cloud Manager](#view-metrics). - [Troubleshooting Longview for MySQL](#troubleshooting). ## Configure Longview with MySQL {#configure-longview} @@ -58,7 +58,7 @@ If MySQL is installed and running when you install the Longview agent, Longview Successfully connected to MySQL ``` - Once you see this successful message, the Longview should automatically start collecting MySQL data. Refresh Longview in the Cloud Manager to start viewing your MySQL metrics for your Longview Client instance. + Once you see this successful message, the Longview should automatically start collecting MySQL data. Refresh Longview in Cloud Manager to start viewing your MySQL metrics for your Longview Client instance. {{< note >}} Unless you already have a specific Longview database user set up in the `/etc/linode/longview.d/MySQL.conf` file, Longview will locate and use the `debian-sys-maint` database user credentials if it can, located at `/etc/mysql/debian.cnf`. @@ -112,13 +112,13 @@ You cannot configure the location of a socket for the Longview client. sudo systemctl restart longview ``` -1. Refresh Longview in the Cloud Manager to verify that the MySQL tab is now present and collecting data for your Longview client instance. +1. Refresh Longview in Cloud Manager to verify that the MySQL tab is now present and collecting data for your Longview client instance. You should now be able to see Longview data for MySQL. If that's not the case, proceed to the [Troubleshooting](#troubleshooting) section at the end of this article. ## View MySQL Metrics {#view-metrics} -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select the **Longview** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select the **Longview** link in the sidebar. 1. Locate the Longview Client you have configured for MySQL and click the corresponding **View details** link. @@ -193,7 +193,7 @@ This indicates that Longview can't locate any valid MySQL user credentials, so i flush privileges; ``` - Refresh Longview in the Cloud Manager to verify that the MySQL tab is now present and collecting data for your Longview client instance. + Refresh Longview in Cloud Manager to verify that the MySQL tab is now present and collecting data for your Longview client instance. If you've added the credentials to MySQL and it still doesn't work, double-check your MySQL installation, and then do a [manual configuration](#manual-configuration-all-distributions). diff --git a/docs/products/tools/longview/guides/nginx/index.md b/docs/products/tools/longview/guides/nginx/index.md index cb7de0c8cc9..701e9514e29 100644 --- a/docs/products/tools/longview/guides/nginx/index.md +++ b/docs/products/tools/longview/guides/nginx/index.md @@ -14,7 +14,7 @@ relations: - distribution: NGINX --- -In addition to capturing general system metrics, Longview can also be used to capture metrics for NGINX. The NGINX tab appears in the Cloud Manager when Longview detects that you have NGINX installed on your system. It can help you keep track of NGINX workers, requests, system resource consumption, and other information. +In addition to capturing general system metrics, Longview can also be used to capture metrics for NGINX. The NGINX tab appears in Cloud Manager when Longview detects that you have NGINX installed on your system. It can help you keep track of NGINX workers, requests, system resource consumption, and other information. {{< note >}} In order to use Longview to capture data for NGIXN, you must have the Longview Agent successfully installed on the system you wish to monitor. See [Create a Longview Client and Install the Longview Agent](/docs/products/tools/longview/get-started/). @@ -25,7 +25,7 @@ In order to use Longview to capture data for NGIXN, you must have the Longview A This guide covers using Longview with NGINX and includes the following topics: - [Configuring Linode Longview for NGINX](#configure-longview). -- [Interacting with the NGINX data provided by Longview in the Cloud Manager](#view-metrics). +- [Interacting with the NGINX data provided by Longview in Cloud Manager](#view-metrics). - [Troubleshooting Linode Longview for NGINX](#troubleshooting). ## Configure Longview for NGINX {#configure-longview} @@ -82,7 +82,7 @@ If NGINX is installed and running when you install the Longview agent, Longview The automatic configuration sets the status page location to `http://127.0.0.2/nginx_status`. {{< /note >}} -1. Refresh Longview in the Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. +1. Refresh Longview in Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. If instead you received a failure message similar to the output example, double-check your NGINX installation and then perform a [manual configuration](#manual-configuration). You can also visit the [Troubleshooting](#troubleshooting) section at the end of this guide. @@ -130,13 +130,13 @@ To enable the NGINX Longview integration manually, follow these steps on your sy sudo systemctl restart longview ``` -1. Refresh Longview in the Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. +1. Refresh Longview in Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. You should now be able to see Longview data for NGINX. If that's not the case, proceed to the [Troubleshooting](#troubleshooting) section at the end of this article. ## View NGINX Metrics {#view-metrics} -1. Log in to the [Cloud Manager](https://cloud.linode.com/) and select the **Longview** link in the sidebar. +1. Log in to [Cloud Manager](https://cloud.linode.com/) and select the **Longview** link in the sidebar. 1. Locate the Longview Client you have configured for NGINX and click the corresponding **View details** link. @@ -214,7 +214,7 @@ To fix this, follow these steps: } ``` -1. Longview is designed to check the default location automatically. If you use the default location shown above, you should be done. Refresh Longview in the Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. +1. Longview is designed to check the default location automatically. If you use the default location shown above, you should be done. Refresh Longview in Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. 1. If you're not using the default location, you need to create a new file, `/etc/linode/longview.d/Nginx.conf`, and set the `location` variable to match what you set in the NGINX configuration file: @@ -228,7 +228,7 @@ To fix this, follow these steps: sudo systemctl restart nginx ``` -1. Refresh Longview in the Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. +1. Refresh Longview in Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. {{< note >}} If you originally compiled NGINX without the status module, you will need to recompile it with `--with-http_stub_status_module` and all your other settings. Then go back and try to enable the Longview Nginx App. @@ -261,7 +261,7 @@ To resolve this issue, follow these steps: sudo systemctl restart longview ``` -1. Refresh Longview in the Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. +1. Refresh Longview in Cloud Manager to verify that the NGINX tab is now present and collecting data for your Longview client instance. ### NGINX Tab is Missing diff --git a/docs/products/tools/longview/guides/troubleshooting/index.md b/docs/products/tools/longview/guides/troubleshooting/index.md index 66e0aba6784..9bb3614a0d1 100644 --- a/docs/products/tools/longview/guides/troubleshooting/index.md +++ b/docs/products/tools/longview/guides/troubleshooting/index.md @@ -131,9 +131,9 @@ If you use iptables, you should also make sure to persist any of your firewall r The API key given in the Linode Cloud Manager should match that on your system in `/etc/linode/longview.key`. -1. In the Cloud Manager, the API key is located in the **Installation** tab of your Longview Client instance's [detailed view](/docs/products/tools/longview/get-started/). +1. In Cloud Manager, the API key is located in the **Installation** tab of your Longview Client instance's [detailed view](/docs/products/tools/longview/get-started/). -1. SSH into your Linode. The Longview key is located at `/etc/linode/longview.key`. Use `cat` to view the contents of that file and compare it to what's shown in the Cloud Manager: +1. SSH into your Linode. The Longview key is located at `/etc/linode/longview.key`. Use `cat` to view the contents of that file and compare it to what's shown in Cloud Manager: ```command cat /etc/linode/longview.key diff --git a/docs/products/tools/marketplace/_shortguides/deploy-marketplace-app-cluster-shortguide/index.md b/docs/products/tools/marketplace/_shortguides/deploy-marketplace-app-cluster-shortguide/index.md index e2e81450995..e48b7d6dacc 100644 --- a/docs/products/tools/marketplace/_shortguides/deploy-marketplace-app-cluster-shortguide/index.md +++ b/docs/products/tools/marketplace/_shortguides/deploy-marketplace-app-cluster-shortguide/index.md @@ -1,13 +1,13 @@ --- -# Shortguide: Instructions on deploying a Marketplace App Cluster from the Cloud Manager +# Shortguide: Instructions on deploying a Marketplace App Cluster from Cloud Manager headless: true show_on_rss_feed: false --- -The Linode Marketplace allows you to easily deploy an application cluster on Compute Instances using the Cloud Manager. See [Get Started with Marketplace Apps](/docs/products/tools/marketplace/get-started/) for complete steps. +The Linode Marketplace lets you easily deploy an application cluster on Compute Instances using Cloud Manager. See [Get Started with Marketplace Apps](/docs/products/tools/marketplace/get-started/) for complete steps. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select the **Marketplace** link from the left navigation menu. This displays the Linode **Create** page with the **Marketplace** tab pre-selected. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select the **Marketplace** link from the left navigation menu. This displays the Linode **Create** page with the **Marketplace** tab pre-selected. 1. Under the **Select App** section, select the cluster app you would like to deploy. Marketplace Apps that are deployed as clusters have a **cluster** label next to the app's name. diff --git a/docs/products/tools/marketplace/_shortguides/deploy-marketplace-apps-shortguide/index.md b/docs/products/tools/marketplace/_shortguides/deploy-marketplace-apps-shortguide/index.md index a34c675fcaf..2b1f2e5ee31 100644 --- a/docs/products/tools/marketplace/_shortguides/deploy-marketplace-apps-shortguide/index.md +++ b/docs/products/tools/marketplace/_shortguides/deploy-marketplace-apps-shortguide/index.md @@ -1,13 +1,13 @@ --- -# Shortguide: Instructions on deploying a Marketplace App from the Cloud Manager +# Shortguide: Instructions on deploying a Marketplace App from Cloud Manager headless: true show_on_rss_feed: false --- -The Linode Marketplace allows you to easily deploy software on a Compute Instance using the Cloud Manager. See [Get Started with Marketplace Apps](/docs/products/tools/marketplace/get-started/) for complete steps. +The Linode Marketplace lets you easily deploy software on a Compute Instance using Cloud Manager. See [Get Started with Marketplace Apps](/docs/products/tools/marketplace/get-started/) for complete steps. -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select the **Marketplace** link from the left navigation menu. This displays the Linode **Create** page with the **Marketplace** tab pre-selected. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select the **Marketplace** link from the left navigation menu. This displays the Linode **Create** page with the **Marketplace** tab pre-selected. 1. Under the **Select App** section, select the app you would like to deploy. diff --git a/docs/products/tools/marketplace/_shortguides/marketplace-required-limited-user-fields-shortguide/index.md b/docs/products/tools/marketplace/_shortguides/marketplace-required-limited-user-fields-shortguide/index.md index 1a4be3c8d08..f335f172423 100644 --- a/docs/products/tools/marketplace/_shortguides/marketplace-required-limited-user-fields-shortguide/index.md +++ b/docs/products/tools/marketplace/_shortguides/marketplace-required-limited-user-fields-shortguide/index.md @@ -14,7 +14,7 @@ You need to fill out the following fields to automatically create a limited sudo {{< note type="warning" title="Locating The Generated Sudo Password">}} A password is generated for the limited user and stored in a `.credentials` file in their home directory, along with application specific passwords. This can be viewed by running: `cat /home/$USERNAME/.credentials` - For best results, add an [account SSH key](/docs/products/platform/accounts/guides/manage-ssh-keys/) for the Cloud Manager user that is deploying the instance, and select that user as an `authorized_user` in the API or by selecting that option in the Cloud Manager. Their SSH pubkey will be assigned to _both_ root and the limited user. + For best results, add an [account SSH key](/docs/products/platform/accounts/guides/manage-ssh-keys/) for the Cloud Manager user that is deploying the instance, and select that user as an `authorized_user` in the API or by selecting that option in Cloud Manager. Their SSH pubkey will be assigned to _both_ root and the limited user. {{< /note >}} - **Disable root access over SSH:** To block the root user from logging in over SSH, select *Yes*. You can still switch to the root user once logged in, and you can also log in as root through [Lish](/docs/products/compute/compute-instances/guides/lish/). diff --git a/docs/products/tools/marketplace/developers/index.md b/docs/products/tools/marketplace/developers/index.md index 34cd4a2d13b..04fc671c93d 100644 --- a/docs/products/tools/marketplace/developers/index.md +++ b/docs/products/tools/marketplace/developers/index.md @@ -14,7 +14,7 @@ Marketplace applications are deployed in the API via the ## Linode CLI - The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. + The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. ## App Developers and Marketplace Contributors diff --git a/docs/products/tools/marketplace/get-started/index.md b/docs/products/tools/marketplace/get-started/index.md index 26307c65f5b..0153a813a3c 100644 --- a/docs/products/tools/marketplace/get-started/index.md +++ b/docs/products/tools/marketplace/get-started/index.md @@ -20,7 +20,7 @@ When a Marketplace App is deployed, a new Compute Instance is created and the ap There are two types of deployments available: single instances and clusters. Most Marketplace Apps that are available in the Linode Marketplace are single instances and, as such, only deploy a single Compute Instance to your account. If an app is marked with the `cluster` label, it instead creates multiple Compute Instances as part of a cluster deployment. {{< /note >}} -1. Log in to the [Cloud Manager](https://cloud.linode.com) and select the **Marketplace** link from the left navigation menu. This displays the Linode **Create** page with the **Marketplace** tab pre-selected. +1. Log in to [Cloud Manager](https://cloud.linode.com) and select the **Marketplace** link from the left navigation menu. This displays the Linode **Create** page with the **Marketplace** tab pre-selected. 1. Under the **Select App** section, select the app you would like to deploy. Click on the info icon (**i**) to open the details panel for that app and learn more about the included software. Within the panel, there is also a link to the corresponding guide where you can learn how to deploy and access that Marketplace App. diff --git a/docs/products/tools/marketplace/guides/aapanel/index.md b/docs/products/tools/marketplace/guides/aapanel/index.md index cbff17c0586..8b116bd89ca 100644 --- a/docs/products/tools/marketplace/guides/aapanel/index.md +++ b/docs/products/tools/marketplace/guides/aapanel/index.md @@ -11,7 +11,7 @@ external_resources: - '[aaPanel Documentation](https://doc.aapanel.com/web)' --- -[aaPanel](https://www.aapanel.com/) is a free and open source web hosting control panel. It allows you to manage the server's web server, websites, databases, FTP, and more through a simple web-based interface. Through aaPanel, you can quickly install a LEMP (NGINX) or LAMP (Apache) stack on your server and start hosting your websites. +[aaPanel](https://www.aapanel.com/) is a free and open source web hosting control panel. It lets you manage the server's web server, websites, databases, FTP, and more through a simple web-based interface. Through aaPanel, you can quickly install a LEMP (NGINX) or LAMP (Apache) stack on your server and start hosting your websites. ## Deploying a Marketplace App diff --git a/docs/products/tools/marketplace/guides/akaunting/index.md b/docs/products/tools/marketplace/guides/akaunting/index.md index bdbb8508006..ef270e4fdc4 100644 --- a/docs/products/tools/marketplace/guides/akaunting/index.md +++ b/docs/products/tools/marketplace/guides/akaunting/index.md @@ -50,6 +50,6 @@ It is built with modern technologies (such as Laravel and VueJS) and includes a 1. The Akaunting login page appears. The username for this instance is the *Admin Email* and the password is the *Admin Password* that you set when you deployed this One-Click Marketplace App. -Now that you’ve accessed your dashboard, check out [the official Akaunting documentation](https://akaunting.com/docs) to learn how to further utilize your Akaunting instance. +Now that you’ve accessed your dashboard, check out [the official Akaunting documentation](https://akaunting.com/docs) to learn how to further use your Akaunting instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/appwrite/index.md b/docs/products/tools/marketplace/guides/appwrite/index.md index 2312c5a18f7..a58d185cfba 100644 --- a/docs/products/tools/marketplace/guides/appwrite/index.md +++ b/docs/products/tools/marketplace/guides/appwrite/index.md @@ -6,7 +6,7 @@ keywords: ['Appwrite','Firebase','backend', 'low-code'] tags: ["marketplace", "linode platform", "cloud manager"] --- -[Appwrite](https://appwrite.io/) is an open-source, self-hosted backend server that provides developers with a set of tools and services to build and manage web and mobile applications. It offers various features to simplify the development process, including user authentication, database management, file storage, and more. +[Appwrite](https://appwrite.io/) is an open-source, self-hosted back-end server that provides developers with a set of tools and services to build and manage web and mobile applications. It offers various features to simplify the development process, including user authentication, database management, file storage, and more. ## Deploying a Marketplace App @@ -33,7 +33,7 @@ tags: ["marketplace", "linode platform", "cloud manager"] ![Screenshot of the Appwrite login page](appwrite-signin.png) -1. The sign up page should open, which allows you to create a new user on this Appwrite deployment. Enter your name, your email address, and a secure password. Then, click the **Sign up** button. +1. The sign up page should open, which lets you create a new user on this Appwrite deployment. Enter your name, your email address, and a secure password. Then, click the **Sign up** button. ![Screenshot of the Appwrite sign up page](appwrite-signup.png) @@ -45,6 +45,6 @@ tags: ["marketplace", "linode platform", "cloud manager"] ![Screenshot of the Appwrite project screen](appwrite-project.png) -Now that you’ve accessed your Appwrite instance, check out [the official Appwrite documentation](https://appwrite.io/docs) to learn how to further utilize your instance. +Now that you’ve accessed your Appwrite instance, check out [the official Appwrite documentation](https://appwrite.io/docs) to learn how to further use your instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/azuracast/index.md b/docs/products/tools/marketplace/guides/azuracast/index.md index 5ca6a83b5cc..a055babcc47 100644 --- a/docs/products/tools/marketplace/guides/azuracast/index.md +++ b/docs/products/tools/marketplace/guides/azuracast/index.md @@ -63,8 +63,8 @@ The AzuraCast Marketplace App installs the following software on your Linode: | **Software** | **Description** | |:--------------|:------------| | [**Lquidsoap**](https://www.liquidsoap.info/) | An AutoDJ that keeps the tunes streaming.| -| [**Icecast 2.4 (Icecast-KH on supported systems)**](https://icecast.org/) | A broadcasting frontend. | -| [**SHOUTcast 2 DNAS**](http://wiki.shoutcast.com/wiki/SHOUTcast_DNAS_Server_2) | An alternate broadcasting frontend. | +| [**Icecast 2.4 (Icecast-KH on supported systems)**](https://icecast.org/) | A broadcasting front end. | +| [**SHOUTcast 2 DNAS**](http://wiki.shoutcast.com/wiki/SHOUTcast_DNAS_Server_2) | An alternate broadcasting front end. | | [**NGINX**](https://www.nginx.com/) | A webserver a proxy. | | [**MariaDB**](https://mariadb.org/) | A database. | | [**PHP 7**](https://secure.php.net/) | General purpose programming language used for the website. | diff --git a/docs/products/tools/marketplace/guides/beef/index.md b/docs/products/tools/marketplace/guides/beef/index.md index 2bed5734c71..79093b73597 100644 --- a/docs/products/tools/marketplace/guides/beef/index.md +++ b/docs/products/tools/marketplace/guides/beef/index.md @@ -10,7 +10,7 @@ external_resources: aliases: ['/guides/deploying-beef-marketplace-app/','/guides/beef-marketplace-app/'] --- -[BeEF](https://beefproject.com/) (The Browser Exploitation Framework) is a penetration testing tool that focuses on the web browser. BeEF offers an efficient and affective penetration test tool to assess the actual security posture of a target environment by using client-side attack vectors. BeEF looks beyond just the network perimeter and client system. It allows you to examine exploitability within the context of the web browser. +[BeEF](https://beefproject.com/) (The Browser Exploitation Framework) is a penetration testing tool that focuses on the web browser. BeEF offers an efficient and affective penetration test tool to assess the actual security posture of a target environment by using client-side attack vectors. BeEF looks beyond just the network perimeter and client system. It lets you examine exploitability within the context of the web browser. ## Deploying a Marketplace App @@ -43,7 +43,7 @@ aliases: ['/guides/deploying-beef-marketplace-app/','/guides/beef-marketplace-ap 1. Once the app has been *fully* deployed, view the BeEF completion message through one of the methods below: - - **Lish Console:** Within the Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). + - **Lish Console:** Within Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). - **SSH:** Log in to your Compute Instance over SSH using the `root` user and run the following command. See [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/) for assistance. ```command @@ -74,6 +74,6 @@ aliases: ['/guides/deploying-beef-marketplace-app/','/guides/beef-marketplace-ap ``` {{< /note >}} -Now that you’ve accessed your BeEF instance, check out [the official BeEF documentation](https://github.com/beefproject/beef/wiki) to learn how to further utilize your BeEF instance. +Now that you’ve accessed your BeEF instance, check out [the official BeEF documentation](https://github.com/beefproject/beef/wiki) to learn how to further use your BeEF instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/bitninja/index.md b/docs/products/tools/marketplace/guides/bitninja/index.md index d42f97bf778..3347b804034 100644 --- a/docs/products/tools/marketplace/guides/bitninja/index.md +++ b/docs/products/tools/marketplace/guides/bitninja/index.md @@ -48,6 +48,6 @@ BitNinja requires a valid license to use the software beyond the initial 7 day [ ### Accessing the BitNinja App -Now that you’ve deployed your BitNinja instance, check out [the official BitNinja documentation](https://doc.bitninja.io/docs/command_line_interface#usage) to learn how to further utilize your BitNinja instance. +Now that you’ve deployed your BitNinja instance, check out [the official BitNinja documentation](https://doc.bitninja.io/docs/command_line_interface#usage) to learn how to further use your BitNinja instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/chevereto/index.md b/docs/products/tools/marketplace/guides/chevereto/index.md index c76d6738d88..ba72f4af4cc 100644 --- a/docs/products/tools/marketplace/guides/chevereto/index.md +++ b/docs/products/tools/marketplace/guides/chevereto/index.md @@ -48,7 +48,7 @@ Chevereto requires a valid license to use the software. To purchase a license, v ![Chevereto Installer](chevereto-installer.png) -1. To utilize Chevereto, you need to obtain a license key. You can do so by clicking the purchase button and entering the license key provided by Chevereto. +1. To use Chevereto, you need to obtain a license key. You can do so by clicking the purchase button and entering the license key provided by Chevereto. ![Chevereto License](chevereto-license.png) @@ -56,7 +56,7 @@ Chevereto requires a valid license to use the software. To purchase a license, v ![Chevereto cPanel](chevereto-cpanel.png) -1. The next page allows you to input the database information for this application. It should be pre-filled with the user and password details. +1. The next page lets you input the database information for this application. It should be pre-filled with the user and password details. ![Chevereto Database](chevereto-database.png) diff --git a/docs/products/tools/marketplace/guides/cpanel/index.md b/docs/products/tools/marketplace/guides/cpanel/index.md index ca4169ebb3d..3a6a73402a9 100644 --- a/docs/products/tools/marketplace/guides/cpanel/index.md +++ b/docs/products/tools/marketplace/guides/cpanel/index.md @@ -47,7 +47,7 @@ WHM is the core interface for managing your server and all websites (also called 1. Next, enter in the email address where you would prefer to receive notifications and alerts. -1. On the same page, you must also enter in the nameservers for this server. Nameservers are the underlying servers of the DNS system that map domain names to IP addresses. Managing DNS through cPanel allows you to quickly add sites, configure subdomains, set up email, and more without needing to manually update DNS records. For this step, make sure you have a registered domain name. +1. On the same page, you must also enter in the nameservers for this server. Nameservers are the underlying servers of the DNS system that map domain names to IP addresses. Managing DNS through cPanel lets you quickly add sites, configure subdomains, set up email, and more without needing to manually update DNS records. For this step, make sure you have a registered domain name. 1. Within the nameservers for your domain name, create two [*A records*](/docs/guides/dns-overview/#a-and-aaaa). The *hostname* / *name* field should be *ns1* (for the first record) and *ns2* (for the second). The IP address should be the IPv4 address of your new Compute Instance. If you do not have a nameserver for your registered domain, consider using Linode's [DNS Manager](/docs/products/networking/dns-manager/). diff --git a/docs/products/tools/marketplace/guides/discourse/index.md b/docs/products/tools/marketplace/guides/discourse/index.md index b5d0c2450b1..3d628b9bf94 100644 --- a/docs/products/tools/marketplace/guides/discourse/index.md +++ b/docs/products/tools/marketplace/guides/discourse/index.md @@ -68,12 +68,12 @@ Discourse requires that you have a domain name and SMTP email. These fields are Discourse is now installed and ready to use. -1. Your A and AAAA Domain records for the domain and subdomain, if you designated one, have been created and you should see them in the Cloud Manager. +1. Your A and AAAA Domain records for the domain and subdomain, if you designated one, have been created and you should see them in Cloud Manager. - - In the Cloud Manager [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/), confirm that there are now an entries for your domain and possible subdomain. + - In Cloud Manager's [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/), confirm that there are now an entries for your domain and possible subdomain. - [Configure rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) on your Linode to point to `subdomain.your-domain.com` or `your-domain.com` if you did not enter a subdomain. -1. While the installation has created the A and AAAA domain records, it does not create the email records you need. In the Cloud Manager DNS Manager, [add the MX, TXT, and any other records](/docs/products/networking/dns-manager/guides/manage-dns-records/) required to send email as specified by your email provider. +1. While the installation has created the A and AAAA domain records, it does not create the email records you need. In Cloud Manager DNS Manager, [add the MX, TXT, and any other records](/docs/products/networking/dns-manager/guides/manage-dns-records/) required to send email as specified by your email provider. 1. You can now navigate to the Discourse app in your browser with the fully qualified domain name you entered during configuration, `https://subdomain.your-domain.com` or `https://your-domain.com`. @@ -100,7 +100,7 @@ The Discourse Marketplace App installs the following software on your Linode: | **Software** | **Description** | |:--------------|:------------| | [**Discourse**](https://www.discourse.org/) | Discourse is an open source discussion platform that provides a forum, mailing list, chat room, and more. | -| [**ufw**](https://wiki.ubuntu.com/UncomplicatedFirewall) | ufw is the uncomplicated firewall, a frontend for iptables. | +| [**ufw**](https://wiki.ubuntu.com/UncomplicatedFirewall) | ufw is the uncomplicated firewall, a front end for iptables. | {{% content "email-warning-shortguide" %}} diff --git a/docs/products/tools/marketplace/guides/easypanel/index.md b/docs/products/tools/marketplace/guides/easypanel/index.md index aff0a1089f0..4f82bbeb7d2 100644 --- a/docs/products/tools/marketplace/guides/easypanel/index.md +++ b/docs/products/tools/marketplace/guides/easypanel/index.md @@ -31,6 +31,6 @@ tags: ["marketplace", "linode platform", "cloud manager"] ![Screenshot of the Easypanel setup page](easypanel-setup.png) -1. After logging in, the admin control panel appears. From there, you can manage your projects. Check out [the official Easypanel documentation](https://easypanel.io/docs) to learn how to further utilize your Easypanel instance. +1. After logging in, the admin control panel appears. From there, you can manage your projects. Check out [the official Easypanel documentation](https://easypanel.io/docs) to learn how to further use your Easypanel instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/focalboard/index.md b/docs/products/tools/marketplace/guides/focalboard/index.md index d0e95f19cb8..cc3c88d041f 100644 --- a/docs/products/tools/marketplace/guides/focalboard/index.md +++ b/docs/products/tools/marketplace/guides/focalboard/index.md @@ -58,6 +58,6 @@ aliases: ['/guides/focalboard-marketplace-app/'] ![The Focalboard Create a Board page](focalboard-create-board.png) -Now that you’ve accessed your dashboard, check out [the official Focalboard documentation](https://www.focalboard.com/guide/user/) to learn how to further utilize your Focalboard instance. +Now that you’ve accessed your dashboard, check out [the official Focalboard documentation](https://www.focalboard.com/guide/user/) to learn how to further use your Focalboard instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/galera-cluster/index.md b/docs/products/tools/marketplace/guides/galera-cluster/index.md index cddb47f91d2..1e53cbfd7d0 100644 --- a/docs/products/tools/marketplace/guides/galera-cluster/index.md +++ b/docs/products/tools/marketplace/guides/galera-cluster/index.md @@ -11,7 +11,7 @@ external_resources: - '[MySQLdb User''s Guide](http://mysql-python.sourceforge.net/MySQLdb.html)' --- -Galera provides a performant MariaDB database solution with synchronous replication to achieve high availability. Galera is deployed with MariaDB, which is an open-source database management system that uses a relational database and SQL (Structured Query Language) to manage its data. MariaDB was originally based off of MySQL and maintains backwards compatibility. +Galera provides a performant MariaDB database solution with synchronous replication to achieve high availability. Galera is deployed with MariaDB, which is an open-source database management system that uses a relational database and SQL (Structured Query Language) to manage its data. MariaDB was originally based off of MySQL and maintains backward compatibility. {{< note type="warning" title="Marketplace App Cluster Notice" >}} This Marketplace App deploys 3 Compute Instances to create a highly available and redundant MariaDB Galera cluster, each with the plan type and size that you select. Please be aware that each of these Compute Instances will appear on your invoice as separate items. To instead deploy MariaDB on a single Compute Instance, see [Deploy MySQL/MariaDB through the Linode Marketplace](/docs/products/tools/marketplace/guides/mysql/). @@ -97,7 +97,7 @@ The standard tool for interacting with MariaDB is the `mysql` client which insta prompt (\R) Change your mysql prompt. quit (\q) Quit mysql. rehash (\#) Rebuild completion hash. - source (\.) Execute an SQL script file. Takes a file name as an argument. + source (\.) Execute an SQL script file. Takes a filename as an argument. status (\s) Get status information from the server. system (\!) Execute a system shell command. tee (\T) Set outfile [to_outfile]. Append everything into given outfile. diff --git a/docs/products/tools/marketplace/guides/gitea/index.md b/docs/products/tools/marketplace/guides/gitea/index.md index d8158a4c7c2..a0a46a20fb3 100644 --- a/docs/products/tools/marketplace/guides/gitea/index.md +++ b/docs/products/tools/marketplace/guides/gitea/index.md @@ -7,7 +7,7 @@ keywords: ['Gitea','version control','git'] tags: ["linode platform","version control system","marketplace","cloud-manager"] external_resources: - '[Gitea Documentation](https://docs.gitea.io/)' -aliases: ['/guides/deploy-gitea-with-one-click-apps/', '/guides/deploy-gitea-with-marketplace-apps/', '/guides/deploy-Gitea-with-marketplace-apps/','/guides/gitea-marketplace-app/'] +aliases: ['/guides/deploy-gitea-with-one-click-apps/', '/guides/deploy-gitea-with-marketplace-apps/', '/guides/gitea-marketplace-app/'] --- [Gitea](https://gitea.io/) is a community managed, painless, self-hosted Git service. Gitea is a complete solution for all aspects of your software development. At its core, Gitea serves as your centralized remote Git repository. Gitea also features built-in tools that represent every task in your development workflow, from planning to testing to releasing. diff --git a/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md b/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md index 83ac264055c..1bb450c08fd 100644 --- a/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md +++ b/docs/products/tools/marketplace/guides/glusterfs-cluster/index.md @@ -37,7 +37,7 @@ external_resources: {{% content "marketplace-required-limited-user-fields-shortguide" %}} {{% content "marketplace-special-character-limitations-shortguide" %}} -- **List of IP addresses to whitelist:** A list of IP address that will be whitelisted to the GlusterFS cluster. These should be client IPs that will mount GlusterFS. SSL certificates will be created for the provided IP addresses. +- **List of IP addresses to whitelist:** A list of IP address that will be allowed to access GlusterFS cluster. These should be client IPs that will mount GlusterFS. SSL certificates will be created for the provided IP addresses. ## Getting Started After Deployment diff --git a/docs/products/tools/marketplace/guides/grav/index.md b/docs/products/tools/marketplace/guides/grav/index.md index e4c07bab4ab..07d7ed4d8f0 100644 --- a/docs/products/tools/marketplace/guides/grav/index.md +++ b/docs/products/tools/marketplace/guides/grav/index.md @@ -53,6 +53,6 @@ aliases: ['/guides/grav-marketplace-app/'] ![Screenshot of the Admin dashboard](grav-admin.png) -Now that you’ve accessed your dashboard, check out [the official Grav documentation](https://learn.getgrav.org/) to learn how to further utilize your Grav instance. +Now that you’ve accessed your dashboard, check out [the official Grav documentation](https://learn.getgrav.org/) to learn how to further use your Grav instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/harbor/index.md b/docs/products/tools/marketplace/guides/harbor/index.md index 88d85040a0e..1c3e4b681f7 100644 --- a/docs/products/tools/marketplace/guides/harbor/index.md +++ b/docs/products/tools/marketplace/guides/harbor/index.md @@ -47,7 +47,7 @@ Harbor is an excellent compliment to the [Linode Kubernetes Engine (LKE)](/docs/ 1. To locate your Harbor login credentials, view the Harbor credentials file through one of the methods below: - - **Lish Console:** Within the Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). + - **Lish Console:** Within Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). - **SSH:** Log in to your Compute Instance over SSH using the `root` user and run the following command. See [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/) for assistance. ```command @@ -58,6 +58,6 @@ Harbor is an excellent compliment to the [Linode Kubernetes Engine (LKE)](/docs/ ![Harbor Login Page](harbor-login.png) -Now that you’ve accessed your dashboard, check out [the official Harbor documentation](https://goharbor.io/docs/2.3.0/administration/) to learn how to further utilize your Harbor instance. +Now that you’ve accessed your dashboard, check out [the official Harbor documentation](https://goharbor.io/docs/2.3.0/administration/) to learn how to further use your Harbor instance. {{% content "marketplace-update-note-shortguide" %}} diff --git a/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md b/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md index b5697b57bf3..0df07ac97b0 100644 --- a/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md +++ b/docs/products/tools/marketplace/guides/hashicorp-nomad-cluster/index.md @@ -7,7 +7,7 @@ keywords: ['HashiCorp','Nomad','Scheduling', 'orchestration'] tags: ["marketplace", "linode platform", "cloud manager"] --- -[HashiCorp Nomad](https://www.nomadproject.io/) is a workload scheduler and orchestrator that allows you to deploy and manage containerized or non-containerized, legacy applications using a single, unified workflow. Nomad uses bin packaging for efficient job scheduling and resource optimization, as well as enables developers to use declarative infrastructure-as-code for their deployments. +[HashiCorp Nomad](https://www.nomadproject.io/) is a workload scheduler and orchestrator that lets you deploy and manage containerized or non-containerized, legacy applications using a single, unified workflow. Nomad uses bin packaging for efficient job scheduling and resource optimization, as well as enables developers to use declarative infrastructure-as-code for their deployments. {{< note type="warning" title="Marketplace App Cluster Notice" >}} This Marketplace App deploys 6 Compute Instances to create a highly available, redundant Hashicorp Nomad Cluster. The plan type and size you select is applied to each individual instance. @@ -90,6 +90,6 @@ Please be aware that each Compute Instance will appear on your invoice as a sepa The HashiCorp Nomad Cluster provides default configurations to get you started. We recommend reviewing HashiCorp's [Configuration](https://www.nomadproject.io/docs/configuration) and [Job Spec](https://www.nomadproject.io/docs/job-specification) documentation to customize your Nomad Cluster for your specific workload. -If you find that you need additional Clients for your Nomad Cluster, the [Nomad Clients Cluster](/docs/products/tools/marketplace/guides/hashicorp-nomad-clients-cluster/) deployment allows you to scale horizontally by deploying 3, 5, or 7 additional Compute Instances as Clients. +If you find that you need additional Clients for your Nomad Cluster, the [Nomad Clients Cluster](/docs/products/tools/marketplace/guides/hashicorp-nomad-clients-cluster/) deployment lets you scale horizontally by deploying 3, 5, or 7 additional Compute Instances as Clients. {{% content "marketplace-update-note-shortguide" %}} diff --git a/docs/products/tools/marketplace/guides/illa-builder/index.md b/docs/products/tools/marketplace/guides/illa-builder/index.md index 17ac51895e8..58b499982e8 100644 --- a/docs/products/tools/marketplace/guides/illa-builder/index.md +++ b/docs/products/tools/marketplace/guides/illa-builder/index.md @@ -38,7 +38,7 @@ tags: ["marketplace", "linode platform", "cloud manager"] ![Screenshot of the ILLA Builder login](illa-builder-login-screen.png) -1. The sign up page should open, which allows you to create a new user on this ILLA Builder deployment. Enter your preferred username, your email address, and a secure password. Then, click the **Create Account** button. +1. The sign up page should open, which lets you create a new user on this ILLA Builder deployment. Enter your preferred username, your email address, and a secure password. Then, click the **Create Account** button. ![Screenshot of the ILLA Builder sign up page](illa-builder-signup-screen.png) diff --git a/docs/products/tools/marketplace/guides/jitsi-cluster/index.md b/docs/products/tools/marketplace/guides/jitsi-cluster/index.md index 7f8b0ee4897..171a062632e 100644 --- a/docs/products/tools/marketplace/guides/jitsi-cluster/index.md +++ b/docs/products/tools/marketplace/guides/jitsi-cluster/index.md @@ -14,7 +14,7 @@ external_resources: !["Jitsi Cluster Architecture"](jitsi-cluster.png "Jitsi Cluster Architecture") -[Jitsi](https://jitsi.org) is a suite of open source projects that allows you to host your own virtual video conferences. +[Jitsi](https://jitsi.org) is a suite of open source projects that lets you host your own virtual video conferences. ## Deploying a Marketplace App @@ -46,10 +46,10 @@ Jitsi is now installed and ready to use. 1. Before you go to your app, if you filled out the optional Jitsi configuration fields: - - In the Cloud Manager [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for your domain with two `A/AAAA` records pointing to your new server. One for the domain name and one for the hostname. + - In Cloud Manager's [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for your domain with two `A/AAAA` records pointing to your new server. One for the domain name and one for the hostname. - [Configure the rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) on your Linode. -1. If you didn't setup a domain, navigate to the rDNS address of the Linode in your browser. You can find the rDNS address in the **Networking** tab for your Linode in the [Cloud Manager](https://cloud.linode.com). If you did setup a domain, navigate to the address as described in the [Jitsi Options](#jitsi-options) section above. +1. If you didn't setup a domain, navigate to the rDNS address of the Linode in your browser. You can find the rDNS address in the **Networking** tab for your Linode in [Cloud Manager](https://cloud.linode.com). If you did setup a domain, navigate to the address as described in the [Jitsi Options](#jitsi-options) section above. 1. Jitsi prompts you to start a meeting. diff --git a/docs/products/tools/marketplace/guides/jitsi/index.md b/docs/products/tools/marketplace/guides/jitsi/index.md index 36207dacf6e..4ada6f03c7b 100644 --- a/docs/products/tools/marketplace/guides/jitsi/index.md +++ b/docs/products/tools/marketplace/guides/jitsi/index.md @@ -13,7 +13,7 @@ external_resources: aliases: ['/platform/marketplace/how-to-deploy-jitsi-with-marketplace-apps/', '/platform/one-click/how-to-deploy-jitsi-with-one-click-apps/','/platform/one-click/deploy-jitsi-with-one-click-apps/','/guides/how-to-deploy-jitsi-with-marketplace-apps/','/guides/jitsi-marketplace-app/'] --- !["Jitsi Start a Meeting"](Deploy_Jitsi_oneclickapps.png "Jitsi Start a Meeting") -[Jitsi](https://jitsi.org) is a suite of open source projects that allows you to host your own virtual video conferences. +[Jitsi](https://jitsi.org) is a suite of open source projects that lets you host your own virtual video conferences. ## Deploying a Marketplace App @@ -45,10 +45,10 @@ Jitsi is now installed and ready to use. 1. Before you go to your app, if you filled out the optional Jitsi configuration fields: - - In the Cloud Manager [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for your domain with two `A/AAAA` records pointing to your new server. One for the domain name and one for the hostname. + - In Cloud Manager's [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for your domain with two `A/AAAA` records pointing to your new server. One for the domain name and one for the hostname. - [Configure the rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) on your Linode. -1. If you didn't setup a domain, navigate to the rDNS address of the Linode in your browser. You can find the rDNS address in the **Networking** tab for your Linode in the [Cloud Manager](https://cloud.linode.com). If you did setup a domain, navigate to the address as described in the [Jitsi Options](#jitsi-options) section above. +1. If you didn't setup a domain, navigate to the rDNS address of the Linode in your browser. You can find the rDNS address in the **Networking** tab for your Linode in [Cloud Manager](https://cloud.linode.com). If you did setup a domain, navigate to the address as described in the [Jitsi Options](#jitsi-options) section above. 1. Jitsi prompts you to start a meeting. diff --git a/docs/products/tools/marketplace/guides/joomla/index.md b/docs/products/tools/marketplace/guides/joomla/index.md index 84542d53fe6..21ba22beea0 100644 --- a/docs/products/tools/marketplace/guides/joomla/index.md +++ b/docs/products/tools/marketplace/guides/joomla/index.md @@ -71,7 +71,7 @@ The first time you access your Joomla site, you are prompted to finish the Jooml ![Screenshot of a Joomla admin login form](joomla-admin-login.png) -1. After logging in, the admin dashboard appears. From here, you can manage your site. This includes creating content, new users, adjusting the templates, and *much* more. Check out [the official Joomla documentation](https://docs.joomla.org/Main_Page) to learn how to further utilize your Joomla instance. +1. After logging in, the admin dashboard appears. From here, you can manage your site. This includes creating content, new users, adjusting the templates, and *much* more. Check out [the official Joomla documentation](https://docs.joomla.org/Main_Page) to learn how to further use your Joomla instance. ![Screenshot of a Joomla admin dashboard](joomla-admin-panel.png) diff --git a/docs/products/tools/marketplace/guides/joplin/index.md b/docs/products/tools/marketplace/guides/joplin/index.md index 643e21f5b1d..70c6dc7a999 100644 --- a/docs/products/tools/marketplace/guides/joplin/index.md +++ b/docs/products/tools/marketplace/guides/joplin/index.md @@ -39,7 +39,7 @@ external_resources: ### Accessing the Joplin Server -The Joplin server dashboard allows you to manage your account, add other users, and perform various administration tasks. Before using your new Joplin instance to take notes, you should first log in to the admin dashboard and update your profile using the instructions below. +The Joplin server dashboard lets you manage your account, add other users, and perform various administration tasks. Before using your new Joplin instance to take notes, you should first log in to the admin dashboard and update your profile using the instructions below. 1. Open your web browser and navigate to the custom domain you entered during deployment or your Compute Instance's rDNS domain (such as `192-0-2-1.ip.linodeusercontent.com`). You can also use your IPv4 address, though your connection will not be encrypted. See the [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for information on viewing IP addresses and rDNS. @@ -83,6 +83,6 @@ To start using Joplin to take notes, download the Joplin application for your de 1. If your settings are correct, you should see a success message. Click the **Apply** button to save your settings. -Now you can start taking notes and your changes will automatically be stored on your new Joplin Server instance and synchronized between all of your devices. Check out [the official Joplin documentation](https://joplinapp.org/help/) to learn how to further utilize your Joplin instance. +Now you can start taking notes and your changes will automatically be stored on your new Joplin Server instance and synchronized between all of your devices. Check out [the official Joplin documentation](https://joplinapp.org/help/) to learn how to further use your Joplin instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/kali-linux/index.md b/docs/products/tools/marketplace/guides/kali-linux/index.md index 25e3552c353..9fe397c7f08 100644 --- a/docs/products/tools/marketplace/guides/kali-linux/index.md +++ b/docs/products/tools/marketplace/guides/kali-linux/index.md @@ -50,11 +50,11 @@ This Marketplace App extends Linode's Kali Linux distribution image by allowing ## Getting Started after Deployment -After Kali Linux has been fully deployed, you can log in through an SSH session as the `root` user and perform your workloads as needed. See the [Kali Linux documentation](https://www.kali.org/docs/) to learn how to further utilize your instance. +After Kali Linux has been fully deployed, you can log in through an SSH session as the `root` user and perform your workloads as needed. See the [Kali Linux documentation](https://www.kali.org/docs/) to learn how to further use your instance. ### Remote Desktop Connection with VNC -If you selected the VNC installation option, [TigerVNC](https://tigervnc.org/) is installed. This allows you to connect remotely to the desktop environment and access Kali's GUI tools. Perform the steps below to access your Kali Linux desktop through a VNC client. While there are many options for OS X and Windows, this guide will use [RealVNC Viewer](https://www.realvnc.com/en/connect/download/viewer/). +If you selected the VNC installation option, [TigerVNC](https://tigervnc.org/) is installed. This lets you connect remotely to the desktop environment and access Kali's GUI tools. Perform the steps below to access your Kali Linux desktop through a VNC client. While there are many options for OS X and Windows, this guide will use [RealVNC Viewer](https://www.realvnc.com/en/connect/download/viewer/). 1. From your desktop, create an SSH tunnel to your Compute Instance with the following command. Be sure to replace *[username]* with the VNC username you created and *[ip]* with the IPv4 address of your Compute Instance. See the [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for information on viewing IP addresses. diff --git a/docs/products/tools/marketplace/guides/kepler/index.md b/docs/products/tools/marketplace/guides/kepler/index.md index ed457052034..10699ec8752 100644 --- a/docs/products/tools/marketplace/guides/kepler/index.md +++ b/docs/products/tools/marketplace/guides/kepler/index.md @@ -67,7 +67,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from 1. Log in to your new Compute Instance using one of the methods below: - - **Lish Console:** Within the Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). + - **Lish Console:** Within Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). - **SSH:** Log in to your Compute Instance over SSH using the `root` user. See [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/) for assistance. 1. Once logged in, access the credentials file by running the following command: diff --git a/docs/products/tools/marketplace/guides/lamp-stack/index.md b/docs/products/tools/marketplace/guides/lamp-stack/index.md index 2e8cd4c5bbc..7b452bfbc0a 100644 --- a/docs/products/tools/marketplace/guides/lamp-stack/index.md +++ b/docs/products/tools/marketplace/guides/lamp-stack/index.md @@ -57,7 +57,7 @@ After your LAMP stack has finished deploying, you can: - Upload files to your web root directory with an SFTP application like [FileZilla](/docs/guides/filezilla/). Use the same root credentials that you would use for SSH. -- Assign a domain name to your Linode's IP address. Review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in the Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. +- Assign a domain name to your Linode's IP address. Review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. ## Software Included diff --git a/docs/products/tools/marketplace/guides/litespeed-cpanel/index.md b/docs/products/tools/marketplace/guides/litespeed-cpanel/index.md index af89e334200..aefa9ba2120 100644 --- a/docs/products/tools/marketplace/guides/litespeed-cpanel/index.md +++ b/docs/products/tools/marketplace/guides/litespeed-cpanel/index.md @@ -97,7 +97,7 @@ Please make sure to save this password. ![cPanel home page](cpanel-home-page.png) -Now that you’ve accessed your LiteSpeed instance, check out [the official LiteSpeed documentation](https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki) to learn how to further utilize your LiteSpeed instance. +Now that you’ve accessed your LiteSpeed instance, check out [the official LiteSpeed documentation](https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki) to learn how to further use your LiteSpeed instance. ### Accessing the LiteSpeed WebAdmin Interface diff --git a/docs/products/tools/marketplace/guides/liveswitch/index.md b/docs/products/tools/marketplace/guides/liveswitch/index.md index a90635755cb..295c3acc66b 100644 --- a/docs/products/tools/marketplace/guides/liveswitch/index.md +++ b/docs/products/tools/marketplace/guides/liveswitch/index.md @@ -46,6 +46,6 @@ After deployment, follow the instructions below to access your application. 1. After completing the setup wizard, you should see the main Configuration Console for your installation. To learn more about how to manage your instance, see the [Configuration Console documentation](https://developer.liveswitch.io/liveswitch-server/server/configuration/configuration-console.html). -Now that you’ve accessed your LiveSwitch instance, check out [the official LiveSwitch quick start documentation](https://developer.liveswitch.io/liveswitch-server/get-started/js-server/quickstart-js.html) to learn how to further utilize your LiveSwitch instance. +Now that you’ve accessed your LiveSwitch instance, check out [the official LiveSwitch quick start documentation](https://developer.liveswitch.io/liveswitch-server/get-started/js-server/quickstart-js.html) to learn how to further use your LiveSwitch instance. {{% content "marketplace-update-note-shortguide" %}} diff --git a/docs/products/tools/marketplace/guides/mainconcept-live-encoder-demo/index.md b/docs/products/tools/marketplace/guides/mainconcept-live-encoder-demo/index.md index da015761a45..64351434417 100644 --- a/docs/products/tools/marketplace/guides/mainconcept-live-encoder-demo/index.md +++ b/docs/products/tools/marketplace/guides/mainconcept-live-encoder-demo/index.md @@ -6,7 +6,7 @@ keywords: ['encoder','video','live','rtmp','rtsp','rtp','udp','zixi','srt','mpeg tags: ["marketplace", "linode platform", "cloud manager"] --- -The [MainConcept Live Encoder](https://www.mainconcept.com/live-encoder) is an all-in-one encoding engine designed to simplify common broadcast and OTT video workflows. It features HEVC and AVC codecs with optional GPU decoding, as well as encoding powered by NVIDIA and Intel Quick Sync Video built in. MainConcept Live Encoder allows you to package content for multi-screen delivery in real-time using common input sources via a graphic user interface or REST API. +The [MainConcept Live Encoder](https://www.mainconcept.com/live-encoder) is an all-in-one encoding engine designed to simplify common broadcast and OTT video workflows. It features HEVC and AVC codecs with optional GPU decoding, as well as encoding powered by NVIDIA and Intel Quick Sync Video built in. MainConcept Live Encoder lets you package content for multi-screen delivery in real-time using common input sources via a graphic user interface or REST API. Using the Live Encoder, you are able to set up a live workflow to ingest, prepare, and stream audio-visual content that is compatible with all consumer devices. Video delivery options include, but are not limited to: direct to CDN, online video via RTMP, or low-latency protocols like Zixi and SRT. diff --git a/docs/products/tools/marketplace/guides/mastodon/index.md b/docs/products/tools/marketplace/guides/mastodon/index.md index f76632c0706..34c8a972c46 100644 --- a/docs/products/tools/marketplace/guides/mastodon/index.md +++ b/docs/products/tools/marketplace/guides/mastodon/index.md @@ -87,7 +87,7 @@ Open a web browser and navigate to the custom domain you entered when deploying ![Screenshot of the Mastodon user home page](mastodon-user-home.png) -1. **Access admin settings**. Navigate to `https://[domain.tld]/admin/settings/` to view your site's administration settings. The administration page allows you to alter the look, feel, and behavior of your site. Consider configuring each of these settings, including the site name, contact username, contact email, server description, and fields within other tabs. +1. **Access admin settings**. Navigate to `https://[domain.tld]/admin/settings/` to view your site's administration settings. The administration page lets you alter the look, feel, and behavior of your site. Consider configuring each of these settings, including the site name, contact username, contact email, server description, and fields within other tabs. ![Screenshot of Mastodon admin page](mastodon-server-settings.png) diff --git a/docs/products/tools/marketplace/guides/mysql/index.md b/docs/products/tools/marketplace/guides/mysql/index.md index 8269a8e8621..524b1f958bb 100644 --- a/docs/products/tools/marketplace/guides/mysql/index.md +++ b/docs/products/tools/marketplace/guides/mysql/index.md @@ -91,7 +91,7 @@ The standard tool for interacting with MySQL is the `mysql` client which install prompt (\R) Change your mysql prompt. quit (\q) Quit mysql. rehash (\#) Rebuild completion hash. - source (\.) Execute an SQL script file. Takes a file name as an argument. + source (\.) Execute an SQL script file. Takes a filename as an argument. status (\s) Get status information from the server. system (\!) Execute a system shell command. tee (\T) Set outfile [to_outfile]. Append everything into given outfile. diff --git a/docs/products/tools/marketplace/guides/odoo/index.md b/docs/products/tools/marketplace/guides/odoo/index.md index da3c3f345ed..a48094cb5f6 100644 --- a/docs/products/tools/marketplace/guides/odoo/index.md +++ b/docs/products/tools/marketplace/guides/odoo/index.md @@ -47,6 +47,6 @@ aliases: ['/guides/odoo-marketplace-app/'] ![Screenshot of the Odoo setup page](odoosetuppage.png) -Now that you’ve accessed your dashboard, check out [the official Odoo documentation](https://www.odoo.com/page/docs) to learn how to further utilize your Odoo instance. +Now that you’ve accessed your dashboard, check out [the official Odoo documentation](https://www.odoo.com/page/docs) to learn how to further use your Odoo instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/openlitespeed-django/index.md b/docs/products/tools/marketplace/guides/openlitespeed-django/index.md index e002c2597a7..a5a35ad4271 100644 --- a/docs/products/tools/marketplace/guides/openlitespeed-django/index.md +++ b/docs/products/tools/marketplace/guides/openlitespeed-django/index.md @@ -62,7 +62,7 @@ The OpenLiteSpeed Django app automatically installs Linux, the performance web s 1. The Django page is automatically configured with the custom domain provided during deployment, or the default rDNS. {{< note >}} - For more documentation on how to assign a domain to your Linode, please review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in the Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. + For more documentation on how to assign a domain to your Linode, please review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. {{< /note >}} Now that you’ve accessed your OpenLiteSpeed Django instance, check out [the official OpenLiteSpeed Django documentation](https://docs.litespeedtech.com/cloud/images/django/) for further configuration steps. diff --git a/docs/products/tools/marketplace/guides/openlitespeed-nodejs/index.md b/docs/products/tools/marketplace/guides/openlitespeed-nodejs/index.md index e67111b1d59..529030be1df 100644 --- a/docs/products/tools/marketplace/guides/openlitespeed-nodejs/index.md +++ b/docs/products/tools/marketplace/guides/openlitespeed-nodejs/index.md @@ -39,7 +39,7 @@ The OpenLiteSpeed Node.js One-Click app automatically installs the performance w 1. You are then prompted to enter the domain you'd like to use for this instance. You can optionally use a custom domain provided you've already configured the *A Records* to point to this server's IPv4 and IPv6 addresses. Otherwise, you can skip this by pressing *CTRL+C* which will use the IP address or default RDNS of the Compute Instance. {{< note >}} - For more documentation on how to assign a domain to your Linode, please review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in the Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. + For more documentation on how to assign a domain to your Linode, please review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. {{< /note >}} Now that you’ve accessed your OpenLiteSpeed Node.js instance, check out [the official OpenLiteSpeed Node.js documentation](https://docs.litespeedtech.com/cloud/images/nodejs/) to learn how to further configure your OpenLiteSpeed Node.js instance. diff --git a/docs/products/tools/marketplace/guides/openlitespeed-rails/index.md b/docs/products/tools/marketplace/guides/openlitespeed-rails/index.md index 750a8b20d62..8e41b6e131e 100644 --- a/docs/products/tools/marketplace/guides/openlitespeed-rails/index.md +++ b/docs/products/tools/marketplace/guides/openlitespeed-rails/index.md @@ -39,7 +39,7 @@ The OpenLiteSpeed Rails app automatically installs the performance web server Op 1. You are then prompted to enter the domain you'd like to use for this instance. You can optionally use a custom domain provided you've already configured the *A Records* to point to this server's IPv4 and IPv6 addresses. Otherwise, you can skip this by pressing *CTRL+C* which will use the IP address or default RDNS of the Compute Instance. {{< note >}} - For more documentation on how to assign a domain to your Linode, please review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in the Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. + For more documentation on how to assign a domain to your Linode, please review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in Cloud Manager, and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. {{< /note >}} Now that you’ve accessed your OpenLiteSpeed Rails instance, check out [the official OpenLiteSpeed Rails documentation](https://docs.litespeedtech.com/cloud/images/rails/) to learn how to further configure your OpenLiteSpeed Rails instance. diff --git a/docs/products/tools/marketplace/guides/owncloud/index.md b/docs/products/tools/marketplace/guides/owncloud/index.md index 3ebfd6efcea..8d63e56a181 100644 --- a/docs/products/tools/marketplace/guides/owncloud/index.md +++ b/docs/products/tools/marketplace/guides/owncloud/index.md @@ -69,6 +69,6 @@ After deployment, follow the instructions below to access your application. ![ownCloud Files Screen](owncloud-main-screen.png) -Now that you’ve accessed your ownCloud instance, check out [the official ownCloud documentation](https://doc.owncloud.com/server) to learn how to further utilize your ownCloud instance. +Now that you’ve accessed your ownCloud instance, check out [the official ownCloud documentation](https://doc.owncloud.com/server) to learn how to further use your ownCloud instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/pihole/index.md b/docs/products/tools/marketplace/guides/pihole/index.md index 9ab7cc06212..2cb28e752d5 100644 --- a/docs/products/tools/marketplace/guides/pihole/index.md +++ b/docs/products/tools/marketplace/guides/pihole/index.md @@ -50,6 +50,6 @@ aliases: ['/guides/deploying-pihole-marketplace-app/','/guides/pihole-marketplac 1. To log yourself in and access most of Pi-hole's features, click the **Login** link on the left menu. Enter the Pi-hole user password that you created when deploying the Compute Instance. -Now that you’ve accessed your dashboard, check out [the official Pi-hole documentation](https://docs.pi-hole.net/) to learn how to further utilize your Pi-hole instance. +Now that you’ve accessed your dashboard, check out [the official Pi-hole documentation](https://docs.pi-hole.net/) to learn how to further use your Pi-hole instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/plex/index.md b/docs/products/tools/marketplace/guides/plex/index.md index cd65aa80829..5a885d4d718 100644 --- a/docs/products/tools/marketplace/guides/plex/index.md +++ b/docs/products/tools/marketplace/guides/plex/index.md @@ -11,7 +11,7 @@ external_resources: aliases: ['/platform/marketplace/deploy-plex-with-marketplace-apps/', '/platform/marketplace/deploy-plex-with-one-click-apps/', '/guides/deploy-plex-with-one-click-apps/', '/guides/deploy-plex-with-marketplace-apps/','/platform/one-click/deploy-plex-with-one-click-apps/','/guides/plex-marketplace-app/'] --- -[Plex](https://www.plex.tv/) is a feature-rich streaming platform that allows you to organize and stream your own digital video and audio to your devices. This guide shows you how to deploy the [**Plex Media Server**](https://hub.docker.com/r/plexinc/pms-docker/) using Linode's Plex Marketplace App, upload media to your Plex Server, and connect to it from a Plex client application. Your Plex Media Server could benefit from large amounts of disk space, so consider using our [Block Storage](/docs/products/storage/block-storage/) service with this app. +[Plex](https://www.plex.tv/) is a feature-rich streaming platform that lets you organize and stream your own digital video and audio to your devices. This guide shows you how to deploy the [**Plex Media Server**](https://hub.docker.com/r/plexinc/pms-docker/) using Linode's Plex Marketplace App, upload media to your Plex Server, and connect to it from a Plex client application. Your Plex Media Server could benefit from large amounts of disk space, so consider using our [Block Storage](/docs/products/storage/block-storage/) service with this app. ## Why Use Plex Media Server @@ -131,7 +131,7 @@ For future reference, you can find examples of the instructions provided in this mkdir ~/plex/media/linode-volume -1. Mount your Volume path to the mountpoint you have created, substituting `$FILE_SYSTEM_PATH` with your Volume's file system path (which is viewable from the Cloud Manager [**Volumes**](https://cloud.linode.com/volumes) dashboard): +1. Mount your Volume path to the mountpoint you have created, substituting `$FILE_SYSTEM_PATH` with your Volume's file system path (which is viewable from Cloud Manager's [**Volumes**](https://cloud.linode.com/volumes) dashboard): sudo mount $FILE_SYSTEM_PATH ~/plex/media/linode-volume diff --git a/docs/products/tools/marketplace/guides/pritunl/index.md b/docs/products/tools/marketplace/guides/pritunl/index.md index 6fb1d1afe99..bb9c9d879db 100644 --- a/docs/products/tools/marketplace/guides/pritunl/index.md +++ b/docs/products/tools/marketplace/guides/pritunl/index.md @@ -69,6 +69,6 @@ Pritunl is an open source VPN server and management panel. It gives the user the ![Pritunl Domain Setup](pritunl-config3.png) -Now that you’ve accessed your dashboard, check out [the official Pritunl documentation](https://docs.pritunl.com/docs/connecting) to learn how to add users and further utilize your Pritunl instance. +Now that you’ve accessed your dashboard, check out [the official Pritunl documentation](https://docs.pritunl.com/docs/connecting) to learn how to add users and further use your Pritunl instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/prometheus-grafana/index.md b/docs/products/tools/marketplace/guides/prometheus-grafana/index.md index aa576d50d74..700bac9f352 100644 --- a/docs/products/tools/marketplace/guides/prometheus-grafana/index.md +++ b/docs/products/tools/marketplace/guides/prometheus-grafana/index.md @@ -54,7 +54,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from 1. Log in to your new Compute Instance using one of the methods below: - - **Lish Console:** Within the Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). + - **Lish Console:** Within Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). - **SSH:** Log in to your Compute Instance over SSH using the `root` user, or with the sudo user created during deployment. See [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/) for assistance. 1. Once logged in, find the URLs and credential files listed in the MOTD: @@ -92,7 +92,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from ### Add Prometheus as a Data Source to Grafana -1. Log in to the Grafana frontend. See [Access Grafana and Prometheus](#access-grafana-and-prometheus). +1. Log in to the Grafana front end. See [Access Grafana and Prometheus](#access-grafana-and-prometheus). 1. On the main menu, hover over the gear icon to open the *Configuration* menu. Then click **Data Sources**. @@ -108,6 +108,6 @@ Once the app has been *fully* deployed, you need to obtain the credentials from ![Screenshot of the Prometheus data source](grafana-prometheus-source.png) -Now that the Prometheus Data Source is set, you can browse the [available Grafana dashboards](https://grafana.com/grafana/dashboards/) to see which dashboard fits your needs. Review the official [Prometheus](https://prometheus.io/docs/introduction/overview/) and [Grafana](https://grafana.com/docs/grafana/latest/) documentation to learn how to further utilize your instance. +Now that the Prometheus Data Source is set, you can browse the [available Grafana dashboards](https://grafana.com/grafana/dashboards/) to see which dashboard fits your needs. Review the official [Prometheus](https://prometheus.io/docs/introduction/overview/) and [Grafana](https://grafana.com/docs/grafana/latest/) documentation to learn how to further use your instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/restyaboard/index.md b/docs/products/tools/marketplace/guides/restyaboard/index.md index 13be7e3db58..bf96bd42099 100644 --- a/docs/products/tools/marketplace/guides/restyaboard/index.md +++ b/docs/products/tools/marketplace/guides/restyaboard/index.md @@ -39,6 +39,6 @@ Restyaboard is like an electronic sticky note for organizing tasks and to-dos. I 1. You can reset the default admin password by visiting admin panel at the bottom right of the Restyaboard panel. You can also visit the users page direct at `http://192.0.2.0/#/users`, replacing `192.0.2.0` with your instance's IP address. -Now that you’ve accessed your dashboard, check out [the official Restyaboard documentation](https://restya.com/board/docs/install-restyaboard-linode-marketplace-tutorial/) to learn how to add users and further utilize your Restyaboard instance. +Now that you’ve accessed your dashboard, check out [the official Restyaboard documentation](https://restya.com/board/docs/install-restyaboard-linode-marketplace-tutorial/) to learn how to add users and further use your Restyaboard instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/rocketchat/index.md b/docs/products/tools/marketplace/guides/rocketchat/index.md index c09c155cd28..dd8c3ec8582 100644 --- a/docs/products/tools/marketplace/guides/rocketchat/index.md +++ b/docs/products/tools/marketplace/guides/rocketchat/index.md @@ -10,7 +10,7 @@ external_resources: aliases: ['/guides/deploying-rocketchat-marketplace-app/','/guides/rocketchat-marketplace-app/'] --- -Rocket.Chat is a self-hosted open source chat application that can be used as an alternative to Slack. Rocket.Chat has many key features that you or your business can utilize to improve productivity in the workplace such as video conferencing, group chats, and platform integrations with some of the most popular applications. +Rocket.Chat is a self-hosted open source chat application that can be used as an alternative to Slack. Rocket.Chat has many key features that you or your business can use to improve productivity in the workplace such as video conferencing, group chats, and platform integrations with some of the most popular applications. ## Deploying a Marketplace App @@ -49,6 +49,6 @@ Rocket.Chat is a self-hosted open source chat application that can be used as an ![Rocket.Chat Step 3](rocketchat-setup3.png) ![Rocket.Chat Step 4](rocketchat-setup4.png) -Now that you’ve gone through the setup and accessed your Rocket.Chat instance, check out [the official Rocket.Chat documentation](https://docs.rocket.chat/guides/user-guides) to learn how to further utilize your Rocket.Chat instance. +Now that you’ve gone through the setup and accessed your Rocket.Chat instance, check out [the official Rocket.Chat documentation](https://docs.rocket.chat/guides/user-guides) to learn how to further use your Rocket.Chat instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/rust/index.md b/docs/products/tools/marketplace/guides/rust/index.md index 3ea01518de7..06e128ea6f0 100644 --- a/docs/products/tools/marketplace/guides/rust/index.md +++ b/docs/products/tools/marketplace/guides/rust/index.md @@ -20,7 +20,7 @@ Rust has been removed from the App Marketplace and can no longer be deployed. Th [Rust](https://rust.facepunch.com/) is a multiplayer game where you play as a survivor that must work with or against other players to ensure your own survival. Players are able to steal, lie, cheat, or trick each other. You can build a shelter, hunt animals for food, craft weapons, craft armor, and much more. -Hosting your own Rust server allows you to customize settings and curate the number of players in the world. +Hosting your own Rust server lets you customize settings and curate the number of players in the world. ## Deploying a Marketplace App @@ -39,7 +39,7 @@ Hosting your own Rust server allows you to customize settings and curate the num ### Rust Options -- **RCON Password** *(required)*: The password for your remote console, which allows you to issue commands on the Rust server +- **RCON Password** *(required)*: The password for your remote console, which lets you issue commands on the Rust server - **Server Hostname:** The name of your Rust server. - **Server Description:** Your server's description. Use `\n` to create a new line. - **Maximum Players:** The maximum number of players allowed on a server at one time. Default is 50, minimum is 10, maximum is 100. diff --git a/docs/products/tools/marketplace/guides/saltcorn/index.md b/docs/products/tools/marketplace/guides/saltcorn/index.md index 80f2b324953..1772606be93 100644 --- a/docs/products/tools/marketplace/guides/saltcorn/index.md +++ b/docs/products/tools/marketplace/guides/saltcorn/index.md @@ -53,6 +53,6 @@ aliases: ['/guides/saltcorn-marketplace-app/'] ![The Saltcorn admin dashboard](saltcorn-admin.png) -Now that you’ve accessed your dashboard, check out [the official Saltcorn documentation](https://wiki.saltcorn.com/) to learn how to further utilize your Saltcorn instance. +Now that you’ve accessed your dashboard, check out [the official Saltcorn documentation](https://wiki.saltcorn.com/) to learn how to further use your Saltcorn instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/shadowsocks/index.md b/docs/products/tools/marketplace/guides/shadowsocks/index.md index 02490b5b88f..e166db3f8dd 100644 --- a/docs/products/tools/marketplace/guides/shadowsocks/index.md +++ b/docs/products/tools/marketplace/guides/shadowsocks/index.md @@ -13,7 +13,7 @@ image: 'How_to_Deploy_a_Shadowsocks_Server_with_OneClick_Apps_1200x631.png' aliases: ['/platform/marketplace/deploy-shadowsocks-with-marketplace-apps/', '/platform/one-click/deploy-shadowsocks-with-one-click-apps/','/guides/deploy-shadowsocks-with-one-click-apps/','/guides/deploy-shadowsocks-with-marketplace-apps/','/guides/shadowsocks-marketplace-app/'] --- -Shadowsocks is a lightweight SOCKS5 web proxy tool primarily utilized to bypass network censorship and blocking on certain websites and web protocols. A full setup requires a Linode server to host the Shadowsocks daemon, and a client installed on PC, Mac, Linux, or a mobile device. Unlike other proxy software, Shadowsocks traffic is designed to be both indiscernible from other traffic to third-party monitoring tools, and also able to disguise itself as a normal direct connection. Data passing through Shadowsocks is encrypted for additional security and privacy. +Shadowsocks is a lightweight SOCKS5 web proxy tool primarily used to bypass network censorship and blocking on certain websites and web protocols. A full setup requires a Linode server to host the Shadowsocks daemon, and a client installed on PC, Mac, Linux, or a mobile device. Unlike other proxy software, Shadowsocks traffic is designed to be both indiscernible from other traffic to third-party monitoring tools, and also able to disguise itself as a normal direct connection. Data passing through Shadowsocks is encrypted for additional security and privacy. ## Deploying a Marketplace App @@ -46,7 +46,7 @@ When the client has completed the installation process, ensure that you're setti | **Configuration** | **Description** | |-------------------|-----------------| -| **Address** | Your linodes IPv4 address. Can be found in the `Linodes` section of the [Cloud Manager](https://cloud.linode.com/linodes). +| **Address** | Your linodes IPv4 address. Can be found in the `Linodes` section of [Cloud Manager](https://cloud.linode.com/linodes). | **Port** | The Shadowsocks Marketplace App connects through port `8000` by default. | | **Encryption** | Set to use the `aes-256-gcm` encryption mode. | | **Password** | This is the `Shadowsocks Password` field you created when initially deploying your app. | diff --git a/docs/products/tools/marketplace/guides/team-fortress-2/index.md b/docs/products/tools/marketplace/guides/team-fortress-2/index.md index 12c9e06ee5b..ae9a28351ab 100644 --- a/docs/products/tools/marketplace/guides/team-fortress-2/index.md +++ b/docs/products/tools/marketplace/guides/team-fortress-2/index.md @@ -37,7 +37,7 @@ Setting up a personal game server puts you in control of the game modes and maps ### Team Fortress 2 Options -- **RCON Password** *(required)*: The password for the remote console, which allows you to issue commands on the TF2 server. +- **RCON Password** *(required)*: The password for the remote console, which lets you issue commands on the TF2 server. - **Server Name:** Your Team Fortress 2 server's name. - **Message of the Day:** Message of the day. Text displayed whenever a player logs on to the server. - **Server Password:** The password for the TF2 server. Configuring a TF2 server password will require users of your game server to provide this password. diff --git a/docs/products/tools/marketplace/guides/uptime-kuma/index.md b/docs/products/tools/marketplace/guides/uptime-kuma/index.md index 57aedf45d30..7d67d78bb51 100644 --- a/docs/products/tools/marketplace/guides/uptime-kuma/index.md +++ b/docs/products/tools/marketplace/guides/uptime-kuma/index.md @@ -53,6 +53,6 @@ aliases: ['/guides/uptimekuma-marketplace-app/'] ![Screenshot of Uptime Kuma dashboard](uptimekuma-dashboard.png) -Now that you’ve accessed your dashboard, check out [the official Uptime Kuma Repository](https://github.com/louislam/uptime-kuma) to learn how to further utilize your Uptime Kuma instance. +Now that you’ve accessed your dashboard, check out [the official Uptime Kuma Repository](https://github.com/louislam/uptime-kuma) to learn how to further use your Uptime Kuma instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/utunnel/index.md b/docs/products/tools/marketplace/guides/utunnel/index.md index be02d9b662b..f5a9ed34fff 100644 --- a/docs/products/tools/marketplace/guides/utunnel/index.md +++ b/docs/products/tools/marketplace/guides/utunnel/index.md @@ -83,6 +83,6 @@ In order to use UTunnel VPN, you need to create an account on [UTunnel.io](https sudo /utunnel/bin/utnservice start -Now that you’ve deployed your UTunnel VPN instance, checkout [the official UTunnel VPN documentation](https://help.utunnel.io/About-UTunnel-VPN) to learn how to further utilize your UTunnel instance. +Now that you’ve deployed your UTunnel VPN instance, checkout [the official UTunnel VPN documentation](https://help.utunnel.io/About-UTunnel-VPN) to learn how to further use your UTunnel instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/victoriametrics-single/index.md b/docs/products/tools/marketplace/guides/victoriametrics-single/index.md index 4dd7f8a891f..dd5c8523c57 100644 --- a/docs/products/tools/marketplace/guides/victoriametrics-single/index.md +++ b/docs/products/tools/marketplace/guides/victoriametrics-single/index.md @@ -58,7 +58,7 @@ See more details and examples in [official documentation](https://docs.victoriam ### Accessing the Query Interface -VictoriaMetrics provides a user interface, called [vmui](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html#vmui) for query troubleshooting and exploration. This allows you to explore query results through graphs and tables. +VictoriaMetrics provides a user interface, called [vmui](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html#vmui) for query troubleshooting and exploration. This lets you explore query results through graphs and tables. To access vmui, open the following URL in your browser, replacing *ip-address* with the IPv4 address of your new Compute Instance: diff --git a/docs/products/tools/marketplace/guides/virtualmin/index.md b/docs/products/tools/marketplace/guides/virtualmin/index.md index 79ae9f75044..0c2e7f79985 100644 --- a/docs/products/tools/marketplace/guides/virtualmin/index.md +++ b/docs/products/tools/marketplace/guides/virtualmin/index.md @@ -60,7 +60,7 @@ Virtualmin is now installed and ready to use. 1. Before you go to our app, if you filled out the optional Virtualmin configuration fields: - - In the Cloud Manager [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for your domain with possible subdomain, MX, and SPF records pointing to your new server. + - In Cloud Manager's [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for your domain with possible subdomain, MX, and SPF records pointing to your new server. - [Configure the rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) on your Linode. 1. Virtualmin is served on port 10000, to access it, navigate to either the IP address of your server or to your domain name followed by port 10000. For example, `http://example.com:10000` or `http://203.0.113.0:10000`, replacing the domain name or IP address with values for your server. diff --git a/docs/products/tools/marketplace/guides/vscode/index.md b/docs/products/tools/marketplace/guides/vscode/index.md index 43140ef4cc2..07c7da098d4 100644 --- a/docs/products/tools/marketplace/guides/vscode/index.md +++ b/docs/products/tools/marketplace/guides/vscode/index.md @@ -47,7 +47,7 @@ VS Code is now installed and ready to use. 1. Before you go to the app, if you filled out the optional VS Code configuration fields for domain: - - In the Cloud Manager [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for the domain with possible subdomain records pointing to the new server. + - In Cloud Manager's [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/) there is now an entry for the domain with possible subdomain records pointing to the new server. - [Configure the rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) on the Linode server. 1. VS Code is accessed via the domain name if you entered one, or by the rDNS name if you did not. For example, `http://example.com` or `http://203-0-113-0.ip.linodeusercontent.com`, replacing the domain name or rDNS name with values for the server. @@ -68,6 +68,6 @@ The VS Code Marketplace App installs the following software on the Linode: |:--------------|:------------| | [**Code Server**](https://github.com/cdr/code-server) | Code Server which hosts the open source web interface of VS Code.| | [**NGINX**](https://www.nginx.com) | An open source web server. | -| [**ufw**](https://wiki.ubuntu.com/UncomplicatedFirewall) | ufw is the uncomplicated firewall, a frontend for iptables. | +| [**ufw**](https://wiki.ubuntu.com/UncomplicatedFirewall) | ufw is the uncomplicated firewall, a front end for iptables. | {{% content "marketplace-update-note-shortguide" %}} diff --git a/docs/products/tools/marketplace/guides/warpspeed/index.md b/docs/products/tools/marketplace/guides/warpspeed/index.md index 69cdc92af5e..9ee8ce19f8c 100644 --- a/docs/products/tools/marketplace/guides/warpspeed/index.md +++ b/docs/products/tools/marketplace/guides/warpspeed/index.md @@ -41,7 +41,7 @@ WarpSpeed makes it easy for developers to access cloud infrastructure via the po ### Accessing the WarpSpeed VPN App -1. Configure your custom domain to point towards the IPv4 (and IPv6) address of the newly created Compute Instance. Review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in the Cloud Manager and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. +1. Configure your custom domain to point towards the IPv4 (and IPv6) address of the newly created Compute Instance. Review the [DNS Manager](/docs/products/networking/dns-manager/) guide for instructions on setting up your DNS records in Cloud Manager and read through [DNS Records: An Introduction](/docs/guides/dns-overview/) for general information about how DNS works. 1. Once your domain has been configured and has finished propagating, enter the domain within a web browser to access the login page. diff --git a/docs/products/tools/marketplace/guides/wazuh/index.md b/docs/products/tools/marketplace/guides/wazuh/index.md index 324b7079487..750c36d218b 100644 --- a/docs/products/tools/marketplace/guides/wazuh/index.md +++ b/docs/products/tools/marketplace/guides/wazuh/index.md @@ -121,6 +121,6 @@ sudo systemctl enable wazuh-agent sudo systemctl start wazuh-agent ``` -For more documentation on Wazuh, check out [the official Wazuh documentation](https://documentation.wazuh.com/current/installation-guide/index.html) to learn how to further utilize your instance. +For more documentation on Wazuh, check out [the official Wazuh documentation](https://documentation.wazuh.com/current/installation-guide/index.html) to learn how to further use your instance. {{% content "marketplace-update-note-shortguide" %}} \ No newline at end of file diff --git a/docs/products/tools/marketplace/guides/webmin/index.md b/docs/products/tools/marketplace/guides/webmin/index.md index 107d22a7e92..4f92d526884 100644 --- a/docs/products/tools/marketplace/guides/webmin/index.md +++ b/docs/products/tools/marketplace/guides/webmin/index.md @@ -21,7 +21,7 @@ deprecated: true Webmin has been removed from the App Marketplace and can no longer be deployed. This guide has been retained for reference only. {{< /note >}} -[Webmin](http://www.webmin.com) is an open source interface for Unix system administration that offers an easy to use graphical interface for managing user accounts, DNS, file sharing, and more. Webmin alleviates the need to use the command line to edit Unix system configuration files and allows you to configure your system easily from a simple web interface. +[Webmin](http://www.webmin.com) is an open source interface for Unix system administration that offers an easy to use graphical interface for managing user accounts, DNS, file sharing, and more. Webmin alleviates the need to use the command line to edit Unix system configuration files and lets you configure your system easily from a simple web interface. ## Deploying a Marketplace App @@ -61,7 +61,7 @@ Webmin is now installed and ready to use. 1. If you filled out the optional Webmin configuration fields: - - In the Cloud Manager [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/), confirm that there is now an entry for your domain with possible subdomain, MX, and SPF records pointing to your new server. + - In Cloud Manager's [DNS Manager](/docs/products/networking/dns-manager/guides/create-domain/), confirm that there is now an entry for your domain with possible subdomain, MX, and SPF records pointing to your new server. - [Configure rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) on your Linode to point to your new domain name. 1. Webmin is served on port 10000. To access Webmin, navigate to either the IP address of your server, or to your domain name followed by port 10000. For example, entering `http://example.com:10000` or `http://203.0.113.0:10000` while replacing the domain name or IP address with values for your server will allow you to reach the Webmin login screen. diff --git a/docs/products/tools/marketplace/guides/webuzo/index.md b/docs/products/tools/marketplace/guides/webuzo/index.md index 93f1bd92f96..2ab0b4d2d61 100644 --- a/docs/products/tools/marketplace/guides/webuzo/index.md +++ b/docs/products/tools/marketplace/guides/webuzo/index.md @@ -1,6 +1,6 @@ --- title: "Deploy Webuzo through the Linode Marketplace" -description: "This guide shows you how to deploy Webuzo from Softaculous, a LAMP stack control panel that allows you to deploy a growing number of applications and scripts." +description: "This guide shows you how to deploy Webuzo from Softaculous, a LAMP stack control panel that lets you deploy a growing number of applications and scripts." published: 2020-12-02 modified: 2022-08-08 keywords: ['webuzo','control panel','dashboard','marketplace'] @@ -11,7 +11,7 @@ external_resources: aliases: ['/platform/marketplace/how-to-deploy-webuzo-with-marketplace-apps/', '/platform/one-click/how-to-deploy-webuzo-with-one-click-apps/','/guides/how-to-deploy-webuzo-with-one-click-apps/','/guides/deploy-webuzo-with-marketplace-apps/','/guides/webuzo-marketplace-app/'] --- -Softaculous [Webuzo](https://www.webuzo.com) is a single user LAMP stack control panel that allows you to deploy a growing number of applications and scripts on your server with a single click. +Softaculous [Webuzo](https://www.webuzo.com) is a single user LAMP stack control panel that lets you deploy a growing number of applications and scripts on your server with a single click. ## Deploying a Marketplace App @@ -56,7 +56,7 @@ After the deployment process has finished and your Compute Instance has rebooted To set your hostname and name servers, navigate to **Settings** > **Panel Config** and make any needed adjustments to the *Hostname (Panel domain)* and nameserver (*NS1* and *NS2*) fields. If you registered the domain name *example.com*, you may want to configure your *Hostname* as `server.example.com` and your name servers as `ns1.example.com` and `ns2.example.com`. Before doing so, you need log in to your DNS provider and add an A record from `server.example.com` to the IPv4 address of your Compute Instance. You also need to register the name servers through your domain's registrar. For further instructions, consult your domain registrar's documentation. -1. **Create a user.** Webuzo allows you to have multiple users, each with their own website(s), resource allowances, and dedicated backend panels. To create your first user, navigate to **Users** > **Add User**. In the **Add user** page that appears, fill out the desired username, password, domain, and email address for the new user. You can also set custom resource allotments and additional settings as needed. +1. **Create a user.** Webuzo lets you have multiple users, each with their own website(s), resource allowances, and dedicated back-end panels. To create your first user, navigate to **Users** > **Add User**. In the **Add user** page that appears, fill out the desired username, password, domain, and email address for the new user. You can also set custom resource allotments and additional settings as needed. 1. **Log in as the user.** You can log in to the user panel (also called the enduser panel) by navigating to the following URL: `http://[ip-address]:2002`. At the login prompt, enter the user credentials that you just created and press **Login**. The user panel should appear: diff --git a/docs/products/tools/marketplace/guides/wireguard/index.md b/docs/products/tools/marketplace/guides/wireguard/index.md index 2876e9bee3e..177c00e6495 100644 --- a/docs/products/tools/marketplace/guides/wireguard/index.md +++ b/docs/products/tools/marketplace/guides/wireguard/index.md @@ -13,7 +13,7 @@ external_resources: aliases: ['/platform/marketplace/deploy-wireguard-with-marketplace-apps/', '/platform/one-click/deploy-wireguard-with-one-click-apps/','/guides/deploy-wireguard-with-one-click-apps/','/guides/deploy-wireguard-with-marketplace-apps/','/guides/wireguard-marketplace-app/'] --- -WireGuard® is a simple, fast, and modern virtual private network (VPN) which utilizes state-of-the-art cryptography. It aims to be faster and leaner than other VPN protocols such as OpenVPN and IPSec, and it has a much smaller source code footprint. +WireGuard® is a simple, fast, and modern virtual private network (VPN) which uses state-of-the-art cryptography. It aims to be faster and leaner than other VPN protocols such as OpenVPN and IPSec, and it has a much smaller source code footprint. Configuring WireGuard is as simple as configuring SSH. A connection is established by an exchange of public keys between server and client, and only a client whose public key is present in the server's configuration file is considered authorized. WireGuard sets up standard network interfaces which behave similarly to other common network interfaces, like `eth0`. This makes it possible to configure and manage WireGuard interfaces using standard networking tools such as ifconfig and ip. @@ -42,7 +42,7 @@ Your WireGuard configuration can be adjusted after you first set up your Marketp ### WireGuard Options -The WireGuard Marketplace form includes fields for your WireGuard client's [*public key*](https://www.wireguard.com/quickstart/#key-generation) and for your client's *endpoint IP* (which is your client's public IP address). If you have already set up your client and installed the WireGuard software on it prior to setting up your WireGuard Marketplace App, then you may already have this information. If you do have the key and the endpoint IP for the client, you can enter them into the app's creation form, and your server's configuration will be pre-populated with those values. +The WireGuard Marketplace form includes fields for your WireGuard client's [*public key*](https://www.wireguard.com/quickstart/#key-generation) and for your client's *endpoint IP* (which is your client's public IP address). If you have already set up your client and installed the WireGuard software on it before setting up your WireGuard Marketplace App, then you may already have this information. If you do have the key and the endpoint IP for the client, you can enter them into the app's creation form, and your server's configuration will be pre-populated with those values. {{< note >}} A public key generated by WireGuard will not resemble [a public key that you might use for SSH connections](/docs/guides/use-public-key-authentication-with-ssh/); when in doubt, leave the form's **Public Key (Client)** field blank. diff --git a/docs/products/tools/marketplace/guides/woocommerce/index.md b/docs/products/tools/marketplace/guides/woocommerce/index.md index 3ad8979b952..e668a3ae286 100644 --- a/docs/products/tools/marketplace/guides/woocommerce/index.md +++ b/docs/products/tools/marketplace/guides/woocommerce/index.md @@ -61,7 +61,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from 1. Log in to your new Compute Instance using one of the methods below: - - **Lish Console:** Within the Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). + - **Lish Console:** Within Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). - **SSH:** Log in to your Compute Instance over SSH using the `root` user. See [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/) for assistance. 1. Once logged in, access the credentials file by running the following command: diff --git a/docs/products/tools/marketplace/guides/wordpress/index.md b/docs/products/tools/marketplace/guides/wordpress/index.md index 324165a0f1b..e9b5ba154c9 100644 --- a/docs/products/tools/marketplace/guides/wordpress/index.md +++ b/docs/products/tools/marketplace/guides/wordpress/index.md @@ -55,7 +55,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from 1. Log in to your new Compute Instance using one of the methods below: - - **Lish Console:** Within the Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). + - **Lish Console:** Within Cloud Manager, navigate to **Linodes** from the left menu, select the Compute Instance you just deployed, and click the **Launch LISH Console** button. Log in as the `root` user. See [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/). - **SSH:** Log in to your Compute Instance over SSH using the `root` user. See [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/) for assistance. 1. Once logged in, access the credentials file by running the following command: @@ -110,7 +110,7 @@ If you didn't set up a domain during the deployment process, you can add it manu ### Resetting Your Admin Password or Email Address -If you need to reset your admin user's password and you aren't receiving the password reset request email, you can update the password from command line. This method also allows you to update the email address for your admin account without needing an email confirmation. +If you need to reset your admin user's password and you aren't receiving the password reset request email, you can update the password from command line. This method also lets you update the email address for your admin account without needing an email confirmation. 1. Log in to the Compute Instance using [SSH](/docs/guides/connect-to-server-over-ssh/) or [Lish](/docs/products/compute/compute-instances/guides/lish/). diff --git a/docs/products/tools/monitoring/_index.md b/docs/products/tools/monitoring/_index.md index bb63098ceb6..2cc67357cbe 100644 --- a/docs/products/tools/monitoring/_index.md +++ b/docs/products/tools/monitoring/_index.md @@ -1,6 +1,6 @@ --- title: Monitoring -description: "Linode performance Monitoring allows you to set custom thresholds and enable the shutdown watchdog, Lassie." +description: "Linode performance Monitoring lets you set custom thresholds and enable the shutdown watchdog, Lassie." tab_group_main: is_root: true title: Overview diff --git a/docs/products/tools/monitoring/developers/index.md b/docs/products/tools/monitoring/developers/index.md index 74a666c012d..6cc561d1b95 100644 --- a/docs/products/tools/monitoring/developers/index.md +++ b/docs/products/tools/monitoring/developers/index.md @@ -21,4 +21,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. diff --git a/docs/products/tools/stackscripts/developers/index.md b/docs/products/tools/stackscripts/developers/index.md index 555c753f0ec..3f620998f28 100644 --- a/docs/products/tools/stackscripts/developers/index.md +++ b/docs/products/tools/stackscripts/developers/index.md @@ -15,4 +15,4 @@ Linode’s [API v4](/docs/api) provides the ability to programmatically manage t ## Linode CLI -The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that allows you to manage your Linode account and resources from the command line. +The [Linode CLI](https://github.com/linode/linode-cli) is a wrapper around the Linode API v4 that lets you manage your Linode account and resources from the command line. diff --git a/docs/products/tools/stackscripts/get-started/index.md b/docs/products/tools/stackscripts/get-started/index.md index ef09f8f297c..25a1d8be16f 100644 --- a/docs/products/tools/stackscripts/get-started/index.md +++ b/docs/products/tools/stackscripts/get-started/index.md @@ -15,7 +15,7 @@ StackScripts allow you to reproduce specific software configurations when deploy ## Write the Script -When creating a StackScript, most of the time is spent writing the deployment script itself. This script runs the first time a Compute Instance boots up and allows you to configure the system to fit your precise needs and requirements. Before you write the script, consider the following: +When creating a StackScript, most of the time is spent writing the deployment script itself. This script runs the first time a Compute Instance boots up and lets you configure the system to fit your precise needs and requirements. Before you write the script, consider the following: - **What is the purpose of your script?** The first question you should ask is *what purpose will your script serve*. Do you want to build a web server? Are you building a script to take care of securing new servers? Consider each task you want your script to perform. @@ -23,7 +23,7 @@ When creating a StackScript, most of the time is spent writing the deployment sc - **Which Linux distributions should the script support?** Since each distribution bundles different core software, the commands needed to install applications or configure networking vary between distributions. You need to determine which distributions you want to have available when deploying the Compute Instance. Then, you can customize your script to include commands for those distributions. -- **Which dynamic variables do you want the user to set when deploying a Compute Instance?** Determine what information you wish to collect during deployment. These user variables can be defined through the use of UDF fields within the script. All UDF fields are visible in the Cloud Manager when creating a Compute Instance based on the StackScript. +- **Which dynamic variables do you want the user to set when deploying a Compute Instance?** Determine what information you wish to collect during deployment. These user variables can be defined through the use of UDF fields within the script. All UDF fields are visible in Cloud Manager when creating a Compute Instance based on the StackScript. For more details on the components of a StackScript, see [Write a Custom Script for Use with StackScripts](/docs/products/tools/stackscripts/guides/write-a-custom-script/) guide. @@ -31,7 +31,7 @@ For more details on the components of a StackScript, see [Write a Custom Script After your script has been written, you are ready to create the StackScript. See [Create a StackScript](/docs/products/tools/stackscripts/guides/create/) for complete instructions. -1. Log into the [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. Click the **Create StackScript** button on the top right of the page. +1. Log into [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. Click the **Create StackScript** button on the top right of the page. 1. Enter a **Label** and **Description** for your StackScript. @@ -45,7 +45,7 @@ After your script has been written, you are ready to create the StackScript. See When creating a new Compute Instance, you can use one of your Account StackScripts or a Community StackScript. For full instructions, see [Deploy a Compute Instance Using a StackScript](/docs/products/tools/stackscripts/guides/deploy-a-compute-instance/). -1. Log into the [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. +1. Log into [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. 1. Navigate to either the **Account StackScript** tab (to deploy your own StackScript) or the **Community StackScript** tab (to deploy a public StackScript). diff --git a/docs/products/tools/stackscripts/guides/_index.md b/docs/products/tools/stackscripts/guides/_index.md index 9519e1cfd87..51e096cc920 100644 --- a/docs/products/tools/stackscripts/guides/_index.md +++ b/docs/products/tools/stackscripts/guides/_index.md @@ -1,7 +1,7 @@ --- title: Guides title_meta: "Guides and Tutorials for StackScripts" -description: "Learn to create and use StackScripts in the Cloud Manager and other related topics, like best practices when writing scripts." +description: "Learn to create and use StackScripts in Cloud Manager and other related topics, like best practices when writing scripts." modified: 2022-11-30 tab_group_main: weight: 30 diff --git a/docs/products/tools/stackscripts/guides/create/index.md b/docs/products/tools/stackscripts/guides/create/index.md index 686891a0078..8eec83621fc 100644 --- a/docs/products/tools/stackscripts/guides/create/index.md +++ b/docs/products/tools/stackscripts/guides/create/index.md @@ -8,9 +8,9 @@ aliases: ['/products/tools/stackscripts/guides/stackscripts-create-stackscript/' {{% content "metadata-stackscripts-notice" %}} -This guide walks you through creating a StackScript through the Cloud Manager. +This guide walks you through creating a StackScript through Cloud Manager. -1. [Open the Create StackScript Form in the Cloud Manager](#open-the-create-stackscript-form-in-the-cloud-manager) +1. [Open the Create StackScript Form in Cloud Manager](#open-the-create-stackscript-form-in-cloud-manager) 1. [Set the Label](#set-the-label) 1. [Add a Description](#add-a-description) 1. [Select Compatible Distribution Images](#select-compatible-distribution-images) @@ -18,9 +18,9 @@ This guide walks you through creating a StackScript through the Cloud Manager. 1. [Enter a Revision Note](#enter-a-revision-note) 1. [Save the StackScript](#save-the-stackscript) -## Open the Create StackScript Form in the Cloud Manager +## Open the Create StackScript Form in Cloud Manager -Log in to the [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. Click the **Create StackScript** button. This opens the *[StackScript Create](https://cloud.linode.com/stackscripts/create)* form. +Log in to [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. Click the **Create StackScript** button. This opens the *[StackScript Create](https://cloud.linode.com/stackscripts/create)* form. ## Set the Label diff --git a/docs/products/tools/stackscripts/guides/deploy-a-compute-instance/index.md b/docs/products/tools/stackscripts/guides/deploy-a-compute-instance/index.md index 77618bb027d..8af84ddd861 100644 --- a/docs/products/tools/stackscripts/guides/deploy-a-compute-instance/index.md +++ b/docs/products/tools/stackscripts/guides/deploy-a-compute-instance/index.md @@ -1,6 +1,6 @@ --- title: Deploy a Compute Instance Using a StackScript -description: 'In this guide, you will learn the various methods you can use in conjunction with the Cloud Manager to deploy a new Linode with a StackScript.' +description: 'In this guide, you will learn the various methods you can use in conjunction with Cloud Manager to deploy a new Linode with a StackScript.' published: 2020-04-22 modified: 2023-02-02 keywords: ["stackscripts", "automation", "script", "custom instance", "deployment"] @@ -11,10 +11,10 @@ aliases: ['/platform/stackscripts/how-to-deploy-a-new-linode-using-a-stackscript When deploying a Compute Instance, you can choose to select a StackScript. This causes the StackScript to run the first time the instance boots up. The StackScript can be from your own account or one that a member of the community has publicly shared. {{< note >}} -Linode does not verify the accuracy of any community submitted StackScripts. Prior to deploying a Compute Instance using a Community StackScript, you should review the script so that you understand what changes it will make on your new instance. +Linode does not verify the accuracy of any community submitted StackScripts. Before deploying a Compute Instance using a Community StackScript, you should review the script so that you understand what changes it will make on your new instance. {{< /note >}} -1. Log into the [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. +1. Log into [Cloud Manager](https://cloud.linode.com/) and select **StackScripts** from the left navigation menu. 1. Navigate to either the *Account StackScripts* tab (for StackScripts on your own customer account) or *Community StackScripts* tab (for StackScripts publicly shared by other members of the community). diff --git a/docs/products/tools/stackscripts/guides/manage/index.md b/docs/products/tools/stackscripts/guides/manage/index.md index a8ded5d8e12..e5c49e9598b 100644 --- a/docs/products/tools/stackscripts/guides/manage/index.md +++ b/docs/products/tools/stackscripts/guides/manage/index.md @@ -11,7 +11,7 @@ aliases: ['/platform/stackscripts/creating-and-managing-stackscripts-a-tutorial/ ## View StackScripts -Log in to the [Cloud Manager](https://cloud.linode.com) and select **StackScripts** from the left menu. If any StackScripts exist on your account, they are listed on this page. +Log in to [Cloud Manager](https://cloud.linode.com) and select **StackScripts** from the left menu. If any StackScripts exist on your account, they are listed on this page. ![Screenshot of the StackScripts page in Cloud Manager](view-stackscripts.png) @@ -25,7 +25,7 @@ See [Create a StackScript](/docs/products/tools/stackscripts/guides/create/) for ## Edit a StackScript -1. Navigate to the **StackScripts** page in the Cloud Manager. See [View StackScripts](#view-stackscripts). +1. Navigate to the **StackScripts** page in Cloud Manager. See [View StackScripts](#view-stackscripts). 1. Locate the StackScript you wish to view or edit. Click on the corresponding **Edit** link, which may appear within the ellipsis menu. @@ -39,7 +39,7 @@ See [Create a StackScript](/docs/products/tools/stackscripts/guides/create/) for Making an Account StackScript public allows the rest of the Linode community to access your script as a *Community StackScript*. -1. Navigate to the **StackScripts** page in the Cloud Manager. See [View StackScripts](#view-stackscripts). +1. Navigate to the **StackScripts** page in Cloud Manager. See [View StackScripts](#view-stackscripts). 1. Locate the StackScript you wish to view or edit. Click on the corresponding **Make StackScript Public** link, which may appear within the ellipsis menu. @@ -61,7 +61,7 @@ Your public StackScript is available to you for use on the Account StackScripts You cannot delete Account StackScripts that have been made public. {{< /note >}} -1. Navigate to the **StackScripts** page in the Cloud Manager. See [View StackScripts](#view-stackscripts). +1. Navigate to the **StackScripts** page in Cloud Manager. See [View StackScripts](#view-stackscripts). 1. Locate the StackScript you wish to delete. Click on the corresponding **Delete** link, which may appear within the ellipsis menu. diff --git a/docs/products/tools/stackscripts/guides/write-a-custom-script/index.md b/docs/products/tools/stackscripts/guides/write-a-custom-script/index.md index 79fe6b496db..cc12971318b 100644 --- a/docs/products/tools/stackscripts/guides/write-a-custom-script/index.md +++ b/docs/products/tools/stackscripts/guides/write-a-custom-script/index.md @@ -13,7 +13,7 @@ At the core of all StackScripts is a custom script that is written to perform a ## Before You Begin -When creating a StackScript, most of the time is spent writing the deployment script itself. This script runs the first time a Compute Instance boots up and allows you to configure the system to fit your precise needs and requirements. Before you write the script, consider the following: +When creating a StackScript, most of the time is spent writing the deployment script itself. This script runs the first time a Compute Instance boots up and lets you configure the system to fit your precise needs and requirements. Before you write the script, consider the following: - **What is the purpose of your script?** The first question you should ask is *what purpose will your script serve*. Do you want to build a web server? Are you building a script to take care of securing new servers? Consider each task you want your script to perform. @@ -21,7 +21,7 @@ When creating a StackScript, most of the time is spent writing the deployment sc - **Which Linux distributions should the script support?** Since each distribution bundles different core software, the commands needed to install applications or configure networking vary between distributions. You need to determine which distributions you want to have available when deploying the Compute Instance. Then, you can customize your script to include commands for those distributions. -- **Which dynamic variables do you want the user to set when deploying a Compute Instance?** Determine what information you wish to collect during deployment. These user variables can be defined through the use of UDF fields within the script. All UDF fields are visible in the Cloud Manager when creating a Compute Instance based on the StackScript. +- **Which dynamic variables do you want the user to set when deploying a Compute Instance?** Determine what information you wish to collect during deployment. These user variables can be defined through the use of UDF fields within the script. All UDF fields are visible in Cloud Manager when creating a Compute Instance based on the StackScript. ## Components of a StackScript @@ -31,7 +31,7 @@ When creating a StackScript, most of the time is spent writing the deployment sc #!/bin/bash ``` -- **Declaration of user-defined fields** *(optional)*: These fields are presented to the user in the Cloud Manager during the deployment process. See [Declare User-Defined Fields (UDFs)](#declare-user-defined-fields-udfs). +- **Declaration of user-defined fields** *(optional)*: These fields are presented to the user in Cloud Manager during the deployment process. See [Declare User-Defined Fields (UDFs)](#declare-user-defined-fields-udfs). ```file {linenostart="2"} # @@ -62,7 +62,7 @@ The first line of the script must include a [*shebang*](https://en.wikipedia.org ## Declare User-Defined Fields (UDFs) -The StackScript system provides a basic markup specification that interfaces with the Linode deployment process. This syntax allows users to customize the behavior of a StackScript on a per-deployment basis. When a StackScript contains a *user-defined field (UDF)*, the Cloud Manager presents the UDF as a form field. The user can then insert a corresponding custom value into the field. The values and their related variables are inserted into the script's environment when used to deploy a new Compute Instance. +The StackScript system provides a basic markup specification that interfaces with the Linode deployment process. This syntax allows users to customize the behavior of a StackScript on a per-deployment basis. When a StackScript contains a *user-defined field (UDF)*, Cloud Manager presents the UDF as a form field. The user can then insert a corresponding custom value into the field. The values and their related variables are inserted into the script's environment when used to deploy a new Compute Instance. {{< note >}} UDF fields are only usable by scripts written in bash. @@ -96,13 +96,13 @@ A UDF tag accepts the following attributes: `label="[field-label]"` - The label attribute is used when displaying the field to the user in the Cloud Manager. This should be a short string that clearly indicates what the field is used for. If needed, you can also enter helper text using the `example` attribute. + The label attribute is used when displaying the field to the user in Cloud Manager. This should be a short string that clearly indicates what the field is used for. If needed, you can also enter helper text using the `example` attribute. - **Helper text** (*optional*): `example="[helper-text]"` - This text is displayed in the Cloud Manager underneath the field. It should be used to further explain to the user what the field is used for. + This text is displayed in Cloud Manager underneath the field. It should be used to further explain to the user what the field is used for. - **Select one** (*optional*): @@ -114,17 +114,17 @@ A UDF tag accepts the following attributes: `manyOf="[value1],[value2],..."` - A comma separated list of acceptable values for the field in any quantity, combination, or order. These values are displayed within a dropdown menu in the Cloud Manager. Multiple values can be selected by the user. This cannot be used within the *oneOf* attribute (discussed above) within the same UDF tag. + A comma separated list of acceptable values for the field in any quantity, combination, or order. These values are displayed within a dropdown menu in Cloud Manager. Multiple values can be selected by the user. This cannot be used within the *oneOf* attribute (discussed above) within the same UDF tag. - **Default value** (*optional*): `default="[default-value]"` - This defines the default value for this UDF. If no value is specified by the user during deployment, this default value is used. The default value is displayed to the user within the Cloud Manager. + This defines the default value for this UDF. If no value is specified by the user during deployment, this default value is used. The default value is displayed to the user within Cloud Manager. - - **String** (neither `oneOf` or `manyOf` are used): The default value can be any string and is displayed as plain text within the form field in the Cloud Manager. - - **Select one** (`oneOf` attribute is defined): The default value needs to correspond with a single value defined in the `oneOf` attribute. This value is pre-selected in the radio field or dropdown box in the Cloud Manager. - - **Select multiple** (`manOf` attribute is defined): The default value needs to correspond with one or more values defined in the `manyOf` attribute. If setting multiple values as the default, delimit them with a comma. These values are pre-selected in the dropdown box in the Cloud Manager. + - **String** (neither `oneOf` or `manyOf` are used): The default value can be any string and is displayed as plain text within the form field in Cloud Manager. + - **Select one** (`oneOf` attribute is defined): The default value needs to correspond with a single value defined in the `oneOf` attribute. This value is pre-selected in the radio field or dropdown box in Cloud Manager. + - **Select multiple** (`manOf` attribute is defined): The default value needs to correspond with one or more values defined in the `manyOf` attribute. If setting multiple values as the default, delimit them with a comma. These values are pre-selected in the dropdown box in Cloud Manager. ## Default Environment Variables @@ -159,7 +159,7 @@ The files you reference within your script must exist and be accessible via `HTT ## Import a StackScript -Your scripts can import any other StackScript, including those from within your own account or those shared with the community. This allows you to reuse code between StackScripts, minimizing the amount of new code you might need to write. +Your scripts can import any other StackScript, including those from within your own account or those shared with the community. This lets you reuse code between StackScripts, minimizing the amount of new code you might need to write. - **Bash:** @@ -174,9 +174,9 @@ Your scripts can import any other StackScript, including those from within your ./ssinclude-[ID] ``` -In the example syntax above, replace *[ID]* with the ID corresponding to the StackScript you wish to use. You can find the ID by viewing the StackScript in the Cloud Manager and copying the value within the **StackScript ID** field, as shown below: +In the example syntax above, replace *[ID]* with the ID corresponding to the StackScript you wish to use. You can find the ID by viewing the StackScript in Cloud Manager and copying the value within the **StackScript ID** field, as shown below: -![Screenshot of the StackScript ID in the Cloud Manager](stackscript-id.png) +![Screenshot of the StackScript ID in Cloud Manager](stackscript-id.png) ### Using the Linode StackScript Bash Library