diff --git a/doc/howto/usage/k8s/k8s_aws_en.md b/doc/howto/usage/k8s/k8s_aws_en.md
index 8d88e9d1cd609770abcb8e13fd800fc9e5ba2dfc..ce72b0803818d5bf0c18753c421848cf2fc1b668 100644
--- a/doc/howto/usage/k8s/k8s_aws_en.md
+++ b/doc/howto/usage/k8s/k8s_aws_en.md
@@ -384,14 +384,16 @@ Edit `/etc/hosts` to associate above ip with the DNS name.
    - Domain name: "paddle"
    - Type: "Private hosted zone for amazon VPC"
    - VPC ID: `<Your VPC ID>`
-   - <center>![route53 zone setting](src/route53_create_zone.png =400x)</center>
+
+   ![route53 zone setting](src/route53_create_zone.png)
  - 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>`
-        - <center>![route53 create recordset](src/route53_create_recordset.png =400x)</center>
+
+        ![route53 create recordset](src/route53_create_recordset.png)
  - 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_zone.png b/doc/howto/usage/k8s/src/route53_create_zone.png
index b8162da4426b38241222323fa4a51b98f820888d..25b7ddb831c5cba97f4b2edddd27da3234d621af 100644
Binary files a/doc/howto/usage/k8s/src/route53_create_zone.png and b/doc/howto/usage/k8s/src/route53_create_zone.png differ