S3 access keys enable the authentication of compatible applications and tools to Cyberin S3 Object Storage. They are commonly used to connect storage clients, scripts and apps to a storage Space .
This guide explains how to obtain or create access keys, configure an S3-compatible client with them, and handle them securely.
Log into your Cyberin account
Go to your S3 Object Storage service.
Search for the access credentials, API keys or S3 access management section.
Select the Create access key or Generate access key action, if available.

Follow the instructions displayed on the dashboard.
If displayed, securely save the access key ID and secret access key.
The access key ID is the identifier of the credentials, and the secret access key is used to authenticate the requests. Consider the secret key as a password.
If you don’t see an option to create keys, check the service documentation or contact Cyberin Support to confirm the process for provisioning credentials.
To be able to connect a compatible client to Cyberin S3 Object Storage you will typically require the following information:
Access key id: The name of your S3 credentials.
Secret Access Key The secret key for request authentication.
Endpoint: The endpoint assigned to your Cyberin storage service.
Region: The region you chose for your storage service.
Space Name: The name of the space you want to access.
These details should be in your S3 compatible client config settings. The field names and how you set them up will vary depending on the tool you use.
Make sure your Cyberin service has the correct endpoint and region. Do not replace data from another storage provider.
Follow these security practices when using S3 access keys:
Never share your secret access key publicly.
Do not publish credentials in source code, public repositories, screenshots, or support requests.
Store credentials using a secure configuration file, environment variables, or another secrets manager.
If permission controls are supported, use the minimum permissions required for the task at hand.
Use different credentials for unrelated apps.
Check credentials and change if compromised.
If you think your credentials might have been compromised, act quickly.
If available, open the section on open access credential management.
Create a new key
“Update applications and tools with the compromised credentials.
Ensure that objects needed by new config are accessible.
If possible revoke/disable the exposed credentials from the dashboard.
Make sure you check to see which apps are using a key before you revoke it. If a key is revoked too early, it will break access to the storage.
If self-service key rotation or revocation is not supported in your Cyberin account, please reach out to Cyberin Support for the supported process.
Check that the access key ID was copied correctly.
Confirm that you are using credentials associated with the correct storage service.
Remove unintended spaces or extra characters.
Verify the secret access key.
Check the configured endpoint and region.
Confirm that the client supports S3-compatible storage and is configured correctly.
Review the complete error message returned by the client.
Valid credentials do not automatically grant permission to every Space for object. Check whether the credentials are authorized to perform the requested action and whether the Space or object is private.
Update the application's configuration with the current credentials. If the old key was revoked, confirm that no remaining service is still using it.
If you cannot create, locate, or update S3 access keys, contact Cyberin Support. Include the error message, the client you are using, and the operation you attempted.
Never include your secret access key or password in the support request.