![]() ![]() This image is a pre-configured, ready-to-run image for running WordPress on Amazon Lightsail supplied by Bitnami.Īmazon Lightsail console: instance blueprints Then we select WordPress as the type of Operating System + Application. You get to pick the region to which you want to deploy your instance. Choose a region that is the closest to your audience/readers. ![]() In the next step, we want to choose our instance type (basically the horsepower of the machine). ![]() When you create the instance, it starts to boot up with the WordPress image. You will see that it has an external IP address. But it’s only a dynamic address which means you will lose it once you stop/start the machine. This can become a problem if you point your DNS’s A record to the IP address and you decide to stop/start the server. The A record will still point to the old dynamic IP address. To fix this, you should assign a static IP address in the networking tab. Amazon Lightsail console: create static IPĬreating a static IP is free of charge when it’s attached to the instance. When you don’t attach it, AWS starts charging you for reserving the IP address.īefore we’re going to optimize the WordPress configuration on the server, we’re going to update the Lightsail instance’s firewall to protect it from outsiders. By default Port 22/80/443 is allowed for everyone, which is something that’s not considered best practice for security measures! #Bitnami wordpress stack stop auto starting update You should restrict access to port 22 (SSH) for your IP address. #Bitnami wordpress stack stop auto starting update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |