fix inline policy in Advanced installation in README.md

Author: tinuva

README.md

@@ -1,14 +1,14 @@
 <img src="http://awsmedia.s3.amazonaws.com/AWS_Logo_PoweredBy_127px.png" alt="Powered by Amazon Web Services" align="right">
 
-# LambdaBlogPlatform 
+# LambdaBlogPlatform
 ## serverless blogging platform built with AWS
 
 ## Table of Contents
  * [About](#about)
  * [Installation prerequisites](#prerequisites)
  * [Installation](#installation)
  * [Advanced installation](#installation_advanced)
-  
+
 ## <a name="about"></a>About
  ![alt tag](https://s3-us-west-2.amazonaws.com/s-media.si/static/img/LBP_perspective_UI.jpg)
 AWS Lambda Blog Platform is a complete blogging solution that uses the following Amazon Web Services for operation
@@ -18,12 +18,12 @@ AWS Lambda Blog Platform is a complete blogging solution that uses the following
  * S3
  * Cloudfront
  * SES
- 
+
 It runs completely serverless - free of any inflexible hardware infrastructure. The whole system running as a team of small misroservices means that the running expenses are without any overhead even at the smallest scale.
 
 ## <a name="prerequisites"></a>Installation prerequisites
 * Have an AWS account
-* Have your domain/subdomain set up in Route53 
+* Have your domain/subdomain set up in Route53
 * make sure you can receive email on one of the following adressees for https certificate generation (if you dont have mail server set up, you can use https://github.com/sirceljm/AWS-SES-simple-mail-forward to forward emails to your email address)
  * administrator@domain.com
  * hostmaster@domain.com
@@ -68,7 +68,7 @@ It runs completely serverless - free of any inflexible hardware infrastructure.
         }
     ]
 }
-``` 
+```
 * (install script will add other permisions that are necessary for installation)
 * run ```node install.js```
 * wizard will take you through the process of installation
@@ -79,42 +79,44 @@ It runs completely serverless - free of any inflexible hardware infrastructure.
 * run ```npm install```
 * Create a new user in IAM (you will put this user name into install_config.js later)
  * [IAM -> Users -> Add User -> Access type -> check Programmatic access]
-* Copy account keys for the user and make a json file that looks like this: 
+* Copy account keys for the user and make a json file that looks like this:
  ![user_access_keys](https://s3-us-west-2.amazonaws.com/s-media.si/static/img/user_access_keys.png)
 
  ```json
  {
-    "accessKeyId": "AK************", 
-    "secretAccessKey": "BX**********************", 
+    "accessKeyId": "AK************",
+    "secretAccessKey": "BX**********************",
     "region": "eu-west-1"
 }
 ```
- * add a new inline policy to the user 
+ * add a new inline policy to the user
   * [IAM -> Users -> your_user -> Permissions -> Add inline policy -> Custom policy -> Select -> Copy JSON below and enter a policy name
-  
+
    ```json
 
-{
-    "Version": "2012-10-17",
-    "Statement": [
-        {
-            "Sid": "Stmt1481118325000",
-            "Effect": "Allow",
-            "Action": [
-                "iam:CreatePolicy",
-                "iam:CreateRole",
-                "iam:GetPolicy",
-                "iam:GetRole",
-                "iam:AttachUserPolicy",
-                "iam:AttachRolePolicy",
-                "iam:PassRole"
-            ],
-            "Resource": [
-                "*"
-            ]
-        }
-    ]
-}
+   {
+       "Version": "2012-10-17",
+       "Statement": [
+           {
+               "Sid": "Stmt1481118325000",
+               "Effect": "Allow",
+               "Action": [
+                   "iam:CreatePolicy",
+                   "iam:CreateRole",
+                   "iam:GetPolicy",
+                   "iam:GetRole",
+                   "iam:AttachUserPolicy",
+                   "iam:AttachRolePolicy",
+                   "iam:PassRole",
+                   "route53:ListHostedZones",
+                   "acm:ListCertificates"
+               ],
+               "Resource": [
+                   "*"
+               ]
+           }
+       ]
+   }
 ```
 
  -> Attach policy]
@@ -126,6 +128,6 @@ It runs completely serverless - free of any inflexible hardware infrastructure.
  ![alt tag](https://s3-us-west-2.amazonaws.com/s-media.si/static/img/cert_arn.png)
  * get your recaptcha key (you can edit this later in API Gateway)
  * copy install/install_config_template.js to install/install_config.js
- * change values in install/install_config.js 
+ * change values in install/install_config.js
  * run ```node install.js```
  * if everything went smooth you should see your page after CloudFront changes resolve (usually takes around 15 minutes)