April 11, 2022 — New release
-
Granular namespace permissions
When creating a namespace you can now define user access and permissions to that namespace using Akamai Control Center group membership. EdgeKV achieves this by tying a namespace to a Control Center access group.You can make a namespace available to ANY access group under a contract with EdgeKV entitlement if the namespace is created using
groupId=0. Alternatively, you can lock access to a namespace to a single access group when a groupID, such as groupId=1234, is specified. For more information about granular namespace permissions see Manage access to EdgeKV. -
EdgeKV access token expiration notification
An Akamai Control Center notification now appears when an access token approaches its expiration date. Some users will also receive the 1 day notification in an email in addition to the notification center. For more information about who can receive these messages and when notifications are sent, refer to the Generate and retrieve EdgeKV access tokens section in the documentation. -
Increased limits
We updated the following product limits to expand the supported use cases for EdgeKV and remove earlier constraints. Some of these limits are orders of magnitude higher, so please refer to the EdgeKV guide for a complete list of all the limits.
| Description | Previously supported limit | New limit for April 2022 release |
|---|---|---|
| Recommended data storage limit per account | 200 GB | 20 TB |
| Items per account | 2,000,000 | 200,000,000 |
| Items per namespace | 100,000 | 10,000,000 |
| Value size | 256 KB | 999,999 Bytes |
| Number of item reads per second from EdgeWorkers | The maximum number of reads per second is defined by the EdgeWorkers HTTP sub-request limitations. - an aggregate of 2,500 reads per second from all EdgeWorkers for up to 98/2 read/write ratio. - an aggregate of 250 reads per second from all EdgeWorkers when the write ratio is greater than 2%. | The maximum number of reads per second is defined by the EdgeWorkers HTTP sub-request limitations. - an aggregate of 10,000 reads per second from all EdgeWorkers for up to 98/2 read/write ratio. - an aggregate of 1,000 reads per second from all EdgeWorkers when the write ratio is greater than 2%. |
| Number of items returned per group read request | 100 by default. | The number of items returned per group read request can now be configured to return a value between 1 and 1000 using the maxItems query string. The default value remains at 100. |
| Number of item writes/deletes per second from EdgeWorkers | An aggregate of 50 per second allowed from all EdgeWorkers. | An aggregate of 200 per second allowed from all EdgeWorkers. You can now exceed more than an aggregate of 40 instead of 10 write/delete operations per second before distinct items negatively impact read performance and throughput. |
| Number of tokens per account | Revoked tokens may count towards the limit for one month after expiry. | Revoked tokens no longer count towards this limit. |
-
Updates to the EdgeKV CLI package
(Note that you need to update or install the latest version of the EdgeKV CLI package to access these enhancements.)
- You can now specify which Akamai Control Center groupIds can access a namespace. Previously the groupId could only be set to 0 which allows access to all groups in your account.
- The CLI now lets you list all the permission groups with EdgeKV access, list the details for a specific permission group, and modify the permissions group associated with a namespace.
- You can the details of a specific data group.
- The list items command now supports
maxitems.maxItemslets you specify how many items to return when performing a group read request. - When creating a namespace in production you can specify any of the supported namespace geolocations.
- We fixed an issue in the create token command where restricting the access token to a specific EdgeWorker ID did not take effect.