diff options
| author | rebortg <github@ghlr.de> | 2024-04-16 21:54:01 +0200 |
|---|---|---|
| committer | rebortg <github@ghlr.de> | 2024-04-16 21:54:01 +0200 |
| commit | 0a3febc9524e7f5d3df856bd9cf58aafb3500252 (patch) | |
| tree | e7d2eab267c4a61b944fd9474c34a9b181530068 /docs/automation/terraform/terraformAWS.rst | |
| parent | a5fcebd11b19577e082c344fd2532e8689719d9e (diff) | |
| download | vyos-documentation-0a3febc9524e7f5d3df856bd9cf58aafb3500252.tar.gz vyos-documentation-0a3febc9524e7f5d3df856bd9cf58aafb3500252.zip | |
fix several build warnings and errors
Diffstat (limited to 'docs/automation/terraform/terraformAWS.rst')
| -rw-r--r-- | docs/automation/terraform/terraformAWS.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/automation/terraform/terraformAWS.rst b/docs/automation/terraform/terraformAWS.rst index c705d55e..e068377d 100644 --- a/docs/automation/terraform/terraformAWS.rst +++ b/docs/automation/terraform/terraformAWS.rst @@ -26,16 +26,16 @@ Step by step: AWS - 1 Create an account with AWS and get your "access_key", "secret key" +1 Create an account with AWS and get your "access_key", "secret key" - 2 Create a key pair_ and download your .pem key +2 Create a key pair_ and download your .pem key .. image:: /_static/images/keypairs.png :width: 50% :align: center :alt: Network Topology Diagram - 3 Create a security group_ for the new VyOS instance and open all traffic +3 Create a security group_ for the new VyOS instance and open all traffic .. image:: /_static/images/sg.png :width: 50% @@ -263,7 +263,7 @@ If you need to delete the instance please type the command: Troubleshooting --------------- - 1 Ansible doesn't connect via SSH to your AWS instance: you have to check that your SSH key has copied into the path /root/aws/. +1 Ansible doesn't connect via SSH to your AWS instance: you have to check that your SSH key has copied into the path /root/aws/. Also, increase the time in the file instance.yml from 300 sec to 500 sec or more. (It depends on your location). Make sure that you have opened access to the instance in the security group. |