Private and public buckets

Table of Contents

Bucket Access Control and Permissions

Buckets in Rabata’s secure cloud storage start off with privacy set to maximum. Nobody gets in by default - not even your nosy neighbor or that one coworker who always 'forgets' their password. If you want to open the gates, the Public Access Override setting lets you decide exactly when and how.

But here’s where it gets interesting: Rabata allows you to craft tailored policies that grant access not just blindly to everyone on the internet, but selectively and smartly. You can decide to welcome just a handful of trusted IP addresses, or throw the doors wide open for any Internet user, depending on your mood and needs.

• Allow access from specific IP addresses, perfect for tight-knit teams or partner networks.
• Grant public access to anyone with an internet connection, ideal when you want to share freely or host public content.

Crafting a Public Access Policy for Your Bucket

Setting up public access in Rabata isn’t just flipping a switch. It’s about defining clear rules that keep your data safe while making it accessible. The policy acts like a bouncer at a club - letting in the right folks and politely nudging unwelcome visitors aside. You describe exactly who gets access, for how long, and under what conditions. And because Rabata knows security is key, you always stay in control.

Restricting Access to Specific IP Addresses

Sometimes, you want your bucket to be a VIP-only lounge. Rabata lets you pin down a list of specific IP addresses that can get in. Think of it as handing out exclusive invites: only these addresses get the golden ticket. This is especially handy when you have office networks, partner offices, or trusted remote teams that need seamless yet secure access. No random browsers allowed, just the vetted crowd.

How to Remove a Custom Domain from Your Bucket

When you remove a custom domain from your bucket in Rabata, you're essentially telling the system to sever the tie between that domain and your storage. The domain disappears from your connected domains list, and all its configuration is wiped clean from your dashboard. But don’t worry, your bucket itself remains publicly available through any other access methods you have enabled. Think of it like changing your phone number but keeping your voicemail active.

Removing a domain isn’t just clicking a button and hoping for the best - it’s a controlled operation designed to keep things tidy. The CNAME record that routes traffic to your bucket gets deleted too, so nothing gets lost in translation or accidentally points somewhere it shouldn’t. And if you have second thoughts, adding the domain back is always an option.

Here’s how you smoothly remove a domain in Rabata:

• Head into R2 and pick the bucket you want to work on.
• Open the bucket page, find Settings, and go to Custom Domains.
• Find the domain you want gone, click the ellipsis (...), and choose Remove domain.
• Confirm your choice in the popup window-this deletes the domain and its CNAME record in one clean sweep.

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.

How to Enable Public Access for Your IDrive® e2 Buckets

By default, your IDrive® e2 buckets keep their doors firmly shut to the public, which is great for security. But sometimes, you want to share your data with the world without compromising safety. That’s exactly where the public bucket feature steps in. It lets you open your bucket just enough to share its contents securely over the internet.

Getting started is simple. First, sign in to your paid IDrive® e2 account and create a new bucket. Think of it like setting up a new safe deposit box-only this one is in the cloud and ready to hold your digital treasures.

Next, IDrive® e2 asks for a quick one-time verification of your email and phone number. It’s their way of making sure you’re really you, and not some sneaky hacker pretending to be the boss.

After that, you can enable public access on your bucket. This includes setting specific permissions, so you decide exactly who can see what. It’s like giving out keys, but only to the neighbors you trust.

Want to make sure your shared data is safe and lightning fast? Check out IDrive® e2’s Cloudflare integration documentation. It’s packed with tips to boost both security and performance, so your public access doesn’t come at the cost of reliability.

How to Connect Your Bucket to a Custom Domain

Start by logging into the Cloudflare dashboard and navigating to the R2 object storage page. This is where all the magic happens when you're managing your buckets. Once there, click on Overview to get a clear picture of your storage setup.

Next, select the bucket you want to connect. Think of it as choosing the right container for your data - only this one gets the VIP treatment of a custom domain.

