aziontech · GabrielAzion · Nov 4, 2025 · Nov 4, 2025
@@ -18,7 +18,7 @@ Azion supports compliance efforts at multiple levels by offering robust security
 - **Security configurations and policies**: customers can customize security configurations like access control, traffic filtering, and encryption through Azion's tools, ensuring alignment with specific GRC policies.
 - **Shared responsibility**: compliance is shared, with Azion securing the platform and customers managing application-specific controls like access policies and data encryption.
 - **Support and incident response**: Azion's [Security Response Team (SRT)](/en/documentation/services/security-response-team/) helps customers manage incidents and monitor security to maintain ongoing compliance.
-- **Certificate management**: Azion enables customers to manage digital certificates, ensuring secure, encrypted communications, particularly for sensitive data transmission.
+- **Certificate management**: Azion enables customers to manage certificate manager, ensuring secure, encrypted communications, particularly for sensitive data transmission.
 
 ### About Shared Responsibility
 

@@ -131,7 +131,7 @@ See each available field and their descriptions below.
 | upstreamBytesReceivedStr | List with all `upstreamBytesReceived` responses. |
 | upstreamBytesSent | Number of bytes sent to the origin. Example: `2733` |
 | upstreamBytesSentStr | List with all `upstreamBytesSent` responses. |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamConnectTime | Time it takes for the edge to establish a connection with the origin, in seconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **Returns `0` for KeepAlive and `-` for cache** |
 | upstreamConnectTimeStr | List with all `upstreamConnectTime` responses. |
 | upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin, in seconds. Example: `0.345`. **In case of cache, the response is `-`** |
@@ -192,7 +192,7 @@ See each available field and their descriptions below.
 | status | HTTP status code of the request. Example: `200` |
 | tcpInfoRtt | Round-Trip Time (RTT) in microseconds measured by the edge for the user. Available on systems that support the TCP_INFO socket option. Example: `72052` |
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamResponseTimeStr | List with all `upstreamResponseTime` responses. |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`.** |
@@ -228,7 +228,7 @@ See each available field and their descriptions below.
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
 | upstreamBytesReceived | Number of bytes received by the origin’s edge if the content isn’t cached. Example: `8304` |
 | upstreamBytesReceivedStr | List with all `upstreamBytesReceived` responses. |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamConnectTime | Time it takes for the edge to establish a connection with the origin, in seconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **Returns `0` for KeepAlive and `-` for cache** |
 | upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin, in seconds. Example: `0.345`. **In case of cache, the response is `-`** |
 | upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`** |
@@ -318,7 +318,7 @@ The following datasets were discontinued. It's recommended to use the [new datas
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
 | upstreamBytesReceived | Number of bytes received by the origin’s edge if the content isn’t cached. Example: `8304` |
 | upstreamBytesReceivedStr | List with all `upstreamBytesReceived` responses. |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamConnectTime | Time it takes for the edge to establish a connection with the origin, in seconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **Returns `0` for KeepAlive and `-` for cache** |
 | upstreamHeaderTime | Time it takes for the edge to receive the response header from the origin, in seconds. Example: `0.345`. **In case of cache, the response is `-`** |
 | upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`** |

@@ -45,7 +45,7 @@ The Real-Time Metrics interface on Azion Console also has the `domains` field fo
 | status | HTTP status code of the request. Example: `200` |
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
 | upstreamBytesReceived | Number of bytes received by the origin’s edge if the content isn’t cached. This field is the result of a sum. Example: `8304` |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is -**. |
 | wafAttackFamily | Category or type of attack detected by the Web Application Firewall (WAF), based on their characteristics. Example: `$SQL`, `$RFI`, `$SQL`, `$XSS`, `$OTHERS` |
@@ -154,7 +154,7 @@ When a field results from any kind of calculation, such as a sum, they're consid
 | status | HTTP status code of the request. Example: `200` |
 | ts | Timestamp the event was created. Example: `2022-10-20T10:10:10` |
 | upstreamBytesReceived | Number of bytes received by the origin’s edge if the content isn’t cached. This field is the result of a sum. Example: `8304` |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`**. |
 
