### Terraform Version ```shell Terraform v1.9.8 on darwin_arm64 + provider registry.terraform.io/hashicorp/aws v5.72.1 ``` ### Terraform Configuration Files ```terraform terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 5.72.0" } } required_version = ">= 1.2.0" } provider "aws" { region = "us-east-1" } resource "aws_instance" "app_server" { ami = "ami-06b21ccaeff8cd686" instance_type = "t2.micro" tags = { Name = "JustWork" } } ``` ### Debug Output The relevant lines from: https://gist.github.com/bronius/5ade651801ca5ea6f6018602fb1548c3 are ``` 2024-10-22T16:35:32.975-0500 [DEBUG] provider: waiting for RPC address: plugin=.terraform/providers/registry.terraform.io/hashicorp/aws/5.72.1/darwin_arm64/terraform-provider-aws_v5.72.1_x5 2024-10-22T16:35:37.142-0500 [DEBUG] provider.terraform-provider-aws_v5.72.1_x5: Starting github.com/hashicorp/terraform-provider-aws@5.72.1 (go1.23.2)... ``` Notice the time gap between here is ~4 seconds. You'll see the same happen two more times in the linked gist. This adds 12 seconds to any terraform plan or apply command. TRACE did not add any additional detail between or nearly surrounding these lines. ### Expected Behavior The time gap between "provider: Waiting for RPC address:" and "provider.terraform-provider-aws_v5.72.1_x5: Starting github.com/hashicorp/terraform-provider-aws@5.72.1 (go1.23.2)..." is consistently 4 seconds every time on any network, but a coworker on the same network with a similar machine does not experience this. ### Actual Behavior The time gap following "provider: Waiting for RPC address:" should be negligible, in the milliseconds. ### Steps to Reproduce It does not matter what `main.tf` this runs, I just provided a very simple "should work anywhere" basic example grabbing an aws ami. 1. `terraform init` 2. `TF_LOG=DEBUG terraform plan` (of course, without logging, the delay still occurs, it just takes fully 12 seconds for the most basic plan/apply to run.) ### Additional Context This is unusual to me, and I seek to understand the problem better: Is it something with my work AWS account (a personal work sandbox)? Something about my machine? Some specific version of something on my machine? Other coworkers do not observe a similar delay, and I saw one's DEBUG log and saw only ~300ms delay on the line in question. ### References _No response_