Status Update
No update yet.
Comments
ka...@google.com
on...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback. Thank you for your understanding and collaboration.
Thanks & Regards,
Ashalatha
Google Cloud Support
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
One customer outside the service perimeter of Cloud logging for a project has sufficient permission for their organization and is asked by a person inside the service boundary to troubleshoot VPC SC.
That time they have error message
"An error occurred when fetching the log response. This can occur when the project resource selected is wrong or the log entry unique ID is outdated"
How this might work:
This Customer thought they could get the reason why the VPC SC issue happens/violated. Even they were outside of the perimeter.
If applicable, reasons why alternative solutions are not sufficient:
Organization users who are outside of perimeter should be better to acknowledge the VPC trouble issue when they use the troubleshooter.
Other information (workarounds you have tried, documentation consulted, etc):
Steps to reproduce:
Create the Access level with an IP address.
Create the VPC SC perimeter with this IP address. prohibit access when the cloud logging API is used from outside of this IP address.
Try to access the project cloud logging under this IP address. ( then we can get the vpcServiceControlsUniqueIdentifier# )
Once perimeter off, get the vpcServiceControlsUniqueIdentifier.
Again permeter turn on. wait 3 or 5 mins. And try to use the VPC SC troubleshoot with vpcServiceControlsUniqueIdentifier from the IP address environment ->> get the error message.