API Gateway 10.11 | Administering API Gateway | Operating API Gateway | Configuring External Accounts
 
Configuring External Accounts
 
Adding a Service Registry
Removing a Service Registry
Configuring an AWS Alias
Configuring Integration Server Instance for API Implementation
API Gateway provides capability to add and configure external accounts such as service registries, AWS accounts, Integration Server, and service mesh instances and communicate these changes across nodes in the cluster. An API Gateway administrator can add and remove the configured external accounts.
Service registry
The Service registry section allows you to configure service registries that API Gateway could use.
A service registry is essentially a catalog of services. Applications that expose services can register their services with one or more service registries. Applications that need to consume a service look up a service registry and obtain the address of an application server that provides the service. Using service registries with API Gateway adds resilience, scalability, and security to the application stack.
API Gateway uses service registries in the following ways:
*You can publish APIs defined in API Gateway to service registries. This enables other applications to use the service registry to dynamically locate an API Gateway instance that provides that API.
*You can set an API Gateway route to a service registry endpoint. This enables API Gateway to use the service registry to dynamically locate an application instance and route the request to it.
Service Registries supported by API Gateway
API Gateway currently supports the following service registries.
*Eureka
Eureka is a REST-based service for locating services for the purpose of load balancing and failover of middle-tier servers. It has been primarily designed for applications in the AWS cloud.
*Service Consul
Service Consul is a tool for discovering and configuring services in IT infrastructure.
AWS configuration
The AWS configuration section allows you to configure AWS aliases that are used in custom policy extension and custom destination sections.
Integration Server
The Integration server section allows you to configure the details of Integration Server instances required for API first implementation.
Service mesh
The Service mesh section allows you to configure the details of service mesh environment. To discover the services and deploy AppMesh, you must configure API Gateway to connect to the service mesh environment where the services reside. For information on configuring service mesh, see Configure API Gateway to Connect to a Service Mesh Environment.