---
title: Starting an Authorize gateway instance
description: Deploy and start an Authorize gateway instance in your infrastructure.
component: pingone
page_id: pingone:integrations:p1_start_authz_gateway_instance
canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_start_authz_gateway_instance.html
section_ids:
  before-you-begin: Before you begin
  steps: Steps
  next-steps: Next steps
---

# Starting an Authorize gateway instance

Deploy and start an Authorize gateway instance in your infrastructure.

Gateway instances evaluate policy versions published from PingOne in order to make authorization decisions. Gateway instances are distributed as container images, and they maintain a WebSocket connection with the PingOne platform.

|   |                                                                                                                                                      |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Make sure you install gateway instances on a system that can reach PingOne and any information points that will be used for authorization decisions. |

To start a gateway instance, you'll use the Docker command that you copied earlier on the Authorize gateway **Download** tab.

![A screen capture of the gateway Download tab showing download instructions and the Docker command.](_images/p1-az-gateway-download-tab.png)

## Before you begin

* Ensure that Docker is installed and the Docker Engine is running.

* Review the end-user license agreement at <http://www.pingidentity.com/en/legal/subscription-agreement.html>.

## Steps

1. In the Docker command that you copied in step 7 of [Adding an Authorize gateway](p1_add_authz_gateway.html), consent to the license agreement by changing `no` to `yes`:

   ```
   -e PING_IDENTITY_ACCEPT_EULA=yes
   ```

   The command will look something like this (line breaks are included for readability and aren't necessary in your command):

   ```
   docker run --init \
     -e PING_IDENTITY_ACCEPT_EULA=yes \
     -e gatewayCredential=<your-gateway-credential> \
     -p 8080:8080 pingidentity/pingone-authorize-gateway:1.2.1
   ```

2. Run the command.

   The container starts and you have a connected gateway instance.

   ![A screen capture of the Overview tab for a connected gateway instance showing the gateway credential.](_images/p1-az-gateway-instance.png)

   |   |                                                                   |
   | - | ----------------------------------------------------------------- |
   |   | If the gateway instance can't connect to PingOne, it won't start. |

## Next steps

* Review the gateway instance's startup log message to confirm that the instance uses the expected environment and gateway. Learn more in [Startup logging](p1_logging_authz_gateway_instances.html#p1_az_gateway_startup_logging).

* Start additional gateway instances in your infrastructure as needed for your organization's use cases.

* [Publish authorization policy versions to Authorize gateway instances](p1_publish_policy_versions_to_authz_gateway_instances.html).