The permissions granted to an API client are identical to those of the user creating it. If a user's permissions change after the API client is created, the API client permissions are not automatically updated.
We recommend that you create a new API client to use with EdgeKV during this availability phase. You should do this even if you already have a working API client for EdgeKV for a previous phase. You should also create a new API client whenever a user’s permissions are modified, as described above. You can also deactivate the API clients that you are no longer using at any time.
To use EdgeKV management APIs or the Edge KV CLI, the API credentials need to be created using the Admin role. You can also use a custom role based on the Publisher or Editor roles. When using the custom role, you need to add the CP Code - View CP Code Information- View CP Codes permission. Without the View CP Code permission you may get a “500 Server Error, An internal error occurred” response. For more information refer to the Assign roles and permissions section.
Akamai Sandbox cannot currently be used to test an EdgeWorker ID that includes EdgeKV functionality. We are working to remedy this issue.
EdgeKV is not supported on Akamai CDNs created to accommodate unique regional or governmental requirements. This limitation currently includes China.
EdgeKV data cannot be used to calculate a cacheKey in an EdgeWorkers function. The EdgeWorkers
onClientRequest event handler may succeed, but the data purging may fail or result in incorrect behavior.
A timeout may occur when trying to initialize a namespace through the CLI, and you may receive this error:
ERROR: Error while creating namespace. The EdgeKV service was unable to respond in time. Please retry the request later. [TraceId: undefined]
We recommend that you retry the initialization using a larger timeout value directive with each CLI command, such as,
--timeout 2000000. We are actively working to resolve this problem.
First, make sure you have API credentials for a user at the top level group under your account. If you still get a failure, you can try calling the Initialize EdgeKV API endpoint or CLI command again.
If initialization continues to fail, capture the API response or CLI command output. You'll also need the response from the
GET /edgekv/v1/initialize API or the output of the
edgekv show status CLI command to help debug the problem. Once you have this information please contact Akamai support at email@example.com.
If you receive an error indicating that, “The client does not have the grant needed for the request,” your API client is missing the required READ-WRITE access level. For instructions on how to add it, refer to the Get started section in the EdgeKV API documentation.
The EdgeKV CLI
--overwrite option for the token
download commands does not work when you change the token name associated with a namespace.
As a workaround, you can manually delete the token in question from the
edgekv_tokens.js file before using the
--save_path option. You can then use the token create and download CLI commands with the
--save_path option to update the
Updated about 19 hours ago