marc:studie:hashicorp_terraform_certified_associate
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| marc:studie:hashicorp_terraform_certified_associate [2026/05/13 21:00] – [Providers] marcv | marc:studie:hashicorp_terraform_certified_associate [2026/05/14 11:01] (current) – marcv | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== HashiCorp Terraform Associate ====== | ====== HashiCorp Terraform Associate ====== | ||
| + | |||
| + | FIXME | ||
| + | |||
| + | Needed for terraform to provision on AWS: | ||
| + | The Terraform CLI (1.2.0+) installed. | ||
| + | The AWS CLI installed. | ||
| + | An AWS account and associated credentials that allow you to create resources in the us-west-2 region, including an EC2 instance, VPC, and security groups. | ||
| :!: __**Infrastructure as Code**__ is the practice of defining infrastructure deployments using machine-readable files that can be used to provision infrastructure in an automated fashion. | :!: __**Infrastructure as Code**__ is the practice of defining infrastructure deployments using machine-readable files that can be used to provision infrastructure in an automated fashion. | ||
| Line 127: | Line 134: | ||
| 12 ... | 12 ... | ||
| 13 }</ | 13 }</ | ||
| + | |||
| + | In this configuration we have already used two separate providers to create a single S3 bucket. The | ||
| + | Random provider gives us a random integer for naming the bucket and the AWS provider gives us | ||
| + | the S3 bucket resource. When using a provider it can be explicitly defined in a provider block, or | ||
| + | implied by the presence of a resource that uses the provider. | ||
marc/studie/hashicorp_terraform_certified_associate.1778698835.txt.gz · Last modified: by marcv
