-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Allow External Instances Attached to EIP #2952
Comments
Hey @stack72 –
In your example, your EIP already has a
(From AssociateAddress API docs) Oddly enough, I tried it and I don't get an error... do you see something I don't? |
@catsby when my instance comes up, it bascially attaches itself to the ENI. I am not attaching it to the EIP at all. But terraform believes it is attached at that point and tries to remove it My user_data script works as follows:
|
Ah... so when you attach it to the ENI (which is using the EIP), the EIP gets the instance associated with it. I just tested that out to confirm. Thanks for the follow up! I'll make the update and send a PR |
you got it :) Look forward to testing the follow up |
@catsby any idea if this can be merged? |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
As per #2943
When we attach an instance to an EIP, terraform currently tries to destroy it:
My code works as follows:
When an instance comes up, it attaches itself to the ENI (thanks to the PR above, that stays). But it looks like the EIP is removing itself on the second run:
The text was updated successfully, but these errors were encountered: