https://github.com/azavea/terraform-aws-ecs-cluster
A Terraform module to create an Amazon Web Services (AWS) EC2 Container Service (ECS) cluster.
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (5.4%) to scientific vocabulary
Keywords
Keywords from Contributors
Repository
A Terraform module to create an Amazon Web Services (AWS) EC2 Container Service (ECS) cluster.
Basic Info
- Host: GitHub
- Owner: azavea
- License: apache-2.0
- Language: HCL
- Default Branch: develop
- Size: 90.8 KB
Statistics
- Stars: 79
- Watchers: 13
- Forks: 67
- Open Issues: 4
- Releases: 0
Topics
Metadata Files
README.md
terraform-aws-ecs-cluster
A Terraform module to create an Amazon Web Services (AWS) EC2 Container Service (ECS) cluster.
Table of Contents
Usage
This module creates a security group that gets associated with the launch template for the ECS cluster Auto Scaling group. By default, the security group contains no rules. In order for network traffic to flow egress or ingress (including communication with ECS itself), you must associate all of the appropriate aws_security_group_rule resources with the container_instance_security_group_id module output.
See below for an example.
```hcl data "templatefile" "containerinstancecloudconfig" { template = "${file("cloud-config/container-instance.yml.tpl")}"
vars { environment = "${var.environment}" } }
module "containerservicecluster" { source = "github.com/azavea/terraform-aws-ecs-cluster?ref=3.0.0"
vpcid = "vpc-20f74844" amiid = "ami-b2df2ca4" instancetype = "t2.micro" keyname = "hector" cloudconfigcontent = "${data.templatefile.containerinstancecloudconfig.rendered}"
rootblockdevicetype = "gp2" rootblockdevicesize = "10"
healthcheckgraceperiod = "600" desiredcapacity = "1" minsize = "0" maxsize = "1"
enabled_metrics = [ "GroupMinSize", "GroupMaxSize", "GroupDesiredCapacity", "GroupInServiceInstances", "GroupPendingInstances", "GroupStandbyInstances", "GroupTerminatingInstances", "GroupTotalInstances", ]
subnet_ids = [...]
project = "Something" environment = "Staging" }
resource "awssecuritygrouprule" "containerinstancehttpegress" { type = "egress" fromport = 80 toport = 80 protocol = "tcp" cidr_blocks = ["0.0.0.0/0"]
securitygroupid = "${module.containerservicecluster.containerinstancesecuritygroupid}" }
resource "awssecuritygrouprule" "containerinstancehttpsegress" { type = "egress" fromport = 443 toport = 443 protocol = "tcp" cidr_blocks = ["0.0.0.0/0"]
securitygroupid = "${module.containerservicecluster.containerinstancesecuritygroupid}" } ```
Auto Scaling
This module creates an Auto Scaling group for the ECS cluster. By default, there are no Auto Scaling policies associated with this group. In order for Auto Scaling to function, you must define aws_autoscaling_policy resources and associate them with the container_instance_autoscaling_group_name module output.
See this article for more information on Auto Scaling, and below for example policies.
```hcl resource "awsautoscalingpolicy" "containerinstancecpureservation" { name = "asgScalingPolicyCPUReservation" autoscalinggroupname = "${module.containerservicecluster.containerinstanceautoscalinggroupname}" adjustmenttype = "ChangeInCapacity" policy_type = "TargetTrackingScaling"
targettrackingconfiguration { customizedmetricspecification { metricdimension { name = "ClusterName" value = "${module.containerservice_cluster.name}" }
metric_name = "CPUReservation"
namespace = "AWS/ECS"
statistic = "Average"
}
target_value = "50.0"
} }
resource "awsautoscalingpolicy" "containerinstancememoryreservation" { name = "asgScalingPolicyMemoryReservation" autoscalinggroupname = "${module.containerservicecluster.containerinstanceautoscalinggroupname}" adjustmenttype = "ChangeInCapacity" policy_type = "TargetTrackingScaling"
targettrackingconfiguration { customizedmetricspecification { metricdimension { name = "ClusterName" value = "${module.containerservice_cluster.name}" }
metric_name = "MemoryReservation"
namespace = "AWS/ECS"
statistic = "Average"
}
target_value = "90.0"
} } ```
It's worth noting that the aws_autoscaling_policy documentation suggests we remove desired_capacity from the aws_autoscaling_group resource when using Auto Scaling. That makes sense, because when it is present, any Terraform plan/apply cycle will reset it.
Unfortunately, removing it from the aws_autoscaling_group resource means removing it from the module too.
We will reevaluate things when Terraform 0.12 comes out because it promises handling of a null desired_capacity.
Variables
cluster_name- Name of the ECS Cluster, it is optionalautoscaling_group_name- Name of the autoscaling group for ECS Cluster, it is optionalsecurity_group_name- Name of the security group for ECS Cluster, it is optionalecs_for_ec2_service_role_name- Name of iam role for ECS Cluster, it is optionalecs_service_role_name- Name of iam role for ECS Service, it is optionalvpc_id- ID of VPC meant to house clusterlookup_latest_ami- lookup the latest Amazon-owned ECS AMI. If this variable istrue, the latest ECS AMI will be used, even ifami_idis provided (default:false).ami_id- Cluster instance Amazon Machine Image (AMI) ID. Iflookup_latest_amiistrue, this variable will be silently ignored.ami_owners- List of accounts that own the AMI (default:self, amazon, aws-marketplace)root_block_device_type- Instance root block device type (default:gp2)root_block_device_size- Instance root block device size in gigabytes (default:8)instance_type- Instance type for cluster instances (default:t2.micro)cpu_credit_specification- Credit option for CPU usage. Can be "standard" or "unlimited". (default:standard).detailed_monitoring- If this variable istrue, then detailed monitoring will be enabled on the instance. (default:false)key_name- EC2 Key pair namecloud_config_content- user data supplied to launch configuration for cluster nodescloud_config_content_type- the type of configuration being passed in as user data, see EC2 user guide for a list of possible types (default:text/cloud-config)health_check_grace_period- Time in seconds after container instance comes into service before checking health (default:600)desired_capacity- Number of EC2 instances that should be running in cluster (default:1)min_size- Minimum number of EC2 instances in cluster (default:0)max_size- Maximum number of EC2 instances in cluster (default:1)enabled_metrics- A list of metrics to gather for the clustersubnet_ids- A list of subnet IDs to launch cluster instancesproject- Name of project this cluster is for (default:Unknown)environment- Name of environment this cluster is targeting (default:Unknown)
Outputs
id- The container service cluster IDname- The container service cluster namecontainer_instance_security_group_id- Security group ID of the EC2 container instancescontainer_instance_ecs_for_ec2_service_role_name- Name of IAM role associated with EC2 container instancesecs_service_role_name- Name of IAM role for use with ECS servicesecs_service_role_arn- ARN of IAM role for use with ECS servicescontainer_instance_ecs_for_ec2_service_role_arn- ARN of IAM role associated with EC2 container instancescontainer_instance_autoscaling_group_name- Name of container instance Auto Scaling Group
Owner
- Name: Azavea
- Login: azavea
- Kind: organization
- Location: Philadelphia, PA
- Website: https://www.azavea.com
- Repositories: 383
- Profile: https://github.com/azavea
Geospatial software engineering for good
GitHub Events
Total
- Fork event: 2
Last Year
- Fork event: 2
Committers
Last synced: 7 months ago
Top Committers
| Name | Commits | |
|---|---|---|
| Hector Castro | h****o@g****m | 13 |
| Taylor Nation | t****4@g****m | 10 |
| Rocky Breslow | r****w@a****m | 7 |
| Hector Castro | h****o@a****m | 6 |
| Miguel Ferreira | m****a@m****m | 3 |
| Claude M. Schrader | c****r@a****m | 3 |
| yeer | y****b@g****m | 1 |
| bizmate | d****o@b****z | 1 |
| Christophe Verclytte | c****e@g****m | 1 |
| Pubudu Perera | s****2@g****m | 1 |
| production-dave | d****m@g****m | 1 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 7 months ago
All Time
- Total issues: 23
- Total pull requests: 36
- Average time to close issues: 2 months
- Average time to close pull requests: about 1 month
- Total issue authors: 14
- Total pull request authors: 12
- Average comments per issue: 1.78
- Average comments per pull request: 1.03
- Merged pull requests: 25
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- hectcastro (8)
- tnation14 (2)
- pa-yourserveradmin-com (1)
- Kgirthofer (1)
- nanotubing (1)
- pessoa (1)
- echeipesh (1)
- chris-verclytte (1)
- rbreslow (1)
- davehodg (1)
- bizmate (1)
- miguelaferreira (1)
- damusix (1)
- joseguerrero (1)
Pull Request Authors
- hectcastro (6)
- miguelaferreira (6)
- tnation14 (6)
- rbreslow (6)
- athom (4)
- tvaughan77 (1)
- rv-drassakhatsky (1)
- chris-verclytte (1)
- bizmate (1)
- suharshan (1)
- nanotubing (1)
- linuxplayground (1)