<- All Blueprints
Customizable templates for deploying cloud infrastructure

AWS VPC

This blueprint creates an AWS VPC with best practices in mind, such as enabling DNS support and hostnames by default to facilitate resource naming and resolution within the VPC. It sets a default CIDR block of "10.0.0.0/16" but allows customization to suit different network requirements. The blueprint encourages the use of tagging for better resource management and organizes variables into groups to assist users who may not be cloud infrastructure experts.

Define and customize Blueprints to set what infrastructure configuration options are available to developers.

---
constants:
  __name: "{{ name }}_{{ __guid }}"
variables:
  name:
    desc: "Name of the VPC."
    required: true
    group: VPC Details
  cidr_block:
    desc: "The CIDR block for the VPC."
    required: true
    group: VPC Details
    default: "10.0.0.0/16"
  instance_tenancy:
    desc: "Tenancy option for instances launched into the VPC."
    required: false
    group: VPC Details
    default: "default"
    suggested: "default"
  enable_dns_support:
    desc: "Enable DNS support in the VPC."
    required: false
    group: DNS Settings
    default: true
  enable_dns_hostnames:
    desc: "Enable DNS hostnames in the VPC."
    required: false
    group: DNS Settings
    default: true
  tags:
    group: Tags
    required: false
groups:
  VPC Details:
    order: 1
    desc: "Basic details for the VPC."
  DNS Settings:
    order: 2
    desc: "DNS settings for the VPC."
  Tags:
    order: 3
    desc: "Tags to assign to the VPC."
---

resource "aws_vpc" "__name" {
  cidr_block           = {{ cidr_block }}
  instance_tenancy     = {{ instance_tenancy }}
  enable_dns_support   = {{ enable_dns_support }}
  enable_dns_hostnames = {{ enable_dns_hostnames }}

  tags = {
    Name = {{ name }}
    {{# tags }}
      {{ tags.key | required: false }} = {{ tags.value | required: false }}
    {{/ tags }}
  }
}

// DNS support and hostnames are enabled by default for better resource naming and resolution.
// The CIDR block defaults to "10.0.0.0/16" but can be customized.
// Tags are encouraged for resource identification and management.
//
A form is created automatically that accepts inputs that you defined in the Blueprint.
After filling out the Blueprint form, Terraform is generated and a PR is automatically submitted.
What am I looking at?

Talk to a Human

See Resourcely in action and learn how it can help you secure and manage your cloud infrastructure today!