anchor.diff:  
   **SSH to EC2 Instances**
   
  -In order to answer these questions, you will first need to be able to SHH to the EC2 instances:
  +In order to answer these questions, you will first need to be able to SSH to the EC2 instances:
   
   From the EC2 dashboard, you can locate the instances by filtering on a prefix of the name of your stack, in my case `my-stack`,
  -and as indicated below you will see the instances for KIll Bill server and KAUI. In the example below we see one of each:
  +and as indicated below you will see the instances for Kill Bill server and KAUI. In the example below we see one of each:
   
   
   image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/ec2-instances.png[align=center]
   
  -You can select one instance and and then from the description tag, you will have access to:
  +You can select one instance and then from the description tag, you will have access to:
  +
   1. Public DNS
   2. The security group
   
   image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/ec2-description.png[align=center]
   
  -You will need to first click on the security group link to open the inbound port 22 required for SHH, as shown below:
  +You will need to first click on the security group link to open the inbound port 22 required for SSH, as shown below:
   
   image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/security-group.png[align=center]
   
  -Then, you can issue the SHH command, by copying the Public DNS from the description tab:
  +Then, you can issue the SSH command, by copying the Public DNS from the description tab:
   
   ```
   # SSH as ubuntu user
  
positive.code: RDS cluster, so be patient...
  
  
  Let's start with the https://console.amazonaws.cn/cloudformation[CloudFormation console]: The stack will have a status which will be `CREATE_IN_PROGRESS` for the duration of the initialization, and will then either transition to `CREATE_COMPLETE` or `CREATE_FAILED`. In case of `CREATE_FAILED`, try to locate from the `Resources` tab which resource fail to initialize properly.
  
  ==== Possible Issues
  
  
negative.code: **AWS Errors**
  
  Typical Issues are:
  
    * Insufficient IAM Permissions
    * Limit Exceeded
    * Security Group Does Not Exist in VPC
    * RDS Cluster failed to come up
    * ...
  
  Make sure to check our `Pre-requisites` section to ensure you have setup a valid VPC with valid subnets. Fow AWS specific issues, please refer to the https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html[AWS troubleshooting documentation]
      
  **Service Unavailable**
  
  