Keep these limitations in mind when designing your EdgeWorkers functions. These limitations apply to all EdgeWorkers functions regardless of the selected resource tier.
You can also refer to the limitations that are applied based on the resource tier you selected for your EdgeWorker ID.
|Supported delivery products||Ion|
Dynamic Site Accelerator (DSA)
Adaptive Media Delivery
|Supported delivery method||Enhanced TLS|
When you've applied a custom certificate to a property configuration, the associated Edge hostname uses the
Standard TLS, used to serve non PCI compliant traffic over HTTP or HTTPS via an
Note: EdgeKV is currently not supported if you select the Standard TLS delivery method.
EdgeWorkers is not supported on Akamai CDNs created to accommodate unique regional or governmental requirements. This limitation currently includes China CDN.
|Execution restrictions||EdgeWorkers functions cannot be executed by an ESI (Edge Side Includes) fragment request.|
|Number of EdgeWorker scripts executed per request||1|
|Maximum number of EdgeWorker IDs per account||200|
|Maximum number of versions per EdgeWorker ID||1000|
|Maximum number of activations each minute on a network per account||20|
|Maximum number of activations each day per account||500|
|Compressed size for a code bundle||512 KB|
|Uncompressed size for a code bundle||1 MB|
|Maximum response header size for HTTP sub-requests||8000 bytes|
|Maximum body size for responses created through the ||2048 characters|
|Maximum body size for responses from origin to an EdgeWorkers function, using ||128 KB when using |
5 MB when using
|Maximum body size for responses from an EdgeWorkers function to a browser when the response is passed through as a string||100,000 bytes if you pass a string to |
No direct limit if you pass a stream to
|Maximum body size for responses from an EdgeWorkers function to a client browser||2048 characters if you use |
|Maximum body size when ||16 KB|
|Maximum streaming request body size when ||1 MB|
Updated 3 days ago