In order to connect via AWS Direct Connect, a provider needs to have a permanent connection between themselves and Amazon. These are provided by the companies listed in "AWS Direct Connect Solution Providers" ("ADSCP") for Northern VA, e.g. IX Reach, Abovenet, Equinix, etc.
So the 'middlemen' between you and AWS are:
You - Hosting Provider - ADSCP - AWS
Your Hosting Provider would have to have enough business, or potential business, to justify having a direct connection to ADSCP to reach AWS instances.
In order for them to multiplex the service for you, they would either have to strike a deal with AWS to allow them to dynamically connect your instance to their pipe (AWS doesn't do one-offs, and this is not a product, yet), or they'd have to dedicate the cross-connect to a connection with AWS in your name that would do this.
The cost of a cross connect from most providers is on the order of $250/mo.
So you would have to bear the cost of the cross connect to the ADSCP, in addition to your monthly hosting costs.
Most managed hosting proviers are going to figure that customers spending $250-$1k per month, are not going to be so excited to spend an extra 25-100% to connect to Amazon.
I can see why you'd want to do this, and I think we'll be able to someday.
If you want to, you can rent a cabinet for $1k/mo, put power in for $500/mo, and get a gig-e to the internet for $2k/mo and an AWS connection via an ADSCP for ~$250/mo. Then you can put your server in there for free and connect up.
Point is, for as "little" as $1750/mo, you could do this yourself by colocating with the ADSCP.
Alternatively, one could offer a multiplexed connection to AWS via an ADSCP, then route the traffic from within Amazon.
Bottom line, the fixed costs for doing this probably higher than justified for most people with a single server.
This analysis does not include the per-hour AWS Direct Connet costs, which are marginally fixed per usage without regards to infrastructure scale.
Here's why:
In order to connect via AWS Direct Connect, a provider needs to have a permanent connection between themselves and Amazon. These are provided by the companies listed in "AWS Direct Connect Solution Providers" ("ADSCP") for Northern VA, e.g. IX Reach, Abovenet, Equinix, etc.
So the 'middlemen' between you and AWS are:
You - Hosting Provider - ADSCP - AWS
Your Hosting Provider would have to have enough business, or potential business, to justify having a direct connection to ADSCP to reach AWS instances.
In order for them to multiplex the service for you, they would either have to strike a deal with AWS to allow them to dynamically connect your instance to their pipe (AWS doesn't do one-offs, and this is not a product, yet), or they'd have to dedicate the cross-connect to a connection with AWS in your name that would do this.
The cost of a cross connect from most providers is on the order of $250/mo.
So you would have to bear the cost of the cross connect to the ADSCP, in addition to your monthly hosting costs.
Most managed hosting proviers are going to figure that customers spending $250-$1k per month, are not going to be so excited to spend an extra 25-100% to connect to Amazon.
I can see why you'd want to do this, and I think we'll be able to someday.
If you want to, you can rent a cabinet for $1k/mo, put power in for $500/mo, and get a gig-e to the internet for $2k/mo and an AWS connection via an ADSCP for ~$250/mo. Then you can put your server in there for free and connect up.
Point is, for as "little" as $1750/mo, you could do this yourself by colocating with the ADSCP.
Alternatively, one could offer a multiplexed connection to AWS via an ADSCP, then route the traffic from within Amazon.
Bottom line, the fixed costs for doing this probably higher than justified for most people with a single server.
This analysis does not include the per-hour AWS Direct Connet costs, which are marginally fixed per usage without regards to infrastructure scale.
-alan