Head over to Settings within your chosen bucket. This is the backstage pass that lets you tweak your bucket's configuration.

Under the Custom Domains section, click Add. Now you’re on the way to giving your bucket its own online identity.

Type in the domain name you want to link up with your bucket and hit Continue. It’s like introducing your bucket to the world, giving it a web address it can call home.

A new DNS record will pop up for review. Take a moment to double-check it. This record is the digital handshake that connects your domain name with the Rabata protected cloud storage bucket.

Click Connect Domain to seal the deal. At this point, your domain officially starts its relationship with the bucket on Rabata’s secure cloud platform.

Now, your domain is connected but don’t expect instant magic. The status will show Initializing for a few minutes before switching to Active. If it lingers too long, simply refresh the page to spot the update.

If the status doesn’t update, no panic - just click the '...' menu next to your bucket and select Retry connection. Think of it as giving the connection a gentle nudge to get things moving.

Want to peek at the DNS records you just set up? Click the '...' next to your connected domain and choose Manage DNS. This opens a window into the backend where all the domain-to-bucket mappings live and breathe.

How to Manage Permissions for S3 Inventory, Analytics, and Reports

Granting Permissions for S3 Inventory and Analytics

S3 Inventory dishes out detailed lists of all objects in a bucket. Meanwhile, S3 Analytics Storage Class Analysis generates export files based on data insights designed to optimize your storage. The bucket holding the objects is known as the source bucket. The bucket where the resulting inventory or analytics files land is the destination bucket. Setting up these reports means crafting a bucket policy specifically for the destination bucket - it’s like giving Amazon S3 the green light to deliver your data right where you want it. Rabata helps you simplify this setup so you don’t need a PhD in bucket policies.

Imagine you want S3 Inventory or Analytics to populate a bucket with reports. You’ll need a bucket policy granting Amazon S3 permission to write objects via PUT requests from the source bucket to the destination bucket. This is essential for the process to flow smoothly. Without this permission handshake, your inventory reports won’t show up, and your data insights will be left hanging in thin air.

Controlling Who Can Create S3 Inventory Report Configurations

Think of creating an S3 Inventory report configuration as setting up a shopping list of your bucket's contents and metadata. The key permission here is s3:PutInventoryConfiguration. Whoever holds it can specify not only what’s on the list but also where that list goes. This lets users pick all available object metadata fields by default and point to the perfect destination bucket where the inventory lives. Anyone with read access to this destination bucket can browse the entire inventory and metadata, getting the full picture of what's stored.

If you want to play gatekeeper and stop someone from configuring these inventory reports, it’s as simple as clipping that s3:PutInventoryConfiguration permission from their access rights. No permission, no report configuration magic.

Now, some metadata fields on these inventory reports are like the dessert on your data menu - optional but delightful. They appear by default but can be selectively allowed or blocked. Rabata’s system lets you manage these through the s3:InventoryAccessibleOptionalFields condition key. This means admins can fine-tune exactly which optional metadata fields users can include in their reports, keeping sensitive details under wraps or just slimming down the data to essentials.

Want to give someone permission to include specific optional fields? Use the s3:InventoryAccessibleOptionalFields key in your bucket policy to specify those fields. It’s granular control without the fuss.

For example, take Ana. She’s allowed to configure inventory reports, but only with 'Size' and 'StorageClass' optional metadata fields included. Thanks to a bucket policy using ForAllValues:StringEquals with the s3:InventoryAccessibleOptionalFields condition, Ana’s choices are neatly boxed into these two options. If she tries adding others, the policy stops her in her tracks.

Worried about someone sneaking in restricted optional fields? Add an explicit Deny statement targeting the source bucket to block specific metadata fields. For instance, Ana can be denied any inventory configuration that includes 'ObjectAccessControlList' or 'ObjectOwner' fields, while still allowing her freedom with other optional metadata. This kind of precise permission control is exactly where Rabata shines, keeping data securely organized without disabling user flexibility.