DEV Community: Olu

Day 20 Of Cloud Computing

Olu — Wed, 17 Jul 2024 10:03:27 +0000

Comprehensive Coverage of Amazon S3

I’ve just completed an in-depth exploration of Amazon S3, touching on a wide range of topics essential for leveraging this powerful storage service. Here's a summary of what I've covered:

Amazon S3 Security and Bucket Policy: Detailed insights into securing your data and configuring bucket policies to control access.
Creating a Static S3 Website: Step-by-step guide on hosting a static website using Amazon S3.
S3 Versioning: Explained how to enable and manage versioning to keep multiple versions of your data for backup and recovery.
S3 Replication: Covered Cross-Region Replication (CRR) and Same-Region Replication (SRR) for data redundancy and compliance.
S3 Storage Classes: Overview of various storage classes, including Standard, Intelligent-Tiering, Standard-IA, One Zone-IA, Glacier, Glacier Instant Retrieval, Glacier Flexible Retrieval, and Glacier Deep Archive, to optimize cost and performance.
S3 Encryption: Discussed different encryption options to secure data at rest, including SSE-S3, SSE-KMS, SSE-C, and client-side encryption.
IAM Access Analyzer: Explored how IAM Access Analyzer helps monitor and analyze S3 bucket policies to prevent unintentional public access.
Amazon Snow Family: Introduced Snowcone, Snowball, and Snowmobile devices for secure, large-scale data transfer and edge computing solutions.
Storage Gateways: Discussed how AWS Storage Gateway connects on-premises environments to AWS, enabling seamless integration and backup.

This comprehensive overview equips me with the knowledge to effectively manage and utilize Amazon S3 for your storage needs.

AWS Billing Scare

Olu — Sun, 07 Jul 2024 17:38:52 +0000

Just had a scare this morning when I was checking my email. Apparently, I racked up a bill on AWS last night. At first, I thought I was hacked and someone was using my account for bitcoin mining or something similarly costly. But after a call with AWS, it turns out it was my own doing.
When using both ELB (Elastic Load Balancer) and ASG (Auto Scaling Group), these services by default draw their IPv4 addresses from the VPC (Virtual Private Cloud). Unlike EC2 instances, the VPC is not free, so I was racking up charges for all the public IPv4 addresses I was using, even if they were not active.
The amount I had to pay was insignificant, only $0.02, but it was only that way because I terminated both my load balancer and my auto scaling group after I finish messing with them. This experience showed me that if you're messing with AWS, be careful about what you play with and what you leave running. You might find yourself with a bill in the hundreds, if not thousands, of dollars if you're careless enough.
Stay vigilant, folks!

Day 13 of Cloud Computing

Olu — Sun, 07 Jul 2024 01:32:24 +0000

Here’s a summary of what I did:

Created 2 EC2 Instances:These are your servers.
Launched an Application Load Balancer:This helps distribute incoming traffic evenly across your servers.
Created a Security Group:This allows only HTTP traffic to your servers.
Grouped Instances in a Target Group: This is a set of servers the load balancer will distribute traffic to.
Created an Auto Scaling Group (ASG): This adjusts the number of servers automatically based on demand.
Created a Launch Template: This template provides the ASG with the necessary instructions to create new EC2 instances.
Attached ASG to the Load Balancer: This ensures traffic is evenly distributed across the instances, and new instances are created or deleted as needed.

In essence, I set up a system where the load balancer distributes traffic and the ASG ensures the right number of servers are running based on current demand.

Day 12 of Studying AWS

Olu — Sat, 06 Jul 2024 03:30:01 +0000

I successfully created a 2 GB EBS (Elastic Block Store) volume and attached it to my EC2 instance (server). Then, I made a snapshot of the EBS and loaded a copy of that onto another instance I created.