diff --git a/doc/howto/usage/k8s/k8s_aws_en.md b/doc/howto/usage/k8s/k8s_aws_en.md
index ce5ccbca5ee33b334872d9bdde42ac2ede5d041c..eda2b639e2f5d90d26942652d0457c4e3433bf6d 100644
--- a/doc/howto/usage/k8s/k8s_aws_en.md
+++ b/doc/howto/usage/k8s/k8s_aws_en.md
@@ -383,13 +383,15 @@ Edit `/etc/hosts` to associate above ip with the DNS name.
  - Create hosted zone with following config
    - Domain name: "paddle"
    - Type: "Private hosted zone for amazon VPC"
-   - VPC ID: <Your VPC ID>
+   - VPC ID: `<Your VPC ID>`
+   - <center>![route53 zone setting](src/route53_create_zone.png)</center>
  - Add A record
     - Click on the zone "paddle" just created
     - Click the button "Create record set"
         - Name : leave blank
         - type: "A"
-        - Value: <kube-controller ec2 private ip>
+        - Value: `<kube-controller ec2 private ip>`
+        - <center>![route53 create recordset](src/route53_create_recordset.png)</center>
  - Verify name service
     - Connect to any instance created by kube-aws via ssh
     - Run command "host paddle", see if the ip returned is the private ip of kube-controller
diff --git a/doc/howto/usage/k8s/src/route53_create_recordset.png b/doc/howto/usage/k8s/src/route53_create_recordset.png
new file mode 100644
index 0000000000000000000000000000000000000000..c4afac6b666186920707668a8d74bc0d6ad3bc07
Binary files /dev/null and b/doc/howto/usage/k8s/src/route53_create_recordset.png differ
diff --git a/doc/howto/usage/k8s/src/route53_create_zone.png b/doc/howto/usage/k8s/src/route53_create_zone.png
new file mode 100644
index 0000000000000000000000000000000000000000..d59f87bc605170fde97a8f4aae4c3eb8d4bb8c41
Binary files /dev/null and b/doc/howto/usage/k8s/src/route53_create_zone.png differ