[Enhancement]: Support Timestream for InfluxDB

[sentros]

Description

It's now possible to select a different engine for a Timestream database in the aws console. The previous engine is now called LiveAnalytics and a new engine was added called InfluxDB. Terraform has no support for the InfluxDB engine or for its configuration options.

If you plan to add the new engine as an option to the pre existing aws_timestreamwrite_database you could just add new parameters for it as shown in the example. At least the parameter group needs its own new resource.

Not much is shared between the engines so maybe a whole new resource for InfluxDB type Timestream would be better. For example the RDS resource handles engine types all in the same resource but RDS engine types at least share some configuration options between them as opposed to Timestream for LiveAnalytics vs InfluxDB.

Affected Resource(s) and/or Data Source(s)

• aws_timestreamwrite_database

Potential Terraform Configuration

resource "aws_timestreamwrite_database" "example" {
  database_name = "database-example"
  engine        = "influxdb"

  db_name           = "db-name-example"
  username          = "example-username"
  password          = "example-password"
  organization_name = "example-org"
  bucket_name       = "example-bucket"

  instance_class    = "db.influx.medium"
  storage_type      = "included-3000"
  allocated_storage = 200
  multi_az          = true

  db_subnet_group_name   = aws_db_subnet_group.example.name
  vpc_security_group_ids = [aws_security_group.example.id]
  publicly_accessible    = false

  parameter_group_name = aws_timestreamwrite_parametergroup.example.name
  s3_logs_location     = aws_s3_bucket.example.id

  tags = {
    Name = "value"
  }
}

resource "aws_timestreamwrite_parametergroup" "example" {
  name        = "example-name"
  description = "example-description"

  parameter {
    name  = "flux-log-enabled"
    value = "TRUE"
  }

  parameter {
    name  = "log-level"
    value = "error"
  }

  tags = {
    Name = "value"
  }

}

References

• Announcement
• Blog post
• Developer Guide
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/timestreamwrite_database

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[ewbankkit]

At the API level Timestream for InfluxDB is a distinct service.
Following our naming guidelines the first resource should be:

resource "aws_timestreaminfluxdb_db_instance" "example" {
  name = "..."
}

[trevorbonas]

I would like to work on this issue.

[trevorbonas]

I am working on the aws_timestreaminfluxdb_db_instance resource and will provide updates in the coming weeks.

So far, my implementation differs in a few ways from the proposed implementation.

• I will not be creating an aws_timestreaminfluxdb_provider_group resource.

  • Provider groups cannot currently be deleted. To avoid swamping users with unnecessary errors, a provider group ID can be used as an argument for an aws_timestreaminfluxdb_db_instance resource; users will have to create this provider group themselves, without Terraform.

• S3 log buckets will follow the format defined by AWS SDK Go V2. Instead of providing an S3 bucket ID for logging, users will provide the following:

  log_delivery_configuration {
      s3_configuration {
          bucket_name = aws_s3_bucket.example.bucket
          enabled = true
      }
  } 
  

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.61.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.