You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would be nice if we can provide our own elasticIP while creating a nat gateway. Since elastic IPs are very valuable for some organizations, losing them is difficult (whitelisting issues).
We completely stopped managing elasticIP through any automation tools since it leads to accidental releases. Would be nice if the same can be achieved here.
The text was updated successfully, but these errors were encountered:
* support using existing elastic ips
closes#42
* add test content to main.tf and enable nat gateway
* use custom test file for existing-ips example
* use existing eips feature for NAT gateway and instance
* add nat instance ips to nat_ips output
* correct reference to existing_nat_ips
* use separate count variable for eip resources
* update README
* rebase and update docs again
* terraform fmt, address missing conflict
* remove duplicate local declaration
* remove duplicate import of eips
* correct README template after rebase
during rebase wrong side was accepted to resolve a conflict in 9cf2a85
* remove unrelated description part
nat_gateway_public_ips represent public ec2 ip addresses
Would be nice if we can provide our own elasticIP while creating a nat gateway. Since elastic IPs are very valuable for some organizations, losing them is difficult (whitelisting issues).
We completely stopped managing elasticIP through any automation tools since it leads to accidental releases. Would be nice if the same can be achieved here.
The text was updated successfully, but these errors were encountered: