Enhanced token workflow

You can now delete a namespace and all of its contents. You might want to delete a namespace if you're about to reach the limit on the number of namespaces per account.

When creating a namespace you can now specify a GLOBAL storage location for data on the production network. The GLOBAL location automatically replicates data to US, EU, and JP storage locations. If you use the GLOBAL location, reads are faster but write operations are slightly slower.

EdgeKV is now supported in Beta using the Standard TLS delivery method. By default, EdgeKV databases can only access data from Akamai's Enhanced TLS network. You can, however, configure the data access policy to allow access from both Akamai's Enhanced TLS and Standard TLS networks.

EdgeKV reports are now available in the EdgeWorkers Management application. This dashboard will help you understand your usage of EdgeKV, troubleshoot errors, and ensure you stay within system limits.

The new EdgeKV Postman collection (beta) is now available! Try the API, build workflows, and stay on top of development changes.

You can now test your EdgeKV-enabled EdgeWorkers functions in Sandbox. Sandbox is an isolated development environment that lets you test locally before deploying to production.

You can now use the administrative API to list groups within a namespace.

• 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.

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.