Interested more on the On-Premises and AWS part, internally we are working on starting to use queue services from the cloud and integrate them into our daily operations. I think this post will serve us as a good introductory to connecting both ends...
Else you can make your entire services in AWS public so routing does not go through the VPN, but that's not recommended...
Of course if you route everything through the public internet layer, you are not doing anything good to your business security measures. That shouln't be a considered option, not even the last one in the list.
You can use a Direct Connect [1] option if you want a dedicated connection between your data center and AWS. Its more secure, but more hard-to-maintain and a bit more costly than VPN option.
Else you can make your entire services in AWS public so routing does not go through the VPN, but that's not recommended...