Show Table of Contents Hide Table of Contents English English Multi-page HTML Single-page HTML PDF ePub API Devops1. Differentiate API environments1.1. Overview1.2. Option 1: Staging restricts access based on rate limits or methods1.3. Option 2: Application plan determines API call routing to staging or production environment1.3.1. Note2. Production Tips2.1. Load balancing with the 3scale API gateway2.2. Correctly configure DNS resolution in NGINX2.3. Bypassing the authorization step in case of network failure2.3.1. Status updates3. Using Chef With Your API Gateway3.1. Prerequisites3.2. How to use it3.2.1. 1. Add the Cookbook to your run list3.2.2. 2. Configure the required Cookbook attributes3.3. Applying your own 3scale configuration3.3.1. Option 1: Local configuration files3.3.2. Option 2: Fetch configuration files from your 3scale account3.4. Rolling back to a previous version of the configuration3.4.1. Troubleshooting4. Troubleshooting4.1. Common issues4.1.1. Integration issues4.1.2. Production issues4.1.3. Post-deploy issues4.2. Troubleshooting 1014.2.1. 1. Can we connect?4.2.2. 2. Is it me or is it them?4.2.3. 3. Is it a DNS issue?4.2.4. 4. Is it an SSL issue?4.3. Troubleshooting checklists4.3.1. API4.3.2. API Gateway > API4.3.3. API gateway4.3.4. API gateway > 3scale4.3.5. 3scale4.3.6. Client API gateway4.3.7. Client4.4. Other Issues4.4.1. ActiveDocs issues4.5. Appendix4.5.1. Logging in NGINX4.5.2. 3scale error codesLegal Notice API Devops Red Hat 3scale 2.2For Use with Red Hat 3scale 2.2Red Hat Customer Content Services Legal NoticeAbstract This guide documents development operations with Red Hat 3scale 2.2. 1. Differentiate API environments Where did the comment section go?Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.