Skip to content

[4.6.0] Add AWS Lambda connection pooling related configurations #10989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thivindu merged 4 commits into from
Mar 30, 2026
Merged

[4.6.0] Add AWS Lambda connection pooling related configurations #10989

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
debb1d4
Document AWS Lambda HTTP client connection pooling related configs
thivindu Mar 26, 2026
7466a79
Add newline to EOF
thivindu Mar 26, 2026
0c32e70
Update config catalog
thivindu Mar 30, 2026
65cb389
Remove note from doc
thivindu Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
117 changes: 117 additions & 0 deletions en/docs/reference/config-catalog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17108,3 +17108,120 @@ same_site_cookies = "lax"
</section>
</div>



## API-M AWS Lambda Configurations


<div class="mb-config-catalog">
<section>
<div class="mb-config-options">
<div class="superfences-tabs">

<input name="116" type="checkbox" id="_tab_116">
<label class="tab-selector" for="_tab_116"><i class="icon fa fa-code"></i></label>
<div class="superfences-content">
<div class="mb-config-example">
<pre><code class="toml">[apim.aws_lambda.http_client]
max_connections = 50
connection_timeout = 10
socket_timeout = 30
connection_acquisition_timeout = 60
</code></pre>
</div>
</div>
<div class="doc-wrapper">
<div class="mb-config">
<div class="config-wrap">
<code>[apim.aws_lambda.http_client]</code>

<p>
Configurations to tune the underlying HTTP connection pool settings used by each AWS Lambda client instance, to improve performance under high load.
</p>
</div>
<div class="params-wrap">
<div class="param">
<div class="param-name">
<span class="param-name-wrap"> <code>max_connections</code> </span>
</div>
<div class="param-info">
<div>
<p>
<span class="param-type string"> integer </span>

</p>
<div class="param-default">
<span class="param-default-value">Default: <code>100</code></span>
</div>

</div>
<div class="param-description">
<p>The maximum number of concurrent HTTP connections allowed per AWS Lambda client instance. Increase this value if you expect high concurrent throughput to Lambda functions.</p>
</div>
</div>
</div><div class="param">
<div class="param-name">
<span class="param-name-wrap"> <code>connection_timeout</code> </span>
</div>
<div class="param-info">
<div>
<p>
<span class="param-type string"> integer </span>

</p>
<div class="param-default">
<span class="param-default-value">Default: <code>2</code></span>
</div>

</div>
<div class="param-description">
<p>The maximum time (in seconds) to wait when establishing a new TCP connection to AWS.</p>
</div>
</div>
</div><div class="param">
<div class="param-name">
<span class="param-name-wrap"> <code>socket_timeout</code> </span>
</div>
<div class="param-info">
<div>
<p>
<span class="param-type string"> integer </span>

</p>
<div class="param-default">
<span class="param-default-value">Default: <code>30</code></span>
</div>

</div>
<div class="param-description">
<p>The maximum time (in seconds) to wait for data to be transferred after a connection is established.</p>
</div>
</div>
</div><div class="param">
<div class="param-name">
<span class="param-name-wrap"> <code>connection_acquisition_timeout</code> </span>
</div>
<div class="param-info">
<div>
<p>
<span class="param-type string"> integer </span>

</p>
<div class="param-default">
<span class="param-default-value">Default: <code>30</code></span>
</div>

</div>
<div class="param-description">
<p>The maximum time (in seconds) to wait for a connection to become available from the pool if max_connections has been reached.</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
</div>

73 changes: 73 additions & 0 deletions en/docs/tutorials/create-and-publish-awslambda-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,3 +146,76 @@ When using AWS Lambda, you can execute your code without having to manage or pro
2. Go to **Lifecycle** page and click on **PUBLISH** to publish the API to Developer Portal.

You have successfully published the AWS Lambda API. Try invoking the Lambda API in the Developer Portal.

!!! note "Configure Connection Pooling"
This capability is supported only from the U2 levels listed below in APIM products

