Deploy your agents with Axway CLI
Learn how to deploy your agents using Axway CLI so that you can manage your AWS API Gateway environment within Amplify Central.
3 minute read
Connecting AWS API Gateway to Amplify Central will provide you with a global centralized view of your APIs and their related traffic.
Each AWS Gateway can be represented by an Amplify Central environment allowing you to better filter APIs and their traffic. Supplied with the environment, two agents (Discovery and Traceability) interact with AWS API Gateway and Amplify Central to:
The Discovery Agent is used to discover new deployments and stage updates to existing deployments for publishing related APIs in Amplify Central (either as a catalog item or as an API service). As part of the deployment package, use the provided cloud formation scripts to set up the following agent-dependent AWS Services:
The Traceability Agent is used to filter the AWS CloudWatch logs and prepare the transaction events that are sent to Amplify Central and visible in the API Observer. Viewing your traffic helps you to identify the bottleneck and errors. The traffic can be filtered by environment in case multiples are involved in your topography. As part of the deployment package, you can use cloud formation scripts to set up the following agent-dependent AWS Services:
The types of logging you can do with API Gateway to CloudWatch:
For additional logging information, see https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-logging.html.
Amplify Central supports two regions, US (default) and EU. The data (APIs, traffic) that the agents send to Amplify Central is stored in one of those regions based on the agent configuration.
Use one of the following URLs to access the Amplify Central UI:
Update the following variables to move data to the EU region:
CENTRAL_DEPLOYMENT
= prod-euCENTRAL_URL
= https://central.eu-fr.axway.comTRACEABILITY_HOST
= ingestion-lumberjack.visibility.eu-fr.axway.com:453The following is a high-level overview of the required steps to connect an AWS API Gateway environment to Amplify Central:
You will be guided through this procedure using Axway Central CLI. See Deploy your agents with Axway CLI.
Learn how to deploy your agents using Axway CLI so that you can manage your AWS API Gateway environment within Amplify Central.
As a Cloud Administrator / Operator, you are responsible for configuring and managing your organization’s AWS infrastructure. This topic contains setup and test details for the additional AWS services that are required for Axway’s agents to govern your AWS API Gateway service. The additional services which will be configured are AWS CloudWatch, AWS SQS, AWS Config, and AWS Lambda.
Traffic is always initiated by the Agent to AWS and Amplify Central. No sessions are ever initiated back to the Agent.
This section describes the main security features of the AWS API Gateway agents.
You can set up tag-based condition expressions using the AWS_FILTER environment variable to discover APIs that could be added to Amplify Central. Conditional expressions statements use logical operators to compare values. This section provides sample syntax for defining expressions.
A subscription provides the consumer, or subscriber, with the required security and endpoint materials to correctly consume the API. The security material and/or quota to access an API is configured inside the usage plan on AWS API Gateway.
Learn how to deploy your Discovery Agent and Traceability Agent using Docker containers so that you can manage your AWS API Gateway environment within Amplify Central. Once agents are correctly deployed, they can collect the data from the AWS API Gateway and send it securely to Amplify Central.
This section provides troubleshooting, known limitations and restrictions that you may encounter while you are working with the connected managed environment for AWS API Gateway within Amplify Central. It also provides tips you may find useful when working with this environment.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.