| Table of Contents |
|---|
| Warning | ||
|---|---|---|
| ||
This implementation is only valid for resources hosted within Solvay's GCP organization. For further information, please contact the Syensqo's GCP support team. |
Why am I not able to call the Google APIs with Google Service Accounts?
| Expand | ||
|---|---|---|
| ||
There are several possibilities that you are not able to call the Google APIs with Google Service Accounts.
|
Why do the Google Service Accounts need the client application's Internet Gateway's IP?
| Expand | ||
|---|---|---|
| ||
Google Service Accounts are identified by Security to be a likely avenue for bad actors to extract Solvay's data. Therefore, since Nov-2024, Application Owner for each GCP projects will need to provide the Internet Gateway's IPs for each clients to the GCP CloudOps to implement the VPC Service Control. |
The Client's Internet Gateway IP should be allowed to call the Google APIs, how should I get it
fixed?
| Expand | |||||
|---|---|---|---|---|---|
| |||||
If you identify there is a client's Internet Gateway IP needs to be added, please discuss with the application owner and the application owner will submit a ticket to the GCP CloudOps for additional implementation. Please note that:
|
How come for some GCP projects, there are no such restriction, while other GCP projects there are?
| Expand | ||
|---|---|---|
| ||
This is normal as the teams are working progressively to implement the VPC Service Control, project by project. The implementation will be impactful to many existing project usage, therefore the implementation will taken individually. |