# How to Whitelist IP? **The Whitelist IP** feature enhances your container's security by restricting access to only authorized sources. * **Default State**: All IP addresses are allowed to access the Container. * **After Configuration**: Access is strictly limited to the IP addresses defined in your whitelist. {% hint style="success" %} **Prerequisite**: This feature is only available after a Container has been successfully created and is in "Running" status. {% endhint %} #### Access the Feature 1. You need to [Create a container](https://ai-docs.fptcloud.com/~/revisions/MN07vkRkyAKKaDfqwwSf/fpt-gpu-cloud/gpu-container/tutorials/how-to-create-a-container) before using this feature.

2. Navigate to the **Container View** screen and select the specific Container you wish to secure.

3. Click on the **Whitelist IP tab** from the navigation menu. #### Add a New Whitelist IP Rule

1. Click the **\[+ Add Rule]** button. A new entry row will appear in the list. 2. Configure the Rule Details:


Field	Description	Format / Requirement
Type	Choose the protocol for the rule.	TCP or HTTP
Port	Ports are automatically populated based on your Container's access settings.	You can manually remove specific ports to limit the rule's scope.
Source	Define the specific IP addresses or ranges allowed to access.	• Single IPv4: `192.168.1.1` • CIDR Range: `192.168.1.0/24` • Bulk: Use commas for multiple IPs.
Description (Optional)	Add a short note to identify the purpose of this rule .	Alphanumeric, max 100 characters.

3. Click **Save** to deploy the configuration. #### View Whitelist IP


Field	Description	Examples
Protocol	Shows the assigned communication protocol for the rule.	TCP, HTTP
Port	Displays the specific service ports protected by the rule.	22, 80, 443, 8080
Source (Inbound only)	Lists the authorized IP addresses or network ranges allowed to access the container.	Single IP (1.2.3.4) or CIDR (1.2.3.0/24)
Description (Optional)	Displays custom labels used to quickly identify the purpose of the rule.	"Dev Team", "Office VPN", "Customer A"

**Filter**: The top navigation bar provides dynamic filters to help you locate specific rules quickly, especially when managing large environments. * **By Protocol**: Click the Protocol dropdown to isolate rules by their communication type. * **By Port**: Use the Port filter to find all rules associated with a specific service port. * **By Source**: Use the Source search box to filter the list by a specific IP address or network range. #### Edit Whitelist IP You can update any field of an existing rule without having to delete and recreate it. 1. Click **Edit** button 2. Edit Rules 3. Click the **Save** button (usually located at the bottom of the table) to push your updates live. #### Delete Whitelist IP If a rule is no longer needed (e.g., a project has ended or a consultant no longer needs access), you can remove it permanently. {% hint style="danger" %} *Once a rule is deleted, the blocked IP addresses will immediately lose access to the specified ports.* {% endhint %} 1. Click **Edit** button 2. Locate the rule you wish to remove in the Whitelist table. 3. Navigate to the Action column on the far right and click the **Trash Can icon** (Red) associated with that specific row. 4. Click the **Save** button (usually located at the bottom of the table) to push your updates live. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-container/tutorials/how-to-whitelist-ip.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.