From 0414efd0a9b005db611a557e786f328c3a415b1b Mon Sep 17 00:00:00 2001 From: "gabriel.alves" Date: Tue, 4 Nov 2025 10:50:50 -0300 Subject: [PATCH] Fixing-old-product-names-on-docs-more-files-04-11-25-certificate-manager-edge-storage-edge-cache --- .../compliance/compliance-architecture.mdx | 2 +- .../api-graphql/features/events-fields.mdx | 8 +++--- .../api-graphql/features/metrics-fields.mdx | 8 +++--- .../pages/devtools/azion-lib/usage/utils.mdx | 2 +- .../azion-cli/commands/dev-command/dev.mdx | 2 +- .../cli/azion-cli/config/azion-config-js.mdx | 4 +-- .../en/pages/guides/mtls/configure-mtls.mdx | 4 +-- .../create-blocklists.mdx | 2 +- .../build/edge-application/edge-caching.mdx | 2 +- .../build/edge-application/l2-caching.mdx | 2 +- .../edge-orchestrator/edge-orchestrator.mdx | 2 +- .../observe/data-stream/data-stream.mdx | 2 +- .../real-time-events/real-time-events.mdx | 4 +-- .../reference/secure/api-v4-migration.mdx | 2 +- .../secure/edge-firewall/edge-firewall.mdx | 2 +- .../reference/secure/edge-firewall/mtls.mdx | 2 +- .../network-layer-protection/network-list.mdx | 2 +- .../reference/secure/worklads/workloads.mdx | 2 +- .../work-with-domains/create-certificate.mdx | 2 +- .../store-journey/storage/download-object.mdx | 2 +- .../store-journey/storage/upload-object.mdx | 2 +- .../storage/use-bucket-as-origin.mdx | 28 +++++++++---------- .../api-gateways/api-gateways-security.mdx | 2 +- .../guias/devtools/integrar-com-api/index.mdx | 2 +- .../edge-application/ea-cache-policies.mdx | 2 +- ...uest-lets-encrypt-certificates-via-api.mdx | 2 +- .../use-bucket-as-origin/index.mdx | 12 ++++---- .../edge-storage/use-s3-protocol/index.mdx | 2 +- .../templates/vite-boilerplate.mdx | 2 +- .../pages/guias/mtls/configurar-mtls.mdx | 8 +++--- .../build/edge-application/cache-settings.mdx | 2 +- .../edge-application/digital-certificates.mdx | 6 ++-- .../edge-application/domains/domains.mdx | 4 +-- .../edge-app-primeiros-passos.mdx | 2 +- .../edge-application/edge-application.mdx | 6 ++-- .../build/edge-application/l2-caching.mdx | 2 +- .../v3/edge-application-v3.mdx | 6 ++-- .../referencia/contas/teams-permissions.mdx | 12 ++++---- .../edge-orchestrator/edge-orchestrator.mdx | 2 +- .../referencia/secure/api-v4-migration.mdx | 2 +- .../secure/edge-firewall/edge-firewall.mdx | 2 +- .../network-layer-protection.mdx | 2 +- .../network-lists.mdx | 2 +- .../criar-certificado.mdx | 6 ++-- .../storage/usar-bucket-como-origem.mdx | 26 ++++++++--------- src/i18n/en/nav.ts | 2 +- src/i18n/en/secureMenu.ts | 2 +- src/i18n/en/ui.ts | 4 +-- src/i18n/pt-br/ui.ts | 2 +- .../RulesEngineExecution/en/snippet.mdx | 2 +- .../RulesEngineExecution/pt/snippet.mdx | 2 +- 51 files changed, 108 insertions(+), 108 deletions(-) diff --git a/src/content/docs/en/pages/architectures/compliance/compliance-architecture.mdx b/src/content/docs/en/pages/architectures/compliance/compliance-architecture.mdx index 0d3c4f454d..3073ed3422 100644 --- a/src/content/docs/en/pages/architectures/compliance/compliance-architecture.mdx +++ b/src/content/docs/en/pages/architectures/compliance/compliance-architecture.mdx @@ -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 diff --git a/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx b/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx index 582e375e67..388d812b66 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/features/events-fields.mdx @@ -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 `-`** | diff --git a/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx b/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx index 97da1b9e34..8ce5e7e7d2 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/features/metrics-fields.mdx @@ -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 `-`**. | diff --git a/src/content/docs/en/pages/devtools/azion-lib/usage/utils.mdx b/src/content/docs/en/pages/devtools/azion-lib/usage/utils.mdx index 97b4f2c651..4fb26559be 100644 --- a/src/content/docs/en/pages/devtools/azion-lib/usage/utils.mdx +++ b/src/content/docs/en/pages/devtools/azion-lib/usage/utils.mdx @@ -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:** diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx index e5b89ceaf5..2932153a83 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/dev-command/dev.mdx @@ -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 --- diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/config/azion-config-js.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/config/azion-config-js.mdx index a690e8e58f..ff05772c26 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/config/azion-config-js.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/config/azion-config-js.mdx @@ -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. diff --git a/src/content/docs/en/pages/guides/mtls/configure-mtls.mdx b/src/content/docs/en/pages/guides/mtls/configure-mtls.mdx index bb586cc4a1..b533cc3f47 100644 --- a/src/content/docs/en/pages/guides/mtls/configure-mtls.mdx +++ b/src/content/docs/en/pages/guides/mtls/configure-mtls.mdx @@ -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. diff --git a/src/content/docs/en/pages/guides/network-layer-protection/blacklists-ip-addresses-edge/create-blocklists.mdx b/src/content/docs/en/pages/guides/network-layer-protection/blacklists-ip-addresses-edge/create-blocklists.mdx index c6796e0307..a8dd5829b7 100644 --- a/src/content/docs/en/pages/guides/network-layer-protection/blacklists-ip-addresses-edge/create-blocklists.mdx +++ b/src/content/docs/en/pages/guides/network-layer-protection/blacklists-ip-addresses-edge/create-blocklists.mdx @@ -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/ diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx index 35d94b2b44..04bce97ea4 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx @@ -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/ diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/l2-caching.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/l2-caching.mdx index e199646297..01667f2a00 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/l2-caching.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/l2-caching.mdx @@ -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/ diff --git a/src/content/docs/en/pages/main-menu/reference/deploy/edge-orchestrator/edge-orchestrator.mdx b/src/content/docs/en/pages/main-menu/reference/deploy/edge-orchestrator/edge-orchestrator.mdx index cb1f115830..47c409762f 100644 --- a/src/content/docs/en/pages/main-menu/reference/deploy/edge-orchestrator/edge-orchestrator.mdx +++ b/src/content/docs/en/pages/main-menu/reference/deploy/edge-orchestrator/edge-orchestrator.mdx @@ -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. diff --git a/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx b/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx index 1beeceae5a..f4860482ae 100644 --- a/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx +++ b/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx @@ -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 `-`** | diff --git a/src/content/docs/en/pages/main-menu/reference/observe/real-time-events/real-time-events.mdx b/src/content/docs/en/pages/main-menu/reference/observe/real-time-events/real-time-events.mdx index 252a542913..c81c9234b5 100644 --- a/src/content/docs/en/pages/main-menu/reference/observe/real-time-events/real-time-events.mdx +++ b/src/content/docs/en/pages/main-menu/reference/observe/real-time-events/real-time-events.mdx @@ -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 `-`.** | diff --git a/src/content/docs/en/pages/main-menu/reference/secure/api-v4-migration.mdx b/src/content/docs/en/pages/main-menu/reference/secure/api-v4-migration.mdx index 6aa108b382..0039ba1000 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/api-v4-migration.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/api-v4-migration.mdx @@ -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": { diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-firewall.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-firewall.mdx index 85d944fb4a..c91bfaf6f3 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-firewall.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-firewall.mdx @@ -41,7 +41,7 @@ For more details on the product's accounting, see the [pricing](/en/documentatio | Get to know WAF Custom Allowed Rules | [WAF Custom Allowed Rules](/en/documentation/products/secure/edge-firewall/web-application-firewall/custom-allowed-rules/) | | Get to know Functions | [Functions Instances for Firewall](/en/documentation/products/secure/edge-firewall/edge-functions-instances/) | | Get to know Rules Engine | [Rules Engine for Firewall](/en/documentation/products/secure/edge-firewall/rules-engine/) | -| Get to know Digital Certificates | [Digital Certificates for Secure](/en/documentation/products/secure/edge-firewall/digital-certificates/) | +| Get to know Certificate Manager | [Certificate Manager for Secure](/en/documentation/products/secure/edge-firewall/digital-certificates/) | | DNSSEC Compatibility | [DNSSEC Compatibility](/en/documentation/products/secure/edge-dns/dnssec-compatibility/) | | Create network lists | [How to create IP blocklists with Network Shield](/en/documentation/products/guides/blocklists-ip-addresses-edge/) | | WAF Mode | [How to check your WAF mode](/en/documentation/products/guides/how-to-check-your-waf-mode/) | diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/mtls.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/mtls.mdx index 876c28b403..1d5ab1aceb 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/mtls.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/mtls.mdx @@ -3,7 +3,7 @@ title: Support for mTLS for Secure description: Understand how mTLS works at Azion and why to use it. meta_tags: >- mutual transport layer security, mtls, tls handshake, open banking, - certificates, digital certificates + certificates, certificate manager namespace: documentation_mtls permalink: /documentation/products/secure/firewall/mtls/ --- diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-list.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-list.mdx index c381a1ea40..61476aaf92 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-list.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-list.mdx @@ -3,7 +3,7 @@ title: Network Lists description: >- Discover how Azion's Network Lists provide granular control over network layer protection allowlists, blocklists, and graylists with IPs, ASNs and countries. -meta_tags: 'network layer protection, network list, edge computing, azion, security' +meta_tags: 'network shield, network list, edge computing, azion, security' namespace: documentation_products_edge_firewall_network_lists permalink: >- /documentation/products/secure/edge-firewall/network-layer-protection/network-lists/ diff --git a/src/content/docs/en/pages/main-menu/reference/secure/worklads/workloads.mdx b/src/content/docs/en/pages/main-menu/reference/secure/worklads/workloads.mdx index 1ba18fdc42..847a33cce5 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/worklads/workloads.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/worklads/workloads.mdx @@ -27,7 +27,7 @@ You may also bind a **Digital Certificate** to your workload to enable HTTPS/TLS | Scope | Resource | | --- | --- | | Adding a custom domain | [Getting started](/en/documentation/products/guides/configure-a-domain/) | -| About Digital Certificates | [Digital Certificates](/en/documentation/products/secure/firewall/certificate-manager/) | +| About Certificate Manager | [Certificate Manager](/en/documentation/products/secure/firewall/certificate-manager/) | | About mTLS | [mTLS](/en/documentation/products/secure/edge-firewall/mtls/) | --- diff --git a/src/content/docs/en/pages/main-menu/work-with-domains/create-certificate.mdx b/src/content/docs/en/pages/main-menu/work-with-domains/create-certificate.mdx index ab41718cf1..09d3e9b368 100644 --- a/src/content/docs/en/pages/main-menu/work-with-domains/create-certificate.mdx +++ b/src/content/docs/en/pages/main-menu/work-with-domains/create-certificate.mdx @@ -1,7 +1,7 @@ --- title: How to create a digital certificate description: >- - Digital Certificates are essential for online security, providing + Digital certificates are essential for online security, providing authentication and encryption for your data. meta_tags: 'digital certificate, encryption, TLS, SSL, authentication, security' namespace: docs_guides_create_digital_certificate diff --git a/src/content/docs/en/pages/store-journey/storage/download-object.mdx b/src/content/docs/en/pages/store-journey/storage/download-object.mdx index e7872fc8f4..b0c3aa3590 100644 --- a/src/content/docs/en/pages/store-journey/storage/download-object.mdx +++ b/src/content/docs/en/pages/store-journey/storage/download-object.mdx @@ -4,7 +4,7 @@ description: >- Discover how to download files from an Object Storage bucket with a comprehensive guide. meta_tags: >- - edge storage, cloud storage, s3 bucket, file storage, download files, Azion + object storage, cloud storage, s3 bucket, file storage, download files, Azion Object Storage namespace: documentation_products_store_storage_object_storage_download permalink: /documentation/products/store/storage/download-object/ diff --git a/src/content/docs/en/pages/store-journey/storage/upload-object.mdx b/src/content/docs/en/pages/store-journey/storage/upload-object.mdx index ac167a6f87..0f69cfee4d 100644 --- a/src/content/docs/en/pages/store-journey/storage/upload-object.mdx +++ b/src/content/docs/en/pages/store-journey/storage/upload-object.mdx @@ -2,7 +2,7 @@ title: How to upload an object to an Object Storage bucket description: Discover how to upload files to an Object Storage bucket with this guide. meta_tags: >- - edge storage, cloud storage, s3 bucket, file storage, upload files, Azion Edge + object storage, cloud storage, s3 bucket, file storage, upload files, Azion Edge Storage, object storage namespace: documentation_products_store_storage_object_storage_upload permalink: /documentation/products/store/storage/upload-object/ diff --git a/src/content/docs/en/pages/store-journey/storage/use-bucket-as-origin.mdx b/src/content/docs/en/pages/store-journey/storage/use-bucket-as-origin.mdx index 0686f73468..937ba7b2cb 100644 --- a/src/content/docs/en/pages/store-journey/storage/use-bucket-as-origin.mdx +++ b/src/content/docs/en/pages/store-journey/storage/use-bucket-as-origin.mdx @@ -4,7 +4,7 @@ description: >- Learn how to use a bucket as the origin of a static applications using Object Storage and make the bucket content public. meta_tags: >- - edge storage, storage, cloud, s3, bucket, objects, files, storage, file + object storage, storage, cloud, s3, bucket, objects, files, storage, file storage, origin, object storage namespace: documentation_products_sotre_storage_object_storage_origin permalink: /documentation/products/store/storage/use-bucket-as-origin/ @@ -240,7 +240,7 @@ Once the changes have been made, access `http://xxxxxxxxxx.map.azionedge.net/ind --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage app", + "name": "object storage app", "modules": { "edge_cache": { "enabled": true @@ -271,7 +271,7 @@ Once the changes have been made, access `http://xxxxxxxxxx.map.azionedge.net/ind "state": "pending", "data": { "id": "edge_application_id", - "name": "edge storage app", + "name": "object storage app", "last_editor": "education1@azion.com", "last_modified": "2025-07-25T19:06:13.854005Z", "modules": { @@ -307,7 +307,7 @@ Once the changes have been made, access `http://xxxxxxxxxx.map.azionedge.net/ind --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": { @@ -323,7 +323,7 @@ Once the changes have been made, access `http://xxxxxxxxxx.map.azionedge.net/ind ", - "name": "edge storage connector", + "name": "object storage connector", "last_editor": "your-email@example.com", "last_modified": "2025-07-22T14:34:31.009649Z", "active": true, @@ -343,7 +343,7 @@ Once the changes have been made, access `http://xxxxxxxxxx.map.azionedge.net/ind --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage domain", + "name": "object storage domain", "active": true, "infrastructure": 1, "protocols": { @@ -363,7 +363,7 @@ Once the changes have been made, access `http://xxxxxxxxxx.map.azionedge.net/ind "state": "pending", "data": { "id": "workload_id", - "name": "edge storage domain", + "name": "object storage domain", "active": true, "last_editor": "your-email@example.com", "last_modified": "2025-07-25T18:58:25.817955Z", @@ -502,7 +502,7 @@ Once the changes have been made, access the domain you created, in the format `h --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage app", + "name": "object storage app", "delivery_protocol": "http", "http3": false, "origin_type": "single_origin", @@ -520,7 +520,7 @@ Once the changes have been made, access the domain you created, in the format `h ", - "name": "edge storage app", + "name": "object storage app", "delivery_protocol": "http" ... }, @@ -535,7 +535,7 @@ Once the changes have been made, access the domain you created, in the format `h --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage domain", + "name": "object storage domain", "cname_access_only": false, "digital_certificate_id": null, "edge_application_id": "" @@ -546,7 +546,7 @@ Once the changes have been made, access the domain you created, in the format `h ", - "name": "edge storage domain", + "name": "object storage domain", ... "edge_application_id": "", "is_active": true, @@ -557,14 +557,14 @@ Once the changes have been made, access the domain you created, in the format `h }`} /> 6. Copy the URL in the `domain_name` value and paste it in a text editing app to access later. -7. Run the following `POST` request to create an edge storage origin for the application, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/), `` with the ID of the applications, and the value of `bucket` with the name of the bucket you created: +7. Run the following `POST` request to create an object storage origin for the application, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/), `` with the ID of the applications, and the value of `bucket` with the name of the bucket you created: /origins' \ --header 'Accept: application/json;' \ --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage origin", + "name": "object storage origin", "origin_type": "object_storage", "bucket": "app-origin", "prefix": "/src" @@ -652,7 +652,7 @@ Once the changes have been made, access the domain you created, in the format `h To create an applications with the necessary configurations to use a bucket as origin: - diff --git a/src/content/docs/pt-br/pages/arquiteturas/api-gateways/api-gateways-security.mdx b/src/content/docs/pt-br/pages/arquiteturas/api-gateways/api-gateways-security.mdx index 091ebfd301..7c59e69ea3 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/api-gateways/api-gateways-security.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/api-gateways/api-gateways-security.mdx @@ -63,7 +63,7 @@ Através desse perímetro, você pode implementar soluções como: - Você pode usar o [Azion Console](https://console.azion.com/), a [Azion API](https://api.azion.com/) ou a [Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/) para criar e implantar uma aplicação. - [Defina as configurações principais da aplicação](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/). 3. Associe o [domínio personalizado](/pt-br/documentacao/produtos/guias/configurar-dominio/) do seu API Gateway com sua application. -4. [Crie seus Digital Certificates](/pt-br/documentacao/produtos/guias/criar-certificado-digital/). +4. [Crie seus Certificados Digitais](/pt-br/documentacao/produtos/guias/criar-certificado-digital/). 5. [Crie um firewall](/pt-br/documentacao/produtos/guias/secure/edge-firewall-definir-main-settings/) e selecione o domínio que deseja proteger. - Defina quaisquer [regras WAF](/pt-br/documentacao/produtos/guias/secure/criar-waf-rule-set/), [regras do Rules Engine](/pt-br/documentacao/produtos/secure/edge-firewall/rules-engine/) ou [functions](/pt-br/documentacao/produtos/secure/edge-firewall/edge-functions/) que deseja implementar e instanciar no firewall. - Instale e configure as [Azion Integrations](/pt-br/documentacao/produtos/marketplace/integracoes/) que deseja usar para aprimorar suas políticas de segurança. diff --git a/src/content/docs/pt-br/pages/guias/devtools/integrar-com-api/index.mdx b/src/content/docs/pt-br/pages/guias/devtools/integrar-com-api/index.mdx index d270535302..c376e0d1fa 100644 --- a/src/content/docs/pt-br/pages/guias/devtools/integrar-com-api/index.mdx +++ b/src/content/docs/pt-br/pages/guias/devtools/integrar-com-api/index.mdx @@ -71,7 +71,7 @@ const adapt = (httpResponse) => { field: 'cdnCache', header: 'Cache' }, - // cria a coluna edge cache TTL + // cria a coluna cache TTL { field: 'edgeCacheTtl', header: 'Cache TTL' diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-cache-policies.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-cache-policies.mdx index ce67e1606d..39f8a98deb 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-cache-policies.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-cache-policies.mdx @@ -5,7 +5,7 @@ description: >- do cache do conteúdo na origem e no navegador, ignorar cache da origem, ou enviar cookies para o usuário usando Application Accelerator para Edge Application. -meta_tags: 'edge cache, edge computing, ttl, bypass cache, forward cookies' +meta_tags: 'cache, edge computing, ttl, bypass cache, forward cookies' namespace: docs_use_case_edge_caching permalink: /documentacao/produtos/guias/cache-settings/ og_image: /assets/docs/images/uploads/02-09-edge-caching-1.png diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx index 168dd87984..a5c2f3c6c9 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx @@ -15,7 +15,7 @@ A Azion agora oferece emissão e renovação de [certificados Let's Encrypt](/pt Os certificados são renovados automaticamente antes de expirar, eliminando janelas de manutenção e mantendo as cotas, faturamento e permissões existentes. Perfeito para plataformas de e-commerce e provedores de hospedagem, esse aprimoramento permite um onboarding mais rápido e garante segurança aos sites dos clientes em minutos, sem alterações no DNS. -Para mais informações sobre essas atualizações, visite a documentação de [Digital Certificates](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/). +Para mais informações sobre essas atualizações, visite a documentação de [Certificate Manager](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/). --- diff --git a/src/content/docs/pt-br/pages/guias/edge-storage/use-bucket-as-origin/index.mdx b/src/content/docs/pt-br/pages/guias/edge-storage/use-bucket-as-origin/index.mdx index f26210183e..7e74a82f96 100644 --- a/src/content/docs/pt-br/pages/guias/edge-storage/use-bucket-as-origin/index.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-storage/use-bucket-as-origin/index.mdx @@ -7,7 +7,7 @@ description: >- arquivos estáticos e tornar público o conteúdo do bucket. meta_tags: >- object storage, storage, cloud, s3, bucket, objetos, arquivos, armazenamento, - file storage, origin, origem, edge storage + file storage, origin, origem, object storage namespace: documentation_guides_object_storage_origin permalink: /documentacao/produtos/guias/usar-bucket-como-origem/ --- @@ -203,7 +203,7 @@ curl --location 'https://api.azionapi.net/edge_applications' \ --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage app", + "name": "object storage app", "delivery_protocol": "http", "http3": false, "origin_type": "single_origin", @@ -223,7 +223,7 @@ curl --location 'https://api.azionapi.net/edge_applications' \ { "results": { "id": "", - "name": "edge storage app", + "name": "object storage app", "delivery_protocol": "http" }, "schema_version": 3 @@ -239,7 +239,7 @@ curl --location 'https://api.azionapi.net/domains' \ --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage domain", + "name": "object storage domain", "cname_access_only": false, "digital_certificate_id": null, "edge_application_id": @@ -252,7 +252,7 @@ curl --location 'https://api.azionapi.net/domains' \ { "results": { "id": "", - "name": "edge storage domain", + "name": "object storage domain", // ... "edge_application_id": "", "is_active": true, @@ -272,7 +272,7 @@ curl --location 'https://api.azionapi.net/edge_applications/- você possua para permitir operações específicas para cada acesso verificado com a credencial. meta_tags: >- - object storage, storage, cloud, s3, bucket, file storage, edge storage, s3 + object storage, storage, cloud, s3, bucket, file storage, object storage, s3 protocol namespace: documentation_guides_s3_protocol_edge_storage permalink: /documentacao/produtos/guias/protocolo-s3-para-object-storage/ diff --git a/src/content/docs/pt-br/pages/guias/marketplace/templates/vite-boilerplate.mdx b/src/content/docs/pt-br/pages/guias/marketplace/templates/vite-boilerplate.mdx index 25e5a916d2..05f6766cc4 100644 --- a/src/content/docs/pt-br/pages/guias/marketplace/templates/vite-boilerplate.mdx +++ b/src/content/docs/pt-br/pages/guias/marketplace/templates/vite-boilerplate.mdx @@ -14,7 +14,7 @@ Preview O **Vue3/Vite Boilerplate** acelera a implantação de uma aplicação baseada nesses frameworks diretamente no edge. -Este template implanta um novo stack com uma application contendo um domínio para acessar a Single-Page Application (SPA), bem como configurações de edge storage, configurações de cache e regras do Rules Engine para melhorar o desempenho dos arquivos estáticos. Além disso, ele cria um novo repositório GitHub, incluindo uma GitHub Action para habilitar um fluxo de trabalho de desenvolvimento contínuo e manter sua aplicação atualizada. +Este template implanta um novo stack com uma application contendo um domínio para acessar a Single-Page Application (SPA), bem como configurações de object storage, configurações de cache e regras do Rules Engine para melhorar o desempenho dos arquivos estáticos. Além disso, ele cria um novo repositório GitHub, incluindo uma GitHub Action para habilitar um fluxo de trabalho de desenvolvimento contínuo e manter sua aplicação atualizada. Usa a versão `3.3.4` de Vue e a versão `4.4.6` de Vite. diff --git a/src/content/docs/pt-br/pages/guias/mtls/configurar-mtls.mdx b/src/content/docs/pt-br/pages/guias/mtls/configurar-mtls.mdx index ed2395c73e..356c146954 100644 --- a/src/content/docs/pt-br/pages/guias/mtls/configurar-mtls.mdx +++ b/src/content/docs/pt-br/pages/guias/mtls/configurar-mtls.mdx @@ -30,11 +30,11 @@ Se você não tem certeza de quais etapas se aplicam à sua conta, consulte [o g --- -## Adicione um Trusted CA à sua biblioteca de Digital Certificates +## Adicione um Trusted CA à sua biblioteca de Certificate Manager -Com seu **Trusted CA** criado, é necessário adicioná-lo à sua biblioteca de **Digital Certificates**, em **Edge Libraries**: +Com seu **Trusted CA** criado, é necessário adicioná-lo à sua biblioteca de **Certificate Manager**, em **Edge Libraries**: -1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Digital Certificates**, na seção **Edge Libraries**. +1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Certificate Manager**, na seção **Edge Libraries**. 2. Clique no botão **+ Digital Certificate**. 3. Na página de cadastro de novos certificados, defina um nome de identificação para este certificado no campo **Name**. 4. Na seção **Import or Request Certificate**, selecione a opção **Import a Trusted CA certificate**. @@ -42,7 +42,7 @@ Com seu **Trusted CA** criado, é necessário adicioná-lo à sua biblioteca de - O arquivo do certificado precisa ser do tipo `.pem` Privacy Enhanced Mail (PEM). Exemplo: `certificado.pem`. 6. Clique no botão *Save* para prosseguir. -Você será redirecionado para a página **Digital Certificates**, onde estarão listados todos os seus certificados, incluindo este recém-adicionado. +Você será redirecionado para a página **Certificate Manager**, onde estarão listados todos os seus certificados, incluindo este recém-adicionado. --- diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/cache-settings.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/cache-settings.mdx index d447f20c0f..f4c7a2058d 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/cache-settings.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/cache-settings.mdx @@ -3,7 +3,7 @@ title: Cache Settings description: >- Configure o TTL do cache, fragmentação de arquivos grandes, entrega adaptável e regras de cache para sua aplicação. -meta_tags: 'cache settings, edge cache, edge, application' +meta_tags: 'cache settings, cache, edge, application' namespace: documentation_products_edge_application_cache_settings permalink: /documentacao/produtos/build/applications/cache-settings/ --- diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/digital-certificates.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/digital-certificates.mdx index a43807da9c..e15abc026c 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/digital-certificates.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/digital-certificates.mdx @@ -2,8 +2,8 @@ title: Certificate Manager para Build description: >- Você pode conectar um certificado TLS para suas applications que usam o - protocolo HTTPS através do Digital Certificates da Azion. -meta_tags: 'Digital Certificates, edge computing' + protocolo HTTPS através do Certificate Manager da Azion. +meta_tags: 'Certificate Manager, edge computing' namespace: documentation_products_edge_applications_digital_certificates permalink: /documentacao/produtos/build/applications/certificate-manager/ --- @@ -87,7 +87,7 @@ Uma Trusted CA é uma entidade autorizada a emitir certificados digitais que pod [Let's Encrypt](https://letsencrypt.org/)™ é uma CA que permite que indivíduos e empresas obtenham, renovem e gerenciem certificados TLS gratuitamente. Quando você [cria um Domínio](/pt-br/documentacao/produtos/build/applications/domains/) com a Azion, você pode escolher obter um um certificado TLS assinado pela Let's Encrypt. Você pode requisitar a criação de certificados Let's Encrypt certificates para domínios hospedados no [Edge DNS](/pt-br/documentacao/produtos/secure/edge-dns/) ou em um provedor de DNS externo. -Quando você [cria um domínio com a Azion](/pt-br/documentacao/produtos/guias/configurar-dominio/), você pode escolher a opção **Let's Encrypt** para gerar automaticamente um certificado Let's Encrypt. Uma entrada para esse certificado será listada na página **Digital Certificates** [no Azion Console](https://console.azion.com). Depois que o certificado for submetido à validação, emissão e armazenamento do DNS, ele se tornará ativo. +Quando você [cria um domínio com a Azion](/pt-br/documentacao/produtos/guias/configurar-dominio/), você pode escolher a opção **Let's Encrypt** para gerar automaticamente um certificado Let's Encrypt. Uma entrada para esse certificado será listada na página **Certificate Manager** [no Azion Console](https://console.azion.com). Depois que o certificado for submetido à validação, emissão e armazenamento do DNS, ele se tornará ativo. > Consulte o guia [Como gerar um certificado Let's Encrypt para o seu domínio](/pt-br/documentacao/produtos/guias/como-gerar-um-certificado-lets-encrypt/) para saber como validar esse tipo de certificado. diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/domains/domains.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/domains/domains.mdx index 80f66bc668..cb0efc188f 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/domains/domains.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/domains/domains.mdx @@ -28,7 +28,7 @@ Você também pode vincular um certificado digital a domínios que usam o protoc | Escopo | Recurso | | --- | --- | | Adicionar um domínio personalizado | [Como configurar um domínio](/pt-br/documentacao/produtos/guias/configurar-dominio/) | -| Sobre Digital Certificates | [Digital Certificates](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/) | +| Sobre Certificate Manager | [Certificate Manager](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/) | | Sobre mTLS | [mTLS](/pt-br/documentacao/produtos/secure/edge-firewall/mtls/) | --- @@ -54,7 +54,7 @@ O **limite padrão** é *50* CNAMEs por domínio. No entanto, você pode aumenta --- -## Digital Certificates +## Certificate Manager Para utilizar seu domínio em HTTPS, você precisará de um certificado TLS (X.509). Você pode, sem custos adicionais, incluir seus certificados TLS no [Azion Console](https://console.azion.com) ou gerar um certificado *Let's Encrypt*™ que será gerenciado automaticamente pela Azion. diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-app-primeiros-passos.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-app-primeiros-passos.mdx index 28eaa1df56..713dc009e9 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-app-primeiros-passos.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-app-primeiros-passos.mdx @@ -1,7 +1,7 @@ --- title: Applications primeiros passos description: See the first steps for Applications. -meta_tags: 'application, web, api, cache, edge cache, edge computing, build' +meta_tags: 'application, web, api, cache, cache, edge computing, build' namespace: documentation_products_edge_application_first_steps permalink: /documentacao/produtos/build/applications/primeiros-passos/ --- diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-application.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-application.mdx index a95f1c562b..23cc91131e 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-application.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/edge-application.mdx @@ -100,11 +100,11 @@ Com o **Workloads** você pode configurar as opções de protocolo de entrega, i --- -## Digital Certificates +## Certificate Manager -Com **Digital Certificates**, você pode aprimorar a segurança de seus aplicativos HTTPS vinculando um certificado TLS personalizado à sua application. +Com **Certificate Manager**, você pode aprimorar a segurança de seus aplicativos HTTPS vinculando um certificado TLS personalizado à sua application. - + --- diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/l2-caching.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/l2-caching.mdx index 6f2089b519..ead98605d1 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/l2-caching.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/l2-caching.mdx @@ -5,7 +5,7 @@ description: >- servidores de origem, reduzindo efetivamente a latência e minimizando as despesas com infraestrutura. 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 namespace: documentation_products_edge_application_l2_caching permalink: /documentacao/produtos/build/applications/cache/tiered-cache/ diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/v3/edge-application-v3.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/v3/edge-application-v3.mdx index ff490faf03..2ab7a724d7 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/v3/edge-application-v3.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/build/edge-application/v3/edge-application-v3.mdx @@ -103,11 +103,11 @@ Azion **Domains** oferece a flexibilidade de usar domínios gerados automaticame --- -## Digital Certificates +## Certificate Manager -Com **Digital Certificates**, você pode aprimorar a segurança de seus aplicativos HTTPS vinculando um certificado TLS personalizado à sua application. +Com **Certificate Manager**, você pode aprimorar a segurança de seus aplicativos HTTPS vinculando um certificado TLS personalizado à sua application. - + --- diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx index 265df9ab5a..b1133a1215 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx @@ -57,12 +57,12 @@ Nesta tabela, você encontra o que cada permissão concede acesso: | Edit Firewall | Ele concede permissão para visualizar, criar, editar e remover firewalls. Também requer a permissão **View Firewall**. | | View Functions | Concede permissão para visualizar domínios existentes, mas não permite criação, remoção ou modificações. | | Edit Functions | Concede permissão para criar, editar e remover functions. Também requer a permissão **View Functions**. | -| View Storage Bucket | Concede permissão para visualizar Edge Storage buckets usando a API da Azion. | -| Edit Storage Bucket | Concede permissão para criar e editar Edge Storage buckets usando a API da Azion. | -| Delete Storage Bucket | Concede permissão para remover Edge Storage buckets usando a API da Azion. | -| View Storage Object | Concede permissão para visualizar os metadados de objetos e fazer o download de objetos de Edge Storage buckets usando a API da Azion. | -| Edit Storage Object | Concede permissão para criar e editar objetos em Edge Storage buckets usando a API da Azion. | -| Delete Storage Object | Concede permissão para remover objetos usando de Edge Storage buckets usando a API da Azion. | +| View Storage Bucket | Concede permissão para visualizar Object storage buckets usando a API da Azion. | +| Edit Storage Bucket | Concede permissão para criar e editar Object storage buckets usando a API da Azion. | +| Delete Storage Bucket | Concede permissão para remover Object storage buckets usando a API da Azion. | +| View Storage Object | Concede permissão para visualizar os metadados de objetos e fazer o download de objetos de Object storage buckets usando a API da Azion. | +| Edit Storage Object | Concede permissão para criar e editar objetos em Object storage buckets usando a API da Azion. | +| Delete Storage Object | Concede permissão para remover objetos usando de Object storage buckets usando a API da Azion. | | View client list | Concede permissão para visualizar a lista de clientes. Não permite a criação, modificação ou remoção de clientes. O recurso Clients está disponível apenas para contas do tipo Grupo. | | Change clients | Concede permissão para criar, editar ou remover clientes. Também requer a permissão **View Client list**. | | View SQL Database | Concede permissão para visualizar os bancos de dados criados e seu conteúdo usando a API da Azion. | diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/deploy/edge-orchestrator/edge-orchestrator.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/deploy/edge-orchestrator/edge-orchestrator.mdx index 4ccb4396f7..17d8c8f856 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/deploy/edge-orchestrator/edge-orchestrator.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/deploy/edge-orchestrator/edge-orchestrator.mdx @@ -13,7 +13,7 @@ Azion **Orchestrator** é um serviço de orquestração criptografada de ponta a Com o Orchestrator, você pode: -- Gerenciar e controlar recursos Edge em tempo real, o que inclui: provisionamento, atualização e gerenciamento de Applications, Firewalls, Functions, Digital Certificates, Edge Nodes, Services e serviços de terceiros via Marketplace. +- Gerenciar e controlar recursos Edge em tempo real, o que inclui: provisionamento, atualização e gerenciamento de Applications, Firewalls, Functions, Certificate Manager, Edge Nodes, Services e serviços de terceiros via Marketplace. - Abrir e executar em vários tipos de arquiteturas, como microprocessadores como x86 e ARM, e em vários tipos de tamanho de equipamento, incluindo Raspberry PI, equipamentos de rede como switches e roteadores SD-WAN e também servidores corporativos, pois foi projetado para isso. - Usar na maioria das arquiteturas de rede, incluindo redes locais e públicas, e também por trás de NATs. - Simplificar a instalação e atualização do software, pois é compilado com todas as dependências do núcleo e de bibliotecas. diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx index 3d2fcdd0cc..b581d9958e 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx @@ -237,7 +237,7 @@ Você pode gerenciar **Connectors** e suas configurações pela API utilizando o --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ -- '{ - "name": "edge storage connector", + "name": "object storage connector", "active": true, "type": "edge_storage", "attributes": { diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/edge-firewall.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/edge-firewall.mdx index 0ec3cdef64..8f0cb2494a 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/edge-firewall.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/edge-firewall.mdx @@ -40,7 +40,7 @@ Para detalhes sobre a contabilização do produto, acesse a página de [preços] | Saiba mais sobre WAF Custom Allowed Rules | [WAF Custom Allowed Rules](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/custom-allowed-rules/) | | Saiba mais sobre Functions | [Functions Instances para Firewall](/pt-br/documentacao/produtos/secure/firewall/functions-instances/) | | Saiba mais sobre Rules Engine | [Rules Engine para Firewall](/pt-br/documentacao/produtos/secure/firewall/rules-engine/) | -| Saiba mais sobre Digital Certificates | [Digital Certificates para Secure](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/) | +| Saiba mais sobre Certificate Manager | [Certificate Manager para Secure](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/) | | Compatibilidade com DNSSEC | [Compatibilidade com DNSSEC](/pt-br/documentacao/produtos/secure/edge-dns/compatibilidade-dnssec/) | | Criar network lists | [Como criar blocklists de IP com Network Shield](/pt-br/documentacao/produtos/guias/blocklists-enderecos-ip-edge/) | | Modo do WAF | [Como verificar o seu modo WAF](/pt-br/documentacao/produtos/guias/como-verificar-modo-do-seu-waf/) | diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx index 9c4763a091..b79c38a94c 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx @@ -4,7 +4,7 @@ description: >- Network Shield da Azion permite a criação de Network Lists com base na rede (IP/CIDR), geolocalização e ASN. meta_tags: >- - network layer protection, security, edge computing, azion, firewall, + network shield, security, edge computing, azion, firewall, firewall namespace: documentation_products_network_layer_protection permalink: /documentacao/produtos/secure/firewall/network-shield/ diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-lists.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-lists.mdx index ca13650f77..8325821767 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-lists.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/network-layer-protection/network-lists.mdx @@ -1,7 +1,7 @@ --- title: Network Lists description: 'Crie e gerencie allowlists, blocklists e graylists com Network Lists.' -meta_tags: 'network layer protection, network list, edge computing, azion, security' +meta_tags: 'network shield, network list, edge computing, azion, security' namespace: documentation_products_edge_firewall_network_lists permalink: >- /documentacao/produtos/secure/firewall/network-shield/network-lists/ diff --git a/src/content/docs/pt-br/pages/menu-principal/trabalhe-com-dominios/criar-certificado.mdx b/src/content/docs/pt-br/pages/menu-principal/trabalhe-com-dominios/criar-certificado.mdx index 50824d3679..ac45fe0285 100644 --- a/src/content/docs/pt-br/pages/menu-principal/trabalhe-com-dominios/criar-certificado.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/trabalhe-com-dominios/criar-certificado.mdx @@ -14,7 +14,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/pt/snippet.mdx' -Se sua aplicação roda em HTTPS, você precisa cadastrar um certificado digital com Azion [Digital Certificates](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/). Um certificado digital TLS confirma a identidade de um site e protege as transferências de dados. Ele garante transações financeiras e qualquer troca de informações sensíveis, desde credenciais de login até dados pessoais. +Se sua aplicação roda em HTTPS, você precisa cadastrar um certificado digital com Azion [Certificate Manager](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/). Um certificado digital TLS confirma a identidade de um site e protege as transferências de dados. Ele garante transações financeiras e qualquer troca de informações sensíveis, desde credenciais de login até dados pessoais. Você também pode solicitar que um **certificado Let's Encrypt** seja gerado para o seu domínio através da Azion. O processo para solicitar um certificado Let's Encrypt é diferente dos certificados personalizados. Consulte [como gerar um certificado Let's Encrypt](/pt-br/documentacao/produtos/guias/como-gerar-um-certificado-lets-encrypt/) para mais informações. @@ -38,7 +38,7 @@ Se você não tem certeza de quais passos se aplicam à sua conta, consulte [o g API -1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Digital Certificates**. +1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Certificate Manager**. 2. Clique no botão **+ Digital Certificate**. 3. Nomeie seu certificado. 4. Selecione a opção **Import a server certificate**. @@ -104,7 +104,7 @@ Ao fazer o upload de seu certificado, você receberá uma resposta confirmando a -1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Digital Certificates**. +1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Certificate Manager**. 2. Clique no botão **+ Digital Certificate**. 3. Nomeie seu certificado. 4. Selecione a opção **Import a Trusted CA certificate**. diff --git a/src/content/docs/pt-br/pages/store-jornada/storage/usar-bucket-como-origem.mdx b/src/content/docs/pt-br/pages/store-jornada/storage/usar-bucket-como-origem.mdx index de46e7fe9b..b2cd021ac7 100644 --- a/src/content/docs/pt-br/pages/store-jornada/storage/usar-bucket-como-origem.mdx +++ b/src/content/docs/pt-br/pages/store-jornada/storage/usar-bucket-como-origem.mdx @@ -4,7 +4,7 @@ description: >- Aprenda a usar um bucket como a origem de uma application estática usando Object Storage e a tornar o conteúdo do bucket público. meta_tags: >- - edge storage, storage, cloud, s3, bucket, objects, files, storage, file + object storage, storage, cloud, s3, bucket, objects, files, storage, file storage, origin, object storage namespace: documentation_products_sotre_storage_object_storage_origin permalink: /documentacao/produtos/store/storage/usar-bucket-como-origin/ @@ -249,7 +249,7 @@ Uma vez que as alterações tenham sido feitas, acesse `http://xxxxxxxxxx.map.az --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage app", + "name": "object storage app", "modules": { "edge_cache": { "enabled": true @@ -280,7 +280,7 @@ Uma vez que as alterações tenham sido feitas, acesse `http://xxxxxxxxxx.map.az "state": "pending", "data": { "id": "edge_application_id", - "name": "edge storage app", + "name": "object storage app", "last_editor": "education1@azion.com", "last_modified": "2025-07-25T19:06:13.854005Z", "modules": { @@ -316,7 +316,7 @@ Uma vez que as alterações tenham sido feitas, acesse `http://xxxxxxxxxx.map.az --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": { @@ -332,7 +332,7 @@ Uma vez que as alterações tenham sido feitas, acesse `http://xxxxxxxxxx.map.az ", - "name": "edge storage connector", + "name": "object storage connector", "last_editor": "your-email@example.com", "last_modified": "2025-07-22T14:34:31.009649Z", "active": true, @@ -352,7 +352,7 @@ Uma vez que as alterações tenham sido feitas, acesse `http://xxxxxxxxxx.map.az --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage domain", + "name": "object storage domain", "active": true, "infrastructure": 1, "protocols": { @@ -372,7 +372,7 @@ Uma vez que as alterações tenham sido feitas, acesse `http://xxxxxxxxxx.map.az "state": "pending", "data": { "id": "workload_id", - "name": "edge storage domain", + "name": "object storage domain", "active": true, "last_editor": "your-email@example.com", "last_modified": "2025-07-25T18:58:25.817955Z", @@ -512,7 +512,7 @@ curl --location 'https://api.azionapi.net/edge_applications' \ --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage app", + "name": "object storage app", "delivery_protocol": "http", "http3": false, "origin_type": "single_origin", @@ -532,7 +532,7 @@ curl --location 'https://api.azionapi.net/edge_applications' \ { "results": { "id": , - "name": "edge storage app", + "name": "object storage app", "delivery_protocol": "http" ... }, @@ -549,7 +549,7 @@ curl --location 'https://api.azionapi.net/domains' \ --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{ - "name": "edge storage domain", + "name": "object storage domain", "cname_access_only": false, "digital_certificate_id": null, "edge_application_id": @@ -562,7 +562,7 @@ curl --location 'https://api.azionapi.net/domains' \ { "results": { "id": , - "name": "edge storage domain", + "name": "object storage domain", ... "edge_application_id": , "is_active": true, @@ -582,7 +582,7 @@ curl --location 'https://api.azionapi.net/edge_applications/ diff --git a/src/i18n/en/nav.ts b/src/i18n/en/nav.ts index d472dfe6ca..af07ed78a7 100644 --- a/src/i18n/en/nav.ts +++ b/src/i18n/en/nav.ts @@ -469,7 +469,7 @@ export default [ key: 'mtls', }, { - text: 'Manage Digital Certificates', + text: 'Certificate Manager', header: true, anchor: true, type: 'learn', diff --git a/src/i18n/en/secureMenu.ts b/src/i18n/en/secureMenu.ts index 73347342f9..e29dd3d503 100644 --- a/src/i18n/en/secureMenu.ts +++ b/src/i18n/en/secureMenu.ts @@ -48,7 +48,7 @@ export default [ { text: 'Select TLS ciphers', header: true, anchor: true, type: 'learn', slug: '/documentation/products/guides/secure/ciphers/', key: 'ciphers', hasLabel: 'menu.secureTransportLayerSecurity' }, { text: 'Configure mTLS', header: true, anchor: true, type: 'learn', slug: '/documentation/products/guides/secure/mtls/', key: 'mtls' }, - { text: 'Manage Digital Certificates', header: true, anchor: true, type: 'learn', slug: '/documentation/products/guides/secure/digital-certificates/', key: 'digitalCertificates' }, + { text: 'Certificate Manager', header: true, anchor: true, type: 'learn', slug: '/documentation/products/guides/secure/digital-certificates/', key: 'digitalCertificates' }, { text: 'Functions', header: true, anchor: true, type: 'learn', slug: '/documentation/products/secure/automate/functions/', key: 'automateEdgeFunctions', hasLabel: 'menu.secureAutomate' }, diff --git a/src/i18n/en/ui.ts b/src/i18n/en/ui.ts index 6c9707080a..e70f24de44 100644 --- a/src/i18n/en/ui.ts +++ b/src/i18n/en/ui.ts @@ -144,7 +144,7 @@ export default { 'menu.cli': 'Azion CLI', 'menu.devTools': 'Dev Tools', 'menu.secure': 'Secure', - 'menu.edgeFirewall': 'Edge Firewall', + 'menu.edgeFirewall': 'Firewall', 'menu.intelligentDns': 'Edge DNS', 'menu.secureAdvanced': 'Advanced configuration', 'menu.secureTransportLayerSecurity': 'Transport Layer Security', @@ -167,7 +167,7 @@ export default { 'menu.runtime': 'Azion Runtime', 'menu.store': 'Store', 'menu.storage': 'Object Storage', - 'menu.edgeSQL': 'Edge SQL' + 'menu.edgeSQL': 'SQL Database' }; diff --git a/src/i18n/pt-br/ui.ts b/src/i18n/pt-br/ui.ts index 4723966da0..87c57ccf74 100644 --- a/src/i18n/pt-br/ui.ts +++ b/src/i18n/pt-br/ui.ts @@ -134,7 +134,7 @@ export default UIDictionary({ 'menu.cli': 'Azion CLI', 'menu.devTools': 'Dev Tools', 'menu.secure': 'Secure', - 'menu.edgeFirewall': 'Edge Firewall', + 'menu.edgeFirewall': 'Firewall', 'menu.intelligentDns': 'Edge DNS', 'menu.secureAdvanced': 'Configurações avançadas', 'menu.secureTransportLayerSecurity': 'Transport Layer Security', diff --git a/src/includes/snippets/RulesEngineExecution/en/snippet.mdx b/src/includes/snippets/RulesEngineExecution/en/snippet.mdx index ff4f393aa2..acc2095084 100644 --- a/src/includes/snippets/RulesEngineExecution/en/snippet.mdx +++ b/src/includes/snippets/RulesEngineExecution/en/snippet.mdx @@ -1,6 +1,6 @@ While behaviors and rules are executed in the order they're arranged, some behaviors can't be stacked. -If a behavior of the type **Set**, such as **Set Custom Response** in Edge Firewall and **Set Origin** in Applications, is added multiple times to the rules in Rules Engine, only the last behavior from the last rule in which the criteria was met will be executed. +If a behavior of the type **Set**, such as **Set Custom Response** in Firewall and **Set Origin** in Applications, is added multiple times to the rules in Rules Engine, only the last behavior from the last rule in which the criteria was met will be executed. Behaviors of the type **Add** are cumulative and can be added multiple times to rules. This means that if **Add Cookie** and **Add Header** are executed multiple times for the same key-value pairs, multiple identical entries will be added. diff --git a/src/includes/snippets/RulesEngineExecution/pt/snippet.mdx b/src/includes/snippets/RulesEngineExecution/pt/snippet.mdx index 8a8c628044..fee7394f8a 100644 --- a/src/includes/snippets/RulesEngineExecution/pt/snippet.mdx +++ b/src/includes/snippets/RulesEngineExecution/pt/snippet.mdx @@ -1,6 +1,6 @@ Enquanto behaviors e regras são executados na ordem em que são distribuidos, alguns tipos de behaviors não podem ser encadeados. -Se um behavior do tipo **Set**, como **Set Custom Response** no Edge Firewall ou **Set Origin** no Applications, for adicionado múltiplas vezes a regras no Rules Engine, apenas o último behavior da última regra na qual o criteria foi atendido será executado. +Se um behavior do tipo **Set**, como **Set Custom Response** no Firewall ou **Set Origin** no Applications, for adicionado múltiplas vezes a regras no Rules Engine, apenas o último behavior da última regra na qual o criteria foi atendido será executado. Behaviors do tipo **Add** são cumulativos e podem ser adicionados várias vezes às regras. Isso significa que se **Add Cookie** e **Add Header** forem executados várias vezes para os mesmos pares key-value, múltiplas entradas idênticas serão adicionadas.