HashiCorp Developer Documentation

website·Indexed 20 days ago

https://developer.hashicorp.com/consul/docs/connect/

Technical documentation and validated patterns for HashiCorp products, including Consul, Packer, Boundary, and Terraform. Covers topics such as service mesh gateways, KV store management, container registry patterns for AWS, Azure, and GCP, and infrastructure automation using Consul-Terraform-Sync (CTS).

Tokens
7.8M
Snippets
31.8K
Records
55.3K
Agent score
0%

What's inside HashiCorp Developer

  1. Overview of Consul JWT Authentication Method

    The jwt auth method (available in Consul 1.8.0+) allows users or applications to authenticate with Consul by providing a JSON Web Token (JWT) directly. This is a headless, machine-oriented login process that requires no browser interaction, making it ideal for VMs or containers where a JWT is already provided. It differs from the oidc method, which is designed for human-oriented interactive login via a browser and is only available in Consul Enterprise.
  2. Overview of the Amazon instance-store builder

    v1.0.1

    The amazon-instance builder creates Amazon AMIs backed by instance storage as the root device. It works by launching an EC2 instance from an existing instance-storage backed AMI, provisioning it, and then bundling it into a new AMI within the user's AWS account.

    Key constraints and requirements:

    • Windows Support: Instance builds are not supported for Windows; use the amazon-ebs builder instead.
    • Tooling: The Amazon EC2 AMI Tools must be installed on the machine being built (e.g., via a provisioner) before the builder finishes.
    • Resource Management: The builder creates temporary key pairs and security groups (prefixed with packer by default) to facilitate the build. It does not manage the resulting AMI after creation.
    # Builder Type
    type = "amazon-instance"
    # Builder ID
    id = "mitchellh.amazon.instance"
  3. Overview of Vault Integrated Raft Storage

    Integrated storage is a built-in storage option for Vault that provides high availability, backup/restore workflows, and Enterprise replication features without requiring third-party systems. It uses the Raft consensus protocol to ensure CAP consistency. Performance is primarily bound by disk I/O and network latency.
  4. Overview of the WordPress Nomad Pack

    The WordPress Nomad Pack provides a service job that deploys WordPress, MariaDB, and phpMyAdmin on a single Nomad client using the Docker driver. It utilizes Consul Connect for service-to-service communication via sidecar proxies and employs Nomad Host Volumes for MariaDB state persistence. By default, Consul service registration and health checks are enabled for WordPress and phpMyAdmin, while MariaDB only has service registration enabled.
  5. Overview of the Amazon instance-store builder

    v1.3.7

    The amazon-instance builder creates Amazon AMIs backed by instance storage as the root device. It works by launching an EC2 instance from an existing instance-storage backed AMI, provisioning it, and then bundling it into a new AMI within the user's AWS account.

    Key constraints and behaviors:

    • Windows Support: Instance builds are not supported for Windows; use the amazon-ebs builder instead.
    • Dependencies: The Amazon EC2 AMI Tools must be installed on the machine (e.g., via a provisioner) before the builder finishes.
    • Resource Management: Packer creates temporary key pairs and security group rules (prefixed with packer by default) to access the instance. It does not manage the resulting AMI after creation.

    Builder Details:

    • Type: amazon-instance
    • BuilderId: mitchellh.amazon.instance
  6. Overview of the Nomad Virt task driver

    The Virt task driver (name: virt) allows Nomad to run and manage virtual machines by utilizing the libvirt API and hypervisors such as QEMU. It supports core Nomad features including workload identity, task templates, and service discovery.

    Warning: This driver is currently a Beta feature under active development and is not recommended for use in production environments.