EVAL wizard not able to provision access routing for Internet

I am new to ApiGee and when I select a sandbox trial, I follow the steps but when I try and select internet I always get the error below.

I see a template created under Goolgle Compute, but no MIG.

Any help will be appriciated

Invalid value for field ‘resource.versions[0].instanceTemplate’: ‘regions/europe-west1/instanceTemplates/apigee-proxy-europe-west1’. https://www.googleapis.com/compute/v1/projects/(PII Removed by Staff)/regions/europe-west1/instanceTemplates/apigee-proxy-europe-west1 does not exist.

1 Like

Hello @Apigeefico

it seems that the instance template is being created by Apigee in the global region rather than in a regional scope. Use PSC-based routing to your Apigee X instance.

1 Like

Hello @Apigeefico ,

I would recommend creating a support ticket for the noted issue (I can reproduce) - as a workaround you can select No Internet traffic and follow: Provision a paid org with VPC peering  |  Apigee  |  Google Cloud Documentation to configure PSC-based routing to your Apigee X instance (CLI commands to create are in the documentation)

Best
Matt

I can reproduce this as well. I attempted to implement this workaround but it’s challenging for me (a GCP neophyte) to complete the steps when done as part of a time-limited Google Skills course (e.g. “Provisioning an Apigee X Evaluation Organization”).

Hi all,

same issue here , that has been reported with the sandbox trial. When I select the “Internet” option during setup, I receive similar error.

A template is created in Compute, but no Managed Instance Group appears. I tried creating a regional instance manually, but the setup still fails with network errors and Access Routing cannot complete.

Workarounds suggest selecting “No Internet traffic” and configuring PSC-based routing manually, but I want guidance on completing the sandbox trial with Internet access.

Has anyone successfully done this?

Thanks!

2 Likes

Hey all,

As previously noted, this is something actively being work on/resolved through our engineering organization. At this time, the workaround provided should unblock given use case requirements (ie: following the commands in our PSC documentation).

Please let me know if you have any questions and/or concerns on the above - I will be providing updates once made available.

Best
Matt

1 Like

Hello all,

The noted fix is being rolled out to production now - please give it a go and let us know of any questions/concerns.

Thanks!

1 Like

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