Get help with Connected AWS Gateway
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.
8 minute read
Troubleshooting
| Question | Answer |
|---|---|
| Why isn’t my API discovered? | Check that the tag set on the stage has a correct name and value based on the AWS_FILTER variable. |
| Why can’t my agents connect to AWS API Gateway? | Go to AWS console / IAM service and make sure that AWS_REGION, AWS_AUTH_ACCESSKEY and AWS_AUTH_SECRETKEY are valid and not inactivated. |
| Why can’t my agents connect to Amplify Central? | Go to Amplify Central UI > Access > Service Accounts and make sure that the Service Account is correctly named and valid. Make sure that the organizationID and team configuration are correct. |
| Why don’t I see traffic in Amplify Central? | Make sure that the Condor URL is accessible from the machine where Traceability Agent is installed. |
| Why isn’t my agent status displayed in the environment details page? | It is possible that your agents and their corresponding resources are not linked together. Follow this procedure to ensure the correct usage of agent resources. |
Error Codes and Mitigations
| Code # | Description | Mitigation |
|---|---|---|
| 1001 | initialization error checking for dependencies to respond, possibly network or settings | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1002 | timeout error checking for dependencies to respond, possibly network or settings | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1100 | general configuration error in CENTRAL | See Reference - Agent configuration for the Central Config |
| 1101 | error attempting to query for ENVIRONMENT | Check that the Environment Name in config matches the name on Amplify Central |
| 1102 | could not find specified team in Amplify Central, check CENTRAL_TEAM | Check that the Team Name in config matches the name on Amplify Central |
| 1110 | connection to Amplify Central failed | See Administer AWS Gateway network traffic |
| 1120 | request to Amplify Central failed | See Administer AWS Gateway network traffic and that the Environment Name in config matches the name on Amplify Central |
| 1130 | request to get authentication token failed | Check the Auth configuration (ClientId, Private and Public keys/index.html). See Reference - Agent configuration |
| 1131 | token retrieved but was invalid on request to Amplify Central | Check the Auth configuration (ClientId, Private and Public keys/index.html). See Reference - Agent configuration |
| 1140 | couldn’t find a subscriber email address based on the ID in the subscription event | The user requesting this subscription may not have an Email address set |
| 1141 | couldn’t contact Amplify Central for subscription, possible network error | See Administer AWS Gateway network traffic |
| 1142 | couldn’t get subscription data from Amplify Central | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1143 | couldn’t create or update subscription schema data | See Administer AWS Gateway network traffic |
| 1144 | unexpected response when managing subscription schema on Amplify Central | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1145 | unable to create webhook for the subscription definition | See Administer AWS Gateway network traffic |
| 1146 | unable to create secret for the subscription definition | See Administer AWS Gateway network traffic |
| 1147 | error parsing filter in configuration. Syntax error | See Discover APIs |
| 1148 | error parsing filter in configuration. Unrecognized expression | See Discover APIs |
| 1149 | error parsing filter in configuration | See Discover APIs |
| 1150 | error parsing filter in configuration. Invalid call argument | See Discover APIs |
| 1151 | error parsing filter in configuration. Invalid selector type | See Discover APIs |
| 1152 | error parsing filter in configuration. Invalid selector expression | See Discover APIs |
| 1153 | error parsing filter in configuration. Invalid operator | See Discover APIs |
| 1154 | error parsing filter in configuration. Unrecognized condition | See Discover APIs |
| 1155 | error getting subscription definition properties in Amplify Central | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1156 | error updating subscription definition properties in Amplify Central | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1157 | error getting catalog item API server info properties in Amplify Central | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1158 | subscription manager is not running likely because the agent can’t communicate with Amplify Central | See Administer AWS Gateway network traffic and Reference - Agent configuration |
| 1160 | error getting endpoints for the API specification | Verify that the OpenAPI Specification for the discovered API has available endpoints and operations on each endpoint |
| 1161 | error deleting API Service for catalog item in Amplify Central | Verify that the catalog item exists in Amplify Central |
| 1162 | error deleting catalog item in Amplify Central | Verify that the catalog item exists in Amplify Central |
| 1300 | error communicating with server for subscription notifications (SMTP or webhook/index.html), check SUBSCRIPTION config | See Manage subscription workflow |
| 1301 | subscription notifications not configured, check SUBSCRIPTION config | See Manage subscription workflow |
| 1302 | error creating data for sending subscription notification | Check AWS Console for configuration of API and its Usage Plan(s/index.html) |
| 1303 | email template not updated because an invalid authType was supplied | Check AWS Console for configuration of API and its Usage Plan(s/index.html), specifically enabled API Keys on the Usage Plan |
| 1304 | no email template found for action | See Manage subscription workflow for the SMTP template settings |
| 1305 | error sending email to SMTP server | See Manage subscription workflow for the SMTP settings |
| 1401 | error parsing configuration values, check the config referenced in error | See Reference - Agent configuration |
| 1402 | error in overriding configuration using file with environment variables | See Reference - Agent configuration. Make sure the env_vars file exists and is properly formatted |
| 1403 | invalid value for statusHealthCheckPeriod. Value must be between 1 and 5 minutes | See Reference - Agent configuration. Make sure the env_vars file exists and is properly formatted |
| 1404 | invalid value for statusHealthCheckInterval. Value must be between 30 seconds and 5 minutes | See Reference - Agent configuration. Make sure the env_vars file exists and is properly formatted |
| 1405 | a key file could not be read | On Linux, give the User ID in the container read access to the file. setfacl -m u:2500:r private_key.pem |
| 1410 | invalid configuration settings for the logging setup | See Set up agent configuration for logging configuration options |
| 1503 | http transport is not connected | See the TRACEABILITY_HOST setting at Reference - Agent configuration |
| 1504 | failed to encode the json content | Internal system error. Contact your system administrator |
| 1505 | invalid traceability config | See Reference - Agent configuration for the Traceability Config |
| 1510 | global redactions have not been initialized | See Trace redaction |
| 1511 | error while compiling regular expression | See Trace redaction |
| 1520 | global sampling has not been initialized | See Trace sampling |
| 1521 | invalid sampling configuration | See Trace sampling |
| 1550 | error hit while applying redaction | See Trace redaction |
| 1600 | error registering the job | The agent attempted to register a job, but could not do so successfully |
| 1601 | error executing a job | A job defined in the agent failed, see the logs for more info |
| 1602 | error executing a retry job | A job defined in the agent failed, see the logs for more info |
| 1611 | periodic healthcheck failed | One of the agent healthchecks failed, check the agent logs for more info |
| 1612 | a healthcheck failed the maximum consecutive times | One of the agent healthchecks failed, check the agent logs for more info |
| 2001 | aws region must be set in the configuration | Check that AWS_REGION is set in the config. See Reference - Agent configuration |
| 2002 | sqs queue name is a required configuration in continuous mode | Check that AWS_QUEUENAME is set in the config. See Reference - Agent configuration |
| 2003 | sqs poll interval cannot be greater than 20 seconds | Check that AWS_SQSPOLLINTERVAL value is not greater than 20 seconds. See Reference - Agent configuration |
| 2004 | aws auth config not properly set up in the configuration | Check that AWS_AUTH_ACCESSKEY and AWS_AUTH_SECRETKEY are set in the config. See Reference - Agent configuration |
| 2100 | failed to process subscription request. Cannot find API related to ID | Could not find the Rest API on AWS related to this Catalog Item, it may have been removed from AWS |
| 2101 | failed to process a request for a rest api and stage | Check AWS Setup. See Administer AWS Gateway cloud |
| 2102 | can’t get email address for a Service Account subscriber | A service account was used to create this subscription and does not have an email address associated with it |
| 2110 | unable to register the subscription schema with API Key auth | Check the usage plan selected and ensure it has an enabled API Key |
| 2111 | unable to update a subscription schema | Check that the Environment is configured and exists in Amplify Central. See Reference - Agent configuration |
| 2112 | unable to register subscription webhook | Check that the Environment is configured and exists in Amplify Central. See Reference - Agent configuration |
| 2113 | error updating subscription in Amplify Central | Check that the Environment is configured and exists in Amplify Central. See Reference - Agent configuration |
| 2200 | error getting a list of AWS resources from AWS | Check AWS Setup. See Administer AWS Gateway cloud |
| 2201 | error getting a specific AWS resource | Check AWS Setup. See Administer AWS Gateway cloud |
| 2202 | error updating an AWS resource | Check AWS Setup. See Administer AWS Gateway cloud |
| 2203 | error tagging an AWS resource | Check AWS Setup. See Administer AWS Gateway cloud |
| 2204 | error creating an association between AWS resources | Check AWS Setup. See Administer AWS Gateway cloud |
| 2205 | error sending the list of usage plans | Could not update the agent cache with the new list of Usage Plans |
| 2206 | error creating a specific AWS resource | Check AWS Setup. See Administer AWS Gateway cloud |
| 2210 | error loading AWS configuration | Check AWS Setup. See Administer AWS Gateway cloud |
| 2250 | error sending request to AWS SQS | Check AWS Setup. See Administer AWS Gateway cloud |
| 2500 | could not set the proxy url environment variable | Check the LOGSTASH_PROXYURL setting here Reference - Agent configuration |
| 2600 | error sending request to AWS CloudWatch | Check AWS Setup. See Administer AWS Gateway cloud |
Feedback
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.
Last modified May 28, 2021: APIGOV-18499 - new error codes (#1895) (56e7ab96)