prehistoric-systems/scottslowe-learning-tools
1
0
Fork 0
mirror of https://codeberg.org/scottslowe/learning-tools.git synced 2026-03-11 09:04:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
scottslowe-learning-tools/terraform/aws/bastion-aws
History
Scott Lowe d209719e15
Add documentation for Terraform+AWS environments 
Add `README.md` files for the Terraform+AWS environments that did not already have documentation on use. Update `README.md` for the bastion-aws environment to appropriately reflect the environment.

Closes #83.

Signed-off-by: Scott Lowe <scott.lowe@scottlowe.org>
2017-09-07 09:57:19 -06:00
..
data.tf Commit finalized Terraform configuration 2017-05-23 16:19:56 -06:00
instances.tf Commit finalized Terraform configuration 2017-05-23 16:19:56 -06:00
networking.tf Commit finalized Terraform configuration 2017-05-23 16:19:56 -06:00
output.tf Commit finalized Terraform configuration 2017-05-23 16:19:56 -06:00
provider.tf Clean up SSH bastion environment 2017-05-25 09:50:48 -06:00
README.md Add documentation for Terraform+AWS environments 2017-09-07 09:57:19 -06:00
security.tf Commit finalized Terraform configuration 2017-05-23 16:19:56 -06:00
ssh.cfg.example Fix ssh.cfg.example 2017-05-26 08:54:02 -06:00
variables.tf Clean up SSH bastion environment 2017-05-25 09:50:48 -06:00

README.md

SSH Bastion Hosts on AWS with Terraform

These files provide an example of how to use Terraform to create a "private" EC2 subnet where instances can only be reached via use of an SSH bastion host. Refer to this blog post for more information on SSH bastion hosts.

Contents

  • data.tf: This Terraform configuration file provides information to Terraform on which AWS AMIs to use.

  • instances.tf: This Terraform configuration file specifies the AWS instances to create.

  • networking.tf: This Terraform configuration creates all the networking components: the VPC (Virtual Private Cloud), subnets, Internet gateway, and the route table.

  • output.tf: This Terraform configuration file supplies information about the instances created by Terraform (public and private IP addresses, as appropriate).

  • provider.tf: This Terraform configuration files configures the AWS provider.

  • README.md: The file you're currently reading.

  • security.tf: Security groups and security group rules are defined in this Terraform configuration file.

  • ssh.cfg.example: This is an example of the configuration stanzas that may be needed to support the use of an SSH bastion host.

  • variables.tf: This Terraform configuration file specifies variables that Terraform will need in order to create the desired AWS infrastructure.

Instructions

These instructions assume that you have an AWS account, that Terraform is installed and working correctly, and that you've appropriately supplied the necessary AWS credentials to Terraform.

  1. Place the files from the terraform/aws/bastion-aws directory of this GitHub repository into a directory on your local system. You can clone the entire "learning-tools" repository (using git clone) or just download the specific files from the terraform/aws/bastion-aws folder.

  2. Create a file named terraform.tfvars and populate it with the name of the AWS keypair you'd like to use for the instances, the AWS region to use, and the type (like "t2.micro") of the instances. Refer to this URL for specific details on the syntax of this file. You can refer to the contents of variables.tf for the names of the variables that need to be defined.

  3. Run terraform plan to have Terraform examine the current infrastructure and determine what changes are necessary to realize the desired configuration.

  4. Run terraform apply to have Terraform make the changes necessary to realize the desired configuration.

  5. When Terraform is done running, it will output the public and private IP addresses of the bastion along with the private IP address of the remote host. Use these values, as appropriate, to configure your SSH client. You can refer to the file ssh.cfg.example for an example of how your SSH configuration may need to be modified.

  6. When your SSH client is properly configured, attempt to connect via SSH to the bastion host. It should work as expected.

  7. Now attempt to connect via SSH to the private host's private (non-routable) IP address. This should also work, as the connection is operating via the bastion host.

Enjoy!

License

This content is licensed under the MIT License.