When connecting a customer gateway to a VPC VPN, what hardware or software is providing the service on Amazon's side?
closed as off topic by RobM, joeqwerty, Smudge, sysadmin1138♦ Feb 9 '12 at 19:12
Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.
That should be none of your concerns actually ;)
I'm not trying to be mean here, but in a proper Service-oriented Architecture (SOA) you should only need to know respective contracts/interfaces/protocols to obey, alongside some Service-level Agreement (SLA) eventually.
In addition, Amazon is notoriously secretive about the actual hardware in use, e.g. many have speculated about this regarding the Amazon Elastic Compute Cloud (Amazon EC2) and they have never specified it in other than comparative terms, e.g. their EC2 Compute Unit (ECU) is defined as:
You might try to deduce the Amazon Virtual Private Cloud (VPC) hardware accordingly via the information in Customer Gateway Devices We've Tested and the respective Requirements for Your Customer Gateway, which is the closest indication available I think. Further, you might want to have a look at A Detailed View of the Customer Gateway and an Example Configuration, which includes an architecture diagram.
Most notably, Amazon VPC requires support for establishing Border Gateway Protocol (BGP) peerings:
Unfortunately BGP is not implemented in many consumer-level VPN devices, thus requires respective professional hardware or software VPN appliances.
AWS has just dropped the requirement to establish Border Gateway Protocol (BGP) peerings in order to use the built in VPN connectivity to an Amazon Virtual Private Cloud (VPC), see Amazon VPC - Additional VPN Features:
The outlined reason for this change specifically highlights BGP as a previous barrier to adoption of this otherwise very appealing VPN connectivity to a VPC:
I couldn't agree more, accordingly I'm looking forward to facilitate this built in VPN connectivity in a lot more commonly encountered scenarios.
I asked in a premium support ticket.
Their response was that the policy was not to disclose the information and, regardless, that the support department was not privy to all of the technical details - the VPC knowledge is kept by the VPC team.
Anecdotally, they suggested it was currently (as of Q1 2012) high-end branded gear/software rather than anything bespoke.