How to Import an AWS S3 Bucket Encryption into Terraform

Import AWS S3 Bucket Encryption 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 Encryption 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_server_side_encryption_configuration.assets
  id = "my-app-assets"
}

Example aws_s3_bucket_server_side_encryption_configuration configuration

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

resource "aws_s3_bucket_server_side_encryption_configuration" "assets" {
  bucket = "my-app-assets"

  rule {
    apply_server_side_encryption_by_default {
      sse_algorithm = "aws:kms"
      kms_master_key_id = "arn:aws:kms:us-east-1:123456789012:key/1234abcd-12ab-34cd-56ef-1234567890ab"
    }
    bucket_key_enabled = true
  }
}

Gotchas when importing a AWS S3 Bucket Encryption

• Encryption is a standalone resource in the modern provider; it imports separately from aws_s3_bucket by the bucket name.
• Buckets now have SSE-S3 (AES256) on by default, so even an untouched bucket may import with an encryption configuration present.
• sse_algorithm aws:kms requires kms_master_key_id; sse_algorithm AES256 must not set a key.
• Enable bucket_key_enabled with KMS to cut request costs; if it was on in the console, set it here or expect a diff.

Doing it manually with terraform import

The native approach is to write the aws_s3_bucket_server_side_encryption_configuration block by hand, then run terraform import aws_s3_bucket_server_side_encryption_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