- wso2am-4.6.0 - U2 level 19
- wso2am-acp-4.6.0 - U2 level 20
- wso2am-universal-gw-4.6.0 - U2 level 19
- wso2am-wso2am-tm-4.6.0 - U2 level 19

You can fine-tune the underlying HTTP connection pool used by the **AWS Lambda client** to optimize performance under high load.

To configure the connection pooling, add the following configuration to the <code>&lt;API-M_HOME&gt;/repository/conf/deployment.toml</code> file. For more information, see [Configuration Catalog]({{base_path}}/reference/config-catalog/).



```toml
[apim.aws_lambda.http_client]
max_connections = 50
connection_timeout = 10
socket_timeout = 30
connection_acquisition_timeout = 60
```

The elements in the above configuration are described below. If these values are not configured, the system will use the default settings.

<table>
<thead>
<tr>
<th>Setting</th>
<th>Key</th>
<th>Description</th>
<th>Default</th>
</tr>
</thead>

<tbody>
<tr>
<td><strong>Max Connections</strong></td>
<td><code>max_connections</code></td>
<td>
The maximum number of concurrent HTTP connections allowed in the pool.
Increase this value if you expect high concurrent throughput to Lambda functions.
</td>
<td>100</td>
</tr>

<tr>
<td><strong>Connection Timeout</strong></td>
<td><code>connection_timeout</code></td>
<td>The maximum time (in seconds) to wait when establishing a new TCP connection to AWS.</td>
<td>2 seconds</td>
</tr>

<tr>
<td><strong>Socket Timeout</strong></td>
<td><code>socket_timeout</code></td>
<td>The maximum time (in seconds) to wait for data to be transferred after a connection is established.</td>
<td>30 seconds</td>
</tr>

<tr>
<td><strong>Connection Acquisition Timeout</strong></td>
<td><code>connection_acquisition_timeout</code></td>
<td>
The maximum time (in seconds) to wait for a connection to become available from the pool
if <strong>Max Connections</strong> has been reached.
</td>
<td>30 seconds</td>
</tr>
</tbody>
</table>

These configurations serve as the global settings for all AWS Lambda endpoints in the Gateway. However, please note that each API resource initializes its own independent **AWS Lambda client**. Therefore, the values defined here (such as <code>max_connections</code>) are applied per API resource, not as a server-wide aggregate limit.
5 changes: 5 additions & 0 deletions en/tools/config-catalog-generator/data/apim.aws_lambda.http_client.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
[apim.aws_lambda.http_client]
max_connections = 50
connection_timeout = 10
socket_timeout = 30
connection_acquisition_timeout = 60
45 changes: 45 additions & 0 deletions en/tools/config-catalog-generator/data/configs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6498,6 +6498,51 @@
}
],
"exampleFile": "web_app.cookie_processor.toml"
},
{
"title": "API-M AWS Lambda Configurations",
"options": [
{
"name": "apim.aws_lambda.http_client",
"required": false,
"description": " Configurations to tune the underlying HTTP connection pool settings used by each AWS Lambda client instance, to improve performance under high load.",
"params": [
{
"name": "max_connections",
"type": "integer",
"required": false,
"default": "100",
"possible": "",
"description": "The maximum number of concurrent HTTP connections allowed per AWS Lambda client instance. Increase this value if you expect high concurrent throughput to Lambda functions."
},
{
"name": "connection_timeout",
"type": "integer",
"required": false,
"default": "2",
"possible": "",
"description": "The maximum time (in seconds) to wait when establishing a new TCP connection to AWS."
},
{
"name": "socket_timeout",
"type": "integer",
"required": false,
"default": "30",
"possible": "",
"description": "The maximum time (in seconds) to wait for data to be transferred after a connection is established."
},
{
"name": "connection_acquisition_timeout",
"type": "integer",
"required": false,
"default": "30",
"possible": "",
"description": "The maximum time (in seconds) to wait for a connection to become available from the pool if max_connections has been reached."
}
]
}
],
"exampleFile": "apim.aws_lambda.http_client.toml"
}
]
}
Expand Down