Akave O3 setup

Setting Up an AWS CLI Profile for Akave O3

To streamline your workflow, you can configure a dedicated AWS CLI profile for interacting with Akave O3. This allows you to avoid setting environment variables for each session and keeps your credentials organized under a named profile.

Installation

Before setting up the profile, make sure you have the AWS CLI installed for your operating system using the installation instructions here.

Step 1: Configure the Profile

aws configure --profile akave-o3

Enter:

• AWS Access Key ID: <your-access-key>
• AWS Secret Access Key: <your-secret-key>
• Default region name: akave-network
• Default output format: json

You can also edit the credentials file at ~/.aws/credentials and add the endpoint URL to avoid having to use the --endpoint-url flag in every command. Note that this only applies to commands used with the specific profile(s) you have the endpoint_url variable listed for.

Use the below command to edit the credentials file:

nano ~/.aws/credentials

Then add the following to the file:

[akave-o3]
aws_access_key_id = <your_access_key>
aws_secret_access_key = <your_secret_key>
endpoint_url = https://o3-rc2.akave.xyz

Make sure to save your changes and exit the editor.

Step 2: Use the Profile in Commands

aws s3api list-buckets \
  --profile akave-o3 \
  --endpoint-url https://o3-rc2.akave.xyz

You can now run any AWS CLI or s3api command with --profile akave-o3 instead of exporting your credentials each time.

Note: Throughout the rest of the documentation, we won’t include the --profile flag in every command. It’s up to you whether to use a profile or export credentials manually – both approaches are supported.