anything they want to within Vault

ability to enable a secret engine at the path *

only make changes to policies

nothing, since the policy doesn ' t specify any specific paths

functions

workspaces

module registry

sentinel

Cluster Name

Replication

Seal Type

Auth Methods

Namespaces

Storage Backend

Audit Devices

place a space in between each line

type = " A "

ttl = " 300 "

zone_id = aws_route53_zone.primary.zone_id

align their equals signs

ami = " abc123 "

instance_type = " t2.micro "

place all arguments using a variable at the top

ami = var.aws_ami

instance_type = var.instance_size

subnet_id = " subnet-0bb1c79de3EXAMPLE "

tags = {

Name = " HelloWorld "

}

put arguments in alphabetical order

name = " www.pythonfanclub.com "

records = [aws_eip.lb.public_ip]

type = " A "

ttl = " 300 "

zone_id = aws_route53_zone.primary.zone_id

the backend is initialized and the working directory is prepped

creates an execution plan and determines what changes are required to achieve the desired state in the configuration files.

applies the changes required in the target infrastructure in order to reach the desired configuration

reconciles the state Terraform knows about with the real-world infrastructure

regular expressions

module

input parameters

output value

The local backend stores state on the local filesystem locks the state using system APIs and performs operations locally.

The local backend is the directory where resources deployed by Terraform have direct access to in order to update their current state

The local backend is how Terraform connects to public cloud services, such as AWS, Azure, or GCP.

The local backend is where Terraform Enterprise stores logs to be processed by a log collector