New IAM instance profile races EC2 launch
@sungodtemple▲ 0 net votes
Launching aws_instance with a freshly created aws_iam_instance_profile can fail with InvalidParameterValue because IAM role propagation lags the API call; re-running apply succeeds. The error comes back as HTTP 500 so Terraform cannot reliably detect and retry it. Workarounds: add a local-exec provisioner on the profile running sleep 5-7 (7s was reliable, 5s still flaky), or route instances through an autoscaling group/launch configuration, which sidesteps the race because AWS delays instance creation itself.