Cloud Resume Challenge on AWS

Deploy your resume as a serverless AWS app with a live visitor counter — S3, CloudFront, Lambda, DynamoDB, API Gateway, GitHub Actions.

~75 Minutes

5 Topics

Hands-on Scenarios

What You'll Learn

Architecture Overview

This project deploys a static resume as a fully serverless AWS application with a live visitor counter. A browser request hits CloudFront, which serves cached HTML/CSS/JS from an S3 bucket over HTTPS. Client-side JavaScript then calls an API Gateway endpoint, which invokes a Lambda function that atomically increments a counter stored in DynamoDB. Every layer here maps directly to a production pattern: S3 for static assets, CloudFront for CDN + TLS, API Gateway as the HTTP front door, Lambda for stateless compute, and DynamoDB for low-latency key-value storage. GitHub Actions ties it together with automated test-and-deploy pipelines for both the frontend and backend. [ Browser ] | v [ CloudFront ] (HTTPS, edge caching) | v [ S3 Bucket ] (HTML / CSS / JS) | v (JS fetch call) [ API Gateway ] (GET /count) | v [ Lambda Function ] (Python, boto3) | v [ DynamoDB Table ] (visitor count) > 📌 **Remember:** Every service used here fits inside the AWS Free Tier at this traffic volume — S3, CloudFront, Lambda, DynamoDB, and API Gateway all have generous free allowances. ### What each service actually does (read this before you start) If you are new to AWS, here is what each of the five services is, in plain terms, before you touch any commands: * **S3 (Simple Storage Service)** is object storage — think of it like a folder in the cloud that can hold any file. It has a special mode called "static website hosting" that lets it serve HTML/CSS/JS files directly to a browser, like a basic web server, but with no server for you to manage or patch. * **CloudFront** is a Content Delivery Network (CDN). It copies your files to data centers around the world so people load your site from a server near them instead of one far away. It also gives you free HTTPS — S3 alone cannot do this. * **DynamoDB** is a NoSQL database — a place to store simple pieces of data (like a visitor count) without needing to design tables and relationships the way you would in MySQL or PostgreSQL. You just store a key and a value. * **Lambda** is a way to run a small piece of code (a "function") without owning or managing a server. AWS runs your Python code only when something triggers it, and you are billed only for the milliseconds it actually runs. * **API Gateway** is the "front door" that lets a browser call your Lambda function over the internet. A browser cannot call Lambda directly — API Gateway turns your function into a normal HTTPS URL the browser can `fetch()`. Together: the browser loads your resume from CloudFront/S3, then JavaScript on the page quietly asks API Gateway "how many people have visited?", API Gateway wakes up Lambda, Lambda adds 1 to the number stored in DynamoDB and hands the new number back, and your page displays it.

