• You can now use the EdgeWorkers Management application, the API, and CLI to delete an EdgeWorker ID and version.
• Delete an EdgeWorker ID from your property configuration. All versions, code bundles, and the activation and deactivation history associated with the EdgeWorker ID are also deleted.
• Delete an EdgeWorker version from an EdgeWorker ID.
• View the properties using an existing EdgeWorker ID.

We are pleased to announce a new availability phase for EdgeWorkers. During the last availability phase we introduced the EdgeWorkers Management application, response orchestration, expanded product delivery support, and increased resource limits. We also added support for EdgeKV, a key-value store database.

• All event handlers now support HTTP sub-requests.
• A getHeaders() method is now available for the Request Object in the responseProvider event handler. A getHeaders() method is also available for the httpResponse Object.
• We added an FAQ section to answer commonly asked questions about EdgeWorkers.
• We added Best practices for performance to help you maximize the performance of your custom JavaScript code.
• You can now deactivate an EdgeWorker version. The deactivation history of an EdgeWorker version is also available.
• When activating an EdgeKV-enabled EdgeWorkers code bundle the EdgeKV files are now validated. We’ve added error messages that describe which files or tokens are missing, invalid, or expired.

• Response Orchestration - With the introduction of Response Orchestration, EdgeWorkers now supports the ability to read and modify response bodies. This capability lets EdgeWorkers developers make Edge decisions, build content, and optionally cache response output.
• External requests - External requests are supported via the responseProvider event handler. EdgeWorkers developers can now fetch resources from other external origins and add them directly or indirectly into the main response body.
• Reports - We’ve added Reports to the EdgeWorkers Management application to provide insight about the performance and execution status of your EdgeWorkers.
• Fast Activation - EdgeWorkers supports Fast Activation to decrease the EdgeWorkers code bundle activation times.
• Expanded Product Delivery support - The following media products are now supported as EdgeWorkers delivery products: Adaptive Media Delivery, Download Delivery, Object Delivery, and API Acceleration.
• Enhanced debug headers - To protect sensitive content, EdgeWorkers now require an authorization token in an additional second header to retrieve detailed debug information.
• Increased resource limit - We’ve increased the memory, CPU time, and wall time compute resources limits.

EdgeWorkers code bundles can now be directly edited in the EdgeWorkers Management application user interface!
Online code editing is ideal for small code changes and iterative bug fixes. Coding, configuration, and activation can all be done centrally within the EdgeWorkers UI.
To learn more see Code bundle editor.

• EdgeWorkers now supports user-defined variables via the setVariable() request method.
• You can use setVariable to interact with Property Manager or to maintain a state where EdgeWorkers can pass information between callbacks.

This next release of EdgeWorkers uniquely combines the power of Serverless functions and the Akamai Edge; the April release adds powerful features to improve cached delivery and offload, as well as other features to ensure fast and accurate coding from design to production.

We’re excited to announce the expansion of EdgeWorkers to Akamai’s enhanced secure network. You can now run edge functions everywhere on the network. Other notable changes include our new EdgeWorkers Management application and the Command Line Interface (CLI).