Publish APIs in from different regions on one dev portal

[a-tan]

Admin can publish APIs hosted in API Gateway from different regions on to one Dev Portal. These "out of region" APIs have the same support and capabilities as a normal "in the region" API. For example, customers of the Dev Portal can get an API key, associate it with a usage plan, and monitor usage.

[AntonioMPereira]

Hello, I manage a development team and have an interest in this proposed functionality. I would like to put some of my team to develop this functionality. We have our APIs exposed in the São Paulo / Brazil region and for reasons of dependence on Cognito (not available in São Paulo) Developer Portal is deployed in the North Virginia region. I understand being more productive if someone who knows the architecture of the Portal deeply can give us guidance. In this way I understand that it can be more easily incorporated into the official project. Would it be possible?

[echo-bravo-yahoo]

Hey! Sorry for the delay on responding to this. This functionality (a dev portal in one region that could interact with API gateway APIs in many regions) would require a number of changes:

• Most of the dev portal's logic is implemented in a lambda function that makes calls to API Gateway in the same region. That function's permissions (BackendLambdaExecutionRole) would need to be expanded for all the regions the APIs are published in. Since this would likely require iterating (e.g., for each region in a stack parameter, make a permission), you'd need to add either a macro or a custom resource to the stack that can modify that IAM role.
• The lambda function itself (DevPortalLambdaFunction) would need to take in as a property and environment variable the list of regions that are used and make calls against API Gateway in all of those regions (for things like usage plans, apis, api key, etc.) instead of just the region it exists in.
• The same would need to be done to the catalog updater lambda function (CatalogUpdaterLambdaFunction) to allow it to take the list of regions and make calls to those regions' API Gateway.
• Optionally, the catalog updater could also be modified to encode the region in the resulting catalog objects so that the front-end UI could tell end users of the dev portal what region the APIs were in. This would be useful in cases where you may have the same API deployed as a REGIONAL API in 2 regions, and expect your customers to use the one that's closest to them.

I may have missed some details, but I believe that's the bulk of the work.

[AntonioMPereira]

Thank you very much. I really need this and I'm going to put some people on my team to make this happen. Very cool to be able to help with this project. All the best, Antonio

[jramakan]

I wanted to follow up on this feature and any updates that can be shared.

[rrjgithub]

Hi. Just wanted to follow up on the status of this project

[soulfreaky]

Hello. Interested on the status too