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.
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.
You can now use the
geoLocation parameter to specify the storage location for data when creating a namespace on the production network. This can help optimize performance by storing data where most or all of your users are located. By default, the
geoLocation is set to
US (United States). The available geoLocations on the production network also include
EU (Europe) and
JP (Japan). For more information see the Namespace section in the EdgeKV data model documentation.
num_retries_on_timeout parameter lets you specify the maximum number of retries to attempt when executing the getText() and getJson() methods. You can also specify the number of retries to attempt in the Constructor.
We’ve made more enhancements to the administrative API and command-line interface (CLI) for EdgeKV.
We've made several enhancements and bug fixes to the administrative API and command-line interface for EdgeKV.
To improve the EdgeKV developer experience we’ve made the following improvements to our helper library.