Connect an S3 client
CloudNx object storage speaks the S3 API. Any S3 client works once it has four settings right: the endpoint, the region, path-style addressing, and an access key copied exactly.
The settings
| Endpoint | https://s3.cloudnx.in (port 443) |
|---|---|
| Region | in-mum |
| Addressing style | Path-style: https://s3.cloudnx.in/my-bucket/key |
| Access key ID | 20 characters, starts with CN, e.g. CNEXAMPLE7KQ2M4ZB5RT |
| Secret access key | 40 characters, shown once when the key is created |
Path-style, not virtual-host
Many clients default to virtual-host addressing, which puts the bucket in the hostname (my-bucket.s3.cloudnx.in). That is not supported yet: configure every client for path-style, as in the examples below.
Get a key
Portal → Storage → Access keys → New access key. Choose a permission and either all your buckets or specific ones. After creating it, the dialog tests the key with a signed request and shows Key tested: works (or the error), and offers ready-made configuration for the clients below, a .csv of the credentials and a Cyberduck bookmark. Use the copy buttons rather than selecting the text by hand — a stray space or line break in the key ID is the most common cause of InvalidAccessKeyId.
Key names are unique per account, so each key in the list can be told apart.
Cyberduck
- In Cyberduck, open Preferences → Profiles, search for S3 (Deprecated path style requests) and enable it. (The plain Amazon S3 profile uses virtual-host addressing and will not work.)
- Either download Cyberduck bookmark (.duck) from the create-key dialog and open it, or click Open Connection and fill in:
- Profile: S3 (Deprecated path style requests)
- Server:
s3.cloudnx.in, Port:443 - Access Key ID: your
CN…key ID - Secret Access Key: your secret
- Path (under More Options, optional):
/my-bucket— set this if the key is limited to specific buckets
- The bookmark does not contain the secret. Cyberduck asks for it on the first connection and can store it in your keychain.
AWS CLI
Setting endpoint_url in the config file needs AWS CLI v2.13 or later; on older versions pass --endpoint-url https://s3.cloudnx.in on each command instead.
# ~/.aws/credentials
[cloudnx]
aws_access_key_id = CNEXAMPLE7KQ2M4ZB5RT
aws_secret_access_key = <secret>
# ~/.aws/config
[profile cloudnx]
region = in-mum
endpoint_url = https://s3.cloudnx.in
s3 =
addressing_style = pathaws s3 ls s3://my-bucket --profile cloudnx
aws s3 cp report.pdf s3://my-bucket/ --profile cloudnxrclone
# ~/.config/rclone/rclone.conf
[cloudnx]
type = s3
provider = Minio
access_key_id = CNEXAMPLE7KQ2M4ZB5RT
secret_access_key = <secret>
endpoint = https://s3.cloudnx.in
region = in-mum
force_path_style = truerclone ls cloudnx:my-bucket
rclone sync ./backups cloudnx:my-bucket/backupsPython (boto3)
import boto3
from botocore.config import Config
s3 = boto3.client(
"s3",
endpoint_url="https://s3.cloudnx.in",
region_name="in-mum",
aws_access_key_id="CNEXAMPLE7KQ2M4ZB5RT",
aws_secret_access_key="<secret>",
config=Config(s3={"addressing_style": "path"}),
)
s3.upload_file("report.pdf", "my-bucket", "report.pdf")JavaScript (AWS SDK v3)
import { S3Client, ListObjectsV2Command } from "@aws-sdk/client-s3";
const s3 = new S3Client({
region: "in-mum",
endpoint: "https://s3.cloudnx.in",
forcePathStyle: true,
credentials: {
accessKeyId: "CNEXAMPLE7KQ2M4ZB5RT",
secretAccessKey: process.env.CLOUDNX_S3_SECRET,
},
});
await s3.send(new ListObjectsV2Command({ Bucket: "my-bucket" }));Troubleshooting
| Error | Usual cause | Fix |
|---|---|---|
InvalidAccessKeyId — “The Access Key ID you provided does not exist” | The key ID was mistyped, picked up an extra space or line break when pasted, or the key was deleted. | Re-paste the key ID using the copy button (or from the downloaded .csv). Check that it is exactly 20 characters and still listed under Access keys. |
SignatureDoesNotMatch | Wrong secret (or a stray character in it), or your computer’s clock is off by more than 15 minutes. | Re-paste the secret. If it was not saved, delete the key and create a new one — secrets cannot be shown again. Turn on automatic time sync. |
AccessDenied | The key is signed correctly but not allowed to do this: the bucket is not in the key’s scope, or the permission is too narrow (for example a read-only key uploading). | Check the key’s scope and permission under Access keys; create a key with the right ones. |
AuthorizationHeaderMalformed | The client signed for a different region (often us-east-1). | Set the region to in-mum. |
NoSuchBucket | The bucket name is wrong, or the client is using virtual-host addressing. | Check the name in the portal and switch the client to path-style. |
Still stuck? Open a support ticketwith the key’s name and the exact error — never the secret.