Terraform module to define a generic Bastion host with parameterized user_data
This project is part of our comprehensive "SweetOps" approach towards DevOps.
It's 100% Open Source and licensed under the APACHE2.
We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!
Available targets:
help Help screen
help/all Display help for all targets
help/short This help short screen
lint Lint terraform code
| Name | Version |
|---|---|
| terraform | >= 0.12.0 |
| aws | ~> 2.55 |
| null | ~> 2.1 |
| template | ~> 2.1 |
| Name | Version |
|---|---|
| aws | ~> 2.55 |
| template | ~> 2.1 |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| allowed_cidr_blocks | A list of CIDR blocks allowed to connect | list(string) |
[ |
no |
| ami | AMI to use | string |
"ami-efd0428f" |
no |
| associate_public_ip_address | Whether to associate a public IP to the instance. | bool |
true |
no |
| attributes | Additional attributes (e.g. 1) |
list(string) |
[] |
no |
| delimiter | Delimiter to be used between namespace, stage, name and attributes |
string |
"-" |
no |
| enabled | When disabled, module will not create any resources | bool |
true |
no |
| ingress_security_groups | AWS security group IDs allowed ingress to instance | list(string) |
[] |
no |
| instance_type | Elastic cache instance type | string |
"t2.micro" |
no |
| key_name | Key name | string |
"" |
no |
| metadata_http_endpoint_enabled | Whether the metadata service is available | bool |
true |
no |
| metadata_http_put_response_hop_limit | The desired HTTP PUT response hop limit (between 1 and 64) for instance metadata requests. | number |
1 |
no |
| metadata_http_tokens_required | Whether or not the metadata service requires session tokens, also referred to as Instance Metadata Service Version 2. | bool |
false |
no |
| name | Name (e.g. app or bastion) |
string |
n/a | yes |
| namespace | Namespace (e.g. eg or cp) |
string |
n/a | yes |
| root_block_device_encrypted | Whether to encrypt the root block device | bool |
false |
no |
| 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 |
| security_groups | AWS security group IDs associated with instance | list(string) |
[] |
no |
| ssh_user | Default SSH user for this AMI. e.g. ec2user for Amazon Linux and ubuntu for Ubuntu systems |
string |
n/a | yes |
| stage | Stage (e.g. prod, dev, staging) |
string |
n/a | yes |
| subnets | AWS subnet IDs | list(string) |
n/a | yes |
| tags | Additional tags (e.g. map('BusinessUnit,XYZ) |
map(string) |
{} |
no |
| user_data | User data content | list(string) |
[] |
no |
| vpc_id | VPC ID | string |
n/a | yes |
| zone_id | Route53 DNS Zone ID | string |
"" |
no |
| Name | Description |
|---|---|
| hostname | DNS hostname |
| instance_id | Instance ID |
| private_ip | Private IP of the instance |
| public_ip | Public IP of the instance (or EIP) |
| role | Name of AWS IAM Role associated with the instance |
| security_group_id | Security group ID |
| ssh_user | SSH user |
Like this project? Please give it a ★ on our GitHub! (it helps us a lot)
Are you using this project or any of our other projects? Consider leaving a testimonial. =)
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
Got a question? We got answers.
File a GitHub issue, send us an email or join our Slack Community.
We are a DevOps Accelerator. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
- Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
- Release Engineering. You'll have end-to-end CI/CD with unlimited staging environments.
- Site Reliability Engineering. You'll have total visibility into your apps and microservices.
- Security Baseline. You'll have built-in governance with accountability and audit logs for all changes.
- GitOps. You'll be able to operate your infrastructure via Pull Requests.
- Training. You'll receive hands-on training so your team can operate what we build.
- Questions. You'll have a direct line of communication between our teams via a Shared Slack channel.
- Troubleshooting. You'll get help to triage when things aren't working.
- Code Reviews. You'll receive constructive feedback on Pull Requests.
- Bug Fixes. We'll rapidly work with you to fix any bugs in our projects.
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.
Participate in our Discourse Forums. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
Sign up for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
Join us every Wednesday via Zoom for our weekly "Lunch & Learn" sessions. It's FREE for everyone!
Please use the issue tracker to report any bugs or file feature requests.
If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
- 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!
Copyright © 2017-2020 Cloud Posse, LLC
See LICENSE for full details.
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.
All other trademarks referenced herein are the property of their respective owners.
This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!
We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.
We offer paid support on all of our projects.
Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.
 Erik Osterman |
 Andriy Knysh |
 Igor Rodionov |
 Bobby Larson |
|---|
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent