Awesome

Terraform module to define a generic Bastion host with parameterized user_data and support for AWS SSM Session Manager for remote access with IAM authentication.

[!TIP]

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform. Works with Github Actions, Atlantis, or Spacelift.
<details> <summary>Watch demo of using Atmos with Terraform</summary> <img src="https://github.com/cloudposse/atmos/blob/master/docs/demo.gif?raw=true"/> Example of running <a href="https://atmos.tools"><code>atmos</code></a> to manage infrastructure from our <a href="https://atmos.tools/quick-start/">Quick Start</a> tutorial. </detalis>

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Requirements

Name	Version
<a name="requirement_terraform"></a> terraform	>= 0.13.0
<a name="requirement_aws"></a> aws	>= 2.55

Providers

Name	Version
<a name="provider_aws"></a> aws	>= 2.55

Modules

Name	Source	Version
<a name="module_dns"></a> dns	cloudposse/route53-cluster-hostname/aws	0.12.2
<a name="module_security_group"></a> security_group	cloudposse/security-group/aws	0.3.3
<a name="module_this"></a> this	cloudposse/label/null	0.25.0

Resources

Name	Type
aws_eip.default	resource
aws_iam_instance_profile.default	resource
aws_iam_role.default	resource
aws_iam_role_policy.main	resource
aws_instance.default	resource
aws_ami.default	data source
aws_iam_policy_document.default	data source
aws_iam_policy_document.main	data source
aws_region.default	data source
aws_route53_zone.domain	data source

Inputs

