Workshop

Running Laravel

on Amazon ECS

(Part 1)

Slides: https://hackmd.io/@dwchiang/workshop-laravel-ecs-pahud-part1

工作坊適合對象

• 對 Laravel 有初步認識者
• 想部署高可用性 Laravel 應用者
• 想要一個步驟一個步驟拆解細節者
• 想要嘗試 AWS Fargate 無伺服器架構者
• 想要嘗試 CDK 跟 YAML 說蟹蟹再見者
• 喜歡打破沙鍋問到底還問砂鍋在哪裡者
• 以上皆是或隨喜任選者

Please get your development environment to join us!

Workshop Repo:

https://github.com/dwchiang/laravel-on-aws-ecs-workshops/tree/master

Finish preparation on your development environment before starting the workshop:

https://github.com/dwchiang/laravel-on-aws-ecs-workshops/tree/master#preparations

(We have a checklist at the end of this HackMD page. Feel free to copy/paste and create one list for yourself.)

Who am I?

• Open source/COSCUP/MozTW
• PHP/Laravel
• AWS
• Bluetooth

In the very beginning…

• 為了喝牛奶，開了一個農場
  • 原本做了個 Docker image – nginx-php-fpm
  • 結果開了個 – 工作坊 XDD
• 初衷
  • share
  • arm64 / AWS Graviton

Items of Today

• Laravel
• Amazon ECS
• AWS CDK

Outline

1. Quick Demo: Section 1
2. Preparation checklist
3. Section 2

Let's Demo

AWS CDK

https://www.ernestchiang.com/en/notes/aws/cdk/

Hands On!!

AWS ECS

https://www.ernestchiang.com/en/notes/aws/ecs/

Wrap up

Thank you!

You can find me on

• GitHub: https://github.com/dwchiang
• Twitter: https://twitter.com/dwchiang

Checklist

Copy and paste one for yourself :)

Preparation Checklist: {yuyuyu}

COPY & PASTE ABOVE (DO NOT EDIT PLEASE) (KEEP IT AT THE BOTTOM)

• Having an IAM user with AdministratorAccess policy (or an AWS Root Account (not recommended))
• Having git.
• git clone this repository to your local machine.
• Having GNU Make.
• Having tree command.
• Having AWS CLI v2 installed and configured with profile name laravel-on-aws-ecs-workshops.
• Having jq to parse json outputs from AWS CLI.
• Having Docker on your local machine.
• Having composer on your local machine to install Laravel.
• Having Node.js and npm on your local machine. You may use nvm (Node Version Manager) to easily manage multiple versions.
• Having AWS CDK
• Having a domain name you can manage. (e.g adding a new CNAME record for it.)