Terraform-provider-aws: Kinesis stream bug in China AWS

[DanishKhakwani]

Terraform Version

Terraform v0.11.1

• provider.aws v1.10.0

Affected Resource(s)

• aws_kinesis_stream

Terraform Configuration Files

resource "aws_kinesis_stream" "kstream" {
  name             = "kstream"
  shard_count      = 64
  retention_period = 168

  shard_level_metrics = [
    "IncomingBytes",
    "OutgoingRecords",
    "IteratorAgeMilliseconds",
    "IncomingRecords",
    "ReadProvisionedThroughputExceeded",
    "WriteProvisionedThroughputExceeded",
    "OutgoingBytes"
  ]
}

When the above resource is applied, the following change keeps showing up on subsequent apply/plan.

  ~ aws_kinesis_stream.kstream
      encryption_type: "" => "NONE"

I have tried with both encryption_type defined and undefined (which should default to "NONE").

Expected Behavior

What should have happened?
No change

Actual Behavior

What actually happened?
1 to change

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply -target aws_kinesis_stream.kstream
2. terraform plan -target aws_kinesis_stream.kstream

NOTE: I am only seeing this on AWS China Account. Other regions are fine.

[bflad]

Bug fix pull request submitted: #4575

[bflad]

The fix for this will release with v1.20.0 of the AWS provider, likely later today. 👍

[ryanmaclean]

Fantastic news!

[bflad]

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

[hashibot[bot]]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!