Akave O3
Solutions and Integrations
Akash

Akash

Akash is a decentralized compute protocol that provides a secure, scalable, and cost-effective way to run and manage compute resources. It allows applications to utilize the Akave O3 decentralized storage endpoints.

Prerequisites

  • Akash account
    • If you do not already have an Akash account, please create one at Akash
  • Akave Cloud Credentials
    • If you do not already have these, please create them on Akave Cloud

Setup Guide

To get started with Akave and Akash, make sure you have access to your Akave:

  • Access Key ID
  • Secret Access Key
  • Endpoint URL

As well as a bucket in Akave to store your data. More information on how to create a bucket can be found in the Bucket Management section of these docs.

Akash Configuration

Start by opening the Akash Console at: console.akash.network

Then, click on the “Deploy” button.

Akash Deploy

Then from the available options you can select “Upload your SDL” and use the example SDL provided here: akave.yaml

  • Replace the AKAVE_ENDPOINT with the appropriate Akave Endpoint URL
  • Replace the AKAVE_BUCKET with your Akave Bucket Name
  • Replace the AKAVE_ACCESS with your Akave Access Key ID
  • Replace the AKAVE_SECRET with your Akave Secret Access Key

Note: These are all values in the env section of the SDL, and so won’t be exposed after deployment.

Akave SDL

Next, name your deployment, add funds to the Akash escrow account, then select a provider and deploy.

Escrow

In this example I select the “hurricane” provider from Akash.

Provider Selection

Once deployed you’ll be able to see information on the deployment similar to the one below, which includes a URI to view your deployed service.

ℹ️
Note that the deployment may take a few minutes to fully initialize and become available.

Deployment Details

Usage

For the example SDL provided above this creates a service that interacts with the Akave O3 endpoint at the URI shown. You can use this URI to see objects uploaded to your Akave bucket, as well as access those objects with pre-signed URLs. The SDL uploads an object to the bucket as part of the deployment process, demonstrating that the integration is working correctly.

You can verify the object was uploaded by checking your Akave bucket using standard object management commands.

This basic deployment demonstrates how to launch an Akash instance which interacts with Akave storage and uses the AWS CLI to:

Deployed

To add additional functionality modify the SDL using:

Last updated on
Akave MCP Server