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
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
Open Object Storage
In the portal sidebar, click Object Storage under Infrastructure, then click Create Bucket.
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.
Step 2: Upload a file in the portal
Open the bucket
Click the bucket name in the list. The bucket has three tabs: Objects, Metrics and Settings.
Step 3: Create an S3 credential
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.)
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:
Create a small file and upload it. Replace WORKSPACE-ID with the value from your S3 Endpoint:
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.
Download it again and compare:
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.
- Delete every object in the bucket:
aws s3 rm s3://my-first-bucket --recursive --endpoint-url https://WORKSPACE-ID.blob.ibeestorage.com --profile ibee - In the portal, open the bucket → Settings → General, and click Delete bucket in the Danger Zone. Confirm with Delete.
- Open Organization → API Tokens → S3 Credentials, click Revoke on the
quickstartcredential, then Delete.
Limits and timing
Troubleshooting
Related pages
- Core Concepts
- Objects: folders, downloads and bulk delete
- API Credentials: permission levels and rotation
- Presigned URLs: share a file with a link
- Bucket Policies: make a bucket public
