# Enable connection_throttling on Azure PostgreSQL Servers to Prevent Connection Overload and DoS Attacks

- Source: https://support.icompaas.com/support/solutions/articles/62000234796-enable-connection-throttling-on-azure-postgresql-servers-to-prevent-connection-overload-and-dos-attac
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Azure Database Services Benchmark v1.0.0](https://support.icompaas.com/support/solutions/62000112693) › [Azure Database Services Benchmark](https://support.icompaas.com/support/solutions/folders/62000169261)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability:**

-   **Level 1**  
    

**Description:** The connection\_throttling parameter in PostgreSQL controls the throttling of incoming connections when the server is under heavy load. Enabling this setting helps prevent Denial of Service (DoS) attacks and ensures that the database can handle a high number of legitimate users without degrading the server's performance.

**Rationale:** By enabling connection\_throttling, PostgreSQL can protect itself from being overwhelmed by too many concurrent connections. This ensures that the system continues to perform optimally even under heavy load, preventing service degradation and potential outages.

**Impact:**

-   Pros:  
    
    -   Prevents overloading of database resources by limiting the number of concurrent connections.  
        
    -   Helps in mitigating DoS attacks that target connection resources.  
        
    -   Improves the overall stability and performance of the server.  
        
-   Cons:  
      
    
    -   If set too low, legitimate users may experience delays or be unable to connect during peak usage.  
        
    -   Requires careful tuning to balance performance and protection.  
        

**Default Value:**

By default, connection\_throttling is set to OFF.

**Pre-requisites:** Ensure that the PostgreSQL server is under sufficient resource capacity to handle the number of connections required, even with throttling enabled.

**Remediation**

**Test Plan:**

**Using Azure Portal:**

1.  Log in to the Azure Portal: [https://portal.azure.com](https://portal.azure.com/).  
    
2.  Navigate to Azure Database for PostgreSQL Servers.  
    
3.  Select the desired PostgreSQL server.  
    
4.  Under Settings, click on Server parameters.  
    
5.  Search for the connection\_throttling parameter and verify that it is set to ON.
    

**Using Azure CLI:**1\.  Run the following command to check the connection\_throttling setting:

az postgres server show --resource-group <resource-group-name> --name <server-name> --query "properties.parameters.connection\_throttling"

  

-   The output should show ON.  
    

**Implementation Plan:**

**Using Azure Portal:**

1.  Go to Azure Database for PostgreSQL Servers.  
    
2.  Select the PostgreSQL server and click on Server parameters.  
    
3.  Set the connection\_throttling parameter to ON and save the changes.
    

**Using Azure CLI:** 1. To enable connection\_throttling, run the following command:

az postgres server configuration set --resource-group <resource-group-name> --server-name <server-name> --name connection\_throttling --value ON

  

**Backout Plan:**

**Using Azure Portal:**

1.  Go to Azure Database for PostgreSQL Servers.  
    
2.  Under Settings, click on Server parameters.  
    
3.  Set the connection\_throttling parameter back to OFF if necessary.
    

**Using Azure CLI:**1.  To disable connection\_throttling, run:

az postgres server configuration set --resource-group <resource-group-name> --server-name <server-name> --name connection\_throttling --value OFF

  

**References:**

-   [Azure PostgreSQL Server - Configure Connection Throttling  
      
    ](https://docs.microsoft.com/en-us/azure/postgresql/single-server/configure-connection-throttling)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
