Register ADK Agent from GCP Proj A in a Gemini Enterprise from a GCP Proj B

Google Cloud Build with AI Agents
, ,
1

I created an agent using the ADK and deployed it in GCP Project A. Within my organization, we have Gemini Enterprise activated in GCP Project B.

Is it possible to register the agent deployed in GCP Project A to Gemini Enterprise in the GCP Project B? I would like to know if this configuration is supported across different GCP projects.

2

Hello @Fabs,

From what Iā€™ve read on Register and manage ADK agents hosted on Vertex AI Agent Engine, it seems possible.

I would even say that it sounds like the best practice to separate your ADK Agent from the Gemini Enterprise app.

As long as the resources path and permissions are set correctly, it seems to be designed to work.

1 Like
3

I agree with you @LeoK , that seems like a good practice for keeping the agent costs assigned to the correct bill within the organization.

However, Iā€™m currently receiving this error when attempting to register an ADK agent deployed in an Agent Engine from a different GCP project: ā€œAgent and reasoning engine must be in the same project. Agent project number: ā€˜GE GCP Proj Numberā€™, reasoning engine project number: ā€˜ADK Agent GCP Proj Numberā€™ā€.

4

@Fabs,

I took the time to deploy 2 GCP projects to sort this out.

I had project A and project B (with Gemini Enterprise) and unfortunately, Iā€™m having the same error as you. I have tried from the Console and using curl. I even tried bypassing front-end control, in vain. There is a clear check on the project number.

Note that:

  • Agents are in preview mode in Gemini Enterprise
  • The documentation is nebulous and seems not up to date. Some parts are just plain wrong (ex: Agent Engine reasoning engine resource path)

I have sent feedback to Google from the documentation page.. letā€™s hope this gets fixed as the implementation and the documentation seem to indicate that it should be possible.

At the moment, I think that you should consider these 2 possibilities:

  1. Use Agent2Agent protocol as itā€™s mentioned:

Custom Agents deployed anywhere that speak A2A protocol.

  1. Host your agent on Project B until cross-project Agent x Gemini Enterprise is supported

I wish I could have delivered you a more pleasant answer, but I think thatā€™s not possible, at least, for the moment.

1 Like
5

Thanks for taking the time to simulate this on your end, @LeoK .

Iā€™ll mark your comment as a ā€œsolutionā€ since options 1 and 2 align exactly with what I had mentioned to my stakeholder.

Thank you once again.

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.