@@ -212,7 +212,7 @@ When a field is a result of any kind of calculation, such as a sum, they're cons
 | sourceLocPop | Location and PoP of the server that received the request. Example: `lax-bso` |
 | status | HTTP status code of the request. Example: `200` |
 | ts | Timestamp of when the event was created. Example: `2022-10-20T10:10:10` |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`**. |
 
@@ -362,7 +362,7 @@ The following datasets were discontinued. It's recommended to use the [new datas
 | status | HTTP status code of the request. Example: `200` |
 | ts | Timestamp the event was created. Example: `2022-10-20T10:10:10` |
 | upstreamBytesReceived | Number of bytes received by the origin’s edge if the content isn’t cached. This field is the result of a sum. Example: `8304` |
-| upstreamCacheStatus | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| upstreamCacheStatus | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | upstreamResponseTime | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`** |
 | upstreamStatus | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`**. |
 

@@ -36,7 +36,7 @@ console.log(myApp);
 
 ### mountMPA
 
-The `mountMPA` function handles requests for Multi-Page Applications (MPA) at the edge. It processes the incoming request URL, constructs the appropriate asset path, and fetches the corresponding response from the origin server or edge cache.
+The `mountMPA` function handles requests for Multi-Page Applications (MPA) at the edge. It processes the incoming request URL, constructs the appropriate asset path, and fetches the corresponding response from the origin server or cache.
 
 **TypeScript example:**
 

@@ -6,7 +6,7 @@ description: >-
 permalink: /documentation/products/cli/dev-command/
 meta_tags: >-
   Azion, Edge Computing, Applications, Functions, Local Development
-  Server, CLI, Dev Command, JavaScript, Edge Firewall
+  Server, CLI, Dev Command, JavaScript, Firewall
 namespace: documentation_cli_dev
 menu_namespace: cliMenuAlpha
 ---

@@ -144,8 +144,8 @@ Type definition for the cache configuration.
   - `options?: boolean` - Whether to cache OPTIONS requests.
 - `browser?: BrowserCacheConfig` - Browser cache settings.
   - `maxAgeSeconds: number | string` - Maximum age for browser cache in seconds.
-- `edge?: EdgeCacheConfig` - Edge cache settings.
-  - `maxAgeSeconds: number | string` - Maximum age for edge cache in seconds.
+- `edge?: EdgeCacheConfig` - Cache  settings.
+  - `maxAgeSeconds: number | string` - Maximum age for cache in seconds.
 - `cacheByCookie?: CacheByCookieConfig` - Cache by cookie settings.
   - `option: 'ignore' | 'varies' | 'whitelist' | 'blacklist'` - Cache by cookie option.
   - `list?: string[]` - List of cookies to use for caching.

@@ -3,7 +3,7 @@ title: How to configure mTLS
 description: Learn how to configure mTLS in your application at Azion.
 meta_tags: >-
   mutual transport layer security, mtls, tls handshake, open banking,
-  certificates, digital certificates
+  certificates, certificate manager
 namespace: documentation_products_guides_mtls
 permalink: /documentation/products/guides/mtls/
 ---
@@ -18,7 +18,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx'
 
 To configure mTLS in your applications, you need to activate the service through [Azion Sales Team](https://www.azion.com/en/contact-sales/) in addition to having a digital certificate with mTLS support, provided by a third-party certificate authority. At Azion, this certificate is called **Trusted Certificate (Trusted CA)**.
 
-More information about requirements, digital certificates, Trusted CA, and how mTLS works at Azion is available on the [Support for mTLS page](/en/documentation/products/secure/edge-firewall/mtls/).
+More information about requirements, certificate manager, Trusted CA, and how mTLS works at Azion is available on the [Support for mTLS page](/en/documentation/products/secure/edge-firewall/mtls/).
 
 There are separate instructions using [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings using the new [Workloads](/en/documentation/products/secure/workloads) product.
 

@@ -4,7 +4,7 @@ description: >-
   Manage lists of IPs, ASNs, and geolocations from accessing your applications
   at the edge with Network Lists.
 meta_tags: >-
-  edge computing, network layer protection, secure, network lists, network layer
+  edge computing, network shield, secure, network lists, network layer
   security
 namespace: docs_use_case_blacklists_ip_addresses_edge
 permalink: /documentation/products/guides/blocklists-ip-addresses-edge/

@@ -4,7 +4,7 @@ description: >-
   Cache speeds up content delivery by keeping your content cached at the
   edge and bringing your application closer to your users.
 meta_tags: >-
-  caching, edge, edge cache, edge computing, performance, cache status, bypass,
+  caching, edge, cache, edge computing, performance, cache status, bypass,
   hit, miss
 namespace: documentation_products_edge_caching
 permalink: /documentation/products/build/applications/cache/

@@ -4,7 +4,7 @@ description: >-
   Tiered Cache establishes an extra cache layer between the edge and your origin
   servers, effectively lowering latency and minimizing infrastructure expenses.
 meta_tags: >-
-  caching, edge, edge cache, edge computing, l2, layer 2, cache layer, purge
+  caching, edge, cache, edge computing, l2, layer 2, cache layer, purge
   cache, tiered cache
 namespace: documentation_products_edge_application_l2_caching
 permalink: /documentation/products/build/applications/cache/tiered-cache/

@@ -14,7 +14,7 @@ Azion **Orchestrator** is an end-to-end encrypted orchestration service with clo
 
 With Orchestrator, you can:
 
-- Manage and control edge resources in real time, including provisioning, updating, and managing applications, firewalls, functions, digital certificates, Nodes, Services, and third-party services via Marketplace.
+- Manage and control edge resources in real time, including provisioning, updating, and managing applications, firewalls, functions, certificate manager, Nodes, Services, and third-party services via Marketplace.
 
 - Operate and run on different types of architecture: microprocessors, like x86 and ARM, and different sizes of equipment, including Raspberry PI, network equipment such as switches and SD-WAN routers, as well as corporate servers, because it was designed for it.
 

@@ -165,7 +165,7 @@ The **Applications** data source provides the data from requests made to your [A
 | $upstream_addr | Client IP address and port. Can also store multiple servers or server groups. Example: 192.168.1.1:80. When the response is `127.0.0.1:1666`, the upstream is Azion [Cells Runtime](/en/documentation/runtime/overview/). |
 | $upstream_bytes_received | Number of bytes received by the origin's edge if the content isn't cached. Example: 8304 |
 | $upstream_bytes_sent | Number of bytes sent to the origin. Example: 2733 |
-| $upstream_cache_status | Status of the local edge cache. Example: MISS, BYPASS, EXPIRED, STALE, UPDATING, REVALIDATED, or HIT |
+| $upstream_cache_status | Status of the local cache. Example: MISS, BYPASS, EXPIRED, STALE, UPDATING, REVALIDATED, or HIT |
 | $upstream_connect_time | Time it takes for the edge to establish a connection with the origin, in seconds. In the case of TLS, it includes time spent on handshake. Example: `0.123`. **Returns `0` for KeepAlive and `-` for cache** |
 | $upstream_header_time | Time it takes for the edge to receive the response header from the origin, in seconds. Example: `0.345`. **In case of cache, the response is `-`** |
 | $upstream_response_time | Time it takes for the edge to receive a default response from the origin, in seconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`** |

