-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
InvalidParameterException: The new ARN and resource ID format must be enabled to propagate tags. Opt in to the new format and try again. #39
Comments
Please note that I use AWS account with precreated VPC and Subnets (I cannot recreate these as per security here. Also I followed this guide and make changes by enabling checkboxes as per image: I deleted manually the cluster an d trying again, but same error. Not sure what is or not wrong here. |
@archenroot |
@aknysh - I see, thing is I don't have root account, so I used my own which is admin, but has some restrictions, and I enabled new format as per guide, but after creating new cluster same error occurs. I am on our dev environment, so no need for migration here, I just play around here... |
@aknysh - do you know how to switch via aws cli? I didn't find it. Actually problem is that for console I have other user than for terraform, so will need to configure it via cli. My domain account is integrate3d with AWS for console access, while for non-console access we use IAM users. |
sry - found it : https://docs.aws.amazon.com/cli/latest/reference/ecs/put-account-setting.html Thx for feedback. |
Actually I tried following:
After terraform destroy and terraform apply the issue still persist... The profile is the same as I use with terraform. |
@aknysh - Can I temporarily disable this resource from your module? or is it some dependency for other functionality? |
Ok, I am waiting for migration, I analyzed module and this tagging is core requirement for module as how it is designed, anyway, thx for response again. |
Ok, so there is bad request issue:
|
I think when we opted in on global level via ROOT, something is running in background and need to recreate all roles in IAM, etc. so maybe the task need some time for propagation. |
I think I found the issue, I can tag the ECS itself, but the issue happens (after we enabled opt-in from root account globally) with ECS service creation. Following is resosource to be created:
Then SDK use this object to call:
So actually ECS is created with Tags without issue, but ECS Service cannot be tagged I think I will report this to Terraform AWS provider. |
So as stated on above linked issue, we had to update user which was created before root account opted-in with long arns. After change it works as expected. |
I am getting this error with latest Terraform 0.12:
The text was updated successfully, but these errors were encountered: