provider
A plugin that teaches Terraform how to talk to one API, such as AWS or your local disk, and which resource types it offers.
In more detail
Terraform itself knows no clouds; every resource type, such as aws_vpc or local_file, comes from a provider. Providers are written by vendors or the community, published to a registry, declared in required_providers and downloaded per directory by terraform init. The provider's registry documentation is the reference for which arguments each resource accepts.
Example
provider "aws" {
region = "eu-west-2"
}Related terms
- Terraform — An infrastructure-as-code tool from HashiCorp that creates and changes cloud resources such as servers, networks and databases from configuration files.
- API — A defined way for one program to ask another program to do something, such as a list of web requests a service accepts.
- plugin — An add-on package that extends a tool with extra features without changing the tool itself.
- required_providers — The block inside the terraform block that lists each provider a configuration needs, where to download it from and which versions are acceptable.
- provider block — A top-level block that configures a provider, for example which region or endpoint it talks to and which credentials it uses.
- Terraform Registry — HashiCorp's public website where providers and reusable modules are published, with the documentation for each.
- Terraform Core — The Terraform program itself, which handles the language, the graph, state and the workflow but knows nothing about any cloud.
Taught in
- Users, Groups and Roles — Cloud Infrastructure & Hyperscaler Architecture
- Subnets: Public and Private — Cloud Infrastructure & Hyperscaler Architecture
- Infrastructure as Code (Handover to Terraform) — Cloud Infrastructure & Hyperscaler Architecture
- What Is Infrastructure As Code? — Infrastructure as Code with Terraform
- Installing Terraform And Meeting The CLI — Infrastructure as Code with Terraform
- Providers And The required_providers Block — Infrastructure as Code with Terraform
- Writing Your First Configuration In HCL — Infrastructure as Code with Terraform
- Initialising The Working Directory — Infrastructure as Code with Terraform
- Predicting Changes, Then Applying Them — Infrastructure as Code with Terraform
- Functions And Expressions In HCL — Infrastructure as Code with Terraform
- Querying Existing Infrastructure With Data Sources — Infrastructure as Code with Terraform
- Why Modules: Composition Versus Monoliths — Infrastructure as Code with Terraform
- The Terraform Registry And Public Modules — Infrastructure as Code with Terraform
- Running Terraform In CI — Infrastructure as Code with Terraform
- Provider Mocking For Tests — Infrastructure as Code with Terraform
- The Plan That Wanted To Destroy Production — HashiCorp Terraform Associate (004) Exam Prep
- One Hour, No Weights Published — HashiCorp Terraform Associate (004) Exam Prep
- Infrastructure As Code, And One Workflow For Every Platform — HashiCorp Terraform Associate (004) Exam Prep
- Providers: How Terraform Reaches Every API — HashiCorp Terraform Associate (004) Exam Prep
- Versions, The Lock File And Provider Aliases — HashiCorp Terraform Associate (004) Exam Prep
- State: Terraform's Memory Of What It Built — HashiCorp Terraform Associate (004) Exam Prep
- Write, Plan, Apply, And What Init Prepares — HashiCorp Terraform Associate (004) Exam Prep
- Reading A Plan, Saving It, Applying It — HashiCorp Terraform Associate (004) Exam Prep