Deployment

the default distribution for jumpwire is through docker containers there are two containers published by jumpwire, one for the control web application and one for the execution engine additional containers may also be necessary to implement functionality depending on the cloud environment jumpwire is installed into see the components docid 6jbari9pcyga5o6rpf eh page for details environments kubernetes in addition to cloud container runtimes, jumpwire is compatible with self hosted kubernetes environments the deployment team can provide helm charts to assist with installation google cloud platform terraform code for deploying to gcp elastic container service is available at https //github com/jumpwire ai/infrastructure tools/tree/main/terraform/gcp/gce to use jumpwire with google kubernetes engine, follow the instructions for self hosting with helm docid\ ygdh7hnqlohlmpbm 2kj6 amazon web services terraform code for deploying to aws elastic container service is available at https //github com/jumpwire ai/infrastructure tools/tree/main/terraform/aws/ecs instructions for using the web console are also available at self hosting with aws ecs docid\ xxevqsw78pws223bfy4ux to use jumpwire with amazon elastic kubernetes service, follow the instructions for self hosting with helm docid\ ygdh7hnqlohlmpbm 2kj6 self hosted web authentication jumpwire supports any oauth or openid providers for authenticating to the web frontend with client credentials configured during setup if your preferred provider is not listed below, let us know and we will add it! google oauth google’s single sign on for oauth authentication the oauth client is tied to an installation’s domain name (for callbacks) and a customer’s email domain (for identity verification) you can read more about provisioning google oauth applications on this support page when using google oauth, the following configuration docid\ and6t wc2kywbr p1y gr variables must be set jumpwire auth domains google client id google client secret auth0 details on setting up a new auth0 application are available in auth0's documentation the application should be a "regular web application" with these settings allowed callback url https //jumpwire domain/auth/auth0/callback allowed logout url https //jumpwire domain allowed web origins https //jumpwire domain allowed origins (cors) https //jumpwire domain under advanced > oauth json web token (jwt) signature algorithm rs256 oidc conformant toggled on when using auth0, the following configuration docid\ and6t wc2kywbr p1y gr variables must be set auth0 domain auth0 client id auth0 token secret