-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
launch_template error when using new iam_instance_profile #5217
Comments
Had the same issue, the only workaround I found was to add a bit of delay after the creation of the launch template:
|
So it seems the retry handling added to the |
The fix here was actually in the |
The fix for this has been merged into master and will release with version 1.34.0 of the AWS provider, likely later today. |
Thanks @bflad! |
This has been released in version 1.34.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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! |
Community Note
Terraform Version
terraform version
Terraform v0.11.7
Affected Resource(s)
aws_iam_instance_profile
aws_launch_template
Terraform Configuration Files
Expected Behavior
Launch template created with IAM instance profile attached
Actual Behavior
Launch template fails to create on first run. Resources created successfully on second run.
aws_autoscaling_group.asg_router_app_c: Error creating AutoScaling Group: ValidationError: You must use a valid fully-formed launch template. Value (router_app_instance_profile) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name
status code: 400, request id: d43ab76e-89d4-11e8-b720-278140b97e98
Steps to Reproduce
terraform apply (x2)
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: