During deployment, the logs show this error : google.api_core.exceptions.PermissionDenied: 403 Permission ‘resourcemanager.projects.get’ denied on resource ‘//cloudresourcemanager.googleapis.com/projects/MY_PROJECT_ID’ (or it may not exist). [reason: “IAM_PERMISSION_DENIED]”
Regarding whether it’s normal for a Google-managed Service Account to be missing roles for its own task-purpose: Generally, no, this is not normal. Google-managed service agents are automatically provisioned by Google with specific IAM roles (e.g., “Vertex AI Service Agent”) designed to give them the necessary permissions for their designated functions. The role assigned to the Vertex AI Google-managed Service Account provides permissions for the Vertex AI service itself to carry out backend deployment operations and manage the agent, not for your identity to initiate the deployment call.
Moreover, concerning specifying a different service account for deployment: The “service-PROJECT_NUMBER@gcp-sa-aiplatform-re.iam.gserviceaccount.com” account is a Google-managed service account that is automatically used by Vertex AI. As of now, you cannot specify a different service account for internal Vertex AI tasks, including agent engine deployments, because the platform is designed to use this specific service account.
Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.