S3-compatible API
Works with the AWS SDKs, the CLI, s3cmd and anything else that speaks S3. The endpoint and the region change; the code does not.
Addis Ababa, Ethiopia. Support on 6993.MCP ready. Attach your agents 100% self-service. Sign up using google or phone number. No sales call to get started
Buckets on AletCloud's storage fabric, reached at one endpoint with the tools you already use. Change the endpoint and the region, and code written against AWS keeps working.
From 5 GB at 50 ETB a month, in et-addis-1.
Nothing here is an AletCloud client library. The endpoint speaks S3, so the four steps end with the same commands and SDK calls you would write against anybody else's storage.
01
A name, a capacity and whether the objects are readable by anyone. Versioning is a switch at creation, and the bucket exists by the time the dialog closes.
Bucket name
shop-media
3 to 63 characters, lowercase letters, numbers and hyphens. It cannot start or end with a hyphen.
Storage tier
02
Each key pair reaches this bucket and no other bucket on the account, so an app, a script or an agent gets its own and loses it the moment you revoke it. The secret is shown once, at the moment it is made.
Revoking one key leaves every other key on the bucket working.
03
Two environment variables and the AWS CLI, boto3, the JavaScript SDK or s3cmd are talking to Addis instead of Virginia. For a one-off handover, a presigned URL gives somebody an hour on a single object without a key.
export AWS_ENDPOINT_URL=https://s3.aletcloud.com export AWS_REGION=et-addis-1 $ aws s3 cp poster.jpg s3://t01-shop-media/ upload: ./poster.jpg to s3://t01-shop-media/poster.jpg
https://s3.aletcloud.com/t01-shop-media/poster.jpg?X-Amz-Expires=3600
04
Pick a hosted app and the console mints a key, writes the five variables into its environment and redeploys it. Nothing is copied through a clipboard, and the secret never leaves the platform.
Redeployed, and reading from the bucket on the next request.
All seven on the 5 GB bucket and on the 100 GB one. Nothing here is held back for the larger tiers.
Works with the AWS SDKs, the CLI, s3cmd and anything else that speaks S3. The endpoint and the region change; the code does not.
Name it, pick a capacity, and there is an endpoint and a key pair waiting. Uploading can start before you have finished reading this card.
Issue a key pair per app or per agent and revoke it on its own. A key reaches the bucket it was made for and nothing else on the account.
Serve assets straight off a public URL, or keep the bucket closed and hand out presigned links that expire. The setting is per bucket and changes whenever.
Connect a bucket to a hosted app and the S3 variables are written into its environment and the app redeployed, with no secret passing through you.
The objects sit in Addis Ababa, a few milliseconds from anyone in the country and inside Ethiopian jurisdiction rather than under somebody else.
Top up through chapa.
Short answers to the ones that come up most. For anything else, call 6993 and a person answers.
Ask us something elseYes. It speaks the S3 API, so the AWS SDKs, the AWS CLI, s3cmd and most S3 libraries work once they are pointed at the AletCloud endpoint, region and keys. The code does not change.
By its tier. Each bucket carries its own capacity and its own monthly figure, from 5 GB at 50 ETB a month, charged by the minute from the wallet. Reads, writes and presigned links are not counted. Buckets and access keys are unlimited.
Yes. Set a bucket to public read and its objects answer on a public URL. Keep it private and hand out presigned links that expire. The setting is per bucket and changes whenever you want.
13 ETB buys you an afternoon. Signup is a phone number and one SMS.
If it does not work the way this page says it does, call 6993 and say so.