Fixed
Status Update
Comments
am...@google.com <am...@google.com> #2
Hello
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through
I recommend you to
I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you
da...@britepayments.com <da...@britepayments.com> #3
Can we reopen this?
I'm facing a similar issue.
* App Engine Standard with VPC Connector, all-traffic setting and CloudNAT to provide egress traffic.
* Cloud Function Gen2 with exact same VPC Connector
using anything but `all` ingress setting on Cloud Function results in a 403.
I'm facing a similar issue.
* App Engine Standard with VPC Connector, all-traffic setting and CloudNAT to provide egress traffic.
* Cloud Function Gen2 with exact same VPC Connector
using anything but `all` ingress setting on Cloud Function results in a 403.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
When using App Engine Standard with Java 11, it is not possible to trigger a function that only allows traffic from the same VPC network.
What you expected to happen:
- To be able to trigger the function
Steps to reproduce:
- Use App Engine Standard with Java 11
- Create a VPC Access Connector to trigger a Cloud Functions function that only allows traffic from the same VPC network from App Engine Standard
- Receive 403
Other information (workarounds you have tried, documentation consulted, etc):
- We tried to create a VPC Access Connector [1] to achieve it but it is not possible because requests must use the external address of your serverless service. [2]
- It is possible to connect App Engine or Cloud Functions to other resources but not between them. [3]
[1]
[2]
[3]