Building a Digital Sanctuary: An AWS-Inspired Journey Through Cloud Architecture and Spiritual Connections
Seenivasa Ramadurai
Posted on September 1, 2024
In the journey to realize the eternal truth, I ventured into the "AMAZON forest" (AWS). Upon signing into that region, I started exploring all the available resources. I decided to build a house and named it VPC (Virtual Private Cloud). My house had two rooms, labeled Public and Private Subnets. The address was 10.0.0.3, falling within the 10.0.0.1/16 CIDR block. To protect myself from the wilderness, I built a fence called NSG (Network Security Group). The house had two stories—downstairs was the Public Subnet, and upstairs was the Private Subnet. Our family of five, whom we called VMs (Very Good Men), connected to the outside world through a NIC (Network Interface Card). My kids, living upstairs in the Private Subnet, accessed the internet via NAT.
We meticulously planned how our rooms should be connected and how to access special spaces like the pooja room, which we called the Route Table. To monitor the surroundings, we installed security cameras powered by CloudTrail. For alerts during emergencies or natural events, we relied on CloudWatch. All our important documents—blueprints, passports, tax records—were stored in an S3 bucket. For old memories and childhood photos, we used Glacier for long-term storage.
Our relatives lived in the same city, and we stayed connected with them through VPC Peering. Sometimes our kids used P2S (Point-to-Site) connections, and at times we connected via S2S (Site-to-Site). We had helpers who accessed our house through a Bastion Host—they didn’t know our direct cell numbers but could reach us via the house phone (Bastion). Inside the house, we shared information using Service Endpoints, like a coffee table for easy access.
Our valuables, like jewelry and important documents, were stored securely in a Key Vault (KMS). When we sent messages to the outside world, we used SQS or SNS, and delivery services like USPS would consume these messages. If any messages were for us, they were delivered through SNS.
Our parents, residing in India, reached us through Route 53 **DNS. Our community used **RDS to store all homeowner information. Mailboxes were deployed as PODs in EKS, and parcels were placed in ECS for delivery. We paid our Homeowner Association, which took care of services like parks and pools—what we referred to as Lambda functions. When we moved to a new house, we used the Snowball service. Our community library, known as Redshift, was a place to study and analyze data. To keep our community secure, we built it around a WAF (Web Application Firewall) so no intruder could enter without permission.
Our city was protected by numerous IoT devices, and any incidents were sent to the Kinesis Firehouse department.
If you’re thinking of moving to our city, feel free to reach out. I can connect you with other great builders like Azure and GCP.
Thanks
Sreeni Ramadurai
Posted on September 1, 2024
Join Our Newsletter. No Spam, Only the good stuff.
Sign up to receive the latest update from our blog.
Related
November 29, 2024