Skip to navigation

Upload Your First Object

This quickstart is a 10-minute path to a working bucket. You create a bucket, upload a file in the portal, then use the AWS CLI to upload, list and download files the way your apps will. At the end you delete what you made, so nothing keeps costing money.

When to use this guide

You want to…Start here
Try Object Storage for the first timeThis page
Understand buckets, keys and endpoints firstCore Concepts
Connect an existing S3 app or SDKUsing the S3 API
Share one file with someonePresigned URLs

Before you begin

  • An IBEE organization with identity verification (KYC) completed. See Verify your identity.
  • For organizations billed in India: a verified payment method (₹1, added to your wallet), unless you’ve already paid a top-up or an invoice. See Verify a payment method.
  • For steps 3–5, an S3 credential. If your organization is verified by the ₹1 alone, S3 credentials need a first top-up of at least ₹500. Without one, you can still do steps 1 and 2 in the portal, and delete the bucket there (step 6).
  • Wallet credit or billing set up. Storage, downloads and requests are billed by usage; see Pricing.
  • The AWS CLI version 2 on your computer, for steps 3–5. Install it from the AWS CLI guide, then check with aws --version.
  • Access to Organization → API Tokens in the portal, to create an S3 credential.

Step 1: Create a bucket

1

Open Object Storage

In the portal sidebar, click Object Storage under Infrastructure, then click Create Bucket.

2

Name the bucket

Under Bucket name, enter a name such as my-first-bucket: 3–63 characters, lowercase letters, numbers and hyphens, starting and ending with a letter or number. The name must be new in this workspace.

3

Choose the location and storage type

Keep Automatic location, or click Need a specific location? click here and pick Amaravati. Under Storage type, keep the selected plan.

Leave Versioning and object lock off for this quickstart: Object lock (WORM) makes a bucket that can never be deleted.

4

Create it

Click Create Bucket. The page shows Creating bucket…, usually for a few seconds, then the toast Bucket created successfully. If it takes more than 10 seconds you see This is taking longer than usual. We’re still creating your bucket. — wait, or click Check status.

Step 2: Upload a file in the portal

1

Open the bucket

Click the bucket name in the list. The bucket has three tabs: Objects, Metrics and Settings.

2

Upload

On the Objects tab, click Upload (or Upload Files in an empty bucket) and choose a file, or drag one onto the list. Each file can be up to 300 MB in the portal.

3

Check it

The file appears in the list with its Type, Storage Class, Size and Modified date. Click its name to see details and download it.

Step 3: Create an S3 credential

1

Open S3 Credentials

In the sidebar, open Organization → API Tokens, then the S3 Credentials tab. (The S3 API Credentials button on the Object Storage page opens the same tab.)

2

Create the credential

Click Create S3 Credential. Enter a name such as quickstart, choose the bucket’s workspace, and choose Object Read & Write with Apply to specific buckets only → my-first-bucket. Click Create Credential.

3

Copy the three values

Copy the Access Key ID, Secret Access Key and S3 Endpoint (https://WORKSPACE-ID.blob.ibeestorage.com) now.

The Secret Access Key is shown once. If you lose it, revoke the credential and create a new one.

A workspace’s endpoint is set up when its first credential is created and can take a few minutes to start answering.

Step 4: Upload and list with the AWS CLI

Save the credential as a profile called ibee. These four commands set the keys, the region auto (IBEE rejects the AWS default us-east-1) and path-style addressing:

aws configure set aws_access_key_id YOUR-ACCESS-KEY-ID --profile ibee
aws configure set aws_secret_access_key YOUR-SECRET-ACCESS-KEY --profile ibee
aws configure set region auto --profile ibee
aws configure set s3.addressing_style path --profile ibee

Create a small file and upload it. Replace WORKSPACE-ID with the value from your S3 Endpoint:

echo "hello, IBEE" > hello.txt
aws s3 cp hello.txt s3://my-first-bucket/hello.txt \
--endpoint-url https://WORKSPACE-ID.blob.ibeestorage.com --profile ibee

The CLI prints upload: ./hello.txt to s3://my-first-bucket/hello.txt.

Step 5: Verify and download

List the bucket. You should see both files: the one from the portal and hello.txt.

aws s3 ls s3://my-first-bucket/ \
--endpoint-url https://WORKSPACE-ID.blob.ibeestorage.com --profile ibee
2026-10-30 10:15:02 12 hello.txt

Download it again and compare:

aws s3 cp s3://my-first-bucket/hello.txt ./hello-copy.txt \
--endpoint-url https://WORKSPACE-ID.blob.ibeestorage.com --profile ibee
cat hello-copy.txt

Step 6: Clean up

Delete what you made so it stops being billed.

Deleting objects and buckets can’t be undone. Check the bucket name before you run these commands.

  1. Delete every object in the bucket: aws s3 rm s3://my-first-bucket --recursive --endpoint-url https://WORKSPACE-ID.blob.ibeestorage.com --profile ibee
  2. In the portal, open the bucket → Settings → General, and click Delete bucket in the Danger Zone. Confirm with Delete.
  3. Open Organization → API Tokens → S3 Credentials, click Revoke on the quickstart credential, then Delete.

Limits and timing

Value
Bucket creationUsually a few seconds; the portal warns after 10 seconds
Portal uploadUp to 300 MB per file
One-request upload (CLI, SDK)Up to 5 GiB; the AWS CLI splits bigger files into parts automatically
New workspace endpointCan take a few minutes after the first credential is created
Secret Access KeyShown once

Troubleshooting

You seeWhat it meansWhat to do
Verify Identity instead of Create BucketIdentity verification isn’t completeFinish identity verification.
Verify payment method instead of Create BucketYour organization must verify a payment method firstClick it and pay ₹1, which is added to your wallet. See Verify a payment method.
Top up ₹500 on the S3 credentials tabYour organization is verified by the ₹1 aloneTop up at least ₹500, or work in the portal only (steps 1, 2 and 6).
Bucket name must start and end with a letter or number, and contain only lowercase letters, numbers, and hyphensThe name has uppercase letters, dots, underscores or spacesUse lowercase letters, numbers and hyphens.
Bucket already existsThis workspace already has a bucket with that nameChoose another name.
Files larger than 300 MB must be uploaded via the API.The portal’s per-file limitUpload with the AWS CLI (step 4).
403 AccessDenied — Invalid region scopeThe CLI signed with us-east-1 or another regionRun aws configure set region auto --profile ibee.
”Could not resolve host” for my-first-bucket.WORKSPACE-ID.blob.ibeestorage.comThe CLI put the bucket name in the hostnameRun aws configure set s3.addressing_style path --profile ibee.
403 AccessDenied — Invalid access keyThe key was mistyped, or the credential was revokedCopy the Access Key ID again, or create a new credential.
403 SignatureDoesNotMatchThe secret key is wrongCopy the Secret Access Key again with no spaces.
403 AccessDenied — Access key does not belong to this workspaceThe endpoint is another workspace’sUse the S3 Endpoint shown with this credential.
Delete bucket is disabled: This bucket contains X objects. Empty it first to delete.Only empty buckets can be deletedRun the cleanup command in step 6, or use Empty bucket.