A customer with an existing Lightsail server may want a fixed public IPv4 address before pointing a domain at it. PD AWS Lightsail provides this through the service's Overview page when you enable the customer control. This guide covers an existing server; allocation during initial provisioning is a separate setting.

Enable the customer control

Open Packages → your package → Module Options. Enable Client: Static IP and save. This control permits both allocation and release, so enable it when customers should manage the address themselves. If your team manages networking for the customer, keep that responsibility reflected in the controls you offer.

The server must use an IPv4-capable plan. Static IPv4 allocation is not available for an IPv6-only instance, and the server must be running before an address can be attached. The module also needs a working AWS connection.

Allocate an address from the service page

1. In the customer area, open the Lightsail service's Overview.
2. Find Server details and its Static IP row.
3. If an address is already shown as Enabled, use that address; the service already has a static IP.
4. Otherwise, on a running eligible server, choose Allocate static IP and confirm.
5. Check the completion message and refresh the service page. The Static IP row should show Enabled and the attached address.

Allocation attaches a new fixed address. Review DNS records and any external allow-lists that still refer to the server's previous address before relying on the new one. Allocating a static IP does not create a DNS record or configure the website on the server.

Example: point a domain at an existing server

Suppose a customer has finished preparing a website and now wants to connect their domain. After allocating the static IP, they use the displayed address in the relevant DNS A record. They then check that the domain reaches the intended website and that its web-server configuration is ready. The attached static address stays the same across server stop/start; there is no need to interrupt the server simply to test that behaviour.

Understand the release control

The same row offers Release static IP when an address is attached and customer management is enabled. Releasing returns the address to AWS; do not treat it as a temporary disconnect or a way to refresh the address. DNS records and allow-lists using it will need to change, and the old address cannot be relied on for reuse.

For an intentional release, first plan the replacement addressing and affected DNS changes. Select Release static IP, read the confirmation and type the current address exactly when prompted. After completion, refresh the service page and check its current connection address before updating dependent services. An ordinary public IPv4 address can change after stop/start.

If Allocate static IP is unavailable

Check the saved Client: Static IP setting and any override for this service. Confirm that the server is running, the plan supports public IPv4 and the module can reach the configured AWS account. If a static IP is already listed, allocation is unnecessary. These checks address the conditions the module uses to offer the control.

For new orders, see assign a static IP when a Lightsail service is created.