Name	Description	Type	Default	Required
<a name="input_additional_tag_map"></a> additional_tag_map	Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`.<br/>This is for some rare cases where resources want additional configuration of tags<br/>and therefore take a list of maps with tag key, value, and additional configuration.	`map(string)`	`{}`	no
<a name="input_ami"></a> ami	AMI to use for the instance. Setting this will ignore `ami_filter` and `ami_owners`.	`string`	`null`	no
<a name="input_ami_filter"></a> ami_filter	List of maps used to create the AMI filter for the action runner AMI.	`map(list(string))`	<pre>{<br/> "name": [<br/> "amzn2-ami-hvm-2.*-x86_64-ebs"<br/> ]<br/>}</pre>	no
<a name="input_ami_owners"></a> ami_owners	The list of owners used to select the AMI of action runner instances.	`list(string)`	<pre>[<br/> "amazon"<br/>]</pre>	no
<a name="input_assign_eip_address"></a> assign_eip_address	Assign an Elastic IP address to the instance	`bool`	`true`	no
<a name="input_associate_public_ip_address"></a> associate_public_ip_address	Whether to associate a public IP to the instance.	`bool`	`false`	no
<a name="input_attributes"></a> attributes	ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`,<br/>in the order they appear in the list. New attributes are appended to the<br/>end of the list. The elements of the list are joined by the `delimiter`<br/>and treated as a single ID element.	`list(string)`	`[]`	no
<a name="input_context"></a> context	Single object for setting entire context at once.<br/>See description of individual variables for details.<br/>Leave string and numeric variables as `null` to use default value.<br/>Individual variable settings (non-null) override settings in context object,<br/>except for attributes, tags, and additional_tag_map, which are merged.	`any`	<pre>{<br/> "additional_tag_map": {},<br/> "attributes": [],<br/> "delimiter": null,<br/> "descriptor_formats": {},<br/> "enabled": true,<br/> "environment": null,<br/> "id_length_limit": null,<br/> "label_key_case": null,<br/> "label_order": [],<br/> "label_value_case": null,<br/> "labels_as_tags": [<br/> "unset"<br/> ],<br/> "name": null,<br/> "namespace": null,<br/> "regex_replace_chars": null,<br/> "stage": null,<br/> "tags": {},<br/> "tenant": null<br/>}</pre>	no
<a name="input_delimiter"></a> delimiter	Delimiter to be used between ID elements.<br/>Defaults to `-` (hyphen). Set to `""` to use no delimiter at all.	`string`	`null`	no
<a name="input_descriptor_formats"></a> descriptor_formats	Describe additional descriptors to be output in the `descriptors` output map.<br/>Map of maps. Keys are names of descriptors. Values are maps of the form<br/>`{<br/> format = string<br/> labels = list(string)<br/>}`<br/>(Type is `any` so the map values can later be enhanced to provide additional options.)<br/>`format` is a Terraform format string to be passed to the `format()` function.<br/>`labels` is a list of labels, in order, to pass to `format()` function.<br/>Label values will be normalized before being passed to `format()` so they will be<br/>identical to how they appear in `id`.<br/>Default is `{}` (`descriptors` output will be empty).	`any`	`{}`	no
<a name="input_disable_api_termination"></a> disable_api_termination	Enable EC2 Instance Termination Protection	`bool`	`false`	no
<a name="input_ebs_block_device_encrypted"></a> ebs_block_device_encrypted	Whether to encrypt the EBS block device	`bool`	`true`	no
<a name="input_ebs_block_device_volume_size"></a> ebs_block_device_volume_size	The volume size (in GiB) to provision for the EBS block device. Creation skipped if size is 0	`number`	`0`	no
<a name="input_ebs_delete_on_termination"></a> ebs_delete_on_termination	Whether the EBS volume should be destroyed on instance termination	`bool`	`true`	no
<a name="input_ebs_device_name"></a> ebs_device_name	The name of the EBS block device to mount on the instance	`string`	`"/dev/sdh"`	no
<a name="input_enabled"></a> enabled	Set to false to prevent the module from creating any resources	`bool`	`null`	no
<a name="input_environment"></a> environment	ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'	`string`	`null`	no
<a name="input_host_name"></a> host_name	The Bastion hostname created in Route53	`string`	`"bastion"`	no
<a name="input_id_length_limit"></a> id_length_limit	Limit `id` to this many characters (minimum 6).<br/>Set to `0` for unlimited length.<br/>Set to `null` for keep the existing setting, which defaults to `0`.<br/>Does not affect `id_full`.	`number`	`null`	no
<a name="input_instance_profile"></a> instance_profile	A pre-defined profile to attach to the instance (default is to build our own)	`string`	`""`	no
<a name="input_instance_type"></a> instance_type	Bastion instance type	`string`	`"t2.micro"`	no
<a name="input_key_name"></a> key_name	Key name	`string`	`""`	no
<a name="input_label_key_case"></a> label_key_case	Controls the letter case of the `tags` keys (label names) for tags generated by this module.<br/>Does not affect keys of tags passed in via the `tags` input.<br/>Possible values: `lower`, `title`, `upper`.<br/>Default value: `title`.	`string`	`null`	no
<a name="input_label_order"></a> label_order	The order in which the labels (ID elements) appear in the `id`.<br/>Defaults to ["namespace", "environment", "stage", "name", "attributes"].<br/>You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.	`list(string)`	`null`	no
<a name="input_label_value_case"></a> label_value_case	Controls the letter case of ID elements (labels) as included in `id`,<br/>set as tag values, and output by this module individually.<br/>Does not affect values of tags passed in via the `tags` input.<br/>Possible values: `lower`, `title`, `upper` and `none` (no transformation).<br/>Set this to `title` and set `delimiter` to `""` to yield Pascal Case IDs.<br/>Default value: `lower`.	`string`	`null`	no
<a name="input_labels_as_tags"></a> labels_as_tags	Set of labels (ID elements) to include as tags in the `tags` output.<br/>Default is to include all labels.<br/>Tags with empty values will not be included in the `tags` output.<br/>Set to `[]` to suppress all generated tags.<br/>Notes:<br/> The value of the `name` tag, if included, will be the `id`, not the `name`.<br/> Unlike other `null-label` inputs, the initial setting of `labels_as_tags` cannot be<br/> changed in later chained modules. Attempts to change it will be silently ignored.	`set(string)`	<pre>[<br/> "default"<br/>]</pre>	no
<a name="input_metadata_http_endpoint_enabled"></a> metadata_http_endpoint_enabled	Whether the metadata service is available	`bool`	`true`	no
<a name="input_metadata_http_put_response_hop_limit"></a> metadata_http_put_response_hop_limit	The desired HTTP PUT response hop limit (between 1 and 64) for instance metadata requests.	`number`	`1`	no
<a name="input_metadata_http_tokens_required"></a> metadata_http_tokens_required	Whether or not the metadata service requires session tokens, also referred to as Instance Metadata Service Version 2.	`bool`	`true`	no
<a name="input_monitoring"></a> monitoring	Launched EC2 instance will have detailed monitoring enabled	`bool`	`true`	no
<a name="input_name"></a> name	ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.<br/>This is the only ID element not also included as a `tag`.<br/>The "name" tag is set to the full `id` string. There is no tag with the value of the `name` input.	`string`	`null`	no
<a name="input_namespace"></a> namespace	ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique	`string`	`null`	no
<a name="input_regex_replace_chars"></a> regex_replace_chars	Terraform regular expression (regex) string.<br/>Characters matching the regex will be removed from the ID elements.<br/>If not set, `"/[^a-zA-Z0-9-]/"` is used to remove all characters other than hyphens, letters and digits.	`string`	`null`	no
<a name="input_root_block_device_encrypted"></a> root_block_device_encrypted	Whether to encrypt the root block device	`bool`	`true`	no
<a name="input_root_block_device_volume_size"></a> root_block_device_volume_size	The volume size (in GiB) to provision for the root block device. It cannot be smaller than the AMI it refers to.	`number`	`8`	no
<a name="input_security_group_description"></a> security_group_description	The Security Group description.	`string`	`"Bastion host security group"`	no
<a name="input_security_group_enabled"></a> security_group_enabled	Whether to create default Security Group for bastion host.	`bool`	`true`	no
<a name="input_security_group_rules"></a> security_group_rules	A list of maps of Security Group rules. <br/>The values of map is fully complated with `aws_security_group_rule` resource. <br/>To get more info see https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule .	`list(any)`	<pre>[<br/> {<br/> "cidr_blocks": [<br/> "0.0.0.0/0"<br/> ],<br/> "description": "Allow all outbound traffic",<br/> "from_port": 0,<br/> "protocol": -1,<br/> "to_port": 0,<br/> "type": "egress"<br/> },<br/> {<br/> "cidr_blocks": [<br/> "0.0.0.0/0"<br/> ],<br/> "description": "Allow all inbound to SSH",<br/> "from_port": 22,<br/> "protocol": "tcp",<br/> "to_port": 22,<br/> "type": "ingress"<br/> }<br/>]</pre>	no
<a name="input_security_group_use_name_prefix"></a> security_group_use_name_prefix	Whether to create a default Security Group with unique name beginning with the normalized prefix.	`bool`	`false`	no
<a name="input_security_groups"></a> security_groups	A list of Security Group IDs to associate with bastion host.	`list(string)`	`[]`	no
<a name="input_ssh_user"></a> ssh_user	Default SSH user for this AMI. e.g. `ec2-user` for Amazon Linux and `ubuntu` for Ubuntu systems	`string`	`"ec2-user"`	no
<a name="input_ssm_enabled"></a> ssm_enabled	Enable SSM Agent on Host.	`bool`	`true`	no
<a name="input_stage"></a> stage	ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'	`string`	`null`	no
<a name="input_subnets"></a> subnets	AWS subnet IDs	`list(string)`	n/a	yes
<a name="input_tags"></a> tags	Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`).<br/>Neither the tag keys nor the tag values will be modified by this module.	`map(string)`	`{}`	no
<a name="input_tenant"></a> tenant	ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for	`string`	`null`	no
<a name="input_user_data"></a> user_data	User data content. Will be ignored if `user_data_base64` is set	`list(string)`	`[]`	no
<a name="input_user_data_base64"></a> user_data_base64	The Base64-encoded user data to provide when launching the instances. If this is set then `user_data` will not be used.	`string`	`""`	no
<a name="input_user_data_template"></a> user_data_template	User Data template to use for provisioning EC2 Bastion Host	`string`	`"user_data/amazon-linux.sh"`	no
<a name="input_vpc_id"></a> vpc_id	VPC ID	`string`	n/a	yes
<a name="input_zone_id"></a> zone_id	Route53 DNS Zone ID	`string`	`""`	no

Outputs

Name	Description
<a name="output_arn"></a> arn	ARN of the instance
<a name="output_hostname"></a> hostname	DNS hostname
<a name="output_id"></a> id	Disambiguated ID of the instance
<a name="output_instance_id"></a> instance_id	Instance ID
<a name="output_name"></a> name	Instance name
<a name="output_private_dns"></a> private_dns	Private DNS of instance
<a name="output_private_ip"></a> private_ip	Private IP of the instance
<a name="output_public_dns"></a> public_dns	Public DNS of instance (or DNS of EIP)
<a name="output_public_ip"></a> public_ip	Public IP of the instance (or EIP)
<a name="output_role"></a> role	Name of AWS IAM Role associated with the instance
<a name="output_security_group_arn"></a> security_group_arn	Bastion host Security Group ARN
<a name="output_security_group_id"></a> security_group_id	Bastion host Security Group ID
<a name="output_security_group_ids"></a> security_group_ids	IDs on the AWS Security Groups associated with the instance
<a name="output_security_group_name"></a> security_group_name	Bastion host Security Group name
<a name="output_ssh_user"></a> ssh_user	SSH user

Related Projects

Check out these related projects.

bastion - 🔒Secure Bastion implemented as Docker Container running Alpine Linux with Google Authenticator & DUO MFA support
terraform-aws-ec2-instance - Terraform module for providing a general EC2 instance provisioned by Ansible
terraform-aws-ec2-ami-backup - Terraform module for automatic & scheduled AMI creation

[!TIP]

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team. ✅ Your team owns everything. ✅ 100% Open Source and backed by fanatical support. 

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-ec2-bastion-server&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>
<details><summary>📚 Learn More</summary> 
Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.

Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.

Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.

Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.

GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-ec2-bastion-server&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>

Day-2: Your Operational Mastery

Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.

Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.

Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.

Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.

Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.

Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.

Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-ec2-bastion-server&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>
</details>

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

Review our Code of Conduct and Contributor Guidelines.
Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours <a href="https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/terraform-aws-ec2-bastion-server&utm_content=office_hours"><img src="https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png" align="right" /></a>

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

<details> <summary>Preamble to the Apache License, Version 2.0</summary>

Complete license is available in the LICENSE file.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

</details>

Trademarks

All other trademarks referenced herein are the property of their respective owners.