Awesome

Terraform Module for providing N general purpose EC2 hosts.

If you only need to provision a single EC2 instance, consider using the terraform-aws-ec2-instance module instead.

IMPORTANT This module by-design does not provision an AutoScaling group. It was designed to provision a discrete number of instances suitable for running stateful services such as databases (e.g. Kafka, Redis, etc).

Included features:

Automatically create a Security Group
Option to switch EIP attachment
CloudWatch monitoring and automatic reboot if instance hangs
Assume Role capability

[!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>

Usage

Note: add ${var.ssh_key_pair} private key to the ssh agent.

Include this repository as a module in your existing terraform code.

Simple example:

module "instance" {
  source = "cloudposse/ec2-instance-group/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"
  namespace                   = "eg"
  stage                       = "prod"
  name                        = "app"
  ami                         = "ami-a4dc46db"
  ami_owner                   = "099720109477"
  ssh_key_pair                = var.ssh_key_pair
  instance_type               = var.instance_type
  vpc_id                      = var.vpc_id
  security_groups             = var.security_groups
  subnet                      = var.subnet
  instance_count              = 3
}

Example with additional volumes and EIP

module "kafka_instance" {
  source = "cloudposse/ec2-instance-group/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"

  namespace                   = "eg"
  stage                       = "prod"
  name                        = "app"
  ami                         = "ami-a4dc46db"
  ami_owner                   = "099720109477"
  ssh_key_pair                = var.ssh_key_pair
  vpc_id                      = var.vpc_id
  security_groups             = var.security_groups
  subnet                      = var.subnet
  associate_public_ip_address = true
  additional_ips_count        = 1
  ebs_volume_count            = 2
  instance_count              = 3

  security_group_rules = [
    {
      type        = "egress"
      from_port   = 0
      to_port     = 65535
      protocol    = "-1"
      cidr_blocks = ["0.0.0.0/0"]
    },
    {
      type        = "ingress"
      from_port   = 22
      to_port     = 22
      protocol    = "tcp"
      cidr_blocks = ["0.0.0.0/0"]
    },
    {
      type        = "ingress"
      from_port   = 80
      to_port     = 80
      protocol    = "tcp"
      cidr_blocks = ["0.0.0.0/0"]
    },
    {
      type        = "ingress"
      from_port   = 443
      to_port     = 443
      protocol    = "tcp"
      cidr_blocks = ["0.0.0.0/0"]
    }
  ]
}

Additional complete working example with variations of how to use the module

In /examples directory

This module depends on these modules:

terraform-terraform-label

It is necessary to run terraform get or terraform init to download this module.

Now reference the label when creating an instance (for example):

resource "aws_ami_from_instance" "example" {
  count              = length(module.instance.*.id)
  name               = "app"
  source_instance_id = element(module.instance.*.id, count.index)
}

[!IMPORTANT] In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic approach for updating versions to avoid unexpected changes.

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	>= 1.0
<a name="requirement_aws"></a> aws	>= 2.0

Providers

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

Modules

Name	Source	Version
<a name="module_label"></a> label	cloudposse/label/null	0.25.0
<a name="module_security_group"></a> security_group	cloudposse/security-group/aws	2.2.0
<a name="module_ssh_key_pair"></a> ssh_key_pair	cloudposse/key-pair/aws	0.19.0
<a name="module_this"></a> this	cloudposse/label/null	0.25.0

Resources

Name	Type
aws_cloudwatch_metric_alarm.default	resource
aws_ebs_volume.default	resource
aws_eip.additional	resource
aws_eip.default	resource
aws_iam_instance_profile.default	resource
aws_iam_role.default	resource
aws_instance.default	resource
aws_network_interface.additional	resource
aws_network_interface_attachment.additional	resource
aws_volume_attachment.default	resource
aws_ami.info	data source
aws_caller_identity.default	data source
aws_iam_policy_document.default	data source
aws_region.default	data source

Inputs

Name	Description	Type	Default	Required
<a name="input_additional_ips_count"></a> additional_ips_count	Count of additional EIPs	`number`	`0`	no
<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	The AMI to use for the instance	`string`	n/a	yes
<a name="input_ami_owner"></a> ami_owner	Owner of the given AMI	`string`	n/a	yes
<a name="input_applying_period"></a> applying_period	The period in seconds over which the specified statistic is applied	`number`	`60`	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	Associate a public IP address with 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_availability_zone"></a> availability_zone	Availability Zone the instance is launched in. If not set, will be launched in the first AZ of the region	`string`	`""`	no
<a name="input_comparison_operator"></a> comparison_operator	The arithmetic operation to use when comparing the specified Statistic and Threshold. Possible values are: GreaterThanOrEqualToThreshold, GreaterThanThreshold, LessThanThreshold, LessThanOrEqualToThreshold	`string`	`"GreaterThanOrEqualToThreshold"`	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_default_alarm_action"></a> default_alarm_action	Default alarm action	`string`	`"action/actions/AWS_EC2.InstanceId.Reboot/1.0"`	no
<a name="input_delete_on_termination"></a> delete_on_termination	Whether the volume should be destroyed on instance termination	`bool`	`true`	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_device_names"></a> ebs_device_names	Name of the EBS device to mount	`list(string)`	<pre>[<br/> "/dev/xvdb",<br/> "/dev/xvdc",<br/> "/dev/xvdd",<br/> "/dev/xvde",<br/> "/dev/xvdf",<br/> "/dev/xvdg",<br/> "/dev/xvdh",<br/> "/dev/xvdi",<br/> "/dev/xvdj",<br/> "/dev/xvdk",<br/> "/dev/xvdl",<br/> "/dev/xvdm",<br/> "/dev/xvdn",<br/> "/dev/xvdo",<br/> "/dev/xvdp",<br/> "/dev/xvdq",<br/> "/dev/xvdr",<br/> "/dev/xvds",<br/> "/dev/xvdt",<br/> "/dev/xvdu",<br/> "/dev/xvdv",<br/> "/dev/xvdw",<br/> "/dev/xvdx",<br/> "/dev/xvdy",<br/> "/dev/xvdz"<br/>]</pre>	no
<a name="input_ebs_iops"></a> ebs_iops	Amount of provisioned IOPS. This must be set with a volume_type of io1	`number`	`0`	no
<a name="input_ebs_optimized"></a> ebs_optimized	Launched EC2 instance will be EBS-optimized	`bool`	`false`	no
<a name="input_ebs_volume_count"></a> ebs_volume_count	Count of EBS volumes that will be attached to the instance	`number`	`0`	no
<a name="input_ebs_volume_encrypted"></a> ebs_volume_encrypted	Size of the EBS volume in gigabytes	`bool`	`true`	no
<a name="input_ebs_volume_size"></a> ebs_volume_size	Size of the EBS volume in gigabytes	`number`	`10`	no
<a name="input_ebs_volume_type"></a> ebs_volume_type	The type of EBS volume. Can be standard, gp2 or io1	`string`	`"gp2"`	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_evaluation_periods"></a> evaluation_periods	The number of periods over which data is compared to the specified threshold	`number`	`5`	no
<a name="input_generate_ssh_key_pair"></a> generate_ssh_key_pair	If true, create a new key pair and save the pem for it to the current working directory	`bool`	`false`	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_count"></a> instance_count	Count of ec2 instances to create	`number`	`1`	no
<a name="input_instance_type"></a> instance_type	The type of the instance	`string`	`"t2.micro"`	no
<a name="input_ipv6_address_count"></a> ipv6_address_count	Number of IPv6 addresses to associate with the primary network interface. Amazon EC2 chooses the IPv6 addresses from the range of your subnet	`number`	`0`	no
<a name="input_ipv6_addresses"></a> ipv6_addresses	List of IPv6 addresses from the range of the subnet to associate with the primary network interface	`list(string)`	`[]`	no
<a name="input_kms_key_id"></a> kms_key_id	KMS key ID used to encrypt EBS volume. When specifying kms_key_id, ebs_volume_encrypted needs to be set to true	`string`	`null`	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_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_metric_name"></a> metric_name	The name for the alarm's associated metric. Allowed values can be found in https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ec2-metricscollected.html	`string`	`"StatusCheckFailed_Instance"`	no
<a name="input_metric_namespace"></a> metric_namespace	The namespace for the alarm's associated metric. Allowed values can be found in https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/aws-namespaces.html	`string`	`"AWS/EC2"`	no
<a name="input_metric_threshold"></a> metric_threshold	The value against which the specified statistic is compared	`number`	`1`	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_permissions_boundary_arn"></a> permissions_boundary_arn	Policy ARN to attach to instance role as a permissions boundary	`string`	`""`	no
<a name="input_private_ips"></a> private_ips	Private IP address to associate with the instances in the VPC	`list(string)`	`[]`	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_region"></a> region	AWS Region the instance is launched in	`string`	n/a	yes
<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_iops"></a> root_iops	Amount of provisioned IOPS. This must be set if root_volume_type is set to `io1`	`number`	`0`	no
<a name="input_root_volume_size"></a> root_volume_size	Size of the root volume in gigabytes	`number`	`10`	no
<a name="input_root_volume_type"></a> root_volume_type	Type of root volume. Can be standard, gp2 or io1	`string`	`"gp2"`	no
<a name="input_security_group_description"></a> security_group_description	The Security Group description.	`string`	`"EC2 instances Security Group"`	no
<a name="input_security_group_enabled"></a> security_group_enabled	Whether to create default Security Group for EC2 instances.	`bool`	`true`	no
<a name="input_security_group_name"></a> security_group_name	The name to assign to the security group. Must be unique within the VPC.<br/>If not provided, will be derived from the `null-label.context` passed in.<br/>If `create_before_destroy` is true, will be used as a name prefix.	`list(string)`	`[]`	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)`	`[]`	no
<a name="input_security_groups"></a> security_groups	A list of Security Group IDs to associate with EC2 instances.	`list(string)`	`[]`	no
<a name="input_source_dest_check"></a> source_dest_check	Controls if traffic is routed to the instance when the destination address does not match the instance. Used for NAT or VPNs	`bool`	`true`	no
<a name="input_ssh_key_pair"></a> ssh_key_pair	SSH key pair to be provisioned on the instance	`string`	`""`	no
<a name="input_ssh_key_pair_path"></a> ssh_key_pair_path	Path to where the generated key pairs will be created. Defaults to $${path.cwd}	`string`	`""`	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_statistic_level"></a> statistic_level	The statistic to apply to the alarm's associated metric. Allowed values are: SampleCount, Average, Sum, Minimum, Maximum	`string`	`"Maximum"`	no
<a name="input_subnet"></a> subnet	VPC Subnet ID the instance is launched in	`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	Instance user data. Do not pass gzip-compressed data via this argument	`string`	`""`	no
<a name="input_vpc_id"></a> vpc_id	The ID of the VPC that the instance security group belongs to	`string`	n/a	yes