\n\n\n```\n\n`frontend/style.css` — basic styling so the page isn't unstyled text:\n\n```css\nbody {\n font-family: Arial, sans-serif;\n max-width: 700px;\n margin: 60px auto;\n color: #222;\n}\n.container { padding: 20px; }\nfooter { margin-top: 40px; color: #888; font-size: 0.9em; }\n```\n\n`frontend/index.js` — this is the only \"logic\" in the whole frontend. Read it line by line:\n\n```javascript\nasync function updateVisitorCount() {\n try {\n // This placeholder gets replaced with your real API Gateway\n // URL in Milestone 6, once that URL actually exists.\n const API_URL = 'YOUR_API_GATEWAY_URL_HERE';\n\n // fetch() asks the browser to make an HTTP GET request.\n // \"await\" pauses this function until the response arrives.\n const res = await fetch(API_URL);\n\n // The Lambda function returns JSON like {\"count\": 42}.\n // .json() parses that response body into a JS object.\n const data = await res.json();\n\n // Find the in the HTML and\n // replace its text (\"Loading...\") with the real number.\n document.getElementById('visitor-count')\n .textContent = data.count;\n } catch (err) {\n // If the API isn't ready yet, or the network fails,\n // show something readable instead of a broken page.\n document.getElementById('visitor-count')\n .textContent = 'unavailable';\n }\n}\n\n// Run the function immediately once the script loads.\nupdateVisitorCount();\n```\n\n> 💡 **Tip:** Keep the frontend framework-free for this project. Vanilla HTML/CSS/JS keeps focus on the AWS plumbing rather than build tooling — you can always rebuild it in React later once the AWS side works.\n\nSanity-check the page locally before touching AWS — open `frontend/index.html` directly in your browser. The layout should look right and the counter will show \"unavailable\" (expected — there's no API yet). If the page itself is broken, fix that before moving to AWS.\n\n### Milestone 2: Create the S3 Bucket and Enable Static Hosting\n\nS3 bucket names must be **globally unique** — across every AWS account in the world, not just yours. `your-unique-resume-bucket-2026` will already be taken; replace it with something like `yourname-resume-2026` everywhere it appears in this guide (all three commands below, plus every later milestone that references it).\n\n```bash\n# \"mb\" = make bucket. --region pins it to Mumbai (ap-south-1);\n# pick whatever region is closest to you or your target audience.\naws s3 mb s3://your-unique-resume-bucket-2026 \\\n --region ap-south-1\n\n# \"sync\" uploads every file in frontend/ to the bucket.\n# Run this again any time you change index.html, style.css, or index.js.\naws s3 sync frontend/ \\\n s3://your-unique-resume-bucket-2026/\n\n# Turns on \"static website hosting\" mode on the bucket.\n# --index-document is served for the root URL (\"/\").\n# --error-document is served for 404s — using index.html here\n# means any bad path still shows your resume instead of an error page.\naws s3 website \\\n s3://your-unique-resume-bucket-2026/ \\\n --index-document index.html \\\n --error-document index.html\n```\n\nBy default, S3 buckets are private — nobody outside your AWS account can read the files. A **bucket policy** is a JSON document that grants specific permissions to specific people. Here, `\"Principal\": \"*\"` means \"anyone on the internet\", and `\"Action\": \"s3:GetObject\"` means \"can download files\" (not upload, not delete):\n\n```bash\ncat > bucket-policy.json << 'EOF'\n{\n \"Version\": \"2012-10-17\",\n \"Statement\": [{\n \"Effect\": \"Allow\",\n \"Principal\": \"*\",\n \"Action\": \"s3:GetObject\",\n \"Resource\": \"arn:aws:s3:::your-unique-resume-bucket-2026/*\"\n }]\n}\nEOF\n\n# Attach that policy to the bucket. Without this step, visitors\n# get \"Access Denied\" even though the files exist.\naws s3api put-bucket-policy \\\n --bucket your-unique-resume-bucket-2026 \\\n --policy file://bucket-policy.json\n```\n\n> 📌 **Remember:** If `put-bucket-policy` fails with an error mentioning \"Block Public Access\", your account has a default safety setting that blocks public buckets. Turn it off for just this bucket in the S3 Console under the bucket's Permissions tab → \"Block public access\" → Edit → uncheck all four boxes → Save. This is safe here because you're only granting read access to static files, never write or delete.\n\nCheck that it worked — visit the S3 website endpoint shown by this command in your browser:\n\n```bash\necho \"http://your-unique-resume-bucket-2026.s3-website.ap-south-1.amazonaws.com\"\n```\n\nYou should see your resume, over plain HTTP (no padlock yet — that comes in Milestone 3).\n\n### Milestone 3: Add CloudFront in Front of S3\n\nA **distribution** is CloudFront's name for \"a CDN configuration pointed at your content.\" Creating one tells AWS: copy whatever is at this S3 website endpoint out to edge locations worldwide, and give me a public HTTPS domain for it.\n\n```bash\n# --origin-domain-name points CloudFront at your S3 website endpoint\n# from Milestone 2 (not the bucket name — the s3-website URL).\n# --default-root-object means visiting the bare domain serves index.html.\naws cloudfront create-distribution \\\n --origin-domain-name your-unique-resume-bucket-2026.s3-website.ap-south-1.amazonaws.com \\\n --default-root-object index.html \\\n --query 'Distribution.DomainName' \\\n --output text\n```\n\nThis prints something like `d1abc2def3ghij.cloudfront.net` — save it, you'll need it repeatedly.\n\nCloudFront takes **5–15 minutes** to finish deploying to every edge location worldwide the first time. Check on it with:\n\n```bash\naws cloudfront list-distributions \\\n --query 'DistributionList.Items[0].Status' \\\n --output text\n```\n\nThis returns `InProgress` while it's still rolling out, then `Deployed` when it's ready. Only once it shows `Deployed` should you visit `https://d1abc2def3ghij.cloudfront.net` in your browser — you should see your resume, this time with a padlock icon (HTTPS).\n\n> 🔴 **Common Mistake:** Forgetting that S3 website endpoints only serve plain HTTP. CloudFront is what adds the free TLS certificate — skipping it means no HTTPS padlock, and browsers increasingly warn users away from plain-HTTP sites.\n\n> 💡 **Tip:** If the page loads but looks broken (missing CSS, broken images), you likely pointed CloudFront at the wrong origin — double check it's the `*.s3-website.*.amazonaws.com` endpoint from Milestone 2, not the plain S3 bucket domain (`*.s3.amazonaws.com`), which is a different, non-website mode.\n\n### Milestone 4: Create the DynamoDB Table\n\nUnlike a SQL table with fixed columns, a DynamoDB table only needs you to define its **primary key** upfront — every other attribute is added freely per item. Here the primary key is `id` (a string), and the whole table will hold exactly one item, since you only need one counter.\n\n```bash\n# --attribute-definitions declares \"id\" exists and is type S (String).\n# --key-schema says \"id\" is the HASH key — DynamoDB's term for\n# the primary key used to look items up.\n# --billing-mode PAY_PER_REQUEST means you pay only per read/write,\n# not for idle provisioned capacity — the right choice at this scale.\naws dynamodb create-table \\\n --table-name cloud-resume-visitors \\\n --attribute-definitions AttributeName=id,AttributeType=S \\\n --key-schema AttributeName=id,KeyType=HASH \\\n --billing-mode PAY_PER_REQUEST \\\n --region ap-south-1\n\n# Insert the starting item. \"S\" = String type, \"N\" = Number type\n# (DynamoDB is explicit about types in its JSON format).\n# This creates one row: { id: \"visitors\", count: 0 }.\naws dynamodb put-item \\\n --table-name cloud-resume-visitors \\\n --item '{\"id\":{\"S\":\"visitors\"},\"count\":{\"N\":\"0\"}}'\n```\n\nConfirm the item exists before moving on:\n\n```bash\naws dynamodb get-item \\\n --table-name cloud-resume-visitors \\\n --key '{\"id\":{\"S\":\"visitors\"}}'\n```\n\nYou should see the item printed back with `count: \"0\"`.\n\n### Milestone 5: Write and Deploy the Lambda Function\n\n`backend/lambda_function.py`:\n\n```python\nimport json\nimport boto3\n\ndef lambda_handler(event, context):\n dynamodb = boto3.resource(\n 'dynamodb', region_name='ap-south-1'\n )\n table = dynamodb.Table('cloud-resume-visitors')\n\n response = table.update_item(\n Key={'id': 'visitors'},\n UpdateExpression='ADD #c :inc',\n ExpressionAttributeNames={'#c': 'count'},\n ExpressionAttributeValues={':inc': 1},\n ReturnValues='UPDATED_NEW'\n )\n new_count = int(response['Attributes']['count'])\n\n return {\n 'statusCode': 200,\n 'headers': {\n 'Access-Control-Allow-Origin': '*',\n 'Content-Type': 'application/json'\n },\n 'body': json.dumps({'count': new_count})\n }\n```\n\n> ⚠️ **Security:** Use `dynamodb:UpdateItem` scoped to only this table in production instead of `AmazonDynamoDBFullAccess`. Full access is used here only to simplify the learning setup.\n\nPackage and deploy:\n\n```bash\ncd backend\nzip function.zip lambda_function.py\n\naws lambda create-function \\\n --function-name cloud-resume-counter \\\n --runtime python3.12 \\\n --role arn:aws:iam::ACCOUNT_ID:role/cloud-resume-lambda-role \\\n --handler lambda_function.lambda_handler \\\n --zip-file fileb://function.zip \\\n --region ap-south-1\n```\n\n### Milestone 6: Expose Lambda via API Gateway\n\n```bash\nAPI_ID=$(aws apigateway create-rest-api \\\n --name cloud-resume-api \\\n --query 'id' --output text)\n\nROOT_ID=$(aws apigateway get-resources \\\n --rest-api-id $API_ID \\\n --query 'items[0].id' --output text)\n\nRESOURCE_ID=$(aws apigateway create-resource \\\n --rest-api-id $API_ID \\\n --parent-id $ROOT_ID \\\n --path-part count \\\n --query 'id' --output text)\n\naws apigateway put-method \\\n --rest-api-id $API_ID \\\n --resource-id $RESOURCE_ID \\\n --http-method GET \\\n --authorization-type NONE\n\naws apigateway create-deployment \\\n --rest-api-id $API_ID \\\n --stage-name prod\n```\n\nUpdate `index.js` with the real API URL, then re-sync to S3 and invalidate the CloudFront cache:\n\n```bash\naws s3 sync frontend/ s3://your-unique-resume-bucket-2026/\naws cloudfront create-invalidation \\\n --distribution-id YOUR_DIST_ID \\\n --paths \"/*\"\n```\n\n### Milestone 7: Automate with GitHub Actions\n\n`.github/workflows/deploy.yml` (backend repo):\n\n```yaml\nname: Deploy Backend\non:\n push:\n branches: [main]\njobs:\n test-and-deploy:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - uses: actions/setup-python@v5\n with:\n python-version: '3.12'\n - run: pip install pytest boto3\n - run: pytest test_lambda.py -v\n - uses: aws-actions/configure-aws-credentials@v4\n with:\n aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}\n aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}\n aws-region: ap-south-1\n - run: zip function.zip lambda_function.py\n - run: |\n aws lambda update-function-code \\\n --function-name cloud-resume-counter \\\n --zip-file fileb://function.zip\n```\n\n> ⚠️ **Security:** Never commit AWS credentials to code. Store them only as GitHub Secrets — public repos are scanned continuously by bots looking for leaked keys.","url":"https://devopsnetwork.in/modules/project-cloud-resume-challenge-aws"},{"@type":"ListItem","position":5,"name":"Validation & Testing","description":"```bash\n# 1. Confirm the resume loads over HTTPS\ncurl -I https://YOUR_DIST_ID.cloudfront.net\n## Expected: HTTP/2 200\n\n# 2. Confirm the counter API responds\ncurl https://$API_ID.execute-api.ap-south-1.amazonaws.com/prod/count\n## Expected: {\"count\": N}\n\n# 3. Confirm DynamoDB is incrementing\naws dynamodb get-item \\\n --table-name cloud-resume-visitors \\\n --key '{\"id\":{\"S\":\"visitors\"}}'\n## Expected: count increases on each API call\n```\n\n> 🔴 **Common Mistake:** Forgetting `Access-Control-Allow-Origin` in the Lambda response body. Without it, the browser silently blocks the fetch even though the API itself works — always test with `curl` first to isolate frontend vs. backend issues.","url":"https://devopsnetwork.in/modules/project-cloud-resume-challenge-aws"}]}

Step-by-Step Implementation Milestones

### Milestone 1: Write and Package the Frontend Create the project structure. `frontend/` will hold the files your browser downloads; `backend/` will hold the Lambda code — keeping them separate mirrors how real projects are organized: ```bash mkdir cloud-resume && cd cloud-resume mkdir frontend backend ``` `frontend/index.html`. This is a plain HTML page — no framework, no build step. The `<span id="visitor-count">` is the one part JavaScript will update after the page loads: ```html <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>Cloud Resume</title> <link rel="stylesheet" href="style.css"> </head> <body> <div class="container"> <h1>Your Name</h1> <p>Cloud Engineer | AWS | Terraform</p> <footer>Visitors: <span id="visitor-count">Loading...</span></footer> </div> <script src="index.js"></script> </body> </html> ``` `frontend/style.css` — basic styling so the page isn't unstyled text: ```css body { font-family: Arial, sans-serif; max-width: 700px; margin: 60px auto; color: #222; } .container { padding: 20px; } footer { margin-top: 40px; color: #888; font-size: 0.9em; } ``` `frontend/index.js` — this is the only "logic" in the whole frontend. Read it line by line: ```javascript async function updateVisitorCount() { try { // This placeholder gets replaced with your real API Gateway // URL in Milestone 6, once that URL actually exists. const API_URL = 'YOUR_API_GATEWAY_URL_HERE'; // fetch() asks the browser to make an HTTP GET request. // "await" pauses this function until the response arrives. const res = await fetch(API_URL); // The Lambda function returns JSON like {"count": 42}. // .json() parses that response body into a JS object. const data = await res.json(); // Find the <span id="visitor-count"> in the HTML and // replace its text ("Loading...") with the real number. document.getElementById('visitor-count') .textContent = data.count; } catch (err) { // If the API isn't ready yet, or the network fails, // show something readable instead of a broken page. document.getElementById('visitor-count') .textContent = 'unavailable'; } } // Run the function immediately once the script loads. updateVisitorCount(); ``` > 💡 **Tip:** Keep the frontend framework-free for this project. Vanilla HTML/CSS/JS keeps focus on the AWS plumbing rather than build tooling — you can always rebuild it in React later once the AWS side works. Sanity-check the page locally before touching AWS — open `frontend/index.html` directly in your browser. The layout should look right and the counter will show "unavailable" (expected — there's no API yet). If the page itself is broken, fix that before moving to AWS. ### Milestone 2: Create the S3 Bucket and Enable Static Hosting S3 bucket names must be **globally unique** — across every AWS account in the world, not just yours. `your-unique-resume-bucket-2026` will already be taken; replace it with something like `yourname-resume-2026` everywhere it appears in this guide (all three commands below, plus every later milestone that references it). ```bash # "mb" = make bucket. --region pins it to Mumbai (ap-south-1); # pick whatever region is closest to you or your target audience. aws s3 mb s3://your-unique-resume-bucket-2026 \ --region ap-south-1 # "sync" uploads every file in frontend/ to the bucket. # Run this again any time you change index.html, style.css, or index.js. aws s3 sync frontend/ \ s3://your-unique-resume-bucket-2026/ # Turns on "static website hosting" mode on the bucket. # --index-document is served for the root URL ("/"). # --error-document is served for 404s — using index.html here # means any bad path still shows your resume instead of an error page. aws s3 website \ s3://your-unique-resume-bucket-2026/ \ --index-document index.html \ --error-document index.html ``` By default, S3 buckets are private — nobody outside your AWS account can read the files. A **bucket policy** is a JSON document that grants specific permissions to specific people. Here, `"Principal": "*"` means "anyone on the internet", and `"Action": "s3:GetObject"` means "can download files" (not upload, not delete): ```bash cat > bucket-policy.json << 'EOF' { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": "*", "Action": "s3:GetObject", "Resource": "arn:aws:s3:::your-unique-resume-bucket-2026/*" }] } EOF # Attach that policy to the bucket. Without this step, visitors # get "Access Denied" even though the files exist. aws s3api put-bucket-policy \ --bucket your-unique-resume-bucket-2026 \ --policy file://bucket-policy.json ``` > 📌 **Remember:** If `put-bucket-policy` fails with an error mentioning "Block Public Access", your account has a default safety setting that blocks public buckets. Turn it off for just this bucket in the S3 Console under the bucket's Permissions tab → "Block public access" → Edit → uncheck all four boxes → Save. This is safe here because you're only granting read access to static files, never write or delete. Check that it worked — visit the S3 website endpoint shown by this command in your browser: ```bash echo "http://your-unique-resume-bucket-2026.s3-website.ap-south-1.amazonaws.com" ``` You should see your resume, over plain HTTP (no padlock yet — that comes in Milestone 3). ### Milestone 3: Add CloudFront in Front of S3 A **distribution** is CloudFront's name for "a CDN configuration pointed at your content." Creating one tells AWS: copy whatever is at this S3 website endpoint out to edge locations worldwide, and give me a public HTTPS domain for it. ```bash # --origin-domain-name points CloudFront at your S3 website endpoint # from Milestone 2 (not the bucket name — the s3-website URL). # --default-root-object means visiting the bare domain serves index.html. aws cloudfront create-distribution \ --origin-domain-name your-unique-resume-bucket-2026.s3-website.ap-south-1.amazonaws.com \ --default-root-object index.html \ --query 'Distribution.DomainName' \ --output text ``` This prints something like `d1abc2def3ghij.cloudfront.net` — save it, you'll need it repeatedly. CloudFront takes **5–15 minutes** to finish deploying to every edge location worldwide the first time. Check on it with: ```bash aws cloudfront list-distributions \ --query 'DistributionList.Items[0].Status' \ --output text ``` This returns `InProgress` while it's still rolling out, then `Deployed` when it's ready. Only once it shows `Deployed` should you visit `https://d1abc2def3ghij.cloudfront.net` in your browser — you should see your resume, this time with a padlock icon (HTTPS). > 🔴 **Common Mistake:** Forgetting that S3 website endpoints only serve plain HTTP. CloudFront is what adds the free TLS certificate — skipping it means no HTTPS padlock, and browsers increasingly warn users away from plain-HTTP sites. > 💡 **Tip:** If the page loads but looks broken (missing CSS, broken images), you likely pointed CloudFront at the wrong origin — double check it's the `*.s3-website.*.amazonaws.com` endpoint from Milestone 2, not the plain S3 bucket domain (`*.s3.amazonaws.com`), which is a different, non-website mode. ### Milestone 4: Create the DynamoDB Table Unlike a SQL table with fixed columns, a DynamoDB table only needs you to define its **primary key** upfront — every other attribute is added freely per item. Here the primary key is `id` (a string), and the whole table will hold exactly one item, since you only need one counter. ```bash # --attribute-definitions declares "id" exists and is type S (String). # --key-schema says "id" is the HASH key — DynamoDB's term for # the primary key used to look items up. # --billing-mode PAY_PER_REQUEST means you pay only per read/write, # not for idle provisioned capacity — the right choice at this scale. aws dynamodb create-table \ --table-name cloud-resume-visitors \ --attribute-definitions AttributeName=id,AttributeType=S \ --key-schema AttributeName=id,KeyType=HASH \ --billing-mode PAY_PER_REQUEST \ --region ap-south-1 # Insert the starting item. "S" = String type, "N" = Number type # (DynamoDB is explicit about types in its JSON format). # This creates one row: { id: "visitors", count: 0 }. aws dynamodb put-item \ --table-name cloud-resume-visitors \ --item '{"id":{"S":"visitors"},"count":{"N":"0"}}' ``` Confirm the item exists before moving on: ```bash aws dynamodb get-item \ --table-name cloud-resume-visitors \ --key '{"id":{"S":"visitors"}}' ``` You should see the item printed back with `count: "0"`. ### Milestone 5: Write and Deploy the Lambda Function `backend/lambda_function.py`: ```python import json import boto3 def lambda_handler(event, context): dynamodb = boto3.resource( 'dynamodb', region_name='ap-south-1' ) table = dynamodb.Table('cloud-resume-visitors') response = table.update_item( Key={'id': 'visitors'}, UpdateExpression='ADD #c :inc', ExpressionAttributeNames={'#c': 'count'}, ExpressionAttributeValues={':inc': 1}, ReturnValues='UPDATED_NEW' ) new_count = int(response['Attributes']['count']) return { 'statusCode': 200, 'headers': { 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json' }, 'body': json.dumps({'count': new_count}) } ``` > ⚠️ **Security:** Use `dynamodb:UpdateItem` scoped to only this table in production instead of `AmazonDynamoDBFullAccess`. Full access is used here only to simplify the learning setup. Package and deploy: ```bash cd backend zip function.zip lambda_function.py aws lambda create-function \ --function-name cloud-resume-counter \ --runtime python3.12 \ --role arn:aws:iam::ACCOUNT_ID:role/cloud-resume-lambda-role \ --handler lambda_function.lambda_handler \ --zip-file fileb://function.zip \ --region ap-south-1 ``` ### Milestone 6: Expose Lambda via API Gateway ```bash API_ID=$(aws apigateway create-rest-api \ --name cloud-resume-api \ --query 'id' --output text) ROOT_ID=$(aws apigateway get-resources \ --rest-api-id $API_ID \ --query 'items[0].id' --output text) RESOURCE_ID=$(aws apigateway create-resource \ --rest-api-id $API_ID \ --parent-id $ROOT_ID \ --path-part count \ --query 'id' --output text) aws apigateway put-method \ --rest-api-id $API_ID \ --resource-id $RESOURCE_ID \ --http-method GET \ --authorization-type NONE aws apigateway create-deployment \ --rest-api-id $API_ID \ --stage-name prod ``` Update `index.js` with the real API URL, then re-sync to S3 and invalidate the CloudFront cache: ```bash aws s3 sync frontend/ s3://your-unique-resume-bucket-2026/ aws cloudfront create-invalidation \ --distribution-id YOUR_DIST_ID \ --paths "/*" ``` ### Milestone 7: Automate with GitHub Actions `.github/workflows/deploy.yml` (backend repo): ```yaml name: Deploy Backend on: push: branches: [main] jobs: test-and-deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-python@v5 with: python-version: '3.12' - run: pip install pytest boto3 - run: pytest test_lambda.py -v - uses: aws-actions/configure-aws-credentials@v4 with: aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} aws-region: ap-south-1 - run: zip function.zip lambda_function.py - run: | aws lambda update-function-code \ --function-name cloud-resume-counter \ --zip-file fileb://function.zip ``` > ⚠️ **Security:** Never commit AWS credentials to code. Store them only as GitHub Secrets — public repos are scanned continuously by bots looking for leaked keys.

Cloud Resume Challenge on AWS

What You'll Learn

Architecture Overview

Problem Solved

Before You Start

Step-by-Step Implementation Milestones

Validation & Testing

Skills You'll Master

Curriculum Index

Architecture Overview

Problem Solved

Before You Start

Step-by-Step Implementation Milestones

Validation & Testing

Career Impact

Troubleshooting & Lab Guides

How to Troubleshoot a Linux Production Server: A Systematic Approach

Next Modules

Foundations

Version Control (Git) for devops

Build & Package Management

Related Guides

What Is AI SRE? How AI Agents Are Changing Incident Response

GitOps Showdown: ArgoCD vs FluxCD for Kubernetes Teams

Platform Engineering 101: Building an Internal Developer Platform with Backstage