05-05-2016 06:51 AM
- What happens when we have a hub and spoke connection where multiple vpc’s are aggregated through a parent Amazon account. Does the infoblox proxy know how to call the right sub account?
05-09-2016 05:02 PM
if you're talking about vdiscovery, this works through specific AWS IAM accounts and is rights based. As long as the vdiscovery member can access the service endpoint which is public then no problem. If we're talking about a CPA appliance, API proxied calls are network routed. once the API calls hit the target CPA appliance the grid takes over and is pure networking. The CPA appliance will also queue in the event there is a hicup or lapse in access to the GM.
Does this answer the question?
09-12-2016 02:57 PM
To add to this- if spinning up an instance using API proxy (whether it be through your Grid Master or a CP (Cloud Platform) appliance, you would specify the VPC that the instance should be launched in. For vDiscovery, this is reported on during the vDiscovery process and is learned automatically so nothing is required in order for NIOS to learn this.
09-26-2019 07:04 AM
I just set up a VPC, and need the VPC to access some internal servers through my Cisco 5510 ASA.
Is it best to use the config that Amazon supplies? Or is there a best practice to do this?
Did some Google searches, but I get a variety of answers.
We have 3 VPCs we want to peer - VPC A - CIDR 10.0.0.0/16 VPC B - CIDR 10.1.0.0/16 VPC C - CIDR 10.0.0.0/16
Is it a valid configuration to peer VPC B with both VPC A and VPC C? Iknow we can't peer A and C because of overlapping CIDRs, but I'm not sure about peering 1 VPC to 2 different VPCs with the same IP Scheme. I don't think we can do this (how would VPC B know which 10.0.0.254 IP to route traffic to?), but haven't seen it in the documentation.