generated from FCJ-DNTU/workshop-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4 from FCJ-DNTU/update-structure
update structure, preparation for ecs
- Loading branch information
Showing
47 changed files
with
391 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,181 @@ | ||
+++ | ||
title = "Preparing for ECS" | ||
date = 2024 | ||
weight = 3 | ||
chapter = false | ||
pre = "<b>3. </b>" | ||
+++ | ||
|
||
#### Adding a Private Subnet | ||
|
||
In the VPC management interface, from the left-hand menu: | ||
|
||
- Select **Subnet** | ||
- Click **Create subnet** | ||
|
||
![3.1](/images/3-prepare-for-ecs/3.1.png) | ||
|
||
- Select the VPC **FCJ-Lab-vpc** | ||
|
||
![3.2](/images/3-prepare-for-ecs/3.2.png) | ||
|
||
Follow these settings: | ||
|
||
- Subnet name: `FCJ-Lab-subnet-private3` | ||
- Choose Availability Zone | ||
- IPv4 VPC CIDR block: `10.0.0.0/16` | ||
- IPv4 subnet CIDR block: `10.0.32.0/20` | ||
- Click **Create subnet** | ||
|
||
![3.3](/images/3-prepare-for-ecs/3.3.png) | ||
|
||
Result: | ||
|
||
![3.4](/images/3-prepare-for-ecs/3.4.png) | ||
|
||
Similarly, create another subnet: | ||
|
||
- Subnet name: `FCJ-Lab-subnet-private4` | ||
- Choose a different Availability Zone than the one chosen earlier | ||
- IPv4 VPC CIDR block: `10.0.0.0/16` | ||
- IPv4 subnet CIDR block: `10.0.64.0/20` | ||
- Click **Create subnet** | ||
|
||
![3.5](/images/3-prepare-for-ecs/3.5.png) | ||
|
||
Result: | ||
|
||
![3.6](/images/3-prepare-for-ecs/3.6.png) | ||
|
||
#### Creating a NAT Gateway | ||
|
||
First, we need to create Elastic IPs to assign to the NAT Gateway. In the VPC management interface, from the left-hand menu: | ||
|
||
- Select **Elastic IPs** | ||
- Click **Allocate Elastic IP address** | ||
|
||
![3.7](/images/3-prepare-for-ecs/3.7.png) | ||
|
||
Elastic IP address configuration: | ||
|
||
- Public IPv4 address pool: **Amazon's pool of IPv4 address** | ||
- Network border group: **ap-southeast-1** if using the same region | ||
|
||
![3.8](/images/3-prepare-for-ecs/3.8.png) | ||
|
||
For tags (optional): | ||
|
||
- Key: `Name` | ||
- Value: `FCJ-Lab-IP` | ||
- Click **Allocate** | ||
|
||
![3.9](/images/3-prepare-for-ecs/3.9.png) | ||
|
||
Next, we'll create the NAT Gateway. From the right-hand menu: | ||
|
||
- Select **NAT gateways** | ||
- Click **Create NAT gateway** | ||
|
||
![3.11](/images/3-prepare-for-ecs/3.11.png) | ||
|
||
NAT Gateway configuration: | ||
|
||
- Name: `FCJ-Lab-nat` | ||
- Subnet: Select a public subnet as instructed | ||
- Connectivity type: **Public** | ||
- Select the Elastic IP created earlier | ||
- Click **Create NAT gateway** | ||
|
||
![3.12](/images/3-prepare-for-ecs/3.12.png) | ||
|
||
Wait a moment until the state changes to **Available**. | ||
|
||
![3.14](/images/3-prepare-for-ecs/3.14.png) | ||
|
||
#### Route Table | ||
|
||
In the VPC management interface, from the left-hand menu: | ||
|
||
- Select **Route tables** | ||
- Click **Create route table** | ||
|
||
![3.15](/images/3-prepare-for-ecs/3.15.png) | ||
|
||
- Name: `FCJ-rtb-private` | ||
- VPC: **FCJ-Lab-vpc** | ||
- Click **Create route table** | ||
|
||
![3.16](/images/3-prepare-for-ecs/3.16.png) | ||
|
||
Next, we'll associate the NAT Gateway with the route table: | ||
|
||
- Select the route table created | ||
- Click **Edit routes** | ||
|
||
![3.17](/images/3-prepare-for-ecs/3.17.png) | ||
|
||
- Click **Add route** | ||
- Destination: **0.0.0.0/0** | ||
- Target: **NAT Gateway** | ||
- Select the NAT Gateway **FCJ-Lab-nat** created earlier | ||
|
||
![3.18](/images/3-prepare-for-ecs/3.18.png) | ||
|
||
Next, associate the private subnets to the route table created. In the route table details: | ||
|
||
- Select **Subnet associations** | ||
- Click **Edit subnet associations** | ||
|
||
![3.19](/images/3-prepare-for-ecs/3.19.png) | ||
|
||
- Select the two private subnets created earlier | ||
|
||
![3.20](/images/3-prepare-for-ecs/3.20.png) | ||
|
||
#### Creating Security Groups | ||
|
||
In the VPC management interface, from the left-hand menu: | ||
|
||
- Select **Security groups** | ||
- Click **Create security group** | ||
|
||
![3.22](/images/3-prepare-for-ecs/3.22.png) | ||
|
||
Security group configuration: | ||
|
||
- Name: `FCJ-Lab-sg-private` | ||
- Description: `Allow access for Internet` | ||
- Select the VPC created earlier | ||
|
||
For Inbound rules: | ||
|
||
- Select **All traffic** | ||
- Choose **FCJ-Lab-sg-public** | ||
|
||
![3.23](/images/3-prepare-for-ecs/3.23.png) | ||
|
||
For Outbound rules: | ||
|
||
- Select **All traffic** | ||
- Choose **Anywhere IPv4** | ||
|
||
![3.24](/images/3-prepare-for-ecs/3.24.png) | ||
|
||
Next, assign this security group to the **FCJ-Lab-sg-db** security group. | ||
|
||
In the Security groups management interface: | ||
|
||
- Select **FCJ-Lab-sg-db** | ||
- Click **Action** | ||
- Choose **Edit inbound rules** | ||
|
||
![3.25](/images/3-prepare-for-ecs/3.25.png) | ||
|
||
In the Inbound Rules: | ||
|
||
- Add rule | ||
- Select **MYSQL/Aurora** | ||
- Custom, select the security group **FCJ-Lab-sg-private** | ||
- Click **Save rules** | ||
|
||
![3.26](/images/3-prepare-for-ecs/3.26.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,181 @@ | ||
+++ | ||
title = "Chuẩn bị cho ECS" | ||
date = 2024 | ||
weight = 3 | ||
chapter = false | ||
pre = "<b>3. </b>" | ||
+++ | ||
|
||
#### Thêm subnet private | ||
|
||
Ở giao diện quản lý VPC, ở bảng chọn phía bên trái | ||
|
||
- Chọn **Subnet** | ||
- Nhấn vào nút **Create subnet** | ||
|
||
![3.1](/images/3-prepare-for-ecs/3.1.png) | ||
|
||
- Chọn VPC **FCJ-Lab-vpc** | ||
|
||
![3.2](/images/3-prepare-for-ecs/3.2.png) | ||
|
||
Làm theo hướng dẫn | ||
|
||
- Subnet name `FCJ-Lab-subnet-private3` | ||
- Chọn Availability Zone | ||
- IPv4 VPC CIDR block `10.0.0.0/16` | ||
- IPv4 subnet CIDR block `10.0.32.0/20` | ||
- Chọn **Create subnet** | ||
|
||
![3.3](/images/3-prepare-for-ecs/3.3.png) | ||
|
||
Kết quả | ||
|
||
![3.4](/images/3-prepare-for-ecs/3.4.png) | ||
|
||
Tương tự chúng ta tạo thêm một subnet nữa | ||
|
||
- Subnet name `FCJ-Lab-subnet-private4` | ||
- Chọn Availability Zone khác với zone của subnet chúng ta vừa tạo ở trên | ||
- IPv4 VPC CIDR block `10.0.0.0/16` | ||
- IPv4 subnet CIDR block `10.0.64.0/20` | ||
- Chọn **Create subnet** | ||
|
||
![3.5](/images/3-prepare-for-ecs/3.5.png) | ||
|
||
Kết quả | ||
|
||
![3.6](/images/3-prepare-for-ecs/3.6.png) | ||
|
||
#### Tạo NAT Gateway | ||
|
||
Trước tiên chúng ta cần tạo Elastic IPs để gán cho NAT Gateway. Ở giao diện quản lý VPC, ở mục chọn bên trái | ||
|
||
- Chọn **Elastic IPs** | ||
- Chọn **Allocate Elastic IP address** | ||
|
||
![3.7](/images/3-prepare-for-ecs/3.7.png) | ||
|
||
Cấu hình Elastic IP address | ||
|
||
- Public IPv4 address pool **Amazon's pool of IPv4 address** | ||
- Network border group **ap-southeast-1** nếu bạn sử dụng cùng region | ||
|
||
![3.8](/images/3-prepare-for-ecs/3.8.png) | ||
|
||
Ở tags optional | ||
|
||
- Key `Name` | ||
- Value `FCJ-Lab-IP` | ||
- Chọn Allocate | ||
|
||
![3.9](/images/3-prepare-for-ecs/3.9.png) | ||
|
||
Tiếp theo chúng ta sẽ tiến hành tạo NAT Gateway. Ở mục chọn bên phải | ||
|
||
- Chọn **NAT gateways** | ||
- Chọn **Create NAT gateway** | ||
|
||
![3.11](/images/3-prepare-for-ecs/3.11.png) | ||
|
||
Cấu hình cho NAT gateway | ||
|
||
- Name `FCJ-Lab-nat` | ||
- Subnet chọn public subnet như hướng dẫn | ||
- Connectivity type **Public** | ||
- Chọn Elastic IP vừa tạo ở bước trên | ||
- Chọn **Create NAT gateway** | ||
|
||
![3.12](/images/3-prepare-for-ecs/3.12.png) | ||
|
||
Sau khi tạo chúng ta sẽ đợi một chút cho tới khi state **Available** | ||
|
||
![3.14](/images/3-prepare-for-ecs/3.14.png) | ||
|
||
#### Route table | ||
|
||
Ở giao diện quản lý VPC, ở bảng chọn bên trái | ||
|
||
- Chọn **Route tables** | ||
- Chọn **Create route table** | ||
|
||
![3.15](/images/3-prepare-for-ecs/3.15.png) | ||
|
||
- Name `FCJ-rtb-private` | ||
- VPC **FCJ-Lab-vpc** | ||
- Chọn **Create route table** | ||
|
||
![3.16](/images/3-prepare-for-ecs/3.16.png) | ||
|
||
Tiếp theo chúng ta sẽ gắn NAT gateway cho route table | ||
|
||
- Chọn vào route table ta vừa tạo | ||
- Chọn **Edit routes** | ||
|
||
![3.17](/images/3-prepare-for-ecs/3.17.png) | ||
|
||
- Chọn **Add route** | ||
- Chọn Destination **0.0.0.0/0** | ||
- Target **NAT Gateway** | ||
- Chọn NAT gateway có tên **FCJ-Lab-nat** mà chúng ta vừa tạo ở bước trước | ||
|
||
![3.18](/images/3-prepare-for-ecs/3.18.png) | ||
|
||
Tiếp theo chúng ta sẽ thực hiện liên kết các private subnet tới Route table chúng ta vừa tạo. Ở trong phần thông tin của Route table chúng ta vừa tạo. | ||
|
||
- Chọn **Subnet associations** | ||
- Chọn **Edit subnet associations** | ||
|
||
![3.19](/images/3-prepare-for-ecs/3.19.png) | ||
|
||
- Chọn 2 subnet private mà chúng ta vừa tạo trước đó | ||
|
||
![3.20](/images/3-prepare-for-ecs/3.20.png) | ||
|
||
#### Tạo security groups | ||
|
||
Ở quản lý VPC, bảng chọn phía bên trái | ||
|
||
- Chọn **Security groups** | ||
- Chọn **Create security group** | ||
|
||
![3.22](/images/3-prepare-for-ecs/3.22.png) | ||
|
||
Cấu hình cho security group | ||
|
||
- Name `FCJ-Lab-sg-private` | ||
- Description `Allow access for Internet` | ||
- Chọn VPC chúng ta đã tạo | ||
|
||
Ở phần Inbound rules | ||
|
||
- Chọn **All traffic** | ||
- Chọn **FCJ-Lab-sg-public** | ||
|
||
![3.23](/images/3-prepare-for-ecs/3.23.png) | ||
|
||
Ở phần Outbound rules | ||
|
||
- Chọn **All traffic** | ||
- Chọn **Anywhere IPv4** | ||
|
||
![3.24](/images/3-prepare-for-ecs/3.24.png) | ||
|
||
Tiếp theo chúng ta sẽ gán security group chúng ta vừa tạo vào security group **FCJ-Lab-sg-db** | ||
|
||
Ở giao diện quản lý các Security groups | ||
|
||
- Chọn **FCJ-Lab-sg-db** | ||
- Chọn **Action** | ||
- Chọn **Edit inbound rules** | ||
|
||
![3.25](/images/3-prepare-for-ecs/3.25.png) | ||
|
||
Ở phần Inbound Rule | ||
|
||
- Chọn add rule | ||
- Chọn MYSQL/Aurora | ||
- Chọn Custom và chọn tới security group **FCJ-Lab-sg-private** | ||
- Chọn **Save rules** | ||
|
||
![3.26](/images/3-prepare-for-ecs/3.26.png) |
4 changes: 2 additions & 2 deletions
4
content/3-ecs-cluster/_index.md → content/4-ecs-cluster/_index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
+++ | ||
title = "Create ECS Cluster" | ||
date = 2024 | ||
weight = 3 | ||
weight = 4 | ||
chapter = false | ||
pre = "<b>3. </b>" | ||
pre = "<b>4. </b>" | ||
+++ | ||
|
||
#### Creating an Admininistrator Group |
4 changes: 2 additions & 2 deletions
4
content/3-ecs-cluster/_index.vi.md → content/4-ecs-cluster/_index.vi.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
+++ | ||
title = "Tạo ECS Cluster" | ||
date = 2024 | ||
weight = 3 | ||
weight = 4 | ||
chapter = false | ||
pre = "<b>3. </b>" | ||
pre = "<b>4. </b>" | ||
+++ | ||
|
||
#### Creating an Admininistrator Group |
4 changes: 2 additions & 2 deletions
4
content/4-ecs-task-definition/_index.md → content/5-ecs-task-definition/_index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
+++ | ||
title = "Create ECS Task Definition" | ||
date = 2024 | ||
weight = 4 | ||
weight = 5 | ||
chapter = false | ||
pre = "<b>4. </b>" | ||
pre = "<b>5. </b>" | ||
+++ | ||
|
||
#### Creating an Admininistrator Group |
Oops, something went wrong.