Initial commit

Author: l0c0luke

.github/workflows/deploy.yml

@@ -0,0 +1,33 @@
+name: Simple Deploy
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+env:
+  AWS_DEFAULT_REGION: "us-east-1"
+  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID}}
+  AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+jobs:
+  apply:
+    name: Terraform apply
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v4
+      - name: Get account ID
+        run: |
+          echo "account_id=$(aws sts get-caller-identity --query Account --output text)" >> "$GITHUB_ENV"
+      - name: Create state bucket
+        run: |
+          if aws s3 ls s3://tf-"$account_id"; then
+            exit
+          else
+            aws s3 mb s3://tf-"$account_id" --no-cli-auto-prompt
+          fi
+      - name: Install Terraform
+        uses: hashicorp/setup-terraform@v3
+      - name: Run Terraform
+        run: |
+          terraform init -backend-config="bucket=tf-"$account_id""
+          terraform apply -auto-approve=true

.gitignore

@@ -0,0 +1,34 @@
+# Local .terraform directories
+**/.terraform/*
+
+# .tfstate files
+*.tfstate
+*.tfstate.*
+
+# Crash log files
+crash.log
+crash.*.log
+
+# Exclude all .tfvars files, which are likely to contain sensitive data, such as
+# password, private keys, and other secrets. These should not be part of version 
+# control as they are data points which are potentially sensitive and subject 
+# to change depending on the environment.
+*.tfvars
+*.tfvars.json
+
+# Ignore override files as they are usually used to override resources locally and so
+# are not checked in
+override.tf
+override.tf.json
+*_override.tf
+*_override.tf.json
+
+# Include override files you do wish to add to version control using negated pattern
+# !example_override.tf
+
+# Include tfplan files to ignore the plan output of command: terraform plan -out=tfplan
+# example: *tfplan*
+
+# Ignore CLI configuration files
+.terraformrc
+terraform.rc

README.md

@@ -1 +1,38 @@
-# js-full-stack-developer-exercise
+# In a nutshell:
+
+This JS Fullstack Developer Challenge is brought to you by your friends at [Last Call Media](https://www.lastcallmedia.com), it is designed to assess your skills and to see how you solve problems. Please don't spend more than 2 hours working on it, and if you have trouble completing it in that time, don't stress about it - just push up whatever you have. There is no right answer here, and work-in-progress code is fine, as long as you can explain what you were working on afterwards.
+
+You have full access to `us-east-1` and `us-west-2`. Credentials should have been provided separately. You can generate as many as you want but those expire after an hour. If you plug them into `credentials.sh` you'll get credentials back that don't expire.
+
+---
+
+### Your solution should:
+
+- Deploy a Next.JS app that shows a video/screen recording of you summarizing your work on this project.
+- The video should be stored in S3.
+- Be reusable. It should be possible to apply it to any AWS account and GitHub repo with the necessary credentials
+- The site should be rebuilt upon pushes to this repository
+- Consider maintainability. The less maintenance it’ll require in the future, the better
+- Be fully automated with no steps that need to be completed in the console
+- Take security into account. Security is hard and your solution doesn’t need to be perfect. It’s ok to take some shortcuts if you call out what you’d do in production to make it safer
+- Be inexpensive
+
+---
+
+### Deliverables:
+
+- A URL that can be accessed from the internet and prompts for a username and password
+  - It’s fine if the URL contains an AWS-owned domain or an IP. After authenticating, the Next.JS site should be shown.
+- Username and password that we can use to authenticate
+- Link to the forked repo containing your solution
+- A README with a brief explanation of your solution and anything else you’d like us to know
+
+**Please be prepared to talk about your solution and to help troubleshoot if we can’t make it work**
+
+---
+
+### Extras:
+
+Some basic scaffolding you may find useful is included but please feel free to use other tools if you prefer.
+
+We don't expect you to write the auth stuff. There are lots of examples on GitHub if you'd like to use one of those. [For example](https://gist.githubusercontent.com/jeroenvollenbrock/94edbbc62adc986d6d6a9a3076e66f5b/raw/259840af8dc2408f2be142588e41aebfa76c44b7/aws-cloudfront-basic-auth.js)

credentials.sh

@@ -0,0 +1,9 @@
+#!/usr/bin/env bash
+
+export AWS_ACCESS_KEY_ID=
+export AWS_SECRET_ACCESS_KEY=
+export AWS_SESSION_TOKEN=
+
+aws iam create-user --user-name iamuser1
+aws iam attach-user-policy --user-name iamuser1 --policy-arn arn:aws:iam::aws:policy/AdministratorAccess
+aws iam create-access-key --user-name iamuser1 

main.tf

@@ -0,0 +1,26 @@
+terraform {
+  backend "s3" {
+    key = "tfstate"
+  }
+}
+
+provider "aws" {}
+
+
+# Below we import the state bucket made with GHA... into our own state
+# Just a quick check that everything works
+
+data "aws_caller_identity" "current" {}
+
+locals {
+  account_id = data.aws_caller_identity.current.account_id
+}
+
+import {
+  to = aws_s3_bucket.tfstate
+  id = "tf-${local.account_id}"
+}
+
+resource "aws_s3_bucket" "tfstate" {
+  bucket = "tf-${local.account_id}"
+}

web/index.html

@@ -0,0 +1,12 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <title>Boy I wish I could make this webpage in Next.JS</title>
+  </head>
+  <body>
+    <p>
+      This is a webpage that I made in HTML. I wish I could make it in Next.JS
+      instead.
+    </p>
+  </body>
+</html>