Lecture 18 - Deployment Final

posted over 1 year ago ⋄ 3 min read

Lecture 18 - Deployment Final#

Lecture 18 - Deployment Final

Housekeeping#

LearningSuite is published; I forgot to hit publish last week but it’s open as of Monday.
Please use [email protected] to communicate with me over email; the university has asked that all email communications I do with you all are done via that email.

News#

Deploying a Lambda Container#

Here’s my basic project setup (also available here):

mkdir my-lambda
cd my-lambda
npm init -f
npm i -D esbuild typescript eslint prettier
touch src/index.ts
touch tsconfig.json

tsconfig.json

1
{
2
  "compilerOptions": {
3
    "target": "es2020",
4
    "strict": true,
5
    "preserveConstEnums": true,
6
    "noEmit": true,
7
    "sourceMap": false,
8
    "module": "commonjs",
9
    "moduleResolution": "node",
10
    "esModuleInterop": true,
11
    "skipLibCheck": true,
12
    "forceConsistentCasingInFileNames": true,
13
    "isolatedModules": true
14
  },
15
  "include": ["src/**/*"],
16
  "exclude": ["node_modules", "**/*.test.ts"]
17
}

package.json

1
{
2
  "name": "my-lambda",
3
  "version": "1.0.0",
4
  "main": "src/index.ts",
5
  "private": true,
6
  "scripts": {
7
    "build": "tsc && esbuild src/index.ts --bundle --minify --platform=node --outfile=dist/index.js"
8
  },
9
  "keywords": []
10
  // ...
11
}

src/index.ts

1
export const handler = async (event: any, context: any) => {
2
  console.log(event);
3
  console.log(context);
4
  return "Hello World!";
5
};

Dockerfile

1
FROM node:18 as builder
2
WORKDIR /app
3
COPY package*.json ./
4
RUN npm install
5
COPY . .
6
RUN npm run build
7

8
FROM amazon/aws-lambda-nodejs:18
9
COPY --from=builder /app/dist/index.js ./
10
COPY package*.json ./
11
RUN npm install --production
12
CMD [ "index.handler" ]

Now to build the container and run it locally:

docker build . -t my-lambda
docker run --rm -p 8080:8080 my-lambda

And to test it locally:

aws lambda invoke \
--region us-west-1 \
--endpoint http://localhost:8080 \
--no-sign-request \
--function-name function \
--cli-binary-format raw-in-base64-out \
--payload '{"a":"b"}' output.txt

Now to deploy it:

aws iam create-role --role-name lambda-ex --assume-role-policy-document '{
    "Version": "2012-10-17",
    "Statement": [{ "Effect": "Allow", "Principal": {"Service": "lambda.amazonaws.com"},
    "Action": "sts:AssumeRole"}]
  }'

arn:aws:iam::778144397950:role/lambda-ex

aws ecr get-login-password --region us-west-1 | docker login --username AWS --password-stdin XXXXXXXXXXXX.dkr.ecr.us-west-1.amazonaws.com/my-lambda
docker tag my-lambda:latest XXXXXXXXXXXX.dkr.ecr.us-west-1.amazonaws.com/hhenrichsen-ecr/my-lambda:latest
docker push XXXXXXXXXXXX.dkr.ecr.us-west-1.amazonaws.com/hhenrichsen-ecr/my-lambda:latest

aws lambda create-function \
--package-type Image \
--function-name lambda-docker-hello-world \
--role arn:aws:iam::XXXXXXXXXXXX:role/lambda-ex \
--code ImageUri=XXXXXXXXXXXX.dkr.ecr.us-west-1.amazonaws.com/hhenrichsen-ecr/lambda-my-lambda:latest

aws lambda \
--region us-west-1 invoke \
--function-name my-lambda \
--cli-binary-format raw-in-base64-out \
--payload '{"a":"b"}' \
output.txt

SST (Serverless STack) and a Simple Image Host#

We’ll be talking about this repo.

SST is fairly approachable, but is JS-only. It generates code to allow you to use your infrastructure in a typesafe way, and includes developer tooling. I think it’s pretty cool.

There are other tools like this, including:

Serverless Framework - mainly focused on lambda creation and deployment
Terraform - lower level, deals with creating individual resources as code
Amazon CDK

Reading#

None! Q&A Session next time. Find something interesting to share for the News section next time.