Skip to content
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

aws_instance parameter network_interfaces is missing! #5765

Closed
P13612 opened this issue Mar 21, 2016 · 2 comments
Closed

aws_instance parameter network_interfaces is missing! #5765

P13612 opened this issue Mar 21, 2016 · 2 comments

Comments

@P13612
Copy link

P13612 commented Mar 21, 2016

Hi,

in AWS CloudFormation you have in AWS::EC2::Instance a parameter NetworkInterfaces:

{
"Type" : "AWS::EC2::Instance",
"Properties" : {
.
.
"NetworkInterfaces" : [ EC2 Network Interface, ... ],
.
.
.
}
}
This Parameter is missing entirely in terraform/builtin/providers/aws/resource_aws_instance.go
This significantly limits how ENIs can be used.

aws_network_interface shows a code example:

resource "aws_network_interface" "myapp" {
subnet_id = "${aws_subnet.public_a.id}"
private_ips = ["10.0.0.50"]
security_groups = ["${aws_security_group.web.id}"]
attachment {
instance = "${aws_instance.test.id}"
device_index = 1
}
}

But ENI's may preferably be used the other way around. First an ENI is created with a private IP and then the instance is hooked to this ENI. This is always true when you try to setup an infrastructure with dedicated fixed private_ips. You first setup the ENIs and then the helpers like RDS databases and caches and they may no longer steel the IP's dedicated for the application instances.

This scenario can not be build with terraform right now. Can somebody add this, so one can write:

resource "aws_instance" "app" {
.
.
.
network_interfaces = [${aws_network_interface.myapp}]
.
.
.

Thanks

Peter

@grubernaut
Copy link
Contributor

Fixed via #12933

@ghost
Copy link

ghost commented Apr 13, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants