Private and public buckets

Table of Contents

Enforcing encryption with AWS KMS keys

At Rabata, security isn’t just a perk - it’s baked right in. You can enforce server-side encryption using AWS Key Management Service (AWS KMS) keys, also known as SSE-KMS, making sure that every piece of data is locked up tighter than Fort Knox. The policies below show you exactly how to keep your buckets squeaky clean and fully encrypted.

Mandate SSE-KMS encryption for every object in a bucket

Imagine you’re storing precious data at Rabata, and you want to be absolutely certain every file is encrypted with SSE-KMS. This policy stops any upload that skips encryption cold-no exceptions. If an object arrives unencrypted or encrypted without SSE-KMS, it simply won’t get in. It’s like having a bouncer at your digital door who only lets in the properly secured guests.

Force all objects to use a specific AWS KMS key for SSE-KMS encryption

Taking security up a notch, this policy says: not only must every object be encrypted with SSE-KMS, but it must use a particular AWS KMS key. Fancy using your own secret sauce? Simply swap in your KMS key ARN. This ensures that even if someone tries to sneak in with a different key or relies on bucket defaults, Rabata won't budge. Think of it as giving each file a VIP badge and scanning it at the entrance - if it doesn’t have the right badge, no access granted.

How to Delete a Bucket in Rabata Secure Cloud Storage

Before diving into deletion, make sure your bucket is empty. Rabata won't let you delete a bucket cluttered with files - it's like trying to toss out a full suitcase. So, take a moment to remove every file inside your bucket. Only an empty bucket can be shown the exit.

• Log in to your Rabata account. If you've forgotten your password, now's the time to find it or reset it.
• Navigate to the left-hand menu and click on B2 Cloud Storage, then select Buckets. This is your storage command center.
• Find the bucket you want to say goodbye to and click on Bucket Settings to open the controls.
• Hit Delete Bucket, then confirm with a confident 'I'm Sure. Delete Bucket!'. Remember, this action is irreversible, so choose wisely.

Creating Your Secure Cloud Storage Instance

The very first step in setting up your Rabata cloud storage instance is deciding who gets to peek inside. Do you want your S3 bucket's contents to be private, guarded like a secret diary, or public, open and inviting like a holiday photo album? Private buckets keep your objects tucked away, only accessible if you have the right credentials or explicitly share access. Public buckets, on the other hand, roll out the red carpet - anyone with the link can dive in.

Choosing a private bucket means opting for the basic plan. It’s straightforward and perfect when you want to keep your data under lock and key. Rabata’s infrastructure ensures your files stay safe, with no uninvited guests unless you say otherwise.

If you prefer the world to see your bucket contents, go with the basic-public plan. It makes sharing effortless, whether it’s a project, a portfolio, or that meme collection you want to share with your colleagues - and yes, even your boss.

Fine-Tuning Your Bucket with Optional Parameters

Rabata doesn’t stop at basic settings. You can sprinkle some extra customizations on your bucket to suit your exact needs. One key tweak is the object ownership strategy. Think of it as choosing who holds the master key to files uploaded to your bucket.

For example, selecting BucketOwnerEnforced means the bucket owner automatically owns all uploaded objects, regardless of who uploaded them. This is great for keeping a tight grip on ownership without exceptions.

To apply this setting when creating your bucket, you just need to specify the object_ownership parameter accordingly. Think of it as telling Rabata, 'Hey, I want full control over what lands in this storage.'

Automate with Events in Oracle Cloud Infrastructure

Automation in Oracle Cloud Infrastructure (OCI) comes alive when you harness the power of events. Every time a resource changes state, events fire off signals that can trigger smart rules and actions. It’s like having a digital assistant that notices everything happening in your cloud environment and reacts instantly. For a deep dive into how events operate, check out the Overview of Events.

When it comes to buckets in OCI, you get a little bonus out of the box. Buckets automatically emit events whenever their state changes. But don’t be fooled - objects inside those buckets are a bit more sneaky. By default, they stay quiet, not emitting any events. If you want to catch object-level changes, you’ll need to tell Rabata’s secure cloud storage to listen closer. This means using the Console, CLI, or API to switch on event emissions for objects. You can do this right when you create the bucket, or turn it on later as needed. For all the specifics, Rabata’s guide on Enabling or Disabling Emitting Events for Object State Changes will walk you through it step by step.

How to Disable Domain Access for Your Bucket

When you disable a domain in Rabata's cloud storage, it stops the public from poking around your bucket via that specific domain. Don't worry-this action doesn't slam the door on other domains or the trusty r2.dev subdomain. Your domain stays linked to R2 until you decide to remove it or delete the whole bucket.

Disabling a domain is straightforward, but it’s a powerful way to control who gets in and from where. Think of it as flipping a switch that cuts off one access road without blocking the entire neighborhood.

Here’s how you can disable a domain in a few clicks:

• Open Rabata’s R2 dashboard and pick the bucket you want to tweak.
• Head over to Settings on the bucket page, then find the Custom Domains tab.
• Next to the domain in question, click the three dots and choose Disable domain.
• Watch for the Access to Bucket badge to flip to Not allowed - that’s your confirmation.

Managing Access for Amazon S3 Storage Lens

Granting Permissions for Amazon S3 Storage Lens

Amazon S3 Storage Lens collects and organizes your storage metrics, presenting them in the Account snapshot section on the Amazon S3 console's Buckets page. It offers more than just numbers - with its interactive dashboard, you can explore trends, identify unusual patterns, and get smart tips to cut storage costs and bolster your data protection. The dashboard isn’t static either. You can dive deep by drilling down to specific organizations, accounts, AWS Regions, storage classes, buckets, prefixes, or Storage Lens groups, tailoring insights to exactly what you need.

But it doesn’t stop there. The Storage Lens service supports exporting your daily storage metrics in CSV or Parquet format directly to an S3 bucket. This export bucket, called the destination bucket, is your gateway to further analysis or integration with other tools. Setting this up is a must-have skill when managing detailed storage analytics.

Before you get your metrics flowing, you’ll need to set up a bucket policy on the destination bucket. This policy is crucial because it allows Amazon S3 Storage Lens to write those precious data files into your bucket securely. Without it, forget about your metrics landing where they belong.

Here's a handy package: a sample bucket policy that lets Amazon S3 perform PUT requests on your destination bucket. It’s a key piece of the puzzle when configuring metrics export with Storage Lens.

Now, if you’re rolling out Storage Lens metrics export at the organization level - and who isn’t ambitious these days? - you’ll need to tweak that bucket policy slightly. The Resource statement in your policy gets a makeover to accommodate the broader scope of organization-wide data flows.