├── .github └── PULL_REQUEST_TEMPLATE.md ├── CODE_OF_CONDUCT.md ├── LICENSE-SUMMARY ├── doc_source ├── resource-level-permissions-and-auth-based-on-tags-support.md ├── detach-lightsail-instances-from-load-balancer.md ├── delete-lightsail-load-balancer.md ├── attach-validated-certificate-to-load-balancer.md ├── understanding-resources-in-amazon-lightsail-and-aws.md ├── managing-your-instance-using-lightsail.md ├── infrastructure-security.md ├── amazon-lightsail-compliance.md ├── understanding-static-ip-addresses-in-amazon-lightsail.md ├── create-policy-that-grants-access-to-amazon-lightsail.md ├── understanding-instances-virtual-private-servers-in-amazon-lightsail.md ├── amazon-lightsail-high-availability-databases.md ├── amazon-lightsail-task-monitor.md ├── lightsail-how-to-set-up-and-configure-aws-cli.md ├── disaster-recovery-resiliency.md ├── enable-set-up-health-checking-for-lightsail-load-balancer-metrics.md ├── troubleshooting-tls-ssl-certificate-issues.md ├── understanding-networking-resources-in-lightsail.md ├── delete-tls-ssl-certificate-lightsail-load-balancer-https.md ├── create-block-storage-disk-snapshot.md ├── security.md ├── detach-and-delete-block-storage-disks.md ├── amazon-lightsail-deleting-your-database.md ├── amazon-lightsail-deleting-snapshots.md ├── lightsail-how-to-ssh-connect-to-instance-virtual-private-server-using-putty.md ├── amazon-lightsail-importing-data-into-your-mysql-database.md ├── amazon-lightsail-download-ssl-certificate-for-managed-database.md ├── troubleshoot-ghost-instance-service-unavailable.md ├── troubleshooting-lightsail-load-balancer-issues.md ├── lightsail-how-to-set-up-vpc-peering-with-aws-resources.md ├── add-alternate-domain-names-to-tls-ssl-certificate-https.md ├── creating-resources-with-cloudformation.md ├── amazon-lightsail-edit-or-delete-a-dns-zone.md ├── amazon-lightsail-deleting-health-metric-alarms.md ├── create-tls-ssl-certificate-and-attach-to-lightsail-load-balancer-https.md ├── amazon-lightsail-importing-data-into-your-postgres-database.md ├── use-non-default-key-with-windows-based-instance-in-lightsail.md ├── amazon-lightsail-creating-a-database-snapshot.md ├── amazon-lightsail-notifications.md ├── lightsail-how-to-configure-server-additional-data-shell-script.md ├── update-settings-for-lightsail-load-balancer-health-check-path-https-session-stickiness-persistence-cookie-duration.md ├── amazon-lightsail-deleting-tags.md ├── lightsail-how-to-create-a-snapshot-of-your-instance.md ├── amazon-lightsail-configuring-database-public-mode.md ├── lightsail-create-static-ip.md ├── amazon-lightsail-managing-database-password.md ├── lightsail-how-to-start-stop-or-restart-your-instance-virtual-private-server.md ├── elastic-block-storage-and-ssd-disks-in-amazon-lightsail.md ├── enable-session-stickiness-persistence-or-change-cookie-duration.md ├── amazon-lightsail-configuring-database-data-import-mode.md ├── amazon-lightsail-update-management.md ├── amazon-lightsail-updating-ec2-instances.md ├── amazon-lightsail-connecting-to-postgres-database-using-ssl.md ├── amazon-lightsail-troubleshooting-notifications.md ├── getting-help-in-amazon-lightsail.md ├── amazon-lightsail-organizing-resources-using-tags.md ├── amazon-lightsail-domain-privacy-protection.md ├── amazon-lightsail-controlling-access-using-tags.md ├── amazon-lightsail-deleting-distribution.md ├── lightsail-how-to-set-up-access-keys-to-use-sdk-api-cli.md ├── amazon-lightsail-adding-tags-to-a-resource.md ├── amazon-lightsail-viewing-database-logs-and-history.md ├── amazon-lightsail-domain-register-other-dns-service-procedure.md ├── amazon-lightsail-domain-whois-rdap.md ├── how-to-create-larger-instance-from-snapshot-using-console.md ├── amazon-lightsail-securing-windows-server-amazon-ec2-instances.md ├── troubleshooting-block-storage-disk-issues.md ├── amazon-lightsail-domain-update-contacts.md ├── amazon-lightsail-organizing-costs-using-tags.md ├── amazon-lightsail-choosing-a-database.md ├── amazon-lightsail-cloudformation-stacks.md ├── amazon-lightsail-troubleshooting-browser-based-ssh-rdp-client-connection.md ├── extending-windows-server-storage-space-in-amazon-lightsail.md ├── what-is-amazon-lightsail.md ├── amazon-lightsail-deleting-notification-contacts.md ├── amazon-lightsail-databases.md ├── amazon-lightsail-define-the-primary-domain-for-your-wordpress-multisite.md ├── lightsail-how-to-create-instance-from-snapshot.md ├── amazon-lightsail-resetting-distribution-cache.md ├── security-iam-awsmanpol.md ├── amazon-lightsail-instance-metadata.md └── getting-started-with-wordpress-and-lightsail.md ├── LICENSE-SAMPLECODE └── README.md /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | *Issue #, if available:* 2 | 3 | *Description of changes:* 4 | 5 | 6 | By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. 7 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | ## Code of Conduct 2 | This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 3 | For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 4 | opensource-codeofconduct@amazon.com with any additional questions or comments. 5 | -------------------------------------------------------------------------------- /LICENSE-SUMMARY: -------------------------------------------------------------------------------- 1 | Copyright 2019 Amazon.com, Inc. or its affiliates. All Rights Reserved. 2 | 3 | The documentation is made available under the Creative Commons Attribution-ShareAlike 4.0 International License. See the LICENSE file. 4 | 5 | The sample code within this documentation is made available under the MIT-0 license. See the LICENSE-SAMPLECODE file. 6 | -------------------------------------------------------------------------------- /doc_source/resource-level-permissions-and-auth-based-on-tags-support.md: -------------------------------------------------------------------------------- 1 | # Support for resource\-level permissions and authorization based on tags in Amazon Lightsail 2 | 3 | *Last updated: June 23, 2022* 4 | 5 | Lightsail supports resource\-level permissions and authorization based on tags for some of its API actions\. For more information, see [Actions, resources, and condition keys for Amazon Lightsail](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonlightsail.html) in the *Service Authorization Reference*\. -------------------------------------------------------------------------------- /doc_source/detach-lightsail-instances-from-load-balancer.md: -------------------------------------------------------------------------------- 1 | # Detach one or more instances from a Lightsail load balancer 2 | 3 | *Last updated: November 29, 2017* 4 | 5 | If you no longer want to have an instance attached to your Lightsail load balancer, you can detach it\. When you detach a Lightsail instance from a load balancer, we wait until the specified instances are no longer needed before detaching\. 6 | 7 | 1. On the Lightsail home page, choose **Networking**\. 8 | 9 | 1. Choose the load balancer you want to manage\. 10 | 11 | 1. On the **Target instances** tab, choose **Detach** next to the load balancer you want to detach\. -------------------------------------------------------------------------------- /doc_source/delete-lightsail-load-balancer.md: -------------------------------------------------------------------------------- 1 | # Delete a Lightsail load balancer 2 | 3 | *Last updated: November 29, 2017* 4 | 5 | You can delete a Lightsail load balancer if you no longer need it\. Deleting a load balancer also detaches any Lightsail instances attached to it but doesn't delete the Lightsail instances\. If you enabled encrypted \(HTTPS\) traffic using an SSL/TLS certificate, deleting the load balancer will also permanently delete any SSL/TLS certificates associated with the load balancer\. 6 | 7 | **Important** 8 | Deleting a Lightsail load balancer and its associated certificate is final and can't be undone\. 9 | 10 | 1. On the Lightsail home page, choose **Networking**\. 11 | 12 | 1. Choose the load balancer you want to delete\. 13 | 14 | 1. Choose **Delete**\. 15 | 16 | 1. Choose **Delete load balancer**\. 17 | 18 | 1. Choose **Yes, delete**\. -------------------------------------------------------------------------------- /doc_source/attach-validated-certificate-to-load-balancer.md: -------------------------------------------------------------------------------- 1 | # Attach a validated SSL/TLS certificate to your Lightsail load balancer 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | After you verify that you control your domain, the certificate's status will change to **Valid**\. 6 | 7 | ![\[Successful validation of domain\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/example-com-verified-and-ready-to-use.png) 8 | 9 | Your next step is to attach the certificate to your Lightsail load balancer\. 10 | 11 | 1. From the Lightsail home page, choose **Networking**\. 12 | 13 | 1. Choose your load balancer\. 14 | 15 | 1. Choose the **Custom domains** tab\. 16 | 17 | 1. In the **Certificates** section, choose **Attach certificate**\. 18 | 19 | 1. Select a certificate from the dropdown list\. 20 | 21 | 1. Choose **Attach** to attach the certificate\. -------------------------------------------------------------------------------- /LICENSE-SAMPLECODE: -------------------------------------------------------------------------------- 1 | Copyright 2019 Amazon.com, Inc. or its affiliates. All Rights Reserved. 2 | 3 | Permission is hereby granted, free of charge, to any person obtaining a copy of this 4 | software and associated documentation files (the "Software"), to deal in the Software 5 | without restriction, including without limitation the rights to use, copy, modify, 6 | merge, publish, distribute, sublicense, and/or sell copies of the Software, and to 7 | permit persons to whom the Software is furnished to do so. 8 | 9 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, 10 | INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 11 | PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT 12 | HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION 13 | OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 14 | SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 15 | -------------------------------------------------------------------------------- /doc_source/understanding-resources-in-amazon-lightsail-and-aws.md: -------------------------------------------------------------------------------- 1 | # Resources in Amazon Lightsail and AWS 2 | 3 | **Note** 4 | In AWS, everything you create and work with is called a resource\. A virtual private server \(or *instance*\) is a resource, a database is a resource, and so on\. In Lightsail, resources include Lightsail instances, static IP addresses, DNS zones, and instance snapshots\. 5 | 6 | *Last updated: March 22, 2017* 7 | 8 | Learn more about Lightsail resources: 9 | + [DNS zones](understanding-dns-in-amazon-lightsail.md) 10 | + [Lightsail instances](understanding-instances-virtual-private-servers-in-amazon-lightsail.md) 11 | + [Snapshots](understanding-instance-snapshots-in-amazon-lightsail.md) 12 | + [Static IP addresses](understanding-static-ip-addresses-in-amazon-lightsail.md) 13 | 14 | To work with AWS resources outside of Lightsail, you need to [peer your Amazon VPC with your Lightsail VPC](lightsail-how-to-set-up-vpc-peering-with-aws-resources.md)\. -------------------------------------------------------------------------------- /doc_source/managing-your-instance-using-lightsail.md: -------------------------------------------------------------------------------- 1 | # Managing your Amazon Lightsail instance 2 | 3 | *Last updated: May 17, 2017* 4 | 5 | In Lightsail, your virtual private server is called an instance\. You can connect to your instance, manage your ports and firewall settings, view metrics, associate a static IP with your instance, and more\. Choose a task to learn how to get the most out of your instance: 6 | + [Connecting to your Linux or Unix instance in Amazon Lightsail](lightsail-how-to-connect-to-your-instance-virtual-private-server.md) 7 | + [View metrics](understanding-instance-health-metrics-in-amazon-lightsail.md) 8 | + [Create a static IP address and attach it to an instance](lightsail-create-static-ip.md) 9 | + [Firewall and ports in Amazon Lightsail](understanding-firewall-and-port-mappings-in-amazon-lightsail.md) 10 | + [Creating a snapshot of your Linux or Unix instance in Amazon Lightsail](lightsail-how-to-create-a-snapshot-of-your-instance.md) 11 | + [Start, stop, or restart your instance](lightsail-how-to-start-stop-or-restart-your-instance-virtual-private-server.md) -------------------------------------------------------------------------------- /doc_source/infrastructure-security.md: -------------------------------------------------------------------------------- 1 | # Infrastructure Security in Amazon Lightsail 2 | 3 | *Last updated: February 18, 2020* 4 | 5 | As a managed service, Amazon Lightsail is protected by the AWS global network security procedures that are described in the [Amazon Web Services: Overview of Security Processes](https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Whitepaper.pdf) whitepaper\. 6 | 7 | You use AWS published API calls to access Lightsail through the network\. Clients must support Transport Layer Security \(TLS\) 1\.0 or later\. We recommend TLS 1\.2 or later\. Clients must also support cipher suites with perfect forward secrecy \(PFS\) such as Ephemeral Diffie\-Hellman \(DHE\) or Elliptic Curve Ephemeral Diffie\-Hellman \(ECDHE\)\. Most modern systems such as Java 7 and later support these modes\. 8 | 9 | Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal\. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/Welcome.html) \(AWS STS\) to generate temporary security credentials to sign requests\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-compliance.md: -------------------------------------------------------------------------------- 1 | # Compliance Validation for Amazon Lightsail 2 | 3 | *Last updated: January 10, 2022* 4 | 5 | AWS provides the following resources to help with compliance: 6 | + [Security and Compliance Quick Start Guides](https://aws.amazon.com/quickstart/?awsf.quickstart-homepage-filter=categories%23security-identity-compliance) – These deployment guides discuss architectural considerations and provide steps for deploying security\- and compliance\-focused baseline environments on AWS\. 7 | + [AWS Compliance Resources](https://aws.amazon.com/compliance/resources/) – This collection of workbooks and guides might apply to your industry and location\. 8 | + [Evaluating Resources with Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *AWS Config Developer Guide* – The AWS Config service assesses how well your resource configurations comply with internal practices, industry guidelines, and regulations\. 9 | + [AWS Security Hub](https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html) – This AWS service provides a comprehensive view of your security state within AWS that helps you check your compliance with security industry standards and best practices\. -------------------------------------------------------------------------------- /doc_source/understanding-static-ip-addresses-in-amazon-lightsail.md: -------------------------------------------------------------------------------- 1 | # Static IP addresses in Amazon Lightsail 2 | 3 | **Note** 4 | A static IP is a fixed, public IP address that you can assign and reassign to an instance or other resource\. If you haven't set up a static IP address, each time you stop or restart your instance, Lightsail assigns a new public IP address\. 5 | 6 | *Last updated: March 23, 2017* 7 | 8 | Learn about these common tasks for working with static IP addresses: 9 | + [IP addresses in Amazon Lightsail](understanding-public-ip-and-private-ip-addresses-in-amazon-lightsail.md) 10 | + [Create a static IP address in Lightsail](lightsail-create-static-ip.md) 11 | + [Restart, stop, or start your Lightsail instance](lightsail-how-to-start-stop-or-restart-your-instance-virtual-private-server.md) 12 | 13 | **Important** 14 | If you stop or restart your instance without first creating a static IP address and attaching it to your instance, you lose your IP address when your instance restarts\. You should create a static IP address and attach it to your instance to ensure that your instance always has the same public IP address\. For more information, see [Create a static IP address in Lightsail](lightsail-create-static-ip.md)\. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # NOTICE 2 | 3 | **This repository is archived and the content on this branch is out of date.** You can find up-to-date AWS technical documentation on the [AWS Documentation website](https://docs.aws.amazon.com/), where you can also submit feedback and suggestions for improvement. 4 | 5 | # Announcement 6 | 7 | This repository will be archived and marked read-only next month (June 2023). For more information, read [the announcement on the AWS News Blog](https://aws.amazon.com/blogs/aws/retiring-the-aws-documentation-on-github/). 8 | 9 | You can find the corresponding content for this repo on [the AWS Documentation website](https://docs.aws.amazon.com). If you'd like to continue contributing to the quality of AWS documentation, you can submit feedback and suggestions for improvement there. 10 | 11 | ## Amazon Lightsail Developer Guide 12 | 13 | The open source version of the Amazon Lightsail docs. To submit feedback or requests for changes, submit an issue or make changes and submit a pull request. 14 | 15 | ## License Summary 16 | 17 | The documentation is made available under the Creative Commons Attribution-ShareAlike 4.0 International License. See the LICENSE file. 18 | 19 | The sample code within this documentation is made available under the MIT-0 license. See the LICENSE-SAMPLECODE file. 20 | -------------------------------------------------------------------------------- /doc_source/create-policy-that-grants-access-to-amazon-lightsail.md: -------------------------------------------------------------------------------- 1 | # Troubleshooting a 403 \(unauthorized\) error and getting back into Amazon Lightsail 2 | 3 | *Last updated: May 20, 2019* 4 | 5 | If you get a 403 error when trying to access the [Lightsail console](https://lightsail.aws.amazon.com/), don’t panic\. Try these steps to troubleshoot the problem: 6 | + If your AWS account or your AWS Identity and Access Management \(IAM\) user was recently created, wait a few minutes, and then refresh your browser\. 7 | + If it’s been a while since you last signed in, refresh your browser\. If you're prompted to sign in again, be sure to use an IAM user that has access to Lightsail\. 8 | + If your IAM user doesn’t have access to Lightsail, then contact the [AWS account root user](https://docs.aws.amazon.com/general/latest/gr/root-vs-iam.html) or an IAM user with administrator access to request access to Lightsail\. To learn more, see [Manage access to Amazon Lightsail for an IAM user](amazon-lightsail-managing-access-for-an-iam-user.md)\. 9 | + If you continue to get the 403 error after trying the above steps, contact [AWS Customer Support](https://console.aws.amazon.com/support/home#/)\. In some rare cases for AWS accounts created before 2011, support will have to manually subscribe your account to Lightsail\. -------------------------------------------------------------------------------- /doc_source/understanding-instances-virtual-private-servers-in-amazon-lightsail.md: -------------------------------------------------------------------------------- 1 | # Instances \(virtual private servers\) in Lightsail 2 | 3 | **Note** 4 | Your Lightsail instance is a virtual private server \(also called a *virtual machine*\)\. When you create your instance, you choose an image that has an operating system \(OS\) on it\. You can also choose an instance image that has an application or development stack on it, including the base OS\. 5 | 6 | *Last updated: October 16, 2017* 7 | 8 | For a complete list of operating systems, applications, and development frameworks, see [Choose an Amazon Lightsail instance image](compare-options-choose-lightsail-instance-image.md)\. 9 | 10 | For more tasks and topics about instances, see: 11 | + [Get started with Linux/Unix\-based instances in Lightsail](getting-started-with-amazon-lightsail.md) 12 | + [Get started with Windows\-based instances in Lightsail](get-started-with-windows-based-instances-in-lightsail.md) 13 | + [Connecting to your Linux or Unix instance in Amazon Lightsail](lightsail-how-to-connect-to-your-instance-virtual-private-server.md) 14 | + [Managing your instance using Amazon Lightsail](managing-your-instance-using-lightsail.md) 15 | 16 | Learn more in\-depth information about [Instances and AMIs in Amazon EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instances-and-amis.html)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-high-availability-databases.md: -------------------------------------------------------------------------------- 1 | # High availability databases in Amazon Lightsail 2 | 3 | **Note** 4 | High availability databases in Amazon Lightsail provide failover support by having a primary database in one Availability Zone, and a secondary standby database in another Availability Zone\. 5 | 6 | *Last updated: March 15, 2019* 7 | 8 | Do you need failover support for your Amazon Lightsail database? A Lightsail high availability managed database provides this support with a primary database in one Availability Zone, and a secondary standby database in another\. We recommend high availability databases for production workloads that experience heavy use and require data redundancy\. For development and test purposes, you can use a standard database that isn't high availability\. 9 | 10 | To create a high availability database, select one of the high availability database plans available in Lightsail when creating your managed database\. For more information, see [Creating a database in Amazon Lightsail](amazon-lightsail-creating-a-database.md) \. You can also change your standard database to a high availability database\. Create a snapshot of your standard database, create a new database from the snapshot, and choose a high availability plan\. For more information, see [Creating a database from a snapshot in Amazon Lightsail](amazon-lightsail-creating-a-database-from-snapshot.md)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-task-monitor.md: -------------------------------------------------------------------------------- 1 | # Task monitor in Amazon Lightsail 2 | 3 | **Note** 4 | Use the task monitor in the Amazon Lightsail console to track the status of exporting Lightsail snapshots to Amazon EC2, and creating new Amazon EC2 instances from exported instance snapshots\. 5 | 6 | *Last updated: November 28, 2018* 7 | 8 | The task monitor in the Amazon Lightsail console tracks the status of exporting Lightsail snapshots to Amazon EC2, or creating new EC2 instances from exported instance snapshots\. These tasks can take a while depending on the size and configuration of the source instance or block storage disk\. The task monitor displays the latest 20 tasks that are in progress or completed\. It can be accessed from the top navigation pane on all pages of the Lightsail console\. The task monitor icon is orange when a task is in progress, or grey when all tasks are completed\. 9 | 10 | ![\[The task monitor in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-task-monitor.png) 11 | 12 | For more information about exporting Lightsail snapshots to Amazon EC2, or creating EC2 instances from exported snapshots, see the following guides: 13 | + [Exporting Amazon Lightsail snapshots to Amazon EC2](amazon-lightsail-exporting-snapshots-to-amazon-ec2.md) 14 | + [Creating Amazon EC2 instances from exported snapshots in Amazon Lightsail](amazon-lightsail-creating-ec2-instances-from-exported-snapshots.md) -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-set-up-and-configure-aws-cli.md: -------------------------------------------------------------------------------- 1 | # Configuring the AWS Command Line Interface to work with Amazon Lightsail 2 | 3 | *Last updated: October 2, 2019* 4 | 5 | The AWS Command Line Interface \(AWS CLI\) is a tool that allows advanced users and developers to control the Amazon Lightsail service by typing commands in the terminal \(on Linux and Unix\) or Command Prompt \(on Windows\)\. You can also control Lightsail using the Lightsail console, a graphical user interface, and the Lightsail application program interface \(API\)\. 6 | 7 | In Lightsail, you can install the AWS CLI on your local desktop or install it on your Lightsail instance\. 8 | + To install the AWS CLI on your local desktop, see [Installing the AWS CLI](http://docs.aws.amazon.com/cli/latest/userguide/installing.html) in the AWS Command Line Interface documentation\. 9 | + To install the AWS CLI on your Ubuntu\-based Lightsail instance, connect to your instance, and type `sudo apt-get -y install awscli`\. 10 | 11 | **Note** 12 | The AWS CLI should already be installed on the Amazon Linux Lightsail instance\. If you need to reinstall it, connect to your instance, and type `sudo yum install aws-cli`\. 13 | 14 | After you install the AWS CLI, you need to obtain access keys and then configure the AWS CLI to use them\. For more information, see [Create an access key to use the Amazon Lightsail API or the AWS Command Line Interface](lightsail-how-to-set-up-access-keys-to-use-sdk-api-cli.md)\. -------------------------------------------------------------------------------- /doc_source/disaster-recovery-resiliency.md: -------------------------------------------------------------------------------- 1 | # Resilience in Amazon Lightsail 2 | 3 | *Last updated: February 18, 2020* 4 | 5 | The AWS global infrastructure is built around AWS Regions and Availability Zones\. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low\-latency, high\-throughput, and highly redundant networking\. With Availability Zones, you can design and operate applications and databases that automatically fail over between zones without interruption\. Availability Zones are more highly available, fault tolerant, and scalable than traditional single or multiple data center infrastructures\. 6 | 7 | For more information about AWS Regions and Availability Zones, see [AWS Global Infrastructure](http://aws.amazon.com/about-aws/global-infrastructure/)\. 8 | 9 | In addition to the AWS global infrastructure, Lightsail offers several features to help support your data resiliency and backup needs\. 10 | + Copying instance and disk snapshots across Regions\. For more information, see [Snapshots in Amazon Lightsail](understanding-instance-snapshots-in-amazon-lightsail.md)\. 11 | + Automating instance and disk snapshots snapshots\. For more information, see [Snapshots in Amazon Lightsail](understanding-instance-snapshots-in-amazon-lightsail.md)\. 12 | + Distributing incoming traffic across multiple instances in a single Availability Zone or multiple Availability Zones using a load balancer\. For more information, see [Amazon Lightsail load balancers](understanding-lightsail-load-balancers.md)\. -------------------------------------------------------------------------------- /doc_source/enable-set-up-health-checking-for-lightsail-load-balancer-metrics.md: -------------------------------------------------------------------------------- 1 | # Health checking for your Lightsail load balancer 2 | 3 | *Last updated: November 29, 2017* 4 | 5 | By default, Lightsail performs health checks on your instances at the root \(`"/"`\) of your web application\. The health checks are used to monitor the health of the registered instances so that the load balancer can send requests only to the healthy instances\. The health checks start as soon as you attach the instances to your load balancer\. 6 | 7 | One of the following statuses is returned\. 8 | + Passed 9 | + Failed 10 | 11 | If your health check fails, you can try to figure out what is wrong by using the AWS Command Line Interface or the Lightsail API\. See our troubleshooting guide for more information\. 12 | 13 | ## Customize your health check path 14 | 15 | You might want to customize your health check path\. For example, if your home page loads slowly or has a lot of images on it, you can configure Lightsail to check a different page that loads faster\. 16 | 17 | 1. On the Lightsail home page, choose **Networking**\. 18 | 19 | 1. Choose your load balancer to manage it\. 20 | 21 | 1. On the **Target instances** tab, choose **Customize health checking**\. 22 | 23 | 1. Type a valid path for your health check, and then choose **Save**\. 24 | ![\[Customize the health check path\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/customize-health-checking-path.png) -------------------------------------------------------------------------------- /doc_source/troubleshooting-tls-ssl-certificate-issues.md: -------------------------------------------------------------------------------- 1 | # Troubleshooting Lightsail SSL/TLS certificate issues 2 | 3 | *Last updated: November 29, 2017* 4 | 5 | You might encounter errors with your Lightsail load balancers\. This topic identifies common issues and workarounds for those errors\. 6 | 7 | Choose the issue below that best describes your problem, and follow the links to fix the issue\. If you encounter an issue that's not in the list, use the **Questions? Comments?** link at the bottom of this page to submit feedback or contact AWS Customer Support\. 8 | 9 | **I can't create a certificate\.** 10 | There is a quota to the number of certificates you can create in an AWS account\. For more information, see [Quotas](http://docs.aws.amazon.com/acm/latest/userguide/acm-limits.html) in the AWS Certificate Manager User Guide\. The same quotas apply to Lightsail certificates for load balancers\. 11 | *Actual error message:*  **Sorry, you've requested too many certificates for your account\.** 12 | 13 | **My certificate request failed\.** 14 | If your certificate request failed, you can **Retry** on the **Inbound traffic** tab of the load balancer management page\. 15 | If you still can't figure out what went wrong, contact AWS Customer Support\. 16 | 17 | **My domain showed as invalid\.** 18 | If you're having trouble verifying that you control a domain, check to see that you have access to the DNS management\. If you do and you followed [these instructions](understanding-tls-ssl-certificates-in-lightsail-https.md) but still can't validate, contact AWS Customer Support\. -------------------------------------------------------------------------------- /doc_source/understanding-networking-resources-in-lightsail.md: -------------------------------------------------------------------------------- 1 | # Networking resources in Lightsail 2 | 3 | **Note** 4 | Lightsail has several networking resources to choose from: Static IPs, content delivery network \(CDN\) distributions, DNS zones, and load balancers\. These resources improve how users and outside services connect to your Lightsail instances\. 5 | 6 | *Last updated: July 23, 2020* 7 | 8 | ## Distributions 9 | 10 | You can create a content delivery network \(CDN\) distribution to speed up the delivery of your content to your users around the world\. For more information, see [Content delivery network distributions in Amazon Lightsail](amazon-lightsail-content-delivery-network-distributions.md)\. 11 | 12 | ## Static IPs 13 | 14 | You can create *static IP addresses* to keep the same IP address every time you reboot your instance\. For more information, see [Static IP addresses in Amazon Lightsail](understanding-static-ip-addresses-in-amazon-lightsail.md)\. 15 | 16 | ## DNS zones 17 | 18 | You can create *DNS zones* to make it easier to find your web application\. For more information, see [DNS in Amazon Lightsail](understanding-dns-in-amazon-lightsail.md)\. 19 | 20 | ## Load balancers 21 | 22 | You can create *load balancers* to add redundancy or to handle more traffic\. For more information, see [Amazon Lightsail load balancers](understanding-lightsail-load-balancers.md)\. -------------------------------------------------------------------------------- /doc_source/delete-tls-ssl-certificate-lightsail-load-balancer-https.md: -------------------------------------------------------------------------------- 1 | # Delete an SSL/TLS certificate in Amazon Lightsail 2 | 3 | *Last updated: July 23, 2020* 4 | 5 | You can delete an SSL/TLS certificate that you're no longer using\. For example, your certificate might be expired and you've already attached an updated certificate that's validated\. If you want to duplicate your certificate before deleting it, you can choose **Duplicate** from the same shortcut menu in step 5, below\. 6 | 7 | **Important** 8 | If the certificate you're deleting is valid and in use, your load balancer will no longer be able to handle encrypted \(HTTPS\) traffic\. Your Lightsail load balancer will still support unencrypted \(HTTP\) traffic\. 9 | Deleting an SSL/TLS certificate is final and can't be undone\. You have a quota of certificates you can create over a 365\-day period\. For more information, see [Quotas](http://docs.aws.amazon.com/acm/latest/userguide/acm-limits.html) in the AWS Certificate Manager User Guide\. 10 | 11 | 1. On the Lightsail home page, choose **Networking**\. 12 | 13 | 1. Choose the load balancer where your SSL/TLS certificate is attached\. 14 | 15 | 1. Choose the **Inbound traffic** tab on your load balancer's management page\. 16 | 17 | 1. In the **Certificates** section of the page, choose the ellipsis icon \(⋮\) for the certificate that you want to delete, and choose **Delete**\. 18 | 19 | The **Delete** option is unavailable if the certificate you want to delete is in use\. To delete certificates that are in use, you need to first change the certificate of the load balancer that is using the certificate, or disable HTTPS on the load balancer that is using the certificate\. -------------------------------------------------------------------------------- /doc_source/create-block-storage-disk-snapshot.md: -------------------------------------------------------------------------------- 1 | # Creating a snapshot of your block storage disk in Amazon Lightsail 2 | 3 | *Last updated: November 14, 2017* 4 | 5 | You can create disk snapshots in Lightsail as backups of your additional block storage disks\. 6 | 7 | You can use the snapshot of a disk as a baseline for new disks or for data backup\. If you make periodic snapshots of a disk, the snapshots are incremental\. Only the blocks on the device that have changed after your last snapshot are saved in the new snapshot\. Even though snapshots are saved incrementally, the snapshot deletion process is designed so that you need to retain only the most recent snapshot to restore the entire disk\. 8 | 9 | For more information, see [Snapshots in Amazon Lightsail](understanding-instance-snapshots-in-amazon-lightsail.md)\. 10 | 11 | 1. On the Lightsail home page, choose the **Storage** tab\. 12 | 13 | 1. Choose the name of the block storage disk for which you want to create a snapshot\. 14 | 15 | 1. Choose the **Snapshots** tab\. 16 | 17 | 1. Under the **Manual snapshots** section of the page, choose **Create snapshot**, then enter a name for your snapshot\. 18 | 19 | Resource names: 20 | + Must be unique within each AWS Region in your Lightsail account\. 21 | + Must contain 2 to 255 characters\. 22 | + Must start and end with an alphanumeric character or number\. 23 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 24 | 25 | 1. Choose **Create**\. 26 | 27 | You can see the snapshot you just created with a status of **Snapshotting\.\.\.**\. 28 | 29 | After the snapshot is finished, you can [create another disk from the snapshot](create-new-block-storage-disk-from-snapshot.md)\. -------------------------------------------------------------------------------- /doc_source/security.md: -------------------------------------------------------------------------------- 1 | # Security in Amazon Lightsail 2 | 3 | *Last updated: January 31, 2022* 4 | 5 | Cloud security at AWS is the highest priority\. As an AWS customer, you benefit from a data center and network architecture that is built to meet the requirements of the most security\-sensitive organizations\. 6 | 7 | Security is a shared responsibility between AWS and you\. The [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) describes this as security *of* the cloud and security *in* the cloud: 8 | + **Security of the cloud** – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud\. AWS also provides you with services that you can use securely\. To learn about the compliance programs, and which services they apply to, see [AWS Services in Scope by Compliance Program](https://aws.amazon.com/compliance/services-in-scope/)\. 9 | + **Security in the cloud** – Your responsibility is determined by the AWS service that you use\. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations\. 10 | 11 | This documentation helps you understand how to apply the shared responsibility model when using Lightsail\. The following topics show you how to configure Lightsail to meet your security and compliance objectives\. You also learn how to use other AWS services that help you to monitor and secure your Lightsail resources\. 12 | 13 | **Topics** 14 | + [Identity and Access Management for Amazon Lightsail](security_iam.md) 15 | + [Compliance Validation for Amazon Lightsail](amazon-lightsail-compliance.md) 16 | + [Resilience in Amazon Lightsail](disaster-recovery-resiliency.md) 17 | + [Infrastructure Security in Amazon Lightsail](infrastructure-security.md) -------------------------------------------------------------------------------- /doc_source/detach-and-delete-block-storage-disks.md: -------------------------------------------------------------------------------- 1 | # Detach and delete a block storage disk in Lightsail 2 | 3 | *Last updated: November 14, 2017* 4 | 5 | If you no longer need a block storage disk, you can detach it from your stopped Lightsail instance, and then delete it\. This topic describes how to back up your data and safely delete a disk\. 6 | 7 | ## Prerequisites 8 | + Stop your instance from running\. You have to do this before you can detach and then delete your disk\. [Learn how to stop your instance](lightsail-how-to-start-stop-or-restart-your-instance-virtual-private-server.md) 9 | + \(Optional\) We recommend that you create a snapshot of your disk\. That way, you have a backup in case you change your mind\. For more information, see [Creating a snapshot of your database in Amazon Lightsail](create-block-storage-disk-snapshot.md) 10 | 11 | ## Detach and delete your disk 12 | 13 | Once you stop your Lightsail instance, you can safely detach and delete your disk\. 14 | 15 | 1. On the home page, choose **Storage**\. 16 | 17 | 1. Choose the name of your attached disk to manage it\. 18 | ![\[Example of a block storage disk that is still attached to a Lightsail instance\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/example-disk-still-attached-home-page-storage-tab.png) 19 | 20 | 21 | 22 | 1. On the disk management page, choose **Detach**\. 23 | 24 | After a few seconds, the disk is detached and ready to be deleted or reattached\. 25 | 26 | 1. Choose the **Delete** tab\. 27 | 28 | 1. Choose **Delete disk**, and then confirm by choosing **Yes, delete**\. 29 | **Important** 30 | This is a permanent operation and can't be undone\. You will lose all data on the disk when you delete it\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-deleting-your-database.md: -------------------------------------------------------------------------------- 1 | # Deleting your database in Amazon Lightsail 2 | 3 | *Last updated: March 15, 2019* 4 | 5 | Delete your managed database in Amazon Lightsail if you no longer need it\. You stop incurring charges for the database as soon as it’s deleted\. 6 | 7 | **Note** 8 | You can’t recover a deleted database\. You can create a final snapshot of your database as part of the steps covered in this guide, or you can create a snapshot separately from the deletion process\. For more information, see [Creating a snapshot of your database in Amazon Lightsail](amazon-lightsail-creating-a-database-snapshot.md)\. 9 | 10 | **To delete your database** 11 | 12 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 13 | 14 | 1. On the Lightsail home page, choose the **Databases** tab\. 15 | 16 | 1. Choose the name of the database that you want to delete\. 17 | 18 | 1. Choose the **Delete** tab\. 19 | 20 | 1. Add a checkmark next to **Create snapshot before deletion** to create a final snapshot before deleting the database\. Then enter a name for your snapshot\. 21 | 22 | Resource names: 23 | + Must be unique within each AWS Region in your Lightsail account\. 24 | + Must contain 2 to 255 characters\. 25 | + Must start and end with an alphanumeric character or number\. 26 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 27 | 28 | 1. Choose **Delete database**\. 29 | 30 | 1. Choose **Yes, delete** to confirm the deletion\. 31 | ![\[Creating a database snapshot before deleting a database\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-delete-database-with-snapshot.png) 32 | 33 | If you opted to create a snapshot before deleting, you can view it on the **Snapshots** tab of the Lightsail home page\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-deleting-snapshots.md: -------------------------------------------------------------------------------- 1 | # Deleting snapshots in Amazon Lightsail 2 | 3 | *Last updated: July 8, 2019* 4 | 5 | Delete instance, database, and disk snapshots in Amazon Lightsail if you no longer need them to avoid incurring a monthly charge\. 6 | 7 | **Delete an individual snapshot** 8 | 9 | 1. On the [Lightsail console](https://lightsail.aws.amazon.com/), choose **Snapshots** tab\. 10 | 11 | 1. Find the Lightsail resource whose snapshot you want to delete, and choose the right\-arrow to expand the list of of available snapshots for that resource\. 12 | 13 | 1. Choose the actions menu icon \(⋮\) next to the snapshot you want to delete, and choose **Delete snapshot**\. 14 | ![\[Delete a snapshot in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-delete-snapshot-menu-option.png) 15 | 16 | 1. Choose **Yes** to confirm that you want to delete the snapshot\. 17 | **Important** 18 | This is a permanent operation and can't be undone\. You will lose all data on the snapshot when you delete it\. 19 | 20 | **Delete multiple snapshots** 21 | 22 | 1. From the Lightsail home page, choose **Snapshots**\. 23 | 24 | 1. Find the Lightsail resource whose snapshots you want to delete, and choose the right\-arrow to expand the list of snapshots\. 25 | ![\[Use the shortcut menu to show your disk snapshots and delete multiple disk snapshots\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/animated-gif-delete-disk-snapshot-multiple.gif) 26 | 27 | 1. Choose **Delete multiple**\. 28 | 29 | 1. Choose the snapshots you want to delete, and choose **Delete**\. 30 | 31 | 1. Choose **Yes** to confirm that you want to delete the snapshots\. 32 | **Important** 33 | This is a permanent operation and can't be undone\. You will lose all data on the snapshots when you delete them\. -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-ssh-connect-to-instance-virtual-private-server-using-putty.md: -------------------------------------------------------------------------------- 1 | # Connect to your Linux/Unix\-based Lightsail instance using PuTTY 2 | 3 | *Last updated: September 4, 2020* 4 | 5 | In addition to the browser\-based SSH terminal in Lightsail, you can also connect to your Linux\-based instance using an SSH client such as PuTTY\. To learn how to set up PuTTY, see [Download and set up PuTTY to connect using SSH in Lightsail](lightsail-how-to-set-up-putty-to-connect-using-ssh.md)\. 6 | 7 | **Note** 8 | To connect to a Windows\-based instance using RDP, see [Connect to your Windows\-based Lightsail instance](connect-to-your-windows-based-instance-using-amazon-lightsail.md)\. 9 | 10 | You can use the default private key that Lightsail provides, a new private key from Lightsail, or another private key that you use with another service\. 11 | 12 | 1. Start PuTTY \(for example, from the **Start** menu, choose **All Programs**, **PuTTY**, **PuTTY**\)\. 13 | 14 | 1. Choose **Load**, and then find your saved session\. 15 | 16 | If you don't have a saved session, see [Step 4: Finish configuring PuTTY with your private key and instance information](lightsail-how-to-set-up-putty-to-connect-using-ssh.md)\. 17 | 18 | 1. Log in using one of the following default user names depending on your instance operating system: 19 | + Amazon Linux, Amazon Linux 2, FreeBSD, and openSUSE instances: `ec2-user` 20 | + CentOS instances: `centos` 21 | + Debian instances: `admin` 22 | + Ubuntu instances: `ubuntu` 23 | + Bitnami instances: `bitnami` 24 | + Plesk instances: `ubuntu` 25 | + cPanel & WHM instances: `centos` 26 | 27 | For more information about instance operating systems, see [Choosing an image in Lightsail](compare-options-choose-lightsail-instance-image.md)\. 28 | 29 | To learn more about SSH, see [SSH and connecting to your Amazon Lightsail instance](understanding-ssh-in-amazon-lightsail.md)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-importing-data-into-your-mysql-database.md: -------------------------------------------------------------------------------- 1 | # Importing data into your MySQL database in Amazon Lightsail 2 | 3 | *Last updated: March 15, 2019* 4 | 5 | You can import a SQL file \(\.SQL\) into your MySQL managed database in Amazon Lightsail using MySQL Workbench\. 6 | 7 | **Note** 8 | To learn how to connect MySQL Workbench to your database, see [Connecting to your MySQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-mysql-database.md)\. 9 | 10 | **To import data into your database** 11 | 12 | 1. Open MySQL Workbench\. 13 | 14 | 1. In the list of MySQL Connections, choose your MySQL managed database in Amazon Lightsail\. 15 | 16 | 1. Choose **Data Import/Restore** from the left\-navigation menu\. 17 | 18 | 1. In the Data Import pane, choose **Import from Self\-Contained File** under the **Import Options** section\. 19 | ![\[Importing a self-contained .SQL file\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-import-from-self-contained-file.png) 20 | 21 | 1. Choose the ellipsis button to browse your local drive for the \.SQL file that you want to import\. 22 | 23 | 1. Choose the \.SQL file to import, then choose **Open**\. 24 | 25 | 1. Choose the **Default Target Schema** drop\-down menu, then select the existing database to import the file to\. You can also create a new database by choosing **New**\. 26 | ![\[Choosing a default target schema\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-default-schema-to-import-to.png) 27 | 28 | 1. Choose **Start Import** to start the import\. 29 | 30 | Your import may take a few minutes or more depending on the size of the \.SQL file\. After the import is complete, you should see a message similar to the following: 31 | ![\[Import completed\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-import-finished.png) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-download-ssl-certificate-for-managed-database.md: -------------------------------------------------------------------------------- 1 | # Download an SSL certificate for your managed database in Amazon Lightsail 2 | 3 | *Last updated: April 10, 2023* 4 | 5 | You can use Secure Socket Layer \(SSL\) or Transport Layer Security \(TLS\) from your application to encrypt a connection to a managed database in Amazon Lightsail running MySQL, or PostgreSQL\. Each DB engine has its own process for implementing SSL/TLS\. For more information, see [Using SSL to connect to your MySQL database in Amazon Lightsail](amazon-lightsail-connecting-to-mysql-database-using-ssl.md) or [Using SSL to connect to your PostgreSQL database in Amazon Lightsail](amazon-lightsail-connecting-to-postgres-database-using-ssl.md)\. 6 | 7 | **Note** 8 | The certificates available for download are labeled for Amazon Relational Database Service \(Amazon RDS\), but also work for managed databases in Lightsail\. 9 | 10 | ## Certificate bundles for all AWS Regions 11 | 12 | To get a certificate bundle that contains both the intermediate and root certificates for all AWS Regions, or if your application is on Microsoft Windows and requires a PKCS7 file, see [Certificate bundles for all AWS Regions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions) in the Amazon Relational Database Service User Guide\. 13 | 14 | This root certificate is a trusted root entity and should work in most cases\. However, it might fail if your application doesn't accept certificate chains\. If your application doesn't accept certificate chains, continue to the next section of this document\. 15 | 16 | ## Certificate bundles for specific AWS Regions 17 | 18 | To get a certificate bundle that contains both the intermediate and root certificates for a specific AWS Region, see [Certificate bundles for specific AWS Regions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.RegionCertificates) in the Amazon Relational Database Service User Guide\. -------------------------------------------------------------------------------- /doc_source/troubleshoot-ghost-instance-service-unavailable.md: -------------------------------------------------------------------------------- 1 | # Troubleshooting the 503 service unavailable error for a Ghost instance in Amazon Lightsail 2 | 3 | *Last updated: March 27, 2020* 4 | 5 | After you create a new Ghost instance in Amazon Lightsail, and try to access your website, you might see an error stating that the service is unavailable \(503\)\. In some cases, the Ghost service on the instance is not automatically started when the instance is created\. This can happen when you select the $3\.50 USD/month bundle for your instance\. Use the following procedure to start the Ghost service, and resolve the "service is unavailable" error\. 6 | 7 | ## Starting the Ghost service 8 | 9 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 10 | 11 | 1. On the Lightsail home page, choose the **Instances** tab\. 12 | 13 | 1. Choose the browser\-based SSH client icon for your Ghost instance\. 14 | ![\[Browser-based SSH client in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-ghost-quick-connect.png) 15 | 16 | 1. After the SSH client is connected, enter the following command to restart all services on the instance: 17 | 18 | ``` 19 | sudo /opt/bitnami/ctlscript.sh restart 20 | ``` 21 | 22 | You should see a result similar to the following example: 23 | ![\[Ghost service restarted.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-restart-ghost-services.png) 24 | 25 | 1. Browse to the public IP address of your instance to confirm that your Ghost website is up and running\. 26 | 27 | The public IP address of your instance is listed next to the instance name in the **Instances** tab of the Lightsail console\. 28 | ![\[Instance public IP address.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-ghost-public-ip.png) 29 | 30 | When you browse to the public IP of your new Ghost instance, you should see the default Ghost website template: 31 | ![\[Ghost default website template.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-ghost-website.png) -------------------------------------------------------------------------------- /doc_source/troubleshooting-lightsail-load-balancer-issues.md: -------------------------------------------------------------------------------- 1 | # Troubleshooting Lightsail load balancer issues 2 | 3 | *Last updated: November 29, 2017* 4 | 5 | You might encounter errors with your Lightsail load balancers\. This topic identifies common issues and workarounds for those errors\. 6 | 7 | ## General load balancer errors 8 | 9 | Choose the issue below that best describes your problem, and follow the links to fix the issue\. If you encounter an issue that's not in the list, use the **Questions? Comments?** link at the bottom of this page to submit feedback or contact AWS Customer Support\. 10 | 11 | **I can't create a certificate\.** 12 | There is a quota to the number of certificates you can create in an AWS account\. For more information, see [Quotas](http://docs.aws.amazon.com/acm/latest/userguide/acm-limits.html) in the AWS Certificate Manager User Guide\. The same quota apply to Lightsail certificates for load balancers\. 13 | *Actual error message:*  **Sorry, you've requested too many certificates for your account\.** 14 | 15 | **I can't attach any more instances to my load balancer\.** 16 | You can attach as many Lightsail instances as you like to your load balancer, as long as you stay within the quota of 20 total Lightsail instances per AWS account\. 17 | *Actual error message:*  **Sorry, you've reached the maximum number of instances you can attach to this load balancer\.** 18 | 19 | **I can't attach a specific instance to my load balancer\.** 20 | First, check to make sure your Lightsail instance is running\. If it is stopped, you can start it from the instance management page\. Lightsail instances must be running to be successfully attached to a load balancer\. 21 | It could be that you have attached the same instance to too many load balancers\. 22 | *Actual error message:*  **Sorry, you've reached the maximum number of times an instance can be registered with a load balancer\.** 23 | 24 | **Lightsail can't find the instance I'm trying to attach to my load balancer** 25 | You might be trying to attach an instance that no longer exists or is not in the same VPC as the target group\. 26 | *Actual error message:*  **Sorry, the instance you specified doesn't exist, isn't in the same VPC as the target group, or has an unsupported instance type\.** -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-set-up-vpc-peering-with-aws-resources.md: -------------------------------------------------------------------------------- 1 | # Set up Amazon VPC peering to work with AWS resources outside of Amazon Lightsail 2 | 3 | *Last updated: January 29, 2021* 4 | 5 | Lightsail lets you connect to AWS resources, such as an Amazon RDS database, through virtual private cloud \(VPC\) peering\. A VPC is a virtual network dedicated to your AWS account\. Everything you create inside Lightsail is inside a VPC, and you can connect your Lightsail VPC to an Amazon VPC\. 6 | 7 | Some AWS resources, such as Amazon S3, Amazon CloudFront, and Amazon DynamoDB don't require VPC peering to be enabled\. 8 | 9 | **Note** 10 | To enable VPC peering in Lightsail, you need to have a default Amazon VPC\. If you don’t have a default Amazon VPC, you can create one\. To learn more, see [Creating a Default VPC ](https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html#create-default-vpc) in the *Amazon VPC User Guide*\. 11 | Since AWS Regions are isolated from one another, a VPC is also isolated in the region where you created it\. You'll need to enable VPC peering in each region where you have Lightsail resources\. 12 | 13 | Once you have a default Amazon VPC, follow these instructions to peer your Lightsail VPC with your Amazon VPC\. 14 | 15 | 1. In the [Lightsail console](https://lightsail.aws.amazon.com/), choose **Account** on the top navigation menu\. 16 | 17 | 1. Choose **Account** from the drop\-down\. 18 | 19 | 1. Choose the **Advanced** tab\. 20 | 21 | 1. Choose **Enable VPC peering** under the AWS Region where you want to enable it\. 22 | ![\[Enable VPC peering on the Account page\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-enable-vpc-peering.png) 23 | 24 | If the peering connection fails, try to enable VPC peering again\. If it doesn't work, contact [AWS Customer Support](https://console.aws.amazon.com/support/home/)\. 25 | 26 | A peering connection is created in your AWS account if the peering request is successful\. Go to the [Amazon VPC Dashboard](https://console.aws.amazon.com/vpc/home#PeeringConnections) and choose **Peering Connections** in the navigation pane to view the peering connection that is created\. 27 | 28 | For more information about Amazon VPC, see [Your VPC and Subnets](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html) in the *Amazon VPC User Guide*\. -------------------------------------------------------------------------------- /doc_source/add-alternate-domain-names-to-tls-ssl-certificate-https.md: -------------------------------------------------------------------------------- 1 | # Add alternate domains and subdomains to your SSL/TLS certificate in Lightsail 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | When you create your SSL/TLS certificate for your Lightsail load balancer, you can add alternate domains and subdomains to it\. These alternate names help ensure that all traffic to your load balancer is encrypted\. 6 | 7 | When you specify a primary domain, you can use a fully qualified domain name such as `www.example.com` or an apex domain name such as `example.com`\. 8 | 9 | The total number of domains and subdomains must not exceed 10, so you can add up to 9 alternate domains and subdomains to your certificate\. You might want to add entries similar to the following list\. 10 | + example\.com 11 | + example\.net 12 | + blog\.example\.com 13 | + myexamples\.com 14 | 15 | ## To create a certificate with alternate domains and subdomains 16 | 17 | 1. If you don't have one yet, [create a Lightsail load balancer](create-lightsail-load-balancer-and-attach-lightsail-instances.md)\. 18 | 19 | 1. On the Lightsail home page, choose the **Networking** tab\. 20 | 21 | 1. Choose your Lightsail load balancer\. 22 | 23 | 1. Choose the **Custom domains** tab\. 24 | 25 | 1. Choose **Create certificate**\. 26 | 27 | 1. Enter a name for your certificate or accept the default name\. 28 | 29 | Resource names: 30 | + Must be unique within each AWS Region in your Lightsail account\. 31 | + Must contain 2 to 255 characters\. 32 | + Must start and end with an alphanumeric character or number\. 33 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 34 | 35 | 1. Enter your primary domain \(`www.example.com`\), and up to 9 alternate domains or subdomains\. 36 | 37 | 1. Choose **Create certificate**\. 38 | 39 | Once created, you have 72 hours to verify that you own your domain\. 40 | 41 | ## Next steps 42 | + [Verify domain ownership using DNS](verify-tls-ssl-certificate-using-dns-cname-https.md) 43 | 44 | Once verified, you can select your validated certificate to associate it with your Lightsail load balancer\. 45 | + [Enable session persistence](update-settings-for-lightsail-load-balancer-health-check-path-https-session-stickiness-persistence-cookie-duration.md) -------------------------------------------------------------------------------- /doc_source/creating-resources-with-cloudformation.md: -------------------------------------------------------------------------------- 1 | # Creating Amazon Lightsail resources with AWS CloudFormation 2 | 3 | *Last updated: October 12, 2021* 4 | 5 | Amazon Lightsail is integrated with AWS CloudFormation, a service that helps you to model and set up your AWS resources so that you can spend less time creating and managing your resources and infrastructure\. You create a template that describes all the AWS resources that you want \(such as instances and disks\), and AWS CloudFormation provisions and configures those resources for you\. 6 | 7 | When you use CloudFormation, you can reuse your template to set up your Lightsail resources consistently and repeatedly\. Describe your resources once, and then provision the same resources over and over in multiple AWS accounts and Regions\. 8 | 9 | ## Lightsail and AWS CloudFormation templates 10 | 11 | To provision and configure resources for Lightsail and related services, you must understand [AWS CloudFormation templates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-guide.html)\. Templates are formatted text files in JSON or YAML\. These templates describe the resources that you want to provision in your AWS CloudFormation stacks\. If you're unfamiliar with JSON or YAML, you can use AWS CloudFormation Designer to help you get started with AWS CloudFormation templates\. For more information, see [What is AWS CloudFormation Designer?](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/working-with-templates-cfn-designer.html) in the *AWS CloudFormation User Guide*\. 12 | 13 | Lightsail supports creating instances and disks in AWS CloudFormation\. For more information, see the [Lightsail resource type reference](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Lightsail.html) in the *AWS CloudFormation User Guide*\. 14 | 15 | ## Learn more about AWS CloudFormation 16 | 17 | To learn more about AWS CloudFormation, see the following resources: 18 | + [AWS CloudFormation](https://aws.amazon.com/cloudformation/) 19 | + [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html) 20 | + [AWS CloudFormation API Reference](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/Welcome.html) 21 | + [AWS CloudFormation Command Line Interface User Guide](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/what-is-cloudformation-cli.html) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-edit-or-delete-a-dns-zone.md: -------------------------------------------------------------------------------- 1 | # Edit or delete a DNS zone in Lightsail 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | You can add, edit, or delete the DNS records in your domain's DNS zone\. You can also delete your domain's DNS zone in Amazon Lightsail if you want to transfer management of your domain's DNS records to another DNS hosting provider or back to the registrar where you registered your domain\. 6 | 7 | **Note** 8 | Before you can edit records using the DNS editor in the Lightsail console, you must transfer management of your domain's DNS records to Lightsail\. For more information, see [Creating a DNS zone to manage your domain’s DNS records in Amazon Lightsail](lightsail-how-to-create-dns-entry.md)\. 9 | 10 | ## Edit DNS records for a DNS zone in Lightsail 11 | 12 | You can edit the DNS records for your domain's DNS zone at any time using the Lightsail console\. 13 | 14 | **To edit the DNS zone** 15 | 16 | 1. Sign in to the Lightsail console\. 17 | 18 | 1. Choose the **Domains & DNS** tab, and then choose the name of the DNS zone you want to edit\. 19 | 20 | 1. On the DNS zone **DNS records** page, choose one of the following options: 21 | + To add a new record, choose **Add record**\. 22 | + To edit an existing record, choose the **Edit** icon next to the record you want to edit\. 23 | + To delete an existing record, choose the **Delete** icon next to the record you want to delete\. 24 | 25 | 1. When you're done, choose the **Save** icon to save your changes\. 26 | **Note** 27 | Allow time for the DNS record changes to propagate through the internet's DNS, which may take several hours\. 28 | 29 | ## Delete a DNS zone in Lightsail 30 | 31 | You can delete your domain's DNS zone in Lightsail\. 32 | 33 | **Important** 34 | If you plan to continue routing traffic through your domain, prepare a different DNS hosting provider before deleting your domain's DNS zone in Lightsail\. Otherwise, all traffic to your website stops when you delete the Lightsail DNS zone\. 35 | 36 | **To delete a DNS zone** 37 | 38 | 1. On the Lightsail console home page, choose the **Domains & DNS** tab\. 39 | 40 | 1. Choose the name of the DNS zone you want to delete\. 41 | 42 | 1. Choose the vertical ellipsis menu \(⋮\)\. Then, choose the **Delete** option\. 43 | 44 | 1. Choose **Delete DNS zone** to confirm the deletion\. 45 | 46 | The DNS zone is deleted from Lightsail\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-deleting-health-metric-alarms.md: -------------------------------------------------------------------------------- 1 | # Deleting or disabling metric alarms in Amazon Lightsail 2 | 3 | *Last updated: February 27, 2020* 4 | 5 | You can delete an Amazon Lightsail alarm to stop notifications of when the metric being monitored by the alarm crosses a threshold\. You can also disable the alarm to stop receiving notifications\. For more information, see [Alarms in Amazon Lightsail](amazon-lightsail-alarms.md)\. 6 | 7 | **Contents** 8 | + [Deleting metric alarms using the Lightsail console](#deleting-alarms) 9 | + [Disabling and enabling metric alarms using the Lightsail console](#disable-alarms) 10 | 11 | ## Deleting metric alarms using the Lightsail console 12 | 13 | Complete the following steps to delete a metric alarm using the Lightsail console\. 14 | 15 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 16 | 17 | 1. On the Lightsail home page, choose the **Instances**, **Databases**, or **Networking** tab\. 18 | 19 | 1. Choose the name of the resource \(instance, database, or load balancer\) for which you want to delete an alarm\. 20 | 21 | 1. Choose the **Metrics** tab on the resource’s management page\. 22 | 23 | 1. Choose the metric for which you want to delete an alarm in the drop\-down under the **Metrics Graphs** heading\. 24 | 25 | 1. Scroll down to the **Alarms** section of the page, and choose the ellipsis icon \(⋮\) next to the alarm you want to delete\. 26 | 27 | 1. Choose **Delete**\. 28 | 29 | 1. At the prompt, choose **Delete** to confirm that you want to delete the alarm\. 30 | 31 | ## Disabling and enabling metric alarms using the Lightsail console 32 | 33 | Complete the following steps to disable a metric alarm using the Lightsail console\. 34 | 35 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 36 | 37 | 1. On the Lightsail home page, choose the **Instances**, **Databases**, or **Networking** tab\. 38 | 39 | 1. Choose the name of the resource \(instance, database, or load balancer\) for which you want to disable an alarm\. 40 | 41 | 1. Choose the **Metrics** tab on the resource’s management page\. 42 | 43 | 1. Choose the metric for which you want to disable an alarm in the drop\-down under the **Metrics Graphs** heading\. 44 | 45 | 1. Scroll down to the **Alarms** section of the page, locate the alarm you want to disable, and choose the toggle to disable it\. Likewise, choose the toggle to enable it if it's disabled\. -------------------------------------------------------------------------------- /doc_source/create-tls-ssl-certificate-and-attach-to-lightsail-load-balancer-https.md: -------------------------------------------------------------------------------- 1 | # Create an SSL/TLS certificate for your Lightsail load balancer 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | After you create a Lightsail load balancer, you can attach a Transport Layer Security \(TLS\) certificate to enable HTTPS\. The SSL/TLS certificate lets your load balancer handle encrypted web traffic so that you can provide a more secure experience for your users\. To learn more, see [SSL/TLS certificates in Amazon Lightsail](understanding-tls-ssl-certificates-in-lightsail-https.md)\. 6 | 7 | ## Prerequisites 8 | 9 | Before you get started, you will need the following\. 10 | + A Lightsail load balancer\. To learn more, see [Create a Lightsail load balancer](create-lightsail-load-balancer-and-attach-lightsail-instances.md)\. 11 | 12 | ## Create the certificate request 13 | 14 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 15 | 16 | 1. On the Lightsail home page, choose **Networking**\. 17 | 18 | 1. Choose the name of the load balancer for which you want to configure an SSL/TLS certificate\. 19 | 20 | 1. Choose the **Custom domains** tab\. 21 | 22 | 1. Choose **Create certificate**\. 23 | 24 | 1. Enter a name for your certificate or accept the default\. 25 | 26 | Resource names: 27 | + Must be unique within each AWS Region in your Lightsail account\. 28 | + Must contain 2 to 255 characters\. 29 | + Must start and end with an alphanumeric character or number\. 30 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 31 | 32 | 1. Enter your primary domain \(`www.example.com`\), and up to 9 alternate domains or subdomains\. 33 | 34 | For more information, see [Add alternate domains and subdomains to your SSL/TLS certificate](add-alternate-domain-names-to-tls-ssl-certificate-https.md) 35 | 36 | 1. Choose **Create certificate**\. 37 | 38 | Lightsail begins the validation process\. You have 72 hours to verify that you own your domain\. 39 | 40 | After you create your certificate, you see the certificate along with the domain name and all your alternate domains and subdomains\. You need to create a DNS record for each domain and subdomain\. 41 | 42 | ## Next step 43 | + [Verify that you own your domain](verify-tls-ssl-certificate-using-dns-cname-https.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-importing-data-into-your-postgres-database.md: -------------------------------------------------------------------------------- 1 | # Importing data into your PostgreSQL database in Amazon Lightsail 2 | 3 | *Last updated: March 15, 2019* 4 | 5 | You can import a database backup file into your PostgreSQL managed database in Amazon Lightsail using pgAdmin\. 6 | 7 | **Note** 8 | To learn how to connect pgAdmin to your database, see [Connecting to your PostgreSQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-postgres-database.md)\. For more information about creating a PostgreSQL database backup that you can import to another database, see [Backup Dialog](https://www.pgadmin.org/docs/pgadmin4/dev/backup_dialog.html) in the pgAdmin documentation\. 9 | 10 | **To import a backup file into your database** 11 | 12 | 1. Open pgAdmin\. 13 | 14 | 1. In the list of server connections, double\-click your PostgreSQL managed database in Amazon Lightsail to connect to it\. 15 | 16 | 1. Expand the **Databases** node 17 | 18 | 1. Right\-click the database in which you would like to import data from a database backup file, then choose **Restore**\. 19 | ![\[Restoring a database in pgAdmin.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-pgadmin-restore-database.png) 20 | 21 | 1. In the **Restore** form, complete the following fields: 22 | + **Format** — Choose the format of your backup file\. 23 | + **Filename** — Choose the ellipsis icon, then locate and choose the database backup file on your local drive\. After the file is highlighted, choose **Select** to go back to the **Restore** prompt\. 24 | **Note** 25 | Choose the **Format** drop\-down menu, and select **All files** to view all file formats on your local drive\. Your backup file might be saved as a file type that is different than what is selected by default \(sql\)\. 26 | ![\[Importing a backup file.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-pgadmin-restore-backup-select-file.png) 27 | + **Number of jobs** and **Role name** — Leave these fields blank\. 28 | 29 | 1. Choose **Restore** to start the import\. 30 | 31 | Your import may take a few minutes or more depending on the size of the database backup file\. After the import is complete, you should see a message similar to the following: 32 | ![\[Successful restore of PostgreSQL database backup file.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-pgadmin-successful-restore.png) -------------------------------------------------------------------------------- /doc_source/use-non-default-key-with-windows-based-instance-in-lightsail.md: -------------------------------------------------------------------------------- 1 | # Using the non\-default key with Windows\-based Lightsail instances 2 | 3 | *Last updated: October 16, 2017* 4 | 5 | When you create a Windows Server\-based Lightsail instance, we use the default password for the AWS Region where we create the instance\. This makes it easier to connect using the browser\-based remote desktop \(RDP\) client, as well as a client such as Remote Desktop Connection\. 6 | 7 | **Important** 8 | We strongly encourage you to let Lightsail generate the password for your instance\. Since we don't store your custom password, you can risk losing access to your Lightsail instance if you change the Administrator password\. 9 | 10 | ## Changing your Administrator password using Windows Server 11 | 12 | You can change your Administrator password using the Windows Server **Change Password** tool\. Type `Ctrl` \+ `Alt` \+ `Del` on your Windows Server\-based Lightsail instance, and then choose **Change a password**\. 13 | 14 | ## Decrypt your key 15 | 16 | If you change your password on your Windows Server\-based Lightsail instance, you can use the AWS Command Line Interface \(AWS CLI\) to get information that helps you decrypt your password\. 17 | 18 | **Get your ciphertext using the AWS CLI** 19 | 20 | 1. If you haven't done so already, install and configure the AWS CLI\. 21 | 22 | For more information, see [Configuring the AWS Command Line Interface to work with Amazon Lightsail](lightsail-how-to-set-up-and-configure-aws-cli.md)\. 23 | 24 | 1. Open a command prompt or a terminal\. 25 | 26 | 1. Type the following command\. 27 | 28 | ``` 29 | aws lightsail get-instance-access-details --instance-name my-instance 30 | ``` 31 | 32 | Where *my\-instance* is the name of the instance you want to get information about\. 33 | 34 | You'll see output similar to the following\. 35 | 36 | ``` 37 | { 38 | "accessDetails": { 39 | "username": "Administrator", 40 | "protocol": "rdp", 41 | "ipAddress": "12.345.678.910", 42 | "passwordData": { 43 | "ciphertext": "cipher", 44 | "keyPairName": "my-ohio-key" 45 | }, 46 | "password": "", 47 | "instanceName": "2016-ohio-windows" 48 | } 49 | } 50 | ``` 51 | 52 | 1. You can use the ciphertext with any available application to decrypt your password\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-creating-a-database-snapshot.md: -------------------------------------------------------------------------------- 1 | # Creating a snapshot of your database in Amazon Lightsail 2 | 3 | *Last updated: March 15, 2019* 4 | 5 | You can create a snapshot of your managed database in Amazon Lightsail\. A snapshot is a copy of your database that you can use to restore it if something goes wrong\. You can also use a snapshot to create a new database using a different plan, such as a high availability or standard plan\. 6 | 7 | When you create a snapshot of a standard database, the database becomes unavailable from a few seconds to a few minutes, depending on the size\. High availability databases are not affected by snapshot operations because the snapshot is created using the standby database\. 8 | 9 | **To create a snapshot of your database** 10 | 11 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 12 | 13 | 1. On the Lightsail home page, choose the **Databases** tab\. 14 | 15 | 1. Choose the name of the database for which you want to create a snapshot\. 16 | 17 | 1. Choose the **Snapshots & restore** tab\. 18 | 19 | 1. Under the **Manual snapshots** section of the page, choose **Create snapshot**, then enter a name for your snapshot\. 20 | 21 | Resource names: 22 | + Must be unique within each AWS Region in your Lightsail account\. 23 | + Must contain 2 to 255 characters\. 24 | + Must start and end with an alphanumeric character or number\. 25 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 26 | 27 | 1. Choose **Create**\. 28 | 29 | The snapshot creation process begins and a status of **Snapshot in progress** is shown\. 30 | ![\[Database snapshot in progress\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-database-snapshot-in-progress.png) 31 | 32 | After the snapshot creation process is complete, the new snapshot is listed under the **Recent snapshots** section\. You can also view all of the snapshots for your account in the Lightsail home page, under the **Snapshots** tab\. 33 | ![\[Recent database snapshots in the Lightsail console\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-database-recent-snapshots.png) 34 | 35 | ## Next steps 36 | 37 | After your snapshot is ready, you can create a new database from the snapshot, which is a duplicate of the original database\. For more information, see [Creating a database from a snapshot in Amazon Lightsail](amazon-lightsail-creating-a-database-from-snapshot.md)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-notifications.md: -------------------------------------------------------------------------------- 1 | # Notifications in Amazon Lightsail 2 | 3 | *Last updated: February 27, 2020* 4 | 5 | **Note** 6 | Configure Amazon Lightsail to notify you when a metric for one of your resources crosses a specified threshold\. You can be notified by a banner displayed in the Lightsail console, an email, or an SMS text message\. 7 | 8 | You can configure Lightsail to notify you when a metric for one of your instances, databases, load balancers, or content delivery network \(CDN\) distributions crosses a specified threshold\. Notifications can be in the form of a banner displayed in the Lightsail console, an email sent to an address you specify, or an SMS text message sent to a mobile phone number you specify\. 9 | 10 | To get notifications, you must configure an alarm that monitors a metric for one of your resources\. For example, you can configure an alarm that notifies you when your instance's outgoing network traffic is greater than 500 kilobytes during a specified length of time\. For more information, see [Alarms in Amazon Lightsail](amazon-lightsail-alarms.md)\. 11 | 12 | When an alarm is triggered, a notification banner is displayed in the Lightsail console\. To be notified by email and SMS text message, you must add your email address and mobile phone number as notification contacts in each AWS Region where you want to monitor your resources\. For more information, see [Adding notification contacts in Amazon Lightsail](amazon-lightsail-adding-editing-notification-contacts.md)\. 13 | 14 | **Note** 15 | SMS text messaging is not supported in all AWS Regions in which you can create Lightsail resources, and text messages cannot be sent to some countries and regions of the world\. For more information, see [Adding notification contacts in Amazon Lightsail](amazon-lightsail-adding-editing-notification-contacts.md)\. 16 | 17 | If don't receive notifications when you expect to be notified, then there are a few things you should check to confirm that your notification contacts are configured correctly\. To learn more, see [Troubleshooting notifications in Amazon Lightsail](amazon-lightsail-troubleshooting-notifications.md)\. 18 | 19 | To stop receiving notifications, you can remove your email and mobile phone from Lightsail\. For more information, see [Deleting or disabling metric alarms in Amazon Lightsail](amazon-lightsail-deleting-notification-contacts.md)\. You can also disable or delete an alarm to stop receiving notifications for a specific alarm\. For more information, see [Deleting or disabling metric alarms in Amazon Lightsail](amazon-lightsail-deleting-health-metric-alarms.md)\. -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-configure-server-additional-data-shell-script.md: -------------------------------------------------------------------------------- 1 | # Use a launch script to configure your Amazon Lightsail instance when it starts up 2 | 3 | *Last updated: October 16, 2017* 4 | 5 | When you create a Linux/Unix\-based instance, you can add a launch script that does things like add software, update software, or configure your instance in some other way\. To configure a Windows\-based instance with additional data, see [Configure your new Lightsail instance using Windows PowerShell](create-powershell-script-that-runs-when-you-create-windows-based-instance-in-lightsail.md)\. 6 | 7 | **Note** 8 | Depending on the machine image you choose, the command to get software on your instance varies\. Amazon Linux uses `yum`, while Debian and Ubuntu both use `apt-get`\. WordPress and other application images use `apt-get` because they run Ubuntu as their operating system\. FreeBSD and openSUSE require additional user configuration to use custom tools such as `freebsd-update` or `zypper` \(openSUSE\)\. 9 | 10 | ## Example: Configure an Ubuntu server to install Node\.js 11 | 12 | The following example updates the package list and then installs Node\.js through the `apt-get` command\. 13 | 14 | 1. On the **Create an instance** page, choose **Ubuntu** on the **OS Only** tab\. 15 | 16 | 1. Scroll down and choose **Add launch script**\. 17 | 18 | 1. Type the following: 19 | 20 | ``` 21 | # update package list 22 | apt-get –y update 23 | # install some of my favorite tools 24 | apt-get install –y nodejs 25 | ``` 26 | **Note** 27 | Commands you send to configure your server are run as root, so you don't need to include `sudo` before your commands\. 28 | 29 | 1. Choose **Create instance**\. 30 | 31 | ## Example: Configure a WordPress server to download and install a plugin 32 | 33 | The following example updates the package list, and then downloads and installs the [BuddyPress plugin](https://wordpress.org/plugins/buddypress/) for WordPress\. 34 | 35 | 1. On the **Create an instance** page, choose **WordPress**\. 36 | 37 | 1. Choose **Add launch script**\. 38 | 39 | 1. Type the following: 40 | 41 | ``` 42 | # update package list 43 | apt-get –y update 44 | # download wordpress plugin 45 | wget "https://downloads.wordpress.org/plugin/buddypress.2.7.0.zip" 46 | apt-get –y install unzip 47 | # unzip into wordpress plugin directory 48 | unzip buddypress.2.7.0.zip -d /var/wordpress/plugins 49 | ``` 50 | 51 | 1. Choose **Create instance**\. -------------------------------------------------------------------------------- /doc_source/update-settings-for-lightsail-load-balancer-health-check-path-https-session-stickiness-persistence-cookie-duration.md: -------------------------------------------------------------------------------- 1 | # Update the settings for your Lightsail load balancer 2 | 3 | *Last updated: November 29, 2017* 4 | 5 | When you create a Lightsail load balancer, you simply choose the AWS Region and the name\. This topic tells you how to update your load balancer to enable more options\. 6 | 7 | Of course, you'll need a Lightsail load balancer first\. [Learn how to create a Lightsail load balancer](create-lightsail-load-balancer-and-attach-lightsail-instances.md) 8 | 9 | ## Health checking 10 | 11 | The first thing you're going to want to do is [configure your Amazon Lightsail instances for load balancing](configure-lightsail-instances-for-load-balancing.md)\. Once that's done, you can attach an instance to your load balancer\. Attaching an instance starts the health checking process, and you get a **Passed** or **Failed** message on the load balancer management page\. 12 | 13 | ![\[Health check status indicator\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/target-instances-health-check-passed.png) 14 | 15 | You can also customize your health check path\. For example, if your home page loads slowly or has a lot of images on it, you can configure Lightsail to check a different page that loads faster\. [Learn more about customizing the health check path](enable-set-up-health-checking-for-lightsail-load-balancer-metrics.md) 16 | 17 | ## Encrypted traffic \(HTTPS\) 18 | 19 | You can set up HTTPS to create a more secure experience for your website users\. It's a three\-step process to create and validate an SSL/TLS certificate once you set up your load balancer\. 20 | 21 | [Learn more about HTTPS](understanding-tls-ssl-certificates-in-lightsail-https.md) 22 | 23 | ## Session persistence 24 | 25 | Session persistence is useful if you're storing session information locally in the user's browser\. For example, you might be running a Magento e\-commerce application with a shopping cart on Lightsail\. If you turn on session persistence, your users can add items to their shopping carts,end their sessions, and still find the items in their carts when they come back\. 26 | 27 | You can also adjust the cookie duration for the persistent session\. This is useful if you want to have a particularly long or short duration\. For more information, see [Enable session persistence for Amazon Lightsail load balancers](enable-session-stickiness-persistence-or-change-cookie-duration.md)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-deleting-tags.md: -------------------------------------------------------------------------------- 1 | # Deleting tags in Amazon Lightsail 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | You can delete tags from an Amazon Lightsail resource\. Deleting a tag from one resource does not delete the same tag from all other resources\. To completely delete a tag from all resources, you must remove that tag from each resource\. This guide provides the steps to delete tags from a resource\. 6 | 7 | **Note** 8 | For more information about tags, what resources can be tagged, and the tag restrictions, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 9 | 10 | **To delete tags from a resource** 11 | 12 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 13 | 14 | 1. On the Lightsail home page, choose the tab for the resource type that you want to delete tags from\. For example, to delete tags from a DNS zone, choose the **Networking** tab\. Or choose the **Instances** tab to delete tags from an instance\. 15 | **Note** 16 | Instances, container services, CDN distributions, buckets, databases, disks, DNS zones, and load balancers can be tagged using the Lightsail console\. However, more Lightsail resources can be tagged using the [Lightsail API operations](https://docs.aws.amazon.com/lightsail/2016-11-28/api-reference/Welcome.html), or the [AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/reference/lightsail/) \(AWS CLI\) or SDKs\. For a full list of Lightsail resources that support tagging, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 17 | 18 | 1. Choose the resource that you want to delete tags from\. 19 | 20 | 1. On the management page for the resource you selected, choose the **Tags** tab\. 21 | ![\[Tags tab in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-tags-tab.png) 22 | 23 | 1. Do one of the following, depending on the type of tag that you want to delete from the resource: 24 | 25 | 1. Choose **Edit key\-only tags**, then choose the delete icon \(X\) for the tag that you want to delete from the resource\. Choose **Save** when you’re done deleting tags to remove them from the resource, or choose **Cancel** to not remove them\. 26 | ![\[Deleting a key-only tag in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-delete-key-only-tag.png) 27 | 28 | 1. To remove a key\-value tag, choose the delete icon \(X\) for the key\-value tag\. At the prompt, choose **Yes, delete** to remove the key\-value tag, or choose **No, cancel** to not remove it\. 29 | ![\[Deleting a key-value tag in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-delete-key-value-tag.png) -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-create-a-snapshot-of-your-instance.md: -------------------------------------------------------------------------------- 1 | # Creating a snapshot of your Linux or Unix instance in Amazon Lightsail 2 | 3 | *Last updated: June 28, 2018* 4 | 5 | You can create snapshots of your Linux/Unix\-based Lightsail instances\. An *instance snapshot* is a copy of the system disk and matches the original machine configuration \(memory, CPU, disk size, and data transfer rate\)\. If you've attached block storage disks to your instance, Lightsail copies those additional disks as part of your snapshot\. For more information, see [Snapshots in Amazon Lightsail](understanding-instance-snapshots-in-amazon-lightsail.md)\. 6 | 7 | **Note** 8 | The steps to create a snapshot of a Windows Server\-based Lightsail instance are different\. For more information, see [Creating a snapshot of your Windows Server instance in Amazon Lightsail](prepare-windows-based-instance-and-create-snapshot.md)\. 9 | 10 | You must already have an instance in Lightsail to create a snapshot of it\. After you have an instance, follow these steps to create a snapshot: 11 | 12 | 1. On the Lightsail home page, choose the name of your instance for which you want to create a snapshot\. 13 | 14 | 1. Choose the **Snapshots** tab\. 15 | 16 | 1. Under the **Manual snapshots** section of the page, choose **Create snapshot**, then enter a name for your snapshot\. 17 | 18 | Resource names: 19 | + Must be unique within each AWS Region in your Lightsail account\. 20 | + Must contain 2 to 255 characters\. 21 | + Must start and end with an alphanumeric character or number\. 22 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 23 | 24 | 1. Choose **Create**\. 25 | 26 | You can see the snapshot you just created with a status of **Snapshotting\.\.\.**\. 27 | 28 | After the snapshot is finished, you can [create another instance from the snapshot](lightsail-how-to-create-instance-from-snapshot.md)\. For example, you may want to choose a larger size bundle than you had previously\. 29 | 30 | **Important** 31 | When you create a new instance from a snapshot, Lightsail lets you create an instance bundle that is either the same size or larger size\. We do not currently support creating a *smaller* instance size from a snapshot\. The smaller options will be grayed out when you create a new instance from a snapshot\. 32 | 33 | To create a larger instance size from a snapshot, you can use the Lightsail console, the **create\-instances\-from\-snapshot** CLI command\. or the **CreateInstancesFromSnapshot** API operation\. For more information, see [Creating an instance from a snapshot in Amazon Lightsail](lightsail-how-to-create-instance-from-snapshot.md)\. 34 | 35 | For more information about Lightsail bundles, see [Lightsail Pricing](https://amazonlightsail.com/pricing/)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-configuring-database-public-mode.md: -------------------------------------------------------------------------------- 1 | # Configuring the public mode for your database in Amazon Lightsail 2 | 3 | *Last updated: March 15, 2019* 4 | 5 | Your managed database in Amazon Lightsail is accessible only by your Lightsail resources \(instances, load balancers, etc\.\) that are in the same Lightsail account\. One common scenario is to create both a Lightsail instance with a public\-facing web application and a Lightsail database that is not publicly accessible, and then connect the two\. 6 | 7 | Enable the public mode feature to make your database publicly accessible\. This way, anyone with the database endpoint, port, user name, and password can connect to your database\. For more information, see [Connecting to your MySQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-mysql-database.md) or [Connecting to your PostgreSQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-postgres-database.md)\. 8 | 9 | **To configure the public mode for your database** 10 | 11 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 12 | 13 | 1. On the Lightsail home page, choose the **Databases** tab\. 14 | 15 | 1. Choose the name of the database for which you want to configure public mode\. 16 | 17 | 1. Choose the **Networking** tab\. 18 | 19 | 1. Under the **Public mode** section, use the toggle to turn it on\. Likewise, use the toggle to turn it off\. 20 | ![\[The database public mode toggle in the Lightsail console\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-database-public-mode-toggle.png) 21 | 22 | The public accessibility setting begins applying immediately but may require a few minutes to complete\. During this time, the status of your database changes to **Modifying**\. The status of your database changes to **Available** after the public accessibility setting is applied\. 23 | 24 | ## Next steps 25 | 26 | Here are a few guides to help you manage your database in Lightsail: 27 | + [Configuring the data import mode for your database in Amazon Lightsail](amazon-lightsail-configuring-database-data-import-mode.md) 28 | + [Managing your database password in Amazon Lightsail](amazon-lightsail-managing-database-password.md) 29 | + [Connecting to your MySQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-mysql-database.md) 30 | + [Connecting to your PostgreSQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-postgres-database.md) 31 | + [Importing data into your MySQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-mysql-database.md) 32 | + [Importing data into your PostgreSQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-postgres-database.md) 33 | + [Creating a snapshot of your database in Amazon Lightsail](amazon-lightsail-creating-a-database-snapshot.md) -------------------------------------------------------------------------------- /doc_source/lightsail-create-static-ip.md: -------------------------------------------------------------------------------- 1 | # Create a static IP and attach it to an instance in Amazon Lightsail 2 | 3 | *Last updated: July 14, 2022* 4 | 5 | The default dynamic public IP address attached to your Amazon Lightsail instance changes every time you stop and restart the instance\. Create a static IP address and attach it to your instance to keep the public IP address from changing\. Later, when you point a registered domain name to your instance, you don’t have to update your domain’s DNS records every time you stop and restart your instance\. You can attach one static IP to an instance\. For more information, see [Static IP addresses in Amazon Lightsail](understanding-static-ip-addresses-in-amazon-lightsail.md)\. 6 | 7 | ## Prerequisites 8 | 9 | You need at least one instance running in Lightsail\. To create one, see [Create an instance in Lightsail](getting-started-with-amazon-lightsail.md)\. 10 | 11 | ## Create and assign a Static IP address to an instance 12 | 13 | Follow these steps to create a new static IP address and attach it to an instance in Lightsail\. 14 | 15 | 1. Sign in to the Lightsail console at [https://lightsail\.aws\.amazon\.com/](https://lightsail.aws.amazon.com/)\. 16 | 17 | 1. On the Lightsail home page, choose **Networking**\. 18 | 19 | 1. Choose **Create static IP**\. 20 | 21 | 1. Select the AWS Region where you want to create your static IP\. 22 | **Note** 23 | Static IP addresses can only be attached to instances in the same Region\. 24 | 25 | 1. Choose the Lightsail resource to which you want to attach the static IP\. 26 | 27 | 1. Enter a name for your static IP\. 28 | 29 | Resource names: 30 | + Must be unique within each AWS Region in your Lightsail account\. 31 | + Must contain 2 to 255 characters\. 32 | + Must start and end with an alphanumeric character or number\. 33 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 34 | 35 | 1. Choose **Create**\. 36 | 37 | Now when you go to the home page, you see a static IP address that you can manage\. 38 | ![\[Static IP address attached to an instance\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-static-ip-attached-to-an-instance.png) 39 | 40 | Also, on the **Networking** tab of your instance's management page, you'll see a blue pushpin next to your public IP address\. This indicates that the IP address is now static\. 41 | ![\[The Networking tab of the manage instance page\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-static-ip-pushpin.png) 42 | 43 | **Important** 44 | Static IP addresses are free while attached to a resource\. You can manage up to five at a time\. 45 | 46 | For more information, see [Public IP addresses and private IP addresses in Amazon Lightsail](understanding-public-ip-and-private-ip-addresses-in-amazon-lightsail.md)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-managing-database-password.md: -------------------------------------------------------------------------------- 1 | # Managing your database password in Amazon Lightsail 2 | 3 | *Last updated: March 12, 2021* 4 | 5 | When you create a new database in Amazon Lightsail, you can let Lightsail create a strong password for you or specify your own\. You can view or change the current database password at any time in the Lightsail console\. 6 | 7 | **To manage your database password** 8 | 9 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 10 | 11 | 1. On the Lightsail home page, choose the **Databases** tab\. 12 | 13 | 1. Choose the name of the database for which you want to manage the password\. 14 | 15 | 1. On the **Connect** tab, under the **User name and passwords** section, choose **Show** to view the current database password\. 16 | ![\[Show database password\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-database-show-password.png) 17 | 18 | 1. To change the database password, choose **Change password**\. 19 | 20 | You can opt to have Lightsail create a strong password for you, or you can enter your own password into the text box\.The password can include any printable ASCII character except "/", """, or "@"\. For MySQL databases, the password must contain from 8 to 41 characters\. For PostgreSQL, the password must contain from 8 to 128 characters\. 21 | ![\[Changing your database password\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-database-change-password.png) 22 | 23 | 1. Choose **Save** when you’re done\. 24 | 25 | A database password change is applied immediately\. If you entered your own password, the password is saved immediately\. If Lightsail created the password for you, it is generated within a few seconds\. Choose **Show** to view the new password\. 26 | 27 | ## Next steps 28 | 29 | Here are a few guides to help you manage your database in Lightsail: 30 | + [Configuring the public mode for your database in Amazon Lightsail](amazon-lightsail-configuring-database-public-mode.md) 31 | + [Configuring the data import mode for your database in Amazon Lightsail](amazon-lightsail-configuring-database-data-import-mode.md) 32 | + [Connecting to your MySQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-mysql-database.md) 33 | + [Connecting to your PostgreSQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-postgres-database.md) 34 | + [Importing data into your MySQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-mysql-database.md) 35 | + [Importing data into your PostgreSQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-postgres-database.md) 36 | + [Creating a snapshot of your database in Amazon Lightsail](amazon-lightsail-creating-a-database-snapshot.md) 37 | + [Changing the preferred maintenance and backup windows for your database in Amazon Lightsail](amazon-lightsail-changing-preferred-maintenance-and-backup-windows.md) -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-start-stop-or-restart-your-instance-virtual-private-server.md: -------------------------------------------------------------------------------- 1 | # Start, stop, or restart your Amazon Lightsail instance 2 | 3 | *Last updated: April 17, 2021* 4 | 5 | When Lightsail creates your instance, your machine goes into a **Pending** state before it starts **Running**\. After your instance is running, you can restart it or stop and then restart it\. The cycle looks like this: 6 | 7 | ![\[Instance states\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-instance-state-cycle.png) 8 | 9 | You can see the instance state when you manage your instance or view your instance on the home page\. 10 | 11 | **Important** 12 | The default public IPv4 address that is assigned to your instance when you create it will change when you stop and start your instance\. You can optionally create and attach a static IPv4 address to your instance\. The static IPv4 address replaces the default public IPv4 address of your instance, and it stays the same when you stop and start your instance\. For more information, see [Create a static IP and attach it to an instance in Amazon Lightsail](lightsail-create-static-ip.md)\. 13 | 14 | ## Restart your instance while it's running 15 | + On the home page, choose the instance you want to restart, or choose **Restart** from the manage instance menu\. 16 | ![\[Restart your instance from the manage instance menu\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-restart-instance-from-manage-instance-menu.png) 17 | 18 | If you're viewing your instance from the instance management page, choose **Restart**, and then choose **Confirm** when prompted\. 19 | **Note** 20 | To **Restart** your instance, it must be in a **Running** state\. 21 | 22 | ## Stop a running instance 23 | + On the home page, choose the instance you want to stop, or choose **Stop** from the manage instance menu\. 24 | ![\[Stop your instance from the manage instance menu\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-stop-instance-from-manage-instance-menu.png) 25 | 26 | If you're viewing your instance from the instance management page, choose **Stop**, and then choose **Confirm** when prompted\. 27 | **Note** 28 | To **Stop** your instance, it must be in a **Running** state\. 29 | 30 | ## Start your instance after it's stopped 31 | + On the home page, choose the instance you want to start, or choose **Start** from the manage instance menu\. 32 | ![\[Start your instance from the manage instance menu\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-start-instance-from-manage-instance-menu.png) 33 | 34 | If you're viewing your instance from the instance management page, choose **Start**\. 35 | **Note** 36 | To **Start** your instance, it must be in a **Stopped** state\. -------------------------------------------------------------------------------- /doc_source/elastic-block-storage-and-ssd-disks-in-amazon-lightsail.md: -------------------------------------------------------------------------------- 1 | # Block storage disks in Lightsail 2 | 3 | **Note** 4 | Every Lightsail server comes with high\-performing, persistent SSD\-based block storage\. Your system disk is automatically replicated within its Availability Zone to protect you from component failure\. This offers you high availability and durability\. You can also create additional block storage disks and attach them to your Lightsail instances\. 5 | 6 | *Last updated: July 10, 2019* 7 | 8 | System disks offer the consistent and low\-latency performance you need to run your workloads\. With Lightsail disks, you can scale your usage up or down within minutes—and pay a low price for only what you provision\. 9 | 10 | You can select up to an 80 GB system disk on your Linux/Unix\-based or Windows Server\-based instance\. See [Get started with Linux\-based instances in Lightsail](getting-started-with-amazon-lightsail.md) or [Get started with Windows Server\-based instances](get-started-with-windows-based-instances-in-lightsail.md)\. 11 | 12 | You can also add more storage to your virtual private server by creating additional block storage disks\. See [Create additional block storage disks in Lightsail \(Linux/Unix\)](create-and-attach-additional-block-storage-disks-linux-unix.md) or [Creating and attaching block storage disks to your Windows Server instance in Amazon Lightsail](create-and-attach-additional-block-storage-disks-windows.md)\. 13 | 14 | ## Lightsail block storage disks 15 | 16 | Block storage is a storage architecture that manages data as "blocks"\. Each storage block \(known as a "disk" in Lightsail\) acts like an individual hard disk that you can attach to your server\. In general, you can use additional block storage for applications or software that must separate out specific data from their core service, and to protect application data in case of a failure or other issue with your instance and boot storage disk\. 17 | 18 | Lightsail offers solid\-state drives \(SSD\) for block storage\. This type of block storage balances a reasonable price and good performance\. It's intended to support the vast majority of workloads that run on Lightsail\. Lightsail additional block storage disks offer consistent performance and the low latency needed for applications or software that frequently access stored data\. 19 | 20 | **Note** 21 | For customers with applications that require sustained IOPS performance or high amounts of throughput per disk, or for customers running large databases like MongoDB, Cassandra, etc\., we recommend using Amazon EC2 with GP2 or Provisioned IOPS SSD storage instead of Lightsail\. 22 | 23 | You can learn more about [Amazon EBS volumes](http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/EBSVolumes.html) in the *Amazon EC2 User Guide*\. 24 | 25 | ## Disk Quotas 26 | + 20,000 GB per Region\. 27 | + 16 TB per disk maximum, or 8 GB per disk minimum\. 28 | + Each instance can have up to 15 attached disks, and 1 boot volume disk\. -------------------------------------------------------------------------------- /doc_source/enable-session-stickiness-persistence-or-change-cookie-duration.md: -------------------------------------------------------------------------------- 1 | # Enable session persistence for Amazon Lightsail load balancers 2 | 3 | *Last updated: November 29, 2017* 4 | 5 | You can enable *session persistence* for your users\. This is helpful if you're storing session information locally in the user's browser\. For example, you might be running a Magento e\-commerce application with a shopping cart on Lightsail\. If you turn on session persistence, your users can add items to their shopping carts, leave the site, and still find the items in their carts when they come back\. 6 | 7 | You can also adjust the cookie duration using the AWS Command Line Interface \(AWS CLI\) or the Lightsail API\. 8 | 9 | ## Enable session persistence 10 | 11 | 1. On the Lightsail home page, choose **Networking**\. 12 | 13 | 1. Choose your load balancer to manage it\. 14 | 15 | 1. Choose the **Inbound traffic** tab\. 16 | 17 | 1. Choose **Enable session persistence**\. 18 | ![\[Session persistence enabled\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/session-persistence-enabled.png) 19 | 20 | ## Adjust the cookie duration 21 | 22 | You can also adjust the cookie duration for the persistent session\. This is useful if you want to have a particularly long or short duration\. For example, for many ecommerce sites the duration is quite long\. This lets customers leave and come back without losing items in their shopping carts\. 23 | 24 | If you haven't done so already, set up the AWS CLI and configure it\. 25 | 26 | [Configuring the AWS Command Line Interface to work with Amazon Lightsail](lightsail-how-to-set-up-and-configure-aws-cli.md) 27 | 28 | 1. Open a command prompt or a terminal window\. 29 | 30 | 1. Type the following AWS CLI command to increase the cookie duration to three days \(259,200 seconds\)\. 31 | 32 | ``` 33 | aws lightsail update-load-balancer-attribute --load-balancer-name LoadBalancerName --attribute-name SessionStickiness_LB_CookieDurationSeconds --attribute-value 259200 34 | ``` 35 | 36 | In the command, replace *LoadBalancerName* with the name of your load balancer\. 37 | 38 | If successful, you should see the following response\. 39 | 40 | ``` 41 | { 42 | "operations": [ 43 | { 44 | "status": "Succeeded", 45 | "resourceType": "LoadBalancer", 46 | "isTerminal": true, 47 | "operationDetails": "SessionStickiness_LB_CookieDurationSeconds", 48 | "statusChangedAt": 1511758936.174, 49 | "location": { 50 | "availabilityZone": "all", 51 | "regionName": "us-west-2" 52 | }, 53 | "operationType": "UpdateLoadBalancerAttribute", 54 | "resourceName": "example-load-balancer", 55 | "id": "681c2bd9-9a51-402b-8ad2-12345EXAMPLE", 56 | "createdAt": 1511758936.174 57 | } 58 | ] 59 | } 60 | ``` -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-configuring-database-data-import-mode.md: -------------------------------------------------------------------------------- 1 | # Configuring the data import mode for your database in Amazon Lightsail 2 | 3 | *Last updated: March 15, 2019* 4 | 5 | Regular database backup operations can cause substantial delays, or slowdowns, when importing large amounts of data all at once\. Enable the data import mode for your Amazon Lightsail managed database to suspend these operations while you import large amounts of data\. 6 | 7 | **Important** 8 | All emergency restore backups are deleted when data import mode is enabled\. Create a snapshot of your database if you would like to have a backup before data import mode is enabled\. For more information, see [Creating a snapshot of your database in Amazon Lightsail](amazon-lightsail-creating-a-database-snapshot.md)\. 9 | 10 | **To configure the data import mode for your database** 11 | 12 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 13 | 14 | 1. On the Lightsail home page, choose the **Databases** tab\. 15 | 16 | 1. Choose the name of the database for which you want to configure data import mode\. 17 | 18 | 1. On the **Connect** tab, under the **Data import mode** section, use the toggle to turn on the data import mode\. Likewise, after the import is complete, use the toggle to turn it off\. 19 | ![\[The data import mode toggle in the Lightsail console\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-database-data-import-mode-toggle.png) 20 | 21 | Now that the data import mode is enabled, database backup operations are suspended\. We recommend that you enable data import mode temporarily\. Use it only when it’s necessary for you to import large amounts of data into your database\. Disable data import mode as soon as you’re done to restore backup operations\. 22 | **Note** 23 | Your import may be slowed depending on the amount of data that you're importing\. For more information, see [Optimizing data import](https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-choosing-a-database#optimizing-your-data-import)\. 24 | 25 | ## Next steps 26 | 27 | Here are a few guides to help you manage your database in Lightsail: 28 | + [Configuring the public mode for your database in Amazon Lightsail](amazon-lightsail-configuring-database-public-mode.md) 29 | + [Managing your database password in Amazon Lightsail](amazon-lightsail-managing-database-password.md) 30 | + [Connecting to your MySQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-mysql-database.md) 31 | + [Connecting to your PostgreSQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-postgres-database.md) 32 | + [Importing data into your MySQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-mysql-database.md) 33 | + [Importing data into your PostgreSQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-postgres-database.md) 34 | + [Creating a snapshot of your database in Amazon Lightsail](amazon-lightsail-creating-a-database-snapshot.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-update-management.md: -------------------------------------------------------------------------------- 1 | # Instance and container service update management in Amazon Lightsail 2 | 3 | *Last updated: April 20, 2022* 4 | 5 | Amazon Web Services \(AWS\), Amazon Lightsail, and third\-party application vendors periodically update and patch the instance images \(also known as *blueprints*\) that are available on Lightsail\. AWS and Lightsail do not update or patch the operating system or applications on instances after you create them\. Lightsail also does not update or patch the operating system and software that you configure on your Lightsail container services\. Therefore, we recommend that you regularly update, patch, and secure the operating system and applications on your Amazon Lightsail instances and container services\. For more information, see the [AWS Shared Responsibility Model](https://aws.amazon.com/compliance/shared-responsibility-model/)\. 6 | 7 | ## Instance blueprint software support 8 | 9 | The following list of Amazon Lightsail platforms and blueprints links to each vendor’s support page\. There, you can view information such as how\-to guides, and keeping your operating system and application up to date\. You can use any automatic update service or recommended process for installing updates that are provided by the application vendor\. 10 | 11 | **Windows** 12 | + [Windows Server 2019, Windows Server 2016, and Windows Server 2012](https://docs.microsoft.com/en-us/windows-server/) 13 | + [Microsoft SQL Server](https://docs.microsoft.com/en-us/sql/) 14 | 15 | **Linux and Unix** \- Operating system only 16 | + [Amazon Linux 2](https://aws.amazon.com/amazon-linux-2) 17 | + [Amazon Linux](https://aws.amazon.com/amazon-linux-ami) 18 | + [Ubuntu](https://ubuntu.com/support/community-support) 19 | + [Debian](https://www.debian.org/support) 20 | + [FreeBSD](https://www.freebsd.org/community) 21 | + [openSUSE](https://en.opensuse.org/Portal:Support) 22 | + [CentOS](https://wiki.centos.org/action/show/Documentation) 23 | 24 | **Linux and Unix** \- Operating system plus application 25 | + [Plesk Hosting Stack on Ubuntu](https://www.plesk.com/support) 26 | + [cPanel & WHM for Linux](https://cpanel.com/support) 27 | + [WordPress](https://docs.bitnami.com/general/apps/wordpress) 28 | + [WordPress Multisite](https://docs.bitnami.com/general/apps/wordpress-multisite) 29 | + [LAMP \(PHP 7\)](https://docs.bitnami.com/general/infrastructure/lamp) 30 | + [Node\.js](https://docs.bitnami.com/general/infrastructure/nodejs) 31 | + [Joomla](https://docs.bitnami.com/general/apps/joomla) 32 | + [Magento](https://docs.bitnami.com/general/apps/magento) 33 | + [MEAN](https://docs.bitnami.com/general/infrastructure/mean) 34 | + [Drupal](https://docs.bitnami.com/general/apps/drupal) 35 | + [GitLab CE](https://docs.bitnami.com/general/apps/gitlab) 36 | + [Redmine](https://docs.bitnami.com/general/apps/redmine) 37 | + [Nginx](https://docs.bitnami.com/general/infrastructure/nginx) 38 | + [Ghost](https://docs.bitnami.com/general/apps/ghost) 39 | + [Django](https://docs.bitnami.com/general/infrastructure/django) 40 | + [PrestaShop](https://docs.bitnami.com/general/apps/prestashop) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-updating-ec2-instances.md: -------------------------------------------------------------------------------- 1 | # Updating Amazon EC2 instances for enhanced networking 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | Some Lightsail instances are incompatible with the current generation EC2 instance types \(T3, M5, C5, or R5\) because they are not enabled for enhanced networking\. If your source Lightsail instance is incompatible, you will need to choose a previous generation instance type \(T2, M4, C4, or R4\) when creating an EC2 instance from your exported snapshot\. These instance type options are presented to you when creating an EC2 instance using the **Create an Amazon EC2 instance** page in the Lightsail console\. 6 | 7 | **Note** 8 | For more information about enhanced networking, see [Enhanced Networking on Linux](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html) or [Enhanced Networking on Windows](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/enhanced-networking.html) in the Amazon EC2 documentation\. 9 | 10 | To use the latest generation EC2 instance types when the source Lightsail instance is incompatible, you need to create the new EC2 instance using a previous generation instance type \(T2, M4, C4, or R4\), update the networking driver on your instance, and then upgrade the instance to the desired current generation instance type\. 11 | 12 | ## Prerequisites 13 | 14 | You must create an Amazon EC2 instance from an exported Lightsail snapshot\. If your Lightsail instance is incompatible, you’ll choose a previous generation instance type \(T2, M4, C4, or R4\) when creating the Amazon EC2 instance\. To learn more, see [Creating Amazon EC2 instances from exported snapshots in Lightsail](amazon-lightsail-creating-ec2-instances-from-exported-snapshots.md)\. 15 | 16 | After your new EC2 instance is up and running, continue to the [Enable Enhanced Networking with the Elastic Network Adapter](#enabling-enhanced-networking-with-elastic-network-adapter) section of this guide to learn how to enable enhanced networking\. 17 | 18 | ## Enable Enhanced Networking with the Elastic Network Adapter 19 | 20 | After your new instance is up and running, see one of the following guides in the Amazon EC2 documentation to enable enhanced networking with the Elastic Network Adapter \(ENA\): 21 | + [Enabling Enhanced Networking with the ENA on Linux Instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html) 22 | + [Enabling Enhanced Networking with the ENA on Windows Instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/enhanced-networking-ena.html) 23 | 24 | ## Upgrade your instance type 25 | 26 | After you have enabled enhanced networking, you can upgrade the instance type by following the instructions in one of the following guides: 27 | + For Windows Server instances — [Migrating to Latest Generation Instance Types](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/migrating-latest-types.html) 28 | + For Linux or Unix instances — [Changing the Instance Type](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-connecting-to-postgres-database-using-ssl.md: -------------------------------------------------------------------------------- 1 | # Connecting to your PostgreSQL database in Amazon Lightsail using SSL 2 | 3 | *Last updated: January 2, 2020* 4 | 5 | Amazon Lightsail creates an SSL certificate, and installs it on your PostgreSQL \(Postgres\) managed database when it’s provisioned\. The certificate is signed by a certificate authority \(CA\), and it includes the database endpoint as the Common Name \(CN\) for the SSL certificate to guard against spoofing attacks\. 6 | 7 | An SSL certificate created by Lightsail is the trusted root entity and should work in most cases but might fail if your application does not accept certificate chains\. If your application does not accept certificate chains, you might need to use an intermediate certificate to connect to your AWS Region\. 8 | 9 | For more information about the CA certificates for your managed database, supported AWS Regions, and how you can download intermediate certificates for your applications, see [Downloading an SSL certificate for your managed database in Amazon Lightsail](amazon-lightsail-download-ssl-certificate-for-managed-database.md)\. 10 | 11 | ## Prerequisites 12 | + Install PostgreSQL server on the computer you will use to connect to your database\. For more information, see [PostgreSQL Downloads](https://www.postgresql.org/download/) in the Postgres website 13 | + Download the appropriate certificate for your database\. For information, see [Downloading an SSL certificate for your managed database in Amazon Lightsail](amazon-lightsail-download-ssl-certificate-for-managed-database.md)\. 14 | 15 | ## Connect to your Postgres database using SSL 16 | 17 | Complete the following steps to connect to your Postgres database using SSL\. 18 | 19 | 1. Open a Terminal or Command Prompt window\. 20 | 21 | 1. Enter the following command to connect to a PostgreSQL database\. 22 | 23 | ``` 24 | psql -h DatabaseEndpoint -p 5432 "dbname=DatabaseName user=UserName sslrootcert=/path/to/certificate/rds-combined-ca-bundle.pem sslmode=verify-full" 25 | ``` 26 | 27 | In the command, replace: 28 | + *DatabaseEndpoint* with the endpoint of your database\. 29 | + *DatabaseName* with the name of the database you want to connect to\. 30 | + *UserName* with the user name of your database\. 31 | + */path/to/certificate/rds\-combined\-ca\-bundle\.pem* with the local path where you downloaded and saved the certificate for your database\. 32 | 33 | **Example:** 34 | 35 | ``` 36 | psql -h ls-8e81e07f8b821917b11e1c6a0e26cb73c203.czowadgeezqi.us-west-2.rds.amazonaws.com -p 5432 "dbname=dbmaster user=dbmasteruser sslrootcert=/home/ec2-user/rds-combined-ca-bundle.pem sslmode=verify-full" 37 | ``` 38 | 39 | 1. Type the password for the database user you specified in the previous command when prompted, and press **Enter**\. 40 | 41 | You should see a result similar to the following example\. Your connection is encrypted if you see a value of “SSL connection\." 42 | ![\[Postgres database connection status.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-postgres-ssl-connection.png) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-troubleshooting-notifications.md: -------------------------------------------------------------------------------- 1 | # Troubleshooting notifications in Amazon Lightsail 2 | 3 | *Last updated: February 27, 2020* 4 | 5 | If don't receive notifications when you expect to be notified, then there are a few things you should check to confirm that your notification contacts are configured correctly\. To learn more about notifications, see [Notifications in Amazon Lightsail](amazon-lightsail-notifications.md)\. 6 | 7 | The following list describes common notification contact issues that you may experience, along with what causes them, and how to resolve them\. If you encounter an issue that's not in the list, use the **Questions? Comments?** link at the bottom of this page to submit feedback or contact AWS Customer Support\. 8 | 9 | **I added my email address as a notification contact but I'm not receiving email notifications** 10 | When you add an email address as a notification contact in Lightsail, a verification request is sent to that address\. The verification request email contains a link that the recipient must click to confirm that they want to receive Lightsail notifications\. Notifications are not sent to the email address until after it is verified\. The verification comes from *AWS Notifications *, with a subject of *AWS Notification \- Subscription Confirmation*\. SMS messaging does not require verification\. 11 | Check the mailbox's spam and junk folders if the verification request is not in the inbox folder\. If the verification request got lost, or was deleted, choose **Resend verification** in the notification banner that is displayed in the Lightsail console, and in the **Account** page\. 12 | 13 | ![\[Resend email verification in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-email-verification-banner-resend.png) 14 | 15 | **I see **null** listed as my email notification contact\.** 16 | Email addresses must be verified within 24 hours after they are added\. If you fail to verify an email within 24 hours, that email is automatically given a status of `invalid` and it is removed from Lightsail\. That is why you might see a value of **null** for one or more of your email notification contacts\. 17 | 18 | ![\[Null email notification contact in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-null-email-notification-contact.png) 19 | To fix this issue, remove the **null** email notification contact, and add the correct email address again\. Ensure that you verify the email address immediately after adding it to Lightsail\. For more information, see [Notifications in Amazon Lightsail](amazon-lightsail-notifications.md)\. 20 | 21 | **I have not received SMS text message notifications, or I stopped receiving them recently** 22 | You may have opted out of receiving SMS text message notifications\. You can opt out by responding to an SMS text message notification with `ARRET` \(French\), `CANCEL`, `END`, `OPT-OUT`, `OPTOUT`, `QUIT`, `REMOVE`, `STOP`, `TD`, or `UNSUBSCRIBE`\. If you opt out a mobile phone number, you must wait 30 days before you are able to add that mobile phone number again as a notification contact in Lightsail\. -------------------------------------------------------------------------------- /doc_source/getting-help-in-amazon-lightsail.md: -------------------------------------------------------------------------------- 1 | # Getting help in Amazon Lightsail 2 | 3 | *Last updated: May 17, 2017* 4 | 5 | In Amazon Lightsail, you can get help in several ways\. 6 | 7 | ## Context\-sensitive help panel in Lightsail 8 | 9 | Lightsail has a context\-sensitive **Help** panel on each page of the console with additional tips and information that are specific to the page you're on\. Open the help panel any time you have a question about something on the page, and close it when you're good to go\. You can open the help panel by choosing **Help** on any page, or by choosing any of the small question marks throughout the user interface\. 10 | 11 | ![\[Context-sensitive Help panel in Lightsail\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/context-sensitive-help-panel-in-amazon-lightsail.png) 12 | 13 | ## About this developer guide 14 | 15 | The Amazon Lightsail developer guide contains how\-to topics and conceptual overviews to help you work in Lightsail\. For example, you can [create an instance](getting-started-with-amazon-lightsail.md), [connect to your instance](lightsail-how-to-connect-to-your-instance-virtual-private-server.md), or [manage your domain](lightsail-how-to-create-dns-entry.md)\. 16 | 17 | ## Using search 18 | 19 | You can search for doc topics from any page in Lightsail by using the search box at the top of each page\. To refine your search, you can search again from the documentation search page\. 20 | 21 | Didn't find what you were looking for? Sorry to hear that\! Send us feedback and we'll get on it\. On every page in Lightsail, you can choose **Questions? Comments?** and submit feedback to make suggestions\. We'll get back to you with an answer\. 22 | 23 | ## Using the Lightsail CLI and API 24 | 25 | You can use the AWS Command Line Interface \(AWS CLI\) or the Lightsail REST API to create, read, update, and delete Lightsail resources\. In addition to the REST API, we also have an SDK in multiple languages, including Java, Ruby, JavaScript \(Node\.js\), Go, PHP, Python, \.NET \(C\#\), and C\+\+\. For more information about the Lightsail API, see the [Lightsail API reference](http://docs.aws.amazon.com/lightsail/2016-11-28/api-reference/Welcome.html)\. 26 | 27 | **Note** 28 | You need to generate access keys to use the Lightsail API\. [Learn more about setting up access keys to use the Lightsail API](lightsail-how-to-set-up-access-keys-to-use-sdk-api-cli.md)\. 29 | 30 | The AWS CLI is helpful when you work with your Lightsail resources\. In the AWS CLI, just type `aws lightsail help` to learn about the available commands\. For help on a specific CLI command, type the command name followed by `help` to learn more about its parameters and exceptions\. For more information, see the [Lightsail CLI reference](https://docs.aws.amazon.com/cli/latest/reference/lightsail/index.html)\. 31 | 32 | ## AWS forums and other community resources 33 | 34 | You can also post your questions in our AWS discussion forum: [AWS Forums](https://forums.aws.amazon.com/forum.jspa?forumID=231)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-organizing-resources-using-tags.md: -------------------------------------------------------------------------------- 1 | # Organizing your Amazon Lightsail resources using tags 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | After you tag your Amazon Lightsail resources, you can filter your resources by the tags you have added\. You do this in the Lightsail console by choosing or searching for a tag\. This guide shows you how to view and filter your Lightsail resources by tags\. 6 | 7 | **Note** 8 | For more information about tags, what resources can be tagged, and tag restrictions, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 9 | 10 | ## Viewing tags for a resource 11 | 12 | Instances, container services, CDN distributions, buckets, databases, disks, DNS zones, and load balancers can be tagged using the Lightsail console and therefore contain a **Tags** tab\. That tab is accessible through the resource’s management page, as shown in the following example for an instance resource\. On the **Tags** tab, you can add, edit, or delete tags\. For more information, see [Adding tags to a resource in Amazon Lightsail](amazon-lightsail-adding-tags-to-a-resource.md), and [Deleting tags in Amazon Lightsail](amazon-lightsail-deleting-tags.md)\. 13 | 14 | ![\[Viewing tags for a resource in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-viewing-tags-for-a-resource.png) 15 | 16 | **Note** 17 | Instances, container services, CDN distributions, buckets, databases, disks, DNS zones, and load balancers can be tagged using the Lightsail console\. However, more Lightsail resources can be tagged using the [Lightsail API operations](https://docs.aws.amazon.com/lightsail/2016-11-28/api-reference/Welcome.html), or the [AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/reference/lightsail/) \(AWS CLI\) or SDKs\. For a full list of Lightsail resources that support tagging, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 18 | 19 | ## Filtering Lightsail resources using tags 20 | 21 | The following options are available in the Lightsail console to filter your resources using tags\. All of these options refresh the Lightsail home page to display only the tag that you searched for or selected\. 22 | 23 | **Note** 24 | These filtering options are persistent\. If you filter by a tag, and then navigate between sections of the Lightsail home page, the filter is still applied\. 25 | + On the Lightsail home page, enter the key\-only tag or the value that you want to filter by into the **Search** text box, and press **Enter**\. 26 | ![\[Searching for a tag in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-searching-for-a-tag.png) 27 | + Choose a tag that is displayed under a resource on the Lightsail home page\. 28 | ![\[Choosing a tag in the Lightsail home page.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-choosing-a-tag.png) 29 | + Choose a tag that is displayed in the heading of a resource\. 30 | ![\[Choosing a tag in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-choosing-a-heading-tag.png) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-domain-privacy-protection.md: -------------------------------------------------------------------------------- 1 | # Managing privacy protection for domain contacts 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | When you register a domain with Lightsail, we activate privacy protection by default for all the domain contacts\. This typically hides most of your contact information from WHOIS \("Who is"\) queries and reduces the amount of spam that you receive\. Your contact information is replaced with either the contact information for the registrar or with the phrase "REDACTED FOR PRIVACY\." There are no charges for using privacy protection\. 6 | 7 | If you choose to deactivate privacy protection, anyone can send a WHOIS query for the domain and, for most top\-level domains \(TLDs\), they might be able to get all the contact information that you provided when you registered the domain\. This information includes name, address, phone number, and email address\. The WHOIS command is widely available\. It's included in many operating systems, and it's also available as a web application on many websites\. 8 | 9 | To manage privacy protection for a domain that you registered by using Lightsail, perform the following procedure\. 10 | 11 | **Contents** 12 | + [Complete the prerequisites](#privacy-protection-prerequisites) 13 | + [Manage privacy protection for your domain](#manage-domain-privacy-protection) 14 | 15 | ## Complete the prerequisites 16 | 17 | Register a domain with Lightsail\. For more information, see [Registering a new domain in Amazon Lightsail](amazon-lightsail-register-new-domain.md)\. 18 | 19 | ## Manage privacy protection for your domain 20 | 21 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 22 | 23 | 1. Choose the **Domains & DNS** tab\. 24 | 25 | 1. Choose the name of the domain that you want to change the privacy protection for\. 26 | 27 | 1. Choose **Contact info**\. 28 | 29 | 1. You can manage privacy protection for your contact information by turning the **Privacy protection** toggle switch on or off\. 30 | 31 | **Additional information about domains** 32 | 33 | The following articles can help you manage domains in Lightsail: 34 | + [DNS in Amazon Lightsail](understanding-dns-in-amazon-lightsail.md) 35 | + [Domain registration in Amazon Lightsail](amazon-lightsail-domain-registration.md) 36 | + [Formatting domain names in Amazon Lightsail](amazon-lightsail-domain-name-format.md) 37 | + [Managing a Lightsail domain in Amazon Route 53](amazon-lightsail-manage-domain-advanced.md) 38 | + [Creating a DNS zone to manage your domain’s DNS records in Amazon Lightsail](lightsail-how-to-create-dns-entry.md) 39 | + [Managing domain registration renewal in Amazon Lightsail](amazon-lightsail-domain-manage-auto-renew.md) 40 | + [Edit or delete a DNS zone in Amazon Lightsail](amazon-lightsail-edit-or-delete-a-dns-zone.md) 41 | + [Point your domain to your Lightsail load balancer](add-alias-record-for-lightsail-load-balancer.md) 42 | + [Pointing your domains to your Amazon Lightsail distributions](amazon-lightsail-point-domain-to-distribution.md) 43 | + [Point your domain to a Lightsail instance](amazon-lightsail-routing-to-instance.md) 44 | + [Routing traffic for a domain in Amazon Lightsail to a Lightsail container service](amazon-lightsail-point-domain-to-container-service.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-controlling-access-using-tags.md: -------------------------------------------------------------------------------- 1 | # Using tags to control access to your Amazon Lightsail resources 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | You can use tags in Amazon Lightsail to control access to resources, control access to requests, and control access to tag keys\. In this guide, you’ll learn how to create an AWS Identity and Access Management \(IAM\) policy that specifies a key\-value tag required to create or delete Lightsail resources, and attach the policy to users or groups who need to make those requests\. 6 | 7 | **Note** 8 | To learn more about tags in Lightsail, what resources can be tagged, and the restrictions, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 9 | 10 | ## Step 1: Create an IAM policy 11 | 12 | First, create the following IAM policies in the IAM console\. For more information about creating IAM policies, see [Creating IAM Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the IAM documentation\. 13 | 14 | The following policy restricts users from creating new Lightsail resources unless a key tag of `allow` and a value of `true` is defined with the create request\. This policy also restricts users from deleting resources unless they have the `allow/true` key\-value tag\. 15 | 16 | ``` 17 | { 18 | "Version": "2012-10-17", 19 | "Statement": [ 20 | { 21 | "Effect": "Allow", 22 | "Action": [ 23 | "lightsail:Create*", 24 | "lightsail:TagResource", 25 | "lightsail:UntagResource" 26 | ], 27 | "Resource": "*", 28 | "Condition": { 29 | "StringEquals": { 30 | "aws:RequestTag/allow": "true" 31 | } 32 | } 33 | }, 34 | { 35 | "Effect": "Allow", 36 | "Action": [ 37 | "lightsail:Delete*", 38 | "lightsail:TagResource", 39 | "lightsail:UntagResource" 40 | ], 41 | "Resource": "*", 42 | "Condition": { 43 | "StringEquals": { 44 | "aws:ResourceTag/allow": "true" 45 | } 46 | } 47 | } 48 | ] 49 | } 50 | ``` 51 | 52 | The following policy restricts users from changing the tag for resources that have a key\-value tag that is not `allow/false`\. 53 | 54 | ``` 55 | { 56 | "Version": "2012-10-17", 57 | "Statement": [ 58 | { 59 | "Effect": "Deny", 60 | "Action": [ 61 | "lightsail:TagResource" 62 | ], 63 | "Resource": "*", 64 | "Condition": { 65 | "StringNotEquals": { 66 | "aws:ResourceTag/allow": "false" 67 | } 68 | } 69 | } 70 | ] 71 | } 72 | ``` 73 | 74 | ## Step 2: Attach the policy to users or groups 75 | 76 | After you’ve created the IAM policies, attach them to the users or groups who need to create Lightsail resources using the key\-value pair\. For more information about attaching IAM policies to users or groups, see [Adding and Removing IAM Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_manage-attach-detach.html) in the IAM documentation\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-deleting-distribution.md: -------------------------------------------------------------------------------- 1 | # Deleting your Amazon Lightsail distribution 2 | 3 | *Last updated: July 23, 2020* 4 | 5 | You can delete your Amazon Lightsail distribution at any time if you're no longer using it\. 6 | 7 | ## Delete a distribution 8 | 9 | Complete the following procedure to delete a distribution\. 10 | 11 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 12 | 13 | 1. On the Lightsail home page, choose the **Networking** tab\. 14 | 15 | 1. Choose the name of the distribution you want to delete\. 16 | 17 | 1. Choose the **Delete** tab on your distribution's management page\. 18 | 19 | 1. Choose **Delete distribution** to delete your distribution\. 20 | 21 | 1. Choose **Yes, delete** to confirm the deletion\. 22 | 23 | ## Additional information 24 | 25 | Here are some articles to help you manage distributions in Lightsail: 26 | + [Content delivery network distributions in Amazon Lightsail](amazon-lightsail-content-delivery-network-distributions.md) 27 | + [Creating Amazon Lightsail distributions](amazon-lightsail-creating-content-delivery-network-distribution.md) 28 | + [Understanding request and response behaviors of an Amazon Lightsail distribution](amazon-lightsail-distribution-request-and-response.md) 29 | + [Configuring your WordPress instance to work with your Amazon Lightsail distribution](amazon-lightsail-editing-wp-config-for-distribution.md) 30 | + [Testing your Amazon Lightsail distribution](amazon-lightsail-testing-distribution.md) 31 | + [Changing the origin of your Amazon Lightsail distribution](amazon-lightsail-changing-distribution-origin.md) 32 | + [Changing the caching behavior of your Amazon Lightsail distribution](amazon-lightsail-changing-default-cache-behavior.md) 33 | + [Resetting the cache of your Amazon Lightsail distribution](amazon-lightsail-resetting-distribution-cache.md) 34 | + [Changing the plan of your Amazon Lightsail distribution](amazon-lighstail-changing-distribution-plan.md) 35 | + [Enabling custom domains for your Amazon Lightsail distributions](amazon-lightsail-enabling-distribution-custom-domains.md) 36 | + [Pointing your domains to your Amazon Lightsail distributions](amazon-lightsail-point-domain-to-distribution.md) 37 | + [Changing custom domains for your Amazon Lightsail distribution](amazon-lightsail-changing-distribution-custom-domains.md) 38 | + [Disabling custom domains for your Amazon Lightsail distributions](amazon-lightsail-disabling-distribution-custom-domains.md) 39 | + [Viewing distribution metrics in Amazon Lightsail](amazon-lightsail-viewing-distribution-health-metrics.md) 40 | + [Deleting your Amazon Lightsail distribution](#amazon-lightsail-deleting-distribution) 41 | + [SSL/TLS certificates in Amazon Lightsail](understanding-tls-ssl-certificates-in-lightsail-https.md) 42 | + [Creating SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-create-a-distribution-certificate.md) 43 | + [Validating SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-validating-a-distribution-certificate.md) 44 | + [Viewing SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-viewing-distribution-certificates.md) 45 | + [Deleting SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-deleting-distribution-certificates.md) -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-set-up-access-keys-to-use-sdk-api-cli.md: -------------------------------------------------------------------------------- 1 | # Create an access key to use the Amazon Lightsail API or the AWS Command Line Interface 2 | 3 | *Last updated: January 25, 2021* 4 | 5 | To use the Lightsail API or the AWS Command Line Interface \(AWS CLI\), you need to create a new access key\. The access key consists of an **Access Key ID** and a **Secret Access Key**\. Use the following procedures to create the key and configure the AWS CLI to make calls to the Lightsail API\. 6 | 7 | ## Step 1: Create a new access key 8 | 9 | You can create a new access key in the AWS Identity and Access Management \(IAM\) console\. 10 | 11 | 1. Sign in to the [the IAM console](https://console.aws.amazon.com/iam/home#/users)\. 12 | 13 | 1. Choose the name of the user for which you want to create an access key\. The user you choose should have full access or specific access to Lightsail actions\. 14 | 15 | 1. Choose the **Security credentials** tabs\. 16 | 17 | 1. Choose **Create access key** under the **Access keys** section of the page\. 18 | **Note** 19 | You can have a maximum of two access keys \(active or inactive\) at a time per user\. If you already have two access keys, then you must delete one of them before creating a new one\. Make sure that an access key is not actively in use before deleting it\. 20 | 21 | 1. Make note of the **Access key ID** and **Secret access key** listed\. Choose **Show** under the **Secret access key** column to see your **Secret access key**\. 22 | 23 | You can copy them from this screen or choose **Download Key File** to download a \.csv file containing the access key ID and secret access key\. 24 | **Important** 25 | Keep your access keys in a safe place\. You should name the file something like `MyLightsailKeys.csv` so that you don't struggle to find them later\. If you've downloaded the CSV file from the IAM console, you should delete it after you've completed step 2\. You can create a new access keys later if you need to\. 26 | 27 | ## Step 2: Configure the AWS CLI 28 | 29 | If you haven't installed the AWS CLI, you can do that now\. See [Installing the AWS Command Line Interface](http://docs.aws.amazon.com/cli/latest/userguide/installing.html)\. After you install the AWS CLI, you need to configure it so you can use it\. 30 | 31 | 1. Open a terminal window or command prompt\. 32 | 33 | 1. Type `aws configure`\. 34 | 35 | 1. Paste your **AWS Access Key ID** from the \.csv file you created in the previous step\. 36 | 37 | 1. Paste your **AWS Secret Access Key** when prompted\. 38 | 39 | 1. Enter the AWS Region where your resources are located\. For example, if your resources are primarily in Ohio, choose `us-east-2` when prompted for the **Default region name**\. 40 | 41 | For more information about using the AWS CLI `--region` option, see [General Options](http://docs.aws.amazon.com/cli/latest/topic/config-vars.html#general-options) in the *AWS CLI Reference*\. 42 | 43 | 1. Choose a **Default output format**, such as `json`\. 44 | 45 | ## Next steps 46 | + [Install the SDK](https://aws.amazon.com/tools/#sdk) 47 | + [Configure the AWS Command Line Interface to work with Amazon Lightsail](lightsail-how-to-set-up-and-configure-aws-cli.md) 48 | + [Read the API docs](https://docs.aws.amazon.com/lightsail/2016-11-28/api-reference/Welcome.html) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-adding-tags-to-a-resource.md: -------------------------------------------------------------------------------- 1 | # Adding tags to a resource in Amazon Lightsail 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | Use tags in Amazon Lightsail to categorize your resources by purpose, owner, environment, or other criteria\. Tags can be added to resources at or after they are created\. Follow these steps to add tags to a resource after it’s been created\. 6 | 7 | **Note** 8 | For more information about tags, what resources can be tagged, and the restrictions, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 9 | 10 | **To add tags to a resource** 11 | 12 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 13 | 14 | 1. On the Lightsail home page, choose the tab for the resource type that you want to tag\. For example, to add a tag to a DNS zone, choose the **Networking** tab\. Or choose the **Instances** tab to add a tag to an instance\. 15 | **Note** 16 | Instances, container services, CDN distributions, buckets, databases, disks, DNS zones, and load balancers can be tagged using the Lightsail console\. However, more Lightsail resources can be tagged using the [Lightsail API operations](https://docs.aws.amazon.com/lightsail/2016-11-28/api-reference/Welcome.html), or the [AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/reference/lightsail/) \(AWS CLI\) or SDKs\. For a full list of Lightsail resources that support tagging, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 17 | 18 | 1. Choose the resource that you want to tag\. 19 | 20 | 1. On the management page for the resource that you selected, choose the **Tags** tab\. 21 | ![\[Tags tab in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-tags-tab.png) 22 | 23 | 1. Choose one of the following options, depending on the type of tag that you want to add: 24 | + **Add key\-only tags** or **Edit key\-only tags** \(if tags have already been added\)\. Enter your new tag into the tag key text box, and press **Enter**\. Choose **Save** when you’re done entering your tags to add them, or choose **Cancel** to not add them\. 25 | ![\[Key-only tags in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-key-only-tags.png) 26 | + **Create a key\-value tag**, then enter a key into the **Key** text box, and a value into the **Value** text box\. Choose **Save** when you’re done entering your tags, or choose **Cancel** to not add them\. 27 | 28 | Key\-value tags can only be added one at a time before saving\. To add more than one key\-value tag, repeat the previous steps\. 29 | ![\[Key-value tags in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-key-value-tag.png) 30 | 31 | ## Next steps 32 | 33 | For more information about tasks that you can perform after adding tags to a resource, see the following guides: 34 | + [Organizing your Amazon Lightsail resources using tags](amazon-lightsail-organizing-resources-using-tags.md) 35 | + [Using tags to organize costs for your Amazon Lightsail resources](amazon-lightsail-organizing-costs-using-tags.md) 36 | + [Using tags to control access to your Amazon Lightsail resources](amazon-lightsail-controlling-access-using-tags.md) 37 | + [Deleting tags in Amazon Lightsail](amazon-lightsail-deleting-tags.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-viewing-database-logs-and-history.md: -------------------------------------------------------------------------------- 1 | # Viewing your database logs and history in Amazon Lightsail 2 | 3 | *Last updated: January 3, 2020* 4 | 5 | View your database logs and history of changes in the Amazon Lightsail console\. Database logs provide useful information that could help you diagnose issues with your database\. Likewise, database history shows you changes made to your database, which allows you to associate problems with a recent change\. 6 | 7 | **To view your database logs** 8 | 9 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 10 | 11 | 1. On the Lightsail home page, choose the **Databases** tab\. 12 | 13 | 1. Choose the name of the database for which you want to view logs\. 14 | 15 | 1. Choose the **Logs and history** tab\. 16 | 17 | The page displays the database logs and history of changes made to your database\. 18 | 19 | 1. Choose a database log\. The following database logs are available: 20 | 21 | **MySQL database logs** 22 | + **Error log** — A record of mysqld startup and shutdown times\. It also contains diagnostic messages such as errors, warnings, and notes that occur during server startup and shutdown, and while the server is running\. For more information, see the error log article in the [MySQL 5\.6](https://dev.mysql.com/doc/refman/5.6/en/keywords.html), [MySQL 5\.7](https://dev.mysql.com/doc/refman/5.7/en/keywords.html), or [MySQL 8\.0](https://dev.mysql.com/doc/refman/8.0/en/keywords.html) documentation\. 23 | + **General log** — A general record of what mysqld is doing\. The server writes information to this log when clients connect or disconnect, and logs each SQL statement received from clients\. For more information, see the general query log article in the [MySQL 5\.6](https://dev.mysql.com/doc/refman/5.6/en/keywords.html), [MySQL 5\.7](https://dev.mysql.com/doc/refman/5.7/en/keywords.html), or [MySQL 8\.0](https://dev.mysql.com/doc/refman/8.0/en/keywords.html) documentation\. 24 | + **Slow query log** — A record of SQL statements that took more than long\_query\_time seconds to run, and required at least min\_examined\_row\_limit rows to be examined\. For more information, see the slow query log article in the [MySQL 5\.6](https://dev.mysql.com/doc/refman/5.6/en/keywords.html), [MySQL 5\.7](https://dev.mysql.com/doc/refman/5.7/en/keywords.html), or [MySQL 8\.0](https://dev.mysql.com/doc/refman/8.0/en/keywords.html) documentation\. 25 | **Note** 26 | The general and slow query logs are disabled by default for MySQL databases\. You can enable these logs, and begin collecting data, by updating a few database parameters\. For more information, see [Enabling the MySQL database general and slow query logs in Amazon Lightsail](amazon-lightsail-enabling-mysql-general-and-slow-query-logs)\. 27 | 28 | **PostgreSQL database logs** 29 | + **Postgres log** — A record of database startup and shutdown times\. It can also contain diagnostics, such as errors, warnings, notices, and debug messages that occur during database startup, shutdown, and while the database is running\. For more information, see the error reporting and logging article in the [PostgreSQL 9\.6](https://www.postgresql.org/docs/9.6/runtime-config-logging.html), [PostgreSQL 10](https://www.postgresql.org/docs/10/runtime-config-logging.html), [PostgreSQL 11](https://www.postgresql.org/docs/11/runtime-config-logging.html), or [PostgreSQL 12](https://www.postgresql.org/docs/12/runtime-config-logging.html) documentation\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-domain-register-other-dns-service-procedure.md: -------------------------------------------------------------------------------- 1 | # Updating your domain name servers to use another DNS service 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | You can use an Amazon Lightsail DNS zone to manage the DNS records for a domain that you registered using Lightsail\. Or, if you'd like, you can transfer management of DNS records for the domain to another DNS hosting provider\. In this guide, we show you how to transfer management of DNS records for a domain you registered with Lightsail to another DNS hosting provider\. 6 | 7 | **Important** 8 | Any changes you make to the DNS of your domain might require several hours to propagate through the internet’s DNS\. Because of this, you should keep the DNS records of your domain in place at your current DNS hosting provider until the transfer of management is done\. This ensures that traffic for your domain continues to route to your resources uninterrupted while the transfer takes place\. 9 | 10 | **Contents** 11 | + [Complete the prerequisites](#other-dns-service-prerequisites) 12 | + [Add records to the DNS zone](#other-dns-service-add-records-dns-zone) 13 | 14 | ## Complete the prerequisites 15 | 16 | Complete the following prerequisites if you haven’t already done so: 17 | 18 | 1. Register a domain name\. You can register a domain name using Lightsail\. For more information, see [Registering a New Domain in Amazon Lightsail](amazon-lightsail-register-new-domain.md)\. 19 | 20 | 1. Use the process that’s provided by your DNS service to get the name servers for your domain\. 21 | 22 | ## Add records to the DNS zone 23 | 24 | Complete the following procedure to add the name servers for another DNS hosting provider into your registered domain in Lightsail\. 25 | 26 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 27 | 28 | 1. Choose the **Domains & DNS** tab\. 29 | 30 | 1. Choose the name of the domain that you want to configure to use another DNS service\. 31 | 32 | 1. Choose **Edit Name Servers**\. 33 | 34 | 1. Change the names of the name servers to the name servers that you got from your DNS service when you completed the prerequisites\. 35 | 36 | 1. Choose **Save**\. 37 | 38 | **Additional information about domains** 39 | 40 | The following articles can help you manage domains in Lightsail: 41 | + [DNS in Amazon Lightsail](understanding-dns-in-amazon-lightsail.md) 42 | + [Domain registration in Amazon Lightsail](amazon-lightsail-domain-registration.md) 43 | + [Formatting domain names in Amazon Lightsail](amazon-lightsail-domain-name-format.md) 44 | + [Managing a Lightsail domain in Amazon Route 53](amazon-lightsail-manage-domain-advanced.md) 45 | + [Creating a DNS zone to manage your domain’s DNS records in Amazon Lightsail](lightsail-how-to-create-dns-entry.md) 46 | + [Managing domain registration renewal in Amazon Lightsail](amazon-lightsail-domain-manage-auto-renew.md) 47 | + [Edit or delete a DNS zone in Amazon Lightsail](amazon-lightsail-edit-or-delete-a-dns-zone.md) 48 | + [Point your domain to your Lightsail load balancer](add-alias-record-for-lightsail-load-balancer.md) 49 | + [Pointing your domains to your Amazon Lightsail distributions](amazon-lightsail-point-domain-to-distribution.md) 50 | + [Point your domain to a Lightsail instance](amazon-lightsail-routing-to-instance.md) 51 | + [Routing traffic for a domain in Amazon Lightsail to a Lightsail container service](amazon-lightsail-point-domain-to-container-service.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-domain-whois-rdap.md: -------------------------------------------------------------------------------- 1 | # Viewing information about domains that are registered with Amazon Registrar 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | You can view information about \.com, \.net, and \.org domains that were registered using Amazon Lightsail and Amazon Route 53, for which Amazon Registrar is the registrar\. This information includes details such as when the domain was originally registered and contact information for the domain owner and for the technical and administrative contacts\. 6 | 7 | Note the following: 8 | 9 | **Emailing domain contacts when privacy protection is active** 10 | If privacy protection is active for the domain, contact information for the registrant, technical, and administrative contacts is replaced with contact information for the Amazon Registrar privacy service\. For example, if the **example\.com** domain is registered with Amazon Registrar and if privacy protection is active, the value of **Registrant Email** in the response to a WHOIS query would be similar to `owner1234@example.com.whoisprivacyservice.org`\. 11 | To contact one or more domain contacts when privacy protection is active, send an email to the corresponding email addresses\. We'll automatically forward your email to the applicable contact\. 12 | 13 | **Reporting abuse** 14 | To report any illegal activity or violation of the [Acceptable Use Policy](http://aws.amazon.com/route53/amazon-registrar-policies/#acceptable-use-policy) , including inappropriate content, phishing, malware, or spam, send an email to **abuse@amazon\.com**\. 15 | 16 | **To view information about domains that are registered with Amazon Registrar** 17 | 18 | 1. In a web browser, go to one of the following websites\. Both websites display the same information\. However, they use different protocols and display the information in different formats: 19 | + **WHOIS**: [https://registrar\.amazon\.com/whois](https://registrar.amazon.com/whois) 20 | + **RDAP**: [https://registrar\.amazon\.com/rdap](https://registrar.amazon.com/rdap) 21 | 22 | 1. Enter the name of the domain that you want to view information about, and choose **Search**\. If the domain you search for was not registered using Amazon Lightsail or Route 53, then you will see a message stating that the domain is not in the registrar database\. 23 | 24 | **Additional information about domains** 25 | 26 | The following articles can help you manage domains in Lightsail: 27 | + [DNS in Amazon Lightsail](understanding-dns-in-amazon-lightsail.md) 28 | + [Domain registration in Amazon Lightsail](amazon-lightsail-domain-registration.md) 29 | + [Formatting domain names in Amazon Lightsail](amazon-lightsail-domain-name-format.md) 30 | + [Managing a Lightsail domain in Amazon Route 53](amazon-lightsail-manage-domain-advanced.md) 31 | + [Creating a DNS zone to manage your domain’s DNS records in Amazon Lightsail](lightsail-how-to-create-dns-entry.md) 32 | + [Managing domain registration renewal in Amazon Lightsail](amazon-lightsail-domain-manage-auto-renew.md) 33 | + [Edit or delete a DNS zone in Amazon Lightsail](amazon-lightsail-edit-or-delete-a-dns-zone.md) 34 | + [Point your domain to your Lightsail load balancer](add-alias-record-for-lightsail-load-balancer.md) 35 | + [Pointing your domains to your Amazon Lightsail distributions](amazon-lightsail-point-domain-to-distribution.md) 36 | + [Point your domain to a Lightsail instance](amazon-lightsail-routing-to-instance.md) 37 | + [Routing traffic for a domain in Amazon Lightsail to a Lightsail container service](amazon-lightsail-point-domain-to-container-service.md) -------------------------------------------------------------------------------- /doc_source/how-to-create-larger-instance-from-snapshot-using-console.md: -------------------------------------------------------------------------------- 1 | # Creating a larger instance, block storage disk, or database from a snapshot in Amazon Lightsail 2 | 3 | *Last updated: May 05, 2022* 4 | 5 | It happens\. Your cloud project is growing and you need more compute power right away\! We can help you with that\. To upsize your Lightsail instance, block storage disk, or database, create a snapshot of your resource, and then create a new, larger version of that resource using the snapshot\. 6 | 7 | **Note** 8 | You cannot create a resource from a snapshot using a smaller plan size than the original resource\. For example, you can't go from an 8 GB instance to a 2 GB instance\. 9 | The default public IPv4 address that is assigned to your instance when you create it will change when you stop and start your instance\. You can optionally create and attach a static IPv4 address to your instance\. By using a static IP address, you can mask the failure of an instance or software by rapidly remapping the address to another instance in your account\. Alternatively, you can specify the static IP address in a DNS record for your domain, so that your domain points to your instance\. For more information, see [IP addresses in Amazon Lightsail](understanding-public-ip-and-private-ip-addresses-in-amazon-lightsail.md)\. 10 | 11 | ## Prerequisites 12 | 13 | You'll need a snapshot of your Lightsail instance, block storage disk, or database\. For more information, see [Snapshots in Amazon Lightsail](understanding-instance-snapshots-in-amazon-lightsail.md)\. 14 | 15 | ## Create your resource 16 | 17 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 18 | 19 | 1. Choose the **Snapshots** tab\. 20 | 21 | 1. Find the Lightsail resource whose snapshot you want to use to create a new, larger resource, and choose the right\-arrow to expand the list of snapshots\. 22 | 23 | 1. Choose the ellipsis icon next to the snapshot you want to use, and choose **Create new**\. 24 | ![\[Create new resource from a snapshot in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-create-resource-from-snapshot-menu-option.png) 25 | 26 | 1. On the **Create** page, you have a few optional settings to choose from\. For example, you can change the Availability Zone\. For instances, you can [add a launch script](lightsail-how-to-configure-server-additional-data-shell-script.md), or [change the SSH key you use to connect to it](understanding-ssh-in-amazon-lightsail.md)\. 27 | 28 | You can accept all the defaults and move on to the next step\. 29 | 30 | 1. Choose the plan \(or *bundle*\) for your new resource\. At this point, you can choose a larger bundle size than the original resource, if you'd like\. 31 | **Note** 32 | You cannot create the resource using a smaller plan size than the original resource\. The bundle options that are smaller than the original resource will be unavailable\. 33 | 34 | 1. Enter a name for your instance\. 35 | 36 | Resource names: 37 | + Must be unique within each AWS Region in your Lightsail account\. 38 | + Must contain 2 to 255 characters\. 39 | + Must start and end with an alphanumeric character or number\. 40 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 41 | 42 | 1. Choose **Create**\. 43 | 44 | Lightsail takes you to the management page for your new resource, and you can start managing it\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-securing-windows-server-amazon-ec2-instances.md: -------------------------------------------------------------------------------- 1 | # Securing a Windows Server instance in Amazon EC2 created from an Amazon Lightsail snapshot 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | To improve the security of a Windows Server instance in Amazon Elastic Compute Cloud \(Amazon EC2\) created from an Amazon Lightsail snapshot, we recommend that you change the default administrator password\. This removes the association between your Lightsail key pairs and your new Windows Server instance in Amazon EC2\. 6 | 7 | **Note** 8 | If you created Linux or Unix instances in Amazon EC2 from a Lightsail snapshot, then you should perform a few steps to secure those instances\. For more information, see [Securing a Linux or Unix instance in Amazon EC2 created from an Amazon Lightsail snapshot](amazon-lightsail-securing-linux-unix-amazon-ec2-instances.md)\. 9 | 10 | **Contents** 11 | + [Connect to your Windows Server instance in Amazon EC2](#connect-to-your-windows-server-instance-in-ec2) 12 | + [Change the default administrator password of your Windows Server instance in Amazon EC2](#change-the-password-of-your-windows-server-instance-in-ec2) 13 | 14 | ## Connect to your Windows Server instance in Amazon EC2 15 | 16 | To change your Windows Server administrator password, connect to your Windows Service instance in Amazon EC2 using Remote Desktop Protocol \(RDP\)\. To learn how to connect to your instance, see [Connecting to a Windows Server instance in Amazon EC2 created from an Amazon Lightsail snapshot](amazon-lightsail-connecting-to-windows-server-amazon-ec2-instances.md)\. 17 | 18 | Continue to the [Change the default administrator password of your Windows Server instance in Amazon EC2](#change-the-password-of-your-windows-server-instance-in-ec2) section of this guide after you’re connected to your instance in Amazon EC2\. 19 | 20 | ## Change the default administrator password of your Windows Server instance in Amazon EC2 21 | 22 | Change the default password on your Windows Server instance to remove the association between your Lightsail key pairs and your new Windows Server instance in Amazon EC2\. 23 | 24 | **To change the default administrator password of your Windows Server instance in Amazon EC2** 25 | 26 | 1. After you establish an RDP connection to your instance, open a Command Prompt and enter the following command\. 27 | 28 | ``` 29 | net user Administrator "Password" 30 | ``` 31 | 32 | In the command, replace *Password* with your new password\. 33 | 34 | **Example:** 35 | 36 | ``` 37 | net user Administrator "%4=Bwk^GEAg8$u@5" 38 | ``` 39 | 40 | You should see a result similar to the following: 41 | ![\[Password reset on Windows Server in Amazon EC2.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-ec2-window-server-password-reset.png) 42 | 43 | 1. Store the new password in a safe place\. You cannot retrieve the new password using the Amazon EC2 console\. The console can retrieve only the default password\. If you attempt to connect to the instance using the default password after changing it, an error message appears stating that your credentials did not work\. 44 | 45 | If you lose your password or it expires, you can generate a new password\. For password reset procedures, see [Resetting a Lost or Expired Windows Administrator Password](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ResettingAdminPassword.html) in the Amazon EC2 documentation\. -------------------------------------------------------------------------------- /doc_source/troubleshooting-block-storage-disk-issues.md: -------------------------------------------------------------------------------- 1 | # Troubleshooting disk issues in Lightsail 2 | 3 | *Last updated: March 20, 2023* 4 | 5 | You might encounter errors with your block storage disks in Lightsail\. This topic identifies common issues and workarounds for those errors\. 6 | 7 | ## General disk errors 8 | 9 | Choose the issue below that best describes your problem, and follow the links to fix the issue\. If you encounter an issue that's not in the list, use the **Questions? Comments?** link at the bottom of this page to submit feedback or contact [AWS Support](https://aws.amazon.com/premiumsupport/)\. 10 | 11 | **I can't delete a disk because it's still attached to an instance\.** 12 | Try detaching the disk from your instance first, and then try to delete the disk\. For more information, see [Detach and delete a block storage disk in Lightsail](detach-and-delete-block-storage-disks.md)\. 13 | *Actual error message:* **You can't perform this operation because the disk is still attached to a Lightsail instance: *YOUR\_INSTANCE*** 14 | 15 | **My disk has a status of error\.** 16 | The **error** status indicates that the underlying hardware related to your Lightsail disk has failed\. You can restore the disk from a recent snapshot, otherwise the data associated with the disk is unrecoverable\. For more information, see [Creating a block storage disk from a snapshot in Amazon Lightsail](create-new-block-storage-disk-from-snapshot.md)\. 17 | You are not billed for disks with a status of **error**\. 18 | 19 | **I can't detach a disk because the Lightsail instance is still running\.** 20 | Try stopping your instance first, and then try to detach the disk\. For more information, see [Stop an instance in Lightsail](lightsail-how-to-start-stop-or-restart-your-instance-virtual-private-server.md)\. 21 | *Actual error message:* **You can't detach this disk right now\. The state of this disk is: *DISK\_STATE*** 22 | 23 | **I can't specify a custom disk size above 16 TB \(16,384 GB\)\.** 24 | Try creating a smaller disk\. Additional disks can be up to 16 TB\. If your disk is less than 16 TB and you still can't create it, you might encounter the next error in the list \(too many big disks\)\. That's because you can't have more than 20 TB in additional disk storage across your AWS account\. For more information, see [Block storage disks in Lightsail](elastic-block-storage-and-ssd-disks-in-amazon-lightsail.md)\. 25 | *Actual error message:* **The size of a block storage disk must be between 8 and 16384 GB\.** 26 | 27 | **I can't create any more disks in Lightsail\.** 28 | You might have reached your quota for the number of disks you can create\. Or you might have created too many big disks \(the total size of disk storage can't exceed 20 TB\) in your AWS account\. For more information, see [Block storage disks in Lightsail](elastic-block-storage-and-ssd-disks-in-amazon-lightsail.md)\. 29 | *Actual error message:***You've reached the maximum size limit of all disks in this account\.** or **You've reached the limit of disks in this account\.** 30 | 31 | **I can't attach my disk to my Lightsail instance** 32 | If you encounter the following error, you need to recreate your disk in the same AWS Region and Availability Zone as the instance where you plan to attach the disk\. 33 | 34 | ![\[Block storage disk can't be attached because it's in the wrong Availability Zone\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/block-storage-disk-in-different-zone-than-lightsail-instance.png) 35 | *Actual error message:* **There are currently no instances in the *AWS Region* that can use this disk\.** -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-domain-update-contacts.md: -------------------------------------------------------------------------------- 1 | # Updating contact information for a domain 2 | 3 | *Last updated: November 1, 2022* 4 | 5 | When you register a domain with Amazon Lightsail, you specify contact information for your domain\. Following are three types of contact information: 6 | + Registrant: Owner of the domain 7 | + Administrator: Person responsible for administering your domain 8 | + Technical: Person responsible for making technical changes to your domain 9 | 10 | Your domain’s contact information is used to verify ownership of your domain and to keep you updated about any information related to your domain name\. 11 | 12 | **Topics** 13 | + [Who is the owner of a domain?](#who-is-domain-owner) 14 | + [Updating contact information for a domain](#update-contacts-update-domain-contact-info) 15 | 16 | ## Who is the owner of a domain? 17 | 18 | When the contact type is **Person** and you change the **First Name** or **Last Name** fields for the registrant contact, you change the owner of the domain\. 19 | 20 | When the contact type is any value except **Person** and you change **Organization**, you change the owner of the domain\. 21 | 22 | The following actions happen when you change the contact information for a domain that is currently registered with Lightsail: 23 | + If you change contact information for the domain, we send an email notification to the registrant contact about the change\. This email comes from **noreply@amazon\.com**\. For most changes, the registrant contact is not required to respond\. 24 | + For changes to contact information that also constitute a change in ownership, we send the registrant contact an additional email\. ICANN, the organization that maintains a central database of domain names, requires that the registrant contact confirm receiving the email\. 25 | 26 | ## Updating contact information for a domain 27 | 28 | To update contact information for a domain, perform the following procedure\. 29 | 30 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 31 | 32 | 1. Choose the **Domains & DNS** tab\. 33 | 34 | 1. Choose the name of the domain that you want to update\. 35 | 36 | 1. Choose the **Contact info** tab\. Then, choose **Edit contact**\. 37 | 38 | 1. Update the applicable values\. For more information, see [Values that you specify when you register or transfer a domain](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-register-values-specify.html) in the Amazon Route 53 Developer Guide\. 39 | 40 | 1. Choose **Save**\. 41 | 42 | **Additional information about domains** 43 | 44 | The following articles can help you manage domains in Lightsail: 45 | + [DNS in Amazon Lightsail](understanding-dns-in-amazon-lightsail.md) 46 | + [Domain registration in Amazon Lightsail](amazon-lightsail-domain-registration.md) 47 | + [Formatting domain names in Amazon Lightsail](amazon-lightsail-domain-name-format.md) 48 | + [Managing a Lightsail domain in Amazon Route 53](amazon-lightsail-manage-domain-advanced.md) 49 | + [Creating a DNS zone to manage your domain’s DNS records in Amazon Lightsail](lightsail-how-to-create-dns-entry.md) 50 | + [Managing domain registration renewal in Amazon Lightsail](amazon-lightsail-domain-manage-auto-renew.md) 51 | + [Edit or delete a DNS zone in Amazon Lightsail](amazon-lightsail-edit-or-delete-a-dns-zone.md) 52 | + [Point your domain to your Lightsail load balancer](add-alias-record-for-lightsail-load-balancer.md) 53 | + [Pointing your domains to your Amazon Lightsail distributions](amazon-lightsail-point-domain-to-distribution.md) 54 | + [Point your domain to a Lightsail instance](amazon-lightsail-routing-to-instance.md) 55 | + [Routing traffic for a domain in Amazon Lightsail to a Lightsail container service](amazon-lightsail-point-domain-to-container-service.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-organizing-costs-using-tags.md: -------------------------------------------------------------------------------- 1 | # Using tags to organize costs for your Amazon Lightsail resources 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | You can use tags in Amazon Lightsail to organize your AWS billing to reflect your own cost structure\. To do this, add key\-value tags to your Lightsail resources\. Then activate those tags in the AWS Billing and Cost Management console\. Finally, sign up to get your AWS account bill with the tag key values included in your cost allocation report\. This guide provides the steps to set this up\. 6 | 7 | **Note** 8 | For more information about tags in Lightsail, what resources can be tagged, and tag restrictions, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 9 | 10 | **Important** 11 | Lightsail database snapshots cannot be tracked in the cost allocation report at this time, even after a cost allocation tag is added to them\. 12 | 13 | ## Step 1: Add key\-value tags to Lightsail resources 14 | 15 | Add key\-value tags to the Lightsail resources that you want to organize in your billing console\. For more information about key\-value tags, see [Adding tags to a resource in Amazon Lightsail](amazon-lightsail-adding-tags-to-a-resource.md)\. 16 | 17 | It's a good idea to devise a set of tag keys that represent how you want to organize your costs\. Your cost allocation report displays the tag keys as additional columns with the applicable values for each row\. Therefore, it's more efficient to track your costs if you use a consistent set of tag keys\. For example, you can tag several Lightsail resources with a specific cost center\. You do this with a “Cost center” key and a numerical value pairing\. Then organize your billing information to see the billing for that cost center across several resources\. The following example shows key\-value tags that could be used to organize cost allocation: 18 | 19 | ![\[Key-value tags for cost allocation.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-key-value-tags-for-cost-allocation.png) 20 | 21 | ## Step 2: Activate user\-defined cost allocation tags 22 | 23 | After you add the necessary tags to your Lightsail resources, activate them for cost allocation in the Billing and Cost Management console\. For example, if you created a “Cost center” key tag, then activate that key tag in the Billing and Cost Management console to generate cost\-allocation reports for that tag\. For more information, see [Activating user\-defined cost allocation tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/activating-tags.html) in the AWS Billing and Cost Management documentation\. 24 | 25 | ## Step 3: Set up the cost allocation report, and view it 26 | 27 | The monthly cost allocation report lists the AWS usage for your account by product category and linked account user\. The report contains the same line items as your detailed billing report and additional columns for your tag keys\. To set up the monthly cost allocation report, see [Setting up a monthly cost allocation report](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/configurecostallocreport.html#allocation-report) in the AWS Billing and Cost Management documentation\. 28 | 29 | When you set up the cost allocation report, you defined an Amazon Simple Storage Service \(Amazon S3\) bucket where the report is saved\. Open the Amazon S3 bucket that you defined and open the cost allocation report after it becomes available\. For more information about the contents of the cost allocation report, see [Viewing a cost allocation report](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/configurecostallocreport.html#allocation-viewing) in the AWS Billing and Cost Management documentation\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-choosing-a-database.md: -------------------------------------------------------------------------------- 1 | # Choosing an Amazon Lightsail database 2 | 3 | *Last updated: January 3, 2020* 4 | 5 | Amazon Lightsail provides the latest major versions of the MySQL and PostgreSQL databases\. This guide helps you decide which database is right for your project\. 6 | 7 | ## Compare managed databases in Lightsail 8 | 9 | **MySQL** 10 | 11 | MySQL 5\.7, and 8\.0 are available in Lightsail\. MySQL is the most widely adopted open source relational database\. It serves as the primary relational data store for many popular websites, applications, and commercial products\. MySQL is a reliable, stable, and secure SQL\-based database management system, with more than 20 years of community\-backed development and support\. The MySQL database is suitable for a wide variety of use cases, including mission\-critical apps and dynamic websites\. It also functions as an embedded database for software, hardware, and appliances\. 12 | 13 | For more information, see the following MySQL documentation: 14 | + [MySQL 5\.7 documentation](https://dev.mysql.com/doc/refman/5.7/en/) 15 | + [MySQL 8\.0 documentation](https://dev.mysql.com/doc/refman/8.0/en/) 16 | 17 | **PostgreSQL** 18 | 19 | PostgreSQL 9, 10, 11, and 12 are available in Lightsail\. PostgreSQL is a powerful, open source object\-relational database system with over 30 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance\. 20 | 21 | There is a wealth of information to be found describing how to install and use PostgreSQL through the [official documentation](https://www.postgresql.org/docs/)\. The [PostgreSQL community](https://www.postgresql.org/community/) provides many helpful places to become familiar with the technology, discover how it works, and find career opportunities\. 22 | 23 | For more information, see the following PostgreSQL documentation: 24 | + [PostgreSQL 9\.6 documentation](https://www.postgresql.org/docs/9.6/index.html) 25 | + [PostgreSQL 10 documentation](https://www.postgresql.org/docs/10/index.html) 26 | + [PostgreSQL 11 documentation](https://www.postgresql.org/docs/11/index.html) 27 | + [PostgreSQL 12 documentation](https://www.postgresql.org/docs/12/index.html) 28 | 29 | **Note** 30 | Lightsail also offers a Windows Server 2016 instance with SQL Server 2016 Express\. For more information, see [Choose an Amazon Lightsail instance image](compare-options-choose-lightsail-instance-image.md)\. 31 | 32 | ## Optimizing data import 33 | 34 | Several database plans are available in Lightsail, each with specific memory, vCPU, storage, and data transfer allowance specifications\. Because each database plan has these specifications, it is important that you choose an appropriately\-sized database plan for the amount of data that you want to import into your new Lightsail database\. Your data import may be slowed if you choose a plan that is under your size requirements\. Use the following guidelines to select the appropriate database plan for your data import requirement: 35 | + **Micro $15 USD/month database plan** — Data import may be slowed if you transfer more than 10 GB of data\. 36 | + **Small $30 USD/month database plan** — Data import may be slowed if you transfer more than 20 GB of data\. 37 | + **Medium $60 USD/month database plan** — Data import may be slowed if you transfer more than 85 GB of data\. 38 | + **Large $115 USD/month database plan** — Data import may be slowed if you transfer more than 156 GB of data\. 39 | 40 | **Note** 41 | For more information about importing data into your database, see [Importing data into your MySQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-mysql-database.md) or [Importing data into your PostgreSQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-postgres-database.md)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-cloudformation-stacks.md: -------------------------------------------------------------------------------- 1 | # AWS CloudFormation stacks for Amazon Lightsail 2 | 3 | *Last updated: November 28, 2018* 4 | 5 | Amazon Lightsail uses AWS CloudFormation to create Amazon Elastic Compute Cloud \(Amazon EC2\) instances from exported snapshots\. A CloudFormation stack is created when you request to create an Amazon EC2 instance using the Lightsail console or Lightsail API\. The stack performs a series of actions in your Amazon Web Services \(AWS\) account to create all of the related resources for the instance, such as the Amazon EC2 instance from an Amazon Machine Image \(AMI\), the Elastic Block Store \(EBS\) system volume from an EBS snapshot, and the security group for the instance\. To learn more about AWS CloudFormation stacks, see [Working with Stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacks.html) in the AWS CloudFormation documentation\. 6 | 7 | You can access the AWS CloudFormation stacks through the Lightsail console or in the AWS CloudFormation console\. This guide shows you how to access both\. 8 | 9 | **Note** 10 | The AWS CloudFormation stack used to create your Amazon EC2 resources is permanently linked to your Amazon EC2 resources\. If you delete the stack, then all related resources are automatically deleted\. Because of this, you should not delete any of the AWS CloudFormation stacks created by Lightsail, and instead delete your Amazon EC2 resources using the EC2 console\. 11 | 12 | ## Accessing the AWS CloudFormation stacks through the Lightsail console 13 | 14 | After you choose to create an instance in Amazon EC2 using the Lightsail console or the Lightsail API, an AWS CloudFormation stack is created and its status is tracked using the task monitor\. To learn more about the task monitor, see [Task monitor in Amazon Lightsail](amazon-lightsail-task-monitor.md)\. 15 | 16 | **To view your AWS CloudFormation stacks in the Lightsail console** 17 | 18 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 19 | 20 | 1. Choose the task monitor in the top navigation pane\. 21 | 22 | 1. To access a CloudFormation stack for a previously created Amazon EC2 instance, choose **View details** for a task labeled with **Creating resources in Amazon EC2** or **Created resources in Amazon EC2**\. 23 | ![\[The task monitor in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-task-manager-cloud-formation-stack.png) 24 | 25 | 1. The confirmation page that appears lists the CloudFormation stack for the task\. Choose the stack name to open the stack details in the AWS CloudFormation console\. 26 | ![\[AWS CloudFormation stack details in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-console-cloud-formation-stack.png) 27 | 28 | ## Accessing the stacks in the AWS CloudFormation console 29 | 30 | You can also access your stack details through the [AWS CloudFormation console](https://console.aws.amazon.com/cloudformation)\. The stacks created by Lightsail begin with “Lightsail\-stack” and have a description of “CloudFormation stack used to create Amazon EC2 resources” as shown in the following screenshot\. 31 | 32 | Stacks with a **CREATE\_IN\_PROGRESS** status are in the process of creating Amazon EC2 resources from your exported Lightsail snapshots\. Stacks with a **CREATE\_COMPLETED** status have completed the process of creating Amazon EC2 resources\. To view the resources created by a stack, choose the checkbox next to the stack name, and then choose the **Resources** tab\. 33 | 34 | ![\[AWS CloudFormation stack details.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-cloud-formation-stack-details.png) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-troubleshooting-browser-based-ssh-rdp-client-connection.md: -------------------------------------------------------------------------------- 1 | # Troubleshooting connection issues with the Amazon Lightsail browser\-based SSH or RDP client 2 | 3 | *Last updated: March 18, 2019* 4 | 5 | You may get an error message when trying to connect to an instance using the browser\-based SSH or RDP clients available in the Amazon Lightsail console\. The possible reasons for this error are discussed in the following sections\. 6 | 7 | ## Error message: Can’t connect 8 | 9 | The SSH and RDP browser\-based clients use host key or certificate validation to authenticate an instance when trying to connect to it\. If the instance presents a host key or certificate that doesn’t match the one that Lightsail has on record, one of two error messages display\. Both error messages are shown and described in this section\. 10 | 11 | **Can’t connect, reset record** 12 | 13 | The following error message displays when there’s a host key or certificate mismatch, and Lightsail determines that the mismatch might have been caused by a recent operating system upgrade, or a deliberate update to the host key or certificate by you or another user\. In this case, Lightsail has determined that the host key or certificate mismatch was not caused by a bad actor on the network between your browser and the instance\. 14 | 15 | ![\[Host key or certificate mismatch error for the Lightsail browser-based SSH or RDP client.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-browser-ssh-rdp-cant-connect-resest-record.png) 16 | 17 | Choose **Reset record** if you expected the mismatch\. This action deletes the host key or certificate that Lightsail has on record for the instance, and permits the browser\-based SSH or RDP session to connect to the instance\. 18 | 19 | You can also delete the host key or certificate that Lightsail has on record by using the following AWS Command Line Interface \(AWS CLI\) command\. For *InstanceName*, enter the name of your instance for which you want to delete the known host key or certificate\. For *Region*, enter the AWS Region of the instance\. 20 | 21 | ``` 22 | aws lightsail delete-known-host-keys --region Region --instance-name InstanceName 23 | ``` 24 | 25 | Example: 26 | 27 | ``` 28 | aws lightsail delete-known-host-keys --region us-west-2 --instance-name WordPress-512MB-Oregon-1 29 | ``` 30 | 31 | **Note** 32 | For more information about the AWS CLI, see [Configuring the AWS Command Line Interface to work with Amazon Lightsail](lightsail-how-to-set-up-and-configure-aws-cli.md)\. 33 | 34 | **Can’t connect, contact customer support** 35 | 36 | The following error message displays when there’s a host key or certificate mismatch, and Lightsail determines that there is suspicious activity that warrants further investigation, such as a man\-in\-the\-middle attack\. 37 | 38 | ![\[Host key or certificate mismatch error for the Lightsail browser-based SSH or RDP client.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-browser-ssh-rdp-cant-connect.png) 39 | 40 | This error message means that you can’t connect to the instance using the browser\-based SSH or RDP client\. [Contact support](https://console.aws.amazon.com/support/home#/) for assistance\. 41 | 42 | ## Error message: Can’t connect right now 43 | 44 | The following error message displays when you try to connect to an instance that hasn’t yet started after it’s created, rebooted, or restarted\. Wait a few minutes and then choose **Reconnect** to try again\. 45 | 46 | ![\[Instance unavailable when trying to connect using the Lightsail browser-based SSH or RDP client.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-browser-ssh-rdp-cant-connect-right-now.png) 47 | 48 | If you still can’t connect, [contact support](https://console.aws.amazon.com/support/home#/)\. -------------------------------------------------------------------------------- /doc_source/extending-windows-server-storage-space-in-amazon-lightsail.md: -------------------------------------------------------------------------------- 1 | # Extending the storage space of your Windows Server instance in Amazon Lightsail 2 | 3 | *Last updated: September 3, 2020* 4 | 5 | After you use a snapshot to create a new Windows Server instance with a larger plan, you may see that the available storage space is lower than that specified by the plan\. This is typically because the additional storage space provided by the larger plan has not been allocated; therefore, it’s not being used by the active volume\. The steps in this topic show you how to extend the file system of your Windows Server instance to use the maximum storage space available\. 6 | 7 | **Note** 8 | This scenario happens only when you create a Windows Server instance using a snapshot that was created before running the System Preparation \(Sysprep\) utility\. For more information, see [Creating a snapshot of your Windows Server instance in Amazon Lightsail](prepare-windows-based-instance-and-create-snapshot.md)\. 9 | 10 | **To extend the file system for a Windows Server instance** 11 | 12 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 13 | 14 | 1. On the Lightsail home page, choose the RDP client icon for the instance you want to connect to\. 15 | ![\[Open the browser-based RDP client with quick connect.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/connect-to-windows-instance-using-rdp-connection-shortcut.png) 16 | 17 | The browser\-based RDP client window opens, as shown in the following example: 18 | ![\[Browser-based RDP client in Lightsail.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-web-based-rdp-client.png) 19 | 20 | 1. On the taskbar, choose the Windows icon, then choose one of the following options: 21 | 22 | 1. On Windows Server 2019 and Windows Server 2016 instances, choose **Start**, then choose **Windows Administrative Tools**\. 23 | 24 | 1. On Windows Server 2012 instances, choose **Start**, then choose **Administrative Tools**\. 25 | ![\[Windows Administrative Tools\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-windows-administrative-tools.png) 26 | 27 | 1. Choose **Computer Management**\. 28 | 29 | 1. In the left pane of the Computer Management console, choose **Disk Management**\. 30 | 31 | 1. On the **Actions** menu, choose **Rescan Disks**\. 32 | 33 | You may see unallocated space associated with a disk\. Extend the active volume on the disk to use the unallocated space\. 34 | ![\[Unallocated disk space in Windows Disk Management\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-windows-unallocated-space.png) 35 | 36 | 1. Right\-click the active volume on the same disk as the unallocated space, then choose **Extend Volume**\. 37 | ![\[Extend volume in Windows Disk Management\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-windows-extend-volume.png) 38 | 39 | 1. When the Extend Volume wizard opens, choose **Next**\. 40 | 41 | 1. In the **Select the amount of space in MB** field, enter the number of megabytes by which to extend the volume\. Normally, you set this to the maximum unallocated space\. The value you enter is the amount of space that you are adding, not the final size of the volume\. 42 | ![\[Select unallocated space in the Windows Extend Volume wizard\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-windows-select-unallocated-space.png) 43 | 44 | 1. Complete the Extend Volume wizard\. 45 | 46 | The active volume is extended to use the unallocated space that you specified\. The following example shows all of the unallocated space chosen\. 47 | ![\[Allocated disk space in Windows Disk Management\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-windows-allocated-space.png) -------------------------------------------------------------------------------- /doc_source/what-is-amazon-lightsail.md: -------------------------------------------------------------------------------- 1 | # What is Amazon Lightsail? 2 | 3 | *Last updated: April 1, 2021* 4 | 5 | Amazon Lightsail is the easiest way to get started with Amazon Web Services \(AWS\) for developers who need to build websites or web applications\. It includes everything you need to launch your project quickly \- instances \(virtual private servers\), container services, managed databases, content delivery network \(CDN\) distributions, load balancers, SSD\-based block storage, static IP addresses, DNS management of registered domains, and resource snapshots \(backups\) \- for a low, predictable monthly price\. 6 | 7 | ## Who is Lightsail for? 8 | 9 | Lightsail is for developers\. You can choose an image for your Lightsail instance that jumpstarts your dev project so you don't have to spend as much time installing software or frameworks\. 10 | 11 | If you're an individual developer or hobbyist working on a personal project, Lightsail can help you deploy and manage basic cloud resources\. You might also be interested in learning or experimenting with cloud services, such as virtual machines or networking\. Lightsail provides a quick way to get started\. 12 | 13 | Lightsail has images with base operating systems, development stacks like LAMP, LEMP \(Nginx\), and SQL Server Express, and applications like WordPress, Drupal, and Magento\. For more detailed information about the software installed on each image, see [Choose a Lightsail instance image](compare-options-choose-lightsail-instance-image.md)\. 14 | 15 | As your project grows, you can add block storage disks and attach them to your Lightsail instance\. You can take snapshots of these instances and disks and easily create new instances from those snapshots\. You can also peer your VPC so that your Lightsail instances can use other AWS resources outside of Lightsail\. 16 | 17 | You can also create a Lightsail load balancer and attach target instances to create a highly available application\. You can also configure your load balancer to handle encrypted \(HTTPS\) traffic, session persistence, health checking, and more\. 18 | 19 | ## Operating systems in Lightsail 20 | 21 | **Linux** 22 | + Amazon Linux \(2018\) 23 | + Amazon Linux 2 24 | + CentOS 7 and 8 25 | + Ubuntu 16, 18, and 20 26 | + Free BSD 10 27 | + Debian 8, 9, and 10 28 | + openSUSE Leap 29 | 30 | **Windows** 31 | + Windows Server 2019 32 | + Windows Server 2016 33 | + Windows Server 2012 R2 34 | 35 | ## CMS applications in Lightsail 36 | 37 | **Linux** 38 | + WordPress certified by Bitnami 39 | + WordPress Multisite certified by Bitnami 40 | + cPanel & WHM 41 | + PrestaShop 42 | + Drupal packaged by Bitnami 43 | + Ghost packaged by Bitnami 44 | + Joomla packaged by Bitnami 45 | + Plesk Hosting Stack on Ubuntu 46 | 47 | ## E\-commerce and project management applications in Lightsail 48 | 49 | **Linux** 50 | + Magento packaged by Bitnami \(eCommerce\) 51 | + Redmine packaged by Bitnami \(Project Management\) 52 | 53 | ## Development stacks in Lightsail 54 | 55 | **Linux** 56 | + LAMP stack \(PHP 7\) packaged by Bitnami 57 | + Node\.js packaged by Bitnami 58 | + MEAN Stack packaged by Bitnami \(HVM\) 59 | + Nginx \(LEMP Stack\) packaged by Bitnami 60 | + Django packaged by Bitnami 61 | + GitLab packaged by Bitnami \(HVM\) 62 | 63 | **Windows** 64 | + SQL Server 2016 Express 65 | 66 | ## Get started now 67 | 68 | You can do any of the following to get going: 69 | + [Create your first instance](getting-started-with-amazon-lightsail.md) 70 | + [Connecting to your Linux or Unix instance in Amazon Lightsail](lightsail-how-to-connect-to-your-instance-virtual-private-server.md) 71 | + [Creating a DNS zone to manage your domain’s DNS records in Amazon Lightsail](lightsail-how-to-create-dns-entry.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-deleting-notification-contacts.md: -------------------------------------------------------------------------------- 1 | # Deleting notification contacts in Amazon Lightsail 2 | 3 | *Last updated: February 27, 2020* 4 | 5 | Delete your email and mobile phone number notification contacts from Amazon Lightsail to stop receiving email and SMS text message notifications for your Lightsail resources\. For more information about notifications, see [Notifications in Amazon Lightsail](amazon-lightsail-notifications.md)\. 6 | 7 | You can also disable, or delete an alarm to stop receiving notifications for a specific alarm\. For more information, see [Deleting or disabling metric alarms in Amazon Lightsail](amazon-lightsail-deleting-health-metric-alarms.md)\. 8 | 9 | **Contents** 10 | + [Deleting notification contacts using the Lightsail console](#deleting-notification-contacts-console) 11 | + [Deleting notification contacts using the AWS CLI](#deleting-notification-contacts-cli) 12 | + [Next steps after deleting your notification contacts](#next-steps-deleting-notification-contacts) 13 | 14 | ## Deleting notification contacts using the Lightsail console 15 | 16 | Complete the following steps to delete notification contacts using the Lightsail console\. 17 | 18 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 19 | 20 | 1. On the Lightsail home page, choose **Account** on the top navigation menu\. 21 | 22 | 1. Choose **Account** in the drop\-down menu\. 23 | ![\[Account menu in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-account-drop-down.png) 24 | 25 | 1. Choose the delete icon next to the email address or mobile phone number that you want to delete in the **Notification contacts** section on the **Profile & contacts** tab\. 26 | 27 | 1. Choose **Yes** to confirm that you want to delete the notification contact\. 28 | 29 | ## Deleting notification contacts using the AWS CLI 30 | 31 | Complete the following steps to delete notification contacts for Lightsail using the AWS Command Line Interface \(AWS CLI\)\. 32 | 33 | 1. Open a Terminal or Command Prompt window\. 34 | 35 | If you haven't already, [install the AWS CLI](lightsail-how-to-set-up-and-configure-aws-cli.md) and [configure it to work with Lightsail](lightsail-how-to-set-up-access-keys-to-use-sdk-api-cli.md)\. 36 | 37 | 1. Enter the following command to delete a notification contact: 38 | 39 | ``` 40 | aws lightsail delete-contact-method --region Region --notificationProtocol Protocol 41 | ``` 42 | 43 | In the command, replace: 44 | + *Region* with the AWS Region in which the notification contact should be deleted\. 45 | + *Protocol* with the notification protocol for the contact that you want to delete, such as Email or SMS\. 46 | 47 | Example: 48 | 49 | ``` 50 | aws lightsail delete-contact-method --region us-west-2 --notificationProtocol SMS 51 | ``` 52 | 53 | When you press enter, you'll see an operation response with details about your request\. 54 | 55 | ## Next steps after deleting your notification contacts 56 | 57 | There are a couple of additional tasks that you can perform after deleting your notification contacts: 58 | + Deleting notification contacts stops email and SMS text messaging notifications, but it does not stop notification banners from displaying in the Lightsail console\. To stop notification banners, and to also stop email and SMS text messaging notifications, disable or delete the alarms that are causing them\. For more information, see [Deleting or disabling metric alarms in Amazon Lightsail](amazon-lightsail-deleting-health-metric-alarms.md)\. 59 | + Add your email address and mobile phone number in Lightsail as notification contacts to start receiving email and SMS text messaging notifications again\. For more information, see [Adding notification contacts in Amazon Lightsail](amazon-lightsail-adding-editing-notification-contacts.md)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-databases.md: -------------------------------------------------------------------------------- 1 | # Databases in Amazon Lightsail 2 | 3 | *Last updated: March 15, 2019* 4 | 5 | You can create a MySQL or PostgreSQL managed database in Amazon Lightsail with a few steps\. Lightsail makes database administration more efficient by managing your common maintenance and security tasks\. Using the Lightsail console, you can: 6 | + Back up your database to a snapshot\. 7 | + Create a new larger database from a snapshot\. 8 | + Troubleshoot common issues with browser\-based logs and metrics\. 9 | + Recover data by using point\-in\-time backup and restore operations\. 10 | 11 | The efficient Lightsail experience enables you to build your application on a Lightsail instance and connect it to a Lightsail managed database\. You can also create a standalone database, and connect analytics or querying tools for your company\. Choose from standard or high availability database plans that include your pre\-configured database, SSD\-based storage, and data transfer allocation for a fixed, monthly price\. You can also manage Lightsail databases using the AWS Command Line Interface \(AWS CLI\), API, or SDK\. 12 | 13 | ## More information 14 | 15 | Here's some articles to help you manage your database in Lightsail: 16 | + [High availability databases in Amazon Lightsail](amazon-lightsail-high-availability-databases.md) 17 | + [Choosing an Amazon Lightsail database](amazon-lightsail-choosing-a-database.md) 18 | + [Creating a database in Amazon Lightsail](amazon-lightsail-creating-a-database.md) 19 | + [Configuring the data import mode for your database in Amazon Lightsail](amazon-lightsail-configuring-database-data-import-mode.md) 20 | + [Configuring the public mode for your database in Amazon Lightsail](amazon-lightsail-configuring-database-public-mode.md) 21 | + [Managing your database password in Amazon Lightsail](amazon-lightsail-managing-database-password.md) 22 | + [Connecting to your MySQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-mysql-database.md) 23 | + [Connecting to your PostgreSQL database in Amazon Lightsail](amazon-lightsail-connecting-to-your-postgres-database.md) 24 | + [Downloading an SSL certificate for your managed database in Amazon Lightsail](amazon-lightsail-download-ssl-certificate-for-managed-database.md) 25 | + [Modifying your managed database in Amazon Lightsail to use a specific certificate](amazon-lightsail-modifying-database-to-use-a-specific-certificate.md) 26 | + [Connecting to your MySQL database in Amazon Lightsail using SSL](amazon-lightsail-connecting-to-mysql-database-using-ssl.md) 27 | + [Connecting to your PostgreSQL database in Amazon Lightsail using SSL](amazon-lightsail-connecting-to-postgres-database-using-ssl.md) 28 | + [Importing data into your MySQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-mysql-database.md) 29 | + [Importing data into your PostgreSQL database in Amazon Lightsail](amazon-lightsail-importing-data-into-your-postgres-database.md) 30 | + [Changing the preferred maintenance and backup windows for your database in Amazon Lightsail](amazon-lightsail-changing-preferred-maintenance-and-backup-windows.md) 31 | + [Updating database parameters in Amazon Lightsail](amazon-lightsail-updating-database-parameters.md) 32 | + [Viewing your database health metrics in Amazon Lightsail](amazon-lightsail-viewing-database-health-metrics.md) 33 | + [Viewing your database logs and history in Amazon Lightsail](amazon-lightsail-viewing-database-logs-and-history.md) 34 | + [Enabling the MySQL database general and slow query logs in Amazon Lightsail](amazon-lightsail-enabling-mysql-general-and-slow-query-logs.md) 35 | + [Creating a snapshot of your database in Amazon Lightsail](amazon-lightsail-creating-a-database-snapshot.md) 36 | + [Creating a database from a snapshot in Amazon Lightsail](amazon-lightsail-creating-a-database-from-snapshot.md) 37 | + [Creating a database from a point\-in\-time backup in Amazon Lightsail](amazon-lightsail-creating-a-database-from-point-in-time-backup.md) 38 | + [Deleting your database in Amazon Lightsail](amazon-lightsail-deleting-your-database.md) -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-define-the-primary-domain-for-your-wordpress-multisite.md: -------------------------------------------------------------------------------- 1 | # Define the primary domain for your WordPress Multisite instance in Amazon Lightsail 2 | 3 | *Last updated: June 18, 2021* 4 | 5 | A WordPress Multisite instance in Amazon Lightsail is designed to use multiple domains, or subdomains, for each blog site that you create within that instance\. Because of this, you must define the primary domain to use for the main blog of your WordPress Multisite instance\. 6 | 7 | ## Prerequisites 8 | 9 | Complete the following prerequisites in the order shown: 10 | 11 | 1. Create a WordPress Multisite instance in Lightsail\. For more information, see [Create an Amazon Lightsail instance](how-to-create-amazon-lightsail-instance-virtual-private-server-vps.md)\. 12 | 13 | 1. Create a static IP and attach it to your WordPress Multisite instance in Lightsail\. For more information, see [Create a static IP and attach it to an instance in Amazon Lightsail](lightsail-create-static-ip.md)\. 14 | **Important** 15 | You must reboot your WordPress Multisite instance after you attach a static IP to it\. This will allow the instance to recognize the new static IP associated to it\. 16 | 17 | 1. Add your domain to Lightsail by creating a DNS zone, then point it to the static IP that you attached to your WordPress Multisite instance\. For more information, see [Creating a DNS zone to manage your domain’s DNS records in Amazon Lightsail](lightsail-how-to-create-dns-entry.md)\. 18 | 19 | 1. Allow time for the DNS changes to propagate through the internet's DNS\. Then, you can continue to the [Define the primary domain for your WordPress Multisite instance>](#define-the-primary-domain-for-your-wordpress-multisite) section of this guide\. 20 | 21 | ## Define the primary domain for your WordPress Multisite instance 22 | 23 | Complete these steps to ensure that your domain, such as `example.com`, redirects to the main blog of your WordPress Multisite instance\. 24 | 25 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 26 | 27 | 1. On the Lightsail home page, choose the SSH quick connect icon for your WordPress Multisite instance\. 28 | ![\[SSH quick connect on the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/wp-multisite-ssh-quick-connect.png) 29 | 30 | 1. Enter the following command to define the primary domain name for your WordPress Multisite instance\. Be sure to replace `` with the correct domain name for your WordPress Multisite\. 31 | 32 | ``` 33 | sudo /opt/bitnami/configure_app_domain --domain 34 | ``` 35 | 36 | Example: 37 | 38 | ``` 39 | sudo /opt/bitnami/configure_app_domain --domain example.com 40 | ``` 41 | **Note** 42 | If this command fails, you might be using an older version of the WordPress Multisite instance\. Try running the following commands instead, and be sure to replace `` with the correct domain name for your WordPress Multisite\. 43 | 44 | ``` 45 | cd /opt/bitnami/apps/wordpress 46 | sudo ./bnconfig --machine_hostname 47 | ``` 48 | After running that command, enter the following command to keep the bnconfig tool from automatically running every time the server restarts\. 49 | 50 | ``` 51 | sudo mv bnconfig bnconfig.disabled 52 | ``` 53 | 54 | At this point, browsing to the domain that you defined should redirect you to the main blog of your WordPress Multisite instance\. 55 | 56 | ## Next steps 57 | 58 | Complete the next steps after you have defined the primary domain for your WordPress Multisite instance: 59 | + [Add blogs as subdomains to your WordPress Multisite instance in Amazon Lightsail](amazon-lightsail-add-blogs-as-subdomains-to-your-wordpress-multisite.md) 60 | + [Add blogs as domains to your WordPress Multisite instance in Amazon Lightsail](amazon-lightsail-add-blogs-as-domains-to-your-wordpress-multisite.md) -------------------------------------------------------------------------------- /doc_source/lightsail-how-to-create-instance-from-snapshot.md: -------------------------------------------------------------------------------- 1 | # Creating an instance from a manual snapshot in Amazon Lightsail 2 | 3 | *Last updated: November 14, 2017* 4 | 5 | After you create a snapshot in Lightsail, you can create a new instance from that snapshot\. The new instance will include the system disk and any attached block storage disks you added\. 6 | 7 | You must have a snapshot of an instance before you can create another instance from a snapshot\. For more information, see [Creating a snapshot of your Linux or Unix instance in Amazon Lightsail](lightsail-how-to-create-a-snapshot-of-your-instance.md) or [Creating a snapshot of your Windows Server instance in Amazon Lightsail](prepare-windows-based-instance-and-create-snapshot.md)\. 8 | 9 | 1. On the Lightsail home page, choose the name of your instance for which you want to create a new instance from a snapshot\. 10 | 11 | 1. Choose the **Snapshots** tab\. 12 | 13 | 1. Under the **Manual snapshots** section of the page, choose the actions menu icon \(⋮\) next to the snapshot from which you want to create a new instance, and choose **Create new instance**\. 14 | ![\[Manage snapshot menu\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-create-new-linux-unix-based-lightsail-instance-from-snapshot.png) 15 | 16 | 1. On the **Create an instance from a snapshot** page, you have a few optional settings to decide on at the top\. For example, you can change the Availability Zone, [add a launch script](lightsail-how-to-configure-server-additional-data-shell-script.md), or [change the way you connect to your instance](understanding-ssh-in-amazon-lightsail.md)\. 17 | 18 | You can accept all the defaults and move on to the next step\. 19 | 20 | 1. Choose the plan \(or *bundle*\) for your new instance\. At this point, you can choose to create an instance that uses a larger bundle size than the original instance\. 21 | **Note** 22 | You cannot create a an instance that uses a smaller bundle size than the original instance\. Smaller bundle size options will be unavailable for selection\. 23 | 24 | 1. Enter a name for your instance\. 25 | 26 | Resource names: 27 | + Must be unique within each AWS Region in your Lightsail account\. 28 | + Must contain 2 to 255 characters\. 29 | + Must start and end with an alphanumeric character or number\. 30 | + Can include alphanumeric characters, numbers, periods, dashes, and underscores\. 31 | 32 | 1. Choose one of the following options to add tags to your instance: 33 | + **Add key\-only tags** or **Edit key\-only tags** \(if tags have already been added\)\. Enter your new tag into the tag key text box, and press **Enter**\. Choose **Save** when you’re done entering your tags to add them, or choose **Cancel** to not add them\. 34 | ![\[Key-only tags in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-key-only-tags.png) 35 | + **Create a key\-value tag**, then enter a key into the **Key** text box, and a value into the **Value** text box\. Choose **Save** when you’re done entering your tags, or choose **Cancel** to not add them\. 36 | 37 | Key\-value tags can only be added one at a time before saving\. To add more than one key\-value tag, repeat the previous steps\. 38 | ![\[Key-value tags in the Lightsail console.\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-key-value-tag.png) 39 | **Note** 40 | For more information about key\-only and key\-value tags, see [Tags in Amazon Lightsail](amazon-lightsail-tags.md)\. 41 | 42 | 1. Choose **Create instance**\. 43 | 44 | Lightsail takes you to the management page for your new instance, and you can start managing your new instance\. 45 | **Important** 46 | Custom firewall rules that were created on the original instance are not re\-created on your new instance created from a snapshot\. Only the default rules are created\. For more information, see [Default instance firewall rules](https://lightsail.aws.amazon.com/ls/docs/en_us/articles/understanding-firewall-and-port-mappings-in-amazon-lightsail#default-lightsail-firewall-rules)\. -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-resetting-distribution-cache.md: -------------------------------------------------------------------------------- 1 | # Resetting the cache of your Amazon Lightsail distribution 2 | 3 | *Last updated: July 23, 2020* 4 | 5 | The cache lifespan \(time to live\) setting controls the amount of time your content stays in your Amazon Lightsail distribution's cache\. You can also manually reset the cache on your distribution if you need to clear it before the cache lifespan interval\. After you clear the cache, the next time a user requests content, your distribution pulls the latest version of your content from your origin and caches it\. In this guide, we show you how to manually reset the cache on your distribution\. For more information about distributions, see [Content delivery network distributions in Amazon Lightsail](amazon-lightsail-content-delivery-network-distributions.md)\. 6 | 7 | ## Reset the cache of your distribution 8 | 9 | Complete the following procedure to reset the cache of your distribution\. 10 | 11 | 1. Sign in to the [Lightsail console](https://lightsail.aws.amazon.com/)\. 12 | 13 | 1. On the Lightsail home page, choose the **Networking** tab\. 14 | 15 | 1. Choose the name of the distribution for which you want to reset the cache\. 16 | 17 | 1. Choose the **Cache** tab on your distribution's management page\. 18 | 19 | 1. Scroll to the **Reset cache** section of the page, and choose **Reset cache**\. 20 | 21 | 1. At the confirmation prompt, choose **Yes, reset** to confirm that you want to reset your distribution's cache\. Or choose **No, cancel** to not reset your distribution's cache\. 22 | 23 | ## Additional information 24 | 25 | Here are some articles to help you manage distributions in Lightsail: 26 | + [Content delivery network distributions in Amazon Lightsail](amazon-lightsail-content-delivery-network-distributions.md) 27 | + [Creating Amazon Lightsail distributions](amazon-lightsail-creating-content-delivery-network-distribution.md) 28 | + [Understanding request and response behaviors of an Amazon Lightsail distribution](amazon-lightsail-distribution-request-and-response.md) 29 | + [Configuring your WordPress instance to work with your Amazon Lightsail distribution](amazon-lightsail-editing-wp-config-for-distribution.md) 30 | + [Testing your Amazon Lightsail distribution](amazon-lightsail-testing-distribution.md) 31 | + [Changing the origin of your Amazon Lightsail distribution](amazon-lightsail-changing-distribution-origin.md) 32 | + [Changing the caching behavior of your Amazon Lightsail distribution](amazon-lightsail-changing-default-cache-behavior.md) 33 | + [Resetting the cache of your Amazon Lightsail distribution](#amazon-lightsail-resetting-distribution-cache) 34 | + [Changing the plan of your Amazon Lightsail distribution](amazon-lighstail-changing-distribution-plan.md) 35 | + [Enabling custom domains for your Amazon Lightsail distributions](amazon-lightsail-enabling-distribution-custom-domains.md) 36 | + [Pointing your domains to your Amazon Lightsail distributions](amazon-lightsail-point-domain-to-distribution.md) 37 | + [Changing custom domains for your Amazon Lightsail distribution](amazon-lightsail-changing-distribution-custom-domains.md) 38 | + [Disabling custom domains for your Amazon Lightsail distributions](amazon-lightsail-disabling-distribution-custom-domains.md) 39 | + [Viewing distribution metrics in Amazon Lightsail](amazon-lightsail-viewing-distribution-health-metrics.md) 40 | + [Deleting your Amazon Lightsail distribution](amazon-lightsail-deleting-distribution.md) 41 | + [SSL/TLS certificates in Amazon Lightsail](understanding-tls-ssl-certificates-in-lightsail-https.md) 42 | + [Creating SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-create-a-distribution-certificate.md) 43 | + [Validating SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-validating-a-distribution-certificate.md) 44 | + [Viewing SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-viewing-distribution-certificates.md) 45 | + [Deleting SSL/TLS certificates for your Amazon Lightsail distribution](amazon-lightsail-deleting-distribution-certificates.md) -------------------------------------------------------------------------------- /doc_source/security-iam-awsmanpol.md: -------------------------------------------------------------------------------- 1 | # AWS managed policies for Amazon Lightsail 2 | 3 | *Last updated: January 14, 2022* 4 | 5 | To add permissions to users, groups, and roles, it is easier to use AWS managed policies than to write policies yourself\. It takes time and expertise to [create IAM customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) that provide your team with only the permissions they need\. To get started quickly, you can use our AWS managed policies\. These policies cover common use cases and are available in your AWS account\. For more information about AWS managed policies, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*\. 6 | 7 | AWS services maintain and update AWS managed policies\. You can't change the permissions in AWS managed policies\. Services occasionally add additional permissions to an AWS managed policy to support new features\. This type of update affects all identities \(users, groups, and roles\) where the policy is attached\. Services are most likely to update an AWS managed policy when a new feature is launched or when new operations become available\. Services do not remove permissions from an AWS managed policy, so policy updates won't break your existing permissions\. 8 | 9 | Additionally, AWS supports managed policies for job functions that span multiple services\. For example, the **ReadOnlyAccess** AWS managed policy provides read\-only access to all AWS services and resources\. When a service launches a new feature, AWS adds read\-only permissions for new operations and resources\. For a list and descriptions of job function policies, see [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*\. 10 | 11 | ## AWS managed policy: LightsailExportAccess 12 | 13 | You can't attach LightsailExportAccess to your IAM entities\. This policy is attached to a service\-linked role that allows Lightsail to perform actions on your behalf\. For more information, see [Using Service\-Linked Roles for Amazon Lightsail](amazon-lightsail-using-service-linked-roles.md)\. 14 | 15 | This policy grants permissions that allow Lightsail to export your instance and disk snapshots to Amazon Elastic Compute Cloud, and get the current account\-level Block Public Access configuration from Amazon Simple Storage Service \(Amazon S3\)\. 16 | 17 | **Permissions details** 18 | 19 | This policy includes the following permissions\. 20 | + `ec2` – Allows access to list and copy instance images and disk snapshots\. 21 | + `iam` – Allows access to delete service\-linked roles and retrieve the status of your service\-linked role deletion\. 22 | + `s3` – Allows access to retrieve the `PublicAccessBlock` configuration for an AWS account\. 23 | 24 | ``` 25 | { 26 | "Version": "2012-10-17", 27 | "Statement": [ 28 | { 29 | "Effect": "Allow", 30 | "Action": [ 31 | "iam:DeleteServiceLinkedRole", 32 | "iam:GetServiceLinkedRoleDeletionStatus" 33 | ], 34 | "Resource": "arn:aws:iam::*:role/aws-service-role/lightsail.amazonaws.com/AWSServiceRoleForLightsail*" 35 | }, 36 | { 37 | "Effect": "Allow", 38 | "Action": [ 39 | "ec2:CopySnapshot", 40 | "ec2:DescribeSnapshots", 41 | "ec2:CopyImage", 42 | "ec2:DescribeImages" 43 | ], 44 | "Resource": "*" 45 | }, 46 | { 47 | "Effect": "Allow", 48 | "Action": [ 49 | "s3:GetAccountPublicAccessBlock" 50 | ], 51 | "Resource": "*" 52 | } 53 | ] 54 | } 55 | ``` 56 | 57 | ## Lightsail updates to AWS managed policies 58 | + Edit to the `LightsailExportAccess` managed policy 59 | 60 | Added the `s3:GetAccountPublicAccessBlock` action to the `LightsailExportAccess` managed policy\. It allows Lightsail to get the current account\-level Block Public Access configuration from Amazon S3\. 61 | 62 | January 14, 2022 63 | + Lightsail started tracking changes 64 | 65 | Lightsail started tracking changes for its AWS managed policies\. 66 | 67 | January 14, 2022 -------------------------------------------------------------------------------- /doc_source/amazon-lightsail-instance-metadata.md: -------------------------------------------------------------------------------- 1 | # Instance metadata and user data in Amazon Lightsail 2 | 3 | *Last updated: September 23, 2022* 4 | 5 | *Instance metadata* is data about your instance that you can use to configure or manage the running instance\. Instance metadata is divided into categories, for example, hostname, events, and security groups\. You can also use instance metadata to access user data that you specified when launching your instance\. For example, you can specify parameters for configuring your instance, or include a simple script\. Instances can also include dynamic data, such as an instance identity document that is generated when the instance is launched\. 6 | 7 | **Important** 8 | Although you can only access instance metadata and user data from within the instance itself, the data is not protected by authentication or cryptographic methods\. Anyone who has direct access to the instance, and potentially any software running on the instance, can view its metadata\. Therefore, you should not store sensitive data, such as passwords or long\-lived encryption keys, as user data\. 9 | 10 | ## Use the Instance Metadata Service 11 | 12 | You can access instance metadata from a running instance in Lightsail by using one of the following methods: 13 | + Instance Metadata Service Version 1 \(IMDSv1\) – a request/response method 14 | + Instance Metadata Service Version 2 \(IMDSv2\) – a session\-oriented method 15 | **Important** 16 | Not all instance blueprints in Lightsail support IMDSv2\. Use the `MetadataNoToken` instance metric to track the number of calls to the instance metadata service that are using IMDSv1\. For more information, see [Viewing instance metrics in Amazon Lightsail](amazon-lightsail-viewing-instance-health-metrics.md)\. 17 | 18 | For more information about using IMDS, see [Use the Instance Metadata Service with an Amazon Lightsail instance](amazon-lightsail-configuring-instance-metadata-service.md)\. 19 | 20 | ## Additional IMDS documentation 21 | 22 | The following IMDS documentation is available in the *Amazon Elastic Compute Cloud User Guide for Linux Instances* and the *Amazon Elastic Compute Cloud User Guide for Windows Instances*: 23 | 24 | **Note** 25 | In Amazon EC2, instance blueprints are referred to as Amazon Machine Images \(AMIs\)\. 26 | + For Linux instances: 27 | + [Configure the instance metadata options](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-options.html) 28 | + [Retrieve instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html) 29 | + [Work with instance user data](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-add-user-data.html) 30 | + [Retrieve dynamic data](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-dynamic-data-retrieval.html) 31 | + [Instance metadata categories](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html) 32 | + [Example: AMI launch index value](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMI-launch-index-examples.html) 33 | + [Instance identity documents](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html) 34 | + For Windows instances: 35 | + [Configure the instance metadata options](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/configuring-instance-metadata-options.html) 36 | + [Retrieve instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/instancedata-data-retrieval.html) 37 | + [Work with instance user data](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/instancedata-add-user-data.html) 38 | + [Retrieve dynamic data](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/instancedata-dynamic-data-retrieval.html) 39 | + [Instance metadata categories](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/instancedata-data-categories.html) 40 | + [Example: AMI launch index value](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/AMI-launch-index-examples.html) 41 | + [Instance identity documents](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/instance-identity-documents.html) -------------------------------------------------------------------------------- /doc_source/getting-started-with-wordpress-and-lightsail.md: -------------------------------------------------------------------------------- 1 | # Getting started using WordPress from your Amazon Lightsail instance 2 | 3 | *Last updated: May 17, 2017* 4 | 5 | If you're reading this, it means you successfully created a Lightsail instance that's running WordPress\. Congrats\! If you still need to [create a WordPress instance](getting-started-with-amazon-lightsail.md), go ahead and do that now\. We'll wait for you\.\.\. 6 | 7 | Now you're ready to get started with some basic administrative tasks\. First, let's log in to your WordPress Dashboard\. 8 | 9 | ## Step 1: Go to your WordPress blog and log in 10 | 11 | Here's how to log in to your WordPress blog\. 12 | 13 | 1. Go to the Lightsail home page and find your WordPress blog\. 14 | 15 | 1. Copy the **Public IP** address to the clipboard\. You can find this address on the Lightsail home page or on the instance details page\. 16 | 17 | 18 | 19 | 1. Paste the IP address into your browser\. 20 | 21 | You should see something like this: 22 | ![\[WordPress blog made using Lightsail\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/wordpress-blog-lightsail-bitnami-new.png) 23 | 24 | 1. Choose **Manage** in the lower right corner\. 25 | 26 | If the **Manage** banner is not shown, you can reach the sign in page by browsing to `http:///wp-login.php`\. Replace `` with the public IP address of your instance\. 27 | 28 | 1. Choose **Login** to log in to the admin console\. 29 | 30 | 1. Use the default user name \(**user**\)\. 31 | 32 | 1. To get the password, you need to connect to your instance\. 33 | 34 | Go back to Lightsail and choose **Connect using SSH** to connect to your WordPress instance\. 35 | 36 | 1. Type the following: 37 | 38 | ``` 39 | cat bitnami_application_password 40 | ``` 41 | **Note** 42 | If you're in a directory other than the user home directory, then type `cat $HOME/bitnami_application_password`\. 43 | 44 | You should see something like this: 45 | ![\[Getting the WordPress password from the browser-based SSH terminal\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-bitnami-wordpress-password.png) 46 | 47 | 1. Highlight your password in the terminal screen, then choose the clipboard icon\. 48 | 49 | 1. Highlight the text you want to copy in the clipboard text box, then press Ctrl\+C or Cmd\+C to copy the text to your local clipboard\. 50 | ![\[Copying text using the browser-based clipboard\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/lightsail-terminal-ssh-rdp-clipboard.png) 51 | **Important** 52 | You should save your password somewhere at this time\. You can always change it later\. 53 | 54 | 1. Paste your password into the WordPress login page, and then choose **Log In**\. 55 | 56 | If you succeed, you'll see the WordPress Dashboard\. 57 | ![\[Successful login to the WordPress Dashboard\]](https://d9yljz1nd5001.cloudfront.net/en_us/f1c62fa5316bf1df017e7afb5a0e0a21/images/amazon-lightsail-wordpress-dashboard.png) 58 | 59 | ## Step 2: Update your profile or password in the WordPress Dashboard 60 | 61 | Now that you have access to your WordPress Dashboard, you can create another user or change your password\. 62 | 63 | 1. Choose **Users**\. 64 | 65 | 1. Choose **user**, and then choose **Edit**\. 66 | 67 | 1. Update your **Personal Options** on the **Profile** page, and when you're done choose **Update Profile**\. 68 | 69 | ## Next steps 70 | 71 | Visit [Bitnami WordPress for Amazon Web Services](https://docs.bitnami.com/aws/apps/wordpress/) for more tutorials\. Here are some cool things you can do with your new WordPress blog in Lightsail\. 72 | + [Install plugins](https://docs.bitnami.com/aws/apps/wordpress/#how-to-install-a-plugin-on-wordpress) 73 | + [Create a full backup](https://docs.bitnami.com/aws/apps/wordpress/#how-to-create-a-full-backup-of-wordpress) 74 | + [Enable HTTPS support with SSL certificates](https://docs.bitnami.com/aws/apps/wordpress/#how-to-enable-https-support-with-ssl-certificates) --------------------------------------------------------------------------------