2

Ok, so our setup is as follows:

We have a VPC with some instances in them. For most of the traffic, we want to go back to our existing physical hosting centre and from there to the internet, with our nat'ed public ip. Since we are dependent on this ip to be whitelisted.

The remaining traffic needs to go through the local IGW, because it is high volume. Some of this is going to specific ips, so we have added those to the routing tables. The rest is going to other Amazon webservices, like Kinesis and DynamoDB. These services all have multiple ips associated with them and can change at the discretion of Amazon. This means that just resolving the dns locally and then adding it to the routing table won't work. At least not in a robust manner.

So is there any nice way of doing this?

Grubsnik
  • 918
  • 9
  • 25

1 Answers1

3

You can use services endpoints and route through it.

Thomas L.
  • 1,294
  • 9
  • 13
  • 1
    Seems like the only endpoints currently supported are S3. Doesn't solve my problem when struggling with Kinesis and DynamoDB – Grubsnik Jan 12 '16 at 10:10
  • AFAIK there is no other way to do it in a "nice way". VPC endpoints for other services are probably on the way though. – Thomas L. Jan 12 '16 at 13:46
  • If there is no other way, then patience is the only option. – Grubsnik Jan 13 '16 at 10:44