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.
7 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. |
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 Deploy agents - advanced functionality |
| 1002 | timeout error checking for dependencies to respond, possibly network or settings | See Administer AWS Gateway network traffic and Deploy agents - advanced functionality |
| 1100 | general configuration error in CENTRAL | See Deploy agents - advanced functionality 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 Deploy agents - advanced functionality |
| 1131 | token retrieved but was invalid on request to AMPLIFY Central | Check the Auth configuration (ClientId, Private and Public keys/index.html). See Deploy agents - advanced functionality |
| 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 Deploy agents - advanced functionality |
| 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 Deploy agents - advanced functionality |
| 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 Deploy agents - advanced functionality |
| 1156 | error updating subscription definition properties in AMPLIFY Central | See Administer AWS Gateway network traffic and Deploy agents - advanced functionality |
| 1157 | error getting catalog item API server info properties in AMPLIFY Central | See Administer AWS Gateway network traffic and Deploy agents - advanced functionality |
| 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 Deploy agents - advanced functionality |
| 1402 | error in overriding configuration using file with environment variables | See Deploy your agents - advanced functionality. 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 Deploy your agents - advanced functionality. 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 Deploy your agents - advanced functionality. 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 |
| 1501 | failed to publish events | See Administer AWS Gateway network traffic |
| 1502 | error closing connection with Condor | Likely a timeout error, processing will retry automatically |
| 1503 | http transport is not connected | See the TRACEABILITY_HOST setting at Deploy agents - advanced functionality |
| 1504 | failed to encode the json content | Internal system error. Contact your system administrator |
| 1505 | invalid traceability config | See Deploy agents - advanced functionality for the Traceability Config |
| 2001 | aws region must be set in the configuration | Check that AWS_REGION is set in the config. See Deploy agents - advanced functionality |
| 2002 | sqs queue name is a required configuration in continuous mode | Check that AWS_QUEUENAME is set in the config. See Deploy agents - advanced functionality |
| 2003 | sqs poll interval cannot be greater than 20 seconds | Check that AWS_SQSPOLLINTERVAL value is not greater than 20 seconds. See Deploy agents - advanced functionality |
| 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 Deploy agents - advanced functionality |
| 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 Deploy agents - advanced functionality |
| 2112 | unable to register subscription webhook | Check that the Environment is configured and exists in AMPLIFY Central. See Deploy agents - advanced functionality |
| 2113 | error updating subscription in AMPLIFY Central | Check that the Environment is configured and exists in AMPLIFY Central. See Deploy agents - advanced functionality |
| 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 |
| 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 Deploy agents - advanced functionality |
| 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 January 5, 2021: APIGOV-17163 Reorg Connect AWS Gateway (#1525) (2a9978ba)