---
title: "Access Keys in Wasabi Hot Cloud Storage"
slug: "access-keys-1"
description: "An access key is used to make programmatic calls to AWS API actions. When using the S3 API, you must have an API access key set to exchange storage files between your application and the Wasabi service. There are two types of access keys: Access Key ID and Secret Access Key."
tags: ["Access Key ID", "Secret Access Key"]
updated: 2026-05-07T14:56:47Z
published: 2026-05-07T14:57:06Z
canonical: "docs.wasabi.com/access-keys-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Access Keys in Wasabi Hot Cloud Storage

An access key is used to make programmatic calls to AWS API actions. When using the S3 API, you must have an API access key set to exchange storage files between your application and the Wasabi service. There are two types of access keys:

- Access Key ID
- Secret Access Key

Each key is a text string that you will cut/paste into your storage application. For your protection, you should never share your secret keys with anyone. In addition, industry best practice recommends frequent key rotation.

Access keys are used to make secure REST or Query protocol requests to the Wasabi service API. The Wasabi S3 endpoint is **s3.wasabisys.com**. (See also the [service URLs for different regions](https://docs.wasabi.com/docs/what-are-the-service-urls-for-wasabis-different-storage-regions).) If using Cyberduck, for example as shown below, you would need to enter the appropriate keys in the “Access Key ID” and “Secret Access Key” fields. This is an example of one of many applications that can connect to the Wasabi endpoint.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1698439684919.png)

## Related

- [Reviewing the Access Keys Panel](/reviewing-the-access-keys-panel.md)
- [Managing Access Keys](/changing-the-access-key-status.md)