@@ -100,7 +100,7 @@ Displays the event records from requests made to your [Applications](/en/documen
 | Upstream Addr | Client’s IP address and port. Can also store multiple servers or server groups. Example: `192.168.1.1:80`. When the response is `127.0.0.1:1666`, the upstream is [Azion Cells Runtime](/en/documentation/runtime/overview/). |
 | Upstream Bytes Received | Number of bytes received from the origin by the edge if the content isn’t cached. Example: `8304` |
 | Upstream Bytes Sent | Number of bytes sent to the origin. Example: `2733` |
-| Upstream Cache Status | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| Upstream Cache Status | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | Upstream Response Time | Time it takes for the edge to receive a default response from the origin in seconds, including headers and body. Example: `0.876`. **In case of cache, the response is `-`** |
 | Upstream Status | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `0`** |
 | Waf Block | Informs whether WAF blocked the action or not. `0` when action wasn’t blocked; `1` when action was blocked. When in *Learning Mode*, it won’t be blocked regardless of the return. |
@@ -184,7 +184,7 @@ Displays the event records of requests made to applications using [Image Process
 | SSL Session Reused | Returns `r` if an SSL session was reused or `.` if it wasn't. |
 | Status | HTTP status code of the request. Example: `200` |
 | TCP Info RTT | Round-Trip Time (RTT) in microseconds measured by the edge for the user. Available on systems that support the TCP_INFO socket option. Example: `72052` |
-| Upstream Cache Status | Status of the local edge cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
+| Upstream Cache Status | Status of the local cache. Can be: `MISS`, `BYPASS`, `EXPIRED`, `STALE`, `UPDATING`, `REVALIDATED`, `HIT`, or `-` |
 | Upstream Response Time | Time it takes for the edge to receive a default response from the origin in seconds, including headers and body. This field is the result of a sum. Example: `0.876`. **In case of cache, the response is `-`** |
 | Upstream Status | HTTP status code of the origin. If a server can't be selected, the variable keeps the 502 (Bad Gateway) status code. Example: `200`. **In case of cache, the response is `-`.** |
 

@@ -240,7 +240,7 @@ You can manage **Connectorss** and their configuration through the API using the
   --header 'Authorization: Token [TOKEN VALUE]' \
   --header 'Content-Type: application/json' \
   --data '{
-  "name": "edge storage connector",
+  "name": "object storage connector",
   "active": true,
   "type": "edge_storage",
   "attributes": {