Ward Your Data šļø - Creating Your Secure S3 Bucket for Rift Rewind
More Protected Than an ADC with Lulu, Karma, Janna, and Braum
Learn to create your first secure S3 bucket, upload files safely, and understand AWS pricing. Build cloud storage habits that keep your data private by default - no feeding your files to the enemy team.
Rift Rewind Developer Challenge - Day 2 š®
Welcome to Day 2 of the Riot Games Rift Rewind Developer ChallengeĀ ! š Today you'll create your first piece of cloud infrastructure - a secure Amazon S3 bucket that will store your project files. Don't worry if you've never heard of S3 before, we'll explain everything as we go (it's not a League tier, we promise).
In about 30 minutes, you'll create a private storage bucket in the cloud and upload your first file. We're not just creating storage - we're learning why security comes first in the cloud and how to keep your data private by default, like keeping your champion picks hidden until the last second.
This means creating a bucket that's locked down from the start, understanding why we never make buckets public (because nobody wants their data to int), and uploading a file that will eventually become part of your project. The goal is to build secure cloud storage habits that will serve you well throughout your AWS journey.
By the end of today, you'll have secure cloud storage ready for your project files. Time to get this W!
What You Will Accomplish Today
ā
Create a private Amazon S3 bucket with security best practices
ā Learn why S3 buckets should remain private by default
ā Upload a file to your secure bucket
ā Understand S3 security settings and access controls
ā Organize your files properly in cloud storage
ā Learn why S3 buckets should remain private by default
ā Upload a file to your secure bucket
ā Understand S3 security settings and access controls
ā Organize your files properly in cloud storage
What You Will Need:
- Your AWS account from Day 1 (signed in as your IAM admin user) š»
- A file to upload (any format: JPG, PNG, PDF, etc.) š
- About 30 minutes of your time ā°
Step 1: Understanding Amazon S3 š¤
Before we create your bucket, let's understand what S3 is and why it's essential for cloud projects.
Amazon S3 (Simple Storage Service) is like having unlimited, secure file storage in the cloud. Think of it as a super-powered version of Google Drive, but designed for applications and websites. It's basically the ultimate inventory system for your digital assets.
Key concepts:
- Bucket - A container for your files (like a folder, but at the top level)
- Object - Any file you store in a bucket (images, documents, code files, etc.)
- Private by default - New buckets block all public access for security (because nobody wants their data leaked)
Why S3 for your projects?
- Stores your files reliably with 99.999999999% (11 9's) durability
- Scales automatically as your project grows
- Integrates seamlessly with other AWS services
- Pay-as-you-go pricing based on usage
- More reliable than your internet connection during ranked promos
Step 2: Create Your Private S3 Bucket š
Let's create your secure storage bucket. Remember, we're keeping it private - this is a security best practice that's more important than warding river bush.
Navigate to S3 - In the AWS Console, search for "S3" in the top search bar and click on it
Create a new bucket - Click the orange "Create bucket" button (it's like clicking "Find Match" but for cloud storage)
Choose a unique bucket name - Enter a name like "rift-rewind-[your-name]" (example: "rift-rewind-ana")
- Bucket names must be globally unique across all AWS accounts
- Use lowercase letters, numbers, and hyphens only
- Make it memorable but unique (like a good summoner name)
Keep default security settings - Under "Block Public Access settings for this bucket", ensure all four checkboxes are checked ā
ā
Block all public access (recommended - this enables all four settings below)
ā Block public access to buckets and objects granted through new access control lists (ACLs)
ā Block public access to buckets and objects granted through any access control lists (ACLs)
ā Block public access to buckets and objects granted through new public bucket or access point policies
ā Block public access to buckets and objects granted through any public bucket or access point policies
ā Block public access to buckets and objects granted through new access control lists (ACLs)
ā Block public access to buckets and objects granted through any access control lists (ACLs)
ā Block public access to buckets and objects granted through new public bucket or access point policies
ā Block public access to buckets and objects granted through any public bucket or access point policies
Skip other settings - Leave all other settings as default for now (we're not optimizing our build path just yet)
Create the bucket - Click "Create bucket" at the bottom
You'll know you're done when: You see your new bucket listed in the S3 console with a "Private" access indicator.
Step 3: Upload Your First File š¤
Now let's add your first file to the bucket - this could be an image, document, or any file that might be part of your project.
Open your bucket - Click on your bucket name to enter it (like entering the Rift)
Upload a file - Click the "Upload" button
Add your file - Click "Add files" and select a file from your computer
- Any common file format works (JPG, PNG, PDF, TXT, etc.)
- Keep the file size reasonable (under 5MB is plenty for now)
- Choose something appropriate for a professional challenge
Review upload settings - You'll see your file listed. The default settings are perfect for now
Upload the file - Click "Upload" at the bottom
You'll know you're done when: You see a green "Upload succeeded" message and your file appears in the bucket.
Step 4: Explore Your Bucket and Understand Security š”ļø
Let's explore what you've created and understand the security features protecting your data - because security is more important than getting that pentakill.
View your uploaded file - Click on your file's name to see its details
Check the Object URL - You'll see a URL like
https://your-bucket-name.s3.region.amazonaws.com/your-file.jpgTest the security - Copy this URL and try opening it in a new browser tab
What happens? You should see an "Access Denied" error. This is exactly what we want! Your bucket is private, so even though the file exists, nobody can access it through the public internet. It's like having your match history set to private - the data exists, but random people can't see it.
Why this matters:
- Prevents accidental data exposure
- Protects sensitive information
- Follows security best practices
- Avoids the "oops, I made my bucket public" mistake that's cost companies millions
Step 5: Organize Your Bucket Structure š
Good organization makes managing your project easier. Let's create a proper folder structure - because even cloud storage needs to be more organized than your champion mastery scores.
Create a folder - In your bucket, click "Create folder"
Name it appropriately - Enter a folder name like "assets" or "files" and click "Create folder"
Move your file - Select your uploaded file (checkbox next to it), click "Actions" ā "Move", then select your new folder and click "Move"
Why organize?
- Makes finding files easier as your project grows
- Follows development best practices
- Helps with permissions and access control later
- Keeps things cleaner than your desktop
You'll know you're done when: Your file is now located at
foldername/your-file.jpg inside your bucket.Step 6: Understanding Costs and Your Credit Balance š°
Let's review how S3 pricing works and how it fits within your Free Tier credits - because nobody wants surprise bills like nobody wants surprise Teemo shrooms.
S3 pricing for small projects:
- Storage: Approximately $0.023 per GB per month (US East region)*
- Requests: About $0.0004 per 1,000 GET requests, $0.005 per 1,000 PUT requests
- Data transfer: First 100 GB per month is always free
*Pricing varies by AWS region. For detailed and current pricing information, visit the S3 pricing page and use the AWS Pricing Calculator for accurate estimates based on your specific region and usage patterns.
Your Free Tier credits: You received $100 in credits when you created your account, with the opportunity to earn up to $100 more through activities. For small projects like the one you're building, S3 costs are typically minimal and well within most users' credit balance - it's basically free RP for cloud storage.
Monitoring your usage:
- Check your credit balance in the AWS Cost and Usage dashboard
- Your budget from Day 1 will alert you to any unexpected charges
- S3 usage appears in your billing details with clear cost breakdowns
Data transfer benefits: The 100 GB of free data transfer out each month (always free, doesn't use credits) covers most small project traffic needs. That's enough bandwidth to stream your project to more people than watch your Twitch streams.
Real talk: For the Rift Rewind challenge, your S3 costs will probably be measured in pennies, not dollars. The storage for a typical project might cost less than a pack of gum per month.
Next Steps š
Congratulations! š You've successfully created secure cloud storage and uploaded your first file. Your S3 bucket is now:
- ā Secure by default (private access only)
- ā Properly organized with folders
- ā Ready for your project files
- ā Cost-monitored within your Free Tier
Your cloud storage foundation is solid. In the next step of the Rift Rewind challenge, we'll start building on this foundation!
Remember: Keep your buckets private unless you have a specific reason to make them public (spoiler alert: you probably don't). Security first, flashy features second.
GG on completing Day 2! Your AWS skills are leveling up. š
Post a comment when you've completed the challenge!
Pro tip: Always double-check that "Block all public access" setting. It's saved more AWS bills than Flash has saved lives in League.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article