DOCSEARCHbyAlgolia
Submit Docs

terraform-aws-modules/terraform-aws-security-group

repository·master·Indexed 20 days ago

https://github.com/terraform-aws-modules/terraform-aws-security-group

An AWS Security Group Terraform module providing a flexible and structured way to manage EC2 security groups and their ingress/egress rules within a VPC. It includes specialized submodules for services such as ActiveMQ, Alertmanager, and Carbon Relay, featuring curated preset ingress rules for common protocols.

Tokens
111.4K
Snippets
213
Records
423
Agent score
68%

What's inside terraform-aws-security-group

  1. What is the Loki module wrapper

    master
    The wrappers/loki directory implements a single module wrapper pattern. This pattern is designed for scenarios where using native Terraform for_each is not feasible, such as when using Terragrunt. It allows you to manage multiple instances of a module within a single configuration file (e.g., a single terragrunt.hcl) without duplicating files for every resource. The wrapper itself does not add new functionality; it simply facilitates the bulk management of module instances via defaults and items blocks.

  2. What is the etcd module wrapper

    master

    The etcd wrapper is a pattern used to manage multiple instances of a module within a single configuration. This is particularly useful in environments like Terragrunt where native Terraform for_each logic might not be feasible for managing multiple resources without duplicating configuration files.

    Note: This wrapper does not add any new functionality; it simply provides a structure to pass a map of items and a set of default values to the underlying module.

  3. What is the Zipkin module wrapper

    master
    The wrappers/zipkin directory implements a single module wrapper pattern. This pattern is designed to manage multiple instances of a module within a single configuration. It is particularly useful in environments like Terragrunt where using native Terraform for_each might not be feasible, allowing you to manage several resources without duplicating configuration files for every instance.

  4. What is the Wazuh module wrapper and when to use it

    master

    The wrappers/wazuh directory provides a module wrapper pattern designed to manage multiple instances of the modules/wazuh module within a single configuration block.

    This pattern is specifically useful in environments where native Terraform for_each logic is not feasible or desired, such as when using Terragrunt. It allows you to manage several copies of a module using a single configuration file (like terragrunt.hcl) instead of duplicating files for every individual resource instance.

  5. What is the Grafana module wrapper?

    master

    The wrappers/grafana directory implements a single module wrapper pattern. This pattern is designed for scenarios where using native Terraform for_each is not feasible (such as with Terragrunt) but you still need to manage multiple instances of a module within a single configuration file.

    This wrapper does not add new functionality; it simply provides a way to pass a map of items and a map of defaults to the underlying module to facilitate bulk management of resources.

  6. What is the Promtail module wrapper?

    master
    The wrappers/promtail directory implements a single module wrapper pattern. This pattern is designed to manage multiple instances of a module within a single configuration block. This is particularly useful in environments like Terragrunt where using native Terraform for_each might not be feasible, or when you want to manage multiple resources using a single configuration file without duplicating terragrunt.hcl files for every instance.

  7. What is the Solr module wrapper?

    master
    The wrappers/solr directory implements a single module wrapper pattern. This pattern is designed to manage multiple instances of a module within a single configuration block. This is particularly useful in environments like Terragrunt where native Terraform for_each logic might not be feasible for managing multiple distinct resource copies without duplicating configuration files.

  8. What is the Saltstack module wrapper

    master
    The Saltstack wrapper is a implementation of the 'single module wrapper pattern'. It is designed to allow managing multiple instances of a module within a single configuration block. This is particularly useful in environments like Terragrunt where using the native Terraform for_each feature might not be feasible or where you want to manage multiple resources without duplicating terragrunt.hcl files for every single instance.

  9. What is the ActiveMQ module wrapper

    master
    The wrappers/activemq directory implements a single module wrapper pattern. This pattern allows you to manage multiple instances of the modules/activemq module within a single configuration block. This is particularly useful in environments like Terragrunt where native Terraform for_each logic might not be feasible for managing multiple resource copies without duplicating configuration files.

  10. What is the Splunk module wrapper and when to use it

    master

    The wrappers/splunk directory implements a single module wrapper pattern. This pattern allows you to manage multiple instances of a module within a single configuration block. This is particularly useful in environments like Terragrunt where using native Terraform for_each logic might not be feasible or desired for managing multiple resource copies.

    Note that this wrapper does not add any new functionality; it simply provides a way to pass a map of items to the underlying module to create multiple resources.

  11. What is the Redshift module wrapper

    master

    The wrappers/redshift directory implements a single module wrapper pattern. This pattern is designed to manage multiple instances of a module within a single configuration block. This is particularly useful in environments like Terragrunt where using native Terraform for_each might not be feasible or where you want to manage multiple resources without duplicating terragrunt.hcl files for every instance.

    Note that this wrapper does not implement any additional logic or functionality beyond providing this orchestration pattern; it simply passes arguments through to the underlying module.

  12. What is the LDAP module wrapper and when to use it

    master

    The wrappers/ldap directory implements a single module wrapper pattern. This pattern is designed to manage multiple instances of a module within a single configuration block. This is particularly useful in environments like Terragrunt where using the native Terraform for_each feature might not be feasible or where you want to manage multiple resources using a single configuration file without duplicating terragrunt.hcl files for every instance.

    Note that this wrapper does not implement any additional logic or functionality beyond providing this structural pattern for the underlying modules/ldap module.