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.
10-23-2018 02:55 AM - edited 10-24-2018 11:21 AM
01-06-2019 12:36 AM - edited 01-16-2019 12:23 AM
01-06-2019 10:45 AM
This thread does not specify what is not working or what the exact problem is. There are multiple areas that Infoblox operates in for AWS and each feature may have its own solution, so there is no simple answer to provide here.
For DNS, the most common practice is to deploy an Infoblox appliance in a 'shared services' VPC and EC2 instances in other VPC's (even in separate accounts) would be able to resolve through the Infoblox appliance(s) as long as network connectivity works, such as when using basic routing or VPC peering.
For vDiscovery, you would need to create separate vDiscovery tasks per account. This can be simplified when multiple tasks must be created by using the API to create these, and you can find examples for this in our WAPI reference guide (https://www.infoblox.com/wp-content/uploads/infoblox-deployment-infoblox-rest-api.pdf).
If you are struggling with something else, or have a particular use case that you are concerned about, be sure to elaborate on that and I'm sure you can get the help that you are looking for. Infoblox Support will also be another helpful resource for you.
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.