How to Import an AWS S3 Bucket Website Configuration into Terraform

Import AWS S3 Bucket Website Configuration with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Amazon S3 resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live AWS S3 Bucket Website Configuration to managed Terraform.

terraback scan all aws --region us-east-1

terraback aws import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = aws_s3_bucket_website_configuration.site
  id = "my-site-bucket"
}

Example aws_s3_bucket_website_configuration configuration

Here is a realistic AWS S3 Bucket Website Configuration block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "aws_s3_bucket_website_configuration" "site" {
  bucket = "my-site-bucket"

  index_document {
    suffix = "index.html"
  }

  error_document {
    key = "error.html"
  }
}

Gotchas when importing a AWS S3 Bucket Website Configuration

• Website hosting is a standalone resource in the modern provider; it imports separately from aws_s3_bucket by the bucket name.
• Static website hosting requires public read access, so it usually pairs with a relaxed aws_s3_bucket_public_access_block and a public bucket policy.
• Use either index_document/error_document or a redirect_all_requests_to block, never both in the same configuration.
• The S3 website endpoint differs from the REST endpoint and does not support HTTPS; front it with CloudFront if you need TLS.

Doing it manually with terraform import

The native approach is to write the aws_s3_bucket_website_configuration block by hand, then run terraform import aws_s3_bucket_website_configuration.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other AWS resources