Hello Experts, every document says NLB target IP can be any IP either from peered VPC or on -prem. However while testing I see no such option is available, it only gives options to choose IP from targeted VPC.![Screenshot ](https://repost.aws/media/postImages/original/IMF79369rPQ4u60P-RNXtTRw) In case no such option it gives you same functionality as instances option. is something got changed ?

NLB TARGET IP OVER PEERED VPC CONNECTION

Hello Experts, every document says NLB target IP can be any IP either from peered VPC or on -prem. However while testing I see no such option is available, it only gives options to choose IP from targeted VPC. Screenshot In case no such option it gives you same functionality as instances option. is something got changed ?

주제

네트워킹 및 콘텐츠 전송

태그

아마존 VPC 탄력적 로드 밸런싱

언어

English

rePost-User-1687975

질문됨 2년 전1733회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

수락된 답변

Hello,

That is definitely supported, please make sure to use 'IP Address' as a Target type when creating a Target group.

In the Register targets you would need to select 'Other private IP address' in the dropdown.

Enter image description here

전문가

Tushar_J

답변함 2년 전

전문가

Toni_S

검토됨 2년 전

rePost-User-1687975
2년 전
I exactly did the same and getting error "IP address must belong to an existing subnet" please check my screenshot it ask choose a network and only option is to define VPC & that does not make sense to me since I was trying to mention IP address from peer VPC which is not an option to choose.
Tushar_J 전문가
2년 전
Hello, I modified my answer and added 1 more screenshot, you need to select "Other IP address" in the dropdown for Register target. After that as long as Peering is setup properly, routing, SGs, NACL etc the Target should come Up healthy in NLB.
rePost-User-1687975
2년 전
Many thanks Tushar. Overlooked this option :)

NLB TARGET IP OVER PEERED VPC CONNECTION

관련 콘텐츠