How to Import an AWS Kinesis Data Firehose Delivery Stream into Terraform

Import AWS Kinesis Data Firehose Delivery Stream with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Amazon Kinesis Data Firehose resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live AWS Kinesis Data Firehose Delivery Stream 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_kinesis_firehose_delivery_stream.s3
  id = "arn:aws:firehose:us-east-1:123456789012:deliverystream/s3-stream"
}

Example aws_kinesis_firehose_delivery_stream configuration

Here is a realistic AWS Kinesis Data Firehose Delivery Stream block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "aws_kinesis_firehose_delivery_stream" "s3" {
  name        = "s3-stream"
  destination = "extended_s3"

  extended_s3_configuration {
    role_arn   = "arn:aws:iam::123456789012:role/firehose-role"
    bucket_arn = "arn:aws:s3:::my-firehose-target"
  }
}

Gotchas when importing a AWS Kinesis Data Firehose Delivery Stream

• Import by the delivery stream ARN, not just the stream name.
• The destination type (extended_s3, redshift, elasticsearch, http_endpoint, and so on) is immutable; changing it forces replacement.
• The IAM role, destination S3 bucket or OpenSearch domain, and any CloudWatch log group referenced are separate resources not imported with the stream.
• Secrets such as a Redshift password are never returned by AWS; pass them through variables to avoid a diff.

Doing it manually with terraform import

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