diff --git a/.aws/task_definition.json b/.aws/task_definition.json
index 53b05eae..861c14d0 100644
--- a/.aws/task_definition.json
+++ b/.aws/task_definition.json
@@ -8,9 +8,9 @@
         "memory": "8192",
         "portMappings": [
           {
-            "name": "xuexiao-5050-tcp",
-            "containerPort": 5050,
-            "hostPort": 5050,
+            "name": "xuexiao-80-tcp",
+            "containerPort": 80,
+            "hostPort": 80,
             "protocol": "tcp",
             "appProtocol": "http"
           }
diff --git a/.aws/task_definition_preview.json b/.aws/task_definition_preview.json
index 5f4a23c0..174ddcb8 100644
--- a/.aws/task_definition_preview.json
+++ b/.aws/task_definition_preview.json
@@ -8,9 +8,9 @@
         "memory": "8192",
         "portMappings": [
           {
-            "name": "xuexiao-5050-tcp",
-            "containerPort": 5050,
-            "hostPort": 5050,
+            "name": "xuexiao-80-tcp",
+            "containerPort": 80,
+            "hostPort": 80,
             "protocol": "tcp",
             "appProtocol": "http"
           }
diff --git a/doc/init_aws.md b/doc/init_aws.md
index b1feb3e2..4b98fc5d 100644
--- a/doc/init_aws.md
+++ b/doc/init_aws.md
@@ -71,27 +71,6 @@ Docker Compose's integration for ECS and ACI will be retired in November 2023. L
 Successfully created ecs context "botmetaecscontext"
 ```
 
-The current context in use is marked by  * in the output of context listing:
 
-```bash
-$ docker context ls
-```
-
-```
-NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT                                KUBERNETES ENDPOINT   ORCHESTRATOR
-botmetaecscontext   ecs
-default             moby                Current DOCKER_HOST based configuration   unix:///var/run/docker.sock
-```
-
-To make all subsequent commands target Amazon ECS, make the newly created ECS context the one in use by running:
-
-```bash
-docker context use botmetaecscontext
-```
-
-
-Docker Compose converts the Compose file to a CloudFormation template defining a set of AWS resources. Details on the resource mapping can be found in the documentation. To review the CloudFormation template generated, we can run the command:
-
-```bash
-$ docker compose convert
-```
\ No newline at end of file
+#### REFERENCES
+https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-private-integration.html