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.
04-08-2020 11:19 PM
Is there any benefit of placing servers in their own subnets based on purpose? e.g. Web, App and Database servers.
I can't see why I can't just have 1 public subnet and 1 private subnert with all servers being in the private and traffic controlled by security groups. Maybe I'm over thinking when trying to put each server in it's own subnet.
09-20-2020 10:56 PM - edited 09-23-2020 05:30 AM
I need to know What is the relation between an AWS VPC subnet and a route table?
whether we have to use NAT instance or NAT gateways to instances launched in private subnet to access the internet for software updates.
10-20-2020 11:11 PM
2 weeks ago - last edited a week ago
Back then, the AWS Management Console had fewer services, and I quickly that customers now need a way to connect from one VPC to another. The VPC owner will share subnets with other accounts that we call VPC participants. There is also a new Sharing tab where I can see my sharing status.