First time on AWS?! A Beginner’s Tale of Cloud Computing

Hey there, fellow tech adventurers! Today, I will share my journey of building my first AWS application. Spoiler alert: it involves a lot of coffee, some mild cursing at documentation, and eventually, a working app!

The Grand Plan

Let’s build something simple but useful: a web application that lets users upload photos, store them securely, and view them later. Think of it as Instagram’s much, much, MUCH smaller cousin. We’ll call it “PicStash” (because all good projects need a catchy name, right?).

The AWS Services We’ll Be Using (AKA Our New Best Friends)

1. AWS S3 (Simple Storage Service)

Think of S3 as your digital garage, except it’s infinitely expandable and you don’t have to fight with your partner about storing old Christmas decorations. It’s where we’ll store our photos. The best part? You can’t accidentally leave the garage door open – AWS handles all the security heavy lifting.

Fun fact: S3 can store so much data that you could probably save every selfie you take, even though your wallet might not thank you for trying.

2. AWS Lambda

Lambda is like having a super-efficient personal assistant who only works when needed and bills you by the millisecond. It’s serverless computing at its finest. We’ll use it to process our images when they’re uploaded.

Pro tip: Lambda has a 15-minute timeout limit. If your function takes longer than that, you might want to reconsider your life choices… or at least your code.

3. API Gateway

This is your application’s bouncer. It manages who gets in and out of your API club. It’s like a really strict doorman who checks IDs and makes sure everyone follows the dress code (in this case, proper HTTP requests).

Let’s Build This Thing!

Step 1: Setting Up S3

1. Create a new S3 bucket (I named mine picstash-definitely-not-instagram)
2. Configure the bucket policy (because public access to ALL your photos might not be the best idea)
3. Enable CORS (Cross-Origin Resource Sharing) unless you enjoy debugging mysterious errors

Step 2: Creating Our Lambda Function

Here’s a simple Lambda function to handle image uploads:

import boto3
import json

def lambda_handler(event, context):
    s3_client = boto3.client('s3')
    
    try:
        # Get the uploaded file info from the event
        bucket = event['Records'][0]['s3']['bucket']['name']
        key = event['Records'][0]['s3']['object']['key']
        
        # Do something with the image
        # (Like generate a thumbnail, add a watermark, or just log it)
        
        return {
            'statusCode': 200,
            'body': json.dumps(f'Successfully processed {key}')
        }
    except Exception as e:
        print(e)
        return {
            'statusCode': 500,
            'body': json.dumps('Error processing file')
        }

Step 3: Setting Up API Gateway

1. Create a new REST API
2. Set up your resources and methods (GET for viewing, POST for uploading)
3. Connect them to your Lambda function
4. Deploy your API (and pray to the tech gods)

The Moment of Truth

After connecting all these pieces, you should have a working application where:

1. Users can upload photos through your API
2. Photos get stored in S3
3. Lambda processes them automatically
4. Users can view their masterpieces through your API

What I Learned

1. AWS has more services than a shopping mall has stores
2. The free tier is your best friend while learning
3. Always, ALWAYS set up billing alerts (unless you enjoy surprise bills)
4. The AWS documentation is like a good fantasy novel – lengthy, detailed, and sometimes requires multiple readings to understand the plot

Closing Thoughts

Building your first AWS application is like cooking a complicated recipe for the first time. You might make a mess, and you’ll probably forget something important, but in the end, you’ll have created something to be proud of (or at least something that works).

Remember, everyone starts somewhere. Even Jeff Bezos probably struggled with his first AWS deployment (okay, maybe not, but it makes me feel better to think so).

Happy coding, and may your Lambda functions be quick and your S3 buckets never overflow!

P.S. If you’re wondering why I didn’t mention IAM (Identity and Access Management), explaining IAM properly would require another blog post, three cups of coffee, and possibly a therapy session. We’ll save that for next time! 😉

Muhammad Adel

Former Nuclear Engineer | University Lecturer | Technology Advisor | Digital Transformation evangelist | FinTech | Blockchain | Podcaster | vExpert ⭐️⭐️⭐️⭐️ | VeeamVanguard ⭐️⭐️ | Nutanix SME | MBA | AWS ABW Grant’23

www.archtonic.net