Outputs

Name	Description
<a name="output_alarm_ids"></a> alarm_ids	CloudWatch Alarm IDs
<a name="output_aws_key_pair_name"></a> aws_key_pair_name	Name of AWS key pair
<a name="output_ebs_ids"></a> ebs_ids	IDs of EBSs
<a name="output_eip_per_instance_count"></a> eip_per_instance_count	Number of EIPs per instance.
<a name="output_eni_to_eip_map"></a> eni_to_eip_map	Map of ENI with EIP
<a name="output_ids"></a> ids	Disambiguated IDs list
<a name="output_instance_count"></a> instance_count	Total number of instances created
<a name="output_name"></a> name	Instance(s) name
<a name="output_new_ssh_keypair_generated"></a> new_ssh_keypair_generated	Was a new ssh_key_pair generated
<a name="output_primary_network_interface_ids"></a> primary_network_interface_ids	IDs of the instance's primary network interface
<a name="output_private_dns"></a> private_dns	Private DNS records of instances
<a name="output_private_ips"></a> private_ips	Private IPs of instances
<a name="output_public_dns"></a> public_dns	All public DNS records for the public interfaces and ENIs
<a name="output_public_ips"></a> public_ips	List of Public IPs of instances (or EIP)
<a name="output_role_names"></a> role_names	Names of AWS IAM Roles associated with creating instance
<a name="output_security_group_arn"></a> security_group_arn	EC2 instances Security Group ARN
<a name="output_security_group_id"></a> security_group_id	EC2 instances Security Group ID
<a name="output_security_group_ids"></a> security_group_ids	ID on the new AWS Security Group associated with creating instance
<a name="output_security_group_name"></a> security_group_name	EC2 instances Security Group name
<a name="output_ssh_key_pem_path"></a> ssh_key_pem_path	Path where SSH key pair was created (if applicable)

Related Projects

Check out these related projects.

terraform-aws-ec2-instance - Terraform Module for providing a general EC2 instance provisioned by Ansible
terraform-aws-ec2-bastion-server - Terraform Module to define a generic Bastion host with parameterized user_data
https://github.com/cloudposse/terraform-aws-rds-cluster - Terraform module to provision an RDS Aurora cluster for MySQL or Postgres

References

For additional context, refer to some of these links.

terraform-aws-ec2-bastion-server - Terraform module to define a generic Bastion host with parameterized user_data

[!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-instance-group&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-instance-group&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-instance-group&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-instance-group&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.