# Connectors limits A rule in an application points at a [connector](/en/documentation/platform/connectors/) with the `Set Connector` behavior. The connector holds the addresses of your origin, a bucket, or a Live Ingest region. Here you find the bounds of every connector, the bounds of Load Balancer and Origin Shield on a connector, and the usage each service plan includes. Each value below is either a default limit or an included amount. Azion checks a default limit when you create or update a connector, and the API refuses the call past it. An included amount is the usage a plan includes for a billing metric. [Azion pricing](https://www.azion.com/en/pricing/) sets the Hobby, Pro, and Enterprise plans next to each other. --- ## Connectors The bounds in this section apply to every connector, whatever its type and service plan. ### Default limits A create or update call that passes one of these bounds returns status `400` with an error code and message, shown for each row. | Scope | Limit | Past the limit | | --------------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Connector `name` | 1 to 255 characters | More than 255 characters: `10046` `Ensure this field has no more than 255 characters.` | | Addresses per connector without Load Balancer | 1 | `28004` `To use more than one address, you must enable the Load Balancer module.` Azion Console keeps **Add Address** unavailable until Load Balancer is on. | Further bounds apply. An `address` takes up to 255 characters, and its `http_port` and `https_port` take 1 to 65535. The `host` and `path_prefix` connection options take up to 255 characters each. The `real_ip_header` and `real_port_header` options take up to 100 characters each. On a connector of type `storage`, `bucket` and `prefix` take up to 255 characters each. For the fields these bounds apply to, refer to [Connector settings](/en/documentation/platform/connectors/settings/). ### Included usage per plan Hobby, Pro, and Enterprise each include Single Origin, a connector with one address. A connector that holds more than one address uses Load Balancer, whose included usage is in the Load Balancer section of this page. --- ## Load Balancer [Load Balancer](/en/documentation/platform/connectors/#load-balancer) distributes requests across the addresses of one connector. The bounds in this section apply when Load Balancer is enabled on the connector, on every service plan. ### Default limits With Load Balancer enabled, a create or update call that passes one of these bounds returns status `400` with an error code and message, shown for each row. | Scope | Limit | Past the limit | | ----------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Addresses per connector | Up to 15 | `28011` `When the Load Balancer module is enabled, you can use up to 15 addresses.` | | Address `weight` | 1 to 100 | Below 1: `10050` `Ensure this value is greater than or equal to 1.` Above 100: `10068` `Ensure this value is less than or equal to 100.` Azion Console shows `Weight must be between 1 and 100`. | | `max_retries` | 0 to 20 retries | Above 20: `10068` `Ensure this value is less than or equal to 20.` | | `connection_timeout` | 1 to 300 seconds | Above 300: `10068` `Ensure this value is less than or equal to 300.` | | `read_write_timeout` | 1 to 600 seconds | Above 600: `10068` `Ensure this value is less than or equal to 600.` | A connector with Load Balancer enabled accepts a single address, so the 15-address bound is a ceiling and not a minimum. To request a higher limit, contact [Azion technical support](/en/documentation/support/). For how the balancing method, the weight, and the server role of each address shape the distribution, refer to [Balancing methods](/en/documentation/platform/connectors/load-balancer/balancing-methods/). ### Included usage per plan Load Balancer is billed on Data Transfer, and each plan includes an amount of it every month. | Metric | Hobby | Pro | Enterprise | | ------------- | --------------- | --------------- | ---------- | | Data Transfer | 15 GB per month | 15 GB per month | Custom | For the rate that applies past an included amount, refer to [Pricing](/en/documentation/fundamentals/pricing/#load-balancer). --- ## Origin Shield [Origin Shield](/en/documentation/platform/connectors/#origin-shield) publishes the Azion addresses your origin can allow. When HMAC is enabled inside Origin Shield, the connector also signs its requests with HMAC credentials. The bounds in this section apply when Origin Shield is enabled on the connector. ### Default limits HMAC takes one credential set per connector, and that set applies to every address of the connector. Each HMAC attribute, `region`, `service`, `access_key`, and `secret_key`, takes 1 to 255 characters. For the HMAC fields and where each value comes from, refer to [Origin IP ACL and HMAC](/en/documentation/platform/connectors/origin-shield/origin-ip-acl-and-hmac/). ### Included usage per plan Origin Shield is billed on Shielded Connectors, and each plan includes an amount of it. | Metric | Hobby | Pro | Enterprise | | ------------------- | ----- | --- | ---------- | | Shielded Connectors | 1 | 1 | Custom | For the rate that applies past an included amount, refer to [Pricing](/en/documentation/fundamentals/pricing/#origin-shield). --- ## Live Ingest [Live Ingest](/en/documentation/platform/connectors/#live-ingest) is billed on Data Ingestion, measured per GB. For the rate, refer to [Pricing](/en/documentation/fundamentals/pricing/#live-ingest). --- ## Related resources - [Connector settings](/en/documentation/platform/connectors/settings.md): The type, default, and accepted values of each connector field, including the fields bounded here. - [Balancing methods](/en/documentation/platform/connectors/load-balancer/balancing-methods.md): How Load Balancer picks an address for each request, and how weight and server role change the choice. - [Pricing](/en/documentation/fundamentals/pricing.md): The rates for Load Balancer data transfer, shielded connectors, and Live Ingest data ingestion past each included amount. - [Troubleshoot Connectors](/en/documentation/platform/connectors/troubleshooting.md): The symptoms a connector can show, what causes each one, and how to fix it.