How to Use AWS Provider in Terraform: Syntax and Example

To use the aws provider in Terraform, declare it in your configuration with the provider block specifying the region and credentials. Then, Terraform can manage AWS resources using this provider configuration.

Syntax

The provider block tells Terraform which cloud service to use and how to connect. For AWS, you specify region and optionally credentials or profile. This setup allows Terraform to manage AWS resources in the chosen region.

terraform

provider "aws" {
  region  = "us-east-1"
  profile = "default"
}

Example

This example shows how to configure the AWS provider and create a simple S3 bucket. It demonstrates the basic setup and resource creation using Terraform with AWS.

terraform

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 4.0"
    }
  }
}

provider "aws" {
  region = "us-east-1"
}

resource "aws_s3_bucket" "example" {
  bucket = "my-unique-bucket-terraform-12345"
  acl    = "private"
}

Output

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Common Pitfalls

Common mistakes include not setting the region, missing credentials, or using an already taken S3 bucket name. Also, forgetting to initialize Terraform with terraform init can cause errors.

Always ensure your AWS credentials are configured via environment variables, shared config files, or explicitly in the provider block (not recommended for security).

terraform

provider "aws" {
  # Missing region causes errors
  # region = "us-east-1"
}

# Correct way
provider "aws" {
  region = "us-east-1"
}

Quick Reference

• provider "aws": Declares AWS as the cloud provider.
• region: AWS region to deploy resources.
• profile: Optional AWS CLI profile name.
• terraform init: Initializes Terraform and downloads providers.
• terraform apply: Applies the configuration to AWS.

Key Takeaways

Always declare the AWS provider with a region in your Terraform config.

Use terraform init to download the AWS provider before applying.

Avoid hardcoding credentials; use AWS profiles or environment variables.

Ensure resource names like S3 buckets are globally unique to prevent errors.

Check for missing region or credentials if Terraform cannot connect to AWS.