Anbox Cloud

Learn about configurations >

• agent_id | string

  ID of the agent

• coturn_auth_secret | string

  Authentication secret to use to generate user specific credentials for the configured coturn server. If set an auth secret provided by an established relation to the coturn charm will be ignored.

• coturn_urls | string

  Comma separated list of URLs to the coturn server to use for STUN and TURN. If set an established relation to the coturn charm will be ignored.

• expose_tcp_port | boolean

  Expose a TCP port for each container for WebRTC to bind to avoid a TURN relay server.

• extra_stun_servers | string

  Comma separated list of extra STUN servers the agent should promote for clients connecting to its region

• force_tls13 | boolean

  The Anbox Stream Gateway uses TLS 1.2 by default. As older images based on Ubuntu 18.04 don't support TLS 1.3 enforcing it by default is not yet possible. For deployments where the Ubuntu 18.04 based Anbox images are no longer needed this options allows enforcing TLS 1.3 for all clients.

• location | string

  Location the agent is available on. If not set its private address will be used.

• log_level | string

  Default: info

  Log level for the stream agent. Possible values are: error, info, debug

• nagios_context | string

  Default: juju

  Used by the nrpe subordinate charms. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.

• nagios_servicegroups | string

  A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup

• nats_ca | string

  CA for the NATs servers the agent talks to

• nats_url | string

  URL of the NATs server to use to communicate with the stream gateway [DEPRECATED, use nats_urls]

• nats_urls | string

  Newline separated list URLs of NATs servers to use to communicate with the stream gateway

• port | int

  Default: 8082

  Port the agent listens on.

• public_interface | string

  Identifies which network interface to use for the public address

• region | string

  Region the agent is deployed in

• snap_risk_level | string

  Default: stable

  Sets the snap risk level (https://snapcraft.io/docs/channels) to install the anbox-stream-agent snap from. The channel to use is encoded in the charm and maps to the charm channel (e.g. if charm is on 1.19 the snap will be installed from the 1.19 channel as well).

• tls_use_pinning | boolean

  Default: True

  Enable support for TLS pinning. If the Anbox Stream Agent is not deployed behind a load balancer but uses a certificate signed by an internal CA (e.g. easyrsa) this allows the Anbox container to still verify the TLS certificate based on its fingerprint. When enabled, the agent will pass down the fingerprint of its TLS certificate to the container which then verifies the certificate presented when connecting to the agent based on its fingerprint. Since 1.18.2, if you have a load balancer with proper TLS certificates placed in front of the Anbox stream agent and if you have set the `location` parameter, set `tls_use_pinning` to `false`. Otherwise, Anbox containers will fail to communicate with the stream agent.

• turn_auth_max_lifetime | string

  Default: 5m

  Maximum lifetime of an authentication token generate for the TURN relay server

• ua_source | string

  APT source to use instead of the automatic one generated from UA. Overrides UA source if both are set.

• ua_source_key | string

  Key ID to import to the APT keyring in order to access the specified source archive. Required if ua_source is set.

• ua_token | string

  Ubuntu Advantage token you have received with your license of Anbox Cloud

• ua_use_staging | boolean

  Use staging contracts API service

• use_dummy_launcher | boolean

  Configures a dummy launcher implementation which will not pass container launch requests to AMS but respond directly to the Anbox Stream Gateway with a successful launch. This useful to perform load and stress tests on the upper part of the software stack without having to launch actual containers. The configuration will let the agent expose a single application named "dummy" which can then be referenced in API requests to the Anbox Stream Gateway.