Hi Team,
We’re encountering intermittent issues during the deployment of bunch resources, including SNS, Lambda, Kinesis, Firehose, and IAM roles and policies, all from a single Terraform module.
Typically, the terraform plan command completes successfully in about 30 seconds. However, we’ve observed instances where it takes up to an hour, sometimes ending in success and other times in failure.
The inconsistent nature of this problem makes it difficult to pinpoint the cause. We’ve verified that system resource usage is well within normal limits. Despite analyzing Trace logs, we haven’t identified any specific errors related to this issue. Could you assist us in determining the potential cause?
Below are the versions of Terraform and providers we’re using:
Terraform: v1.0.11
AWS provider: v5.47.0
Archive: v2.2.0
Null: v3.1.1
We’ve also included some warning messages from the Trace logs that we suspect might shed light on the issue
[WARN] Provider “Terraform Registry” produced an invalid plan for aws_kinesis_stream.all_logs_stream[“xyz”], but we are tolerating it because it is using the legacy plugin SDK. The following problems may be the cause of any confusing errors from downstream operations: - .tags: planned value cty.MapValEmpty(cty.String) for a non-computed attribute - .enforce_consumer_deletion: planned value cty.False for a non-computed attribute - .stream_mode_details: block count in plan (1) disagrees with count in config (0)
[WARN] Provider “Terraform Registry” produced an invalid plan for aws_s3_bucket_lifecycle_configuration.eks_raw, but we are tolerating it because it is using the legacy plugin SDK. The following problems may be the cause of any confusing errors from downstream operations: - .expected_bucket_owner: planned value cty.StringVal(“”) for a non-computed attribute
Thanks