amazon web services - Can't attach 2nd interface to ec2 instance -


i've got 2 instances running nicely

web - t2.medium - us-east-1d - private ip - 10.1.1.6 vpn - t2.micro  - us-east-1d - eip assigned 

i'm trying add 2nd interface onto vpn server within 10.1.1.0/24 network.

after create interface can't attach vpn. web instance shows attach that's on internal network.

how can 2nd interface within 10.1.1.0/24 network onto vpn server?

vpc setup:

internal: cidr - 10.1.1.0/24      - us-east-1d (web server) vpn:      cidr - 192.168.247.0/24 - us-east-1d (vpn server) 

i've tried manage priv ip addresses on vpn server see if assign internal comes with:

"ip address not in subnet"

i need vpn server have 2 network interfaces: 1 public , 1 private/internal.

it looks you're trying assign ip isn't in subnet range. if instance in subnet-foo , subnet-foo us-east-1a 10.1.1.0/24 should work. fail instance if tried attach nic ip 10.0.1.6 in example. error message pretty specific ip address not in subnet cidr rang


Comments

Popular posts from this blog

elasticsearch python client - work with many nodes - how to work with sniffer -

angular - Is it possible to get native element for formControl? -

Upload file with tags through OwnCloud or NextCloud API -