#Docker inspect format array how to

If not deploying in an EC2 instance, the secret access key of the AWS account where APIs are stored. Generated when the apigw_cloudformation script is run or you can use your own. If not deploying in an EC2 instance, the access key of the AWS account where APIs are stored. See Discover APIs for conditional expression samples.ĭetermines whether the AWS Stage tags should be pushed to Amplify Central along with the API definition.

Default is true.įilter conditions for discovery based on AWS Stage tags to determine adding the API to Central. A value of false will cause ‘Create an application’ to not be shown in the drop-down. The new Usage Plan in AWS Gateway will be given the name of the subscription ID from Amplify Central. When creating a subscription on Amplify Central, setting this value to true will enable a selection in the App name drop-down for ‘Create a usage plan.’ This allows the user to either select from an existing AWS Gateway Usage Plan, or to create a new Usage Plan in AWS Gateway. See Prepare AWS Gateway to deploy the Discovery Agent AWS config setup. The log group name where API Gateway will send Execution events (output of Step 5). It is the QueueName provided during installation. The name of the queue where Discovery Agent will read relevant AWS events. The interval at which to poll AWS for changes to things like UsagePlans (ns - default, us, ms, s, m, h).

The interval at which to poll SQS for messages (ns - default, us, ms, s). Create your Discovery Agent configuration Variable name

The configuration of the AWS_QUEUENAME is not used in this mode. This mode does not handle any subscription events. Once it has completed this task it will exit and no additional changes will be sent to Amplify Central until the agent is executed again. In this mode the agent will read the configuration on AWS API Gateway and send all REST APIs to Amplify Central. This mode is also required to manage subscriptions and subscription notifications. These events will be processed and sent to Amplify Central. In this mode the agent will receive change events for configuration changes to AWS API Gateway resources. The other synchronizing all APIs and then exits. There are two operating modes of the Discovery Agent, one is receiving continuous changes from AWS API Gateway and pushing to Amplify Central. The Discovery Agent only discovers published APIs where the stage has tags defined in the agent configuration file.

Once they are discovered, the related APIs are published to Amplify Central so that they become available for any consumer. The Discovery Agent is used to discover new deployments and stage updates to existing deployments.

#Docker inspect format array how to

Learn how to create your Discovery Agent and Traceability Agent configuration files, then install and run your agents. Docker must be installed and you will need a basic understanding of Docker commands.Read Amplify Central AWS API Gateway connected overview.Once agents are correctly deployed, they can collect the data from the AWS API Gateway and send it securely to Amplify Central. 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.