A stable server address is useful when customers point DNS records or external services at a Lightsail instance. PD AWS Lightsail can allocate and attach a static public IPv4 address when a new service is created.

Choose an appropriate offering

This guide is for the hosting operator preparing new services. Use an IPv4-capable plan. A Lightsail static IP is an IPv4 address and cannot be attached to an IPv6-only instance. AWS explains the address behaviour in its Lightsail networking guide.

A static address is not a DNS record and does not configure a web server. Customers still need to point their domains at the assigned address and configure the applications they intend to run.

Configure allocation on create

1. Open System Settings → Products/Services → your product → Module Settings for the PD AWS Lightsail product.
2. Check Platform, Region and Instance plan (bundle) for the intended offering.
3. Confirm IPv6-only networking is off when the offering needs a static IPv4 address.
4. Enable Allocate static IP and save.
5. If you expose a Static IP configurable option, check the selected customer choice as well. A checkout choice can override the saved default.
6. Review the order form and offering description so that they accurately state when a stable IPv4 address is included.

Verify a newly provisioned service

When intentionally creating your next test or customer service, wait for provisioning and the address attachment to finish. Open its Overview and confirm that a static IP is shown. Use Connection details to check the address the customer should connect to.

Do not stop a customer’s production server simply to test address persistence. AWS documents that an attached static IPv4 address stays the same across stop/start, while an ordinary public IPv4 can change.

If no static IP appears

Check that the service was created with allocation enabled and was not ordered with a contrary configurable option. Review its Activity and the module’s operational result for an allocation or attachment failure. Provider permissions, capacity limits or a still-pending create operation can require attention.

Changing a product default does not apply a static IP to an existing server. For the affected service, compare the selected options and the allocation/attachment result with the networking state you can see in your own AWS account. Keep a working address in place while investigating; creating a second server does not explain the first service’s address state. Underlying AWS networking resources can incur provider charges.

See the PD AWS Lightsail WHMCS guide for related tasks, or explore the module.