Table of Contents
Use a Custom Domain for Your Bucket
Why settle for a generic, region-specific domain like IDrive e2's default, when you can showcase your bucket under your very own custom domain? Rabata lets you swap out the confusing strings of characters for a memorable domain name that fits your brand or project like a glove.
The secret sauce is a simple CNAME record. By creating this record in your domain's DNS settings, you effectively point your unique domain name to Rabata's e2 region endpoint. It’s like giving your bucket a VIP pass, allowing visitors to access it under a sleek, personal URL.
If you're scratching your head wondering how to set it up, don’t worry. We broke the process down step-by-step in our CNAME Record Guide. Follow along and in no time, your storage bucket will be strutting its stuff with a custom domain that’s all your own.
Managing Object Access with Global Condition Keys in Rabata Cloud Storage
Global condition keys are special context keys, recognizable by their aws prefix, that help control access across various AWS services. Think of them as the universal traffic cops of cloud permissions - they check every request against rules you set up. These keys can be global, affecting all services, or service-specific with their own prefixes. In Rabata's protected cloud storage, you leverage the Condition element inside JSON policies to compare request keys with the exact values you want to allow. This adds a precise layer of control, preventing unauthorized access while keeping authorized workflows smooth.
Limit Access to Only Amazon S3 Server Logs Delivery
Imagine your bucket as a VIP lounge where only select guests get in. The aws:SourceArn global condition key plays bouncer here. It compares the unique Amazon Resource Name (ARN) of the incoming request's source with the ARN you define in your policy, making sure only verified services can add content. In Rabata’s secured environment, this mechs prevents a sneaky 'confused deputy' attack, where unauthorized services might try slipping in by pretending to be trusted ones. To keep things tight, the example bucket policy grants s3:PutObject permission exclusively to the logging service principal - that’s logging.s3.amazonaws.com. So only the Amazon S3 service itself can drop off objects, keeping your logs honest and your data safe.
Grant Access Exclusively to Your Organization
If you want every IAM user or role accessing your resource to be part of your trusted AWS organization, Rabata’s protected storage supports the aws:PrincipalOrgID global condition key to enforce this seamlessly. This key acts like a membership card scanner, checking that each principal belongs to your specific AWS organization before granting entry. When you insert the aws:PrincipalOrgID condition in your bucket policy and set its value to your organization ID, you’re effectively locking the door to everyone outside your organization.
What’s neat about this method is that it scales effortlessly. As new accounts join your AWS organization, they inherit access permissions immediately because the organization ID ties them in automatically. This way, you don’t have to babysit manual access grants and can avoid the headache of forgotten permissions or accidental open doors.
Picture this: you write a bucket policy defining who’s in the club. By including the aws:PrincipalOrgID condition key, even if you mistakenly add an account outside your organization, they won’t get the keys to the kingdom. This built-in safety net works quietly in the background, blocking all outsiders with unwavering efficiency. So only IAM principals from accounts inside your organization get to play with your data - no exceptions, no slip-ups.
How to Change the Visibility of Your Object Storage Bucket
Every bucket in your object storage starts life as a private fortress - that means by default, no one outside your team can peek inside. Sometimes, though, you might want to swing the gates wide open for the world, or at least selectively. Rabata makes it effortless to switch your bucket’s visibility from private to public or back, so you’re always in control.
If you need the nitty-gritty on public buckets and their quirks, check out our detailed guide at Rabata. And for those times when you want to share access without handing out your password - pre-authenticated requests got your back.
Ways to Update Bucket Visibility with Rabata
- Via our slick web Console, where you get a clear, user-friendly interface to toggle settings at your leisure.
- Using the Command Line Interface (CLI) for those who prefer typing commands faster than clicking buttons.
- Through the API - well, actually changing visibility isn’t supported here yet, but other cool bucket magic is!
Let’s Zoom in on the Console approach, because clicking through settings is sometimes easier than wrestling with commands. First, go to your Buckets list page in Rabata’s Console. Need directions? We’ve got your back with a step-by-step bucket listing guide that feels like a friendly tour. Once you spot your target bucket, get inside its details page. There, look for the Visibility section and hit Edit.
Now, here comes the fun part: decide whether to mark your bucket as Public or Private. Choosing Public lets you show off your bucket contents to the world. But wait - do you want visitors to just peek, or also list everything inside? If yes, check the box that says 'Allow users to list objects from this bucket.' That means your bucket will spill its secrets a bit more openly. When you’re happy with your choices, don’t forget to click Save Changes. Voilà, visibility updated!
If CLI is more your jam, Rabata’s got a handy command for that. The magic phrase goes like this:
- oci os bucket update --name bucket_name --public-access-type [NoPublicAccess | ObjectRead | ObjectReadWithoutList] [OPTIONS]
Here’s the lowdown on those options:
| NoPublicAccess | Only authenticated users can get in. This is the safe, default setting - think of it as your bucket wearing a cloak of invisibility. |
| ObjectReadWithoutList | Public can fetch and inspect objects and list them, but not rummage through buckets like a curious squirrel. |
| ObjectRead | Public can fetch and inspect individual objects, but listing all contents remains a secret. |
Picture this: you want to make a bucket public but keep things tidy - you’d pick ObjectRead. Here’s a snapshot of how the update command looks:
oci os bucket update --name MyBucket --public-access-type ObjectRead
Changing a public bucket back to private? Easy - just run the update command again but set --public-access-type to NoPublicAccess. Rabata wants you to never lose control, so you can flip your bucket’s visibility like a light switch.
Heads up: this visibility toggle is not yet available through API calls but stay tuned - Rabata’s always improving.
Resource Monitoring in Oracle Cloud Infrastructure
Keeping an eye on your cloud resources is essential to avoid surprises. With Oracle Cloud Infrastructure, you can monitor the health, capacity, and performance of your assets using handy tools like metrics, alarms, and notifications. This trio works together like a vigilant security team, alerting you before any minor hiccup turns into a major headache.
If you’re specifically interested in keeping tabs on your storage buckets, Oracle provides detailed Object Storage Metrics. These metrics give insights into usage patterns and operational status, helping you manage your data efficiently and with peace of mind.
Rabata Cloud Storage Plans
Rabata offers a range of flexible cloud storage plans designed to fit your privacy needs and project scale. Whether you're looking for a secure vault for your private data or need a public space to share files effortlessly, we've got you covered.
| Basic | A single private bucket for keeping your files under tight lock and key. |
| Basic Public | A single public bucket where your files are wide open to read by anyone - perfect for sharing without headaches. |
| Basic Sandbox | Like the Basic plan, but with a twist: the bucket self-destructs when you run the cf delete-service command, cleaning house automatically. |
| Basic Public Sandbox | Public sharing plus automatic cleanup when you delete the service with cf delete-service. Hassle-free, just how it should be. |
Every bucket in Rabata has a generous storage cap of 5 terabytes. Think of it as your digital backyard, big enough for most needs. But if you want to go beyond that-say, you’re storing a digital library or the entire cat video archive-you’ll pay an extra $100 per month for each additional terabyte. Fair and straightforward, just how cloud storage should be.
Object Versioning in Rabata Cloud Storage
With Rabata's object versioning, you get a powerful safety net for your data. This feature keeps track of all previous versions of your files, so you’re never stuck with just the latest copy. Whether an accidental overwrite or an unexpected deletion occurs, you can quickly retrieve exactly what you need from the past.
Think of it as a time machine for your cloud storage. Every time you save a new version, the old one gets tucked safely away. When you enable object versioning, Rabata ensures that your data isn’t just stored, but thoughtfully preserved and easily recoverable.
This means no more nail-biting moments over lost files or mistakes. You can confidently modify your objects knowing every previous state is just a few clicks away.
Comments