Hi,

I have referred this docs.

Here you have mentioned below thing.

You cannot enable DNS resolution support for an inter-region VPC peering connection.

I am not sure that this is correct or not.

Because i have verified that i am able to resolve DNS in inter-region VPC peering connection.

But as per above docs, This option is disabled from console.

Please suggest me that either documentation is not currect or functionality mentioned is not implemented correctly.

Thanks!

referring to https://docs.aws.amazon.com/vpc/latest/peering/invalid-peering-configurations.html , Example: Edge to Edge Routing Through a VPN Connection or an AWS Direct Connect Connection
.
I am building some solution where it look like below image but I want to access VPC B from corporate network and also from VPC B to go back to corporate network through VPC A. As per the diagram there is VPC peering from VPC A and VPC B (pcx-aaaabbbb) but there is no VPC peering from VPC B to VPC A.

If I create a two way VPC peering VPC A ----> VPC B and then VPC B to VPC A .
Then can I access VPC B resources from corporate network ?
Can I access corporate network resources from VPC B too ?

Is it possible in any way , please add to document.

Also here in diagram it is mention corporate network is connecting using Hardware VPN or AWS Direct Connect Connection . If I use some software based VPN solution like AppGate SDP then Can I reach directly from corporate network to VPC B ?

Thanks
Sas

All:

I have reviewed the CoC and Contributing Guidelines, but I apologize if this is left in the wrong format.

1. First, there is an issue in the docs on GovCloud relating to VPC Links in API Gateway. In differences between API Gateway Commercial and API Gateway GovCloud, it doesn't mention that this feature is NOT available in GovCloud.

2. Second, which I am unable to find an answer for online, is why is there no API Gateway Github Repo, or anything related to GovCloud documentation on Github? Are there still service guides "in the pipeline"?

Thank you for reading this, and also for posting these docs on Github in the first place. Look forward to helping where I can in the future.