diff --git a/src/content/docs/en/homes/build-home.mdx b/src/content/docs/en/homes/build-home.mdx index 0d7ea1290e..63cd988a14 100644 --- a/src/content/docs/en/homes/build-home.mdx +++ b/src/content/docs/en/homes/build-home.mdx @@ -15,7 +15,7 @@ product_cards: description: >- Applications allows you to build your web applications to run on Azion Web Platform. - link: /en/documentation/products/build/edge-application/ + link: /en/documentation/products/build/applications/ - title: Modules cards: - icon: /assets/docs/images/uploads/app-aceleration.svg @@ -24,32 +24,32 @@ product_cards: Speed ​​up the performance of your applications and APIs with protocol optimizations and advanced caching rules. link: >- - /en/documentation/products/build/edge-application/application-accelerator/ + /en/documentation/products/build/applications/application-accelerator/ - icon: /assets/docs/images/uploads/edge-caching.svg title: Cache description: >- Turbocharge delivery by caching content at the edge of the network, closer to your users. - link: /en/documentation/products/build/edge-application/edge-cache/ + link: /en/documentation/products/build/applications/cache/ - icon: /assets/docs/images/uploads/edge-functions.svg title: Functions description: >- Create event-driven, serverless applications, at the edge of the network, closer to users. - link: /en/documentation/products/build/edge-application/edge-functions/ + link: /en/documentation/products/build/applications/functions/ - icon: /assets/docs/images/uploads/image-processor.svg title: Image Processor description: >- Optimize, convert, and manipulate your images just-in-time to enhance the user experience. - link: /en/documentation/products/build/edge-application/image-processor/ + link: /en/documentation/products/build/applications/image-processor/ - icon: /assets/docs/images/uploads/load-balancer.svg title: Load Balancer description: >- Balance loads on your servers and across any cloud provider to boost the reliability and availability of your content, applications, and APIs. - link: /en/documentation/products/secure/edge-connector/load-balancer/ + link: /en/documentation/products/secure/connectors/load-balancer/ - title: Resources cards: - icon: /assets/docs/images/uploads/icon-guides.svg @@ -58,4 +58,3 @@ product_cards: link: /en/documentation/products/guides/ permalink: /documentation/products/build/ --- - diff --git a/src/content/docs/en/homes/deliver-home.mdx b/src/content/docs/en/homes/deliver-home.mdx index 64560d8ce0..8f0ee4ca59 100644 --- a/src/content/docs/en/homes/deliver-home.mdx +++ b/src/content/docs/en/homes/deliver-home.mdx @@ -16,7 +16,7 @@ product_cards: description: >- Bring your applications closer to your users and devices by distributing them on Azion’s edge or on your own edge. - link: /en/documentation/products/deploy/edge-orchestrator/ + link: /en/documentation/products/deploy/orchestrator/ - title: Resources cards: - icon: /assets/docs/images/uploads/icon-guides.svg @@ -25,4 +25,3 @@ product_cards: link: /en/documentation/products/guides/ permalink: /documentation/products/deploy/ --- - diff --git a/src/content/docs/en/homes/secure-home.mdx b/src/content/docs/en/homes/secure-home.mdx index 17c375f5a7..c15dbc9b9e 100644 --- a/src/content/docs/en/homes/secure-home.mdx +++ b/src/content/docs/en/homes/secure-home.mdx @@ -13,7 +13,7 @@ product_cards: - icon: /assets/docs/images/uploads/edge-firewall.svg title: Firewall description: Protect your application from the network to the application layer. - link: /en/documentation/products/secure/edge-firewall/ + link: /en/documentation/products/secure/firewall/ - icon: /assets/docs/images/uploads/edge-dns.svg title: Edge DNS description: >- @@ -27,21 +27,21 @@ product_cards: description: >- Mitigate the largest and most complex network and transport-layer DDoS attacks. - link: /en/documentation/products/secure/edge-firewall/ddos-protection/ + link: /en/documentation/products/secure/firewall/ddos-protection/ - icon: /assets/docs/images/uploads/network-layer-protection.svg title: Network Shield description: >- Get protection from a programmable security perimeter for inbound and outbound traffic at the edge. link: >- - /en/documentation/products/secure/edge-firewall/network-layer-protection/ + /en/documentation/products/secure/firewall/network-shield/ - icon: /assets/docs/images/uploads/waf-rules.svg title: Web Application Firewall description: >- Secure your web application from OWASP Top 10 threats to sophisticated zero-day attacks. link: >- - /en/documentation/products/secure/edge-firewall/web-application-firewall/ + /en/documentation/products/secure/firewall/web-application-firewall/ - title: Resources cards: - icon: /assets/docs/images/uploads/icon-guides.svg @@ -50,4 +50,3 @@ product_cards: link: /en/documentation/products/guides/ permalink: /documentation/products/secure/ --- - diff --git a/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx b/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx index ce237ea191..82f2e03ce9 100644 --- a/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx +++ b/src/content/docs/en/pages/architectures/api-gateways/api-gateways-security.mdx @@ -45,12 +45,12 @@ Through this perimeter, you can implement solutions such as: ### Components -- [Applications](/en/documentation/products/build/edge-application/): allows you to set up an application to configure delivery and cache policies. -- [Firewall](/en/documentation/products/secure/edge-firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. - - [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. - - [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. - - [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. - - [Functions for Firewall](/en/documentation/products/secure/edge-firewall/edge-functions/): build event-driven, serverless applications including functions with your own security source code. +- [Applications](/en/documentation/products/build/applications/): allows you to set up an application to configure delivery and cache policies. +- [Firewall](/en/documentation/products/secure/firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. + - [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. + - [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. + - [Network Shield](/en/documentation/products/secure/firewall/network-shield/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. + - [Functions for Firewall](/en/documentation/products/secure/firewall/functions/): build event-driven, serverless applications including functions with your own security source code. - [Marketplace Integrations](/en/documentation/products/marketplace/integrations/): function-based functionalities to compose and improve your applications, enforcing security policies. - [Data Stream](/en/documentation/products/observe/data-stream/) and [Real-Time Events](/en/documentation/products/observe/real-time-events/) enable you to monitor all API Gateway activity. @@ -64,8 +64,8 @@ Through this perimeter, you can implement solutions such as: - [Configure the application's main settings](/en/documentation/products/guides/build/configure-main-settings/). 3. Associate your API Gateway [custom domain](/en/documentation/products/guides/configure-a-domain/) with the application. 4. [Create your Digital Certificate](/en/documentation/products/guides/create-a-digital-certificate/). -5. [Create a firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) and select the domain you want to protect. - - Define any [WAF rules](/en/documentation/products/guides/secure/create-waf-rule-set/), [Rules Engine rules](/en/documentation/products/secure/edge-firewall/rules-engine/), or [Functions](/en/documentation/products/secure/edge-firewall/edge-functions/) you want to implement and instantiate in the firewall. +5. [Create a firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) and select the domain you want to protect. + - Define any [WAF rules](/en/documentation/products/guides/secure/create-waf-rule-set/), [Rules Engine rules](/en/documentation/products/secure/firewall/rules-engine/), or [Functions](/en/documentation/products/secure/firewall/functions/) you want to implement and instantiate in the firewall. - Install and configure the [Azion Integrations](/en/documentation/products/marketplace/integrations/) you want to use to enhance your security policies. 6. [Monitor your API Gateway behavior](/en/documentation/products/observe/overview/) through the Observe products. diff --git a/src/content/docs/en/pages/architectures/artificial-intelligence/ai-agent-copilot.mdx b/src/content/docs/en/pages/architectures/artificial-intelligence/ai-agent-copilot.mdx index 286224f80e..91418437a6 100644 --- a/src/content/docs/en/pages/architectures/artificial-intelligence/ai-agent-copilot.mdx +++ b/src/content/docs/en/pages/architectures/artificial-intelligence/ai-agent-copilot.mdx @@ -37,9 +37,9 @@ Considering the implementation of a ReAct agent in an Edge Computing Platform, t ### Components -- [Applications](/en/documentation/products/build/edge-application/): allows you to build applications that run in Azion Global Infrastructure. - - [Functions for Applications](/en/documentation/products/build/edge-application/edge-functions/): executes code closer to the end user, enhancing performance and enabling custom logic for handling requests and responses.- [SQL Database](/en/documentation/products/store/edge-sql/): an edge-native SQL solution designed for serverless applications. - - [Vector Search](/en/documentation/products/store/edge-sql/vector-search/): enables customers to implement semantic search engines. +- [Applications](/en/documentation/products/build/applications/): allows you to build applications that run in Azion Global Infrastructure. + - [Functions for Applications](/en/documentation/products/build/applications/functions/): executes code closer to the end user, enhancing performance and enabling custom logic for handling requests and responses.- [SQL Database](/en/documentation/products/store/sql-database/): an edge-native SQL solution designed for serverless applications. + - [Vector Search](/en/documentation/products/store/sql-database/vector-search/): enables customers to implement semantic search engines. - [Global Infrastructure](https://www.azion.com/en/products/our-network/): a highly distributed architecture that includes strategically located edge nodes. --- @@ -48,8 +48,8 @@ Considering the implementation of a ReAct agent in an Edge Computing Platform, t 1. Create an [application](/en/documentation/products/guides/build/build-an-application/). 2. Create the [SQL database](/en/documentation/products/store/sql/create-database/) that will be consulted. -3. [Create a function](/en/documentation/products/build/edge-application/edge-functions/#implementation) with your AI Agent's logic and [instantiate](/en/documentation/products/guides/build/instantiate-edge-functions/) it in the application. -4. Implement [Vector Search](/en/documentation/products/guides/edge-sql-vector-search/). +3. [Create a function](/en/documentation/products/build/applications/functions/#implementation) with your AI Agent's logic and [instantiate](/en/documentation/products/guides/build/instantiate-functions/) it in the application. +4. Implement [Vector Search](/en/documentation/products/guides/sql-database-vector-search/). 5. You can monitor your AI Agent through [Azion Observe products](/en/documentation/products/observe/overview/) and specialized tools such as LangGraph. --- diff --git a/src/content/docs/en/pages/architectures/bot-management/bot-management-architecture.mdx b/src/content/docs/en/pages/architectures/bot-management/bot-management-architecture.mdx index 47eeb956c3..dece44eb40 100644 --- a/src/content/docs/en/pages/architectures/bot-management/bot-management-architecture.mdx +++ b/src/content/docs/en/pages/architectures/bot-management/bot-management-architecture.mdx @@ -39,10 +39,10 @@ This solution is ideal for organizations looking to mitigate security risks, pre ### Components -- [Firewall](/en/documentation/products/secure/edge-firewall/) executes the Bot Manager add-on and other security rules. -- [Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/) is a Firewall add-on for bot management. +- [Firewall](/en/documentation/products/secure/firewall/) executes the Bot Manager add-on and other security rules. +- [Bot Manager](/en/documentation/products/secure/firewall/bot-manager/) is a Firewall add-on for bot management. - This add-on is Azion's comprehensive solution for bot management. A [lite version integration](/en/documentation/products/guides/bot-manager-lite/) is also available in the Marketplace. -- [Applications](/en/documentation/products/build/edge-application/) is your application running on top of the Azion Web Platform. +- [Applications](/en/documentation/products/build/applications/) is your application running on top of the Azion Web Platform. - [Data Stream](/en/documentation/products/observe/data-stream/) and [Real-Time Events](/en/documentation/products/observe/real-time-metrics/) enable you to monitor all Bot Manager activity. --- @@ -85,7 +85,7 @@ You can test and implement Azion Bot Manager in two ways: - From scratch: create an entire edge stack from zero, including Bot Manager. To do so: 1. [Create an application](/en/documentation/products/guides/build/build-an-application/). 2. [Add a custom domain to it](/en/documentation/products/guides/configure-a-domain/). - 3. [Enable Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/). + 3. [Enable Bot Manager](/en/documentation/products/secure/firewall/bot-manager/). - Contact the [Sales team](https://www.azion.com/en/contact-sales/) for more details on the Bot Manager subscription. - [Configure Bot Manager Lite](/en/documentation/products/guides/bot-manager-lite/) if you've decided to use this version. 4. [Monitor bot activity](/en/documentation/products/observe/data-stream/first-steps/) and calibrate rules. 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 3073ed3422..55365ccbfb 100644 --- a/src/content/docs/en/pages/architectures/compliance/compliance-architecture.mdx +++ b/src/content/docs/en/pages/architectures/compliance/compliance-architecture.mdx @@ -54,12 +54,12 @@ Read more on the Azion [Shared Responsibility Model](/en/documentation/shared-re - [Global Infrastructure](https://www.azion.com/en/products/our-network/): it processes data closer to the source, reducing latency and enhancing real-time analysis, including policies and technologies to make it safe and compliant. - [Azion CLI](/en/documentation/products/azion-cli/overview/): an open-source command-line interface (CLI) that lets you interact with Azion Web Platform using a terminal. - [Azion Console](/en/documentation/products/guides/getting-to-know-azion-console/): Azion's interface where you can access all the available products and their settings. -- [Firewall](/en/documentation/products/secure/edge-firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. - - [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. - - [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. - - [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. - - [Functions for Firewall](/en/documentation/products/secure/edge-firewall/edge-functions/): build event-driven, serverless applications including functions with your own security source code. -- [Applications](/en/documentation/products/build/edge-application/): allows you to set up an application to configure delivery and cache policies. +- [Firewall](/en/documentation/products/secure/firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. + - [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. + - [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. + - [Network Shield](/en/documentation/products/secure/firewall/network-shield/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. + - [Functions for Firewall](/en/documentation/products/secure/firewall/functions/): build event-driven, serverless applications including functions with your own security source code. +- [Applications](/en/documentation/products/build/applications/): allows you to set up an application to configure delivery and cache policies. - [Real-Time Events](/en/documentation/products/observe/real-time-events/) enables you to monitor all your applications' activity and by using [Data Stream](/en/documentation/products/observe/data-stream/) connectors you can feed event logs into your stream processing, SIEM, and big data platforms. --- @@ -72,8 +72,8 @@ Read more on the Azion [Shared Responsibility Model](/en/documentation/shared-re - [Configure the application's main settings](/en/documentation/products/guides/build/configure-main-settings/). 3. [Create a domain](/en/documentation/products/guides/configure-a-domain/) and associate it with the application, and [point your traffic to Azion](/en/documentation/products/guides/point-domain-to-azion/). 4. [Create your Digital Certificate](/en/documentation/products/guides/create-a-digital-certificate/). -5. [Create a firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) and select the domains you want to protect. - - Define any [WAF rules](/en/documentation/products/guides/secure/create-waf-rule-set/), [Rules Engine rules](/en/documentation/products/secure/edge-firewall/rules-engine/), or [functions](/en/documentation/products/secure/edge-firewall/edge-functions/) you want to implement and instantiate in the firewall. +5. [Create a firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) and select the domains you want to protect. + - Define any [WAF rules](/en/documentation/products/guides/secure/create-waf-rule-set/), [Rules Engine rules](/en/documentation/products/secure/firewall/rules-engine/), or [functions](/en/documentation/products/secure/firewall/functions/) you want to implement and instantiate in the firewall. 6. Monitor your applications through the [Observe products](/en/documentation/products/observe/overview/) and the [Activity History](/en/documentation/products/accounts/activity-history/) page. --- diff --git a/src/content/docs/en/pages/architectures/edge-application/application-acceleration.mdx b/src/content/docs/en/pages/architectures/edge-application/application-acceleration.mdx index 76859345b9..3350d75da2 100644 --- a/src/content/docs/en/pages/architectures/edge-application/application-acceleration.mdx +++ b/src/content/docs/en/pages/architectures/edge-application/application-acceleration.mdx @@ -68,4 +68,4 @@ Create an application. ## Related docs -- [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/). +- [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/). diff --git a/src/content/docs/en/pages/architectures/edge-application/application-modernization.mdx b/src/content/docs/en/pages/architectures/edge-application/application-modernization.mdx index 34514aa1e1..3124cc7013 100644 --- a/src/content/docs/en/pages/architectures/edge-application/application-modernization.mdx +++ b/src/content/docs/en/pages/architectures/edge-application/application-modernization.mdx @@ -50,15 +50,15 @@ After all this process, the application returns a response to the request. --- ## Components -- [Applications](/en/documentation/products/build/edge-application/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. - - [Cache](/en/documentation/products/build/edge-application/edge-cache/): global module to cache content at the edge. - - [Functions](/en/documentation/products/build/edge-application/edge-functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. - - [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/): a tool to configure the scenarios in which a specific cache policy is enforced. - - [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/): module that creates an additional cache layer between the edge and your origin servers, reducing latency and infrastructure costs. - - [Load Balancer](/en/documentation/products/secure/edge-connector/load-balancer/): module designed to balance traffic across your origins, data centers, or cloud providers, mitigating network congestion and server overload. - - [Object Storage](/en/documentation/products/store/edge-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. - - [Origins](/en/documentation/products/build/edge-application/origins/): allows you to customize the source address of your Application content, the Host header of your application, the path, and the HMAC authentication credentials for protected services. - - [Domains](/en/documentation/products/build/edge-application/domains/): register a custom domain with Azion to deliver the application. +- [Applications](/en/documentation/products/build/applications/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. + - [Cache](/en/documentation/products/build/applications/cache/): global module to cache content at the edge. + - [Functions](/en/documentation/products/build/applications/functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. + - [Rules Engine](/en/documentation/products/build/applications/rules-engine/): a tool to configure the scenarios in which a specific cache policy is enforced. + - [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/): module that creates an additional cache layer between the edge and your origin servers, reducing latency and infrastructure costs. + - [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/): module designed to balance traffic across your origins, data centers, or cloud providers, mitigating network congestion and server overload. + - [Object Storage](/en/documentation/products/store/object-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. + - [Origins](/en/documentation/products/build/applications/origins/): allows you to customize the source address of your Application content, the Host header of your application, the path, and the HMAC authentication credentials for protected services. + - [Domains](/en/documentation/products/build/applications/domains/): register a custom domain with Azion to deliver the application. - [Azion Marketplace](/en/documentation/products/marketplace/) is a digital catalog that makes it easy to find, test, and deploy edge-running software. - [Azion CLI](/en/documentation/products/azion-cli/overview/): an open-source command-line interface (CLI) that lets you interact with Azion Web Platform using a terminal. - [Azion Console](/en/documentation/products/guides/getting-to-know-azion-console/): Azion’s configuration interface where you can access all the available products and their settings. It enables you to complete all tasks in Azion’s platform diff --git a/src/content/docs/en/pages/architectures/edge-application/content-delivery.mdx b/src/content/docs/en/pages/architectures/edge-application/content-delivery.mdx index e48e0c6c5a..e66826340e 100644 --- a/src/content/docs/en/pages/architectures/edge-application/content-delivery.mdx +++ b/src/content/docs/en/pages/architectures/edge-application/content-delivery.mdx @@ -36,11 +36,11 @@ This solution is ideal for organizations looking to modernize their content deli ## Components -- [Applications](/en/documentation/products/build/edge-application/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. - - [Cache](/en/documentation/products/build/edge-application/edge-cache/): global add-on to cache content at the edge. - - [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/): used to customize cache optimization rules and cache keys and cookies based on established patterns. - - [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/): a tool to configure the scenarios in which a specific cache policy is enforced. - - [Image Processor](/en/documentation/products/build/edge-application/image-processor/): that allows image manipulation through the request line. +- [Applications](/en/documentation/products/build/applications/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. + - [Cache](/en/documentation/products/build/applications/cache/): global add-on to cache content at the edge. + - [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/): used to customize cache optimization rules and cache keys and cookies based on established patterns. + - [Rules Engine](/en/documentation/products/build/applications/rules-engine/): a tool to configure the scenarios in which a specific cache policy is enforced. + - [Image Processor](/en/documentation/products/build/applications/image-processor/): that allows image manipulation through the request line. --- @@ -69,4 +69,4 @@ This solution is ideal for organizations looking to modernize their content deli ## Related docs -- [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/). +- [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/). diff --git a/src/content/docs/en/pages/architectures/edge-application/image-processing.mdx b/src/content/docs/en/pages/architectures/edge-application/image-processing.mdx index 34835dee1c..2708f602cf 100644 --- a/src/content/docs/en/pages/architectures/edge-application/image-processing.mdx +++ b/src/content/docs/en/pages/architectures/edge-application/image-processing.mdx @@ -37,11 +37,11 @@ Azion Image Processor offers simplicity and automation to [resource management]( ## Components -- [Applications](/en/documentation/products/build/edge-application/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. - - [Cache](/en/documentation/products/build/edge-application/edge-cache/): global module to cache content at the edge. - - [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/): a tool to configure the scenarios in which a specific cache policy is enforced and activate image optimization. - - [Image Processor](/en/documentation/products/build/edge-application/image-processor/): an add-on that allows image manipulation through the request line. -- [Workloads](/en/documentation/products/build/edge-application/domains/): register a custom domain with Azion to deliver the application. +- [Applications](/en/documentation/products/build/applications/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. + - [Cache](/en/documentation/products/build/applications/cache/): global module to cache content at the edge. + - [Rules Engine](/en/documentation/products/build/applications/rules-engine/): a tool to configure the scenarios in which a specific cache policy is enforced and activate image optimization. + - [Image Processor](/en/documentation/products/build/applications/image-processor/): an add-on that allows image manipulation through the request line. +- [Workloads](/en/documentation/products/build/applications/domains/): register a custom domain with Azion to deliver the application. ## Implementation 1. Create an application: you must first create the content delivery application layer at the edge of the network. You can do that using [Azion Console](https://console.azion.com), [Azion API](https://api.azion.com/#9c61e0fd-e7aa-4a5f-b29e-7f9d71b98d5f) or [Azion CLI](/en/documentation/products/azion-cli/overview/). diff --git a/src/content/docs/en/pages/architectures/edge-application/microservices.mdx b/src/content/docs/en/pages/architectures/edge-application/microservices.mdx index 3df13b39df..0c240037b7 100644 --- a/src/content/docs/en/pages/architectures/edge-application/microservices.mdx +++ b/src/content/docs/en/pages/architectures/edge-application/microservices.mdx @@ -38,10 +38,10 @@ After these distinct yet cohesive processes, the content —processed and assemb ## Components -- [Applications](/en/documentation/products/build/edge-application/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. - - [Functions](/en/documentation/products/build/edge-application/edge-functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. - - [Object Storage](/en/documentation/products/store/edge-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. - - [SQL Database](/en/documentation/products/store/edge-sql/): an edge-native SQL solution designed for serverless applications. It’s fully ACID-compliant and utilizes SQLite’s SQL dialect to provide a familiar development environment, facilitating fast integration. +- [Applications](/en/documentation/products/build/applications/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. + - [Functions](/en/documentation/products/build/applications/functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. + - [Object Storage](/en/documentation/products/store/object-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. + - [SQL Database](/en/documentation/products/store/sql-database/): an edge-native SQL solution designed for serverless applications. It’s fully ACID-compliant and utilizes SQLite’s SQL dialect to provide a familiar development environment, facilitating fast integration. --- @@ -52,7 +52,7 @@ After these distinct yet cohesive processes, the content —processed and assemb - On [Console](https://console.azion.com), create an application using the **+ Create** button on the homepage. - Using the [Azion API](https://api.azion.com/#d43c5509-fb99-4b20-a7bd-64f0924af352) to create an application. - Using the [Azion CLI](/en/documentation/devtools/cli/create/#edge-applications) to create and deploy an application. -2. [Create a function](/en/documentation/products/build/edge-application/edge-functions/#implementation) and [instantiate](/en/documentation/products/guides/build/instantiate-edge-functions/) it in the recently created application. +2. [Create a function](/en/documentation/products/build/applications/functions/#implementation) and [instantiate](/en/documentation/products/guides/build/instantiate-functions/) it in the recently created application. 3. Create a domain and associate it with the application: - On Console, [create a domain](/en/documentation/products/guides/configure-a-domain/) using the + Create button on the homepage. - Using the [Azion API](https://api.azion.com/#d43c5509-fb99-4b20-a7bd-64f0924af352) to create a domain. diff --git a/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx b/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx index cab0033ec0..d55834785c 100644 --- a/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx +++ b/src/content/docs/en/pages/architectures/edge-enhanced/edge-enhanced.mdx @@ -33,10 +33,10 @@ After this process, the application returns a response to the request. --- ## Components -- [Applications](/en/documentation/products/build/edge-application/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. - - [Functions](/en/documentation/products/build/edge-application/edge-functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. - - [Object Storage](/en/documentation/products/store/edge-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. - - [SQL Database](/en/documentation/products/store/edge-sql/): an edge-native SQL solution designed for serverless applications. It’s fully ACID-compliant and utilizes SQLite’s SQL dialect to provide a familiar development environment, facilitating fast integration. +- [Applications](/en/documentation/products/build/applications/): set up an application to configure delivery and cache policies, create rules to automate cache policy assignments based on content type, and determine how content is cached. + - [Functions](/en/documentation/products/build/applications/functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. + - [Object Storage](/en/documentation/products/store/object-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. + - [SQL Database](/en/documentation/products/store/sql-database/): an edge-native SQL solution designed for serverless applications. It’s fully ACID-compliant and utilizes SQLite’s SQL dialect to provide a familiar development environment, facilitating fast integration. --- @@ -46,7 +46,7 @@ After this process, the application returns a response to the request. - On [Console](https://console.azion.com), create an application using the **+ Create** button on the homepage. - Using the [Azion API](https://api.azion.com/#d43c5509-fb99-4b20-a7bd-64f0924af352) to create an application. - Using the [Azion CLI](/en/documentation/devtools/cli/create/#edge-applications) to create and deploy an application. -2. [Create an function](/en/documentation/products/build/edge-application/edge-functions/#implementation) and [instantiate](/en/documentation/products/guides/build/instantiate-edge-functions/) it in the recently created application. +2. [Create an function](/en/documentation/products/build/applications/functions/#implementation) and [instantiate](/en/documentation/products/guides/build/instantiate-functions/) it in the recently created application. 3. Create a domain and associate it with the application: - On Console, [create a domain](/en/documentation/products/guides/configure-a-domain/) using the + Create button on the homepage. - Using the [Azion API](https://api.azion.com/#d43c5509-fb99-4b20-a7bd-64f0924af352) to create a domain. diff --git a/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx b/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx index e15d17b66d..8e8ce061aa 100644 --- a/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx +++ b/src/content/docs/en/pages/architectures/edge-firewall/online-fraud-prevention.mdx @@ -55,17 +55,17 @@ This approach performs fraud detection directly at the edge before reaching your ### Components - [Global Infrastructure](https://www.azion.com/en/products/our-network/): a highly distributed architecture that includes strategically located edge nodes. -- [Applications](/en/documentation/products/build/edge-application/): allows you to build applications that run in Azion Global Infrastructure. - - [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/): used to customize cache optimization rules, cache keys, and cookies based on established patterns. - - [Cache](/en/documentation/products/build/edge-application/edge-cache/): global add-on to cache content at the edge. - - [Functions for Applications](/en/documentation/products/build/edge-application/edge-functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. - - [Rules Engine for Applications](/en/documentation/products/build/edge-application/rules-engine/): allows you to configure scenarios where specific policies are enforced, providing granular control over delivery. -- [Firewall](/en/documentation/products/secure/edge-firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. - - [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. - - [Web Application Firewall (WAF)](/en/documentation/products/secure/edge-firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. - - [Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/): Azion's comprehensive solution for bot management. - - [Functions for Firewall](/en/documentation/products/secure/edge-firewall/edge-functions/): build event-driven, serverless web applications including functions with your own security source code. - - [Rules Engine for Firewall](/en/documentation/products/secure/edge-firewall/rules-engine/): allows you to configure scenarios where specific policies are enforced, providing granular control over delivery. +- [Applications](/en/documentation/products/build/applications/): allows you to build applications that run in Azion Global Infrastructure. + - [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/): used to customize cache optimization rules, cache keys, and cookies based on established patterns. + - [Cache](/en/documentation/products/build/applications/cache/): global add-on to cache content at the edge. + - [Functions for Applications](/en/documentation/products/build/applications/functions/): allows you to create event-driven, serverless applications, at the edge of the network, closer to users. + - [Rules Engine for Applications](/en/documentation/products/build/applications/rules-engine/): allows you to configure scenarios where specific policies are enforced, providing granular control over delivery. +- [Firewall](/en/documentation/products/secure/firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. + - [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. + - [Web Application Firewall (WAF)](/en/documentation/products/secure/firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. + - [Bot Manager](/en/documentation/products/secure/firewall/bot-manager/): Azion's comprehensive solution for bot management. + - [Functions for Firewall](/en/documentation/products/secure/firewall/functions/): build event-driven, serverless web applications including functions with your own security source code. + - [Rules Engine for Firewall](/en/documentation/products/secure/firewall/rules-engine/): allows you to configure scenarios where specific policies are enforced, providing granular control over delivery. - [Azion Marketplace](/en/documentation/products/marketplace/) and Custom Integrations: - Bot protection. - [DataDome Bot Protection](https://console.azion.com/marketplace/solution/datadome/bot-protection/) @@ -89,23 +89,23 @@ This approach performs fraud detection directly at the edge before reaching your 2. Configure your custom integrations with Azion's platform. - For example, IdP for user management via [SAML](/en/documentation/products/guides/sso-google-saml/) or [SCIM](/en/documentation/products/guides/microsoft-entra-automated-user-provisioning/) protocol. 3. [Configure the application](/en/documentation/products/guides/build/configure-main-settings/), including main settings such as origins, cache settings, etc. -- [Configure a custom domain](/en/documentation/products/build/edge-application/domains/) for your application. -- [Set the criteria and behaviors](/en/documentation/products/build/edge-application/rules-engine/) for the Rules Engine rules. For example: +- [Configure a custom domain](/en/documentation/products/build/applications/domains/) for your application. +- [Set the criteria and behaviors](/en/documentation/products/build/applications/rules-engine/) for the Rules Engine rules. For example: - Inspect HTTP headers. - Add or filter cookies. - Validate input parameters. - Block malicious payloads. - Redirects. - Rewrite the request. -4. [Create and configure a firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/). -- [Set the criteria and behaviors](/en/documentation/products/secure/edge-firewall/rules-engine/) for the Rules Engine rules. For example: +4. [Create and configure a firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/). +- [Set the criteria and behaviors](/en/documentation/products/secure/firewall/rules-engine/) for the Rules Engine rules. For example: - Deny or drop requests. - Block malicious IPs. - Filter specific HTTP requests. - Enforce rate limits. - Run functions with custom logic. -- [Instantiate functions](/en/documentation/products/guides/secure/instantiate-edge-functions/) and [integrations](/en/documentation/products/marketplace/integrations/#edge-firewall-functions). -5. [Enable Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/). +- [Instantiate functions](/en/documentation/products/guides/secure/instantiate-functions/) and [integrations](/en/documentation/products/marketplace/integrations/#edge-firewall-functions). +5. [Enable Bot Manager](/en/documentation/products/secure/firewall/bot-manager/). - Contact the [Sales team](https://www.azion.com/en/contact-sales/) for more details on the Bot Manager subscription. 6. [Monitor your application](/en/documentation/products/observe/monitor-applications/) and refine rules. diff --git a/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx b/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx index 72d376f582..b631396237 100644 --- a/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx +++ b/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx @@ -40,12 +40,12 @@ This solution is ideal for organizations looking to safeguard their digital infr ### Components -- [Firewall](/en/documentation/products/secure/edge-firewall/): provides main settings to set up your instance and associate it with domains and activate modules. - - [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks when it's activated. - - [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities found in OWASP Top 10 and block requests. - - [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. - - [Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/): identifies and classifies the request according to the intent-based behavioral analysis. -- [Applications](/en/documentation/products/build/edge-application/): runs your application on top of the Azion Web Platform. +- [Firewall](/en/documentation/products/secure/firewall/): provides main settings to set up your instance and associate it with domains and activate modules. + - [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks when it's activated. + - [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities found in OWASP Top 10 and block requests. + - [Network Shield](/en/documentation/products/secure/firewall/network-shield/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. + - [Bot Manager](/en/documentation/products/secure/firewall/bot-manager/): identifies and classifies the request according to the intent-based behavioral analysis. +- [Applications](/en/documentation/products/build/applications/): runs your application on top of the Azion Web Platform. --- @@ -64,7 +64,7 @@ This solution is ideal for organizations looking to safeguard their digital infr - [Azion API](https://api.azion.com/#9c61e0fd-e7aa-4a5f-b29e-7f9d71b98d5f). - [Azion CLI](/en/documentation/products/azion-cli/overview/). -- [Create a firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) and associate it with the configured domain, so all security rules apply to that specific domain. +- [Create a firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) and associate it with the configured domain, so all security rules apply to that specific domain. - Enable the DDoS Protection module. - Enable the Web Application Firewall module. - Enable the Network Shield module. @@ -72,7 +72,7 @@ This solution is ideal for organizations looking to safeguard their digital infr - Configure Threat Type and Sensitivity levels. - [Create a network list in Network Shield](/en/documentation/products/guides/blocklists-ip-addresses-edge/). - Configure the IPs or countries that'll be blocked. -- [Enable Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/). +- [Enable Bot Manager](/en/documentation/products/secure/firewall/bot-manager/). - Contact the [Sales team](https://www.azion.com/en/contact-sales/) for more details on the Bot Manager subscription. - [Configure Bot Manager Lite](/en/documentation/products/guides/bot-manager-lite/) if you've decided to use this version. - [Create rules in Rules Engine for Firewall](/en/documentation/products/guides/secure/work-with-rules-engine/). diff --git a/src/content/docs/en/pages/architectures/edge-native/edge-native-apps.mdx b/src/content/docs/en/pages/architectures/edge-native/edge-native-apps.mdx index 1132af46c2..3403175cb6 100644 --- a/src/content/docs/en/pages/architectures/edge-native/edge-native-apps.mdx +++ b/src/content/docs/en/pages/architectures/edge-native/edge-native-apps.mdx @@ -29,9 +29,9 @@ The application, via the Azion Lib, ultimately returns a response containing the --- ## Components -- [Applications](/en/documentation/products/build/edge-application/): this component allows delivery and cache policy configuration, automatic cache policy assignment via rules based on content type, and determines content caching. - - [Functions](/en/documentation/products/build/edge-application/edge-functions/): these are serverless, event-driven applications at the network's edge that accommodate your application's logic, including CRUD operations. - - [SQL Database](/en/documentation/products/store/edge-sql/): this serverless SQL solution, built natively for the edge, performs database operations of your CRUD application with lower latency. +- [Applications](/en/documentation/products/build/applications/): this component allows delivery and cache policy configuration, automatic cache policy assignment via rules based on content type, and determines content caching. + - [Functions](/en/documentation/products/build/applications/functions/): these are serverless, event-driven applications at the network's edge that accommodate your application's logic, including CRUD operations. + - [SQL Database](/en/documentation/products/store/sql-database/): this serverless SQL solution, built natively for the edge, performs database operations of your CRUD application with lower latency. - [Azion CLI](/en/documentation/products/azion-cli/overview/): an open-source command-line interface (CLI) that allows interaction with Azion Web Platform using a terminal. - [Azion Lib](https://github.com/aziontech/lib): a suite of tools to interact with various Azion services, including products and utilities. - [Azion Console](/en/documentation/products/guides/getting-to-know-azion-console/): the interface where you can access all the available products and their settings. diff --git a/src/content/docs/en/pages/architectures/jamstack/jamstack.mdx b/src/content/docs/en/pages/architectures/jamstack/jamstack.mdx index 00db65f96d..61261a79de 100644 --- a/src/content/docs/en/pages/architectures/jamstack/jamstack.mdx +++ b/src/content/docs/en/pages/architectures/jamstack/jamstack.mdx @@ -35,8 +35,8 @@ This solution is ideal for organizations looking to enhance website performance, - [Azion Console](/en/documentation/products/guides/getting-to-know-azion-console/): the interface where you can access all the available products and their settings. - [Azion CLI](/en/documentation/products/azion-cli/overview/): an open-source command-line interface (CLI) that allows interaction with Azion Web Platform using a terminal. -- [Applications](/en/documentation/products/build/edge-application/): an Azion product that allows you to build applications that run in Azion's edge network. -- [Object Storage](/en/documentation/products/store/edge-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. +- [Applications](/en/documentation/products/build/applications/): an Azion product that allows you to build applications that run in Azion's edge network. +- [Object Storage](/en/documentation/products/store/object-storage/): a scalable and secure storage service designed to integrate object storage with the Azion Web Platform using the S3 standard for object operations. --- diff --git a/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx b/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx index 560948f211..908d730097 100644 --- a/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx +++ b/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx @@ -39,8 +39,8 @@ This solution is ideal for content providers who require high fidelity and low l ### Components -- [Applications](/en/documentation/products/build/edge-application/) allows you to build applications on top of the Azion Web Platform and deliver your content. - - [Cache](/en/documentation/products/build/edge-application/edge-cache/) enables you to configure how your application caches content to reduce latency and increase transfer rates. +- [Applications](/en/documentation/products/build/applications/) allows you to build applications on top of the Azion Web Platform and deliver your content. + - [Cache](/en/documentation/products/build/applications/cache/) enables you to configure how your application caches content to reduce latency and increase transfer rates. - The **Ingest** component receives signal from encoders and distributes content in HLS format. It works as the origin for the application. --- @@ -58,5 +58,5 @@ This solution is ideal for content providers who require high fidelity and low l ## Related docs - [Azion Global Infrastructure](https://www.azion.com/en/products/our-network/) -- [Cache Settings](/en/documentation/products/build/edge-application/cache-settings/) +- [Cache Settings](/en/documentation/products/build/applications/cache-settings/) - [Content delivery architecture](/en/documentation/architectures/edge-application/content-delivery/) diff --git a/src/content/docs/en/pages/architectures/orch/application-deliver-operation.mdx b/src/content/docs/en/pages/architectures/orch/application-deliver-operation.mdx index d34098baae..6adaedf9e3 100644 --- a/src/content/docs/en/pages/architectures/orch/application-deliver-operation.mdx +++ b/src/content/docs/en/pages/architectures/orch/application-deliver-operation.mdx @@ -8,7 +8,7 @@ meta_tags: >- namespace: docs_arch_infra_auto_apps_delivery --- -[Azion Orchestrator](/en/documentation/products/deploy/edge-orchestrator/) enables frequent and reliable application releases through orchestration. This documentation covers the architecture and steps for automated application delivery using Azion Orchestrator, ensuring optimal performance and streamlined operations. +[Azion Orchestrator](/en/documentation/products/deploy/orchestrator/) enables frequent and reliable application releases through orchestration. This documentation covers the architecture and steps for automated application delivery using Azion Orchestrator, ensuring optimal performance and streamlined operations. --- @@ -113,9 +113,9 @@ HTML with the products list: ## Components - [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/): interface for managing and monitoring applications and services. -- [Azion Orchestrator](/en/documentation/products/deploy/edge-orchestrator/): automates deployment and management of applications across edge nodes. -- [Edge Nodes](/en/documentation/products/deploy/edge-orchestrator/edge-node/): distributed computing resources that process data closer to the source. -- [Edge Services](/en/documentation/products/deploy/edge-orchestrator/edge-services/): enables services creation and customization for orchestration on Edge Nodes. +- [Azion Orchestrator](/en/documentation/products/deploy/orchestrator/): automates deployment and management of applications across edge nodes. +- [Edge Nodes](/en/documentation/products/deploy/orchestrator/edge-node/): distributed computing resources that process data closer to the source. +- [Edge Services](/en/documentation/products/deploy/orchestrator/edge-services/): enables services creation and customization for orchestration on Edge Nodes. --- @@ -136,4 +136,4 @@ HTML with the products list: ## Related docs - [Deploy overview](/en/documentation/products/deploy/overview/) -- [Orchestrator overview](/en/documentation/products/deploy/edge-orchestrator/) +- [Orchestrator overview](/en/documentation/products/deploy/orchestrator/) diff --git a/src/content/docs/en/pages/architectures/orch/infra-automation.mdx b/src/content/docs/en/pages/architectures/orch/infra-automation.mdx index 242bc8e68b..6ea0f6cb3d 100644 --- a/src/content/docs/en/pages/architectures/orch/infra-automation.mdx +++ b/src/content/docs/en/pages/architectures/orch/infra-automation.mdx @@ -8,7 +8,7 @@ meta_tags: >- namespace: docs_arch_infra_auto_apps --- -[Azion Orchestrator](/en/documentation/products/deploy/edge-orchestrator/) allows you to automate and manage your infrastructure efficiently. By leveraging [Azion CLI](/en/documentation/products/azion-cli/overview/), you can perform tasks such as deployment, monitoring, and updates of applications. This documentation provides an in-depth look at the architecture and steps for implementing infrastructure automation using Azion Orchestrator, helping you achieve optimal performance and streamlined operations. +[Azion Orchestrator](/en/documentation/products/deploy/orchestrator/) allows you to automate and manage your infrastructure efficiently. By leveraging [Azion CLI](/en/documentation/products/azion-cli/overview/), you can perform tasks such as deployment, monitoring, and updates of applications. This documentation provides an in-depth look at the architecture and steps for implementing infrastructure automation using Azion Orchestrator, helping you achieve optimal performance and streamlined operations. --- @@ -33,9 +33,9 @@ This flow assumes a service has been created for installing Azion CLI on the edg ## Components - [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/): interface for managing and monitoring applications and services. -- [Azion Orchestrator](/en/documentation/products/deploy/edge-orchestrator/): automates deployment and management of applications across edge nodes. -- [Edge Nodes](/en/documentation/products/deploy/edge-orchestrator/edge-node/): distributed computing resources that process data closer to the source. -- [Edge Services](/en/documentation/products/deploy/edge-orchestrator/edge-services/): enables services creation and customization for orchestration on Edge Nodes. +- [Azion Orchestrator](/en/documentation/products/deploy/orchestrator/): automates deployment and management of applications across edge nodes. +- [Edge Nodes](/en/documentation/products/deploy/orchestrator/edge-node/): distributed computing resources that process data closer to the source. +- [Edge Services](/en/documentation/products/deploy/orchestrator/edge-services/): enables services creation and customization for orchestration on Edge Nodes. --- @@ -56,5 +56,5 @@ This flow assumes a service has been created for installing Azion CLI on the edg ## Related docs - [Deploy overview](/en/documentation/products/deploy/overview/) -- [Orchestrator overview](/en/documentation/products/deploy/edge-orchestrator/) +- [Orchestrator overview](/en/documentation/products/deploy/orchestrator/) \ No newline at end of file diff --git a/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx b/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx index bbfe4c6bb7..014eae6603 100644 --- a/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx +++ b/src/content/docs/en/pages/architectures/security-automation/security-automation.mdx @@ -46,21 +46,21 @@ In this context, autonomous systems operate with minimal or no human interventio ### Components - Azion interfaces: [Console](/en/documentation/products/guides/getting-to-know-azion-console/), [API](https://api.azion.com/), or [CLI](/en/documentation/products/azion-cli/overview/). -- [Firewall](/en/documentation/products/secure/edge-firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. - - [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/) detects and mitigates DDoS and DoS attacks. - - [Firewall Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) allows you to define the conditions (Criteria) and actions (Behaviors) for your rules. If the Criteria are met, the Behaviors will be executed. - - [Firewall Functions](/en/documentation/products/secure/edge-firewall/edge-functions/) are JavaScript functions that run at the edge of the network, close to users, and help secure your applications by applying the logic your business requires. - - [Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/) identifies and classifies the request according to the intent-based behavioral analysis. This add-on is Azion's comprehensive solution for bot management. A [lite version integration](/en/documentation/products/guides/bot-manager-lite/) is also available in the Marketplace. +- [Firewall](/en/documentation/products/secure/firewall/): provides main settings to set up your instance, enabling you to associate it with domains and activate modules to protect users, applications, and networks. + - [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/) detects and mitigates DDoS and DoS attacks. + - [Firewall Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) allows you to define the conditions (Criteria) and actions (Behaviors) for your rules. If the Criteria are met, the Behaviors will be executed. + - [Firewall Functions](/en/documentation/products/secure/firewall/functions/) are JavaScript functions that run at the edge of the network, close to users, and help secure your applications by applying the logic your business requires. + - [Bot Manager](/en/documentation/products/secure/firewall/bot-manager/) identifies and classifies the request according to the intent-based behavioral analysis. This add-on is Azion's comprehensive solution for bot management. A [lite version integration](/en/documentation/products/guides/bot-manager-lite/) is also available in the Marketplace. --- ## Implementation 1. Create an [application](/en/documentation/products/guides/build/build-an-application/). -2. Configure a [firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/). +2. Configure a [firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/). 3. Define all your rules and configurations: - - [Rules Engine rules](/en/documentation/products/secure/edge-firewall/rules-engine/), using criteria and behaviors to define how the request is handled. It includes rules related to network lists, WAF Rules, Custom Allowed Rules, rate limits, custom responses, blocking and dropping requests, and run functions. - - [Functions](/en/documentation/products/secure/edge-firewall/edge-functions/), creating your own code or using [Marketplace Firewall integrations](/en/documentation/products/marketplace/integrations/#edge-firewall-functions). + - [Rules Engine rules](/en/documentation/products/secure/firewall/rules-engine/), using criteria and behaviors to define how the request is handled. It includes rules related to network lists, WAF Rules, Custom Allowed Rules, rate limits, custom responses, blocking and dropping requests, and run functions. + - [Functions](/en/documentation/products/secure/firewall/functions/), creating your own code or using [Marketplace Firewall integrations](/en/documentation/products/marketplace/integrations/#edge-firewall-functions). 4. Enable Bot Manager: - Contact the [Sales team](https://www.azion.com/en/contact-sales/) for more details about the Bot Manager subscription. - Configure [Bot Manager Lite](/en/documentation/products/guides/bot-manager-lite/) if you've decided to use this version. diff --git a/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx b/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx index a22a2b0f5d..11d3788f16 100644 --- a/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx +++ b/src/content/docs/en/pages/architectures/security-modernization/security-modernization-with-edge-computing.mdx @@ -40,14 +40,14 @@ This use case is ideal for organizations looking to build a strong online presen ### Components -- [Applications](/en/documentation/products/build/edge-application/): your application running on top of the Azion Web Platform. -- [Firewall](/en/documentation/products/secure/edge-firewall/): executes its modules and security rules. - - [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. - - [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. - - [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. - - [Functions](/en/documentation/products/secure/edge-firewall/edge-functions/): serverless functions that run on Azion Runtime with low latency, bringing the operational power and security processing closer to the end user. - - [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/): allows you to create customized security logic through rules to block or allow requests and users. - - [Origin Shield](/en/documentation/products/secure/edge-firewall/#origin-shield-add-on): creates a security perimeter for your origin infrastructure. +- [Applications](/en/documentation/products/build/applications/): your application running on top of the Azion Web Platform. +- [Firewall](/en/documentation/products/secure/firewall/): executes its modules and security rules. + - [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/): detects and mitigates DDoS and DoS attacks. + - [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/): allows you to configure protection against attacks and vulnerabilities. + - [Network Shield](/en/documentation/products/secure/firewall/network-shield/): allows you to create lists with IP addresses or countries with suspicious behavior and restrict their access. + - [Functions](/en/documentation/products/secure/firewall/functions/): serverless functions that run on Azion Runtime with low latency, bringing the operational power and security processing closer to the end user. + - [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/): allows you to create customized security logic through rules to block or allow requests and users. + - [Origin Shield](/en/documentation/products/secure/firewall/#origin-shield-add-on): creates a security perimeter for your origin infrastructure. - [Data Stream](/en/documentation/products/observe/data-stream/), [Real-Time Metrics](/en/documentation/products/observe/real-time-metrics/), [Real-Time Events](/en/documentation/products/observe/real-time-events/), and [GraphQL API](/en/documentation/devtools/graphql-api/overview/): enable you to monitor all Firewall and modules activity. --- @@ -67,7 +67,7 @@ This use case is ideal for organizations looking to build a strong online presen - [Azion API](https://api.azion.com/#9c61e0fd-e7aa-4a5f-b29e-7f9d71b98d5f) - [Azion CLI](/en/documentation/products/azion-cli/overview/) -2. [Create a firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) and associate it with the configured domain, so all security rules apply to that specific domain. +2. [Create a firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) and associate it with the configured domain, so all security rules apply to that specific domain. - Enable the Web Application Firewall, Network Shield, and Functions modules. 3. [Create a WAF rule set](/en/documentation/products/guides/secure/create-waf-rule-set/), configuring Threat Type and Sensitivity levels. 4. [Create a network list](/en/documentation/products/guides/blocklists-ip-addresses-edge/) in Network Shield. diff --git a/src/content/docs/en/pages/build-journey/advanced-configurations/image-processor.mdx b/src/content/docs/en/pages/build-journey/advanced-configurations/image-processor.mdx index cca49414a0..79a635c53f 100644 --- a/src/content/docs/en/pages/build-journey/advanced-configurations/image-processor.mdx +++ b/src/content/docs/en/pages/build-journey/advanced-configurations/image-processor.mdx @@ -15,10 +15,10 @@ import Code from '~/components/Code/Code.astro' -Through the [Image Processor](/en/documentation/products/build/edge-application/image-processor/) module, you can adjust image sizes, add filters and watermarks, or convert formats to suit for more efficient content delivery, bandwidth saving, and reduce object storage costs. These changes can be applied directly in the URL of your image by appending `ims` queries to the image's URL. +Through the [Image Processor](/en/documentation/products/build/applications/image-processor/) module, you can adjust image sizes, add filters and watermarks, or convert formats to suit for more efficient content delivery, bandwidth saving, and reduce object storage costs. These changes can be applied directly in the URL of your image by appending `ims` queries to the image's URL. :::caution[warning] -If you wish to optimize your images, in addition to the **Image Processor module, the activation of the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module is recommended for cache efficiency. If these modules are activated, images processed and data transfer could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. +If you wish to optimize your images, in addition to the **Image Processor module, the activation of the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module is recommended for cache efficiency. If these modules are activated, images processed and data transfer could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. ::: :::tip @@ -39,12 +39,12 @@ In this guide, there are separate instructions for API v3 and API v4. If you're 4. Click the **Save** button. 5. Navigate to the **Cache Settings** tab. 6. Click the **+ Cache Setting** button. -7. In the **Cache Expiration Policies** section, configure the [expiration policy](/en/documentation/products/build/edge-application/cache-settings/#browser-cache-settings) for your images. +7. In the **Cache Expiration Policies** section, configure the [expiration policy](/en/documentation/products/build/applications/cache-settings/#browser-cache-settings) for your images. - For images, you may add larger time-to-live (TTL) values, such as `1296000` seconds (15 days). 1. In the **Advanced Cache Key** section, choose one of the following options: - **Content varies by some Query String fields (Allowlist)**: if you want to list all the fields in the Query String that will identify your images. **Image Processor** uses the *ims* field, so this has to be included in the list as one of the required fields for your image manager application. - **Content varies by Query String, except for some fields (Blocklist)**: if you only want to list those fields in the Query String that should be ignored to identify the objects in your cache. In this case, it guarantees that the *ims* field will be removed from the list. - - **Content varies by all Query String fields**: if you don't know or aren't sure about which fields to list in the Query String because you aren't responsible for all the content in the cache or don't have [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) activated. + - **Content varies by all Query String fields**: if you don't know or aren't sure about which fields to list in the Query String because you aren't responsible for all the content in the cache or don't have [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) activated. 2. Click the **Save** button. Now you need to indicate what will trigger the activation of the **Image Processor** module. You can create a rule that identifies image formats as follows: @@ -78,7 +78,7 @@ To confirm whether your image is being optimized, [inspect the page](https://dev -1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your Application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) and [Image Processor](/en/documentation/products/build/edge-application/image-processor/) modules: +1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your Application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) and [Image Processor](/en/documentation/products/build/applications/image-processor/) modules: -1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) and [Image Processor](/en/documentation/products/build/edge-application/image-processor/) modules: +1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) and [Image Processor](/en/documentation/products/build/applications/image-processor/) modules: ' \ diff --git a/src/content/docs/en/pages/build-journey/advanced-configurations/multiple-origins.mdx b/src/content/docs/en/pages/build-journey/advanced-configurations/multiple-origins.mdx index a0f6b7732b..c5449cb84e 100644 --- a/src/content/docs/en/pages/build-journey/advanced-configurations/multiple-origins.mdx +++ b/src/content/docs/en/pages/build-journey/advanced-configurations/multiple-origins.mdx @@ -18,19 +18,19 @@ import Code from '~/components/Code/Code.astro' -When you [create an application](/en/documentation/products/start-with-a-template/), you need to define an origin. However, more complex and robust infrastructures may need multiple origins for the same application. The [Load Balancer](/en/documentation/products/secure/edge-connector/load-balancer/) feature allows you to use load balancing algorithms to manage high access numbers and control the behaviors of your origin. +When you [create an application](/en/documentation/products/start-with-a-template/), you need to define an origin. However, more complex and robust infrastructures may need multiple origins for the same application. The [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/) feature allows you to use load balancing algorithms to manage high access numbers and control the behaviors of your origin. :::caution[warning] If **Load Balancer** is activated, data transfer could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. ::: -There are separate instructions for API v3 using [legacy Origin](/en/documentation/products/build/edge-application/origins/) settings and API v4 using the new [Connectors](/en/documentation/products/secure/edge-connector) product. +There are separate instructions for API v3 using [legacy Origin](/en/documentation/products/build/applications/origins/) settings and API v4 using the new [Connectors](/en/documentation/products/secure/connectors) product. :::tip In this guide, there are separate instructions for API v3 and API v4. If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. ::: -The following steps will walk you through a hypothetical scenario where the default origin should be of the Load Balancer-type with the [Round Robin algorithm](/en/documentation/products/secure/edge-connector/load-balancer/#balancing-method). Feel free to interpret and modify the step-by-step instructions according to your specific use case. +The following steps will walk you through a hypothetical scenario where the default origin should be of the Load Balancer-type with the [Round Robin algorithm](/en/documentation/products/secure/connectors/load-balancer/#balancing-method). Feel free to interpret and modify the step-by-step instructions according to your specific use case. The following business rules of different origin servers must be configured with load balancing: diff --git a/src/content/docs/en/pages/build-journey/build-with-edge-app/build-with-edge-apps.mdx b/src/content/docs/en/pages/build-journey/build-with-edge-app/build-with-edge-apps.mdx index 5a47948304..255246e06a 100644 --- a/src/content/docs/en/pages/build-journey/build-with-edge-app/build-with-edge-apps.mdx +++ b/src/content/docs/en/pages/build-journey/build-with-edge-app/build-with-edge-apps.mdx @@ -11,7 +11,7 @@ meta_tags: >- namespace: docs_guides_build_edge_application --- -[Applications](/en/documentation/products/build/edge-application/) allows you to create new applications and define the variables of your application. It also enables you to automate actions at the request-response level. +[Applications](/en/documentation/products/build/applications/) allows you to create new applications and define the variables of your application. It also enables you to automate actions at the request-response level. Azion provides a range of tools to configure your applications: @@ -39,7 +39,7 @@ Next, you can configure your application's behavior by setting variables and par - **Cache settings**: [tune Cache settings](/en/documentation/products/guides/build/tune-cache-settings/) to reduce the load on origin servers and speed up delivery. Define values such as browse and Cache expiration, large file optimization, cache keys, and adaptive delivery based on devices. - **Connector**: [adjust your origin settings](/en/documentation/products/guides/build/work-with-origins/) to fit the needs of your application and define the values of the `Host` header and origin address. - **Device groups**: [group end-users based on their devices](/en/documentation/products/guides/build/create-device-groups/), operating systems, or browsers with information provided by the `User-Agent` header. -- **Functions**: [instantiate functions](/en/documentation/products/guides/build/instantiate-edge-functions/) to minimize resource usage by processing at the edge. +- **Functions**: [instantiate functions](/en/documentation/products/guides/build/instantiate-functions/) to minimize resource usage by processing at the edge. Some variables may have already been created by default when you first built your application. You can edit your default settings or create new ones if necessary. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-angular.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-angular.mdx index ddc91da452..37f2d7f070 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-angular.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-angular.mdx @@ -26,7 +26,7 @@ Learn more about [Angular](https://angular.io/docs). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-astro.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-astro.mdx index d695b8807e..45b02c8be3 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-astro.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-astro.mdx @@ -29,7 +29,7 @@ Learn more about [Astro](https://docs.astro.build/en/getting-started/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-docusaurus.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-docusaurus.mdx index e1e193b4c1..1ed3bdf80a 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-docusaurus.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-docusaurus.mdx @@ -29,7 +29,7 @@ Learn more about [Docusaurus](https://docusaurus.io/docs). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-eleventy.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-eleventy.mdx index 2da4398d0b..bdfb070bab 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-eleventy.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-eleventy.mdx @@ -29,7 +29,7 @@ Learn more about [Eleventy](https://www.11ty.dev/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-gatsby.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-gatsby.mdx index ba57c2199a..a28f7cbe5b 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-gatsby.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-gatsby.mdx @@ -29,7 +29,7 @@ Learn more about [Gatsby](https://www.gatsbyjs.com/docs/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hexo.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hexo.mdx index 832cb1f1a9..c68a81bf68 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hexo.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hexo.mdx @@ -28,7 +28,7 @@ Learn more about [Hexo](https://hexo.io/docs/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hono.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hono.mdx index 8ab6f64824..2ef8c7c219 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hono.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hono.mdx @@ -29,7 +29,7 @@ Learn more about [Hono](https://hono.dev/docs/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hugo.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hugo.mdx index 0f7804dd24..0f8ef15170 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hugo.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-hugo.mdx @@ -29,7 +29,7 @@ Learn more about [Hugo](https://gohugo.io/documentation/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-jekyll.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-jekyll.mdx index baafef19ba..430f0501a4 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-jekyll.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-jekyll.mdx @@ -29,7 +29,7 @@ Learn more about [Jekyll](https://jekyllrb.com/docs/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-next.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-next.mdx index fe9c91d98b..d3749f2e9e 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-next.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-next.mdx @@ -19,7 +19,7 @@ Next.js is a flexible React framework that allows for the creation of high-perfo Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. @@ -161,7 +161,7 @@ Wait a few minutes so the propagation takes place, and then access your applicat ## Compatibility - + Watch how to build with Next.js on Azion's YouTube channel: diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-overview.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-overview.mdx index 0d56e36e19..f52ba1729e 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-overview.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-overview.mdx @@ -43,7 +43,7 @@ You can check the full list of supported frameworks and some additional informat ::: - +
diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-react.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-react.mdx index f0e2fc7a14..e17c6d2a70 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-react.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-react.mdx @@ -28,7 +28,7 @@ Learn more about [React](https://react.dev/). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-svelte.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-svelte.mdx index d605f5e24e..cf1f9563c4 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-svelte.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-svelte.mdx @@ -29,7 +29,7 @@ Learn more about [Svelte](https://svelte.dev/docs/introduction). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vite.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vite.mdx index 6b8c70af85..3e13a2c2ad 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vite.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vite.mdx @@ -29,7 +29,7 @@ Learn more about [Vite](https://vitejs.dev/) and [VitePress](https://vitepress.d Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vue.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vue.mdx index d42cda9d65..dc711c8d85 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vue.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/frameworks/framework-vue.mdx @@ -29,7 +29,7 @@ Learn more about [Vue](https://vuejs.org/guide/introduction.html). Before getting started, you must have: -- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/edge-application/edge-functions/) enabled. +- An [Azion platform account](/en/documentation/products/accounts/creating-account/) with [Functions](/en/documentation/products/build/applications/functions/) enabled. - [The latest version of Azion CLI installed](/en/documentation/products/azion-cli/overview/). - Code editor. - Access to the terminal. diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/lang-js/lang-javascript.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/lang-js/lang-javascript.mdx index bd6780f43a..579b2ee2bb 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/lang-js/lang-javascript.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/lang-js/lang-javascript.mdx @@ -28,7 +28,7 @@ It's paramount to take a look at the list of available APIs, methods, and types. ## Code Editor -The [Functions Code Editor](/en/documentation/products/edge-application/edge-functions/runtime-api/code-editor/) provides a development experience similar to what developers are accustomed to. The [Functions ChatGPT Integration](/en/documentation/products/edge-application/edge-functions/runtime-api/ai-integration/) helps you to write, refactor, and review code. +The [Functions Code Editor](/en/documentation/products/applications/functions/runtime-api/code-editor/) provides a development experience similar to what developers are accustomed to. The [Functions ChatGPT Integration](/en/documentation/products/applications/functions/runtime-api/ai-integration/) helps you to write, refactor, and review code. --- @@ -43,7 +43,7 @@ To develop your first function for Applications: **Writing an function** -First, the functions for applications work based on a [fetch event](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/fetch/). It's initialized with an `addEventListener` function, passing `fetch` as the event type, and an event. For example: +First, the functions for applications work based on a [fetch event](/en/documentation/products/applications/functions/runtime-apis/javascript/fetch/). It's initialized with an `addEventListener` function, passing `fetch` as the event type, and an event. For example: ```javascript addEventListener('fetch', event => { @@ -88,7 +88,7 @@ In this example, the response will be the HTML content, declared previously by t After writing your functions, you can preview the response and inspect the code. The preview simulates a request, and this simulation can be altered to meet the developer's needs. -Learn more about [Azion Preview Deployment](/en/documentation/products/edge-application/edge-functions/runtime-api/preview-deployment/). +Learn more about [Azion Preview Deployment](/en/documentation/products/applications/functions/runtime-api/preview-deployment/). It's possible to debug the functions through: @@ -101,5 +101,5 @@ It's possible to debug the functions through: Once you've saved your function, it's necessary to instantiate it in an application. -[Learn more on how to instantiate a function on Applications](/en/documentation/products/build/edge-application/edge-functions-instances/). +[Learn more on how to instantiate a function on Applications](/en/documentation/products/build/applications/functions-instances/). diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/lang-wasm/lang-wasm.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/lang-wasm/lang-wasm.mdx index b3e353ff6d..df484c60fb 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/lang-wasm/lang-wasm.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/lang-wasm/lang-wasm.mdx @@ -69,7 +69,7 @@ The const `wasmCode` is the binary representation of the following [WAT](https:/ 6. Click the **Save** button. -Now, the function is ready to be instantiated in an application. Check how to [instantiate and execute the functions in your application](/en/documentation/products/build/edge-application/edge-functions-instances/) and try it out. +Now, the function is ready to be instantiated in an application. Check how to [instantiate and execute the functions in your application](/en/documentation/products/build/applications/functions-instances/) and try it out. The expected output of the recently created function is similar to: diff --git a/src/content/docs/en/pages/build-journey/develop-with-azion/toolsAzion-IDE/code-editor.mdx b/src/content/docs/en/pages/build-journey/develop-with-azion/toolsAzion-IDE/code-editor.mdx index b93f855a9d..d1bd276ca8 100644 --- a/src/content/docs/en/pages/build-journey/develop-with-azion/toolsAzion-IDE/code-editor.mdx +++ b/src/content/docs/en/pages/build-journey/develop-with-azion/toolsAzion-IDE/code-editor.mdx @@ -10,7 +10,7 @@ permalink: /documentation/products/build/develop-with-azion/code-editor/ import LinkButton from 'azion-webkit/linkbutton' - + Azion code editor for Functions is user-friendly and is built on the Monaco code editor, known from VS Code, making it easy for those familiar with VS Code to adapt. diff --git a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-cache-settings/cache-settings.mdx b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-cache-settings/cache-settings.mdx index 9b3c253008..e5dd92fd53 100644 --- a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-cache-settings/cache-settings.mdx +++ b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-cache-settings/cache-settings.mdx @@ -12,10 +12,10 @@ permalink: /documentation/products/guides/build/tune-cache-settings/ import Tabs from '~/components/tabs/Tabs' -Leverage the capabilities of [Cache](/en/documentation/products/build/edge-application/cache-settings/) to configure your application's [cache policies](/en/documentation/products/build/edge-application/cache-settings/), including expiration values at the edge or browser level, large file optimization to break large files into smaller chunks, and cache key segmentation based on HTTP methods, query strings, cookies, or device groups. +Leverage the capabilities of [Cache](/en/documentation/products/build/applications/cache-settings/) to configure your application's [cache policies](/en/documentation/products/build/applications/cache-settings/), including expiration values at the edge or browser level, large file optimization to break large files into smaller chunks, and cache key segmentation based on HTTP methods, query strings, cookies, or device groups. :::caution[warning] -Some cache features require the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module to be active. If **Application Accelerator** is activated, data transfer could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. +Some cache features require the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module to be active. If **Application Accelerator** is activated, data transfer could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. ::: --- @@ -56,9 +56,9 @@ If your application isn't sending `Cache-Control` and `Expires` headers or the v 4. Add the TTL in seconds in the **Max Age (seconds)** field. For example: `864000` = 10 days. :::note -The maximum and default TTL values for the edge should be between `60` and `31536000` seconds (1 year). If you have the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module activated, you can set this value to a minimum of `0`. Additionally, if you have the [Cache](/en/documentation/products/build/edge-application/tiered-cache/) module activated and wish to maintain cache in the cache layer, you must set TTL to at least `3` seconds. +The maximum and default TTL values for the edge should be between `60` and `31536000` seconds (1 year). If you have the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module activated, you can set this value to a minimum of `0`. Additionally, if you have the [Cache](/en/documentation/products/build/applications/cache/tiered-cache/) module activated and wish to maintain cache in the cache layer, you must set TTL to at least `3` seconds. -A TTL zero isn't the same as a cache bypass. For more details, read about the difference between these settings on the [Bypass Cache behavior](/en/documentation/products/build/edge-application/rules-engine/#bypass-cache) documentation. +A TTL zero isn't the same as a cache bypass. For more details, read about the difference between these settings on the [Bypass Cache behavior](/en/documentation/products/build/applications/rules-engine/#bypass-cache) documentation. ::: **Stale cache** @@ -67,7 +67,7 @@ Azion provides the capability to serve stale content from the cache when the ori **Large file optimization** -Instead of downloading a large content file and risking timeouts or connection terminations, [files can be fragmented](/en/documentation/products/build/edge-application/cache-settings/#large-file-optimization) into smaller pieces and cached on-demand. +Instead of downloading a large content file and risking timeouts or connection terminations, [files can be fragmented](/en/documentation/products/build/applications/cache-settings/#large-file-optimization) into smaller pieces and cached on-demand. 5. In **Large file optimization**, enable the switch to activate. 6. The **Cache** layer is already selected by default. If you have the **Cache** module activated, you can also enable this feature for the cache layer. @@ -78,10 +78,10 @@ The default fragment size is of `1024 kB`. **Application Accelerator** -This section lets you customize how cache varies based on HTTP methods, query string fields, cookies and device groups through [cache keys](/en/documentation/products/build/edge-application/cache-settings/#advanced-cache-key). You can choose to segment cache keys using these attributes to control how objects are stored and served from the cache. +This section lets you customize how cache varies based on HTTP methods, query string fields, cookies and device groups through [cache keys](/en/documentation/products/build/applications/cache-settings/#advanced-cache-key). You can choose to segment cache keys using these attributes to control how objects are stored and served from the cache. :::caution[warning] -To enable all Application Accelerator functionalities, you must activate the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module. +To enable all Application Accelerator functionalities, you must activate the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module. ::: To determine content variation in cache: @@ -122,7 +122,7 @@ Once you've finished configuring your cache setting: **Activating your cache setting** -The cache settings page now lists the newly created instance. However, this new cache setting isn't active in your application. You need to define what will trigger the implementation of the cache policies in your application. For this, you can use your application's [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/). +The cache settings page now lists the newly created instance. However, this new cache setting isn't active in your application. You need to define what will trigger the implementation of the cache policies in your application. For this, you can use your application's [Rules Engine](/en/documentation/products/build/applications/rules-engine/). The instructions below will help you create a rule in which any request from your users to `xxxxxxxxxx.map.azionedge.net/cache` will apply the cache setting you created. @@ -147,7 +147,7 @@ To verify how your content is being cached, you can [verify application cache in -1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module: +1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module: ```bash curl --location --request PATCH 'https://api.azionapi.net/v4/edge_applications/' \ @@ -230,8 +230,8 @@ curl --location 'https://api.azionapi.net/v4/edge_application/applications/ -Configure your application to handle error responses from the origin using [Error Responses](/en/documentation/products/build/edge-application/error-responses/). Azion allows you to set a cache TTL for error pages, a custom path, or deliver another HTTP code in the response without needing to change the source code of your application. +Configure your application to handle error responses from the origin using [Error Responses](/en/documentation/products/build/applications/error-responses/). Azion allows you to set a cache TTL for error pages, a custom path, or deliver another HTTP code in the response without needing to change the source code of your application. With this guide, you'll modify the default error response of your application, setting a cache TTL for each error received from the origin. diff --git a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-functions-instances/functions-instances.mdx b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-functions-instances/functions-instances.mdx index 18772cc214..0cc9c0261a 100644 --- a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-functions-instances/functions-instances.mdx +++ b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-functions-instances/functions-instances.mdx @@ -15,12 +15,12 @@ import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -Instantiate [serverless functions](/en/documentation/products/build/edge-application/edge-functions-instances/) directly within your application. +Instantiate [serverless functions](/en/documentation/products/build/applications/functions-instances/) directly within your application. This guide uses the pre-configured *Azion - Hello World* function, which is linked to your account. You can repeat this process using any function already available on [Azion Marketplace](/en/documentation/products/marketplace/) or [develop your own function](/en/documentation/products/guides/edge-functions/api-builder/). :::caution[warning] -You must activate the [Functions](/en/documentation/products/build/edge-application/edge-functions/) module to implement functions in your application. If **Functions** is activated, computing time and invocations could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. +You must activate the [Functions](/en/documentation/products/build/applications/functions/) module to implement functions in your application. If **Functions** is activated, computing time and invocations could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. ::: --- @@ -49,7 +49,7 @@ The functions page now lists the newly created instance. However, this new funct 14. Under the **Criteria** section, select the variable `${uri}`. :::note -The `${uri}` variable may already be selected by default if you didn't activate the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module. +The `${uri}` variable may already be selected by default if you didn't activate the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module. ::: 15. As a comparison operator, select **is equal**. @@ -62,7 +62,7 @@ To see your function running, access your application [using its domain](/en/doc -1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Functions](/en/documentation/products/build/edge-application/edge-functions/) module: +1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Functions](/en/documentation/products/build/applications/functions/) module: -1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module: +1. Run the following `PATCH` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/) to activate the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module: + Through the reverse proxy architecture, the edge processes user requests and maintains cached data, decentralizing object storage and optimizing the rates and efficiency of data transfer. This scalability allows you to adapt to increasing traffic demands without overloading your infrastructure, also reducing maintenance costs. ![Overview of a request/response through Applications](/assets/docs/images/uploads/edge-app-overview.png) -When a user requests content from your application, their browser converts the requested [domain](/en/documentation/products/build/edge-application/domains/) into a pre-set IP address via DNS resolution. +When a user requests content from your application, their browser converts the requested [domain](/en/documentation/products/build/applications/domains/) into a pre-set IP address via DNS resolution. -The request is directed to an edge node, where it's processed. At this stage, in addition to security and observability customizations, the edge node processes the request and executes configuration procedures, such as [behaviors](/en/documentation/products/build/edge-application/rules-engine/) and [cache directives](/en/documentation/products/build/edge-application/cache-settings/). +The request is directed to an edge node, where it's processed. At this stage, in addition to security and observability customizations, the edge node processes the request and executes configuration procedures, such as [behaviors](/en/documentation/products/build/applications/rules-engine/) and [cache directives](/en/documentation/products/build/applications/cache-settings/). -Any cached content at the edge gets delivered directly in the response to the user. Following this, the system can apply [load balancing algorithms](/en/documentation/products/secure/edge-connector/load-balancer/) to distribute requests across multiple origins. +Any cached content at the edge gets delivered directly in the response to the user. Following this, the system can apply [load balancing algorithms](/en/documentation/products/secure/connectors/load-balancer/) to distribute requests across multiple origins. After the mediation by the Azion Web Platform, the request reaches its origin that responds back. The edge once again processes this response before delivering it to the user. diff --git a/src/content/docs/en/pages/build-journey/work-with-data/environment-variables.mdx b/src/content/docs/en/pages/build-journey/work-with-data/environment-variables.mdx index acd6af438a..d35acd68b8 100644 --- a/src/content/docs/en/pages/build-journey/work-with-data/environment-variables.mdx +++ b/src/content/docs/en/pages/build-journey/work-with-data/environment-variables.mdx @@ -13,7 +13,7 @@ namespace: documentation_build_data_env_vars import LinkButton from 'azion-webkit/linkbutton' - + Environment variables are a crucial aspect of software development and deployment. diff --git a/src/content/docs/en/pages/changelog/previous-years/previous-years-changelog.mdx b/src/content/docs/en/pages/changelog/previous-years/previous-years-changelog.mdx index ef5a4f97e3..6c0ec4b2ee 100644 --- a/src/content/docs/en/pages/changelog/previous-years/previous-years-changelog.mdx +++ b/src/content/docs/en/pages/changelog/previous-years/previous-years-changelog.mdx @@ -38,11 +38,11 @@ See the updates from previous years below. **Edge Application** -* **Digital Certificates:** we are now supporting **CSR generation** on our platform. A Certificate Signing Request (CSR) is one of the first steps to obtaining your own TLS certificate with the CA (Certificate Authority) of your choice. Learn more about this feature [here](/en/documentation/products/secure/edge-firewall/digital-certificates/). +* **Digital Certificates:** we are now supporting **CSR generation** on our platform. A Certificate Signing Request (CSR) is one of the first steps to obtaining your own TLS certificate with the CA (Certificate Authority) of your choice. Learn more about this feature [here](/en/documentation/products/secure/firewall/certificate-manager/). **Edge Firewall** -* **WAF Self-Calibration:** with the new **Tuning** option, you can view insights and customize which rules will be allowed quickly and easily, with just a few clicks. Read the [documentation](/en/documentation/products/secure/edge-firewall/web-application-firewall/) for more information. +* **WAF Self-Calibration:** with the new **Tuning** option, you can view insights and customize which rules will be allowed quickly and easily, with just a few clicks. Read the [documentation](/en/documentation/products/secure/firewall/web-application-firewall/) for more information. ## Updates @@ -164,7 +164,7 @@ See the updates from previous years below. **Firewall** -* **Web Application Firewall** has a new feature: _Custom Allowed Rules_, which allows you to select specific Rules IDs, improving the creation and editing of [WAF](/en/documentation/products/secure/edge-firewall/web-application-firewall/) rules. In addition, Firewall gained two fields: _last editor_ and _last modified_. Respectively, they display who created or edited a rule and when this has occurred. +* **Web Application Firewall** has a new feature: _Custom Allowed Rules_, which allows you to select specific Rules IDs, improving the creation and editing of [WAF](/en/documentation/products/secure/firewall/web-application-firewall/) rules. In addition, Firewall gained two fields: _last editor_ and _last modified_. Respectively, they display who created or edited a rule and when this has occurred. **Functions** @@ -231,7 +231,7 @@ See the updates from previous years below. **Edge Application** -* We've added a functionality for [multiport](/en/documentation/products/build/edge-application/#multiport) access to Edge Application, making your implementation more flexible. +* We've added a functionality for [multiport](/en/documentation/products/build/applications/#multiport) access to Edge Application, making your implementation more flexible. ## Updates @@ -246,7 +246,7 @@ See the updates from previous years below. **Edge Application** * Now, with support for using [HTTP](https://api.azion.com/) methods (POST, PUT, PATCH and DELETE) in Functions JavaScript, improving performance, flexibility, and security issues; -* We have also improved security issues when creating rules in [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/). +* We have also improved security issues when creating rules in [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/). **Real Time Events** @@ -379,7 +379,7 @@ See the updates from previous years below. **Edge Application** -* A new feature, [Slice configuration](/en/documentation/products/build/edge-application/edge-cache/#file-slicing), is available on Edge Application. +* A new feature, [Slice configuration](/en/documentation/products/build/applications/cache/#file-slicing), is available on Edge Application. **Edge Orchestrator** @@ -521,10 +521,10 @@ See the updates from previous years below. * Making [API](/en/documentation/products/secure/edge-dns/) available for managing Zones and Records for the Edge DNS product. * Added the graph referring to the "Data Stream Requests" metric of the Data Stream product, in the Real-Time Metrics interface. -* Added support for ECC - _Elliptic Curve Cryptography_ in [Digital Certificates](/en/documentation/products/secure/edge-firewall/digital-certificates/). +* Added support for ECC - _Elliptic Curve Cryptography_ in [Digital Certificates](/en/documentation/products/secure/firewall/certificate-manager/). * Improvements in the propagation of Json args from Function Instances. * Bug fix when editing _Origins_ through the Real-Time Manager interface. -* Bug fix on the _subdomain_ purge when using [Wildcard Purge](/en/documentation/products/build/edge-application/real-time-purge/). +* Bug fix on the _subdomain_ purge when using [Wildcard Purge](/en/documentation/products/build/applications/real-time-purge/). --- @@ -533,8 +533,8 @@ See the updates from previous years below. * Added "host" variable to Real-Time Events for Data Source "Edge Application". * Bug fix in the Real-Time Events interface. * Added the graph referring to the "Data Streamed" metric of the Data Stream product, in the Real-Time Metrics interface. -* New Bot Management solution integrated to the Azion platform, using [Functions](/en/documentation/products/build/edge-application/edge-functions/) in [Firewall](/en/documentation/products/secure/edge-firewall/). -* Added [TLS Minimum Version](/en/documentation/products/build/edge-application/#digital-certificates) selection component to the Application interface. +* New Bot Management solution integrated to the Azion platform, using [Functions](/en/documentation/products/build/applications/functions/) in [Firewall](/en/documentation/products/secure/firewall/). +* Added [TLS Minimum Version](/en/documentation/products/build/applications/#digital-certificates) selection component to the Application interface. * Bug fix in [Api V3](https://api.azion.com/) page when listing Applications. * Bug fix in [Api V3](https://api.azion.com/) page when listing Edge Applications. @@ -831,7 +831,7 @@ See the updates from previous years below. **nov/2017** -* New [types of purge](/en/documentation/products/build/edge-application/real-time-purge/): purges can now be done via URL, CacheKey or Wildcard. +* New [types of purge](/en/documentation/products/build/applications/real-time-purge/): purges can now be done via URL, CacheKey or Wildcard. * The purge history will now show the type, method and form in which the system received the purge request. * Bug fix for purge in the case of URLs with Unicode. @@ -861,8 +861,8 @@ Note: Just as the interface has been updated to require the purge type, the [Pur **jul/2017** -* [Edge Firewall's](/en/documentation/products/secure/edge-firewall/) IP Blocking functionality is integrated into Real-Time Manager. -* [Edge Firewall](/en/documentation/products/secure/edge-firewall/) IP Blocking integrated in to the API. +* [Edge Firewall's](/en/documentation/products/secure/firewall/) IP Blocking functionality is integrated into Real-Time Manager. +* [Edge Firewall](/en/documentation/products/secure/firewall/) IP Blocking integrated in to the API. * Integration of the functionality that allows the download of the advanced settings file (_locked_) with Real-Time Manager, when required by the customer. --- @@ -882,7 +882,7 @@ Note: Just as the interface has been updated to require the purge type, the [Pur * Implementation of the Elastic Search endpoint in the [Data Stream](/en/documentation/products/observe/data-stream/) product. * Implementation of new features in Lua in Content Delivery for advanced conditional rules. * Implementation of new Device Detection functionalities for configuring conditional rules based on the device. -* Evolution of the Learning Tool of the [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/) product. +* Evolution of the Learning Tool of the [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/) product. --- @@ -913,7 +913,7 @@ Note: Just as the interface has been updated to require the purge type, the [Pur * Launch of endpoints to configure the Content Delivery API. * Launch of the new [Data Stream](/en/documentation/products/observe/data-stream/) product. -* Improvements to the texts of the [Advanced Cache Key](/en/documentation/products/build/edge-application/application-accelerator/#advanced-cache-key) options. +* Improvements to the texts of the [Advanced Cache Key](/en/documentation/products/build/applications/application-accelerator/#advanced-cache-key) options. * Improvements in the behavior of the Rules Engine, to simplify the flow of creating Redirect and Access Denied rules. * Implementation of the customizable “Add Request Header” functionality in the Adaptive Delivery product. @@ -921,14 +921,14 @@ Note: Just as the interface has been updated to require the purge type, the [Pur **jan/2017** -* Renewal of the Azion [Shared Certificate](/en/documentation/products/secure/edge-firewall/digital-certificates/) with CA, for all customers of the product. +* Renewal of the Azion [Shared Certificate](/en/documentation/products/secure/firewall/certificate-manager/) with CA, for all customers of the product. * Fix for the creation/editing of the Rule Engine in Real-Time Manager to make the selection of an Edge Firewall rule set optional. * Fix for viewing graphs in Analytics that account for the occupation of the RawLogs bucket in Cloud Storage. * Fix for using Image Optimization in conjunction with Cloud Storage without the need to create a segregated Configuration. * Performance optimization when loading Real-Time Manager. * Launch of authentication framework in the [Azion API](https://api.azion.com/). * Launch of analytics data query endpoints in the Azion API. -* Integration of the Advanced Cache Key functionalities (cache key by cookie and cache key by query string) of the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) product with Real-Time Manager. +* Integration of the Advanced Cache Key functionalities (cache key by cookie and cache key by query string) of the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) product with Real-Time Manager. * Launching of a new Cache Settings tab and changing the behavior of the Rules Engine tab, in Real-Time Manager, to enable the reuse of cache settings by path. --- @@ -949,8 +949,8 @@ Note: Just as the interface has been updated to require the purge type, the [Pur **ago/2016** * HTTP/2 support. -* Update of the Origins tab in Real-Time Manager to integrate the [Load Balancer](/en/documentation/products/secure/edge-connector/load-balancer/) product functionalities. -* Update of Real-Time Manager to include the new interface for creating [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/) rule sets. +* Update of the Origins tab in Real-Time Manager to integrate the [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/) product functionalities. +* Update of Real-Time Manager to include the new interface for creating [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/) rule sets. --- @@ -958,19 +958,19 @@ Note: Just as the interface has been updated to require the purge type, the [Pur * Update in the Permissions by Time interface, in Real-Time Manager. * Real-time Wildcard Purge support. -* Update of the [Image Optimization](/en/documentation/products/build/edge-application/image-processor/) platform, with good gains in image optimization. +* Update of the [Image Optimization](/en/documentation/products/build/applications/image-processor/) platform, with good gains in image optimization. --- **may/2016** -* Launch of the new interface for uploading [Digital Certificates](/en/documentation/products/secure/edge-firewall/digital-certificates/) to Real-Time Manager. +* Launch of the new interface for uploading [Digital Certificates](/en/documentation/products/secure/firewall/certificate-manager/) to Real-Time Manager. * New point of presence (POP) in Rio de Janeiro. --- **apr/2016** -* Update of the [Edge Firewall](/en/documentation/products/secure/edge-firewall/) interface to support the reuse of rule sets. +* Update of the [Edge Firewall](/en/documentation/products/secure/firewall/) interface to support the reuse of rule sets. * Update of the Custom Headers interface to support configuration reuse. * Launching of the tab for configuring Device Groups and updating the Rules Engine tab for integrating the Adaptive Delivery product. diff --git a/src/content/docs/en/pages/deploy-journey/advanced-config/explore-usage/explore-usage.mdx b/src/content/docs/en/pages/deploy-journey/advanced-config/explore-usage/explore-usage.mdx index 549bd01dcc..cddfdaea5e 100644 --- a/src/content/docs/en/pages/deploy-journey/advanced-config/explore-usage/explore-usage.mdx +++ b/src/content/docs/en/pages/deploy-journey/advanced-config/explore-usage/explore-usage.mdx @@ -24,7 +24,7 @@ The list of commands includes: - Help with general commands. - Status of the execution of the agent. - + You can [check logs](/en/documentation/products/guides/deploy/watch-logs/) related to the edge nodes execution by accessing the file `/var/log/azion/edge-orchestrator.log` and edge services logs in `/var/log/azion/edge-services.log`. diff --git a/src/content/docs/en/pages/deploy-journey/automate/zero-touch-provisioning/zero-touch-provisioning.mdx b/src/content/docs/en/pages/deploy-journey/automate/zero-touch-provisioning/zero-touch-provisioning.mdx index 3e050aeefa..212480ab70 100644 --- a/src/content/docs/en/pages/deploy-journey/automate/zero-touch-provisioning/zero-touch-provisioning.mdx +++ b/src/content/docs/en/pages/deploy-journey/automate/zero-touch-provisioning/zero-touch-provisioning.mdx @@ -14,7 +14,7 @@ menu_namespace: deployMenu import LinkButton from 'azion-webkit/linkbutton' -[Azion Orchestrator](/en/documentation/products/deploy/edge-orchestrator/) is a programmable and extensible cloud-management and *zero-touch provisioning* orchestration service purposely built for edge infrastructures and applications. +[Azion Orchestrator](/en/documentation/products/deploy/orchestrator/) is a programmable and extensible cloud-management and *zero-touch provisioning* orchestration service purposely built for edge infrastructures and applications. diff --git a/src/content/docs/en/pages/deploy-journey/configure-node/authorize-node/authorize-node.mdx b/src/content/docs/en/pages/deploy-journey/configure-node/authorize-node/authorize-node.mdx index 0542f63dca..c949b2472d 100644 --- a/src/content/docs/en/pages/deploy-journey/configure-node/authorize-node/authorize-node.mdx +++ b/src/content/docs/en/pages/deploy-journey/configure-node/authorize-node/authorize-node.mdx @@ -58,7 +58,7 @@ curl --location --request PATCH 'https://api.azionapi.net/edge_nodes/authorize' }' ``` -Now, your edge node is authorized and able to work with [edge services](/en/documentation/products/deploy/edge-orchestrator/edge-services/). +Now, your edge node is authorized and able to work with [edge services](/en/documentation/products/deploy/orchestrator/edge-services/). :::tip Check the [Azion API documentation](https://api.azion.com/) and the [OpenAPI specification](https://github.com/aziontech/azionapi-openapi/) to know more about all features available via API. diff --git a/src/content/docs/en/pages/deploy-journey/configure-node/work-with-variables/work-with-variables.mdx b/src/content/docs/en/pages/deploy-journey/configure-node/work-with-variables/work-with-variables.mdx index abb11a693e..9b96af7432 100644 --- a/src/content/docs/en/pages/deploy-journey/configure-node/work-with-variables/work-with-variables.mdx +++ b/src/content/docs/en/pages/deploy-journey/configure-node/work-with-variables/work-with-variables.mdx @@ -14,7 +14,7 @@ menu_namespace: deployMenu import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -During the deployment process on [Orchestrator](/en/documentation/products/deploy/edge-orchestrator/), you can work with variables. A variable can be set on an [edge service](#edge-services-variables) and an [edge node](#edge-node-variables). +During the deployment process on [Orchestrator](/en/documentation/products/deploy/orchestrator/), you can work with variables. A variable can be set on an [edge service](#edge-services-variables) and an [edge node](#edge-node-variables). You can create edge node and edge services variables using: diff --git a/src/content/docs/en/pages/deploy-journey/deploy-service/deploy-service.mdx b/src/content/docs/en/pages/deploy-journey/deploy-service/deploy-service.mdx index f41e2ce1ac..23a721f2c8 100644 --- a/src/content/docs/en/pages/deploy-journey/deploy-service/deploy-service.mdx +++ b/src/content/docs/en/pages/deploy-journey/deploy-service/deploy-service.mdx @@ -84,7 +84,7 @@ With the Orchestrator Agent installed on the device:
- + --- diff --git a/src/content/docs/en/pages/deploy-journey/overview/overview.mdx b/src/content/docs/en/pages/deploy-journey/overview/overview.mdx index c9d18d5a24..e1934d6e63 100644 --- a/src/content/docs/en/pages/deploy-journey/overview/overview.mdx +++ b/src/content/docs/en/pages/deploy-journey/overview/overview.mdx @@ -16,7 +16,7 @@ Azion **Deploy** products are designed to enhance the efficiency of managing edg ## Orchestrator -[Azion Orchestrator](/en/documentation/products/deploy/edge-orchestrator/) is a versatile system for edge computing innovation, enabling efficient workload deployment, management, and automation across edge networks, on-premises, remote devices, and multi-cloud platforms. Designed to orchestrate your applications and [edge services](/en/documentation/products/deploy/edge-orchestrator/edge-services/) on [edge nodes](/en/documentation/products/deploy/edge-orchestrator/edge-node/) by integrating with Azion's built-in products and features, as well as proprietary or third-party applications, services, or resources. +[Azion Orchestrator](/en/documentation/products/deploy/orchestrator/) is a versatile system for edge computing innovation, enabling efficient workload deployment, management, and automation across edge networks, on-premises, remote devices, and multi-cloud platforms. Designed to orchestrate your applications and [edge services](/en/documentation/products/deploy/orchestrator/edge-services/) on [edge nodes](/en/documentation/products/deploy/orchestrator/edge-node/) by integrating with Azion's built-in products and features, as well as proprietary or third-party applications, services, or resources. The system provides robust *end-to-end encryption* and *multi-layer security*, facilitating secure data flow while freeing valuable IT resources. Flexible and adaptable, it can accommodate complex mission-critical environments and is compatible with multiple hardware and network architectures, capable of running natively on the operating system, within containers, or on top of the [Azion Runtime](/en/documentation/runtime/overview/). @@ -26,7 +26,7 @@ An Azion Orchestrator agent is installed on edge nodes and provides end-to-end e When the Azion Orchestrator Agent is installed on a device and the device is authorized, it now represents an edge node. A service can be linked to many edge nodes. When a service is updated, it'll automatically be deployed to the edge nodes to which it's related. ::: - + @@ -36,7 +36,7 @@ When the Azion Orchestrator Agent is installed on a device and the device is aut It allows configuration of install, uninstall, and reload triggers, and definition of resource dependencies for edge network service execution. - + ### Edge Nodes @@ -45,6 +45,6 @@ An edge node is a device that has Azion Orchestrator Agent installed and enables Orchestrator allows customers to manage their own edge nodes, independent of the Azion distributed network. To start provisioning applications, it's essential to configure edge nodes. - + diff --git a/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx b/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx index b56bef7540..86ef107ba3 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/features/consumption-fields.mdx @@ -39,8 +39,8 @@ If you're logged in with a group or reseller account, you can query the consumpt | Product name | Product ID | Modules | Metric name/Calculated Field | |---------------|-------------|---------------|-------------| | [Data Stream](/en/documentation/products/guides/query-data-stream-usage-data-with-graphql/) | 1498670028 | - | - `data_streamed`: total volume of data streamed through Data Stream.
- `requests`: total number of requests processed by Data Stream. | -| [Applications](/en/documentation/products/guides/query-edge-application-usage-data-with-graphql/) | 1441740010 | - image_processor
- edge_firewall
- load_balancer
- application_accelerator | - `data_transferred_total`: total amount of data transferred through Applications.
- `requests`: total number of requests received by Application.
- `waf_requests`: total number of requests inspected by WAF. | -| [Functions](/en/documentation/products/guides/query-edge-functions-usage-data-with-graphql/) | 1531930033 | - | - `compute_time`: Total execution time (in milliseconds) of Functions in milliseconds.
- `invocations`: total number of times an function was executed. | +| [Applications](/en/documentation/products/guides/query-applications-usage-data-with-graphql/) | 1441740010 | - image_processor
- edge_firewall
- load_balancer
- application_accelerator | - `data_transferred_total`: total amount of data transferred through Applications.
- `requests`: total number of requests received by Application.
- `waf_requests`: total number of requests inspected by WAF. | +| [Functions](/en/documentation/products/guides/query-functions-usage-data-with-graphql/) | 1531930033 | - | - `compute_time`: Total execution time (in milliseconds) of Functions in milliseconds.
- `invocations`: total number of times an function was executed. | | [Image Processor](/en/documentation/products/guides/query-image-processor-usage-data-with-graphql/) | 1441110021 | - | `images_processed`: total number of images processed by Image Processor. | | [Cache](/en/documentation/products/guides/query-tiered-cache-usage-data-with-graphql/) | 1564082375 | - | - `data_transferred_total`: total amount of data transferred through Tiered Cache.
- `requests`: total number of cache requests processed by Tiered Cache. | diff --git a/src/content/docs/en/pages/devtools/api-graphql/features/features.mdx b/src/content/docs/en/pages/devtools/api-graphql/features/features.mdx index 5cdcf8b46a..93932489a2 100644 --- a/src/content/docs/en/pages/devtools/api-graphql/features/features.mdx +++ b/src/content/docs/en/pages/devtools/api-graphql/features/features.mdx @@ -42,12 +42,12 @@ Four datasets are deprecated and were replaced by other datsets: | Dataset | Description | | ------- | ----------- | | dataStreamedMetrics | Sent events of data by [Data Stream](/en/documentation/products/observe/data-stream/) to the clients' endpoint | -| edgeFunctionsMetrics | Events executed by [Functions](/en/documentation/products/build/edge-application/edge-functions/) | -| httpMetrics | Request events registered by [Applications](/en/documentation/products/build/edge-application/) and [Firewall](/en/documentation/products/secure/edge-firewall/) | +| edgeFunctionsMetrics | Events executed by [Functions](/en/documentation/products/build/applications/functions/) | +| httpMetrics | Request events registered by [Applications](/en/documentation/products/build/applications/) and [Firewall](/en/documentation/products/secure/firewall/) | | httpBreakdownMetrics | Query real-time, detailed, aggregated data on [HTTP request events blocked](/en/documentation/products/guides/query-httpbreakdownmetrics-data-with-graphql/) | | edgeDnsQueriesMetrics | Query events performed on [Edge DNS](/en/documentation/products/secure/edge-dns/) | -| imagesProcessedMetrics | Image processing events by [Image Processor](/en/documentation/products/build/edge-application/image-processor/) | -| tieredCacheMetrics | Request events registered by [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/) | +| imagesProcessedMetrics | Image processing events by [Image Processor](/en/documentation/products/build/applications/image-processor/) | +| tieredCacheMetrics | Request events registered by [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) | | connectedUsersMetrics | Query the number of users connected to your applications, using [Live Ingest](/en/documentation/products/guides/query-connected-users-data-with-graphql/) | | botManagerMetrics | Query the number of requests evaluated and the actions performed by [Azion Bot Manager](/en/documentation/products/guides/query-bot-manager-data-with-graphql/) (if subscribed) | | botManagerBreakdownMetrics | Query the URLs most impacted by bad bots, according to [Azion Bot Manager](/en/documentation/products/guides/query-bot-manager-breakdown-data-with-graphql/) data (if subscribed) | @@ -61,11 +61,11 @@ Four datasets are deprecated and were replaced by other datsets: | activityHistoryEvents | Events logs from an account on Azion Console regarding activities registered on [Activity History](/en/documentation/products/accounts/activity-history/). It stores data for *2 years* and exhibits data starting from *September 22nd, 2023*. | | cellsConsoleEvents | Events logs from applications using [Azion Runtime](/en/documentation/runtime/overview/) returned by the Cells Console. | | dataStreamedEvents | Sent events of data by [Data Stream](/en/documentation/products/observe/data-stream/) to the clients' endpoint. | -| edgeFunctionsEvents | Events executed by [Functions](/en/documentation/products/build/edge-application/edge-functions/). | -| httpEvents | Request events registered by [Applications](/en/documentation/products/build/edge-application/) and [Firewall](/en/documentation/products/secure/edge-firewall/). | +| edgeFunctionsEvents | Events executed by [Functions](/en/documentation/products/build/applications/functions/). | +| httpEvents | Request events registered by [Applications](/en/documentation/products/build/applications/) and [Firewall](/en/documentation/products/secure/firewall/). | | edgeDnsQueriesEvents | Query events performed on [Edge DNS](/en/documentation/products/secure/edge-dns/). | -| imagesProcessedEvents | Image processing events by [Image Processor](/en/documentation/products/build/edge-application/image-processor/). | -| tieredCacheEvents | Request events registered by [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/). | +| imagesProcessedEvents | Image processing events by [Image Processor](/en/documentation/products/build/applications/image-processor/). | +| tieredCacheEvents | Request events registered by [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/). | | telemetryDeviceInfoEvents | Events related to the device being used for access and recorded by **Azion Mobile SDK**, both at the hardware and software levels. | | telemetrySensorsEvents | Events related to the device's sensors recorded by **Azion Mobile SDK**, such as touchscreen interactions and gyroscope information. | diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/edge-sql/edge-sql.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/edge-sql/edge-sql.mdx index a5f033f395..a5370e4bb0 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/edge-sql/edge-sql.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/edge-sql/edge-sql.mdx @@ -9,7 +9,7 @@ permalink: /documentation/runtime/api-reference/sql-database/ menu_namespace: runtimeMenu --- -The **SQL Database API** provides an interface for interacting with an [SQL Database](/en/documentation/products/store/edge-sql/) database from Functions running on the Azion Web Platform. This document outlines the key components of the API and provides code samples for each. +The **SQL Database API** provides an interface for interacting with an [SQL Database](/en/documentation/products/store/sql-database/) database from Functions running on the Azion Web Platform. This document outlines the key components of the API and provides code samples for each. import LinkButton from 'azion-webkit/linkbutton' diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/environment-variables/environment-variables.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/environment-variables/environment-variables.mdx index 097af201b5..79c1933066 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/environment-variables/environment-variables.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/api-reference/environment-variables/environment-variables.mdx @@ -36,7 +36,7 @@ The Environment Variables interface can be used inside Functions to retrieve env > **Note**: if the key informed is incorrect, it returns `undefined`. -Find out more about [Environment variables](/en/documentation/products/edge-functions/environment-variables/). +Find out more about [Environment variables](/en/documentation/products/functions/environment-variables/). --- diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx index d6f3606319..f15427a635 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx @@ -13,7 +13,7 @@ namespace: documentation_products_edge_functions_runtime_code_editor menu_namespace: runtimeMenu --- -The new code editor for [Functions](/en/documentation/products/build/edge-application/edge-functions/) is the best way to get started developing your functions on the Azion platform. It's a web-based code editor that makes it easier and more intuitive to develop at the edge of the network. It's empowered by the [Monaco Code Editor](https://microsoft.github.io/monaco-editor/docs.html), used in [VS Code](https://code.visualstudio.com/), so if you're used to VS Code, you'll get familiar with it right away. The Monaco Code Editor main features available for the **Functions Code Editor** are: +The new code editor for [Functions](/en/documentation/products/build/applications/functions/) is the best way to get started developing your functions on the Azion platform. It's a web-based code editor that makes it easier and more intuitive to develop at the edge of the network. It's empowered by the [Monaco Code Editor](https://microsoft.github.io/monaco-editor/docs.html), used in [VS Code](https://code.visualstudio.com/), so if you're used to VS Code, you'll get familiar with it right away. The Monaco Code Editor main features available for the **Functions Code Editor** are: - Syntax Highlighting - IntelliSense @@ -23,13 +23,13 @@ The new code editor for [Functions](/en/documentation/products/build/edge-applic ## About the Code Editor -The new code editor for Functions is prepared to [support all types](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/azion-runtime-globals/) and [web APIs](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/web-standards/). +The new code editor for Functions is prepared to [support all types](/en/documentation/products/applications/functions/runtime-apis/javascript/azion-runtime-globals/) and [web APIs](/en/documentation/products/applications/functions/runtime-apis/javascript/web-standards/). ### Code Preview Along with the code editor, it's possible to see the preview of the function being developed, so you can see its outcome on the fly, providing more reliability before the code goes to production. -To know more about the preview, go to [Azion Preview Deployment](/en/documentation/products/edge-application/edge-functions/runtime-api/preview-deployment/). +To know more about the preview, go to [Azion Preview Deployment](/en/documentation/products/applications/functions/runtime-api/preview-deployment/). ### ChatGPT and Functions @@ -40,7 +40,7 @@ Another feature that comes in the package is an integration with [ChatGPT](https - Code explanation - Code generator -Take a look at [Functions ChatGPT integration](/en/documentation/products/edge-application/edge-functions/runtime-api/ai-integration/). +Take a look at [Functions ChatGPT integration](/en/documentation/products/applications/functions/runtime-api/ai-integration/). --- diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/frameworks/template-showcase/nextjs/nextal.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/frameworks/template-showcase/nextjs/nextal.mdx index 34bf6dd23f..4c03aa085b 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/frameworks/template-showcase/nextjs/nextal.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/frameworks/template-showcase/nextjs/nextal.mdx @@ -38,4 +38,4 @@ import Container from 'azion-webkit/container'; -For more information about deploying this template visit the [template guide](/en/documentation/products/guides/nextal/). \ No newline at end of file +For more information about deploying this template visit the [template guide](/en/documentation/products/templates/nextal/). \ No newline at end of file diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx index 349d3f38be..122c4a3a9e 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/compatibility/node-polyfills/cells-node.mdx @@ -139,5 +139,5 @@ You can check the list of APIs resolved through polyfills in [Azion Bundler's re ::: For additional compatibility information: - + diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/debugging/debugging.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/debugging/debugging.mdx index e262f004b9..110f02b643 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/debugging/debugging.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/debugging/debugging.mdx @@ -25,7 +25,7 @@ The debugging process in **Functions** has the purpose of promoting better contr ## How it works -To debug codes, you must create a new [function](/en/documentation/products/build/edge-application/edge-functions/) that will use the **log** method. This method prints to the console a message previously sent by a parameter to the function. +To debug codes, you must create a new [function](/en/documentation/products/build/applications/functions/) that will use the **log** method. This method prints to the console a message previously sent by a parameter to the function. ### Creating an function @@ -65,13 +65,13 @@ Now that you've created the function, you must configure your **application** to To instantiate the newly created function in your application, follow these steps: 1. On the **Products Menu**, navigate to **Build** > **Applications**. -2. Click on the application where you want to add the function or [create a new one](/en/documentation/products/build/edge-application/first-steps/). +2. Click on the application where you want to add the function or [create a new one](/en/documentation/products/build/applications/first-steps/). 3. Go to the **Functions Instances** tab and click **+ Function Instance**. 4. Name your function instance. 5. Select the newly created function from the dropdown menu. 6. Click the **Save** button. -Now your function is instantiated and ready to be used in your application. You can configure the execution conditions and behaviors using the [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/): +Now your function is instantiated and ready to be used in your application. You can configure the execution conditions and behaviors using the [Rules Engine](/en/documentation/products/build/applications/rules-engine/): 1. While still configuring your application, navigate to the **Rules Engine** tab and click the **+ Rule** button. 2. Give your rule a descriptive name. diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/nextjs/2023-02-14-index.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/nextjs/2023-02-14-index.mdx index c5d67d79be..bf16256651 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/nextjs/2023-02-14-index.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/nextjs/2023-02-14-index.mdx @@ -63,7 +63,7 @@ To help improve compatibility, we encourage you to [report bugs](https://github. :::note Azion Functions have a maximum size limit of 50 MB per function. After building your project, pay attention to the compressed (gzipped) size of your deployment package—only the compressed size counts toward this limit. -For more details, see the [documentation on Function size limits](/en/documentation/products/build/edge-application/edge-functions/#limits). +For more details, see the [documentation on Function size limits](/en/documentation/products/build/applications/functions/#limits). ::: ### Examples diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx index 5709b5fca9..1b8108382f 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/overview/overview.mdx @@ -15,7 +15,7 @@ import Tag from 'primevue/tag'; import LinkButton from 'azion-webkit/linkbutton' -The **Azion Runtime** is a set of tools for developing applications at the **Edge**. The Azion Runtime allows you to write JavaScript [functions](/en/documentation/products/build/edge-application/edge-functions/) built on Web standards. +The **Azion Runtime** is a set of tools for developing applications at the **Edge**. The Azion Runtime allows you to write JavaScript [functions](/en/documentation/products/build/applications/functions/) built on Web standards. **Functions** help you to implement the business logic and create serverless applications, at the edge of the network, closer to users. diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/preview/preview.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/preview/preview.mdx index 56ee992633..46d8ef8b82 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/preview/preview.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/preview/preview.mdx @@ -93,7 +93,7 @@ The output is shown right next to the code editor. It's possible to open it on a ## Preview Provider and ChatGPT -The ChatGPT integration helps you to boost your productivity and, alongside the Preview Deployment, enables more analytical implementations, making it possible to test and see new ideas on the fly. Take a look at [Functions Chat GPT integration](/en/documentation/products/edge-application/edge-functions/runtime-api/ai-integration/). +The ChatGPT integration helps you to boost your productivity and, alongside the Preview Deployment, enables more analytical implementations, making it possible to test and see new ideas on the fly. Take a look at [Functions Chat GPT integration](/en/documentation/products/applications/functions/runtime-api/ai-integration/). --- diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/readable-stream-default-reader/2023-01-31-index.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/readable-stream-default-reader/2023-01-31-index.mdx index b1bd4cd803..9ae28c0495 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/readable-stream-default-reader/2023-01-31-index.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/readable-stream-default-reader/2023-01-31-index.mdx @@ -11,7 +11,7 @@ menu_namespace: runtimeMenu The Streams API's **ReadableStreamDefaultReader** is a default reader used to read stream data obtained from a network, such as a fetch request. -Unlike a [ReadableStreamBYOBReader](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/readable-default-reader/), which only works with streams that have a byte source, the ReadableStreamDefaultReader can be used to read from any type of ReadableStream source. +Unlike a [ReadableStreamBYOBReader](/en/documentation/products/applications/functions/runtime-apis/javascript/readable-default-reader/), which only works with streams that have a byte source, the ReadableStreamDefaultReader can be used to read from any type of ReadableStream source. ## Constructor diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx index 3a52fdbd95..85b805a43e 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/request/2021-01-14-index.mdx @@ -8,11 +8,11 @@ permalink: >- menu_namespace: runtimeMenu --- -The `Request` interface represents an HTTP request and integrates the [Fetch API](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/fetch/). +The `Request` interface represents an HTTP request and integrates the [Fetch API](/en/documentation/products/applications/functions/runtime-apis/javascript/fetch/). ## How it works -The Request object can be built and also seen as the property of a [fetchevent](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/fetch-event/) received by function. +The Request object can be built and also seen as the property of a [fetchevent](/en/documentation/products/applications/functions/runtime-apis/javascript/fetch-event/) received by function. ```js addEventListener("fetch", event => { diff --git a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/response/2021-01-14-index.mdx b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/response/2021-01-14-index.mdx index 75b15b1387..5ac4212f71 100644 --- a/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/response/2021-01-14-index.mdx +++ b/src/content/docs/en/pages/devtools/azion-edge-runtime/runtime-apis/response/2021-01-14-index.mdx @@ -10,7 +10,7 @@ permalink: >- menu_namespace: runtimeMenu --- -The `Response` interface represents an HTTP response and integrates the [Fetch API](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/fetch/). +The `Response` interface represents an HTTP response and integrates the [Fetch API](/en/documentation/products/applications/functions/runtime-apis/javascript/fetch/). ## Constructor diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx index b5bf8a227d..c715be9178 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx @@ -172,7 +172,7 @@ For applications that require processing on the edge (compute) rather than only - + 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 2932153a83..42c0cf4a1d 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 @@ -67,4 +67,4 @@ The `--firewall` option indicates the function is intended for Firewall.
- + diff --git a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/update/update.mdx b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/update/update.mdx index 9df9e215db..672c57cbd3 100644 --- a/src/content/docs/en/pages/devtools/cli/azion-cli/commands/update/update.mdx +++ b/src/content/docs/en/pages/devtools/cli/azion-cli/commands/update/update.mdx @@ -45,11 +45,11 @@ The `--application-id` flag specifies the application's ID to be updated. ##### application-acceleration -The `--application-acceleration` flag specifies if the application has the [Application Acceleration](/en/documentation/products/build/edge-application/application-accelerator/) module active. +The `--application-acceleration` flag specifies if the application has the [Application Acceleration](/en/documentation/products/build/applications/application-accelerator/) module active. ##### delivery-protocol -The `--delivery-protocol` flag specifies the application's [delivery protocol](/en/documentation/products/build/edge-application/main-settings/). +The `--delivery-protocol` flag specifies the application's [delivery protocol](/en/documentation/products/build/applications/main-settings/). ##### device-detection @@ -61,7 +61,7 @@ The `--edge-firewall` flag specifies whether the application has an associated f ##### edge-functions -The `--edge-functions` flag specifies if the application has the [Functions](/en/documentation/products/build/edge-application/edge-functions/) module active. +The `--edge-functions` flag specifies if the application has the [Functions](/en/documentation/products/build/applications/functions/) module active. ##### http-port @@ -73,7 +73,7 @@ The `--https-port` flag specifies the application's HTTPS Port. By default, it's ##### image-optimization -The `--image-optimization` flag specifies if the application has the [Image Processor](/en/documentation/products/build/edge-application/image-processor/) module active. +The `--image-optimization` flag specifies if the application has the [Image Processor](/en/documentation/products/build/applications/image-processor/) module active. ##### file @@ -104,11 +104,11 @@ Attributes inside a `JSON` file: ##### l2-caching -The `--l2-caching` flag specifies if the application has the [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/) module active. +The `--l2-caching` flag specifies if the application has the [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) module active. ##### load-balancer -The `--load-balancer` flag specifies if the application has the [Load Balancer](/en/documentation/products/secure/edge-connector/load-balancer/) module active. +The `--load-balancer` flag specifies if the application has the [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/) module active. ##### min-tsl-ver diff --git a/src/content/docs/en/pages/guides/data-streaming/debug-functions-dts.mdx b/src/content/docs/en/pages/guides/data-streaming/debug-functions-dts.mdx index 043b75a7be..1ada956039 100644 --- a/src/content/docs/en/pages/guides/data-streaming/debug-functions-dts.mdx +++ b/src/content/docs/en/pages/guides/data-streaming/debug-functions-dts.mdx @@ -18,7 +18,7 @@ The debugging process in functions' code on [Data Stream](/en/documentation/prod Before analyzing the process, you need to apply the debugging code. Find out more on [Debugging functions](/en/documentation/devtools/debugging/). -There are separate instructions using [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and using the new [Workloads](/en/documentation/products/secure/workloads) product. +There are separate instructions using [legacy Domains](/en/documentation/products/build/applications/domains/) settings and using the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx b/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx index 0a02814baf..c22e819d8a 100644 --- a/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx +++ b/src/content/docs/en/pages/guides/debug-rules/debug-rules.mdx @@ -20,9 +20,9 @@ import Tabs from '~/components/tabs/Tabs' You can debug rules using the **GraphQL API**, Azion **Data Stream**, and Azion **Real-Time Events**. - + -There are separate instructions using [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and using the new [Workloads](/en/documentation/products/secure/workloads) product. +There are separate instructions using [legacy Domains](/en/documentation/products/build/applications/domains/) settings and using the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/guides/edge-application/ea-configure-cache-policies.mdx b/src/content/docs/en/pages/guides/edge-application/ea-configure-cache-policies.mdx index a85785d01d..93a0a56d25 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-configure-cache-policies.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-configure-cache-policies.mdx @@ -15,7 +15,7 @@ import LinkButton from 'azion-webkit/linkbutton' Azion **Applications** can keep your content cached at the edge to support high-levels of demand without compromising quality or performance, resulting in a better user experience, faster load times, and lower maintenance costs. -You can optimize processing times by defining the time-to-live (TTL) for cached content at the origin and at the browser, bypass origin cache settings, and forward cookies with [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/). +You can optimize processing times by defining the time-to-live (TTL) for cached content at the origin and at the browser, bypass origin cache settings, and forward cookies with [Rules Engine](/en/documentation/products/build/applications/rules-engine/). :::tip To configure cache settings for dynamic content, see the guide on [How to configure Advanced Cache Key for Applications](/en/documentation/products/guides/advanced-cache-key/). @@ -45,7 +45,7 @@ To create a new cache setting, follow the steps: - Under **Browser Cache Settings**, select **Override Cache Settings** to define how long your content can be cached in browsers. - Under **Cache Settings**, select **Override Cache Settings** to define how long your content can be cached at the edge. 5. If you've chosen to override cache settings, add the desired **Maximum TTL** in seconds. - - At this point, you may also customize other cache settings for dynamic content provided by the [Advanced Cache Key](/en/documentation/products/build/edge-application/cache-settings/#advanced-cache-key) feature. + - At this point, you may also customize other cache settings for dynamic content provided by the [Advanced Cache Key](/en/documentation/products/build/applications/cache-settings/#advanced-cache-key) feature. 6. Click the **Save** button. Next, you must create a rule to apply the cache settings you've created. To do so, follow the steps: @@ -79,7 +79,7 @@ If you want to bypass origin cache policies, you can create a rule as follows: Bypass Cache only affects origin cache policies, not browser cache policies. You can customize browser cache through the **Set Cache Policy** behavior described above. - + --- diff --git a/src/content/docs/en/pages/guides/edge-application/ea-configure-ports/custom-ports.mdx b/src/content/docs/en/pages/guides/edge-application/ea-configure-ports/custom-ports.mdx index df98db05e7..d4f3ba9f39 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-configure-ports/custom-ports.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-configure-ports/custom-ports.mdx @@ -18,7 +18,7 @@ With Azion, you can customize your application's delivery address port as well a The choice of delivery ports are limited to those supported by Azion. However, for retrieving the content from your origins, you can fetch your content from the appropriate origin port, as long as the port exists. -There are separate instructions for API v3 using [legacy Origins](/en/documentation/products/build/edge-application/origins/) settings and API v4 using the new [Connectors](/en/documentation/products/secure/edge-connector/) product. +There are separate instructions for API v3 using [legacy Origins](/en/documentation/products/build/applications/origins/) settings and API v4 using the new [Connectors](/en/documentation/products/secure/connectors/) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/guides/edge-application/ea-cors/check-cors-permissions.mdx b/src/content/docs/en/pages/guides/edge-application/ea-cors/check-cors-permissions.mdx index 96b5ad2399..7363485c5d 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-cors/check-cors-permissions.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-cors/check-cors-permissions.mdx @@ -21,7 +21,7 @@ Complex HTTP requests require additional headers. These are requests that may in ## Enabling CORS permission for non-complex HTTP requests -The first step in allowing CORS access is to create a rule in [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/): +The first step in allowing CORS access is to create a rule in [Rules Engine](/en/documentation/products/build/applications/rules-engine/): 1. Access [Azion Console](https://console.azion.com). 2. Select **Products Menu** > **Applications**. @@ -71,7 +71,7 @@ You may configure other complex request types as you want by adding them to the ## Enabling CORS permission for specific origins -To enable CORS within a configuration for specific origin servers, you'll need to enable the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module: +To enable CORS within a configuration for specific origin servers, you'll need to enable the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module: 1. Access [Azion Console](https://console.azion.com). 2. Select **Products Menu** > **Applications**. diff --git a/src/content/docs/en/pages/guides/edge-application/ea-cors/fix-cors-errors.mdx b/src/content/docs/en/pages/guides/edge-application/ea-cors/fix-cors-errors.mdx index 1c92ccdf9c..c85712ae5b 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-cors/fix-cors-errors.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-cors/fix-cors-errors.mdx @@ -22,7 +22,7 @@ Error message: Access to XMLHttpRequest at `http://a.domain.com/page-cors-subdomain-a.txt' from origin `http://b.domain.com/` has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. -To solve this type of error, configure your browser on [Azion Console](https://console.azion.com) using [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/). +To solve this type of error, configure your browser on [Azion Console](https://console.azion.com) using [Rules Engine](/en/documentation/products/build/applications/rules-engine/). On Google Chrome, proceed as follows: diff --git a/src/content/docs/en/pages/guides/edge-application/ea-create-rules.mdx b/src/content/docs/en/pages/guides/edge-application/ea-create-rules.mdx index de245279c7..de58eba5cf 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-create-rules.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-create-rules.mdx @@ -15,7 +15,7 @@ import LinkButton from 'azion-webkit/linkbutton'; With Azion **Applications** reverse-proxy architecture, the rules you create will be executed between either the **Request phase**, which contains data that a client sends to an origin server, or **Response phase**, which contains data from the origin that is sent to the client. - + --- diff --git a/src/content/docs/en/pages/guides/edge-application/ea-customize-error-responses.mdx b/src/content/docs/en/pages/guides/edge-application/ea-customize-error-responses.mdx index 31689cc4be..42e7803a85 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-customize-error-responses.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-customize-error-responses.mdx @@ -16,7 +16,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' Find out how to configure your Azion application to show custom error pages for your user based on HTTP error statuses. For this guide you must already have an Application, a Connector and a Workload already setup. -There are separate instructions for API v3 using [legacy Error Responses](/en/documentation/products/build/edge-application/error-responses/) settings and API v4 using the new [Custom Pages](/en/documentation/products/secure/custom-pages/) product. +There are separate instructions for API v3 using [legacy Error Responses](/en/documentation/products/build/applications/error-responses/) settings and API v4 using the new [Custom Pages](/en/documentation/products/secure/custom-pages/) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/guides/edge-application/ea-enable-gzip.mdx b/src/content/docs/en/pages/guides/edge-application/ea-enable-gzip.mdx index 1cdb595cb5..a0c710b353 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-enable-gzip.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-enable-gzip.mdx @@ -24,7 +24,7 @@ Check the [official gzip website](https://www.gzip.org/) for useful links and in ## Enabling gzip compression through Rules Engine -You can enable gzip compression for any application using the [Rules Engine for Applications](/en/documentation/products/build/edge-application/rules-engine/). +You can enable gzip compression for any application using the [Rules Engine for Applications](/en/documentation/products/build/applications/rules-engine/). To enable gzip compression for your application, follow these steps: diff --git a/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx b/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx index 11ed9ea3a3..1997107ec3 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-enforce-hls.mdx @@ -21,7 +21,7 @@ Azion Web Platform allows you to [deliver live streaming content in HLS format]( - An existing Azion application, or [create a new one](/en/documentation/products/guides/build/build-an-application/). - [A domain associated with the application](/en/documentation/products/guides/configure-a-domain/). - [Tiered Cache enabled](/en/documentation/products/guides/billing-and-subscriptions/) in your account. -- Access to [Azion Object Storage](/en/documentation/products/store/edge-storage/) for storing video content. +- Access to [Azion Object Storage](/en/documentation/products/store/object-storage/) for storing video content. --- @@ -92,7 +92,7 @@ Still on the **Cache Settings** tab: :::tip -Read more about setting up [cache settings](/en/documentation/products/build/edge-application/cache-settings/) for your applications. +Read more about setting up [cache settings](/en/documentation/products/build/applications/cache-settings/) for your applications. ::: ### Utilizing Azion Object Storage for HLS video delivery @@ -192,7 +192,7 @@ Now, create a rule for the playlist: Done. Now you can configure your source and encoder pointing to Azion and stream your content, enforcing HLS cache. :::tip -Go to the [Rules Engine for Applications](/en/documentation/products/build/edge-application/rules-engine/) documentation for more details. +Go to the [Rules Engine for Applications](/en/documentation/products/build/applications/rules-engine/) documentation for more details. ::: diff --git a/src/content/docs/en/pages/guides/edge-application/ea-fs-image-processor.mdx b/src/content/docs/en/pages/guides/edge-application/ea-fs-image-processor.mdx index 2e11e3f42c..6ef783dcef 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-fs-image-processor.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-fs-image-processor.mdx @@ -9,21 +9,21 @@ namespace: documentation_guides_image_processor permalink: /documentation/products/guides/image-processor/ --- -To configure [Image Processor](/en/documentation/products/build/edge-application/image-processor/), follow the steps below: +To configure [Image Processor](/en/documentation/products/build/applications/image-processor/), follow the steps below: 1. Access [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/) > **Applications**. 2. Select the application responsible for managing your images from your list of existing applications or add a new one with the help of the [build an application](/en/documentation/products/guides/build/build-an-application/) page. 3. In the **Cache Settings** tab, add or edit a custom cache policy for your images. -4. In the **Cache Expiration Policies** section, configure the [expiration policy](/en/documentation/products/build/edge-application/cache-settings/#browser-cache-settings) for your images. +4. In the **Cache Expiration Policies** section, configure the [expiration policy](/en/documentation/products/build/applications/cache-settings/#browser-cache-settings) for your images. :::tip For images, Azion recommends that you choose larger time-to-live (TTL) values, such as the **Maximum TTL** for **Cache Settings**, which is 7.776.000 seconds (3 months). ::: 5. In the **Advanced Cache Key** section, choose one of the following options: - - **Content varies by some Query String fields (Allowlist)**: if you want to list all the fields in the Query String that will identify your images. **Image Processor** uses the *ims* field, so this has to be included in the list as one of the required fields for your image manager application. For this, you must enable the [Application Accelerator module](/en/documentation/products/build/edge-application/application-accelerator/). - - **Content varies by Query String, except for some fields (Blocklist)**: if you only want to list those fields in the Query String that should be ignored to identify the objects in your cache. In this case, it guarantees that the *ims* field will be removed from the list. For this, you must enable the [Application Accelerator module](/en/documentation/products/build/edge-application/application-accelerator/). - - **Content varies by all Query String fields**: if you don't know or aren't sure about which fields to list in the Query String because you aren't responsible for all the content in the cache or don't have [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) activated. + - **Content varies by some Query String fields (Allowlist)**: if you want to list all the fields in the Query String that will identify your images. **Image Processor** uses the *ims* field, so this has to be included in the list as one of the required fields for your image manager application. For this, you must enable the [Application Accelerator module](/en/documentation/products/build/applications/application-accelerator/). + - **Content varies by Query String, except for some fields (Blocklist)**: if you only want to list those fields in the Query String that should be ignored to identify the objects in your cache. In this case, it guarantees that the *ims* field will be removed from the list. For this, you must enable the [Application Accelerator module](/en/documentation/products/build/applications/application-accelerator/). + - **Content varies by all Query String fields**: if you don't know or aren't sure about which fields to list in the Query String because you aren't responsible for all the content in the cache or don't have [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) activated. :::caution To ensure proper processing of images, the `ims=` query string parameter must be the last parameter in the URL. If any additional query string parameters are included after `ims=`, the request may return a **504** error. @@ -54,7 +54,7 @@ To ensure images are successfully converted to AVIF format, you must also add th From this point on, images from the configured path will be automatically processed. -To resize, crop, optimize, convert, or apply filters to an image, you'll need to append the queries described in the [Image Processor](/en/documentation/products/build/edge-application/image-processor/) page to the image's URL, which you may do using an [function](/en/documentation/products/build/edge-application/edge-functions/). To see the original file, you only need to remove the query string added to the URL. +To resize, crop, optimize, convert, or apply filters to an image, you'll need to append the queries described in the [Image Processor](/en/documentation/products/build/applications/image-processor/) page to the image's URL, which you may do using an [function](/en/documentation/products/build/applications/functions/). To see the original file, you only need to remove the query string added to the URL. To confirm whether your image is being optimized, [inspect the page](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_are_browser_developer_tools) using your browser and find the corresponding path in the image. In the URL's query string, the `ims=VALUExVALUE` field corresponds to the resolution loaded on the page. diff --git a/src/content/docs/en/pages/guides/edge-application/ea-mitigate-httpoxy.mdx b/src/content/docs/en/pages/guides/edge-application/ea-mitigate-httpoxy.mdx index 4908a2652d..659a256947 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-mitigate-httpoxy.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-mitigate-httpoxy.mdx @@ -8,7 +8,7 @@ namespace: documentation_how_to_configurations_mitigating permalink: /documentation/products/guides/mitigating-a-vulnerability-httpoxy/ --- -HTTPoxy is a web application vulnerability caused by malicious HTTP requests. You can configure your application to mitigate HTTPOxy using [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/). +HTTPoxy is a web application vulnerability caused by malicious HTTP requests. You can configure your application to mitigate HTTPOxy using [Rules Engine](/en/documentation/products/build/applications/rules-engine/). --- diff --git a/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx b/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx index 3ffffd4b49..e07f03e272 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates-via-api.mdx @@ -8,15 +8,15 @@ namespace: documentation_guides_lets_encrypt_via_api permalink: /documentation/products/guides/how-to-generate-a-lets-encrypt-certificate-via-api/ --- -Web applications that use the HTTPS protocol require a [Certificate Manager](/en/documentation/products/build/edge-application/digital-certificates/). When you redirect your traffic to Azion, you have the option to generate a *Let's Encrypt*™ certificate, which is a free and secure way to encrypt data for your application. Azion automates the issuance, renewal, and deactivation of this TLS certificate through an internal certificate management solution. +Web applications that use the HTTPS protocol require a [Certificate Manager](/en/documentation/products/build/applications/domains/mtls/). When you redirect your traffic to Azion, you have the option to generate a *Let's Encrypt*™ certificate, which is a free and secure way to encrypt data for your application. Azion automates the issuance, renewal, and deactivation of this TLS certificate through an internal certificate management solution. ## Let's Encrypt HTTP-01 Challenge through API -Azion now offers API-based issuance and renewal of [Let's Encrypt certificates](/en/documentation/products/secure/edge-firewall/digital-certificates/#lets-encrypt-certificate) using the HTTP-01 challenge, providing a streamlined process with no need for DNS TXT records. This offers a straightforward and convenient integration solution, particularly beneficial for customers managing numerous domains and hostnames. +Azion now offers API-based issuance and renewal of [Let's Encrypt certificates](/en/documentation/products/secure/firewall/certificate-manager/#lets-encrypt-certificate) using the HTTP-01 challenge, providing a streamlined process with no need for DNS TXT records. This offers a straightforward and convenient integration solution, particularly beneficial for customers managing numerous domains and hostnames. Certificates auto-renew before expiring, removing maintenance windows, and maintaining existing quotas, billing, and permissions. Perfect for ecommerce platforms and hosting providers, this enhancement enables faster onboarding and secures customer sites in minutes without DNS changes. -For more information on these updates, [visit the Certificate Manager documentation](/en/documentation/products/secure/edge-firewall/digital-certificates/#lets-encrypt-certificate). +For more information on these updates, [visit the Certificate Manager documentation](/en/documentation/products/secure/firewall/certificate-manager/#lets-encrypt-certificate). --- diff --git a/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates.mdx b/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates.mdx index 9c396ab9e8..973ace8efa 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-request-lets-encrypt-certificates.mdx @@ -16,7 +16,7 @@ import Code from '~/components/Code/Code.astro' -Web applications that use the HTTPS protocol require a [Certificate Manager](/en/documentation/products/build/edge-application/digital-certificates/). When you redirect your traffic to Azion, you have the option to generate a *Let's Encrypt*™ certificate, which is a free and secure way to encrypt data for your application. Azion automates the issuance, renewal, and deactivation of this TLS certificate through an internal certificate management solution. +Web applications that use the HTTPS protocol require a [Certificate Manager](/en/documentation/products/build/applications/domains/mtls/). When you redirect your traffic to Azion, you have the option to generate a *Let's Encrypt*™ certificate, which is a free and secure way to encrypt data for your application. Azion automates the issuance, renewal, and deactivation of this TLS certificate through an internal certificate management solution. @@ -102,7 +102,7 @@ Now that the challenge can take place, the next step is to bind your domain to a ## Configuring your domain -Below are steps for adding a certificate to your application. There are separate instructions for the [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. +Below are steps for adding a certificate to your application. There are separate instructions for the [legacy Domains](/en/documentation/products/build/applications/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration to API v4 guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. @@ -136,7 +136,7 @@ Once you have an application, you need to [create a Workload](/en/documentation/ To create an Azion **Domain**, you must have an application. If you haven't created an application yet, check the [build an application](/en/documentation/products/guides/build/build-an-application/) documentation. -Once you have an application, you need to [create a domain](/en/documentation/products/build/edge-application/domains/) and list the CNAMEs that you want to secure with the Let's Encrypt certificate. To do so, follow these steps: +Once you have an application, you need to [create a domain](/en/documentation/products/build/applications/domains/) and list the CNAMEs that you want to secure with the Let's Encrypt certificate. To do so, follow these steps: 1. Access [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/) > **Domains**. 2. Click the **+ Domain** button. @@ -190,7 +190,7 @@ If the **Pending** status remains for over 48 hours, you must check if the CNAME ::: :::tip -For more information on issuing Let's Encrypt certificates, visit the [Certificate Manager for Secure reference](/en/documentation/products/secure/edge-firewall/digital-certificates/#lets-encrypt-certificate). +For more information on issuing Let's Encrypt certificates, visit the [Certificate Manager for Secure reference](/en/documentation/products/secure/firewall/certificate-manager/#lets-encrypt-certificate). ::: --- @@ -208,7 +208,7 @@ To ensure that the certificate is renewed for domains hosted in external service ## Pointing your traffic to Azion -Below are steps for pointing your traffic to Azion. There are separate instructions for the [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. +Below are steps for pointing your traffic to Azion. There are separate instructions for the [legacy Domains](/en/documentation/products/build/applications/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration to API v4 guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/guides/edge-application/ea-send-ip-through-header.mdx b/src/content/docs/en/pages/guides/edge-application/ea-send-ip-through-header.mdx index 1d8921b2fe..16c7112790 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-send-ip-through-header.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-send-ip-through-header.mdx @@ -9,9 +9,9 @@ namespace: documentation_how_to_configurations_original_ip_header permalink: /documentation/products/guides/original-ip-header/ --- -When a user makes a request to an application, the `X-Forwarded-For` HTTP header stores the client IP. However, since [edge nodes](/en/documentation/products/build/edge-application/) mediate requests to an application, the header also stores other addresses in the request route in addition to the client IP address. +When a user makes a request to an application, the `X-Forwarded-For` HTTP header stores the client IP. However, since [edge nodes](/en/documentation/products/build/applications/) mediate requests to an application, the header also stores other addresses in the request route in addition to the client IP address. -To isolate the client IP, you must forward it to a new header by creating a rule using [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/) for **Applications**. +To isolate the client IP, you must forward it to a new header by creating a rule using [Rules Engine](/en/documentation/products/build/applications/rules-engine/) for **Applications**. To send the original client IP through a new request header, follow these steps: diff --git a/src/content/docs/en/pages/guides/edge-application/ea-use-advanced-cache-key.mdx b/src/content/docs/en/pages/guides/edge-application/ea-use-advanced-cache-key.mdx index 27636d8848..6825974070 100644 --- a/src/content/docs/en/pages/guides/edge-application/ea-use-advanced-cache-key.mdx +++ b/src/content/docs/en/pages/guides/edge-application/ea-use-advanced-cache-key.mdx @@ -10,7 +10,7 @@ permalink: /documentation/products/guides/advanced-cache-key/ og_image: /assets/docs/images/uploads/og_image_usecase-api-accelerate.png --- -Azion **Application Accelerator** enables access to the [Advanced Cache Key](/en/documentation/products/build/edge-application/cache-settings/#advanced-cache-key) feature, which allows you to create cache rules based on URL Query Strings and Cookies. You can apply these rules to a dynamic application using [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/). +Azion **Application Accelerator** enables access to the [Advanced Cache Key](/en/documentation/products/build/applications/cache-settings/#advanced-cache-key) feature, which allows you to create cache rules based on URL Query Strings and Cookies. You can apply these rules to a dynamic application using [Rules Engine](/en/documentation/products/build/applications/rules-engine/). To activate **Advanced Cache Key** for an application: diff --git a/src/content/docs/en/pages/guides/edge-firewall/update-edge-firewall.mdx b/src/content/docs/en/pages/guides/edge-firewall/update-edge-firewall.mdx index d7cb461d9f..d1917b6394 100644 --- a/src/content/docs/en/pages/guides/edge-firewall/update-edge-firewall.mdx +++ b/src/content/docs/en/pages/guides/edge-firewall/update-edge-firewall.mdx @@ -20,7 +20,7 @@ Rule Sets deprecated from Firewall show a banner with the following message: `Th This documentation will guide you through updating the Firewall features used in the deprecated versions to the latest ones. Each section describes how each feature works on the new modules, Network Lists, and Rules Engine. - + --- diff --git a/src/content/docs/en/pages/guides/edge-functions/altcha-challenge.mdx b/src/content/docs/en/pages/guides/edge-functions/altcha-challenge.mdx index 9064b3cd4f..ff92911a29 100644 --- a/src/content/docs/en/pages/guides/edge-functions/altcha-challenge.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/altcha-challenge.mdx @@ -49,7 +49,7 @@ The ALTCHA function creates two special endpoints in your application to manage :::note - It's possible to use the ALTCHA Function independently—only with Firewall—to protect specific areas of your application by requiring the challenge. -- To use ALTCHA through Bot Manager, [read the documentation](https://www.azion.com/en/documentation/products/secure/edge-firewall/bot-manager/#captcha). +- To use ALTCHA through Bot Manager, [read the documentation](https://www.azion.com/en/documentation/products/secure/firewall/bot-manager/#captcha). ::: ### Setting up a firewall @@ -78,7 +78,7 @@ Done. Now you have your ALTCHA Function instanced. ### Setting up the Firewall Rules Engine -To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) to configure the behavior and the criteria to run ALTCHA. To do this: +To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) to configure the behavior and the criteria to run ALTCHA. To do this: ### Independently with Firewall diff --git a/src/content/docs/en/pages/guides/edge-functions/edge-functions-api-builder.mdx b/src/content/docs/en/pages/guides/edge-functions/edge-functions-api-builder.mdx index 6f375dddf4..97b3d5bf63 100644 --- a/src/content/docs/en/pages/guides/edge-functions/edge-functions-api-builder.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/edge-functions-api-builder.mdx @@ -8,7 +8,7 @@ namespace: documentation_how_to_edge_functions_api_builder permalink: /documentation/products/guides/edge-functions/api-builder/ --- -Learn about the required process to create an API with [Functions](/en/documentation/products/build/edge-application/edge-functions/) and [ChatGPT](/en/documentation/products/edge-application/edge-functions/runtime-api/ai-integration/) and have the response shown on the [Azion Preview Deployment](/en/documentation/products/edge-application/edge-functions/runtime-api/preview-deployment/). +Learn about the required process to create an API with [Functions](/en/documentation/products/build/applications/functions/) and [ChatGPT](/en/documentation/products/applications/functions/runtime-api/ai-integration/) and have the response shown on the [Azion Preview Deployment](/en/documentation/products/applications/functions/runtime-api/preview-deployment/). To do so, you need to: @@ -167,8 +167,8 @@ At this point, your function should look like this: }) ``` -If you want, you can switch the method inside the `PreviewProvider` function and get a live preview of the responses on the [Azion Preview Deployment](/en/documentation/products/edge-application/edge-functions/runtime-api/preview-deployment/). +If you want, you can switch the method inside the `PreviewProvider` function and get a live preview of the responses on the [Azion Preview Deployment](/en/documentation/products/applications/functions/runtime-api/preview-deployment/). 13. Click the **Save** button. -Now, the function is ready to be instantiated in an application. Check how to [instantiate and execute the functions in your application](/en/documentation/products/build/edge-application/edge-functions-instances/) and try it out. +Now, the function is ready to be instantiated in an application. Check how to [instantiate and execute the functions in your application](/en/documentation/products/build/applications/functions-instances/) and try it out. diff --git a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/browserless-edge-functions.mdx b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/browserless-edge-functions.mdx index d4f91b5623..2458f85fba 100644 --- a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/browserless-edge-functions.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/browserless-edge-functions.mdx @@ -169,5 +169,5 @@ The browserless Function typically includes: --- - + diff --git a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx index a3879b6727..fa5615a821 100644 --- a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx @@ -239,5 +239,5 @@ function authenticateUser(request) { --- - - + + diff --git a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx index 2a86f588cf..4e144bd840 100644 --- a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx @@ -262,4 +262,4 @@ Add tracking capabilities to monitor email engagement: --- - + diff --git a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx index e96f641c8c..7c45efef5f 100644 --- a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx @@ -351,5 +351,5 @@ The RESTful API Function includes: --- - - + + diff --git a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx index 85caed337e..8f72e53ec9 100644 --- a/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx @@ -303,4 +303,4 @@ function logWebhookEvent(event, status, processingTime) { --- - + diff --git a/src/content/docs/en/pages/guides/edge-functions/functions-first-steps.mdx b/src/content/docs/en/pages/guides/edge-functions/functions-first-steps.mdx index 6141664ff4..59f0f38036 100644 --- a/src/content/docs/en/pages/guides/edge-functions/functions-first-steps.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/functions-first-steps.mdx @@ -23,7 +23,7 @@ It's paramount to take a look at the list of available APIs, methods, and types. ## Code Editor -The [Functions Code Editor](/en/documentation/products/edge-application/edge-functions/runtime-api/code-editor/) provides a development experience similar to what developers are accustomed to. The [Functions ChatGPT Integration](/en/documentation/products/edge-application/edge-functions/runtime-api/ai-integration/) helps you to write, refactor, and review code. +The [Functions Code Editor](/en/documentation/products/applications/functions/runtime-api/code-editor/) provides a development experience similar to what developers are accustomed to. The [Functions ChatGPT Integration](/en/documentation/products/applications/functions/runtime-api/ai-integration/) helps you to write, refactor, and review code. --- @@ -38,7 +38,7 @@ Developing your first function for Applications: **Writing a function** -First, the functions for applications work based on a [fetch event](/en/documentation/products/edge-application/edge-functions/runtime-apis/javascript/fetch/). It's initialized with an `addEventListener` function, passing `fetch` as the event type, and an event. For example: +First, the functions for applications work based on a [fetch event](/en/documentation/products/applications/functions/runtime-apis/javascript/fetch/). It's initialized with an `addEventListener` function, passing `fetch` as the event type, and an event. For example: ```javascript addEventListener('fetch', event => { @@ -78,7 +78,7 @@ In this example, the response will be the HTML content, declared previously by t After writing your functions, you can preview the response and inspect the code. The preview simulates a request, and this simulation can be altered to meet the developer's needs. -Learn more about [Azion Preview Deployment](/en/documentation/products/edge-application/edge-functions/runtime-api/preview-deployment/). +Learn more about [Azion Preview Deployment](/en/documentation/products/applications/functions/runtime-api/preview-deployment/). It's possible to debug the functions through: @@ -91,4 +91,4 @@ It's possible to debug the functions through: Once you've saved your function, it's necessary to instantiate it in an applications. -[Learn more on how to instantiate a function on Applications](/en/documentation/products/build/edge-application/edge-functions-instances/). +[Learn more on how to instantiate a function on Applications](/en/documentation/products/build/applications/functions-instances/). diff --git a/src/content/docs/en/pages/guides/edge-functions/serverless-functions.mdx b/src/content/docs/en/pages/guides/edge-functions/serverless-functions.mdx index 7d0108e34a..c5d69c5598 100644 --- a/src/content/docs/en/pages/guides/edge-functions/serverless-functions.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/serverless-functions.mdx @@ -10,15 +10,15 @@ permalink: /documentation/products/guides/serverless-functions/ --- import LinkButton from 'azion-webkit/linkbutton' -[Functions](/en/documentation/products/build/edge-application/edge-functions/) is a module of the Azion Web Platform that allows you to program and execute serverless functions. +[Functions](/en/documentation/products/build/applications/functions/) is a module of the Azion Web Platform that allows you to program and execute serverless functions. - + To run a function, you must: - Create your own function or use any of those already available on [Azion Marketplace](https://console.azion.com/marketplace). - Instantiate a function in an application. -- Define activation triggers within [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/). +- Define activation triggers within [Rules Engine](/en/documentation/products/build/applications/rules-engine/). --- diff --git a/src/content/docs/en/pages/guides/edge-functions/webassembly.mdx b/src/content/docs/en/pages/guides/edge-functions/webassembly.mdx index 4cec2a3fd1..8f884b8c2b 100644 --- a/src/content/docs/en/pages/guides/edge-functions/webassembly.mdx +++ b/src/content/docs/en/pages/guides/edge-functions/webassembly.mdx @@ -10,7 +10,7 @@ og_image: >- “/assets/docs/images/uploads/use-case_-creating-a-function-using-webassembly.png” --- -Learn about the required process to create a [function](/en/documentation/products/build/edge-application/edge-functions/) that uses a [WebAssembly](https://webassembly.org/getting-started/developers-guide/) originated function. +Learn about the required process to create a [function](/en/documentation/products/build/applications/functions/) that uses a [WebAssembly](https://webassembly.org/getting-started/developers-guide/) originated function. 1. Access [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/) > **Functions**. 2. Click **+Function**. @@ -67,7 +67,7 @@ The const `wasmCode` is the binary representation of the following [WAT](https:/ 6. Click the **Save** button. -Now, the function is ready to be instantiated in an application. Check how to [instantiate and execute the functions in your application](/en/documentation/products/build/edge-application/edge-functions-instances/) and try it out. +Now, the function is ready to be instantiated in an application. Check how to [instantiate and execute the functions in your application](/en/documentation/products/build/applications/functions-instances/) and try it out. The expected output of the recently created function is similar to: diff --git a/src/content/docs/en/pages/guides/edge-sql/create-database.mdx b/src/content/docs/en/pages/guides/edge-sql/create-database.mdx index 43a1ab1410..63a575981d 100644 --- a/src/content/docs/en/pages/guides/edge-sql/create-database.mdx +++ b/src/content/docs/en/pages/guides/edge-sql/create-database.mdx @@ -17,9 +17,9 @@ import Tag from 'primevue/tag' **SQL Database** allows you to create and manage relational databases. This guide covers how to create, list, and delete a database using the [Azion API](https://api.azion.com). - + -After creating a database, read [How to create an SQL Database query](/en/documentation/products/guides/create-tables-edge-sql/) to populate your database. +After creating a database, read [How to create an SQL Database query](/en/documentation/products/guides/create-tables-sql-database/) to populate your database. --- diff --git a/src/content/docs/en/pages/guides/edge-sql/create-query.mdx b/src/content/docs/en/pages/guides/edge-sql/create-query.mdx index ccabdc2e79..e8ac309255 100644 --- a/src/content/docs/en/pages/guides/edge-sql/create-query.mdx +++ b/src/content/docs/en/pages/guides/edge-sql/create-query.mdx @@ -15,9 +15,9 @@ import Tag from 'primevue/tag' Preview -Once you've created your [SQL Database database](/en/documentation/products/guides/manage-databases-edge-sql/), you can begin creating tables and inserting data into them. +Once you've created your [SQL Database database](/en/documentation/products/guides/manage-sql-database/), you can begin creating tables and inserting data into them. - + --- diff --git a/src/content/docs/en/pages/guides/edge-sql/retrieve-data/index.mdx b/src/content/docs/en/pages/guides/edge-sql/retrieve-data/index.mdx index 0b47e3ea9f..ce4916c73b 100644 --- a/src/content/docs/en/pages/guides/edge-sql/retrieve-data/index.mdx +++ b/src/content/docs/en/pages/guides/edge-sql/retrieve-data/index.mdx @@ -11,13 +11,13 @@ import LinkButton from 'azion-webkit/linkbutton' See how to retrieve data from an existing database (DB) with SQL Database and Functions. - + --- ## Requirements -- [Azion Functions enabled](/en/documentation/products/build/edge-application/edge-functions/). +- [Azion Functions enabled](/en/documentation/products/build/applications/functions/). - An active [Azion Personal Token](/en/documentation/products/guides/personal-tokens/). --- @@ -137,7 +137,7 @@ Since this example is for retrieving data, the method was set to be only GET. Yo This function was created to communicate with SQL Database. Now, it's necessary to instantiate this function in a running application: - + Learn how to retrieve data effortlessly with Functions. Watch the video below: diff --git a/src/content/docs/en/pages/guides/edge-sql/vector-search-guide.mdx b/src/content/docs/en/pages/guides/edge-sql/vector-search-guide.mdx index 94e37042da..d8f50827e7 100644 --- a/src/content/docs/en/pages/guides/edge-sql/vector-search-guide.mdx +++ b/src/content/docs/en/pages/guides/edge-sql/vector-search-guide.mdx @@ -11,7 +11,7 @@ import LinkButton from 'azion-webkit/linkbutton' **Vector Search** is an Azion SQL Database feature that enables customers to implement semantic search engines. While traditional search models aim to find exact matches, such as keyword matches, vector search models use specialized algorithms to identify similar items based on their mathematical representations, or vector embeddings. - + As an example for implementation, this guide will cover setting up the vector search logic in a TypeScript application, with a database using the Langchain library with OpenAI and the Azion SQL API. @@ -24,7 +24,7 @@ As an example for implementation, this guide will cover setting up the vector se - Install [Azion CLI](/en/documentation/products/azion-cli/overview/). - Create a typescript application. - As in the example, you can use the [Azion CLI](/en/documentation/devtools/cli/init/) to create a Simple Typescript Router application. -- Set up [SQL Database](/en/documentation/products/store/edge-sql/). +- Set up [SQL Database](/en/documentation/products/store/sql-database/). - Install the [Azion Libraries](https://github.com/aziontech/lib). --- diff --git a/src/content/docs/en/pages/guides/edge-storage/create-object-storage/index.mdx b/src/content/docs/en/pages/guides/edge-storage/create-object-storage/index.mdx index 684516b57f..acb7545ad5 100644 --- a/src/content/docs/en/pages/guides/edge-storage/create-object-storage/index.mdx +++ b/src/content/docs/en/pages/guides/edge-storage/create-object-storage/index.mdx @@ -12,7 +12,7 @@ import LinkButton from 'azion-webkit/linkbutton' Azion **Object Storage** allows you to create buckets and integrate your object storage with your edge infrastructure. This guide covers how to create, modify, and delete a bucket using the [Azion API](https://api.azion.com). - + Read [How to upload and download objects from an Object Storage bucket](/en/documentation/products/guides/upload-and-download-objects-from-bucket/) to learn about object operations. @@ -76,7 +76,7 @@ You should receive the following response: ``` :::caution[Warning] -When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for an application, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through an function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/edge-storage/#authentication-and-permissions). +When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for an application, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through an function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/object-storage/#authentication-and-permissions). ::: --- diff --git a/src/content/docs/en/pages/guides/getting-to-know-azion-console/getting-to-know-azion-console.mdx b/src/content/docs/en/pages/guides/getting-to-know-azion-console/getting-to-know-azion-console.mdx index aefc7d6395..9a8dcb365f 100644 --- a/src/content/docs/en/pages/guides/getting-to-know-azion-console/getting-to-know-azion-console.mdx +++ b/src/content/docs/en/pages/guides/getting-to-know-azion-console/getting-to-know-azion-console.mdx @@ -15,7 +15,7 @@ permalink: /documentation/products/guides/getting-to-know-azion-console/ Through Azion Console, you can: - Access and configure your [Azion account](/en/documentation/products/accounts/creating-account/). -- [Build and deploy applications](/en/documentation/products/build/edge-application/). +- [Build and deploy applications](/en/documentation/products/build/applications/). - [Manage your applications](/en/documentation/products/guides/build/configure-main-settings/). - Access and configure [all Azion products and capabilities](/en/documentation/). @@ -44,7 +44,7 @@ Documentation related to Console's screens in the **Help Center** isn't availabl 6. The **Get Started** section includes the button **+ Create** to start using the Azion Web Platform. By clicking this button, you can go through the initial steps to build an applications [starting with the Azion template](/en/documentation/products/use-a-template-via-azion-console/) that best suits your needs or create other resources such as domains, variables, **functions**, edge services, **certificate manager**, and more. 7. Next to this section, there are two blocks: -- **Manage Applications**: use this block to go to the [Applications](/en/documentation/products/build/edge-application/) page. There, you'll be able to manage and add applications' main settings, modules, and features. +- **Manage Applications**: use this block to go to the [Applications](/en/documentation/products/build/applications/) page. There, you'll be able to manage and add applications' main settings, modules, and features. - **View Analytics**: this link will take you to [Real-Time Metrics](/en/documentation/products/observe/real-time-metrics/). You'll find insights based on your applications' performance, availability, and security there. 8. Below, you'll find the shortcut to **Invite Your Team**. This is an optional step, but you can invite other people to Console to work together with you. Find out more on [Teams Permissions](/en/documentation/products/accounts/teams-permissions/). diff --git a/src/content/docs/en/pages/guides/import-from-github/import-from-github.mdx b/src/content/docs/en/pages/guides/import-from-github/import-from-github.mdx index 194cdbb9d1..b5b6cdf7ce 100644 --- a/src/content/docs/en/pages/guides/import-from-github/import-from-github.mdx +++ b/src/content/docs/en/pages/guides/import-from-github/import-from-github.mdx @@ -80,7 +80,7 @@ The link to the application allows you to see it on the browser. However, it tak All application settings can be customized any time you need through Azion Console. To do so, click the **Manage** button that appears during the deployment or go to the **Application** page and select the application you want to update. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) for more details. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) for more details. ::: As your Azion account is connected to the GitHub repository, any changes will be replicated in both, keeping your project up-to-date in a continuous deployment workflow. diff --git a/src/content/docs/en/pages/guides/index.mdx b/src/content/docs/en/pages/guides/index.mdx index 5aa2f6b462..8d8b360e65 100644 --- a/src/content/docs/en/pages/guides/index.mdx +++ b/src/content/docs/en/pages/guides/index.mdx @@ -15,21 +15,21 @@ permalink: /documentation/products/guides/ - [How to configure mTLS on your Applications domains](/en/documentation/products/guides/mtls/) - [Customizing an error response page](/en/documentation/products/guides/customizing-error-response-page/) - [How to send the client IP address through a dedicated HTTP header](/en/documentation/products/guides/original-ip-header/) -- [HTTP2](/en/documentation/products/build/edge-application/main-settings/) +- [HTTP2](/en/documentation/products/build/applications/main-settings/) - [How to check your WAF mode](/en/documentation/products/guides/how-to-check-your-waf-mode/) - [How to find the score of WAF blocked requests](/en/documentation/products/guides/how-to-find-waf-score/) - [How to mitigate the HTTPOxy vulnerability](/en/documentation/products/guides/mitigating-a-vulnerability-httpoxy/) -- [How to update Firewall](/en/documentation/products/guides/how-to-update-your-edge-firewall/) +- [How to update Firewall](/en/documentation/products/guides/how-to-update-your-firewall/) - [Setting up Cross-Origin Resource Sharing (CORS)](/en/documentation/products/guides/cross-origin-resource-sharing-cors/) - [How to enable gzip compression for Applications](/en/documentation/products/guides/gzip-compression/) - [How to create rules using Rules Engine for Applications](/en/documentation/products/guides/rules-engine/) - [How to create IP, ASN, and geolocation blocklists with Network Lists](/en/documentation/products/guides/blocklists-ip-addresses-edge/) -- [How to stage an application through the hosts file](/en/documentation/products/guides/stage-edge-application-through-hosts-file/) +- [How to stage an application through the hosts file](/en/documentation/products/guides/stage-applications-through-hosts-file/) - [How to create and modify an Object Storage bucket](/en/documentation/products/guides/create-and-modify-bucket/) - [How to upload and download objects from an Object Storage bucket](/en/documentation/products/guides/upload-and-download-objects-from-bucket/) - [How to use an Object Storage bucket as the origin of a static application](/en/documentation/products/store/storage/use-bucket-as-origin/) - [How to configure HTTP and HTTPS ports for origins and delivery address](/en/documentation/products/guides/configure-ports/) -- [How to access Object Storage using the S3 protocol](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/) +- [How to access Object Storage using the S3 protocol](/en/documentation/products/store/storage/s3-protocol-for-object-storage/) - [How to enforce HLS cache for live streaming delivery](/en/documentation/products/guides/enforce-hls-cache/) - [How to configure a WAF Custom Allowed Rule](/en/documentation/products/guides/secure/configure-waf-allowed-rules/) - [How to configure WAF rules to allow requests with a specific cookie](/en/documentation/products/guides/secure/waf-rules-for-specific-cookie/) @@ -41,11 +41,11 @@ permalink: /documentation/products/guides/ ## Functions Demonstrations -- [How to build a browserless application with Functions](/en/documentation/products/guides/build/browserless-edge-functions/) -- [How to implement file upload functionality with Functions](/en/documentation/products/guides/build/file-upload-edge-functions/) -- [How to integrate Resend email service with Functions](/en/documentation/products/guides/build/resend-email-edge-functions/) -- [How to build a RESTful API with Functions and SQL Database](/en/documentation/products/guides/build/restful-tasks-api-edge-functions/) -- [How to handle Stripe webhooks with Functions](/en/documentation/products/guides/build/stripe-webhooks-edge-functions/) +- [How to build a browserless application with Functions](/en/documentation/products/guides/build/browserless-functions/) +- [How to implement file upload functionality with Functions](/en/documentation/products/guides/build/file-upload-functions/) +- [How to integrate Resend email service with Functions](/en/documentation/products/guides/build/resend-email-functions/) +- [How to build a RESTful API with Functions and SQL Database](/en/documentation/products/guides/build/restful-tasks-api-functions/) +- [How to handle Stripe webhooks with Functions](/en/documentation/products/guides/build/stripe-webhooks-functions/) --- @@ -70,8 +70,8 @@ permalink: /documentation/products/guides/ ## Applications -- [How to clone an application](/en/documentation/products/guides/clone-edge-application/) -- [How to delete an application](/en/documentation/products/guides/delete-edge-application/) +- [How to clone an application](/en/documentation/products/guides/clone-applications/) +- [How to delete an application](/en/documentation/products/guides/delete-applications/) - [How to import an existing project from GitHub and deploy it](/en/documentation/products/guides/import-an-existing-project-from-github/) - [How to manage the Azion GitHub App](/en/documentation/products/guides/azion-github-app/) - [How to use the "+ Create" button](/en/documentation/products/guides/create-button/) @@ -123,9 +123,9 @@ permalink: /documentation/products/guides/ - [How to deploy the Docusaurus TypeScript Boilerplate](/en/documentation/products/guides/docusaurus-typescript-boilerplate/) - [How to deploy the Docusaurus with Material UI template](/en/documentation/products/guides/docusaurus-material-ui-template/) - [How to deploy the Dynamic and Static File Optimization template](/en/documentation/products/guides/dynamic-and-static-file-optimization-template/) -- [How to deploy the AI Inference Starter Kit template](/en/documentation/products/guides/edge-ai-starter-kit/) +- [How to deploy the AI Inference Starter Kit template](/en/documentation/products/guides/ai-inference-starter-kit/) - [How to deploy the Application Proxy template](/en/documentation/products/guides/edge-application-proxy-template/) -- [How to deploy the Function Starter Kit template](/en/documentation/products/guides/edge-function-starter-kit/) +- [How to deploy the Function Starter Kit template](/en/documentation/products/guides/function-starter-kit/) - [How to deploy the SQL Database Starter Kit template](/en/documentation/products/guides/sqldatabase-starter-kit/) - [How to deploy the Gatsby E-commerce Theme template](/en/documentation/products/guides/gatsby-ecommerce-theme/) - [How to deploy the Hello World template](/en/documentation/products/guides/hello-world-template/) @@ -152,8 +152,8 @@ permalink: /documentation/products/guides/ - [How to integrate a Turso database with Azion using a template](/en/documentation/products/guides/turso-starter-kit/) - [How to migrate a WordPress website to the edge with WordPress EdgeAccelerator](/en/documentation/products/guides/wordpress-edgeaccelerator/) - [How to test Bot Manager Lite using a template](/en/documentation/products/guides/bot-manager-lite-starter-kit/) -- [How to use the Function GitHub AutoDeploy template](/en/documentation/products/guides/edge-function-github-autodeploy/) -- [How to use the QStash Function Scheduler template](/en/documentation/products/guides/qstash-edge-function-scheduler/) +- [How to use the Function GitHub AutoDeploy template](/en/documentation/products/guides/function-github-autodeploy/) +- [How to use the QStash Function Scheduler template](/en/documentation/products/guides/qstash-function-scheduler/) - [How to use the Upstash GeoLocation Deploy template](/en/documentation/products/guides/upstash-geolocation-edgedeploy/) --- @@ -174,11 +174,11 @@ permalink: /documentation/products/guides/ ## Use Cases -- [Azion Firewall: multi-layered security in Edge](/en/documentation/products/guides/edge-firewall/) +- [Azion Firewall: multi-layered security in Edge](/en/documentation/products/guides/firewall/) - [Creating Blacklists of IP Addresses in Edge, using Azion Network Shield](/en/documentation/products/guides/blocklists-ip-addresses-edge/) - [Creating a Function using WebAssembly on Azion's platform](/en/documentation/products/guides/webassembly-on-azion-platform/) - [Hosting a site](/en/documentation/products/guides/hosting-edge-website/) -- [Paywall with Function JWT](/en/documentation/products/guides/paywall-edge-function-jwt/) +- [Paywall with Function JWT](/en/documentation/products/guides/paywall-function-jwt/) - [Protect restricted content from improper access with Azion Secure Token](/en/documentation/products/guides/secure-token/) - [How to run serverless functions on Azion Console](/en/documentation/products/guides/serverless-functions/) - [How to customize the Azion Console interface using the Console Kit](/en/documentation/products/guides/customize-interface-console-kit/) @@ -188,7 +188,7 @@ permalink: /documentation/products/guides/ ## Store -- [How to implement SQL Database Vector Search](/en/documentation/products/guides/edge-sql-vector-search/) +- [How to implement SQL Database Vector Search](/en/documentation/products/guides/sql-database-vector-search/) --- @@ -206,7 +206,7 @@ permalink: /documentation/products/guides/ - [How to use an HTTP/HTTPS POST connector to receive data from Data Stream](/en/documentation/products/guides/observe/connector-standard-https-post/) - [How to use Amazon Kinesis Data Firehose to receive data from Data Stream](/en/documentation/products/guides/endpoint-amazon-kinesis/) - [How to use Amazon S3 to receive data from Data Stream](/en/documentation/products/guides/endpoint-amazon-s3/) -- [How to use Azion Object Storage to receive data from Data Stream](/en/documentation/products/guides/connector-azion-edge-storage/) +- [How to use Azion Object Storage to receive data from Data Stream](/en/documentation/products/guides/connector-azion-object-storage/) - [How to use Azure Blob Storage to receive data from Data Stream](/en/documentation/products/guides/endpoint-azure-blob/) - [How to use Azure Monitor to receive data from Data Stream](/en/documentation/products/guides/endpoint-azure-monitor/) - [How to use Datadog to receive data from Data Stream](/en/documentation/products/guides/endpoint-datadog/) @@ -230,9 +230,9 @@ permalink: /documentation/products/guides/ - [How to identify the Top IPs generating attack traffic using GraphQL API](/en/documentation/products/guides/query-top-ips-attack-traffic-with-graphql/) - [How to identify the top attacks using GraphQL API](/en/documentation/products/guides/query-top-attacks-with-graphql/) - [How to query data from the httpBreakdownMetrics dataset](/en/documentation/products/guides/query-httpbreakdownmetrics-data-with-graphql/) -- [How to query usage data from Functions](/en/documentation/products/guides/query-edge-functions-usage-data-with-graphql/) +- [How to query usage data from Functions](/en/documentation/products/guides/query-functions-usage-data-with-graphql/) - [How to query usage data from Image Processor](/en/documentation/products/guides/query-image-processor-usage-data-with-graphql/) -- [How to query usage data from Applications](/en/documentation/products/guides/query-edge-application-usage-data-with-graphql/) +- [How to query usage data from Applications](/en/documentation/products/guides/query-applications-usage-data-with-graphql/) - [How to query usage data from Data Stream](/en/documentation/products/guides/query-data-stream-usage-data-with-graphql/) - [How to query usage data from Tiered Cache](/en/documentation/products/guides/query-tiered-cache-usage-data-with-graphql/) diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx index 9f79c32b5d..a024fb09fa 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/jwt.mdx @@ -74,7 +74,7 @@ Done. Now you have your JWT instanced. ### Setting up the Firewall Rules Engine -To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) to configure the behavior and the criteria to run the JWT. +To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) to configure the behavior and the criteria to run the JWT. To do so, still on the **Firewall** page, follow these steps: @@ -97,7 +97,7 @@ On the Console, you must now configure your domain so your firewall protects it. Done. Now you have a JWT integration running for every request made to the domain you indicate. :::tip -You can see a use case by visiting the [Setting up a paywall with Function JWT](/en/documentation/products/guides/paywall-edge-function-jwt/) page. +You can see a use case by visiting the [Setting up a paywall with Function JWT](/en/documentation/products/guides/paywall-function-jwt/) page. ::: --- \ No newline at end of file diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx index c7eefa1b04..ca087507dd 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/limit-payload.mdx @@ -79,7 +79,7 @@ Some information about how this integration works: ### Setting up the Firewall Rules Engine -To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the function. +To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the function. Still on the **Firewall** page: diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx index d0d26341f2..5fe7e00330 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/request-data-into-header.mdx @@ -82,7 +82,7 @@ This integration can trigger errors. In this case, the errors will be appended t ## Setting up the Firewall Rules Engine -To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the integration. +To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the integration. Still in the **Firewall** page: diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx index 223b2780e9..0f82175e69 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/scheduled-blocking.mdx @@ -134,7 +134,7 @@ For `static_response` parameter in `action`, you can define the status code that ## Setting up the Rules Engine -Finally, you must set up the [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the function. +Finally, you must set up the [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the function. Still in the **Firewall** page. diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx index 4cc91694a5..b1a5997e14 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/secure-token.mdx @@ -106,7 +106,7 @@ Where the `secure_token_secret` will be the secret string you've passed on the c ### Setting up the Rules Engine -To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the function. +To finish, you have to set up the [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) to configure the *behavior* and the *criteria* to run the function. Still in the **Firewall** page: diff --git a/src/content/docs/en/pages/guides/marketplace/integrations/videoteca-player.mdx b/src/content/docs/en/pages/guides/marketplace/integrations/videoteca-player.mdx index 010cf977fa..e0b45b0871 100644 --- a/src/content/docs/en/pages/guides/marketplace/integrations/videoteca-player.mdx +++ b/src/content/docs/en/pages/guides/marketplace/integrations/videoteca-player.mdx @@ -42,7 +42,7 @@ You can search any integration by browsing through the cards, using the filters, To create an instance of the integration's function: 1. On the **Products menu**, navigate to **Build** > **Application**. -2. Select the application from the list to which you want to add the integration or [create a new application](/en/documentation/products/build/edge-application/first-steps/). +2. Select the application from the list to which you want to add the integration or [create a new application](/en/documentation/products/build/applications/first-steps/). 3. Select the **Functions Instances** tab. 4. Click the **+ Function Instance** button. 5. Give a name to your instance. diff --git a/src/content/docs/en/pages/guides/marketplace/templates/astro-blog-template.mdx b/src/content/docs/en/pages/guides/marketplace/templates/astro-blog-template.mdx index 02daded4a2..81803be57f 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/astro-blog-template.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/astro-blog-template.mdx @@ -26,7 +26,7 @@ This template uses Astro version `4.2.6`. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Image processor](/en/documentation/products/build/edge-application/image-processor/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Image processor](/en/documentation/products/build/applications/image-processor/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/astro-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/astro-boilerplate.mdx index 37f2c70b39..9933cae532 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/astro-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/astro-boilerplate.mdx @@ -25,7 +25,7 @@ This template uses Astro version `4.5.12`. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx b/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx index 0e04e05e76..7c6fc85d47 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx @@ -32,7 +32,7 @@ To use this template, you must: - Go to [Azion Marketplace](https://console.azion.com/marketplace) to install this integration by clicking the **Install** button. Check the [How to install Azion Bot Manager Lite](/en/documentation/products/guides/bot-manager-lite/) guide for more details. - If you didn't launch the Bot Manager Lite function before trying to use this template, the execution will fail and a log explaining the reason will be printed. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), [Image processor](/en/documentation/products/build/edge-application/image-processor/), and [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), [Image processor](/en/documentation/products/build/applications/image-processor/), and [Network Shield](/en/documentation/products/secure/firewall/network-shield/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. ## Deploying the template @@ -57,7 +57,7 @@ Fields identified with an asterisk are mandatory. - **Origin Address** *: the address of the hosted origin the application should fetch the content from. - Example: `www.yourwebsite.com` - **Custom Host Header**: in some cases, it may be necessary to add host information in the header request to retrieve information from the origin. This variable is used for that purpose. - - Example: `${host}`. Read more about the host header and how to customize it on the [Origins](/en/documentation/products/build/edge-application/origins/#host-header) documentation. + - Example: `${host}`. Read more about the host header and how to customize it on the [Origins](/en/documentation/products/build/applications/origins/#host-header) documentation. After completing all the information, click the **Deploy** button, located in the bottom-right corner. This will start the deployment process. @@ -75,7 +75,7 @@ The application includes the following rules and settings: - A default rule composed of: - **Criteria**: if `${uri}` starts with `/`. - - **Behavior**: then [Set Origin](/en/documentation/products/build/edge-application/rules-engine/#set-origin) as `Default Origin`. + - **Behavior**: then [Set Origin](/en/documentation/products/build/applications/rules-engine/#set-origin) as `Default Origin`. - For image optimization and caching, the file extensions that can be enhanced with these configurations are `.jpg`, `.jpeg`, `.bmp`, `.ico`, `.gif`, `.png`. - For static content, the template supports the common static file extensions. - The template: diff --git a/src/content/docs/en/pages/guides/marketplace/templates/bot-starter-kit.mdx b/src/content/docs/en/pages/guides/marketplace/templates/bot-starter-kit.mdx index ab0bf65406..b201a7f1d3 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/bot-starter-kit.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/bot-starter-kit.mdx @@ -17,7 +17,7 @@ The **Bot Manager Lite Starter Kit** template deploys an entirely new edge stack The deployment automatically creates an application, an function, an Firewall, and a domain to access and test the features of Bot Manager Lite. This template is ideal to understand how this integration works and how it can help you secure your applications and digital assets. :::note -Bot Manager Lite integration is a [lite version](/pt-br/documentacao/produtos/guias/bot-manager-lite/) available in the Marketplace. +Bot Manager Lite integration is a [lite version](/en/documentation/products/guides/bot-manager-lite/) available in the Marketplace. Azion provides the Bot Manager add-on, a comprehensive solution for bot management. Contact the [Sales team](https://www.azion.com/pt-br/contate-vendas/) for more details on the Bot Manager subscription. ::: @@ -110,7 +110,7 @@ The Bot Manager Lite function instance is set to always write logs. This way, wh ## Managing the template -Being a testing template, the initial configuration is mostly demonstrative. However, you can use it as a base for creating an actual functional application. You can [configure a new origin](/en/documentation/products/build/edge-application/origins/) for the application and use it as *Default Origin*. You can also modify the JSON Args of your **Bot Manager Lite** instance for a more customized configuration. +Being a testing template, the initial configuration is mostly demonstrative. However, you can use it as a base for creating an actual functional application. You can [configure a new origin](/en/documentation/products/build/applications/origins/) for the application and use it as *Default Origin*. You can also modify the JSON Args of your **Bot Manager Lite** instance for a more customized configuration. To manage and edit your application's settings, proceed as follows: diff --git a/src/content/docs/en/pages/guides/marketplace/templates/bot-with-firewall.mdx b/src/content/docs/en/pages/guides/marketplace/templates/bot-with-firewall.mdx index c8db975807..a662e8d7af 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/bot-with-firewall.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/bot-with-firewall.mdx @@ -17,7 +17,7 @@ Preview The **Bot Manager Lite Integration Kit** template provides an easy way to integrate the Bot Manager Lite function in an existent Firewall on Azion. This template automatically creates a new function instance for Bot Manager Lite and a Rules Engine rule to run it in the selected Firewall. :::note -Bot Manager Lite integration is a [lite version](/pt-br/documentacao/produtos/guias/bot-manager-lite/) available in the Marketplace. +Bot Manager Lite integration is a [lite version](/en/documentation/products/guides/bot-manager-lite/) available in the Marketplace. Azion provides the Bot Manager add-on, a comprehensive solution for bot management. Contact the [Sales team](https://www.azion.com/pt-br/contate-vendas/) for more details on the Bot Manager subscription. ::: @@ -28,7 +28,7 @@ Azion provides the Bot Manager add-on, a comprehensive solution for bot manageme Before deploying this template, you must: -- Have an [Firewall](/en/documentation/products/secure/edge-firewall/) created in your account. +- Have an [Firewall](/en/documentation/products/secure/firewall/) created in your account. - During the setup of the template, you must inform the ID of your existing Firewall to add the Bot Manager Lite instance. If the ID doesn't exist, the execution will fail. Check [how to configure and edit an Firewall](/en/documentation/products/secure/secure-application/#step-1-configure-main-settings). - Launch the latest version of the **Bot Manager Lite** integration. - Go to [Azion Marketplace](https://console.azion.com/marketplace) to install this integration by clicking the **Install* button. Check the [How to install Azion Bot Manager Lite](/en/documentation/products/guides/bot-manager-lite/) guide for more details. @@ -121,7 +121,7 @@ All settings can be customized at any time you need through Azion Console. To ma After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/bot-with-tor.mdx b/src/content/docs/en/pages/guides/marketplace/templates/bot-with-tor.mdx index e2470d3be9..58e23c036c 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/bot-with-tor.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/bot-with-tor.mdx @@ -19,7 +19,7 @@ The **Bot Manager Lite and TOR Block Starter Kit** template enables you to deplo This template automatically creates a new Firewall that includes the rules to execute an function instance, confirm if your domains are valid, and deny requests from the pre-built "Azion IP Tor Exit Nodes" network list. All of this, working in conjunction with the **Functions** and **Network Shield** modules and **Bot Manager Lite**. :::note -Bot Manager Lite integration is a [lite version](/pt-br/documentacao/produtos/guias/bot-manager-lite/) available in the Marketplace. +Bot Manager Lite integration is a [lite version](/en/documentation/products/guides/bot-manager-lite/) available in the Marketplace. Azion provides the Bot Manager add-on, a comprehensive solution for bot management. Contact the [Sales team](https://www.azion.com/pt-br/contate-vendas/) for more details on the Bot Manager subscription. ::: @@ -34,7 +34,7 @@ Before deploying this template, you must: - Go to [Azion Marketplace](https://console.azion.com/marketplace) to install this integration by clicking the **Install* button. Check the [How to install Azion Bot Manager Lite](/en/documentation/products/guides/bot-manager-lite/) guide for more details. - If you didn't install the Bot Manager Lite function before deploying this template, the execution will fail and a log explaining the reason will be printed. -- This template uses [Functions](/en/documentation/products/build/applications/functions/) and [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Functions](/en/documentation/products/build/applications/functions/) and [Network Shield](/en/documentation/products/secure/firewall/network-shield/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- @@ -117,7 +117,7 @@ All settings can be customized at any time you need through Azion Console. To ma After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx b/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx index 849fc84e1e..48d0073128 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx @@ -22,7 +22,7 @@ By deploying this template, the platform creates a new application including all ## Requirements -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) and [Image processor](/en/documentation/products/build/edge-application/image-processor/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) and [Image processor](/en/documentation/products/build/applications/image-processor/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- @@ -50,7 +50,7 @@ Fields identified with an asterisk are mandatory. - **Origin Address** *: the address of the hosted origin the application should fetch the original content from. - Example: `www.yourwebsite.com` - **Custom Host Header**: in some cases, it may be necessary to override the value of the `Host` header request in the request to retrieve information from the origin. Set a value for the `Host` header in this field. - - Use the `${host}` variable to retrieve the Host value from the request URI. Read more about the Host Header and how to customize it on the [Origins documentation](/en/documentation/products/build/edge-application/origins/#host-header). + - Use the `${host}` variable to retrieve the Host value from the request URI. Read more about the Host Header and how to customize it on the [Origins documentation](/en/documentation/products/build/applications/origins/#host-header). After completing all the information, click the **Deploy* button, located in the bottom-right corner. This will start the deployment process. @@ -69,7 +69,7 @@ Now you can [manage and adjust the settings](#managing-the-template) through Azi The deployed application includes the following rules and settings: - **Criteria**: if `${uri}` *starts with* `/`. -- **Behavior**: then [Set Origin](/en/documentation/products/build/edge-application/rules-engine/#set-origin) as `Default Origin`. +- **Behavior**: then [Set Origin](/en/documentation/products/build/applications/rules-engine/#set-origin) as `Default Origin`. - For image optimization and caching, the file extensions that can be enhanced with these configurations are `.jpg`, `.jpeg`, `.bmp`, `.ico`, `.gif`, `.png`. - For static content, the template supports the common static file extensions. - Additionally, the template: @@ -92,7 +92,7 @@ To manage and edit your application's settings, proceed as follows: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/edge-ai-starter-kit.mdx b/src/content/docs/en/pages/guides/marketplace/templates/edge-ai-starter-kit.mdx index 2c89d7b3f2..ac2272d826 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/edge-ai-starter-kit.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/edge-ai-starter-kit.mdx @@ -96,7 +96,7 @@ This example uses the [Qwen3 model](/en/documentation/products/ai/ai-inference/m 5. Click the **Save** button to save your changes. :::tip -Read the documentation about [managing functions](/en/documentation/products/build/edge-application/edge-functions/) for more details. +Read the documentation about [managing functions](/en/documentation/products/build/applications/functions/) for more details. ::: ### Managing the application diff --git a/src/content/docs/en/pages/guides/marketplace/templates/edge-application-proxy.mdx b/src/content/docs/en/pages/guides/marketplace/templates/edge-application-proxy.mdx index 4c197dd29d..fd816cf40c 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/edge-application-proxy.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/edge-application-proxy.mdx @@ -20,7 +20,7 @@ Preview The rule is composed by: - **Criteria**: if `${uri}` *starts with* `/url_route`. -- **Behavior**: then [Set Origin](/en/documentation/products/build/edge-application/rules-engine/#set-origin) `Default Origin`, [Bypass Cache](/en/documentation/products/build/edge-application/rules-engine/#bypass-cache), and [Forward Cookies](/en/documentation/products/build/edge-application/rules-engine/#forward-cookies). +- **Behavior**: then [Set Origin](/en/documentation/products/build/applications/rules-engine/#set-origin) `Default Origin`, [Bypass Cache](/en/documentation/products/build/applications/rules-engine/#bypass-cache), and [Forward Cookies](/en/documentation/products/build/applications/rules-engine/#forward-cookies). You must link your origin with the template to start using this set of rules. After the deployment, the script creates a new application that runs on **Azion Web Platform**, with which you can manage and adjust the settings. @@ -56,7 +56,7 @@ Fields identified with an asterisk are mandatory. - **Origin Address** *: the address of the hosted origin the application should fetch the original content from. - Example: `www.yourwebsite.com` - **Custom Host Header**: in some cases, it may be necessary to add host information in the header request to retrieve information from the origin. This variable is used for that purpose. - - Example: `${host}`. Read more about the host header and how to customize it on the [Origins documentation](/en/documentation/products/build/edge-application/origins/#host-header). + - Example: `${host}`. Read more about the host header and how to customize it on the [Origins documentation](/en/documentation/products/build/applications/origins/#host-header). - **Route to bypass** *: specific URL route to apply the bypassing rules. - Example: `/url_route` @@ -87,7 +87,7 @@ To manage and edit your application's settings, proceed as follows: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. ::: Learn how to deploy the Applications Proxy template. Watch the video below: diff --git a/src/content/docs/en/pages/guides/marketplace/templates/edge-function-github-autopeploy.mdx b/src/content/docs/en/pages/guides/marketplace/templates/edge-function-github-autopeploy.mdx index 886e7b6654..2b8bd03ed3 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/edge-function-github-autopeploy.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/edge-function-github-autopeploy.mdx @@ -94,5 +94,5 @@ The new application has an assigned Azion Workload domain to make it accessible import LinkButton from 'azion-webkit/linkbutton'; - + diff --git a/src/content/docs/en/pages/guides/marketplace/templates/edge-function-starter-kit.mdx b/src/content/docs/en/pages/guides/marketplace/templates/edge-function-starter-kit.mdx index 829e2e0c72..40f6a5414f 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/edge-function-starter-kit.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/edge-function-starter-kit.mdx @@ -75,7 +75,7 @@ This template includes a simple `Hello World` function that is ready to run. Fol 5. Click the **Save** button to save your changes. :::tip -Read the documentation about [managing functions](/en/documentation/products/build/edge-application/edge-functions/) for more details. +Read the documentation about [managing functions](/en/documentation/products/build/applications/functions/) for more details. ::: ### Managing the application diff --git a/src/content/docs/en/pages/guides/marketplace/templates/edgesql-starter-kit.mdx b/src/content/docs/en/pages/guides/marketplace/templates/edgesql-starter-kit.mdx index b6a5bb4568..ad485add9f 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/edgesql-starter-kit.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/edgesql-starter-kit.mdx @@ -22,10 +22,10 @@ The deployment of this template creates a GitHub repository containing your proj ## Requirements - An SQL Database slot. - - The number of available slots is defined by your service plan. For more information visit our [SQL Database reference](https://www.azion.com/en/documentation/products/store/edge-sql/). + - The number of available slots is defined by your service plan. For more information visit our [SQL Database reference](https://www.azion.com/en/documentation/products/store/sql-database/). - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- @@ -80,7 +80,7 @@ To manage and edit your application's settings, follow these steps: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation for more details about [managing applications](/en/documentation/products/build/edge-application/first-steps/) and [managing EdgeSQL databases](/en/documentation/products/guides/manage-databases-edge-sql/). +Read the documentation for more details about [managing applications](/en/documentation/products/build/applications/first-steps/) and [managing EdgeSQL databases](/en/documentation/products/guides/manage-sql-database/). ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/hello-world.mdx b/src/content/docs/en/pages/guides/marketplace/templates/hello-world.mdx index 0743a27f97..814e346f80 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/hello-world.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/hello-world.mdx @@ -93,7 +93,7 @@ The application created during the deployment has an assigned Azion Workload dom import LinkButton from 'azion-webkit/linkbutton'; - + diff --git a/src/content/docs/en/pages/guides/marketplace/templates/hexo-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/hexo-boilerplate.mdx index 2e339b429d..306d63dee4 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/hexo-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/hexo-boilerplate.mdx @@ -96,7 +96,7 @@ The application created during the deployment has an assigned Azion Workload dom import LinkButton from 'azion-webkit/linkbutton'; - + diff --git a/src/content/docs/en/pages/guides/marketplace/templates/image-optimization.mdx b/src/content/docs/en/pages/guides/marketplace/templates/image-optimization.mdx index 39ab9c73d3..ae799f1a79 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/image-optimization.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/image-optimization.mdx @@ -52,7 +52,7 @@ Fields identified with an asterisk are mandatory. - **Origin Address** *: the address of the hosted origin the application should fetch the original content from. - Example: `www.yourwebsite.com` - **Custom Host Header**: in some cases, it may be necessary to add host information in the header request to retrieve information from the origin. This variable is used for that purpose. - - Example: `${host}`. Read more about the host header and how to customize it on the [Origins documentation](/en/documentation/products/build/edge-application/origins/#host-header). + - Example: `${host}`. Read more about the host header and how to customize it on the [Origins documentation](/en/documentation/products/build/applications/origins/#host-header). - **Image file extensions to cache** *: the file extensions for the rules, separated by a comma. You can add as many variables as you need, based on the example. - Example: `jpg,jpeg,bmp,ico,gif,png` - **CDN Static Maximum TTL** *: a maximum TTL (time-to-live), in seconds, for cached content to be delivered. @@ -87,7 +87,7 @@ To manage and edit your application's settings, proceed as follows: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) and [Azion Image Processor](/en/documentation/products/build/edge-application/image-processor/) for more details. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) and [Azion Image Processor](/en/documentation/products/build/applications/image-processor/) for more details. ::: Learn how to deploy the Image Optimization template. Watch the video below: diff --git a/src/content/docs/en/pages/guides/marketplace/templates/mongodb-template.mdx b/src/content/docs/en/pages/guides/marketplace/templates/mongodb-template.mdx index bcc134706e..304c1c642a 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/mongodb-template.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/mongodb-template.mdx @@ -245,7 +245,7 @@ The application created during the deployment has an assigned Azion Workload dom import LinkButton from 'azion-webkit/linkbutton'; - + Learn how to deploy the MongoDB Atlas Boilerplate. Watch the video below: diff --git a/src/content/docs/en/pages/guides/marketplace/templates/neon-database-with-drizzle.mdx b/src/content/docs/en/pages/guides/marketplace/templates/neon-database-with-drizzle.mdx index 6a186aae26..7fb31b84c3 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/neon-database-with-drizzle.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/neon-database-with-drizzle.mdx @@ -24,7 +24,7 @@ The deployment of this template creates a GitHub repository containing your proj - Every push will be deployed automatically to this repository to keep your project updated. - A [Neon database](https://neon.tech/) with available space for a new table. -This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. Database storage and operations could also generate costs directly by Neon. Check [Neon's pricing page](https://neon.tech/pricing) for details. +This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. Database storage and operations could also generate costs directly by Neon. Check [Neon's pricing page](https://neon.tech/pricing) for details. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/next-app-config.mdx b/src/content/docs/en/pages/guides/marketplace/templates/next-app-config.mdx index 1630519732..7a0fd15f68 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/next-app-config.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/next-app-config.mdx @@ -16,7 +16,7 @@ Preview The **Next.js App + Configurations** template provides a quick start to build a Next.js application with custom configurations and App Router to run it directly on the edge. -This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), as well as an [Object Storage configuration](/en/documentation/products/store/edge-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. +This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), as well as an [Object Storage configuration](/en/documentation/products/store/object-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. **Next.js App + Configurations** also creates files to implement the [App Router format](https://nextjs.org/docs/app), including the index page, edge API routing, and Custom Route Handlers, created in the new repository during the deployment. diff --git a/src/content/docs/en/pages/guides/marketplace/templates/next-app-middleware.mdx b/src/content/docs/en/pages/guides/marketplace/templates/next-app-middleware.mdx index c78feca903..f0ea761745 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/next-app-middleware.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/next-app-middleware.mdx @@ -16,7 +16,7 @@ Preview The **Next.js App + Middleware** accelerates the deployment of a Next.js application with custom configurations, App Router, and a middleware to run it directly on the edge. -This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), an [Object Storage configuration](/en/documentation/products/store/edge-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. +This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), an [Object Storage configuration](/en/documentation/products/store/object-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. Next.js App + Middleware creates files to implement the [App Router format](https://nextjs.org/docs/app), with the index page, edge API routing, and Custom Route Handler created in the new repository during the deployment. It also includes a [middleware](https://nextjs.org/docs/app/building-your-application/routing/middleware) that allows you to modify the response for a request and control different aspects of the application, such as performing redirects, setting headers, and others. diff --git a/src/content/docs/en/pages/guides/marketplace/templates/next-pages-config.mdx b/src/content/docs/en/pages/guides/marketplace/templates/next-pages-config.mdx index 2ae9b85d99..fbda529ddd 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/next-pages-config.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/next-pages-config.mdx @@ -16,7 +16,7 @@ Preview The **Next.js Pages + Configurations** template enables you to quickly deploy a Next.js application with Pages Router and custom configurations. -This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), an [Object Storage configuration](/en/documentation/products/store/edge-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. +This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), an [Object Storage configuration](/en/documentation/products/store/object-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. **Next.js Pages + Configurations** also creates files to implement the [Pages Router format](https://nextjs.org/docs/pages), to use a file-system router to map each file to a route. diff --git a/src/content/docs/en/pages/guides/marketplace/templates/next-pages-middleware.mdx b/src/content/docs/en/pages/guides/marketplace/templates/next-pages-middleware.mdx index aa54ebe4be..786179310d 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/next-pages-middleware.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/next-pages-middleware.mdx @@ -16,7 +16,7 @@ Preview The **Next.js Pages + Middleware** template enables you to quickly deploy a Next.js application with Pages Router, a middleware, and custom configurations. -This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), an [Object Storage configuration](/en/documentation/products/store/edge-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. +This template deploys a basic Next.js application containing a domain to access the Single-Page Application (SPA), an [Object Storage configuration](/en/documentation/products/store/object-storage/), cache settings, Gzip compression, and Rules Engine rules to improve the performance and delivery of static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. **Next.js Pages + Middleware** also creates files to implement the [Pages Router format](https://nextjs.org/docs/pages), to use a file-system router to map each file to a route. It also includes a [middleware](https://nextjs.org/docs/app/building-your-application/routing/middleware) that allows you to modify the response for a request and control different aspects of the application, such as performing redirects, setting headers, and others. diff --git a/src/content/docs/en/pages/guides/marketplace/templates/nextjs-static-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/nextjs-static-boilerplate.mdx index 8e425858f2..848519f210 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/nextjs-static-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/nextjs-static-boilerplate.mdx @@ -131,6 +131,6 @@ The application created during the deployment has an assigned Azion Workload dom import LinkButton from 'azion-webkit/linkbutton'; - + diff --git a/src/content/docs/en/pages/guides/marketplace/templates/preact-javascript-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/preact-javascript-boilerplate.mdx index a9c9887764..fb05e9cbae 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/preact-javascript-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/preact-javascript-boilerplate.mdx @@ -25,7 +25,7 @@ This template uses Preact `10.25.3` and Vite `6.0.4` as its build tool. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/preact-typescript-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/preact-typescript-boilerplate.mdx index 2a65eeb6c7..13b1f19953 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/preact-typescript-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/preact-typescript-boilerplate.mdx @@ -25,7 +25,7 @@ This template uses Preact `10.25.3` and Vite `6.0.4` as its build tool. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/qstash-scheduler.mdx b/src/content/docs/en/pages/guides/marketplace/templates/qstash-scheduler.mdx index 4827888d2b..0525f7efde 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/qstash-scheduler.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/qstash-scheduler.mdx @@ -181,7 +181,7 @@ To manage and edit your application's settings, follow these steps: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) for more details. For specific Upstash or QStash-related questions, check the [Upstash documentation](https://docs.upstash.com/). +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) for more details. For specific Upstash or QStash-related questions, check the [Upstash documentation](https://docs.upstash.com/). ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/qwik-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/qwik-boilerplate.mdx index 6d80b8c81e..e210a6a785 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/qwik-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/qwik-boilerplate.mdx @@ -25,7 +25,7 @@ This template uses Qwik version `1.12.0`. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/qwik-minimal.mdx b/src/content/docs/en/pages/guides/marketplace/templates/qwik-minimal.mdx index bccd5ddc88..16bec7482d 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/qwik-minimal.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/qwik-minimal.mdx @@ -25,7 +25,7 @@ This template uses Qwik version `1.12.0`. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. - --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/react-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/react-boilerplate.mdx index 03d880830b..c7d7fb041c 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/react-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/react-boilerplate.mdx @@ -24,7 +24,7 @@ This template uses React version `18.2.0`. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Functions](/en/documentation/products/build/applications/functions/) and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Functions](/en/documentation/products/build/applications/functions/) and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- @@ -98,7 +98,7 @@ The application created during the deployment has an assigned Azion Workload dom import LinkButton from 'azion-webkit/linkbutton'; - + diff --git a/src/content/docs/en/pages/guides/marketplace/templates/static-cache.mdx b/src/content/docs/en/pages/guides/marketplace/templates/static-cache.mdx index ba2c7772e0..f3613cca9d 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/static-cache.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/static-cache.mdx @@ -56,7 +56,7 @@ Fields identified with an asterisk are mandatory. - **Origin Address** *: the address of the hosted origin the application should fetch the original content from. - Example: `www.yourwebsite.com` - **Custom Host Header**: in some cases, it may be necessary to add host information in the header request to retrieve information from the origin. This variable is used for that purpose. - - Example: `${host}`. Read more about the host header and how to customize it on the [Origins documentation](/en/documentation/products/build/edge-application/origins/#host-header). + - Example: `${host}`. Read more about the host header and how to customize it on the [Origins documentation](/en/documentation/products/build/applications/origins/#host-header). - **Static files extensions to cache** *: the static files extensions for the static rules, separated by a comma. You can add as many variables as you need, based on the example. - Example: `aif,aiff,au,avi,bin,cab,carb,cct,cdf,class,doc` - **CDN Static Maximum TTL** *: a maximum TTL (time-to-live), in seconds, for cached content to be delivered. @@ -89,7 +89,7 @@ To manage and edit your application's settings, proceed as follows: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) and [how to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) for more details. ::: Learn how to deploy the Static Cache template. Watch the video below: diff --git a/src/content/docs/en/pages/guides/marketplace/templates/stencil-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/stencil-boilerplate.mdx index 92245b177b..b225996541 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/stencil-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/stencil-boilerplate.mdx @@ -26,7 +26,7 @@ This template uses Stencil version `4.22.2`. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/stencil-pwa-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/stencil-pwa-boilerplate.mdx index 4458ac811a..24ad43594a 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/stencil-pwa-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/stencil-pwa-boilerplate.mdx @@ -22,7 +22,7 @@ This template uses Stencil version `4.17.0`. - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- diff --git a/src/content/docs/en/pages/guides/marketplace/templates/upstash-geolocation.mdx b/src/content/docs/en/pages/guides/marketplace/templates/upstash-geolocation.mdx index 75f49bd668..1c9574addf 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/upstash-geolocation.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/upstash-geolocation.mdx @@ -114,7 +114,7 @@ To manage and edit your application's settings, follow these steps: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) for more details. For specific Upstash-related questions, check the [Upstash documentation](https://docs.upstash.com/). +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) for more details. For specific Upstash-related questions, check the [Upstash documentation](https://docs.upstash.com/). ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/upstash-rate-limiting.mdx b/src/content/docs/en/pages/guides/marketplace/templates/upstash-rate-limiting.mdx index 08db4a7d62..3a5f4f418d 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/upstash-rate-limiting.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/upstash-rate-limiting.mdx @@ -98,7 +98,7 @@ To manage and edit your application's settings on Azion, follow these steps: After selecting the application you'll work on, you'll be directed to a page containing all the settings you can configure. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) for more details. For specific Upstash-related questions, check the [Upstash documentation](https://docs.upstash.com/). +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) for more details. For specific Upstash-related questions, check the [Upstash documentation](https://docs.upstash.com/). ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/videoteca-static-cache.mdx b/src/content/docs/en/pages/guides/marketplace/templates/videoteca-static-cache.mdx index 6c78a10706..373092712a 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/videoteca-static-cache.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/videoteca-static-cache.mdx @@ -24,7 +24,7 @@ The deployment of this template creates a GitHub repository containing your proj - A [GitHub account](https://github.com/signup) to connect with Azion and create your new repository. - Every push will be deployed automatically to this repository to keep your project updated. - The [Videoteca Player integration](/en/documentation/products/guides/videofront-player/) installed and configured in your Azion account. -- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), [Image Processor](/en/documentation/products/build/edge-application/image-processor/), and [Cache](/en/documentation/products/build/edge-application/edge-cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. +- This template uses [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/), [Functions](/en/documentation/products/build/applications/functions/), [Image Processor](/en/documentation/products/build/applications/image-processor/), and [Cache](/en/documentation/products/build/applications/cache/), and it may generate usage-related costs. Check the [pricing page](https://www.azion.com/en/pricing/) for more information. --- @@ -52,7 +52,7 @@ Fields identified with an asterisk are mandatory. - Use a unique and easy-to-remember name. If the name has already been used, the platform returns an error message. 2. Fill the additional fields with the information needed for configuring the **Videoteca Player integration**. - `Origin Address`: the domain name or IP address for your origin. - - `Custom Host Header`: customized value for the `host` header. Leave it blank to use the same address from the previous field. Read more about the host header and how to customize it on the [Origins](/en/documentation/products/build/edge-application/origins/#host-header) documentation. + - `Custom Host Header`: customized value for the `host` header. Leave it blank to use the same address from the previous field. Read more about the host header and how to customize it on the [Origins](/en/documentation/products/build/applications/origins/#host-header) documentation. - `Videoteca Player Path`: the path for the Videoteca player. Example: `/player`. - `Videoteca Username`: the username for the Videoteca account. - `Videoteca API Token`: the token for the Videoteca API. diff --git a/src/content/docs/en/pages/guides/marketplace/templates/vite-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/vite-boilerplate.mdx index bdc58f1ab4..828add3ebb 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/vite-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/vite-boilerplate.mdx @@ -14,7 +14,7 @@ Preview The **Vue3/Vite Boilerplate** accelerates the deployment of an application based on these frameworks directly on the edge. -This template deploys a new stack with a new application containing a domain to access the Single-Page Application (SPA), as well as [Object Storage configuration](/en/documentation/products/store/edge-storage/), cache settings, and Rules Engine rules to improve the performance of the static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. +This template deploys a new stack with a new application containing a domain to access the Single-Page Application (SPA), as well as [Object Storage configuration](/en/documentation/products/store/object-storage/), cache settings, and Rules Engine rules to improve the performance of the static files. Additionally, it creates a new GitHub repository, including a GitHub Action to enable a continuous development workflow and keep your application up to date. This template uses Vue version `3.3.4` and Vite version `4.4.6`. diff --git a/src/content/docs/en/pages/guides/marketplace/templates/vue-boilerplate.mdx b/src/content/docs/en/pages/guides/marketplace/templates/vue-boilerplate.mdx index 3cb344c1e1..2b6f980018 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/vue-boilerplate.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/vue-boilerplate.mdx @@ -100,7 +100,7 @@ The application created during the deployment has an assigned Azion Workload dom import LinkButton from 'azion-webkit/linkbutton'; - + diff --git a/src/content/docs/en/pages/guides/marketplace/templates/wordpress-edgeaccelerator.mdx b/src/content/docs/en/pages/guides/marketplace/templates/wordpress-edgeaccelerator.mdx index e3b3f4c54a..70a78fc8fc 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/wordpress-edgeaccelerator.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/wordpress-edgeaccelerator.mdx @@ -48,7 +48,7 @@ Fields identified with an asterisk are mandatory. - **Origin Address** *: the address of your hosted origin. This information is crucial for the application to know where to fetch the original content from. - For example: `www.yourwebsite.com`. - **Custom host header**: in some cases, it may be necessary to add host information in the header request to retrieve information from the origin. This variable is used for that purpose. - - For example: `${host}`. Read more about the Host Header and how to customize it on the [Origins documentation](/en/documentation/products/build/edge-application/origins/). + - For example: `${host}`. Read more about the Host Header and how to customize it on the [Origins documentation](/en/documentation/products/build/applications/origins/). After completing all the information, click the **Deploy** button, located in the bottom-right corner. This will start the deployment process. @@ -83,7 +83,7 @@ After selecting the application you'll work on, you're directed to a page contai Additionally, once the template is deployed, you also have full control over customizing your website's design, content, and functionality using the WordPress admin panel. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) for more details. For specific WordPress-related questions, check [WordPress official](https://wordpress.com/) channels. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) for more details. For specific WordPress-related questions, check [WordPress official](https://wordpress.com/) channels. ::: ### Adding a custom domain diff --git a/src/content/docs/en/pages/guides/marketplace/templates/wordpress-instacreator.mdx b/src/content/docs/en/pages/guides/marketplace/templates/wordpress-instacreator.mdx index 049b43371b..77d428d4ff 100644 --- a/src/content/docs/en/pages/guides/marketplace/templates/wordpress-instacreator.mdx +++ b/src/content/docs/en/pages/guides/marketplace/templates/wordpress-instacreator.mdx @@ -112,7 +112,7 @@ After selecting the application you'll work on, you're directed to a page contai Once the template is deployed, you also have full control over customizing your website's design, content, and functionality using the WordPress admin panel. :::tip -Read the documentation about [managing applications](/en/documentation/products/build/edge-application/first-steps/) for more details. For specific WordPress-related questions, check [WordPress official](https://wordpress.com/) channels. +Read the documentation about [managing applications](/en/documentation/products/build/applications/first-steps/) for more details. For specific WordPress-related questions, check [WordPress official](https://wordpress.com/) channels. ::: ### Adding a custom domain 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 b533cc3f47..601866fe47 100644 --- a/src/content/docs/en/pages/guides/mtls/configure-mtls.mdx +++ b/src/content/docs/en/pages/guides/mtls/configure-mtls.mdx @@ -18,9 +18,9 @@ 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, 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/). +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/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. +There are separate instructions using [legacy Domains](/en/documentation/products/build/applications/domains/) settings using the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. @@ -121,7 +121,7 @@ In this example, the Rule Set will block `(Error 403 Forbidden)` any incoming ne If your application is part of the Open Banking model, you' wi'll need to specify the variables `${ssl_client_escaped_cert}` and `${ssl_client_s_dn_parsed}` in the *header* of your application. You can also insert other mTLS variables. - + To add a variable to your application header, follow the steps: 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 a8dd5829b7..6d5b898956 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 @@ -20,9 +20,9 @@ Network Lists can be based on user's IP addresses, ASN, and geolocation addresse
- + -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. +There are separate instructions using [legacy Domains](/en/documentation/products/build/applications/domains/) settings using the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/guides/open-next/get-started-opennext.mdx b/src/content/docs/en/pages/guides/open-next/get-started-opennext.mdx index d04e2d0c74..1b87050597 100644 --- a/src/content/docs/en/pages/guides/open-next/get-started-opennext.mdx +++ b/src/content/docs/en/pages/guides/open-next/get-started-opennext.mdx @@ -148,7 +148,7 @@ module.exports = { ### Local Development -Use the [Azion CLI](/en/documentation/products/cli/) for local development: +Use the [Azion CLI](/en/documentation/products/azion-cli/overview/) for local development: ```sh azion dev diff --git a/src/content/docs/en/pages/guides/open-next/troubleshooting-opennext.mdx b/src/content/docs/en/pages/guides/open-next/troubleshooting-opennext.mdx index e22052edad..550bc95821 100644 --- a/src/content/docs/en/pages/guides/open-next/troubleshooting-opennext.mdx +++ b/src/content/docs/en/pages/guides/open-next/troubleshooting-opennext.mdx @@ -142,7 +142,7 @@ To resolve this: 3. **Optimize imports**: Prefer importing specific functions instead of entire libraries (for example, `import { parse } from "date-fns"` instead of `import * as dateFns from "date-fns"`). 4. **Leverage Azion’s caching**: Move static assets and large files to Azion’s Object Storage or CDN, and reference them via URLs instead of bundling them. -Refer to [Azion’s documentation on Functions limits](/en/documentation/products/build/edge-application/edge-functions/#limits) for up-to-date size restrictions. +Refer to [Azion’s documentation on Functions limits](/en/documentation/products/build/applications/functions/#limits) for up-to-date size restrictions. --- @@ -156,6 +156,6 @@ If your code can't access an expected environment variable: 2. **Redeploy after changes**: Any change to environment variables requires a redeploy of your function to take effect. 3. **Access variables correctly**: In your code, use `process.env.MY_VARIABLE` (for Node.js compatibility) or the platform-specific API if using another runtime. -If you’re using a framework like Next.js, ensure your build process does not overwrite or ignore these variables. For more, see [Azion’s guide to environment variables](/en/documentation/products/edge-functions/environment-variables/). +If you’re using a framework like Next.js, ensure your build process does not overwrite or ignore these variables. For more, see [Azion’s guide to environment variables](/en/documentation/products/functions/environment-variables/). --- \ No newline at end of file diff --git a/src/content/docs/en/pages/guides/waf/allowlist-waf-cookie.mdx b/src/content/docs/en/pages/guides/waf/allowlist-waf-cookie.mdx index 5c053cc4d4..0cbe5f5f65 100644 --- a/src/content/docs/en/pages/guides/waf/allowlist-waf-cookie.mdx +++ b/src/content/docs/en/pages/guides/waf/allowlist-waf-cookie.mdx @@ -22,7 +22,7 @@ To configure WAF rules to allow requests with a specific cookie, you must comple To implement this solution, you must have: -- An [existent firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) with the WAF add-on activated. +- An [existent firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) with the WAF add-on activated. --- @@ -42,7 +42,7 @@ First, you must create your primary **WAF Rule Set** that will be used as a stan ## Creating a secondary WAF Rule Set for a specific cookie -Still on the **WAF Rules** page, you must create a secondary **WAF Rule Set** including a [Custom Allowed Rule](/en/documentation/products/secure/edge-firewall/web-application-firewall/custom-allowed-rules/). To do so: +Still on the **WAF Rules** page, you must create a secondary **WAF Rule Set** including a [Custom Allowed Rule](/en/documentation/products/secure/firewall/web-application-firewall/custom-allowed-rules/). To do so: 1. Click the **+ WAF Rule** button to create the second instance. 2. Give a unique and descriptive name to identify your new WAF rule set. @@ -57,7 +57,7 @@ To create a Custom Allowed Rule, still in the WAF Rule Set you created: 2. Click the **+ Allowed Rule** button. 3. In the **Rule ID** dropdown menu, select a rule. - This example will use the `1005 Possible SQL Injection attack: MySQL keyword | found in Body, Path, Query String or Cookies.` rule. - - Read more about all the [available internal rules](/en/documentation/products/secure/edge-firewall/web-application-firewall/custom-allowed-rules/). + - Read more about all the [available internal rules](/en/documentation/products/secure/firewall/web-application-firewall/custom-allowed-rules/). 4. In **Description**, explain the reason this rule was allowed. 5. In **Path**, this example will use `/` to apply the rule to the whole site. - Type a more specific path to attend to your needs, if required. diff --git a/src/content/docs/en/pages/guides/waf/check-waf-mode.mdx b/src/content/docs/en/pages/guides/waf/check-waf-mode.mdx index d62b141430..1a1b3261f0 100644 --- a/src/content/docs/en/pages/guides/waf/check-waf-mode.mdx +++ b/src/content/docs/en/pages/guides/waf/check-waf-mode.mdx @@ -12,7 +12,7 @@ Azion **Web Application Firewall (WAF)** can operate in two different modes *lea The learning mode (or *calibration stage*) helps to improve WAF services and reduce false positives. Blocking mode will provide real-time protection against all supported threat families. :::tip -Check the list of all [threat families](/en/documentation/products/secure/edge-firewall/web-application-firewall/) that WAF can protect your applications from. +Check the list of all [threat families](/en/documentation/products/secure/firewall/web-application-firewall/) that WAF can protect your applications from. ::: This documentation will guide you on how to create, locate, and edit the operation mode of a WAF Rule Set configuration. @@ -25,8 +25,8 @@ This documentation will guide you on how to create, locate, and edit the operati The WAF operation mode is set on the **Rules Engine** tab of an **Firewall** configuration. Make sure you have: -- A [firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) associated with the domains of your applications. -- This firewall should have at least one [WAF Rule Set](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/). +- A [firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) associated with the domains of your applications. +- This firewall should have at least one [WAF Rule Set](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/). If you don't have a configured WAF Rule Set, check [this guide](/en/documentation/products/guides/secure/create-waf-rule-set/) for more details. diff --git a/src/content/docs/en/pages/guides/waf/configure-allowed-rules.mdx b/src/content/docs/en/pages/guides/waf/configure-allowed-rules.mdx index 83fe67e405..6ebdb0ed6e 100644 --- a/src/content/docs/en/pages/guides/waf/configure-allowed-rules.mdx +++ b/src/content/docs/en/pages/guides/waf/configure-allowed-rules.mdx @@ -16,7 +16,7 @@ Configuring a **WAF Custom Allowed Rule** allows you to instantiate specific rul This guide explains how to configure a WAF Custom Allowed Rule via Azion Web Platform. - + --- @@ -24,7 +24,7 @@ This guide explains how to configure a WAF Custom Allowed Rule via Azion Web Pla To instantiate Custom Allowed Rules in a WAF Rule Set, you must have: -- A [firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) with the Web Application Firewall module activated. +- A [firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) with the Web Application Firewall module activated. - A configured [WAF Rule Set](/en/documentation/products/guides/secure/create-waf-rule-set/). --- @@ -32,16 +32,16 @@ To instantiate Custom Allowed Rules in a WAF Rule Set, you must have: ## Configuring a WAF Custom Allowed Rule 1. Access [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/) > **WAF Rules** in **Edge Libraries**. -2. Create a [new WAF Rule Set](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/) or select an existent one. +2. Create a [new WAF Rule Set](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/) or select an existent one. 3. Select the **Allowed Rules** tab. 4. Click the **+ Allowed Rule** button. 5. Select the **Rule ID** you want to use. - - Check the list of all [available internal rules](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/). + - Check the list of all [available internal rules](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/). 6. Type a description to explain the reason this rule was allowed. 7. In the **Match Zone Set** section configure the behavior that should be used to allow a rule: - In **Path**, configure the behavior that should be used to allow a rule. Example: `/api/v1/resources/*`. - In **Match Zones**, select the part of the request to match such as headers, body, etc. - - According to the option, you could complete additional fields to add a specific value representing the match option and the matches for the value or the key name. Read more about [Allowed Rules fields](/en/documentation/products/secure/edge-firewall/web-application-firewall/#allowed-rules). + - According to the option, you could complete additional fields to add a specific value representing the match option and the matches for the value or the key name. Read more about [Allowed Rules fields](/en/documentation/products/secure/firewall/web-application-firewall/#allowed-rules). - If necessary, activate the **Regex** switch to treat conditional fields as regular expressions in all match zones. 8. Enable the **Status** switch. 9. Click the **Save** button. diff --git a/src/content/docs/en/pages/guides/waf/find-waf-score.mdx b/src/content/docs/en/pages/guides/waf/find-waf-score.mdx index ab915e83f1..9c980a500d 100644 --- a/src/content/docs/en/pages/guides/waf/find-waf-score.mdx +++ b/src/content/docs/en/pages/guides/waf/find-waf-score.mdx @@ -48,5 +48,5 @@ Check the [Real-Time Events documentation](/en/documentation/products/observe/re The higher the value of the `waf_score` field, the more indicative of threats were found in this request. If the result is `-`, no indication of threat has been found. This means the stricter the sensitivity level defined in your WAF, the greater the number of low `waf_score` blocked requests. :::tip -Check the scores for each sensitivity level available in the [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/) documentation. To find out if your WAF is operating in Learning or Blocking mode, you can use this same method and check the `waf_learning` field, or see [How to check your WAF mode](/en/documentation/products/guides/how-to-check-your-waf-mode/) guide. +Check the scores for each sensitivity level available in the [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/) documentation. To find out if your WAF is operating in Learning or Blocking mode, you can use this same method and check the `waf_learning` field, or see [How to check your WAF mode](/en/documentation/products/guides/how-to-check-your-waf-mode/) guide. ::: \ No newline at end of file diff --git a/src/content/docs/en/pages/main-menu/additional-resources/migrate-to-azion/migrate-to-azion.mdx b/src/content/docs/en/pages/main-menu/additional-resources/migrate-to-azion/migrate-to-azion.mdx index c9f2a446cd..cc7084aa7c 100644 --- a/src/content/docs/en/pages/main-menu/additional-resources/migrate-to-azion/migrate-to-azion.mdx +++ b/src/content/docs/en/pages/main-menu/additional-resources/migrate-to-azion/migrate-to-azion.mdx @@ -20,10 +20,10 @@ If you're subscribed to a service plan **Business** or higher, you have access t Before you migrate applications to Azion, there are two major variables that must exist: 1. **Origin address**: the source server of the application. This entry point to the edge takes the form of either a host, an IPv4, or an IPv6 address of a storage service or an existing application. - + 2. **Delivery domain**: the target domain of the application. This output takes the form of an Azion domain, which can be pointed to a custom domain. - + Most applications need an origin from which Azion retrieves the content and code that make them up. That application passes through Azion edge nodes for it to be delivered to users through a domain address. @@ -43,7 +43,7 @@ See the [full list of available templates](/en/documentation/products/guides/#az ## Step 2: Test locally -Before fully deploying the application, the recommendation is to [stage your application through the hosts file](/en/documentation/products/guides/stage-edge-application-through-hosts-file/) to ensure everything is working correctly. This step helps to identify and address any misconfigurations or issues caused by the migration. +Before fully deploying the application, the recommendation is to [stage your application through the hosts file](/en/documentation/products/guides/stage-applications-through-hosts-file/) to ensure everything is working correctly. This step helps to identify and address any misconfigurations or issues caused by the migration. --- diff --git a/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/understand-azion-templates.mdx b/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/understand-azion-templates.mdx index 4dcc617115..e886a186ee 100644 --- a/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/understand-azion-templates.mdx +++ b/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/understand-azion-templates.mdx @@ -301,7 +301,7 @@ This template helps you deploy a Docusaurus website integrated with Material UI The **AI Inference Starter Kit** template helps you create an edge AI-based application without origin dependencies. - + + + + + diff --git a/src/content/docs/en/pages/main-menu/get-started/azion-platform-overview.mdx b/src/content/docs/en/pages/main-menu/get-started/azion-platform-overview.mdx index 90a5ae4a14..ad16b2f70d 100644 --- a/src/content/docs/en/pages/main-menu/get-started/azion-platform-overview.mdx +++ b/src/content/docs/en/pages/main-menu/get-started/azion-platform-overview.mdx @@ -65,11 +65,11 @@ Azion provides different products and modules based on edge computing technology This includes tasks such as: -- Building and deploying [applications](/en/documentation/products/build/edge-application/) that run directly at the edge of the network. +- Building and deploying [applications](/en/documentation/products/build/applications/) that run directly at the edge of the network. - Using [templates and integrations](/en/documentation/products/marketplace/templates-and-integrations-overview/) to speed up your deployment and test pre-built solutions. - Creating [zero trust architectures](/en/documentation/architectures/) to protect your content and applications. - Improving your content delivery by relying on a [highly distributed network](https://www.azion.com/en/products/our-network/). -- Defining [caching rules](/en/documentation/products/build/edge-application/edge-cache/), custom optimizations, and advanced configurations. +- Defining [caching rules](/en/documentation/products/build/applications/cache/), custom optimizations, and advanced configurations. - Monitoring your applications with [data in real time](/en/documentation/products/observe/real-time-metrics/). - Improving your [performance](/en/documentation/architectures/edge-application/content-delivery/), with lower latency and bandwidth usage, while reducing operational costs. - Developing with different [supported frameworks and languages](/en/documentation/products/build/develop-with-azion/frameworks-specific/overview/). diff --git a/src/content/docs/en/pages/main-menu/get-started/go-live-with-azion.mdx b/src/content/docs/en/pages/main-menu/get-started/go-live-with-azion.mdx index fc4a38361f..99e2d0f0ce 100644 --- a/src/content/docs/en/pages/main-menu/get-started/go-live-with-azion.mdx +++ b/src/content/docs/en/pages/main-menu/get-started/go-live-with-azion.mdx @@ -37,8 +37,8 @@ This will open the Domains page to perform your changes. To do so, click the **Add Domain** button and fill in the presented fields to set up your custom domain: - **Add Configuration Name**: type a name for your domain. You can use the same name as your domain name. -- [Digital Certificate](/en/documentation/products/secure/edge-firewall/digital-certificates/): you can select the standard Azion Certificate (SAN), a [Let's Encrypt Certificate](/en/documentation/products/guides/how-to-generate-a-lets-encrypt-certificate/), or any [third-party Digital Certificate](/en/documentation/products/guides/create-a-digital-certificate/). -- [Canonical Names (CNAMES)](/en/documentation/products/build/edge-application/domains/#cname): write all the CNAMES your domain has. CNAMES must be added one per line, no punctuation. +- [Digital Certificate](/en/documentation/products/secure/firewall/certificate-manager/): you can select the standard Azion Certificate (SAN), a [Let's Encrypt Certificate](/en/documentation/products/guides/how-to-generate-a-lets-encrypt-certificate/), or any [third-party Digital Certificate](/en/documentation/products/guides/create-a-digital-certificate/). +- [Canonical Names (CNAMES)](/en/documentation/products/build/applications/domains/#cname): write all the CNAMES your domain has. CNAMES must be added one per line, no punctuation. - **CNAME Access Only** switch: it should be activated if you want your users to access your application only by CNAME. - **Application**: select the one your **Domain** will be connected to from the dropdown list. - The **Active** switch: it must be on. diff --git a/src/content/docs/en/pages/main-menu/reference/ai-inference/edge-ai-reference.mdx b/src/content/docs/en/pages/main-menu/reference/ai-inference/edge-ai-reference.mdx index d9768f42e2..d9086690f7 100644 --- a/src/content/docs/en/pages/main-menu/reference/ai-inference/edge-ai-reference.mdx +++ b/src/content/docs/en/pages/main-menu/reference/ai-inference/edge-ai-reference.mdx @@ -46,10 +46,10 @@ Integrate with **SQL Database** to enable vector search capabilities, allowing f ## Related products -- [Applications](/en/documentation/products/build/edge-application/): build applications that run directly on Azion's distributed network, delivering exceptional performance and customization options. -- [Functions](/en/documentation/products/build/edge-application/edge-functions/): execute code closer to end users, enhancing performance and enabling custom logic for handling requests and responses. -- [SQL Database](/en/documentation/products/store/edge-sql/): an edge-native SQL solution designed for serverless applications, providing data storage and querying capabilities at the edge. -- [Vector Search](/en/documentation/products/store/edge-sql/vector-search/): enable semantic search engines and AI-powered recommendations through vector embeddings at the edge. +- [Applications](/en/documentation/products/build/applications/): build applications that run directly on Azion's distributed network, delivering exceptional performance and customization options. +- [Functions](/en/documentation/products/build/applications/functions/): execute code closer to end users, enhancing performance and enabling custom logic for handling requests and responses. +- [SQL Database](/en/documentation/products/store/sql-database/): an edge-native SQL solution designed for serverless applications, providing data storage and querying capabilities at the edge. +- [Vector Search](/en/documentation/products/store/sql-database/vector-search/): enable semantic search engines and AI-powered recommendations through vector embeddings at the edge. --- diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/cache-settings.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/cache-settings.mdx index 084592ad0d..465c8452e5 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/cache-settings.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/cache-settings.mdx @@ -17,7 +17,7 @@ With **Cache Settings** for **Applications**, you can edit cache configurations | --- | --- | | Applications first steps | [First steps](/en/documentation/products/build/applications/first-steps/) | | Cache module | [Cache](/en/documentation/products/build/applications/cache/) | -| Tiered Cache module | [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/) | +| Tiered Cache module | [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) | | Creating a cache setting | [How to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) | | Configuring Advanced Cache Key | [How to configure Advanced Cache Key for Applications](/en/documentation/products/guides/advanced-cache-key/) | @@ -37,7 +37,7 @@ With **Cache Settings** for **Applications**, you can edit cache configurations **CDN Cache Settings** configures how Azion caches the content at the edge. You can select from the following options: - **Honor Origin Cache Headers**: maintains the cache definitions sent by your origin servers through HTTP headers (*Cache-Control and Expires*), sending the same headers to the web browser. -- **Override Cache Settings**: overrides the cache setting of your origin server with the desired TTL. To set the TTL of CDN cache to values under 60 seconds, you must enable the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module. +- **Override Cache Settings**: overrides the cache setting of your origin server with the desired TTL. To set the TTL of CDN cache to values under 60 seconds, you must enable the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module. --- @@ -45,7 +45,7 @@ With **Cache Settings** for **Applications**, you can edit cache configurations **Large File Optimization** works with a default fragment size of *1024 kB*. If you want to modify the fragmentation range, [contact the Sales team](https://www.azion.com/en/contact-sales/). - + :::note When activating this feature, each fragment of the file within the defined the range will carry a different cache key. @@ -53,7 +53,7 @@ When activating this feature, each fragment of the file within the defined the r Large File Optimization can be applied to both the cache layer at the edge and the tiered cache layer, provided that **Tiered Cache** is an active module. - + --- diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx index 381734daa8..84e054651f 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx @@ -32,8 +32,8 @@ You may also bind a **Digital Certificate** to domains that use the HTTPS protoc | Scope | Resource | | --- | --- | | Adding a custom domain | [Getting started](/en/documentation/products/guides/configure-a-domain/) | -| About Certificate Manager | [Certificate Manager](/en/documentation/products/secure/edge-firewall/digital-certificates/) | -| About mTLS | [mTLS](/en/documentation/products/secure/edge-firewall/mtls/) | +| About Certificate Manager | [Certificate Manager](/en/documentation/products/secure/firewall/certificate-manager/) | +| About mTLS | [mTLS](/en/documentation/products/secure/firewall/mtls/) | --- @@ -78,7 +78,7 @@ To enable this feature, contact our [Sales Team](https://www.azion.com/en/contac ## Local staging of custom domain -The local `etc/hosts` file maps IP addresses to domains. When you [associate the edge node IP with the CNAME](/en/documentation/products/guides/stage-edge-application-through-hosts-file/) assigned to your domain in your `hosts` file, you force your computer's DNS resolution to access this domain through the edge node and not through public DNS servers. This way, you can stage your application locally as if it were already deployed on your custom domain on the edge before you [point your domain](/en/documentation/products/guides/point-domain-to-azion/) to Azion. +The local `etc/hosts` file maps IP addresses to domains. When you [associate the edge node IP with the CNAME](/en/documentation/products/guides/stage-applications-through-hosts-file/) assigned to your domain in your `hosts` file, you force your computer's DNS resolution to access this domain through the edge node and not through public DNS servers. This way, you can stage your application locally as if it were already deployed on your custom domain on the edge before you [point your domain](/en/documentation/products/guides/point-domain-to-azion/) to Azion. --- diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-application.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-application.mdx index 07200a1017..7ee5d110d4 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-application.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-application.mdx @@ -21,7 +21,7 @@ You're viewing the latest version of this documentation. If your account hasn't By operating on a reverse proxy architecture, Applications allows you to create applications on the edge and direct traffic from your domain to Azion. Through this process, your users can access your application via a highly distributed global network of edge nodes. Then, Azion selects which edge node closest to the user can handle the request. -Your content or application must be served from one or more origins. An origin, also called your applications backend, can be made up of one or more web servers in your infrastructure, a cloud service, or [Object Storage](/en/documentation/products/store/edge-storage/). *Connector* is used to connect to these origin sources. For more information, see the [Connectors reference](/en/documentation/products/secure/connector/). +Your content or application must be served from one or more origins. An origin, also called your applications backend, can be made up of one or more web servers in your infrastructure, a cloud service, or [Object Storage](/en/documentation/products/store/object-storage/). *Connector* is used to connect to these origin sources. For more information, see the [Connectors reference](/en/documentation/products/secure/connectors/). With Applications, you can: - Define how your content will be cached. @@ -29,7 +29,7 @@ With Applications, you can: - Bring your business rules for any request or response. - Optimize content and image delivery for your users. - + You can create and manage applications using: @@ -50,7 +50,7 @@ You can create and manage applications using: | Get to know Functions | [Functions Instances](/en/documentation/products/build/applications/functions-instances/) | | Get to know Device Groups | [Device Groups](/en/documentation/products/build/applications/device-groups/) | | Get to know Workloads | [Workloads](/en/documentation/products/secure/workloads/) | -| Get to know Connectors | [Connectors](/en/documentation/products/secure/connector/) | +| Get to know Connectors | [Connectors](/en/documentation/products/secure/connectors/) | | Get to know Real-Time Purge | [Real-Time Purge](/en/documentation/products/build/applications/real-time-purge/) | | Rules Engine for Applications | [Rules Engine](/en/documentation/products/build/applications/rules-engine/) | @@ -68,7 +68,7 @@ See the documentation for each module: | [Cache](/en/documentation/products/build/applications/cache/) | Configure cache settings to speed up the delivery of static and dynamic content. | | [Functions](/en/documentation/products/build/applications/functions/) | Build ultra-low latency applications and customize content delivery. | | [Image Processor](/en/documentation/products/build/applications/image-processor/) | Optimize image processing for various devices, browsers, and screen resolutions. | -| [Tiered Cache](/en/documentation/products/build/applications/tiered-cache/) | Add a cache layer between your users and the edge to keep objects in cache for longer periods of time. | +| [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) | Add a cache layer between your users and the edge to keep objects in cache for longer periods of time. | --- @@ -90,7 +90,7 @@ See the documentation for each available setting: ## Real-Time Purge -Use **Real-Time Purge** to clear cached content from Azion's edge or from the [tiered cache layer]](/en/documentation/products/build/applications/tiered-cache/) to maintain content accuracy, reduce outdated content delivery, and deliver an optimal user experience on your application. +Use **Real-Time Purge** to clear cached content from Azion's edge or from the [tiered cache layer]](/en/documentation/products/build/applications/cache/tiered-cache/) to maintain content accuracy, reduce outdated content delivery, and deliver an optimal user experience on your application. 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 04bce97ea4..455038d901 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 @@ -22,7 +22,7 @@ If origin servers experience downtime or become unavailable, Azion Cache can als | Scope | Resource | | --- | --- | | Available cache settings | [Cache Settings](/en/documentation/products/build/applications/cache-settings/) | -| Tiered Cache module | [Tiered Cache](/en/documentation/products/build/applications/tiered-cache/) | +| Tiered Cache module | [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) | | Configuring a cache policy | [How to configure cache policies for Applications](/en/documentation/products/guides/cache-settings/) | --- @@ -191,7 +191,7 @@ The ability to customize both the browser cache TTL and cache TTL at the edge al ## Adaptive Delivery -**Adaptive Delivery** detects device groups you've created using [Device Groups](/en/documentation/products/build/edge-application/device-groups/), allowing you to configure how Azion delivers your content. You may choose to deliver the same version of the content, regardless of device detection or keep device-based variations of objects in cache. +**Adaptive Delivery** detects device groups you've created using [Device Groups](/en/documentation/products/build/applications/device-groups/), allowing you to configure how Azion delivers your content. You may choose to deliver the same version of the content, regardless of device detection or keep device-based variations of objects in cache. diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-functions.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-functions.mdx index dbae0b2f39..8e800ae0ce 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-functions.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-functions.mdx @@ -45,7 +45,7 @@ By using the [Azion Runtime](/en/documentation/runtime/overview/) to develop you
-
+

--- @@ -56,7 +56,7 @@ Functions provides support for advanced AI workflows, enabling you to: - Run AI agents directly on Azion's distributed infrastructure with ultra-low latency, building enterprise-grade solutions that operate at the edge with reliability and scale. - Create sophisticated AI workflows using **LangGraph** and **LangChain** integrations, including advanced retrieval capabilities that combine vector and full-text search for complex use cases. -- Leverage native [SQL Database](/en/documentation/products/store/edge-sql/) integration for RAG implementations and vector storage, along with MCP Servers that enable agent-to-agent collaboration using Google's Agent2Agent (A2A) protocol. +- Leverage native [SQL Database](/en/documentation/products/store/sql-database/) integration for RAG implementations and vector storage, along with MCP Servers that enable agent-to-agent collaboration using Google's Agent2Agent (A2A) protocol. - Access state-of-the-art models like Mistral, Florence, Qwen, and others, that follow OpenAI's API standard, all while reducing complexity with a fully integrated AI infrastructure running at the edge of the network. Azion's **AI Inference** allows you to run AI models on Azion Runtime, and can be used together with Functions to create complex AI-powered applications. diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/first-steps.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/first-steps.mdx index 2ca553a6a2..ac413571f5 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/first-steps.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/first-steps.mdx @@ -31,7 +31,7 @@ You're now in the page to configure the general delivery settings of your applic - [Cache](/en/documentation/products/build/applications/cache/) - [Functions](/en/documentation/products/build/applications/functions/) - [Image Processor](/en/documentation/products/build/applications/image-processor/) -- [Tiered Cache](/en/documentation/products/build/applications/tiered-cache/) +- [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) Some **Applications modules** are billed products and it may generate usage-related costs. Check the [Applications modules pricing](/en/documentation/products/pricing/) for more information. @@ -58,7 +58,7 @@ Each tab stores in other configuration options for your application. A backend, also known as an origin, is the server from which Azion retrieves your content. This can include object storage services, cloud servers, or other infrastructure that hosts your application assets or data. -To configure your application's origin you'll use [Connectors](/en/documentation/products/secure/edge-connector/). +To configure your application's origin you'll use [Connectors](/en/documentation/products/secure/connectors/). 1. [Access Console](https://console.azion.com). 2. On the upper-left corner of the page, select **Products Menu** > **Connectors**. @@ -68,7 +68,7 @@ To configure your application's origin you'll use [Connectors](/en/documentation 6. Click the **Save** button. :::note -For more details on Connector Types, please visit the [Connectors reference](/en/documentation/products/secure/edge-connector/). +For more details on Connector Types, please visit the [Connectors reference](/en/documentation/products/secure/connectors/). ::: To activate an Connector: @@ -80,7 +80,7 @@ To activate an Connector: 5. Select the Connector you want to apply. 6. Click the **Save** button. -**Connector** enables you to configure multiple origins and distribute traffic among them by using [Load Balancer](/en/documentation/products/secure/edge-connector/load-balancer/). +**Connector** enables you to configure multiple origins and distribute traffic among them by using [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/). :::tip You can use [Custom Pages](/en/documentation/products/secure/custom-pages/) to configure custom error pages that are displayed when **Connector** receives specific error responses (such as HTTP 4xx or 5xx status codes) from your origin. @@ -131,7 +131,7 @@ Edit your cache configuration in [Cache Settings](/en/documentation/products/bui #### Tiered Cache -To use the [Tiered Cache](/en/documentation/products/build/applications/tiered-cache/) module: +To use the [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) module: 1. In the **Main Settings** tab, at the end of the **Applications Modules** section, enable the **Tiered Cache** switch. 2. Access the **Cache Settings** tab. diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/origins.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/origins.mdx index e213179cdf..fdb6ee34a7 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/origins.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/origins.mdx @@ -44,7 +44,7 @@ There are three options for you to customize your origin: When **Load Balancer** is selected as an origin type, you can configure the **Balancing Method** to determine how large amounts of requests are distributed among addresses, add multiple **Addresses** to your origin, and change the **Sever Role** and **Weight** of each address. - + ### Object Storage @@ -54,7 +54,7 @@ The bucket name is defined when you [create or modify an Object Storage bucket]( The prefix is the path to the folder within the bucket that stores the objects. This field can be left blank if you wish your application's origin to be the root of the bucket. - + --- diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/real-time-purge.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/real-time-purge.mdx index 9bbc8a314c..ea6ee3f0bf 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/real-time-purge.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/real-time-purge.mdx @@ -48,7 +48,7 @@ You can use the `DEL` if your goal is to: **Real-Time Purge** offers you two layers to purge your cache from: - **Cache**: purges cache kept with Azion at the edge. -- **Tiered Cache**: purges cache from the second layer at the edge. Can only be done when the [Tiered Cache](/en/documentation/products/build/applications/tiered-cache/) module is active. +- **Tiered Cache**: purges cache from the second layer at the edge. Can only be done when the [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) module is active. --- diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/edge-application-v3.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/edge-application-v3.mdx index 4951806824..1dd6003497 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/edge-application-v3.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/edge-application-v3.mdx @@ -13,7 +13,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' :::caution[important] -You're viewing an earlier version of this documentation. If your account has already been migrated, see the updated [Applications reference](/en/documentation/products/build/edge-application/). +You're viewing an earlier version of this documentation. If your account has already been migrated, see the updated [Applications reference](/en/documentation/products/build/applications/). ::: **Applications** is an Azion product that allows you to build applications that run in Azion's edge network. By reducing latency and enhancing throughput, Applications optimizes your end-user experience by bringing your application closer to them. @@ -30,7 +30,7 @@ With Applications, you can: - Optimize content and image delivery for your users. - Customize origins and error pages. - + You can create and manage applications using: @@ -43,17 +43,17 @@ You can create and manage applications using: | Scope | Resource | | --- | --- | -| Applications first steps | [First steps](/en/documentation/products/build/edge-application/first-steps/) | -| Clone an Applications | [How to clone an Application](/en/documentation/products/guides/clone-edge-application/) | -| Delete an Application | [How to delete an Application](/en/documentation/products/guides/delete-edge-application/) | +| Applications first steps | [First steps](/en/documentation/products/build/applications/first-steps/) | +| Clone an Applications | [How to clone an Application](/en/documentation/products/guides/clone-applications/) | +| Delete an Application | [How to delete an Application](/en/documentation/products/guides/delete-applications/) | | Application Main Settings | [Main Settings](/en/documentation/products/build/edge-application/main-settings/v3/) | -| Application Cache Settings | [Cache Settings](/en/documentation/products/build/edge-application/cache-settings/) | -| Get to know Functions | [Functions Instances](/en/documentation/products/build/edge-application/edge-functions-instances/) | -| Get to know Device Groups | [Device Groups](/en/documentation/products/build/edge-application/device-groups/) | -| Get to know Error Responses | [Error Responses](/en/documentation/products/build/edge-application/error-responses/) | -| Get to know Origins | [Origins](/en/documentation/products/build/edge-application/origins/) | -| Get to know Real-Time Purge | [Real-Time Purge](/en/documentation/products/build/edge-application/real-time-purge/) | -| Rules Engine for Application | [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/) | +| Application Cache Settings | [Cache Settings](/en/documentation/products/build/applications/cache-settings/) | +| Get to know Functions | [Functions Instances](/en/documentation/products/build/applications/functions-instances/) | +| Get to know Device Groups | [Device Groups](/en/documentation/products/build/applications/device-groups/) | +| Get to know Error Responses | [Error Responses](/en/documentation/products/build/applications/error-responses/) | +| Get to know Origins | [Origins](/en/documentation/products/build/applications/origins/) | +| Get to know Real-Time Purge | [Real-Time Purge](/en/documentation/products/build/applications/real-time-purge/) | +| Rules Engine for Application | [Rules Engine](/en/documentation/products/build/applications/rules-engine/) | --- @@ -65,13 +65,13 @@ See the documentation for each module: | Module | Description | | --- | --- | -| [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) | Optimize API protocols and manage dynamic content delivery to accelerate applications and APIs. | -| [Cache](/en/documentation/products/build/edge-application/edge-cache/) | Configure cache settings to speed up the delivery of static and dynamic content. | -| [Functions](/en/documentation/products/build/edge-application/edge-functions/) | Build ultra-low latency applications and customize content delivery. | -| [Image Processor](/en/documentation/products/build/edge-application/image-processor/) | Optimize image processing for various devices, browsers, and screen resolutions. | -| [Load Balancer](/en/documentation/products/secure/edge-connector/load-balancer/) | Balance traffic between your origin servers and cloud providers to improve fault tolerance and avoid network congestion. | -| [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/) | Add a cache layer between your users and the edge to keep objects in cache for longer periods of time. | -| [WebSocket Proxy](/en/documentation/products/build/edge-application/websocket/) | Enable the WebSocket protocol to establish full-duplex communication channels over one TCP connection. | +| [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) | Optimize API protocols and manage dynamic content delivery to accelerate applications and APIs. | +| [Cache](/en/documentation/products/build/applications/cache/) | Configure cache settings to speed up the delivery of static and dynamic content. | +| [Functions](/en/documentation/products/build/applications/functions/) | Build ultra-low latency applications and customize content delivery. | +| [Image Processor](/en/documentation/products/build/applications/image-processor/) | Optimize image processing for various devices, browsers, and screen resolutions. | +| [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/) | Balance traffic between your origin servers and cloud providers to improve fault tolerance and avoid network congestion. | +| [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) | Add a cache layer between your users and the edge to keep objects in cache for longer periods of time. | +| [WebSocket Proxy](/en/documentation/products/build/applications/websocket/) | Enable the WebSocket protocol to establish full-duplex communication channels over one TCP connection. | --- @@ -83,13 +83,13 @@ See the documentation for each available setting: | Setting | Description | | --- | --- | -| [Main Settings](/en/documentation/products/build/edge-application/main-settings/) | Customize your application delivery with Azion's range of protocol options including HTTP, HTTPS, and HTTP/3 support for a better user experience and secure your connection with TLS ciphers. | -| [Origins](/en/documentation/products/build/edge-application/origins/) | Modify your origin address, `Host` header, path, protocol policies, and HMAC authentication credentials. | -| [Device Groups](/en/documentation/products/build/edge-application/device-groups/) | Create groups to change your application's cache and delivery behavior according to end-user devices. | -| [Error Responses](/en/documentation/products/build/edge-application/error-responses/) | Customize error response pages, their cache expiration time, and their origin. | -| [Cache Settings](/en/documentation/products/build/edge-application/cache-settings/) | Configure your application's browser and cache expiration time, large file optimization, and advanced cache behavior based on cookies or query strings. | -| [Functions](/en/documentation/products/build/edge-application/edge-functions-instances/) | Instantiate functions created with **Functions**. | -| [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/) | Automate the execution of behaviors based on specific parameters for your application. | +| [Main Settings](/en/documentation/products/build/applications/main-settings/) | Customize your application delivery with Azion's range of protocol options including HTTP, HTTPS, and HTTP/3 support for a better user experience and secure your connection with TLS ciphers. | +| [Origins](/en/documentation/products/build/applications/origins/) | Modify your origin address, `Host` header, path, protocol policies, and HMAC authentication credentials. | +| [Device Groups](/en/documentation/products/build/applications/device-groups/) | Create groups to change your application's cache and delivery behavior according to end-user devices. | +| [Error Responses](/en/documentation/products/build/applications/error-responses/) | Customize error response pages, their cache expiration time, and their origin. | +| [Cache Settings](/en/documentation/products/build/applications/cache-settings/) | Configure your application's browser and cache expiration time, large file optimization, and advanced cache behavior based on cookies or query strings. | +| [Functions](/en/documentation/products/build/applications/functions-instances/) | Instantiate functions created with **Functions**. | +| [Rules Engine](/en/documentation/products/build/applications/rules-engine/) | Automate the execution of behaviors based on specific parameters for your application. | --- @@ -97,7 +97,7 @@ See the documentation for each available setting: Azion **Workloads** provides you with the flexibility to use automatically generated domains or your own custom domains, allowing you to manage and deliver content effectively through your applications with support for secure connections over HTTP and HTTPS. - + --- @@ -105,15 +105,15 @@ Azion **Workloads** provides you with the flexibility to use automatically gener With **Certificate Manager**, you can enhance the security of your HTTPS applications by binding a custom TLS certificate to your application. - + --- ## Real-Time Purge -Use **Real-Time Purge** to clear cached content from Azion's edge or from the [tiered cache layer](/en/documentation/products/build/edge-application/tiered-cache/) to maintain content accuracy, reduce outdated content delivery, and deliver an optimal user experience on your application. +Use **Real-Time Purge** to clear cached content from Azion's edge or from the [tiered cache layer](/en/documentation/products/build/applications/cache/tiered-cache/) to maintain content accuracy, reduce outdated content delivery, and deliver an optimal user experience on your application. - + --- @@ -128,12 +128,12 @@ These are the **default limits**: | Scope | Limit | | ----- | ----- | -| Minimum CDN cache TTL | 60 seconds

For the [Application Accelerator](/en/documentation/products/build/edge-application/application-accelerator/) module: 0 seconds | +| Minimum CDN cache TTL | 60 seconds

For the [Application Accelerator](/en/documentation/products/build/applications/application-accelerator/) module: 0 seconds | | Debug Rules log size | 1.5 kB | | Edge-client keepalive connection¹ | 10 to 15 minutes | | Single object size in cache | 10 GB | -> ¹ Azion enforces a keepalive connection duration limit between users and applications. To avoid the termination of active connections that require more time to complete, consider implementing [file slicing](/en/documentation/products/build/edge-application/cache-settings/#slice-settings) or [file compression](/en/documentation/products/guides/gzip-compression/) for large files to improve data transfer speeds. +> ¹ Azion enforces a keepalive connection duration limit between users and applications. To avoid the termination of active connections that require more time to complete, consider implementing [file slicing](/en/documentation/products/build/applications/cache-settings/#slice-settings) or [file compression](/en/documentation/products/guides/gzip-compression/) for large files to improve data transfer speeds. These are the **default limits** for each Service Plan: diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/main-settings-v3.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/main-settings-v3.mdx index e9c944a4ef..27e74e0201 100644 --- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/main-settings-v3.mdx +++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/v3/main-settings-v3.mdx @@ -17,11 +17,11 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' :::caution[important] -You're viewing an earlier version of this documentation. If your account has already been migrated, see the updated [Application main settings reference](/en/documentation/products/build/edge-application/main-settings/). +You're viewing an earlier version of this documentation. If your account has already been migrated, see the updated [Application main settings reference](/en/documentation/products/build/applications/main-settings/). ::: -With [Application](/en/documentation/products/build/edge-application/), you can choose your application's delivery protocol and ports. You can also ensure the security of the HTTPS connection between the application and its users with TLS ciphers. +With [Application](/en/documentation/products/build/applications/), you can choose your application's delivery protocol and ports. You can also ensure the security of the HTTPS connection between the application and its users with TLS ciphers. --- @@ -31,7 +31,7 @@ With [Application](/en/documentation/products/build/edge-application/), you can - **HTTP & HTTPS**: delivers your application using both the HTTP and HTTPS protocols. :::note -If you choose to deliver your application through HTTP & HTTPS, you must associate a [digital certificate](/en/documentation/products/secure/edge-firewall/digital-certificates/) to your domain. +If you choose to deliver your application through HTTP & HTTPS, you must associate a [digital certificate](/en/documentation/products/secure/firewall/certificate-manager/) to your domain. ::: ### HTTP/3 support 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 47c409762f..f142720448 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 @@ -54,7 +54,7 @@ Learn more about the [Azion Orchestrator agent installation](/en/documentation/p **Node** enables the creation and management of devices, as well as integration with Azion. You need to install our agent so that the Azion platform can orchestrate its settings and ensure secure communication between the devices and Azion. -[Learn more about Node](/en/documentation/products/deploy/edge-orchestrator/edge-node/). +[Learn more about Node](/en/documentation/products/deploy/orchestrator/edge-node/). --- @@ -62,7 +62,7 @@ Learn more about the [Azion Orchestrator agent installation](/en/documentation/p **Services** enables you to create your own services. You can use your customized services and ensure your device is managed and orchestrated by [Azion Console](https://console.azion.com). -[Learn more about Services](/en/documentation/products/deploy/edge-orchestrator/edge-services/). +[Learn more about Services](/en/documentation/products/deploy/orchestrator/edge-services/). diff --git a/src/content/docs/en/pages/main-menu/reference/glossary/glossary.mdx b/src/content/docs/en/pages/main-menu/reference/glossary/glossary.mdx index c30d0b2c1c..79040cd25e 100644 --- a/src/content/docs/en/pages/main-menu/reference/glossary/glossary.mdx +++ b/src/content/docs/en/pages/main-menu/reference/glossary/glossary.mdx @@ -180,7 +180,7 @@ Ability of a system or component to continue functioning properly even if faults ### Feature -A part of a [product](#product) or [module](#module) that performs a specific function. For example: [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/). +A part of a [product](#product) or [module](#module) that performs a specific function. For example: [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/). --- @@ -234,7 +234,7 @@ Part of the HTTP protocol. They're used to transmit additional information betwe ### HTTP status -Response codes that a server sends to a client in response to an HTTP request. These status codes indicate the success or failure of the request and provide information about the specific nature of the response. The HTTP status codes are three-digit numbers grouped into [different categories](/en/documentation/products/build/edge-application/error-responses/#overview). +Response codes that a server sends to a client in response to an HTTP request. These status codes indicate the success or failure of the request and provide information about the specific nature of the response. The HTTP status codes are three-digit numbers grouped into [different categories](/en/documentation/products/build/applications/error-responses/#overview). --- @@ -270,7 +270,7 @@ Type of software architecture where an application is built as a single, self-co ### Module -A component of a system or application associated with a [product](#product), but working independently. It offers specific characteristics and functions to complement a product. For example: [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/). +A component of a system or application associated with a [product](#product), but working independently. It offers specific characteristics and functions to complement a product. For example: [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/). --- @@ -300,7 +300,7 @@ A platform or software based on open standards must be openly available, accessi ### Orchestration -Orchestration, in the context of Azion, refers to the process of managing and controlling edge resources in real time. This includes provisioning, updating, and managing various components such as applications, firewalls, functions, edge nodes, edge services, and third-party services via Marketplace. [Orchestrator](/en/documentation/products/deploy/edge-orchestrator/) allows users to simplify the installation and software updates by compiling all the necessary dependencies and libraries. It can be implemented manually on each edge node or automatically through the installation of the Azion agent on compatible systems. The orchestration process is sequential and respects the dependencies and triggers required for configuration. +Orchestration, in the context of Azion, refers to the process of managing and controlling edge resources in real time. This includes provisioning, updating, and managing various components such as applications, firewalls, functions, edge nodes, edge services, and third-party services via Marketplace. [Orchestrator](/en/documentation/products/deploy/orchestrator/) allows users to simplify the installation and software updates by compiling all the necessary dependencies and libraries. It can be implemented manually on each edge node or automatically through the installation of the Azion agent on compatible systems. The orchestration process is sequential and respects the dependencies and triggers required for configuration. --- @@ -318,7 +318,7 @@ Physical location where [edge computing](#edge-computing) infrastructure is depl ### Product -A digital service, such as software or data, offered to customers for use in different scenarios. For example: [Firewall](/en/documentation/products/secure/edge-firewall/). +A digital service, such as software or data, offered to customers for use in different scenarios. For example: [Firewall](/en/documentation/products/secure/firewall/). --- diff --git a/src/content/docs/en/pages/main-menu/reference/marketplace/marketplace-reference.mdx b/src/content/docs/en/pages/main-menu/reference/marketplace/marketplace-reference.mdx index 275f62e794..c903251445 100644 --- a/src/content/docs/en/pages/main-menu/reference/marketplace/marketplace-reference.mdx +++ b/src/content/docs/en/pages/main-menu/reference/marketplace/marketplace-reference.mdx @@ -66,7 +66,7 @@ By accessing [Azion Console](https://console.azion.com), you find the ideal opti ### Types of integrations -In Azion Marketplace, you'll find integrations that run functions in two ways: by using [Firewall](/en/documentation/products/secure/edge-firewall/) or by using [Applications](/en/documentation/products/build/edge-application/). The Firewall functions are focused on network security, authentication, and traffic control, while Applications functions are best fit to process data or run services on the edge, closer to the user. +In Azion Marketplace, you'll find integrations that run functions in two ways: by using [Firewall](/en/documentation/products/secure/firewall/) or by using [Applications](/en/documentation/products/build/applications/). The Firewall functions are focused on network security, authentication, and traffic control, while Applications functions are best fit to process data or run services on the edge, closer to the user. Check [Azion’s guides page](/en/documentation/products/guides/#marketplace) for more details on the installation for type of integration. 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 f4860482ae..b356199a49 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 @@ -181,10 +181,10 @@ The **Applications** data source provides the data from requests made to your [A | $waf_total_processed | Informs the total number of processed requests. | :::note -You can add the `$traceback` variable when using a custom template for the Applications data source if you have the *Debug rules* option activated in your application. See more on [Debugging rules on Application](/en/documentation/products/build/edge-application/rules-engine/#debugging-rules). +You can add the `$traceback` variable when using a custom template for the Applications data source if you have the *Debug rules* option activated in your application. See more on [Debugging rules on Application](/en/documentation/products/build/applications/rules-engine/#debugging-rules). ::: -The variables: `$upstream_bytes_received`, `$upstream_cache_status`, `$upstream_connect_time`, `$upstream_header_time`, `$upstream_response_time`, and `$upstream_status` can have *more than one comma-separated element*. When a connection is triggered, either by internal redirection or choice of source with [Load Balancer](/en/documentation/products/build/edge-application/load-balancer/), for example, each value contained in the field represents the respective initiated connection. The field can be separated by: +The variables: `$upstream_bytes_received`, `$upstream_cache_status`, `$upstream_connect_time`, `$upstream_header_time`, `$upstream_response_time`, and `$upstream_status` can have *more than one comma-separated element*. When a connection is triggered, either by internal redirection or choice of source with [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/), for example, each value contained in the field represents the respective initiated connection. The field can be separated by: - A comma, representing multiple IPs. - A colon, representing internal redirection. @@ -226,7 +226,7 @@ The following variables are available for this option: Requires: Web Application Firewall -The **WAF Events** data source provides the data from requests analyzed by [Web Application Firewall (WAF)](/en/documentation/products/secure/edge-firewall/web-application-firewall/) to allow you to map the score assigned to the request, the WAF rules that matched, and the reason for the block. +The **WAF Events** data source provides the data from requests analyzed by [Web Application Firewall (WAF)](/en/documentation/products/secure/firewall/web-application-firewall/) to allow you to map the score assigned to the request, the WAF rules that matched, and the reason for the block. The following variables are available for this option: @@ -283,7 +283,7 @@ By selecting one of the templates provided by Azion, you can't modify the variab ## Domains -You can associate your [existing domains](/en/documentation/products/build/edge-application/domains/) registered on Azion to your stream. If you haven't registered any domains to your account yet, see the [Creating a new domain associated with your Application](/en/documentation/products/guides/configure-a-domain/) documentation. +You can associate your [existing domains](/en/documentation/products/build/applications/domains/) registered on Azion to your stream. If you haven't registered any domains to your account yet, see the [Creating a new domain associated with your Application](/en/documentation/products/guides/configure-a-domain/) documentation. When you associate a domain, the events related with that or those specific domains are collected and sent to the endpoint you configure through a Data Stream. You can associate one or more domains and you have the option to **Filter Domains** or select **All Domains**. @@ -474,7 +474,7 @@ To configure the [IBM Qradar](https://www.ibm.com/qradar) endpoint, you need acc ### S3 - Simple Storage Service :::note -The S3 credentials used with the endpoint must include the `List Bucket` permission (to list and view objects within a bucket) and the `Put Object` permission (to add or overwrite objects within a bucket), ensuring the necessary access for reading and writing operations in the information storage, including logs. Find out more about [S3 credentials](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/). +The S3 credentials used with the endpoint must include the `List Bucket` permission (to list and view objects within a bucket) and the `Put Object` permission (to add or overwrite objects within a bucket), ensuring the necessary access for reading and writing operations in the information storage, including logs. Find out more about [S3 credentials](/en/documentation/products/store/storage/s3-protocol-for-object-storage/). ::: You can use any type of S3 (Simple Storage Service) provider of your choice, including [Azion Object Storage](/en/documentation/products/store/object-storage/). To configure the S3 endpoint, you need access to the chosen platform to get the required information: @@ -490,7 +490,7 @@ You can use any type of S3 (Simple Storage Service) provider of your choice, inc - **Content Type**: the format in which the object will be created in your bucket. You can chose between *plain/text* or *application/gzip*. - + --- 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 89f637895b..cb3109930b 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 @@ -123,7 +123,7 @@ The `Set WAF [Your WAF]` Firewall behavior performs special processing, allowing Requires: Functions -Displays the event records of requests made to your [Functions](/en/documentation/products/build/edge-application/edge-functions/). +Displays the event records of requests made to your [Functions](/en/documentation/products/build/applications/functions/). | Variable | Description | | -------- | ----------- | @@ -162,7 +162,7 @@ Displays the event records from applications using [Azion Runtime](/en/documenta Requires: Image Processor -Displays the event records of requests made to applications using [Image Processor](/en/documentation/products/build/edge-application/image-processor/). +Displays the event records of requests made to applications using [Image Processor](/en/documentation/products/build/applications/image-processor/). | Variable | Description | | -------- | ----------- | @@ -194,7 +194,7 @@ Displays the event records of requests made to applications using [Image Process Requires: Tiered Cache -Displays the event records of requests made to applications using [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/). +Displays the event records of requests made to applications using [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/). | Variable | Description | | -------- | ----------- | diff --git a/src/content/docs/en/pages/main-menu/reference/observe/real-time-metrics/real-time-metrics.mdx b/src/content/docs/en/pages/main-menu/reference/observe/real-time-metrics/real-time-metrics.mdx index 4f1bacb5eb..077d2c6a0b 100644 --- a/src/content/docs/en/pages/main-menu/reference/observe/real-time-metrics/real-time-metrics.mdx +++ b/src/content/docs/en/pages/main-menu/reference/observe/real-time-metrics/real-time-metrics.mdx @@ -207,7 +207,7 @@ Next, you can find detailed information about each tab and subtabs and about eac ### Applications -The **Applications** tab displays metrics related to the accesses of your [Applications](/en/documentation/products/build/edge-application/) configured in your account. You find four subtabs with different charts: [Data Transferred](#data-transferred), [Requests](#requests), [Status Codes](#status-codes), and [Bandwidth Saving](#bandwidth-saving). +The **Applications** tab displays metrics related to the accesses of your [Applications](/en/documentation/products/build/applications/) configured in your account. You find four subtabs with different charts: [Data Transferred](#data-transferred), [Requests](#requests), [Status Codes](#status-codes), and [Bandwidth Saving](#bandwidth-saving). #### Data Transferred @@ -229,7 +229,7 @@ import EdgeCaching from "~/includes/docs_help_center/en/real-time-metrics/edge-a ![Cache graph information flow for Data Transferred, representing all data being transferred from both Data Transferred In and Data Transferred Out.](/assets/docs/images/uploads/edge-applications.png) -If you have [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/) enabled, your Cache graph will exhibit: +If you have [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) enabled, your Cache graph will exhibit: - **Data Transferred In**: data transferred from the end user to the edges, and from the edges to the tiered cache layer. @@ -380,7 +380,7 @@ The table displays the 10 most frequently used Remote Addresses, but you can app ### Tiered Cache -The Tiered Cache tab displays metrics related to the data of your applications using [Tiered Cache](/en/documentation/products/build/edge-application/tiered-cache/) configured in your account. +The Tiered Cache tab displays metrics related to the data of your applications using [Tiered Cache](/en/documentation/products/build/applications/cache/tiered-cache/) configured in your account. Find out more about each chart: @@ -406,7 +406,7 @@ import L2Offload from "~/includes/docs_help_center/en/real-time-metrics/l2-cachi ### Functions -The **Functions** tab displays metrics related to the invocations of the [Functions](/en/documentation/products/build/edge-application/edge-functions/) configured in your account. +The **Functions** tab displays metrics related to the invocations of the [Functions](/en/documentation/products/build/applications/functions/) configured in your account. Find out more about the chart: @@ -416,7 +416,7 @@ import TotalInvocations from "~/includes/docs_help_center/en/real-time-metrics/e ### Image Processor -The **Image Processor** tab displays metrics related to the requests made to your images processed through [Image Processor](/en/documentation/products/build/edge-application/image-processor/) configured in your account. +The **Image Processor** tab displays metrics related to the requests made to your images processed through [Image Processor](/en/documentation/products/build/applications/image-processor/) configured in your account. Find out more about each chart: @@ -433,7 +433,7 @@ import TotalRequestsPerSecondIp from "~/includes/docs_help_center/en/real-time-m ### WAF -The **WAF** tab displays metrics related to [threats protected by WAF](/en/documentation/products/secure/edge-firewall/web-application-firewall/) in your account. +The **WAF** tab displays metrics related to [threats protected by WAF](/en/documentation/products/secure/firewall/web-application-firewall/) in your account. Find out more about each chart: @@ -505,9 +505,9 @@ The **WAF Threat Requests by Host** graph displays the total number of requests This graph helps you quickly identify which hosts are responsible for the highest volume of detected threats. By analyzing this data, you can take targeted security measures to mitigate risks, protect your applications, and take proactive steps to mitigate potential risks. For example: -- [Analyze flagged request logs](/en/documentation/products/secure/troubleshoot/edge-firewall-understand-metrics/) to identify patterns or potential vulnerabilities that need addressing. +- [Analyze flagged request logs](/en/documentation/products/secure/troubleshoot/firewall-understand-metrics/) to identify patterns or potential vulnerabilities that need addressing. - [Adjust WAF Rules Sets](/en/documentation/products/guides/secure/create-waf-rule-set/) to strengthen filtering policies to block or challenge suspicious requests from high-risk hosts. -- [Implement rate limiting](/en/documentation/products/secure/edge-firewall/rules-engine/#set-rate-limit) and restrict the number of requests from specific hosts to prevent abuse. +- [Implement rate limiting](/en/documentation/products/secure/firewall/rules-engine/#set-rate-limit) and restrict the number of requests from specific hosts to prevent abuse. - [Define blocklists](/en/documentation/products/guides/blocklists-ip-addresses-edge/) with identified threat sources to prevent repeated attacks. ### Edge DNS 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 3e12ea0c6e..485b5ad922 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 @@ -316,13 +316,13 @@ If you have an automation that currently uses the **Applications - Origins** API - **Simplified Backend Management**: **Connectors** centralizes all backend connection definitions, reducing configuration complexity. Multiple **Applications** can use a single **Connectors**, streamlining maintenance and ensuring configuration consistency. - **Future-Ready Architecture**: **Connectors** provides the foundation for upcoming Azion Web Platform features and optimizations, ensuring your Applications are ready to leverage new capabilities as they become available. - + --- ## Custom Pages -**Custom Pages** is an Azion feature that allows you to customize error pages for users based on the status code received from an [Connectors](/en/documentation/products/secure/edge-connector/) when fetching the content from your origin. +**Custom Pages** is an Azion feature that allows you to customize error pages for users based on the status code received from an [Connectors](/en/documentation/products/secure/connectors/) when fetching the content from your origin. **Custom Pages*** replaces Applications's **Error Responses** settings. All settings previously managed in Applications' **Error Responses** tab are now organized under **Custom Pages**. diff --git a/src/content/docs/en/pages/main-menu/reference/secure/custom-pages/custom-pages.mdx b/src/content/docs/en/pages/main-menu/reference/secure/custom-pages/custom-pages.mdx index 533464716a..ff6defe2d1 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/custom-pages/custom-pages.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/custom-pages/custom-pages.mdx @@ -14,10 +14,10 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' :::note -This page documents the new Custom Pages product. If your account hasn't been migrated yet, refer to the [legacy Error Responses documentation](/en/documentation/products/build/edge-application/error-responses/). +This page documents the new Custom Pages product. If your account hasn't been migrated yet, refer to the [legacy Error Responses documentation](/en/documentation/products/build/applications/error-responses/). ::: -**Custom Pages** is an Azion feature that allows you to customize error pages for users based on the status code received from an [Connector](/en/documentation/products/secure/connector/). +**Custom Pages** is an Azion feature that allows you to customize error pages for users based on the status code received from an [Connector](/en/documentation/products/secure/connectors/). When a user requests content from an application, Azion sends the request to the origin servers using **Connector**. As a response, the **Connector** sends back an HTTP status code, which indicates whether or not the request has been completed. @@ -31,9 +31,9 @@ With **Custom Pages**, you can customize how your application will handle *Clien | Scope | Resource | | --- | --- | -| Application first steps | [First steps](/en/documentation/products/build/edge-application/first-steps/) | +| Application first steps | [First steps](/en/documentation/products/build/applications/first-steps/) | | Customizing error page | [How to customize an error response page](/en/documentation/products/guides/customizing-error-response-page/) | -| Connectors | [Connectors reference](/en/documentation/products/secure/connector/) | +| Connectors | [Connectors reference](/en/documentation/products/secure/connectors/) | | Workloads | [Workloads reference](/en/documentation/products/secure/workloads/) | | Custom Pages API | [API reference](https://api.azion.com/v4#/operations/GetWorkspaceCustomPages) | @@ -76,7 +76,7 @@ These are the available status codes: Defines the time in seconds that the error page will remain in cache before it's refreshed. - + --- diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/edge-connector.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/edge-connector.mdx index 1e8abf163d..22a072df61 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/edge-connector.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/edge-connector.mdx @@ -12,7 +12,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' :::note -This page documents the new Connectors product. If your account hasn't been migrated yet, refer to the [legacy Origins reference](/en/documentation/products/build/edge-application/origins/). +This page documents the new Connectors product. If your account hasn't been migrated yet, refer to the [legacy Origins reference](/en/documentation/products/build/applications/origins/). ::: **Connectors** centralize connection settings, allowing you to reuse them across multiple applications, and provides granular control over performance, security, and routing through a unified interface for connecting Applications to an origin, natively incorporating features such as load balancing, HMAC authentication, and Origin Shield. @@ -21,7 +21,7 @@ This page documents the new Connectors product. If your account hasn't been migr | Scope | Resource | | --- | --- | -| Application first steps | [First steps](/en/documentation/products/build/edge-application/first-steps/) | +| Application first steps | [First steps](/en/documentation/products/build/applications/first-steps/) | | Load Balancer module | [Load Balancer](/en/documentation/products/secure/connectors/load-balancer/) | --- @@ -157,7 +157,7 @@ Below are the attributes for the [Connectors API](https://api.azion.com/v4#/oper ### Object Storage - When Object Storage is selected as an origin type, it connects directly with an [Azion Object Storage](/en/documentation/products/store/edge-storage/) bucket where you must add the bucket name and prefix. + When Object Storage is selected as an origin type, it connects directly with an [Azion Object Storage](/en/documentation/products/store/object-storage/) bucket where you must add the bucket name and prefix. The bucket name is defined when you [create or modify an Object Storage bucket](/en/documentation/products/guides/create-and-modify-bucket/). @@ -172,7 +172,7 @@ Below are the attributes for the [Connectors API](https://api.azion.com/v4#/oper | bucket | String | The name of the bucket. | | prefix | String | The prefix path for the bucket. | - + ### Live Ingest diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/load-balancer.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/load-balancer.mdx index 3084abc87f..f04e8d8bcf 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/load-balancer.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/load-balancer.mdx @@ -18,7 +18,7 @@ With Load Balancer, you can: - Choose between load balancing algorithms. - Create routing rules to balance HTTP and HTTPS requests. -For more options on how to direct traffic to **Load Balancer** based on other criteria, see the [Rules Engine for Application](/en/documentation/products/build/edge-application/rules-engine/) page. +For more options on how to direct traffic to **Load Balancer** based on other criteria, see the [Rules Engine for Application](/en/documentation/products/build/applications/rules-engine/) page. ## Implementation @@ -33,7 +33,7 @@ For more options on how to direct traffic to **Load Balancer** based on other cr The balancing method defines how requests will be distributed, considering the availability of your origins (layer 3) and potential access errors, such as when the origin returns an HTTP STATUS 500 (layer 7). :::note -**Load Balancer** will query the origins according to the balancing method and weight they're assigned. If an origin returns a `4xx` or a `5xx` error, or takes longer to respond than the [timeouts](/en/documentation/products/build/edge-application/origins/#timeouts) defined in the origin, the Load Balancer will override the balancing method and weight to query the remaining origins before returning an error to your users. +**Load Balancer** will query the origins according to the balancing method and weight they're assigned. If an origin returns a `4xx` or a `5xx` error, or takes longer to respond than the [timeouts](/en/documentation/products/build/applications/origins/#timeouts) defined in the origin, the Load Balancer will override the balancing method and weight to query the remaining origins before returning an error to your users. To customize this behavior, [contact the support team](https://tickets.azion.com/en/support/login). ::: @@ -58,7 +58,7 @@ The **IP Hash** balancing algorithm tracks user IP addresses and associates the You may add more than one **Address** for your origin. Addresses in **Load Balancer** follow the same logic as a **Single Origin** address. - + --- diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/origin-shield.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/origin-shield.mdx index 3416f95f9c..1ba1c47e78 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/origin-shield.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-connector/origin-shield.mdx @@ -22,7 +22,7 @@ Clients are responsible for automating updates to their security policies to kee | --- | --- | | Secure an application | [Secure an application](/en/documentation/products/secure/secure-infrastructure/) | | Connectors | [Connectors](/en/documentation/products/secure/connectors/) | -| Applications first steps | [First steps](/en/documentation/products/build/edge-application/first-steps/) | +| Applications first steps | [First steps](/en/documentation/products/build/applications/first-steps/) | --- diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/azion-bot-manager.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/azion-bot-manager.mdx index c4690e1230..39c955c097 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/azion-bot-manager.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/azion-bot-manager.mdx @@ -69,7 +69,7 @@ Bot Manager is able to execute **7 different actions** whenever the request's sc All these actions can be configured for web and mobile applications, as well as APIs, offering protection in different environments. :::tip -You can also benefit from **Secure** products, including [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/), [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/), [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/), and [Edge DNS](/en/documentation/products/secure/edge-dns/), to increase your protection, adding extra security layers to your infrastructure. +You can also benefit from **Secure** products, including [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/), [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/), [Network Shield](/en/documentation/products/secure/firewall/network-shield/), and [Edge DNS](/en/documentation/products/secure/edge-dns/), to increase your protection, adding extra security layers to your infrastructure. ::: ### Use cases diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/ddos-protection/ddos-protection.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/ddos-protection/ddos-protection.mdx index c047b4278a..1d714678e6 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/ddos-protection/ddos-protection.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/ddos-protection/ddos-protection.mdx @@ -8,7 +8,7 @@ permalink: /documentation/products/secure/firewall/ddos-protection/ import LinkButton from 'azion-webkit/linkbutton' -**DDoS Protection** is an [Firewall](/en/documentation/products/secure/edge-firewall/) add-on that protects your applications against *Denial of Service (DoS)* and *Distributed Denial of Service (DDoS)* attacks, at the network, transport, presentation, and application layers (layers 3, 4, 6, and 7 of the OSI model, respectively). +**DDoS Protection** is an [Firewall](/en/documentation/products/secure/firewall/) add-on that protects your applications against *Denial of Service (DoS)* and *Distributed Denial of Service (DDoS)* attacks, at the network, transport, presentation, and application layers (layers 3, 4, 6, and 7 of the OSI model, respectively). At Azion, DDoS Protection is **unmetered** and is automatically enabled in all accounts. It offers protection against DoS and DDoS attacks with unmetered bandwidth. This means that, no matter how much DDoS attack traffic is directed to your applications or the Azion infrastructure, the Azion dedicated network will guarantee that all services are constant and not affected by the attack. As it's unmetered, mitigation using this protection won't appear on *billing*. For more information regarding traffic accounting, see the [pricing](/en/documentation/products/pricing/) page. diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx index da55b7b2d2..a07af84b80 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx @@ -32,8 +32,8 @@ Azion also supports **Certificate Revocation List (CRL)** via [Azion API](https: | Scope | Resource | | --- | --- | -| About Domains | [Domains](/en/documentation/products/build/edge-application/domains/) | -| About mTLS | [mTLS](/en/documentation/products/secure/edge-firewall/mtls/) | +| About Domains | [Domains](/en/documentation/products/build/applications/domains/) | +| About mTLS | [mTLS](/en/documentation/products/secure/firewall/mtls/) | --- @@ -77,13 +77,13 @@ Smaller keys are less computationally intensive to generate signatures because t ### Trusted CA certificate -A Trusted CA is an entity that is authorized to issue digital certificates that can be used for the [Mutual Transport Layer Security (mTLS)](/en/documentation/products/secure/edge-firewall/mtls/) security protocol. You may upload Trusted CA certificates and intermediate certificates. +A Trusted CA is an entity that is authorized to issue digital certificates that can be used for the [Mutual Transport Layer Security (mTLS)](/en/documentation/products/secure/firewall/mtls/) security protocol. You may upload Trusted CA certificates and intermediate certificates. --- ## Let's Encrypt certificate -[Let's Encrypt](https://letsencrypt.org/)™ is a nonprofit global CA that allows people and organizations to obtain, renew, and manage TLS certificates for free. When [creating a Domain](/en/documentation/products/build/edge-application/domains/) with Azion, you may choose to obtain a TLS certificate signed by Let's Encrypt. You can request Let's Encrypt certificates for domains hosted in [Edge DNS](/en/documentation/products/secure/edge-dns/) or in a third-party DNS provider. +[Let's Encrypt](https://letsencrypt.org/)™ is a nonprofit global CA that allows people and organizations to obtain, renew, and manage TLS certificates for free. When [creating a Domain](/en/documentation/products/build/applications/domains/) with Azion, you may choose to obtain a TLS certificate signed by Let's Encrypt. You can request Let's Encrypt certificates for domains hosted in [Edge DNS](/en/documentation/products/secure/edge-dns/) or in a third-party DNS provider. Once you [create a domain with Azion](/en/documentation/products/guides/configure-a-domain/), you can choose the option **Let's Encrypt** to automatically generate a Let's Encrypt certificate. An entry for this certificate will be listed in the **Certificate Manager** page in [Azion Console](https://console.azion.com). After the certificate undergoes DNS validation, issuance, and storage, it'll become active. @@ -176,7 +176,7 @@ For more information about the API parameters, see the [Certificates API referen :::note[Note] Let's Encrypt certificates cross-signed by IdenTrust expired on September 30th, 2024. Devices and applications using the [Let's Encrypt certificate that used IdenTrust are now invalid](https://letsencrypt.org/2023/07/10/cross-sign-expiration.html). This could impact the functionality of devices and applications utilizing these certificates, mainly users of older Android devices (pre-7.1). It'll be necessary to take the following actions: -- **For users of Let's Encrypt Certificates with IdenTrust**: you must migrate to the new Let's Encrypt signing technology or an [Azion edge certificate](/en/documentation/products/build/edge-application/digital-certificates/#edge-certificate). +- **For users of Let's Encrypt Certificates with IdenTrust**: you must migrate to the new Let's Encrypt signing technology or an [Azion edge certificate](/en/documentation/products/build/applications/domains/mtls/#edge-certificate). - **For users of other types of Let's Encrypt**: no immediate action is necessary, considering other certificates remain unaffected with this update, since the problem is caused by outdated certificate chains on the device. - **For user with applications using Let's Encrypt on Azion**: no action needed. Certificates are automatically updated, although an affected device must have its CAs updated as well. ::: @@ -205,7 +205,7 @@ You'll need to inform: A **Certificate Revocation List (CRL)** is a list of digital certificates revoked before their expiration date. It works as a block list that you can add to your account to state those certificates can't be trusted. The issuing certificate authority (CA) signs this list to guarantee its security. -The CRL works when associated with an [mTLS CA Certificate](/en/documentation/products/secure/edge-firewall/mtls/). Therefore, you must have mTLS enabled in the domain you want to associate it with. +The CRL works when associated with an [mTLS CA Certificate](/en/documentation/products/secure/firewall/mtls/). Therefore, you must have mTLS enabled in the domain you want to associate it with. The CRL is automatically validated before the creation is successful in the Azion Web Platform. The management, including creation, of a CRL is available via [Azion API](https://api.azion.com/#b2df23ee-7a28-4900-9ad5-ffd135b4c6cf). 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 c91bfaf6f3..d9c9743502 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 @@ -34,14 +34,14 @@ For more details on the product's accounting, see the [pricing](/en/documentatio | Scope | Source | | ----- | ------ | -| Main settings | [How to configure main settings](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) | -| Update Firewall | [How to update your Firewall](/en/documentation/products/guides/how-to-update-your-edge-firewall/) | +| Main settings | [How to configure main settings](/en/documentation/products/guides/secure/firewall-configure-main-settings/) | +| Update Firewall | [How to update your Firewall](/en/documentation/products/guides/how-to-update-your-firewall/) | | Get to know Network Lists | [Network Lists](/en/documentation/products/secure/edge-firewall/network-layer-protection/network-lists/) | -| Get to know WAF Rule Sets | [WAF Rule Sets](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/) | -| 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 Certificate Manager | [Certificate Manager for Secure](/en/documentation/products/secure/edge-firewall/digital-certificates/) | +| Get to know WAF Rule Sets | [WAF Rule Sets](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/) | +| Get to know WAF Custom Allowed Rules | [WAF Custom Allowed Rules](/en/documentation/products/secure/firewall/web-application-firewall/custom-allowed-rules/) | +| Get to know Functions | [Functions Instances for Firewall](/en/documentation/products/secure/firewall/functions-instances/) | +| Get to know Rules Engine | [Rules Engine for Firewall](/en/documentation/products/secure/firewall/rules-engine/) | +| Get to know Certificate Manager | [Certificate Manager for Secure](/en/documentation/products/secure/firewall/certificate-manager/) | | 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/) | @@ -56,7 +56,7 @@ You can share the same firewall among all applications that adopt the same secur An firewall consists in an identification name, all your application domains where Firewall should be applied, what are the applied modules, and what are the security rules configured in the **Rules Engine** tab. - + :::note You need to activate at least one for the firewall to work. @@ -101,7 +101,7 @@ The **DDoS Protection** module protects your content and applications against *D - + ### Network Shield diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-firewall.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-firewall.mdx index c4914942fd..76b2831d08 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-firewall.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-firewall.mdx @@ -9,7 +9,7 @@ namespace: documentation_products_edge_functions_firewall permalink: /documentation/products/secure/firewall/functions/ --- -[Functions](/en/documentation/products/build/edge-application/edge-functions/) are functions that run on the Azion Web Platform with low latency, bringing the operational power closer to the end user. +[Functions](/en/documentation/products/build/applications/functions/) are functions that run on the Azion Web Platform with low latency, bringing the operational power closer to the end user. [Firewall](/en/documentation/products/secure/firewall/) supports functions. Through them you can write your own security source code in JavaScript and deploy it to run at the edge of the network. @@ -124,25 +124,25 @@ By using this metadata you're able to filter and manage the access to your appli You can deny access to your application when the request comes from certain places. -Find out more about the [GeoIP metadata list](/en/documentation/products/edge-application/edge-functions/runtime/api-reference/metadata/#geo-ip). +Find out more about the [GeoIP metadata list](/en/documentation/products/applications/functions/runtime/api-reference/metadata/#geo-ip). ### Remote You're able to check the IP address and the TCP port used. -Find out more about the [Remote metadata list](/en/documentation/products/edge-application/edge-functions/runtime/api-reference/metadata/#remote). +Find out more about the [Remote metadata list](/en/documentation/products/applications/functions/runtime/api-reference/metadata/#remote). ### Server You're able to check the protocol being used in the request. -Find out more about the [Server metadata list](/en/documentation/products/edge-application/edge-functions/runtime/api-reference/metadata/#server). +Find out more about the [Server metadata list](/en/documentation/products/applications/functions/runtime/api-reference/metadata/#server). ### TLS The TLS-related metadata is available when the request is made over a secure TLS connection. -Find out more about the [TLS metadata list](/en/documentation/products/edge-application/edge-functions/runtime/api-reference/metadata/#tls). +Find out more about the [TLS metadata list](/en/documentation/products/applications/functions/runtime/api-reference/metadata/#tls). --- diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-instances.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-instances.mdx index 0824511a85..fbf89bfcf9 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-instances.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/edge-functions-for-edge-firewall/edge-functions-instances.mdx @@ -103,7 +103,7 @@ In this example, `threshold` and `action` are overridden by the instance configu The **Args** field in **Functions Instance** supports a maximum of 100KB of arguments. ::: - + To associate an execution trigger, you simply need to associate the instance with a **Behavior** of a **Rules Engine** Rule, in Request. Thus, when a request meets the criteria defined in the **Rules Engine** rules, the **Function** will be invoked and executed directly on Azion's Edges Nodes. 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 1d5ab1aceb..f773846d18 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 @@ -56,7 +56,7 @@ If your application needs special access, it is necessary to configure a permiss You can also change and specify the *header variables* of your **mTLS** to meet Open Banking requirements. This can be done in the **Application** configuration page, within [Azion Console](https://console.azion.com). -> The list of accepted variables is available on the [Rules Engine for Application](/en/documentation/products/build/edge-application/rules-engine/) page. +> The list of accepted variables is available on the [Rules Engine for Application](/en/documentation/products/build/applications/rules-engine/) page. ## Limits diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx index 7b27744cbe..229bc9d2d0 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/network-layer-protection/network-layer-protection.mdx @@ -37,7 +37,7 @@ Advantages of using Azion's Network Shield: When activating the **Network Shield** module in the *Main Settings* of a **Firewall Rule Set**, the conditions (*criteria*) and commands (*behavior*) will be enabled in the **Rules Engine** tab of the firewall. :::tip -Learn more about [Firewall](/en/documentation/products/secure/edge-firewall/) configurations and [Rules Engine for Firewall](/en/documentation/products/secure/edge-firewall/rules-engine/). +Learn more about [Firewall](/en/documentation/products/secure/firewall/) configurations and [Rules Engine for Firewall](/en/documentation/products/secure/firewall/rules-engine/). ::: The *criteria* available with the activation of the Network Shield module are: @@ -66,7 +66,7 @@ Behavior: `[Then] [Deny (403 Forbidden)]`. In this example, requests originating from countries that are on the blocklist will be blocked unless the `User-Agent` header contains the string "Googlebot". :::note -The conditions and behaviors available in the Firewall Rules Engine tab depend on the activated modules. Learn more about [Firewall modules](/en/documentation/products/secure/edge-firewall/). +The conditions and behaviors available in the Firewall Rules Engine tab depend on the activated modules. Learn more about [Firewall modules](/en/documentation/products/secure/firewall/). ::: diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/rules-engine.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/rules-engine.mdx index 4a8617ef70..c9ef104a04 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/rules-engine.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/rules-engine.mdx @@ -27,7 +27,7 @@ You can use the Rules Engine for Firewall to configure all operational aspects o A firewall can have as many rules as needed. These rules are interchangeable, allowing you to share the same rule across all other firewalls. - + @@ -36,7 +36,7 @@ A firewall can have as many rules as needed. These rules are interchangeable, al | Scope | Resource | | --- | --- | | Secure an application | [How to secure an application](/en/documentation/products/secure/secure-application/) | -| Configuring main settings | [How to configure Firewall main settings](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) | +| Configuring main settings | [How to configure Firewall main settings](/en/documentation/products/guides/secure/firewall-configure-main-settings/) | | Creating a WAF rule set | [How to create a WAF rule set](/en/documentation/products/guides/secure/create-waf-rule-set/) | | Blocking Tor exit node IP addresses | [How to block Tor exit node IP addresses](/en/documentation/products/guides/secure/block-tor-networks/) | @@ -53,7 +53,7 @@ The processing of the rules is sequential and you can use them as a powerful set :::note A firewall is composed of several key components that define its functionality and operation. While configuring a firewall, you can define its main settings, including: a **Name**, the **Domains** that will be secured by the firewall, and the **Modules** that will be used to extend the usability of **Rules Engine**, as well as enable the **Debug Rules** feature. -After that, you'll be able to add [Functions Instances](/en/documentation/products/secure/edge-firewall/edge-functions-instances/) and **Rules Engine** rules. The fields and requirements to use **Rules Engine for Firewall** are explained in the sections below. +After that, you'll be able to add [Functions Instances](/en/documentation/products/secure/firewall/functions-instances/) and **Rules Engine** rules. The fields and requirements to use **Rules Engine for Firewall** are explained in the sections below. ::: --- @@ -88,7 +88,7 @@ For example, this criteria identifies requests where the URI starts with a forwa | If | `Request URI` | *starts with* | `/` | :::note -The availability of certain criteria depends on the enabled modules of your Firewall. Go to the [Firewall modules reference](/en/documentation/products/secure/edge-firewall/#about-edge-firewall-modules) for more details. +The availability of certain criteria depends on the enabled modules of your Firewall. Go to the [Firewall modules reference](/en/documentation/products/secure/firewall/#about-edge-firewall-modules) for more details. ::: ### Variables @@ -182,7 +182,7 @@ The `Maximum Burst size` is only available for the `Req/s` (request per second). Requires WAF -It associates the WAF Rule Set to be used in the request. WAF policies must be previously configured in **Edge Libraries** > **WAF Rules**. You must also define the **WAF mode**: **Learning** or **Blocking**. Read more on [WAF Rule Sets](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/). +It associates the WAF Rule Set to be used in the request. WAF policies must be previously configured in **Edge Libraries** > **WAF Rules**. You must also define the **WAF mode**: **Learning** or **Blocking**. Read more on [WAF Rule Sets](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/). :::caution[Warning] Azion platform maintains only one `Set WAF Rule Set` behavior configuration for each criteria logic. If you have two different firewalls configured with the same criteria logic but different `Set WAF Rule Set` behaviors, only the most recent one will be processed. This can be useful in case your application needs constant switching between two or more behaviors for the same criteria. @@ -192,7 +192,7 @@ Azion platform maintains only one `Set WAF Rule Set` behavior configuration for Requires Functions -It runs a function specified as a parameter. The function must have been previously [instantiated and parameterized](/en/documentation/products/guides/secure/instantiate-edge-functions/) in the Functions tab in order to be used. +It runs a function specified as a parameter. The function must have been previously [instantiated and parameterized](/en/documentation/products/guides/secure/instantiate-functions/) in the Functions tab in order to be used. ### Set Custom Response diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx index 9a397970f0..1ab6e93459 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx @@ -18,7 +18,7 @@ WAF operates in the seventh layer of the OSI model, the application layer, where **Web Application Firewall** is based on requests *scoring* methodology. Each HTTP/HTTPS request is compared to a very strict and detailed set of application standards and given a *score* that is associated with a particular family of threats. According to the *score* received by the request, it can be released or blocked directly in Azion's edge nodes, before the threat reaches its origin or causes any type of damage. You define the desired level of sensitivity for blocking each family of threats. -WAF can operate in two modes: **Learning** or **Blocking**. You can set the mode in a rule in [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) with the **Set WAF Rule Set** behavior or via [Azion API](https://api.azion.com/#ace1b2f6-253a-48a1-bf58-4c5381e22c21). +WAF can operate in two modes: **Learning** or **Blocking**. You can set the mode in a rule in [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) with the **Set WAF Rule Set** behavior or via [Azion API](https://api.azion.com/#ace1b2f6-253a-48a1-bf58-4c5381e22c21). You can use the **Learning** mode to avoid blocking lawful requests and malfunctions of your application. In this step, WAF identifies the legitimate behaviors of your application by placing them in an *allowlist*. @@ -54,7 +54,7 @@ Learn more about [Firewall modules](/en/documentation/products/secure/firewall/) ::: - + ## WAF Main Settings @@ -62,7 +62,7 @@ The **Main Settings** section is configured by activating protection against spe The **Threat Type Configuration** table categorizes threats into families, according to the purpose of the attack. -

+

@@ -72,7 +72,7 @@ It's possible to enable and disable protection for each threat family individual Each sensitivity level tolerates a defined number of threat indicatives and the WAF score represents this amount of threat indicatives. The more flexible the sensitivity level is, the higher the WAF score it accepts. The most rigid sensitivity levels, on the other hand, only accept requests with fewer signs of threats. - + ## WAF Rule IDs @@ -80,7 +80,7 @@ Each WAF rule has a unique numeric identifier, called `Rule ID`. - **Visibility:** the `Rule IDs` appear on the **WAF Tuning** and **Allowed Rules** screens. - **Usage:** you can use the `Rule ID` to identify, filter, and allow/block specific behaviors of your application. -- **Full list:** see the description of rule families and their `Rule IDs` in [WAF Rule Sets](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/). +- **Full list:** see the description of rule families and their `Rule IDs` in [WAF Rule Sets](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/). ### Rule 13: POST format validation @@ -97,7 +97,7 @@ To understand the expected formats and the semantics of `POST` requests, see: - [RFC 7231 – Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content](https://datatracker.ietf.org/doc/html/rfc7231) - [RFC 2388 – Returning Values from Forms: multipart/form-data](https://datatracker.ietf.org/doc/html/rfc2388) -You can find the detailed description of Rule 13 and its parameters on the [WAF Rule Sets](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/) page. +You can find the detailed description of Rule 13 and its parameters on the [WAF Rule Sets](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/) page. ## WAF Tuning @@ -124,7 +124,7 @@ The Allowed Rules are composed of the fields: | Field | Description | | ----- | ----------- | -| `Rule ID` | Unique numeric ID of a WAF Rule. See the list of rules in [WAF Rule Sets](/en/documentation/products/secure/edge-firewall/web-application-firewall/rules-set/). | +| `Rule ID` | Unique numeric ID of a WAF Rule. See the list of rules in [WAF Rule Sets](/en/documentation/products/secure/firewall/web-application-firewall/rules-set/). | | `Rule Description` | Automatic textual description of what the rule is/does | | `Reason` | Alternative manual textual description | | `URI` | *Uniform Resource Identifier (URI)* is the path that goes after the domain in the URL | diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/wildcard-lets-encrypt-certificates.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/wildcard-lets-encrypt-certificates.mdx index 6267fb427e..25dc0c4df7 100644 --- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/wildcard-lets-encrypt-certificates.mdx +++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/wildcard-lets-encrypt-certificates.mdx @@ -93,7 +93,7 @@ By centralizing wildcard certificate issuance and management, the platform minim Integration with Azion's management environment enables certificates to be easily associated with customer domains and subdomains, maintaining consistency and compliance with security policies. - + --- 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 847a33cce5..aa91ec5a31 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 @@ -13,7 +13,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' :::note -This page documents the new Workloads product. If your account hasn't been migrated yet, refer to the [legacy Domains reference](/en/documentation/products/build/edge-application/domains/). +This page documents the new Workloads product. If your account hasn't been migrated yet, refer to the [legacy Domains reference](/en/documentation/products/build/applications/domains/). ::: **Workloads** is an [Azion Console](https://console.azion.com) feature that centralizes communication protocol settings, such as certificates, domains, ports and protocols. @@ -28,7 +28,7 @@ You may also bind a **Digital Certificate** to your workload to enable HTTPS/TLS | --- | --- | | Adding a custom domain | [Getting started](/en/documentation/products/guides/configure-a-domain/) | | About Certificate Manager | [Certificate Manager](/en/documentation/products/secure/firewall/certificate-manager/) | -| About mTLS | [mTLS](/en/documentation/products/secure/edge-firewall/mtls/) | +| About mTLS | [mTLS](/en/documentation/products/secure/firewall/mtls/) | --- @@ -42,7 +42,7 @@ With this setting you can control where your configuration will be deployed whil Select the infrastructure type for your workload. Once this option is saved, it cannot be modified. :::tip -The local `etc/hosts` file maps IP addresses to domains. When you [associate the edge node IP with the CNAME](/en/documentation/products/guides/stage-edge-application-through-hosts-file/) assigned to your domain in your `hosts` file, you force your computer's DNS resolution to access this domain through the edge node and not through public DNS servers. This way, you can stage your application locally as if it were already deployed on your custom domain on the edge before you [point your domain](/en/documentation/products/guides/point-domain-to-azion/) to Azion. +The local `etc/hosts` file maps IP addresses to domains. When you [associate the edge node IP with the CNAME](/en/documentation/products/guides/stage-applications-through-hosts-file/) assigned to your domain in your `hosts` file, you force your computer's DNS resolution to access this domain through the edge node and not through public DNS servers. This way, you can stage your application locally as if it were already deployed on your custom domain on the edge before you [point your domain](/en/documentation/products/guides/point-domain-to-azion/) to Azion. ::: --- ## Domains @@ -62,7 +62,7 @@ You may allow access to the self-generated workload domain after creating a work --- ## Deployment Settings -Configure your workload deployment by selecting an [Application](/en/documentation/products/build/edge-application/) and an [Firewall](/en/documentation/products/secure/firewall/). You can also set up [Custom Pages](/en/documentation/products/secure/custom-pages/) to handle errors and configure cache time-to-live (TTL) settings based on the HTTP status code returned from the edge connectors. +Configure your workload deployment by selecting an [Application](/en/documentation/products/build/applications/) and an [Firewall](/en/documentation/products/secure/firewall/). You can also set up [Custom Pages](/en/documentation/products/secure/custom-pages/) to handle errors and configure cache time-to-live (TTL) settings based on the HTTP status code returned from the edge connectors. A Workload Deployment is a configuration that ties **Application** (mandatory), **Firewall** and **Custom Pages** together for your application. diff --git a/src/content/docs/en/pages/main-menu/reference/services/support/technical-support.mdx b/src/content/docs/en/pages/main-menu/reference/services/support/technical-support.mdx index 0594a845ff..e27d571933 100644 --- a/src/content/docs/en/pages/main-menu/reference/services/support/technical-support.mdx +++ b/src/content/docs/en/pages/main-menu/reference/services/support/technical-support.mdx @@ -83,7 +83,7 @@ The table below describes the severity options for tickets of the **Request** ty | General Guidance | You have a general request for the Azion Web Platform. | | New Feature | You want to request a feature. | | Solutions Labs | You want to request the assistance of a specialist to propose a new solution. | -| CNAMEs already in use | You have encountered the error *CNAMEs already in use* when listing a CNAME in one of your [Azion domains](/en/documentation/products/build/edge-application/domains/). | +| CNAMEs already in use | You have encountered the error *CNAMEs already in use* when listing a CNAME in one of your [Azion domains](/en/documentation/products/build/applications/domains/). | | Integration Services | You want to request [Integration Services](/en/documentation/services/integration-services/) initiate a new integration with Azion. | | Template (Preview) | You need a new [Template](/en/documentation/products/marketplace/templates/) to be added to the Azion Marketplace. | @@ -94,7 +94,7 @@ The table below describes the severity options for tickets of the **Question** t | Severity | Definition | | -------- | ---------- | | General Guidance | You have a question about the Azion Platform. | -| Rules Engine | You have questions about how to set up a behavior using [Rules Engine for Applications](/en/documentation/products/build/edge-application/rules-engine/) or [Rules Engine for Firewall](/en/documentation/products/secure/edge-firewall/rules-engine/). | +| Rules Engine | You have questions about how to set up a behavior using [Rules Engine for Applications](/en/documentation/products/build/applications/rules-engine/) or [Rules Engine for Firewall](/en/documentation/products/secure/firewall/rules-engine/). | ## Severity of cases and response times according to service plans diff --git a/src/content/docs/en/pages/main-menu/reference/store/edge-sql/edge-sql.mdx b/src/content/docs/en/pages/main-menu/reference/store/edge-sql/edge-sql.mdx index 0e06c57875..a6da59def9 100644 --- a/src/content/docs/en/pages/main-menu/reference/store/edge-sql/edge-sql.mdx +++ b/src/content/docs/en/pages/main-menu/reference/store/edge-sql/edge-sql.mdx @@ -30,11 +30,11 @@ There are two ways to build a database through SQL Database: using the SQL Datab | Scope | Resource | | ----- | -------- | -| Manage databases with REST API | [How to create an SQL Database database](/en/documentation/products/guides/manage-databases-edge-sql/) | -| Create queries with REST API | [How to create and query data on SQL Database](/en/documentation/products/guides/create-tables-edge-sql/) | -| Retrieve data from a database | [How to retrieve data from a database with SQL Database and Functions](/en/documentation/products/guides/edge-sql/retrieve-data-with-edge-functions/) | +| Manage databases with REST API | [How to create an SQL Database database](/en/documentation/products/guides/manage-sql-database/) | +| Create queries with REST API | [How to create and query data on SQL Database](/en/documentation/products/guides/create-tables-sql-database/) | +| Retrieve data from a database | [How to retrieve data from a database with SQL Database and Functions](/en/documentation/products/guides/edge-sql/retrieve-data-with-functions/) | | Get to know SQL Database Vector Search | [SQL Database Vector Search reference](/en/documentation/products/store/sql-database/vector-search/) | -| Import data to SQL Database | [How to import data guide ](/en/documentation/products/guides/import-data-edge-sql/) | +| Import data to SQL Database | [How to import data guide ](/en/documentation/products/guides/import-data-sql-database/) | --- @@ -66,7 +66,7 @@ With a distributed architecture running across Azion's edge nodes, SQL Database A database is a set of structured tables that allow to write and read data in SQL language. Organized in columns and rows, users are able to add data logically, with columns representing specific information in the vertical axis, while rows represent individual entry data, related to a column, in the horizontal axis. -[Creating a database](/en/documentation/products/guides/manage-databases-edge-sql/) is the first step to use SQL Database and add data: +[Creating a database](/en/documentation/products/guides/manage-sql-database/) is the first step to use SQL Database and add data: ```bash curl --location 'https://api.azion.com/v4/edge_sql/databases' \ @@ -124,7 +124,7 @@ You can interact with SQL Database directly from your terminal using [the edgesq Check the documentation below for details on how to install and use EdgeSQL Shell. - + Learn how to master SQL Database via Terminal. Watch the video below:
diff --git a/src/content/docs/en/pages/main-menu/reference/store/edge-sql/vector-search.mdx b/src/content/docs/en/pages/main-menu/reference/store/edge-sql/vector-search.mdx index d834365b76..c717e43127 100644 --- a/src/content/docs/en/pages/main-menu/reference/store/edge-sql/vector-search.mdx +++ b/src/content/docs/en/pages/main-menu/reference/store/edge-sql/vector-search.mdx @@ -26,7 +26,7 @@ Distributed across the Azion global edge network, this feature enables more rele | Scope | Resource | |---|---| -| Implement Vector Search | Guide explaining the basics of [implementing Vector Search](/en/documentation/products/guides/edge-sql-vector-search/) | +| Implement Vector Search | Guide explaining the basics of [implementing Vector Search](/en/documentation/products/guides/sql-database-vector-search/) | | Get to know Azion SQL Database and its features | [SQL Database reference](/en/documentation/products/store/sql-database/) | | Integrate with AI Inference | Learn about [AI Inference capabilities](/en/documentation/products/ai/ai-inference/) | diff --git a/src/content/docs/en/pages/main-menu/reference/store/object-storage/index.mdx b/src/content/docs/en/pages/main-menu/reference/store/object-storage/index.mdx index f7e1800a86..05525ce021 100644 --- a/src/content/docs/en/pages/main-menu/reference/store/object-storage/index.mdx +++ b/src/content/docs/en/pages/main-menu/reference/store/object-storage/index.mdx @@ -26,7 +26,7 @@ This product is available through [Console](https://console.azion.com/object-sto | Manage a bucket | [How to create and modify an Object Storage bucket](/en/documentation/products/guides/create-and-modify-bucket/) | | Upload and download objects | [How to upload and download objects from an Object Storage bucket](/en/documentation/products/guides/upload-and-download-objects-from-bucket/) | | Use bucket as origin | [How to use an Object Storage bucket as the origin of a static application](/en/documentation/products/store/storage/use-bucket-as-origin/) | -| Set up the S3 protocol | [How to access an Object Storage bucket using the S3 protocol](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/) | +| Set up the S3 protocol | [How to access an Object Storage bucket using the S3 protocol](/en/documentation/products/store/storage/s3-protocol-for-object-storage/) | | Runtime API | [Object Storage API](/en/documentation/runtime/api-reference/storage/) | --- @@ -75,7 +75,7 @@ When creating an Object Storage origin, you can set a prefix to serve to the edg ### Origin -With **Object Storage**, you can use buckets as an [origin](/en/documentation/products/secure/connector/#connector-type) in Azion **Connectors** to retrieve the content of an application. +With **Object Storage**, you can use buckets as an [origin](/en/documentation/products/secure/connectors/#connector-type) in Azion **Connectors** to retrieve the content of an application. You can determine if the content is retrieved from the root of the bucket or from a prefix within the bucket. @@ -201,7 +201,7 @@ Class C operations are free. If an operation falls out of the scope of class C o > If `listBuckets` is enabled, when attempting to retrieve files that aren't in the bucket using an S3 credential, the proper `404 Not Found` status response returns instead of a `403 Forbidden` status. Find out more about S3 capabilities in [S3 protocol compatibility](#s3-protocol-compatibility). -Read more on [How to access Object Storage using the S3 protocol](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/). +Read more on [How to access Object Storage using the S3 protocol](/en/documentation/products/store/storage/s3-protocol-for-object-storage/). #### ListBuckets @@ -345,7 +345,7 @@ When a bucket is configured with **read-write permissions**, any user can access Credentials can be created for any bucket that you own or for your account as a whole to manage all your buckets. With them, you can control permissions for operations associated with that credential. The permissions for the credential are exclusive to access through the S3 protocol. -To [create a S3 credential](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/), you must use an Azion personal token and run a `POST` request via API. However, after the credential is created, it works independently from your Azion token. This way, even if the token expires, the credential remains valid. +To [create a S3 credential](/en/documentation/products/store/storage/s3-protocol-for-object-storage/), you must use an Azion personal token and run a `POST` request via API. However, after the credential is created, it works independently from your Azion token. This way, even if the token expires, the credential remains valid. Once a credential is created, an *access key* and a *secret key* are generated, which can be used to set up access to the bucket through the S3 protocol. For security reasons, the *secret key* won't be available after the credential is created. Existing credentials can't be modified in any way. @@ -372,7 +372,7 @@ The S3 protocol allows you to access buckets and objects using an Object Storage You can use the access and secret keys provided by the [S3 credentials API](https://api.azion.com) to set up a connection using the S3 protocol. - + To do so, you'll need the following information: diff --git a/src/content/docs/en/pages/main-menu/release-notes/release-notes.mdx b/src/content/docs/en/pages/main-menu/release-notes/release-notes.mdx index e3e11ffb14..e6895b4d2c 100644 --- a/src/content/docs/en/pages/main-menu/release-notes/release-notes.mdx +++ b/src/content/docs/en/pages/main-menu/release-notes/release-notes.mdx @@ -209,7 +209,7 @@ Sync command fix aligned with API page size maximum (100 items). Fixed an issue that blocked Let's Encrypt certificate issuance during domain creation. -Read more about [Azion CLI](/en/documentation/products/azion-cli/overview/) and [Let's Encrypt certificates](/en/documentation/products/secure/edge-firewall/digital-certificates/#lets-encrypt-certificate). +Read more about [Azion CLI](/en/documentation/products/azion-cli/overview/) and [Let's Encrypt certificates](/en/documentation/products/secure/firewall/certificate-manager/#lets-encrypt-certificate). --- @@ -451,7 +451,7 @@ Activating the new engine may cause temporary changes in bot classification patt Until you update your JSON Args, Bot Manager will continue using the previous fingerprinting engine. ::: -For complete configuration details, please refer to the [Bot Manager documentation](/en/documentation/products/secure/edge-firewall/bot-manager/). +For complete configuration details, please refer to the [Bot Manager documentation](/en/documentation/products/secure/firewall/bot-manager/). ## July 9, 2025 @@ -503,7 +503,7 @@ JavaScript ES Module Support Edge Functions now supports JavaScript modules. Making it easier than ever for you to bring your JavaScript applications to the Azion Web Platform. -Visit the [handlers](/en/documentation/products/edge-application/edge-functions/runtime/api-reference/handlers/) documentation for more details. +Visit the [handlers](/en/documentation/products/applications/functions/runtime/api-reference/handlers/) documentation for more details. ## May 15, 2025 @@ -515,11 +515,11 @@ Visit the [handlers](/en/documentation/products/edge-application/edge-functions/ ### Let’s Encrypt HTTP-01 Challenge through API -Azion now offers API-based issuance and renewal of [Let’s Encrypt certificates](https://www.azion.com/en/documentation/products/secure/edge-firewall/digital-certificates/#lets-encrypt-certificate) using the HTTP-01 challenge, providing a streamlined process with no need for DNS TXT records. This offers a straightforward and convenient integration solution, particularly beneficial for customers managing numerous domains and hostnames. +Azion now offers API-based issuance and renewal of [Let’s Encrypt certificates](https://www.azion.com/en/documentation/products/secure/firewall/certificate-manager/#lets-encrypt-certificate) using the HTTP-01 challenge, providing a streamlined process with no need for DNS TXT records. This offers a straightforward and convenient integration solution, particularly beneficial for customers managing numerous domains and hostnames. Certificates auto-renew before expiring, removing maintenance windows, and maintaining existing quotas, billing, and permissions. Perfect for ecommerce platforms and hosting providers, this enhancement enables faster onboarding and secures customer sites in minutes without DNS changes. -For more information on these updates, [visit the Digital Certificates documentation](https://www.azion.com/en/documentation/products/secure/edge-firewall/digital-certificates/#lets-encrypt-certificate). +For more information on these updates, [visit the Digital Certificates documentation](https://www.azion.com/en/documentation/products/secure/firewall/certificate-manager/#lets-encrypt-certificate). ## May 7, 2025 @@ -576,7 +576,7 @@ Azion introduces several new Artificial Intelligence capabilities, including **A - **LangGraph AI Agent Boilerplate**: Template to create an agent that can query and interact with data stored in EdgeSQL databases. - **Compatibility**: Integrates with OpenAI-compatible APIs and LangChain/LangGraph for workflow automation. -For more details, visit the documentation for [AI Inference](/en/documentation/products/ai/ai-inference/), [Edge Functions](/en/documentation/products/build/edge-application/edge-functions/), and [Edge SQL](/en/documentation/products/store/edge-sql/). +For more details, visit the documentation for [AI Inference](/en/documentation/products/ai/ai-inference/), [Edge Functions](/en/documentation/products/build/applications/functions/), and [Edge SQL](/en/documentation/products/store/sql-database/). ## March 26, 2025 @@ -676,7 +676,7 @@ Example: `user/logs/2024/10/12/06/24/37d66e78-c308-4006-9d4d-1c013ed89276`. This structure simplifies log management and monitoring by enabling precise searches and filtering using the date, time, and UUID. -Read more on [Data Stream](/en/documentation/products/observe/data-stream/) and how to configure [Object Storage](/en/documentation/products/guides/connector-azion-edge-storage/) and [Amazon S3](/en/documentation/products/guides/endpoint-amazon-s3/) connectors to receive data. +Read more on [Data Stream](/en/documentation/products/observe/data-stream/) and how to configure [Object Storage](/en/documentation/products/guides/connector-azion-object-storage/) and [Amazon S3](/en/documentation/products/guides/endpoint-amazon-s3/) connectors to receive data. --- @@ -720,7 +720,7 @@ Learn more about [Data Stream](/en/documentation/products/observe/data-stream/) **Vector Search** is a new **Azion Edge SQL** feature that enables customers to implement semantic search engines for various use cases, resulting in more relevant search results, real-time recommendations, and insights while drastically reducing latency and improving user satisfaction. -Get to know Edge SQL Vector Search by reading the [documentation](/en/documentation/products/store/edge-sql/vector-search/). +Get to know Edge SQL Vector Search by reading the [documentation](/en/documentation/products/store/sql-database/vector-search/). --- @@ -750,7 +750,7 @@ Check on [Metrics' monitoring charts](/en/documentation/products/observe/real-ti **Azion Copilot** is an AI-powered assistant integrated directly into Azion Console. Customers can use it to resolve issues or get answers to queries, with immediate, context-driven responses based on Azion’s knowledge base. This new capability simplifies tasks for users of all skill levels, making it easier to use Azion's products and improving their workflow. -Additionally, Copilot runs directly on Azion's distributed edge platform, ensuring fast processing and leveraging edge-native products, such as [Edge Application](/en/documentation/products/build/edge-application/), [Edge Functions](/en/documentation/products/build/edge-application/edge-functions/), and [EdgeSQL](/en/documentation/products/store/edge-sql/), for optimal performance. +Additionally, Copilot runs directly on Azion's distributed edge platform, ensuring fast processing and leveraging edge-native products, such as [Edge Application](/en/documentation/products/build/applications/), [Edge Functions](/en/documentation/products/build/applications/functions/), and [EdgeSQL](/en/documentation/products/store/sql-database/), for optimal performance. To test the new Azion Copilot, access [Azion Console](https://console.azion.com/). @@ -853,7 +853,7 @@ Read more on this topic in the [documentation](/en/documentation/products/guides The **Image Processor** module can now process images in the `AVIF` format, which provides superior compression and quality compared to other formats like WEPB, JPEG or PNG. -Read more about [Image Processor](/en/documentation/products/build/edge-application/image-processor/). +Read more about [Image Processor](/en/documentation/products/build/applications/image-processor/). --- @@ -882,7 +882,7 @@ Read more about [GraphQL API](/en/documentation/devtools/graphql-api/overview/) Azion **Edge SQL REST API** is now available in **Preview**. This API allows you to create, read, update, delete, and list **Edge SQL** databases, a database product, distributed on the edge, fully ACID compliant, and using the SQLite dialect. -Get to know more about [Azion Edge SQL](https://www.azion.com/en/documentation/products/store/edge-sql/) and the [Edge SQL API](https://api.azion.com/#2b0cbfe6-50ee-4858-8fbe-e8072d01518b). +Get to know more about [Azion Edge SQL](https://www.azion.com/en/documentation/products/store/sql-database/) and the [Edge SQL API](https://api.azion.com/#2b0cbfe6-50ee-4858-8fbe-e8072d01518b). --- @@ -1021,7 +1021,7 @@ No changes have been made to the functionality of the products. **Digital Certificates** now supports the management of **Certificate Revocation Lists (CRL)** through Azion API. CRL is a list of digital certificates revoked before their expiration date. -Use the [Azion API](https://api.azion.com/#b2df23ee-7a28-4900-9ad5-ffd135b4c6cf) to manage CRLs and see the [Digital Certificates reference](/en/documentation/products/secure/edge-firewall/digital-certificates/#certificate-revocation-list-crl) for more information. +Use the [Azion API](https://api.azion.com/#b2df23ee-7a28-4900-9ad5-ffd135b4c6cf) to manage CRLs and see the [Digital Certificates reference](/en/documentation/products/secure/firewall/certificate-manager/#certificate-revocation-list-crl) for more information. --- @@ -1261,7 +1261,7 @@ Get to know more about [Azion CLI](/en/documentation/products/azion-cli/overview **Customizable Edge Firewall HTTP return code** is in **General Availability**. Now you can set a specific return (status code, content type, and content body) as an Edge Firewall Rules Engine behavior, using SSL status. -Visit the [documentation](/en/documentation/products/secure/edge-firewall/rules-engine/#behaviors) for further details. +Visit the [documentation](/en/documentation/products/secure/firewall/rules-engine/#behaviors) for further details. --- @@ -1291,7 +1291,7 @@ Get to know [Azion Service Plans](https://www.azion.com/en/professional-services You can now use the new behavior **Set Custom Response**, allowing you to customize HTTP headers and status codes. -Read more in the [documentation](/en/documentation/products/secure/edge-firewall/rules-engine/#behaviors). +Read more in the [documentation](/en/documentation/products/secure/firewall/rules-engine/#behaviors). --- @@ -1309,13 +1309,13 @@ HTTP/3 support is now compatible with all TLS versions supported by **Edge Appli You can now insert variables created with **Capture Match Groups** in the **Add Request Header** behavior argument. -Check the [Capture Match Groups](/en/documentation/products/build/edge-application/rules-engine/#capture-match-groups) documentation for more details. +Check the [Capture Match Groups](/en/documentation/products/build/applications/rules-engine/#capture-match-groups) documentation for more details. **Websocket** The Websocket module is now in **General Availability**. This module for Edge Application allows you to establish the WebSocket communication protocol between your origin and your users under the reverse proxy architecture. -Go to the Websocket [documentation](/en/documentation/products/build/edge-application/websocket/) to learn more about the requirements, specifications, and limits. +Go to the Websocket [documentation](/en/documentation/products/build/applications/websocket/) to learn more about the requirements, specifications, and limits. > At the moment, this module is exclusively accessible to subscribers of the **Enterprise** and **Mission Critical** Service Plans. Contact the [Support team](https://tickets.azion.com/en/support/loginen/support/login/new) to request access to this module. @@ -1323,7 +1323,7 @@ Go to the Websocket [documentation](/en/documentation/products/build/edge-applic **DDoS Protection** is now automatically enabled in all accounts. It offers protection against DoS and DDoS attacks with unmetered bandwidth for all Azion customers. -Get to know more about [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/). +Get to know more about [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/). --- @@ -1380,22 +1380,22 @@ For more details, check the documentation on [How to integrate Azion with Grafan **Edge Application** -- [Rules Engine](/en/documentation/products/build/edge-application/rules-engine/) now provides a **description** field for you to describe your rule. +- [Rules Engine](/en/documentation/products/build/applications/rules-engine/) now provides a **description** field for you to describe your rule. - You can customize the description via [Real-Time Manager](https://console.azion.com) or [Azion API](https://api.azion.com/). -- For Azion [Domains](/en/documentation/products/build/edge-application/domains/), you can request the issuance of a [Let's Encrypt certificate](/en/documentation/products/secure/edge-firewall/digital-certificates/#lets-encrypt-certificate) through Azion. +- For Azion [Domains](/en/documentation/products/build/applications/domains/), you can request the issuance of a [Let's Encrypt certificate](/en/documentation/products/secure/firewall/certificate-manager/#lets-encrypt-certificate) through Azion. - This TLS certificate will be automatically managed and renewed by Azion before the expiration date of 90 days. - See the guide on [How to generate a Let's Encrypt certificate](/en/documentation/products/guides/how-to-generate-a-lets-encrypt-certificate/) for more information. - Available in [Real-Time Manager](https://console.azion.com) or [Azion API](https://api.azion.com/). **Edge Functions** -- New [Edge Functions Code Editor](/en/documentation/products/edge-application/edge-functions/runtime-api/code-editor/) with [Azion Preview Deployment](/en/documentation/products/edge-application/edge-functions/runtime-api/preview-deployment/) and [integration with generative AI](/en/documentation/products/edge-application/edge-functions/runtime-api/ai-integration/). +- New [Edge Functions Code Editor](/en/documentation/products/applications/functions/runtime-api/code-editor/) with [Azion Preview Deployment](/en/documentation/products/applications/functions/runtime-api/preview-deployment/) and [integration with generative AI](/en/documentation/products/applications/functions/runtime-api/ai-integration/). - See the guide [How to build an API with Edge Functions and ChatGPT ](/en/documentation/products/guides/edge-functions/api-builder/) to know more about this feature. - Available in [Real-Time Manager](https://console.azion.com). -- New Azion [Network List interface](/en/documentation/products/edge-application/edge-functions/runtime/api-reference/network-list/), which enables access to [Network Lists](/en/documentation/products/secure/edge-firewall/network-layer-protection/network-lists/) and informs you if the list contains a specific IP address. +- New Azion [Network List interface](/en/documentation/products/applications/functions/runtime/api-reference/network-list/), which enables access to [Network Lists](/en/documentation/products/secure/edge-firewall/network-layer-protection/network-lists/) and informs you if the list contains a specific IP address. **GraphQL API** @@ -1461,7 +1461,7 @@ For more details, check the documentation on [How to integrate Azion with Grafan - Users can now choose between multiple `HTTP` and `HTTPS` ports available for simultaneous application delivery using: - [Real-Time Manager](https://console.azion.com). - [Azion API for Edge Application](https://api.azion.com/). -See the [Edge Application documentation](/en/documentation/products/build/edge-application/) for more information about it. +See the [Edge Application documentation](/en/documentation/products/build/applications/) for more information about it. - Ciphers - Users can now choose the cipher suite (encryption algorithms used, in this case, for a more secure data transmission between client and server) that their edge applications will use. diff --git a/src/content/docs/en/pages/main-menu/work-with-domains/configure-domains.mdx b/src/content/docs/en/pages/main-menu/work-with-domains/configure-domains.mdx index 5c972ea938..197763f585 100644 --- a/src/content/docs/en/pages/main-menu/work-with-domains/configure-domains.mdx +++ b/src/content/docs/en/pages/main-menu/work-with-domains/configure-domains.mdx @@ -17,7 +17,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' With Azion, you can create and run applications directly at the edge. To allow access to your application through the browser and start receiving users and monitoring metrics, you need to configure a domain. -To create a free domain address for your application in the format `xxxxxxxxxx.map.azionedge.net`, follow the steps in the appropriate tab below. There are separate instructions for the [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. +To create a free domain address for your application in the format `xxxxxxxxxx.map.azionedge.net`, follow the steps in the appropriate tab below. There are separate instructions for the [legacy Domains](/en/documentation/products/build/applications/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip In this guide, there are separate instructions for API v3 and API v4. If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. 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 09d3e9b368..7a0f2d5945 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 @@ -15,7 +15,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' -If your application runs on HTTPS, you'll need to register a certificate with Azion [Certificate Manager](/en/documentation/products/secure/edge-firewall/digital-certificates/). A TLS digital certificate confirms a website's identity and protects data transfers. It secures financial transactions and any exchange of sensitive information, from login credentials to personal data. +If your application runs on HTTPS, you'll need to register a certificate with Azion [Certificate Manager](/en/documentation/products/secure/firewall/certificate-manager/). A TLS digital certificate confirms a website's identity and protects data transfers. It secures financial transactions and any exchange of sensitive information, from login credentials to personal data. You can also request that a **Let's Encrypt certificate** be generated for your domain through Azion. The process for requesting a Let's Encrypt certificate is different from custom certificates. See [how to generate a Let's Encrypt certificate](/en/documentation/products/guides/how-to-generate-a-lets-encrypt-certificate/) for more information. @@ -24,7 +24,7 @@ You can also request that a **Let's Encrypt certificate** be generated for your - Don't have a digital certificate? Check the guide on [How to acquire and register a Digital Certificate with Azion](/en/documentation/products/guides/secure/digital-certificates/). ::: -There are separate instructions for the [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. +There are separate instructions for the [legacy Domains](/en/documentation/products/build/applications/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip In this guide, there are separate instructions for API v3 and API v4. If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx b/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx index ce255ad201..4b8488a208 100644 --- a/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx +++ b/src/content/docs/en/pages/main-menu/work-with-domains/point-domain.mdx @@ -17,9 +17,9 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' If you already own a domain, you can associate your domain CNAME entries to your Azion Workload address effectively directing access to your application. -There are separate instructions for the [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. +There are separate instructions for the [legacy Domains](/en/documentation/products/build/applications/domains/) settings and the new [Workloads](/en/documentation/products/secure/workloads) product. -Before you point your traffic to Azion, you can test your custom domain on the edge locally by [staging your application through the hosts file](/en/documentation/products/guides/stage-edge-application-through-hosts-file/). +Before you point your traffic to Azion, you can test your custom domain on the edge locally by [staging your application through the hosts file](/en/documentation/products/guides/stage-applications-through-hosts-file/). :::note This process will require you to associate a CNAME record to your domain. To associate an ANAME record to your application, [migrate your nameservers to Azion](/en/documentation/products/guides/migrate-ns-to-azion/). diff --git a/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-amazon-s3.mdx b/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-amazon-s3.mdx index 49b94f7383..47ff9d6962 100644 --- a/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-amazon-s3.mdx +++ b/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-amazon-s3.mdx @@ -20,7 +20,7 @@ Continue reading for a step by step on how to connect an [Amazon S3](https://aws ## Amazon S3 requirements :::note -The S3 credentials used with the endpoint must include the `s3:ListBucket` permission (to list and view objects within a bucket) and the `s3:PutObject` permission (to add or overwrite objects within a bucket), ensuring the necessary access for reading and writing operations in the information storage, including logs. Find out more about [S3 credentials](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/). +The S3 credentials used with the endpoint must include the `s3:ListBucket` permission (to list and view objects within a bucket) and the `s3:PutObject` permission (to add or overwrite objects within a bucket), ensuring the necessary access for reading and writing operations in the information storage, including logs. Find out more about [S3 credentials](/en/documentation/products/store/storage/s3-protocol-for-object-storage/). ::: To get started, you must complete a few configurations in **Amazon S3**: diff --git a/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-azion-edge-storage.mdx b/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-azion-edge-storage.mdx index 3db2b95056..0fc07f1d0e 100644 --- a/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-azion-edge-storage.mdx +++ b/src/content/docs/en/pages/observe-journey/data-stream/integrations/connector-azion-edge-storage.mdx @@ -11,17 +11,17 @@ menu_namespace: observeMenu While configuring [streams](/en/documentation/products/guides/use-data-stream/), you need to set up a specific endpoint to stream your Azion data. -Continue reading for a step-by-step guide on configuring an [Azion Object Storage](/en/documentation/products/store/edge-storage/) connector to receive data from Data Stream. +Continue reading for a step-by-step guide on configuring an [Azion Object Storage](/en/documentation/products/store/object-storage/) connector to receive data from Data Stream. --- ## Requirements :::note -The S3 credentials used with the endpoint must include the `ListBucket` permission (to list and view objects within a bucket) and the `PutObject` permission (to add or overwrite objects within a bucket), ensuring the necessary access for reading and writing operations in the information storage, including logs. Find out more about [S3 credentials](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/). +The S3 credentials used with the endpoint must include the `ListBucket` permission (to list and view objects within a bucket) and the `PutObject` permission (to add or overwrite objects within a bucket), ensuring the necessary access for reading and writing operations in the information storage, including logs. Find out more about [S3 credentials](/en/documentation/products/store/storage/s3-protocol-for-object-storage/). ::: -- Create an [S3 credential via API](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/#create-a-credential-via-api) and [configure access to the bucket through s3cmd](/en/documentation/products/store/storage/s3-protocol-for-edge-storage/#configure-access-to-the-bucket-through-s3cmd). +- Create an [S3 credential via API](/en/documentation/products/store/storage/s3-protocol-for-object-storage/#create-a-credential-via-api) and [configure access to the bucket through s3cmd](/en/documentation/products/store/storage/s3-protocol-for-object-storage/#configure-access-to-the-bucket-through-s3cmd). - Save the **Access Key** and **Secret Key** linked to your credential. You'll need them later. - Create an [Object Storage bucket](/en/documentation/products/store/storage/create-bucket/), or use an existing one. diff --git a/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/investigate-requests.mdx b/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/investigate-requests.mdx index 59f8f59a9e..9bd13a0772 100644 --- a/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/investigate-requests.mdx +++ b/src/content/docs/en/pages/observe-journey/real-time-events/analyze-logs/investigate-requests.mdx @@ -245,7 +245,7 @@ Attackers can change the country their requests are coming from, so by blocking In this example, the **Ubuntu** `User-Agent` will be used. 1. [Access Console](/en/documentation/products/guides/how-to-access-azion-console/) > **Firewall**. -2. Select an existing firewall or [create a new one](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/). +2. Select an existing firewall or [create a new one](/en/documentation/products/guides/secure/firewall-configure-main-settings/). 3. Select the **Rules Engine** tab in the selected firewall. 4. Give your rule a name. 5. In **Criteria**, add the `if Header User Agent matches Ubuntu` criteria. @@ -261,8 +261,8 @@ If you notice there's legitimate requests from other countries being blocked by If you don't want to block all requests from a country through a network list, there are other features of Azion [Secure products](/en/documentation/products/secure/overview/) you can use. -- Create a rule with the [Set Rate Limit behavior](/en/documentation/products/secure/edge-firewall/rules-engine/#behaviors). -- Use [WAF Tuning](/en/documentation/products/secure/edge-firewall/web-application-firewall/#waf-tuning) to monitor and create specific allowed rules. +- Create a rule with the [Set Rate Limit behavior](/en/documentation/products/secure/firewall/rules-engine/#behaviors). +- Use [WAF Tuning](/en/documentation/products/secure/firewall/web-application-firewall/#waf-tuning) to monitor and create specific allowed rules. If you use other configurations, modify your GraphQL API query filters to match the other configurations. For example, using the `stacktrace` field or adding another status, such as `429` for the Set Rate Limit rule. diff --git a/src/content/docs/en/pages/observe-journey/real-time-events/integrations/integrate-grafana.mdx b/src/content/docs/en/pages/observe-journey/real-time-events/integrations/integrate-grafana.mdx index 9e37e8c324..6358621906 100644 --- a/src/content/docs/en/pages/observe-journey/real-time-events/integrations/integrate-grafana.mdx +++ b/src/content/docs/en/pages/observe-journey/real-time-events/integrations/integrate-grafana.mdx @@ -19,7 +19,7 @@ To use the Azion data source plugin, you need: - An [Azion account](https://console.azion.com/signup). - A [personal token](/en/documentation/products/accounts/personal-tokens/) to authenticate your account. -- One or more [applications](/en/documentation/products/build/edge-application/) created on your account. +- One or more [applications](/en/documentation/products/build/applications/) created on your account. - [Access to Grafana](https://grafana.com/). --- diff --git a/src/content/docs/en/pages/secure-journey/automate/edge-functions-apis.mdx b/src/content/docs/en/pages/secure-journey/automate/edge-functions-apis.mdx index 84df683b66..fdcda31fb0 100644 --- a/src/content/docs/en/pages/secure-journey/automate/edge-functions-apis.mdx +++ b/src/content/docs/en/pages/secure-journey/automate/edge-functions-apis.mdx @@ -28,11 +28,11 @@ Through Functions, you can write your own security source code in **JavaScript** The Azion Functions for the firewall run in the request phase, and respect the following process: -1. The rules configured on the [Firewall Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) for the function to run are triggered. +1. The rules configured on the [Firewall Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) for the function to run are triggered. 2. Azion Runtime processes the function, returning an outcome. 3. Firewall Rules Engine resumes the processing, based on the outcome, from the point the behavior was triggered. - + --- @@ -40,7 +40,7 @@ The Azion Functions for the firewall run in the request phase, and respect the f [Azion Runtime](/en/documentation/runtime/overview/) supports a list of APIs that allow manipulation of [metadata](/en/documentation/products/secure/automate/functions/#metadata) and the use of [network lists](/en/documentation/products/secure/automate/functions/##network-list) to help the logic implementation. - + ### Metadata @@ -50,7 +50,7 @@ The Metadata API enables access to a set of metadata that can be manipulated to: - Filter and manage access to your application - Apply specific logic in different scenarios based on GeoIP - + ### Network list @@ -62,7 +62,7 @@ The IPs listed inside network lists can be used to handle: - Blocklists - Greylists - +
--- diff --git a/src/content/docs/en/pages/secure-journey/automate/integrate-siems.mdx b/src/content/docs/en/pages/secure-journey/automate/integrate-siems.mdx index 0040da1903..72da71ffbe 100644 --- a/src/content/docs/en/pages/secure-journey/automate/integrate-siems.mdx +++ b/src/content/docs/en/pages/secure-journey/automate/integrate-siems.mdx @@ -13,7 +13,7 @@ import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -Your logs from [Web Application Firewall (WAF)](/en/documentation/products/secure/edge-firewall/web-application-firewall/) can be integrated with SIEM platforms through **Data Stream** to monitor your applications behaviors, performance, and security. +Your logs from [Web Application Firewall (WAF)](/en/documentation/products/secure/firewall/web-application-firewall/) can be integrated with SIEM platforms through **Data Stream** to monitor your applications behaviors, performance, and security. diff --git a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/edit-main-settings.mdx b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/edit-main-settings.mdx index 45db6188a9..430859324b 100644 --- a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/edit-main-settings.mdx +++ b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/edit-main-settings.mdx @@ -28,24 +28,24 @@ In this section, you'll modify the main settings of your firewalls: name, domain 3. Give your firewall a unique and easy-to-remember name. If you want to protect your domain with an firewall, check the guide below. - + ### Modules -[Modules](/en/documentation/products/secure/edge-firewall/#about-edge-firewall-modules) can unlock additional functionalities and features related to your configured firewalls. See the [Pricing page](/en/documentation/products/pricing/) for more details. +[Modules](/en/documentation/products/secure/firewall/#about-edge-firewall-modules) can unlock additional functionalities and features related to your configured firewalls. See the [Pricing page](/en/documentation/products/pricing/) for more details. There are four available modules that can be activated with your firewall: -- [DDoS Protection](/en/documentation/products/secure/edge-firewall/ddos-protection/) +- [DDoS Protection](/en/documentation/products/secure/firewall/ddos-protection/) Protects your content and applications against Distributed Denial of Service (DDoS) attacks. Automatically enabled in all accounts. -- [Functions](/en/documentation/products/secure/edge-firewall/edge-functions/) +- [Functions](/en/documentation/products/secure/firewall/functions/) Enables you to run serverless functions on Azion's edge with low latency, bringing the operational power closer to the end user. -- [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/) +- [Network Shield](/en/documentation/products/secure/firewall/network-shield/) Allows the creation of filters by IP/CIDR, ASN addresses, or by countries (geolocation) through the configuration of Network Lists and the definition of business rules that will validate blocking or releasing Criteria. -- [Web Application Firewall](/en/documentation/products/secure/edge-firewall/web-application-firewall/) Protects your applications against threats such as SQL Injections, Remote File Inclusion (RFI), Cross-Site Scripting (XSS), and many others. +- [Web Application Firewall](/en/documentation/products/secure/firewall/web-application-firewall/) Protects your applications against threats such as SQL Injections, Remote File Inclusion (RFI), Cross-Site Scripting (XSS), and many others. You can choose between the list of modules: you can select one, a few, or even all. @@ -62,7 +62,7 @@ You'll also find a switch labeled **Active**. You can enable the switch to activ Once you're done configuring your main settings, click the **Save** button. :::tip -To configure an firewall to protect an specific domain, [go to the Protect your domain guide](/en/documentation/products/guides/secure/edge-firewall-protect-your-domain/) +To configure an firewall to protect an specific domain, [go to the Protect your domain guide](/en/documentation/products/guides/secure/firewall-protect-your-domain/) ::: @@ -102,9 +102,9 @@ curl --request PATCH \ | --- | --- | | `name` | Name of the firewall | | `is_active` | Boolean value that enables (`true`) or disables (`false`) the firewall | -| `edge_functions_enabled` | Boolean value that enables (`true`) or disables (`false`) the [Functions](/en/documentation/products/secure/edge-firewall/edge-functions/) module | -| `network_protection_enabled` | Boolean value that enables (`true`) or disables (`false`) the [Network Shield](/en/documentation/products/secure/edge-firewall/network-layer-protection/) module | -| `waf_enabled` | Boolean value that enables (`true`) or disables (`false`) the [Web Application Firewall (WAF)](/en/documentation/products/secure/edge-firewall/web-application-firewall/) module | +| `edge_functions_enabled` | Boolean value that enables (`true`) or disables (`false`) the [Functions](/en/documentation/products/secure/firewall/functions/) module | +| `network_protection_enabled` | Boolean value that enables (`true`) or disables (`false`) the [Network Shield](/en/documentation/products/secure/firewall/network-shield/) module | +| `waf_enabled` | Boolean value that enables (`true`) or disables (`false`) the [Web Application Firewall (WAF)](/en/documentation/products/secure/firewall/web-application-firewall/) module | | `debug_rules` | Boolean value that enables (`true`) or disables (`false`) the [Debug Rules](/en/documentation/products/guides/debug-rules/) feature | Wait a few minutes for the changes to propagate and your firewall will be updated. diff --git a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/instantiate-edge-functions.mdx b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/instantiate-edge-functions.mdx index dbf8a503ba..2ce0cb54d3 100644 --- a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/instantiate-edge-functions.mdx +++ b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/instantiate-edge-functions.mdx @@ -10,14 +10,14 @@ import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -Instantiate [serverless functions](/en/documentation/products/secure/edge-firewall/edge-functions-instances/) directly within your firewall. +Instantiate [serverless functions](/en/documentation/products/secure/firewall/functions-instances/) directly within your firewall. -This guide uses the configured [Deny a request based on Geoip](/en/documentation/products/edge-application/edge-functions/javascript-examples/deny-request/) function. You can repeat this process using any function already available on [Azion Marketplace](/en/documentation/products/marketplace/) or [develop other functions](/en/documentation/products/guides/edge-functions/api-builder/). +This guide uses the configured [Deny a request based on Geoip](/en/documentation/products/applications/functions/javascript-examples/deny-request/) function. You can repeat this process using any function already available on [Azion Marketplace](/en/documentation/products/marketplace/) or [develop other functions](/en/documentation/products/guides/edge-functions/api-builder/). This guide will also presume you have a network list of the [Countries type](/en/documentation/products/secure/edge-firewall/network-layer-protection/network-lists/#types-of-network-lists). :::caution[warning] -You must activate the [Functions](/en/documentation/products/secure/edge-firewall/edge-functions/) module to implement functions in your applications. If **Functions** is activated, computing time and invocations could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. +You must activate the [Functions](/en/documentation/products/secure/firewall/functions/) module to implement functions in your applications. If **Functions** is activated, computing time and invocations could generate usage-related costs. Check the [pricing page](/en/documentation/products/pricing/) for more information. ::: --- diff --git a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/protect-your-domain.mdx b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/protect-your-domain.mdx index e646657c3a..4238f50bca 100644 --- a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/protect-your-domain.mdx +++ b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/protect-your-domain.mdx @@ -20,7 +20,7 @@ In this guide, you'll learn how to select an firewall to protect a particular do On the Console, you must now configure your domain so your firewall protects it. -There are separate instructions for API v3 using [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and API v4 using the new [Workloads](/en/documentation/products/secure/workloads) product. +There are separate instructions for API v3 using [legacy Domains](/en/documentation/products/build/applications/domains/) settings and API v4 using the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. diff --git a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/work-with-rules-engine.mdx b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/work-with-rules-engine.mdx index 993b6c4670..e1af66fac7 100644 --- a/src/content/docs/en/pages/secure-journey/edit-edge-firewall/work-with-rules-engine.mdx +++ b/src/content/docs/en/pages/secure-journey/edit-edge-firewall/work-with-rules-engine.mdx @@ -12,12 +12,12 @@ import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -Implementing rules in your firewall using [Rules Engine](/en/documentation/products/secure/edge-firewall/rules-engine/) will allow you to determine the rules it should execute in specific scenarios. +Implementing rules in your firewall using [Rules Engine](/en/documentation/products/secure/firewall/rules-engine/) will allow you to determine the rules it should execute in specific scenarios. This guide demonstrates the process of creating a rule with a practical example of verifying the existence of a certificate and returning a custom response when there isn't one. This behavior is useful in scenarios such as adjusting your policies to comply with BACEN requirements. :::note -There are different criteria that require different Firewall modules. Make sure you have the [right module](/en/documentation/products/secure/edge-firewall/rules-engine/#criteria) activated to create your rules. +There are different criteria that require different Firewall modules. Make sure you have the [right module](/en/documentation/products/secure/firewall/rules-engine/#criteria) activated to create your rules. ::: --- diff --git a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/add-waf-rule-set.mdx b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/add-waf-rule-set.mdx index 3d06f550b5..6ee516c01d 100644 --- a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/add-waf-rule-set.mdx +++ b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/add-waf-rule-set.mdx @@ -9,9 +9,9 @@ permalink: /documentation/products/guides/secure/create-waf-rule-set/ import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -[Web Application Firewall (WAF)](/en/documentation/products/secure/edge-firewall/web-application-firewall/) allows you to create rule sets regarding possible [threat types](/en/documentation/products/secure/edge-firewall/web-application-firewall/#waf-main-settings). You can set these rule sets on Rules Engine for Firewall to execute their behaviors. +[Web Application Firewall (WAF)](/en/documentation/products/secure/firewall/web-application-firewall/) allows you to create rule sets regarding possible [threat types](/en/documentation/products/secure/firewall/web-application-firewall/#waf-main-settings). You can set these rule sets on Rules Engine for Firewall to execute their behaviors. -This guide will create a rule set to block threats from the **SQL Injection** family to prevent attacks that attempt a `select` query, for example. After [creating an firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) and [activating the WAF module](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/#modules), follow the steps described next. +This guide will create a rule set to block threats from the **SQL Injection** family to prevent attacks that attempt a `select` query, for example. After [creating an firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) and [activating the WAF module](/en/documentation/products/guides/secure/firewall-configure-main-settings/#modules), follow the steps described next. --- diff --git a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx index d324abe81a..eb5f032663 100644 --- a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx +++ b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx @@ -10,7 +10,7 @@ permalink: /documentation/products/guides/secure/manage-bots/ import LinkButton from 'azion-webkit/linkbutton' -You can protect your applications and their contents from bot attacks through Azion Web Platform. To do so, you leverage on functions and allow a serverless solution aligned with [Firewall](/en/documentation/products/secure/edge-firewall/) security policies to execute this task. +You can protect your applications and their contents from bot attacks through Azion Web Platform. To do so, you leverage on functions and allow a serverless solution aligned with [Firewall](/en/documentation/products/secure/firewall/) security policies to execute this task. Check [Firewall integrations](/en/documentation/products/marketplace/integrations/#edge-firewall-functions) on Marketplace to find the available integrations for bot protection. @@ -18,7 +18,7 @@ Check [Firewall integrations](/en/documentation/products/marketplace/integration ## Implementation -Azion provides the [Bot Manager](/en/documentation/products/secure/edge-firewall/bot-manager/) add-on, a comprehensive solution for bot management. A [lite version integration](/en/documentation/products/guides/bot-manager-lite/) is also available in the Marketplace. +Azion provides the [Bot Manager](/en/documentation/products/secure/firewall/bot-manager/) add-on, a comprehensive solution for bot management. A [lite version integration](/en/documentation/products/guides/bot-manager-lite/) is also available in the Marketplace. --- diff --git a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/tune-waf.mdx b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/tune-waf.mdx index 5a2782a17f..68123c5131 100644 --- a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/tune-waf.mdx +++ b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/tune-waf.mdx @@ -16,11 +16,11 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' -You can use the [WAF Tuning](/en/documentation/products/secure/edge-firewall/web-application-firewall/#waf-tuning) feature to analyze network lists, IPs, and countries that have matched configured WAF rule sets. +You can use the [WAF Tuning](/en/documentation/products/secure/firewall/web-application-firewall/#waf-tuning) feature to analyze network lists, IPs, and countries that have matched configured WAF rule sets. In this guide, you'll filter possible attacks in your WAF and create an allowed rule from the results you receive. -There are separate instructions for API v3 using [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and API v4 using the new [Workloads](/en/documentation/products/secure/workloads) product. +There are separate instructions for API v3 using [legacy Domains](/en/documentation/products/build/applications/domains/) settings and API v4 using the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. @@ -32,9 +32,9 @@ If you're not sure which steps apply to your account, see [the Verify Your Accou Requires: -- [Configured firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/)

+- [Configured firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/)

-- [Activated WAF in the firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/#modules) +- [Activated WAF in the firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/#modules) Console - Workloads @@ -97,7 +97,7 @@ You can do a drilldown of the records by clicking on each of them with informati ## Creating an Allowed Rule -Once you filter a query with WAF Tuning, you can create an [allowed rule](/en/documentation/products/secure/edge-firewall/web-application-firewall/custom-allowed-rules/) from the presented results. To do so: +Once you filter a query with WAF Tuning, you can create an [allowed rule](/en/documentation/products/secure/firewall/web-application-firewall/custom-allowed-rules/) from the presented results. To do so: 1. Use the **Field** chechbox to select the records you want to create an allowed rule. - You can select as many records as you want. diff --git a/src/content/docs/en/pages/secure-journey/overview.mdx b/src/content/docs/en/pages/secure-journey/overview.mdx index 3afd65d5a1..ef9ebd457f 100644 --- a/src/content/docs/en/pages/secure-journey/overview.mdx +++ b/src/content/docs/en/pages/secure-journey/overview.mdx @@ -18,19 +18,19 @@ Azion Secure products assist you in protecting your domains, applications, and i **Firewall** is a programmable security product that allows you to secure your applications, your domains, and your user's domains. -

+

- + When a user attempts to access and attack your applications hosted on Azion with any type of attack, Firewall and its modules act as a protection layer before the attack reaches your application and, consequently, the origin. -Firewall is the core to protect your applications and domains but security rules and policies can be enhanced with [modules](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/#modules): **DDoS Protection**, **Functions**, **Network Shield**, and **Web Application Firewall**. As each of them has specific secure purposes, it's recommended to use all of them so your applications are protected with the entire stack. +Firewall is the core to protect your applications and domains but security rules and policies can be enhanced with [modules](/en/documentation/products/guides/secure/firewall-configure-main-settings/#modules): **DDoS Protection**, **Functions**, **Network Shield**, and **Web Application Firewall**. As each of them has specific secure purposes, it's recommended to use all of them so your applications are protected with the entire stack. An attack attempt will pass through each of Firewall's modules and they'll block the attack according to their purposes and configured rules. ![Overview of a request encountering Firewall](/assets/docs/images/uploads/edge-firewall-overview.png) -Furthermore, your configurations need to be set as rules on [Rules Engine](/en/documentation/products/secure/edge-firewall/#rules-engine-for-edge-firewall) for them to be implemented and for requests to be properly analyzed, allowed, or blocked. +Furthermore, your configurations need to be set as rules on [Rules Engine](/en/documentation/products/secure/firewall/#rules-engine-for-edge-firewall) for them to be implemented and for requests to be properly analyzed, allowed, or blocked. diff --git a/src/content/docs/en/pages/secure-journey/secure-application.mdx b/src/content/docs/en/pages/secure-journey/secure-application.mdx index de9a82ba99..7dd6d0e55d 100644 --- a/src/content/docs/en/pages/secure-journey/secure-application.mdx +++ b/src/content/docs/en/pages/secure-journey/secure-application.mdx @@ -32,7 +32,7 @@ To create an Firewall, the first step is to provide: Optionally, you can also enable the **Debug Rules** feature. - + --- @@ -42,13 +42,13 @@ The second step is to instantiate an function. Requires: -[Functions for Firewall](/en/documentation/products/secure/edge-firewall/edge-functions/) +[Functions for Firewall](/en/documentation/products/secure/firewall/functions/) Instantiating an existing function created for security purposes reinforces your security policies and adds another layer of protection for your applications. The instantiation step also allows you to apply specific and customized logic to your functions. -

+

diff --git a/src/content/docs/en/pages/secure-journey/secure-infrastructure.mdx b/src/content/docs/en/pages/secure-journey/secure-infrastructure.mdx index 6a357adf43..9b3018a8ae 100644 --- a/src/content/docs/en/pages/secure-journey/secure-infrastructure.mdx +++ b/src/content/docs/en/pages/secure-journey/secure-infrastructure.mdx @@ -20,7 +20,7 @@ Origin Shield provides a list of IP/CIDR addresses used exclusively by Azion in To access the Origin Shield list, you must have: -- The [Network Shield module](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/#modules) enabled. +- The [Network Shield module](/en/documentation/products/guides/secure/firewall-configure-main-settings/#modules) enabled. - Be subscribed to the Origin Shield add-on. - Contact the [sales team](https://www.azion.com/en/contact-sales/) to subscribe to this feature. diff --git a/src/content/docs/en/pages/secure-journey/transport-layer-security/ciphers.mdx b/src/content/docs/en/pages/secure-journey/transport-layer-security/ciphers.mdx index b2d25fd237..58c41d24c3 100644 --- a/src/content/docs/en/pages/secure-journey/transport-layer-security/ciphers.mdx +++ b/src/content/docs/en/pages/secure-journey/transport-layer-security/ciphers.mdx @@ -40,7 +40,7 @@ To enable the HTTPS protocol for your application: 2. Click the Workload you want to configure. 3. In **Protocol Settings**, select the **HTTP and HTTPS support**. -To specify the [minimum TLS version](/en/documentation/products/build/edge-application/main-settings/#minimum-tls-version) and the [cipher suite](/en/documentation/products/build/edge-application/main-settings/#tls-ciphers) supported by your application, follow these steps: +To specify the [minimum TLS version](/en/documentation/products/build/applications/main-settings/#minimum-tls-version) and the [cipher suite](/en/documentation/products/build/applications/main-settings/#tls-ciphers) supported by your application, follow these steps: 1. In **Minimum TLS version**, select **TLS 1.2**. 2. Under **Cipher suite**, select **TLSv1.2_2021**. @@ -48,7 +48,7 @@ To specify the [minimum TLS version](/en/documentation/products/build/edge-appli It may take some time to propagate your changes to the edge. To verify whether your changes took place, you can inspect the `https://xxxxxxxxxx.map.azionedge.net` page using your browser and locate the security settings of the application. You can also [run the DIG command](/en/documentation/products/guides/run-the-dig-command/) to get more information on your security settings. -The application may still be running in TLS 1.3, since you selected the minimum version and *not the exact TLS version* used. However, you can check the cipher suite being used against the [list of supported ciphers](/en/documentation/products/build/edge-application/main-settings/#tls-ciphers) to verify whether the changes took place. +The application may still be running in TLS 1.3, since you selected the minimum version and *not the exact TLS version* used. However, you can check the cipher suite being used against the [list of supported ciphers](/en/documentation/products/build/applications/main-settings/#tls-ciphers) to verify whether the changes took place. @@ -58,7 +58,7 @@ The application may still be running in TLS 1.3, since you selected the minimum 2. Click the application you want to configure. 3. In **Delivery Settings**, select the **HTTP and HTTPS support**. -Now to specify the [minimum TLS version](/en/documentation/products/build/edge-application/main-settings/#minimum-tls-version) and the [cipher suite](/en/documentation/products/build/edge-application/main-settings/#tls-ciphers) supported by your application: +Now to specify the [minimum TLS version](/en/documentation/products/build/applications/main-settings/#minimum-tls-version) and the [cipher suite](/en/documentation/products/build/applications/main-settings/#tls-ciphers) supported by your application: 1. In **Minimum TLS version**, select **TLS 1.2**. 2. Under **Cipher suite**, select **TLSv1.2_2021**. @@ -66,7 +66,7 @@ Now to specify the [minimum TLS version](/en/documentation/products/build/edge-a It may take some time to propagate your changes to the edge. To verify whether your changes took place, you can inspect the `https://xxxxxxxxxx.map.azionedge.net` page using your browser and locate the security settings of the application. You can also [run the DIG command](/en/documentation/products/guides/run-the-dig-command/) to get more information on your security settings. -The application may still be running in TLS 1.3, since you selected the minimum version and *not the exact TLS version* used. However, you can check the cipher suite being used against the [list of supported ciphers](/en/documentation/products/build/edge-application/main-settings/#tls-ciphers) to verify whether the changes took place. +The application may still be running in TLS 1.3, since you selected the minimum version and *not the exact TLS version* used. However, you can check the cipher suite being used against the [list of supported ciphers](/en/documentation/products/build/applications/main-settings/#tls-ciphers) to verify whether the changes took place. @@ -108,7 +108,7 @@ curl --request PATCH \ | --- | --- | | `protocols` | Enables the HTTP and HTTPS protocols | | `minimum_tls_version` | Enum that establishes the minimum TLS version | -| `ciphers` | Enum that sets the supported cipher suite. See the full list of [list of supported ciphers](/en/documentation/products/build/edge-application/main-settings/#tls-ciphers) for further details | +| `ciphers` | Enum that sets the supported cipher suite. See the full list of [list of supported ciphers](/en/documentation/products/build/applications/main-settings/#tls-ciphers) for further details | 4. You'll receive a response similar to this: @@ -196,7 +196,7 @@ curl --location --request PATCH 'https://api.azionapi.net/edge_applications/ -[Mutual Transport Layer Security (mTLS)](/en/documentation/products/secure/edge-firewall/mtls/) is a security protocol that enables two-way authentication and encryption for network interaction. It confirms that both the client and the server are authenticated and have the clearance for effective communication. +[Mutual Transport Layer Security (mTLS)](/en/documentation/products/secure/firewall/mtls/) is a security protocol that enables two-way authentication and encryption for network interaction. It confirms that both the client and the server are authenticated and have the clearance for effective communication. To configure mTLS in your applications, you need a [digital certificate](/en/documentation/products/guides/secure/digital-certificates/) with mTLS support signed by a third-party certificate authority (CA). At Azion, this type of certificate is called a **Trusted CA**. -There are separate instructions for API v3 using [legacy Domains](/en/documentation/products/build/edge-application/domains/) settings and API v4 using the new [Workloads](/en/documentation/products/secure/workloads) product. +There are separate instructions for API v3 using [legacy Domains](/en/documentation/products/build/applications/domains/) settings and API v4 using the new [Workloads](/en/documentation/products/secure/workloads) product. :::tip In this guide, there are separate instructions for API v3 and API v4. If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. @@ -348,7 +348,7 @@ curl --location 'https://api.azionapi.net/domains' \ ## Creating specific rules for Permissive mTLS -To configure a firewall to block access to a domain using the **Permissive** mode in mTLS, you must use the [Rules Engine for Firewall](/en/documentation/products/secure/edge-firewall/rules-engine/). The following example describes a rule set that will block any incoming network traffic with the hostname `mydomain.com` whose client certificate validation isn't true and deliver a `403 Forbidden` error. +To configure a firewall to block access to a domain using the **Permissive** mode in mTLS, you must use the [Rules Engine for Firewall](/en/documentation/products/secure/firewall/rules-engine/). The following example describes a rule set that will block any incoming network traffic with the hostname `mydomain.com` whose client certificate validation isn't true and deliver a `403 Forbidden` error. Console @@ -357,7 +357,7 @@ To configure a firewall to block access to a domain using the **Permissive** mod 1. Access [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/) > **Firewall**. -2. [Configure an firewall](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/) for the mTLS domain. +2. [Configure an firewall](/en/documentation/products/guides/secure/firewall-configure-main-settings/) for the mTLS domain. 3. Click the **Rules Engine** tab. 4. Click the **+ Rules Engine** button. 5. Give your rule an easy-to-remember name. @@ -459,7 +459,7 @@ curl --request POST \ ## Specifying mTLS variables in HTTP headers -If your application is part of the Open Banking model, you must specify the variables `${ssl_client_escaped_cert}` and `${ssl_client_s_dn_parsed}` in the HTTP headers of your application. You can use the [Rules Engine for Application](/en/documentation/products/build/edge-application/rules-engine/) to create this behavior for your whole application. +If your application is part of the Open Banking model, you must specify the variables `${ssl_client_escaped_cert}` and `${ssl_client_s_dn_parsed}` in the HTTP headers of your application. You can use the [Rules Engine for Application](/en/documentation/products/build/applications/rules-engine/) to create this behavior for your whole application. Requires: @@ -467,7 +467,7 @@ Requires: - [Domain with an mTLS certificate](#add-a-trusted-ca-certificate-and-associate-it-to-a-domain) :::tip -You can also insert headers with other variables from [the list of available mTLS variables](/en/documentation/products/build/edge-application/rules-engine/#mutual-transport-layer-security-mtls-variables). +You can also insert headers with other variables from [the list of available mTLS variables](/en/documentation/products/build/applications/rules-engine/#mutual-transport-layer-security-mtls-variables). ::: To test whether the headers you add are being sent in requests, you can run the following cURL command in your terminal from a directory containing the `.pem` files of your Trusted CA and its private key: diff --git a/src/content/docs/en/pages/secure-journey/troubleshoot/edge-firewall-understand-metrics.mdx b/src/content/docs/en/pages/secure-journey/troubleshoot/edge-firewall-understand-metrics.mdx index 1ce22ed3ce..2a07497e46 100644 --- a/src/content/docs/en/pages/secure-journey/troubleshoot/edge-firewall-understand-metrics.mdx +++ b/src/content/docs/en/pages/secure-journey/troubleshoot/edge-firewall-understand-metrics.mdx @@ -8,7 +8,7 @@ permalink: /documentation/products/secure/troubleshoot/firewall-understand-metri import LinkButton from 'azion-webkit/linkbutton' -Once you create an firewall and [activate the Web Application Firewall (WAF) module](/en/documentation/products/guides/secure/edge-firewall-configure-main-settings/#modules), you can also use [Observe](/en/documentation/products/observe/) products to monitor how WAF is processing requests made to your applications. +Once you create an firewall and [activate the Web Application Firewall (WAF) module](/en/documentation/products/guides/secure/firewall-configure-main-settings/#modules), you can also use [Observe](/en/documentation/products/observe/) products to monitor how WAF is processing requests made to your applications. - [Real-Time Metrics](/en/documentation/products/observe/real-time-metrics/): access to charts with aggregated data to explore behaviors throughout longer periods of data storage. - [GraphQL API](/en/documentation/devtools/graphql-api/overview/): access to aggragated and raw data via API with customized queries with only the data you request. diff --git a/src/content/docs/en/pages/store-journey/overview.mdx b/src/content/docs/en/pages/store-journey/overview.mdx index 5f9a07c58e..0fcb453a1e 100644 --- a/src/content/docs/en/pages/store-journey/overview.mdx +++ b/src/content/docs/en/pages/store-journey/overview.mdx @@ -9,7 +9,7 @@ menu_namespace: storeMenu import LinkButton from 'azion-webkit/linkbutton' -Welcome to the Azion Store Products journey. This documentation introduces [SQL Database](/en/documentation/products/store/edge-sql/) and [Object Storage](/en/documentation/products/store/edge-storage/), powerful tools for efficient data management and processing. +Welcome to the Azion Store Products journey. This documentation introduces [SQL Database](/en/documentation/products/store/sql-database/) and [Object Storage](/en/documentation/products/store/object-storage/), powerful tools for efficient data management and processing. ## Object Storage @@ -19,7 +19,7 @@ Azion Object Storage is an object storage model that organizes data into "bucket Object Storage is ideal for backup and recovery, content management, rich media, static-site hosting, storage of unstructured data, and Jamstack websites. - + ## SQL Database @@ -29,4 +29,4 @@ Azion SQL Database is a cutting-edge SQL solution tailored for edge computing, p SQL Database is suitable for real-time telemetry data storage, access log analysis, efficient access data management, and supporting applications requiring quick data retrieval. - + diff --git a/src/content/docs/en/pages/store-journey/sql/create-table.mdx b/src/content/docs/en/pages/store-journey/sql/create-table.mdx index de35c0345b..fc172a57a6 100644 --- a/src/content/docs/en/pages/store-journey/sql/create-table.mdx +++ b/src/content/docs/en/pages/store-journey/sql/create-table.mdx @@ -13,7 +13,7 @@ import LinkButton from 'azion-webkit/linkbutton' Once you've created your [SQL Database database](/en/documentation/products/store/sql/create-database/), you can begin creating tables and inserting data into them. - + ## Creating a table diff --git a/src/content/docs/en/pages/store-journey/sql/install-edgesql-shell.mdx b/src/content/docs/en/pages/store-journey/sql/install-edgesql-shell.mdx index 8d0c071304..b94aea8f12 100644 --- a/src/content/docs/en/pages/store-journey/sql/install-edgesql-shell.mdx +++ b/src/content/docs/en/pages/store-journey/sql/install-edgesql-shell.mdx @@ -69,4 +69,4 @@ python edgesql-shell.py Now you can use the SQL Database Shell commands, set environment variables and run SQL queries directly in the terminal. - + diff --git a/src/content/docs/en/pages/store-journey/sql/query-rows.mdx b/src/content/docs/en/pages/store-journey/sql/query-rows.mdx index 3dfbee5fd5..1ecce51722 100644 --- a/src/content/docs/en/pages/store-journey/sql/query-rows.mdx +++ b/src/content/docs/en/pages/store-journey/sql/query-rows.mdx @@ -11,7 +11,7 @@ import LinkButton from 'azion-webkit/linkbutton' Once you've created your SQL Database database, you can begin retrieving data from them. - + ## Listing data in a table diff --git a/src/content/docs/en/pages/store-journey/storage/create-bucket.mdx b/src/content/docs/en/pages/store-journey/storage/create-bucket.mdx index 86059a704d..db4d44dc0b 100644 --- a/src/content/docs/en/pages/store-journey/storage/create-bucket.mdx +++ b/src/content/docs/en/pages/store-journey/storage/create-bucket.mdx @@ -147,5 +147,5 @@ You should receive the following response: Now, you have successfully created a bucket and attributed read-write permissions to it. You can start storing and retrieving objects from this bucket. :::caution[Warning] -When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for applications, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through a function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/edge-storage/#authentication-and-permissions). +When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for applications, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through a function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/object-storage/#authentication-and-permissions). ::: diff --git a/src/content/docs/en/pages/store-journey/storage/delete-object.mdx b/src/content/docs/en/pages/store-journey/storage/delete-object.mdx index b782435ede..4c6869bb9b 100644 --- a/src/content/docs/en/pages/store-journey/storage/delete-object.mdx +++ b/src/content/docs/en/pages/store-journey/storage/delete-object.mdx @@ -115,8 +115,8 @@ See the [Object Storage API](/en/documentation/runtime/api-reference/storage/) r Once you have the function ready, you need to create an applications that will proxy the deleting process for the bucket and instantiate the function. - - + + 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 b0c3aa3590..ea25fcc0f6 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 @@ -90,8 +90,8 @@ See the [Object Storage API](/en/documentation/runtime/api-reference/storage/) r Once you have the function ready, you need to create an applications that will proxy the process for the bucket and instantiate the function. - - + + diff --git a/src/content/docs/en/pages/store-journey/storage/list-objects-.mdx b/src/content/docs/en/pages/store-journey/storage/list-objects-.mdx index e495b5f3ef..eac63541e2 100644 --- a/src/content/docs/en/pages/store-journey/storage/list-objects-.mdx +++ b/src/content/docs/en/pages/store-journey/storage/list-objects-.mdx @@ -118,8 +118,8 @@ See the [Object Storage API](/en/documentation/runtime/api-reference/storage/) r Once the function is ready, you need to create an applications that will proxy the listing process for the bucket and instantiate the function. - - + + diff --git a/src/content/docs/en/pages/store-journey/storage/update-bucket.mdx b/src/content/docs/en/pages/store-journey/storage/update-bucket.mdx index 84fd518058..38e1c1d75d 100644 --- a/src/content/docs/en/pages/store-journey/storage/update-bucket.mdx +++ b/src/content/docs/en/pages/store-journey/storage/update-bucket.mdx @@ -90,5 +90,5 @@ The bucket's name cannot be updated. :::caution[Warning] -When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for an application, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through a function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/edge-storage/#authentication-and-permissions). +When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for an application, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through a function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/object-storage/#authentication-and-permissions). ::: diff --git a/src/content/docs/en/pages/store-journey/storage/update-object.mdx b/src/content/docs/en/pages/store-journey/storage/update-object.mdx index 1a68320d12..20125e187d 100644 --- a/src/content/docs/en/pages/store-journey/storage/update-object.mdx +++ b/src/content/docs/en/pages/store-journey/storage/update-object.mdx @@ -110,8 +110,8 @@ See the [Object Storage API](/en/documentation/runtime/api-reference/storage/) r Once you have the function ready, you need to create an applications that will proxy the process for the bucket and instantiate the function. - - + + 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 5b20a197f6..e9605faefa 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 @@ -118,8 +118,8 @@ See the [Object Storage API](/en/documentation/runtime/api-reference/storage/) r Once you have the function ready, you need to create an applications that will proxy the upload process for the bucket and instantiate the function. - - + + 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 5b16d1b3eb..39095555b3 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 @@ -21,9 +21,9 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' This guide walks you through setting a bucket as origin of an applications using the [Azion API](https://api.azion.com/), [Azion CLI](/en/documentation/products/azion-cli/overview/), and [Azion Runtime](/en/documentation/runtime/api-reference/storage/). - + -There are separate instructions for API v3 using [legacy Origin](/en/documentation/products/build/edge-application/domains/) settings and API v4 using the new [Connector](/en/documentation/products/secure/edge-connector) product. +There are separate instructions for API v3 using [legacy Origin](/en/documentation/products/build/applications/domains/) settings and API v4 using the new [Connector](/en/documentation/products/secure/connectors) product. :::tip In this guide, there are separate instructions for API v3 and API v4. If you're not sure which steps apply to your account, see [the Verify Your Account Migration guide](/en/documentation/products/guides/verify-account-migration/) to determine if your account has already been migrated. @@ -132,7 +132,7 @@ h1, p { `} /> :::caution[Warning] -When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for an applications, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through an function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/edge-storage/#authentication-and-permissions). +When a bucket is configured with **read-write permissions**, any user can access and modify its content (for example, by sending a PUT request to overwrite files). If the bucket is used as an origin for an applications, this configuration may expose the content to unauthorized modifications. However, suppose the bucket is accessed through an function. In that case, the risk is managed by the logic implemented in the function code, allowing developers to enforce stricter controls over who can access or modify the data. To mitigate risks, always verify the required permissions for each use case and implement proper access controls. Read more on [Authentication and permissions](/en/documentation/products/store/object-storage/#authentication-and-permissions). ::: --- diff --git a/src/content/docs/en/pages/store-journey/storage/use-s3.mdx b/src/content/docs/en/pages/store-journey/storage/use-s3.mdx index bd1f2ec1f9..2279eac27a 100644 --- a/src/content/docs/en/pages/store-journey/storage/use-s3.mdx +++ b/src/content/docs/en/pages/store-journey/storage/use-s3.mdx @@ -132,7 +132,7 @@ Once you've configured access to the bucket through s3cmd, you can execute opera If any files were deleted within the last 24 hours from the specified bucket, attempting to delete the entire bucket would be blocked. It's recommended to wait for at least 24 hours after deleting files before attempting to delete the entire bucket. ::: -For more details on S3 protocol and s3cmd commands, check the [official documentation](https://s3tools.org/s3cmd). You can also visit the [Object Storage reference](/en/documentation/products/store/edge-storage/). +For more details on S3 protocol and s3cmd commands, check the [official documentation](https://s3tools.org/s3cmd). You can also visit the [Object Storage reference](/en/documentation/products/store/object-storage/). diff --git a/src/content/docs/pt-br/homes/build-home.mdx b/src/content/docs/pt-br/homes/build-home.mdx index 1be3a5de90..27dd93d23c 100644 --- a/src/content/docs/pt-br/homes/build-home.mdx +++ b/src/content/docs/pt-br/homes/build-home.mdx @@ -15,7 +15,7 @@ product_cards: - icon: /assets/docs/images/uploads/edge-application.svg title: Applications description: Construa aplicações web para rodar na Edge da Azion. - link: /pt-br/documentacao/produtos/build/edge-application/ + link: /pt-br/documentacao/produtos/build/applications/ - title: Módulos cards: - icon: /assets/docs/images/uploads/app-aceleration.svg @@ -24,32 +24,32 @@ product_cards: Acelera a performance de suas aplicações e APIs com otimização de protocolos e regras de cache avançadas. link: >- - /pt-br/documentacao/produtos/build/edge-application/application-accelerator/ + /pt-br/documentacao/produtos/build/applications/application-accelerator/ - icon: /assets/docs/images/uploads/edge-caching.svg title: Cache description: >- Acelere entregas mantendo seu conteúdo em cache no edge da rede, mais próximo de seus usuários. - link: /pt-br/documentacao/produtos/build/edge-application/edge-cache/ + link: /pt-br/documentacao/produtos/build/applications/cache/ - icon: /assets/docs/images/uploads/edge-functions.svg title: Functions description: >- Crie aplicações serverless orientadas a eventos no edge da rede, mais perto dos usuários. - link: /pt-br/documentacao/produtos/build/edge-application/edge-functions/ + link: /pt-br/documentacao/produtos/build/applications/functions/ - icon: /assets/docs/images/uploads/image-processor.svg title: Image Processor description: >- Otimize, converta e manipule suas imagens na hora certa para aprimorar a experiência do usuário. - link: /pt-br/documentacao/produtos/build/edge-application/image-processor/ + link: /pt-br/documentacao/produtos/build/applications/image-processor/ - icon: /assets/docs/images/uploads/load-balancer.svg title: Load Balancer description: >- Distribua cargas em seus servidores e em qualquer provedor de cloud para aumentar a confiabilidade e disponibilidade de seus conteúdos, aplicações e APIs. - link: /pt-br/documentacao/produtos/secure/edge-connector/load-balancer/ + link: /pt-br/documentacao/produtos/secure/connectors/load-balancer/ - title: Recursos cards: - icon: /assets/docs/images/uploads/icon-guides.svg @@ -58,4 +58,3 @@ product_cards: link: /pt-br/documentacao/produtos/guias/ permalink: /documentacao/produtos/build/ --- - diff --git a/src/content/docs/pt-br/homes/deploy-home.mdx b/src/content/docs/pt-br/homes/deploy-home.mdx index 2eefffaba5..b2c34fce68 100644 --- a/src/content/docs/pt-br/homes/deploy-home.mdx +++ b/src/content/docs/pt-br/homes/deploy-home.mdx @@ -15,7 +15,7 @@ product_cards: description: >- Aproxime suas aplicações dos seus usuários e dispositivos distribuindo-as na edge da Azion ou em seu próprio edge. - link: /pt-br/documentacao/produtos/deploy/edge-orchestrator/ + link: /pt-br/documentacao/produtos/deploy/orchestrator/ - title: Recursos cards: - icon: /assets/docs/images/uploads/icon-guides.svg @@ -23,4 +23,3 @@ product_cards: description: Encontre documentações práticas sobre como utilizar os produtos. link: /pt-br/documentacao/produtos/guias/ --- - diff --git a/src/content/docs/pt-br/homes/secure-home.mdx b/src/content/docs/pt-br/homes/secure-home.mdx index 39a384565d..826d0e8464 100644 --- a/src/content/docs/pt-br/homes/secure-home.mdx +++ b/src/content/docs/pt-br/homes/secure-home.mdx @@ -13,7 +13,7 @@ product_cards: - icon: /assets/docs/images/uploads/edge-firewall.svg title: Firewall description: Proteja-se sua aplicação a partir da rede até a camada da aplicação. - link: /pt-br/documentacao/produtos/secure/edge-firewall/ + link: /pt-br/documentacao/produtos/secure/firewall/ - icon: /assets/docs/images/uploads/edge-dns.svg title: Edge DNS description: Hospede domínios com uma solução integrada de roteamento de tráfego. @@ -25,21 +25,21 @@ product_cards: description: >- Mitigue os maiores e mais complexos ataques DDoS nas camadas de rede e de transporte. - link: /pt-br/documentacao/produtos/secure/edge-firewall/ddos-protection/ + link: /pt-br/documentacao/produtos/secure/firewall/ddos-protection/ - icon: /assets/docs/images/uploads/network-layer-protection.svg title: Network Shield description: >- Use um perímetro de segurança programável no edge da rede para tráfego de entrada e saída. link: >- - /pt-br/documentacao/produtos/secure/edge-firewall/network-layer-protection/ + /pt-br/documentacao/produtos/secure/firewall/network-shield/ - icon: /assets/docs/images/uploads/waf-rules.svg title: Web Application Firewall description: >- Proteja sua aplicação web das ameaças OWASP Top 10 aos sofisticados ataques zero-day. link: >- - /pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/ + /pt-br/documentacao/produtos/secure/firewall/web-application-firewall/ - title: Recursos cards: - icon: /assets/docs/images/uploads/icon-guides.svg @@ -47,4 +47,3 @@ product_cards: description: Encontre documentações práticas sobre como utilizar os produtos. link: /pt-br/documentacao/produtos/guias/ --- - 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 7c59e69ea3..4a00965c5f 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 @@ -45,12 +45,12 @@ Através desse perímetro, você pode implementar soluções como: ### Componentes -- [Application](/pt-br/documentacao/produtos/build/edge-application/): permite que você configure uma aplicação para definir políticas de entrega e cache. -- [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/): fornece configurações principais para criar sua instância, permitindo que você a associe a domínios e ative módulos para proteger usuários, aplicações e redes. - - [Web Application Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/): permite que você configure proteção contra ataques e vulnerabilidades. - - [DDoS Protection](/pt-br/documentacao/produtos/secure/edge-firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. - - [Network Shield](/pt-br/documentacao/produtos/secure/edge-firewall/network-layer-protection/): permite que você crie listas com endereços IP ou países com comportamento suspeito e restrinja seu acesso. - - [Functions for Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/edge-functions/): construa aplicações serverless baseadas em eventos, incluindo funções com seu próprio código-fonte de segurança. +- [Application](/pt-br/documentacao/produtos/build/applications/): permite que você configure uma aplicação para definir políticas de entrega e cache. +- [Firewall](/pt-br/documentacao/produtos/secure/firewall/): fornece configurações principais para criar sua instância, permitindo que você a associe a domínios e ative módulos para proteger usuários, aplicações e redes. + - [Web Application Firewall](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/): permite que você configure proteção contra ataques e vulnerabilidades. + - [DDoS Protection](/pt-br/documentacao/produtos/secure/firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. + - [Network Shield](/pt-br/documentacao/produtos/secure/firewall/network-shield/): permite que você crie listas com endereços IP ou países com comportamento suspeito e restrinja seu acesso. + - [Functions for Firewall](/pt-br/documentacao/produtos/secure/firewall/functions/): construa aplicações serverless baseadas em eventos, incluindo funções com seu próprio código-fonte de segurança. - [Marketplace Integrations](/pt-br/documentacao/produtos/marketplace/integracoes/): funcionalidades baseadas em funções para compor e melhorar suas aplicações, aplicando políticas de segurança. - [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/) e [Real-Time Events](/pt-br/documentacao/produtos/observe/real-time-events/) permitem que você monitore toda a atividade do API Gateway. @@ -64,8 +64,8 @@ Através desse perímetro, você pode implementar soluções como: - [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 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. +5. [Crie um firewall](/pt-br/documentacao/produtos/guias/secure/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/firewall/rules-engine/) ou [functions](/pt-br/documentacao/produtos/secure/firewall/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. 6. [Monitore o comportamento do seu API Gateway ](/pt-br/documentacao/produtos/observe/visao-geral/) através dos produtos Observe. diff --git a/src/content/docs/pt-br/pages/arquiteturas/artificial-intelligence/ai-agent-copilot.mdx b/src/content/docs/pt-br/pages/arquiteturas/artificial-intelligence/ai-agent-copilot.mdx index 39964ac058..225aa117a0 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/artificial-intelligence/ai-agent-copilot.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/artificial-intelligence/ai-agent-copilot.mdx @@ -37,10 +37,10 @@ Considerando a implementação de um agente ReAct em uma Plataforma de Edge Comp ### Componentes -- [Application](/pt-br/documentacao/produtos/build/edge-application/): permite construir aplicações que rodam na Infraestrutura Global da Azion. - - [Functions for Applications](/pt-br/documentacao/produtos/build/edge-application/edge-functions/): executa código mais próximo do usuário final, melhorando o desempenho e permitindo lógica personalizada para manipulação de requisições e respostas. -- [SQL Database](/pt-br/documentacao/produtos/store/edge-sql/): uma solução SQL nativa para edge projetada para aplicações serverless. - - [Vector Search](/pt-br/documentacao/produtos/store/edge-sql/vector-search/): permite que clientes implementem mecanismos de busca semântica. +- [Application](/pt-br/documentacao/produtos/build/applications/): permite construir aplicações que rodam na Infraestrutura Global da Azion. + - [Functions for Applications](/pt-br/documentacao/produtos/build/applications/functions/): executa código mais próximo do usuário final, melhorando o desempenho e permitindo lógica personalizada para manipulação de requisições e respostas. +- [SQL Database](/pt-br/documentacao/produtos/store/sql-database/): uma solução SQL nativa para edge projetada para aplicações serverless. + - [Vector Search](/pt-br/documentacao/produtos/store/sql-database/vector-search/): permite que clientes implementem mecanismos de busca semântica. - [Global Infrastructure](https://www.azion.com/pt-br/produtos/nossa-rede/): uma arquitetura altamente distribuída que inclui edge nodes estrategicamente localizados. --- @@ -49,7 +49,7 @@ Considerando a implementação de um agente ReAct em uma Plataforma de Edge Comp 1. Crie uma [aplicação](/pt-br/documentacao/produtos/guias/build/criar-uma-aplicacao/). 2. Crie o [banco de dados SQL Database](/pt-br/documentacao/produtos/store/sql/criar-banco-de-dados/) que será consultado. -3. [Crie uma Function](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) com a lógica do seu Agente de AI e [instancie](/en/documentation/products/guides/build/instantiate-edge-functions/) na aplicação. +3. [Crie uma Function](/pt-br/documentacao/produtos/build/applications/functions/) com a lógica do seu Agente de AI e [instancie](/en/documentation/products/guides/build/instantiate-edge-functions/) na aplicação. 4. Implemente [Vector Search](/pt-br/documentacao/produtos/guias/edge-sql-vector-search/). 5. Você pode monitorar seu Agente de IA através dos [produtos Observe da Azion](/pt-br/documentacao/produtos/observe/visao-geral/) e ferramentas especializadas como LangGraph. diff --git a/src/content/docs/pt-br/pages/arquiteturas/bot-management/bot-management-arquitetura.mdx b/src/content/docs/pt-br/pages/arquiteturas/bot-management/bot-management-arquitetura.mdx index 448ab5b558..2390340992 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/bot-management/bot-management-arquitetura.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/bot-management/bot-management-arquitetura.mdx @@ -39,10 +39,10 @@ Essa solução é ideal para organizações que buscam mitigar riscos de seguran ### Componentes -- [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/) executa o add-on Bot Manager e outras regras de segurança. -- [Bot Manager](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/) é um add-on do Firewall para o gerenciamento de bots. +- [Firewall](/pt-br/documentacao/produtos/secure/firewall/) executa o add-on Bot Manager e outras regras de segurança. +- [Bot Manager](/pt-br/documentacao/produtos/secure/firewall/bot-manager/) é um add-on do Firewall para o gerenciamento de bots. - Este add-on é a solução abrangente da Azion para o gerenciamento de bots. Uma [integração com uma versão lite](/pt-br/documentacao/produtos/guias/bot-manager-lite/) também está disponível no Marketplace. -- [Application](/pt-br/documentacao/produtos/build/edge-application/) é sua aplicação em execução na Azion Web Platform. +- [Application](/pt-br/documentacao/produtos/build/applications/) é sua aplicação em execução na Azion Web Platform. - [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/) e o [Real-Time Events](/pt-br/documentacao/produtos/observe/real-time-metrics/) permitem que você monitore toda a atividade do Bot Manager. --- @@ -85,7 +85,7 @@ Você pode testar e implementar o Azion Bot Manager de duas maneiras: - Do zero: crie um stack de edge inteiro do zero, incluindo o Bot Manager. Para fazer isso: 1. [Crie uma aplicação](/pt-br/documentacao/produtos/guias/build/criar-uma-aplicacao/). 2. [Adicione um domínio personalizado à aplicação](/pt-br/documentacao/produtos/guias/configurar-dominio/). - 3. [Habilite o Bot Manager](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/). + 3. [Habilite o Bot Manager](/pt-br/documentacao/produtos/secure/firewall/bot-manager/). - Entre em contato com a [equipe de vendas](https://www.azion.com/pt-br/contate-vendas/) para mais detalhes sobre a assinatura do Bot Manager. - [Configure o Bot Manager Lite](/pt-br/documentacao/produtos/guias/bot-manager-lite/#configure-a-integracao) se você decidir usar essa versão. 4. [Monitore a atividade de bots](/pt-br/documentacao/produtos/observe/data-stream/primeiros-passos/) e calibre as regras. diff --git a/src/content/docs/pt-br/pages/arquiteturas/compliance/compliance-architecture.mdx b/src/content/docs/pt-br/pages/arquiteturas/compliance/compliance-architecture.mdx index 89ec8eded5..b3bc2ee433 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/compliance/compliance-architecture.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/compliance/compliance-architecture.mdx @@ -54,12 +54,12 @@ Leia mais sobre o [Modelo de Responsabilidade Compartilhada](/pt-br/documentacao - [Global Infrastructure](https://www.azion.com/pt-br/produtos/nossa-rede/): processa dados mais perto da fonte, reduzindo a latência e melhorando a análise em tempo real, incluindo políticas e tecnologias para torná-la segura e em conformidade. - [Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/): uma interface de linha de comando (CLI) de código aberto que permite interagir com a Azion Web Platform usando um terminal. - [Azion Console](/pt-br/documentacao/produtos/guias/conhecendo-o-azion-console/): a interface da Azion onde você pode acessar todos os produtos disponíveis e suas configurações. -- [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/): fornece as principais configurações para configurar sua instância, permitindo associá-la a domínios e ativar módulos para proteger usuários, aplicações e redes. - - [Web Application Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/): permite configurar proteção contra ataques e vulnerabilidades. - - [DDoS Protection](/pt-br/documentacao/produtos/secure/edge-firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. - - [Network Shield](/pt-br/documentacao/produtos/secure/edge-firewall/network-layer-protection/): permite criar listas com endereços IP ou países com comportamento suspeito e restringir seu acesso. - - [Functions for Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/edge-functions/): construa aplicações serverless e orientadas a eventos, incluindo funções com seu próprio código-fonte de segurança. -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): permite configurar uma aplicação para definir políticas de entrega e cache. +- [Firewall](/pt-br/documentacao/produtos/secure/firewall/): fornece as principais configurações para configurar sua instância, permitindo associá-la a domínios e ativar módulos para proteger usuários, aplicações e redes. + - [Web Application Firewall](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/): permite configurar proteção contra ataques e vulnerabilidades. + - [DDoS Protection](/pt-br/documentacao/produtos/secure/firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. + - [Network Shield](/pt-br/documentacao/produtos/secure/firewall/network-shield/): permite criar listas com endereços IP ou países com comportamento suspeito e restringir seu acesso. + - [Functions for Firewall](/pt-br/documentacao/produtos/secure/firewall/functions/): construa aplicações serverless e orientadas a eventos, incluindo funções com seu próprio código-fonte de segurança. +- [Applications](/pt-br/documentacao/produtos/build/applications/): permite configurar uma aplicação para definir políticas de entrega e cache. - [Real-Time Events](/pt-br/documentacao/produtos/observe/real-time-events/) permite monitorar toda a atividade de suas aplicações e, utilizando conectores [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/), você pode alimentar logs de eventos em seu processamento de stream, SIEM e plataformas de big data. --- @@ -72,8 +72,8 @@ Leia mais sobre o [Modelo de Responsabilidade Compartilhada](/pt-br/documentacao - [Defina as principais configurações da aplicação](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/). 3. [Crie um domínio](/pt-br/documentacao/produtos/guias/configurar-dominio/) e vincule à aplicação, e [aponte seu tráfego para a Azion](/pt-br/documentacao/produtos/guias/apontar-dominio-para-a-azion/). 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 os domínios que você deseja proteger. - - Defina quaisquer [regras do 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 você deseja implementar e instanciar no firewall. +5. [Crie um firewall](/pt-br/documentacao/produtos/guias/secure/firewall-definir-main-settings/) e selecione os domínios que você deseja proteger. + - Defina quaisquer [regras do WAF](/pt-br/documentacao/produtos/guias/secure/criar-waf-rule-set/), [regras do Rules Engine](/pt-br/documentacao/produtos/secure/firewall/rules-engine/), ou [functions](/pt-br/documentacao/produtos/secure/firewall/functions/) que você deseja implementar e instanciar no firewall. 6. Monitore suas aplicações através dos [produtos Observe](/pt-br/documentacao/produtos/observe/visao-geral/) e da página [Activity History](/pt-br/documentacao/produtos/gestao-de-contas/activity-history/). --- diff --git a/src/content/docs/pt-br/pages/arquiteturas/edge-application/application-acceleration.mdx b/src/content/docs/pt-br/pages/arquiteturas/edge-application/application-acceleration.mdx index 11f81c04f6..2cc2fb58e5 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/edge-application/application-acceleration.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/edge-application/application-acceleration.mdx @@ -64,4 +64,4 @@ Esta solução é ideal para desenvolvedores e organizações que desejam aprimo ## ## Documentação relacionada -- [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/). +- [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/). diff --git a/src/content/docs/pt-br/pages/arquiteturas/edge-application/content-delivery.mdx b/src/content/docs/pt-br/pages/arquiteturas/edge-application/content-delivery.mdx index 58c25aedf8..119bfb92f3 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/edge-application/content-delivery.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/edge-application/content-delivery.mdx @@ -37,11 +37,11 @@ Esta solução é ideal para organizações que procuram modernizar sua estraté ## Componentes -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): crie uma aplicação para configurar políticas de entrega e cache, criar regras para automatizar atribuições de políticas de cache com base no tipo de conteúdo e determinar como o conteúdo é armazenado em cache. - - [Cache](/pt-br/documentacao/produtos/build/edge-application/edge-cache/): add-on global para armazenar conteúdo no edge. - - [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/): usado para personalizar regras de otimização de cache e chaves e cookies de cache com base em padrões estabelecidos. - - [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/): uma ferramenta para configurar os cenários em que uma política de cache específica é aplicada. - - [Image Processor](/pt-br/documentacao/produtos/build/edge-application/image-processor/): que permite a manipulação de imagens através da linha de requisição. +- [Applications](/pt-br/documentacao/produtos/build/applications/): crie uma aplicação para configurar políticas de entrega e cache, criar regras para automatizar atribuições de políticas de cache com base no tipo de conteúdo e determinar como o conteúdo é armazenado em cache. + - [Cache](/pt-br/documentacao/produtos/build/applications/cache/): add-on global para armazenar conteúdo no edge. + - [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/): usado para personalizar regras de otimização de cache e chaves e cookies de cache com base em padrões estabelecidos. + - [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/): uma ferramenta para configurar os cenários em que uma política de cache específica é aplicada. + - [Image Processor](/pt-br/documentacao/produtos/build/applications/image-processor/): que permite a manipulação de imagens através da linha de requisição. --- @@ -75,4 +75,4 @@ Esta solução é ideal para organizações que procuram modernizar sua estraté ## Documentação relacionada -- [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/). +- [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/). diff --git a/src/content/docs/pt-br/pages/arquiteturas/edge-enhanced/edge-enhanced.mdx b/src/content/docs/pt-br/pages/arquiteturas/edge-enhanced/edge-enhanced.mdx index eed454c1fb..bce3cea956 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/edge-enhanced/edge-enhanced.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/edge-enhanced/edge-enhanced.mdx @@ -41,10 +41,10 @@ Após este processo, a aplicação retorna uma resposta à requisição. ## Componentes -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): configure uma aplicação para definir políticas de entrega e cache, criar regras para automatizar atribuições de políticas de cache com base no tipo de conteúdo e determinar como o conteúdo é armazenado em cache. - - [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/): permite criar aplicações serverless orientadas a eventos, no edge da rede, mais próximas dos usuários. -- [Object Storage](/pt-br/documentacao/produtos/store/edge-storage/): um serviço de armazenamento escalável e seguro, projetado para integrar armazenamento de objetos com a Azion, usando o padrão S3 para operações de objetos. -- [SQL Database](/pt-br/documentacao/produtos/store/edge-sql/): uma solução SQL nativa de edge projetada para aplicações serverless. É totalmente compatível com ACID e utiliza o dialeto SQLite para fornecer um ambiente de desenvolvimento familiar, facilitando a integração rápida. +- [Applications](/pt-br/documentacao/produtos/build/applications/): configure uma aplicação para definir políticas de entrega e cache, criar regras para automatizar atribuições de políticas de cache com base no tipo de conteúdo e determinar como o conteúdo é armazenado em cache. + - [Functions](/pt-br/documentacao/produtos/build/applications/functions/): permite criar aplicações serverless orientadas a eventos, no edge da rede, mais próximas dos usuários. +- [Object Storage](/pt-br/documentacao/produtos/store/object-storage/): um serviço de armazenamento escalável e seguro, projetado para integrar armazenamento de objetos com a Azion, usando o padrão S3 para operações de objetos. +- [SQL Database](/pt-br/documentacao/produtos/store/sql-database/): uma solução SQL nativa de edge projetada para aplicações serverless. É totalmente compatível com ACID e utiliza o dialeto SQLite para fornecer um ambiente de desenvolvimento familiar, facilitando a integração rápida. --- @@ -54,7 +54,7 @@ Após este processo, a aplicação retorna uma resposta à requisição. - No [Console](https://console.azion.com), crie uma aplicação usando o botão **+ Create** na página inicial. - Usando a [API da Azion](https://api.azion.com/#9c61e0fd-e7aa-4a5f-b29e-7f9d71b98d5f) para criar uma aplicação. - Usando o [Azion CLI](/pt-br/documentacao/devtools/cli/create/#edge-applications) para criar e implantar uma aplicação. -2. [Crie uma function](/pt-br/documentacao/produtos/build/edge-application/edge-functions/#implementation) e [instancie](/pt-br/documentacao/produtos/guias/build/instanciar-edge-functions/) na aplicação recém-criada. +2. [Crie uma function](/pt-br/documentacao/produtos/build/applications/functions/#implementation) e [instancie](/pt-br/documentacao/produtos/guias/build/instanciar-functions/) na aplicação recém-criada. 3. Crie um domínio e associe-o à aplicação: - No Console, [crie um domínio](/pt-br/documentacao/produtos/guias/configurar-dominio/) usando o botão **+ Create** na página inicial. - Usando a [API da Azion](https://api.azion.com/#8eb89cc2-e58c-4c93-bb96-a4a30d96b818) para criar um domínio. diff --git a/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/prevencao-fraude-online.mdx b/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/prevencao-fraude-online.mdx index 8a14abf076..61923b7ee7 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/prevencao-fraude-online.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/prevencao-fraude-online.mdx @@ -55,17 +55,17 @@ Essa abordagem executa a detecção de fraude diretamente no edge, antes de atin ### Componentes - [Edge Network](https://www.azion.com/pt-br/produtos/nossa-rede/): uma arquitetura altamente distribuída que inclui edge nodes estrategicamente localizados. -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): permite criar aplicações que executam na Azion Edge Network. - - [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/): usado para personalizar regras de otimização de cache, chaves de cache e cookies com base em padrões estabelecidos. - - [Cache](/pt-br/documentacao/produtos/build/edge-application/edge-cache/): add-on global para armazenar conteúdo em cache no edge da rede. - - [Functions for Applications](/pt-br/documentacao/produtos/build/edge-application/edge-functions/): permite criar aplicações serverless baseadas em eventos, no edge da rede, mais próximas dos usuários. - - [Rules Engine for Applications](/pt-br/documentacao/produtos/build/edge-application/rules-engine/): permite configurar cenários onde políticas específicas são aplicadas, proporcionando controle granular sobre a entrega. -- [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/): fornece configurações principais para configurar sua instância, permitindo associá-la a domínios e ativar módulos para proteger usuários, aplicações e redes. - - [DDoS Protection](/pt-br/documentacao/produtos/secure/edge-firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. - - [Web Application Firewall (WAF)](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/): permite configurar proteção contra ataques e vulnerabilidades. - - [Bot Manager](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/): solução abrangente da Azion para gerenciamento de bots. - - [Functions no Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/edge-functions/): crie aplicações serverless baseadas em eventos no edge da rede, incluindo funções com seu próprio código-fonte de segurança. - - [Rules Engine para Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/rules-engine/): permite configurar cenários onde políticas específicas são aplicadas, proporcionando controle granular sobre a entrega. +- [Applications](/pt-br/documentacao/produtos/build/applications/): permite criar aplicações que executam na Azion Edge Network. + - [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/): usado para personalizar regras de otimização de cache, chaves de cache e cookies com base em padrões estabelecidos. + - [Cache](/pt-br/documentacao/produtos/build/applications/cache/): add-on global para armazenar conteúdo em cache no edge da rede. + - [Functions for Applications](/pt-br/documentacao/produtos/build/applications/functions/): permite criar aplicações serverless baseadas em eventos, no edge da rede, mais próximas dos usuários. + - [Rules Engine for Applications](/pt-br/documentacao/produtos/build/applications/rules-engine/): permite configurar cenários onde políticas específicas são aplicadas, proporcionando controle granular sobre a entrega. +- [Firewall](/pt-br/documentacao/produtos/secure/firewall/): fornece configurações principais para configurar sua instância, permitindo associá-la a domínios e ativar módulos para proteger usuários, aplicações e redes. + - [DDoS Protection](/pt-br/documentacao/produtos/secure/firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. + - [Web Application Firewall (WAF)](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/): permite configurar proteção contra ataques e vulnerabilidades. + - [Bot Manager](/pt-br/documentacao/produtos/secure/firewall/bot-manager/): solução abrangente da Azion para gerenciamento de bots. + - [Functions no Firewall](/pt-br/documentacao/produtos/secure/firewall/functions/): crie aplicações serverless baseadas em eventos no edge da rede, incluindo funções com seu próprio código-fonte de segurança. + - [Rules Engine para Firewall](/pt-br/documentacao/produtos/secure/firewall/rules-engine/): permite configurar cenários onde políticas específicas são aplicadas, proporcionando controle granular sobre a entrega. - Integrações do [Marketplace da Azion](/pt-br/documentacao/produtos/marketplace/) e integrações personalizadas: - Proteção contra bot. - [DataDome Bot Protection](https://console.azion.com/marketplace/solution/datadome/bot-protection/) @@ -89,23 +89,23 @@ Essa abordagem executa a detecção de fraude diretamente no edge, antes de atin 2. Configure suas integrações personalizadas com a plataforma da Azion. - Por exemplo, IdP para gerenciamento de usuários via protocolo [SAML](/pt-br/documentacao/produtos/guias/sso-google-saml/) ou [SCIM](/pt-br/documentacao/produtos/guias/microsoft-entra-provisionamento-automatizado-de-usuarios/). 3. [Configure a aplicação](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/), definindo origens, cache e outras configurações essenciais. - - [Configure um domínio personalizado](/pt-br/documentacao/produtos/build/edge-application/domains/) para sua aplicação. - - [Defina os critérios e comportamentos](/pt-br/documentacao/produtos/build/edge-application/rules-engine/) das regras do Rules Engine. Por exemplo: + - [Configure um domínio personalizado](/pt-br/documentacao/produtos/build/applications/domains/) para sua aplicação. + - [Defina os critérios e comportamentos](/pt-br/documentacao/produtos/build/applications/rules-engine/) das regras do Rules Engine. Por exemplo: - Inspecionar cabeçalhos HTTP. - Adicionar ou filtrar cookies. - Validar parâmetros de input. - Bloquear payloads maliciosos. - Redirecionamentos. - Reescrever a requisição. -4. [Crie e configure um firewall](/pt-br/documentacao/produtos/guias/secure/edge-firewall-definir-main-settings/). - - [Defina os critérios e comportamentos](/pt-br/documentacao/produtos/guias/secure/instanciar-edge-functions/) das regras do Rules Engine. Por exemplo: +4. [Crie e configure um firewall](/pt-br/documentacao/produtos/guias/secure/firewall-definir-main-settings/). + - [Defina os critérios e comportamentos](/pt-br/documentacao/produtos/guias/secure/instanciar-functions/) das regras do Rules Engine. Por exemplo: - Negar (Deny) ou descartar (Drop) requisições. - Bloquear IPs maliciosos. - Filtrar requisições HTTP específicas. - Aplicar limites de taxa (rate limits). - Executar functions com lógica personalizada. - - [Instancie functions](/pt-br/documentacao/produtos/guias/secure/instanciar-edge-functions/) e [integrações](/pt-br/documentacao/produtos/marketplace/integracoes/#edge-firewall-functions). -5. [Ative o Bot Manager](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/). + - [Instancie functions](/pt-br/documentacao/produtos/guias/secure/instanciar-functions/) e [integrações](/pt-br/documentacao/produtos/marketplace/integracoes/#edge-firewall-functions). +5. [Ative o Bot Manager](/pt-br/documentacao/produtos/secure/firewall/bot-manager/). - Entre em contato com a [equipe de Vendas](https://www.azion.com/pt-br/contate-vendas/) para mais detalhes sobre a assinatura do Bot Manager. 6. [Monitore sua aplicação](/pt-br/documentacao/produtos/observe/monitorar-aplicacoes/) e refine as regras. diff --git a/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx b/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx index 37cd73e68e..76cc3cb3b2 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx @@ -42,12 +42,12 @@ Esta solução é ideal para organizações que buscam proteger sua infraestrutu ### Componentes -- [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/): fornece as configurações principais para configurar sua instância e associá-la a domínios e ativar módulos. - - [DDoS Protection](/pt-br/documentacao/produtos/secure/edge-firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS quando ativado. - - [Web Application Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/): permite configurar proteção contra ataques e vulnerabilidades encontradas no OWASP Top 10 e bloquear requisições. - - [Network Shield](/pt-br/documentacao/produtos/secure/edge-firewall/network-layer-protection/): permite criar listas com endereços IP ou países com comportamento suspeito e restringir seu acesso. - - [Bot Manager](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/): identifica e classifica a requisição de acordo com a análise comportamental baseada em intenção. -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): executa sua aplicação na Azion Web Platform. +- [Firewall](/pt-br/documentacao/produtos/secure/firewall/): fornece as configurações principais para configurar sua instância e associá-la a domínios e ativar módulos. + - [DDoS Protection](/pt-br/documentacao/produtos/secure/firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS quando ativado. + - [Web Application Firewall](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/): permite configurar proteção contra ataques e vulnerabilidades encontradas no OWASP Top 10 e bloquear requisições. + - [Network Shield](/pt-br/documentacao/produtos/secure/firewall/network-shield/): permite criar listas com endereços IP ou países com comportamento suspeito e restringir seu acesso. + - [Bot Manager](/pt-br/documentacao/produtos/secure/firewall/bot-manager/): identifica e classifica a requisição de acordo com a análise comportamental baseada em intenção. +- [Applications](/pt-br/documentacao/produtos/build/applications/): executa sua aplicação na Azion Web Platform. --- @@ -66,7 +66,7 @@ Esta solução é ideal para organizações que buscam proteger sua infraestrutu - [A API da Azion](https://api.azion.com/#9c1cc0df-16a2-488e-8cfe-3f1238f47aeb). - [A CLI da Azion](/pt-br/documentacao/produtos/azion-cli/visao-geral/). -- [Crie um firewall](/pt-br/documentacao/produtos/guias/secure/edge-firewall-definir-main-settings/) e associe-o ao domínio configurado, para que todas as regras de segurança se apliquem a esse domínio específico. +- [Crie um firewall](/pt-br/documentacao/produtos/guias/secure/firewall-definir-main-settings/) e associe-o ao domínio configurado, para que todas as regras de segurança se apliquem a esse domínio específico. - Ative o módulo de DDoS Protection. - Ative o módulo de Web Application Firewall. - Ative o módulo de Network Shield. @@ -74,7 +74,7 @@ Esta solução é ideal para organizações que buscam proteger sua infraestrutu - Configure os tipos de ameaça e níveis de sensibilidade. - [Crie uma network list no Network Shield](/pt-br/documentacao/produtos/guias/blocklists-enderecos-ip-edge/). - Configure as IPs ou países que serão bloqueados. -- [Configure o Bot Manager](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/). +- [Configure o Bot Manager](/pt-br/documentacao/produtos/secure/firewall/bot-manager/). - Entre em contato com a [equipe de vendas](https://www.azion.com/pt-br/contate-vendas/) para mais detalhes sobre a assinatura do Bot Manager. - [Configure o Bot Manager Lite](/pt-br/documentacao/produtos/guias/bot-manager-lite/#configure-a-integracao) se você decidir usar essa versão. - [Crie regras no Rules Engine do Firewall](/pt-br/documentacao/produtos/guias/secure/trabalhar-com-rules-engine/). diff --git a/src/content/docs/pt-br/pages/arquiteturas/edge-native/edge-native-apps.mdx b/src/content/docs/pt-br/pages/arquiteturas/edge-native/edge-native-apps.mdx index d32e39d38f..6796149145 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/edge-native/edge-native-apps.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/edge-native/edge-native-apps.mdx @@ -30,9 +30,9 @@ Finalmente, a aplicação retorna via Azion Lib uma resposta contendo o resultad ## Componentes -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): este componente permite a configuração de políticas de entrega e de cache, atribuição automática de políticas de cache via regras baseadas no tipo de conteúdo, e determina o cacheamento do conteúdo. - - [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/): aplicações serverless, orientadas a eventos, em arquitetura distribuída que acomodam a lógica da sua aplicação, incluindo operações CRUD. -- [SQL Database](/pt-br/documentacao/produtos/store/edge-sql/): essa solução SQL serverless, construída nativamente para o edge, realiza operações de banco de dados da sua aplicação CRUD com menor latência. +- [Applications](/pt-br/documentacao/produtos/build/applications/): este componente permite a configuração de políticas de entrega e de cache, atribuição automática de políticas de cache via regras baseadas no tipo de conteúdo, e determina o cacheamento do conteúdo. + - [Functions](/pt-br/documentacao/produtos/build/applications/functions/): aplicações serverless, orientadas a eventos, em arquitetura distribuída que acomodam a lógica da sua aplicação, incluindo operações CRUD. +- [SQL Database](/pt-br/documentacao/produtos/store/sql-database/): essa solução SQL serverless, construída nativamente para o edge, realiza operações de banco de dados da sua aplicação CRUD com menor latência. - [Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/): uma interface de linha de comando (CLI) de código aberto que permite a interação com a Azion Web Platform pelo terminal. - [Azion Lib](https://github.com/aziontech/lib): um conjunto de ferramentas para interagir com vários serviços da Azion, incluindo produtos e utilitários. - [Azion Console](/pt-br/documentacao/produtos/guias/conhecendo-o-azion-console/): a interface onde você pode acessar todos os produtos disponíveis e suas configurações. diff --git a/src/content/docs/pt-br/pages/arquiteturas/jamstack/jamstack.mdx b/src/content/docs/pt-br/pages/arquiteturas/jamstack/jamstack.mdx index eead5ffcc5..0d286b528e 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/jamstack/jamstack.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/jamstack/jamstack.mdx @@ -35,8 +35,8 @@ Essa solução é ideal para organizações que buscam melhorar o desempenho do - [Azion Console](/pt-br/documentacao/produtos/guias/conhecendo-o-azion-console/): a interface onde você pode acessar todos os produtos disponíveis e suas configurações. - [Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/): uma interface de linha de comando (CLI) de código aberto que permite a interação com a Azion Web Platform usando um terminal. -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): um produto Azion que permite construir aplicações que são executadas no edge da Azion. -- [Object Storage](/pt-br/documentacao/produtos/store/edge-storage/): um serviço de armazenamento escalável e seguro projetado para integrar o armazenamento de objetos com a Azion Web Platform usando o padrão S3 para operações de objetos. +- [Applications](/pt-br/documentacao/produtos/build/applications/): um produto Azion que permite construir aplicações que são executadas no edge da Azion. +- [Object Storage](/pt-br/documentacao/produtos/store/object-storage/): um serviço de armazenamento escalável e seguro projetado para integrar o armazenamento de objetos com a Azion Web Platform usando o padrão S3 para operações de objetos. --- diff --git a/src/content/docs/pt-br/pages/arquiteturas/live-streaming-delivery/live-streming-delivery-com-hls.mdx b/src/content/docs/pt-br/pages/arquiteturas/live-streaming-delivery/live-streming-delivery-com-hls.mdx index e76d2162da..3f15df8aba 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/live-streaming-delivery/live-streming-delivery-com-hls.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/live-streaming-delivery/live-streming-delivery-com-hls.mdx @@ -40,8 +40,8 @@ Esta solução é ideal para provedores de conteúdo que necessitam de alta fide ### Componentes -- [Applications](/pt-br/documentacao/produtos/build/edge-application/) permite que você construa aplicações na Azion Web Platform e entregue seu conteúdo. - - [Cache](/pt-br/documentacao/produtos/build/edge-application/edge-cache/) permite que você configure como sua aplicação armazena em cache o conteúdo para reduzir a latência e aumentar as taxas de transferência. +- [Applications](/pt-br/documentacao/produtos/build/applications/) permite que você construa aplicações na Azion Web Platform e entregue seu conteúdo. + - [Cache](/pt-br/documentacao/produtos/build/applications/cache/) permite que você configure como sua aplicação armazena em cache o conteúdo para reduzir a latência e aumentar as taxas de transferência. - O componente de **ingestão** recebe sinal dos codificadores e distribui conteúdo no formato HLS. Ele funciona como a origem para a aplicação. --- @@ -59,5 +59,5 @@ Esta solução é ideal para provedores de conteúdo que necessitam de alta fide ## Documentação relacionada - [Azion Edge Network](https://www.azion.com/pt-br/produtos/nossa-rede/) -- [Cache Settings](/pt-br/documentacao/produtos/build/edge-application/cache-settings/) +- [Cache Settings](/pt-br/documentacao/produtos/build/applications/cache-settings/) - [Arquitetura de content delivery](/pt-br/documentacao/arquiteturas/edge-application/content-delivery/) diff --git a/src/content/docs/pt-br/pages/arquiteturas/orch/application-deliver-automation.mdx b/src/content/docs/pt-br/pages/arquiteturas/orch/application-deliver-automation.mdx index e357745c4d..96151e743f 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/orch/application-deliver-automation.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/orch/application-deliver-automation.mdx @@ -8,7 +8,7 @@ meta_tags: >- namespace: docs_arch_infra_auto_apps_delivery --- -O [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/) permite releases frequentes e confiáveis de aplicações através de orquestração. Esta documentação aborda a arquitetura e os passos para a entrega automatizada de aplicações usando o Azion Orchestrator, garantindo desempenho ótimo e operações simplificadas. +O [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/) permite releases frequentes e confiáveis de aplicações através de orquestração. Esta documentação aborda a arquitetura e os passos para a entrega automatizada de aplicações usando o Azion Orchestrator, garantindo desempenho ótimo e operações simplificadas. --- @@ -112,9 +112,9 @@ HTML com a lista de produtos: ## Componentes - [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/): interface para gerenciar e monitorar aplicações e edge services. -- [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/): automatiza o deploy e gerenciamento de aplicações em edge nodes. -- [Edge Nodes](/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-node/): recursos de computação distribuídos que processam dados mais próximos à fonte. -- [Edge Services](/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-services/): permite a criação e customização de serviços para orquestração em edge nodes. +- [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/): automatiza o deploy e gerenciamento de aplicações em edge nodes. +- [Edge Nodes](/pt-br/documentacao/produtos/deploy/orchestrator/edge-node/): recursos de computação distribuídos que processam dados mais próximos à fonte. +- [Edge Services](/pt-br/documentacao/produtos/deploy/orchestrator/edge-services/): permite a criação e customização de serviços para orquestração em edge nodes. --- @@ -135,6 +135,6 @@ HTML com a lista de produtos: ## Documentação Relacionada - [Visão Geral do Deploy](/pt-br/documentacao/produtos/deploy/visao-geral/) -- [Visão Geral do Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/) +- [Visão Geral do Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/) diff --git a/src/content/docs/pt-br/pages/arquiteturas/orch/infra-automation.mdx b/src/content/docs/pt-br/pages/arquiteturas/orch/infra-automation.mdx index 8e6b9e42c4..921f8e9c96 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/orch/infra-automation.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/orch/infra-automation.mdx @@ -8,7 +8,7 @@ meta_tags: >- namespace: docs_arch_infra_auto_apps --- -O [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/) permite que você automatize e gerencie sua infraestrutura de forma eficiente. Ao utilizar a [Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/), você pode realizar tarefas como implantação, monitoramento e atualizações de aplicações. Esta documentação fornece uma visão aprofundada sobre a arquitetura e os passos para implementar a automação de infraestrutura usando o Azion Orchestrator, ajudando você a alcançar desempenho ótimo e operações simplificadas. +O [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/) permite que você automatize e gerencie sua infraestrutura de forma eficiente. Ao utilizar a [Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/), você pode realizar tarefas como implantação, monitoramento e atualizações de aplicações. Esta documentação fornece uma visão aprofundada sobre a arquitetura e os passos para implementar a automação de infraestrutura usando o Azion Orchestrator, ajudando você a alcançar desempenho ótimo e operações simplificadas. --- @@ -32,9 +32,9 @@ Este fluxo pressupõe que um serviço foi criado para instalar a Azion CLI no ed ## Componentes - [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/): interface para gerenciar e monitorar aplicações e serviços de edge. -- [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/): automatiza a implantação e gerenciamento de aplicações em edge nodes. -- [Edge Nodes](/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-node/): recursos de computação distribuídos que processam dados mais próximos à fonte. -- [Edge Services](/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-services/): permite a criação e customização de serviços para orquestração em edge nodes. +- [Azion Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/): automatiza a implantação e gerenciamento de aplicações em edge nodes. +- [Edge Nodes](/pt-br/documentacao/produtos/deploy/orchestrator/edge-node/): recursos de computação distribuídos que processam dados mais próximos à fonte. +- [Edge Services](/pt-br/documentacao/produtos/deploy/orchestrator/edge-services/): permite a criação e customização de serviços para orquestração em edge nodes. --- ## Implementação @@ -54,4 +54,4 @@ Este fluxo pressupõe que um serviço foi criado para instalar a Azion CLI no ed ## Documentação relacionada - [Visão geral do deploy](/pt-br/documentacao/produtos/deploy/visao-geral/) -- [Visão geral do Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/) +- [Visão geral do Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/) diff --git a/src/content/docs/pt-br/pages/arquiteturas/security-automation/security-automation.mdx b/src/content/docs/pt-br/pages/arquiteturas/security-automation/security-automation.mdx index 5ab1b2f84b..c9ad8df974 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/security-automation/security-automation.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/security-automation/security-automation.mdx @@ -34,7 +34,7 @@ Nesse contexto, sistemas autônomos operam com mínima ou nenhuma intervenção 2. No edge node, o Firewall processa o pedido e executa as configurações de segurança: - O DDoS Protection verifica possíveis ataques DDoS ou DoS, bloqueando ou permitindo o pedido conforme necessário. Está automaticamente habilitado em todas as contas. - O Firewall Rules Engine identifica se há regras do WAF e do Network Shield e executa os comportamentos correspondentes. - - Qualquer function configurada e instanciada é executada. Leia mais sobre como [automatizar a segurança com Functions da Azion](/pt-br/documentacao/produtos/secure/automarizar/functions/). + - Qualquer function configurada e instanciada é executada. Leia mais sobre como [automatizar a segurança com Functions da Azion](/pt-br/documentacao/produtos/secure/automatizar/functions/). - O Bot Manager também analisa o pedido usando aprendizado de máquina, análise comportamental baseada em intenção e algoritmos avançados. 3. Se a requisição não corresponder a uma regra do Firewall e não for bloqueada, a requisição continua o fluxo para o Applications. - O Application Rules Engine identifica se há regras relacionadas a cache, otimização de imagens, cookies e redirecionamentos, entre outros. @@ -45,21 +45,21 @@ Nesse contexto, sistemas autônomos operam com mínima ou nenhuma intervenção ### Componentes - Interfaces da Azion: [Console](/pt-br/documentacao/produtos/guias/conhecendo-o-azion-console/), [API](https://api.azion.com/) ou [CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/). -- [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/) fornece as principais configurações para configurar sua instância, permitindo que você a associe a domínios e ative módulos para proteger usuários, aplicações e redes. - - [DDoS Protection](/pt-br/documentacao/produtos/secure/edge-firewall/ddos-protection/) detecta e mitiga ataques DDoS e DoS. - - [Rules Engine para Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/rules-engine/) permite que você defina as condições (Critéria) e omportamentos (behaviors) para suas regras. Se os critérios forem atendidos, os comportamentos serão executados. - - [Functions no Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/edge-functions/) são funções JavaScript que são executadas na borda da rede, próximas aos usuários, e ajudam a proteger suas aplicações aplicando a lógica que seu negócio requer. - - [Bot Manager](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/) identifica e classifica o pedido de acordo com a análise comportamental baseada em intenção. Este add-on é a solução abrangente da Azion para gerenciamento de bots. Uma [versão lite](/pt-br/documentacao/produtos/guias/bot-manager-lite/) também está disponível no Marketplace. +- [Firewall](/pt-br/documentacao/produtos/secure/firewall/) fornece as principais configurações para configurar sua instância, permitindo que você a associe a domínios e ative módulos para proteger usuários, aplicações e redes. + - [DDoS Protection](/pt-br/documentacao/produtos/secure/firewall/ddos-protection/) detecta e mitiga ataques DDoS e DoS. + - [Rules Engine para Firewall](/pt-br/documentacao/produtos/secure/firewall/rules-engine/) permite que você defina as condições (Critéria) e omportamentos (behaviors) para suas regras. Se os critérios forem atendidos, os comportamentos serão executados. + - [Functions no Firewall](/pt-br/documentacao/produtos/secure/firewall/functions/) são funções JavaScript que são executadas na borda da rede, próximas aos usuários, e ajudam a proteger suas aplicações aplicando a lógica que seu negócio requer. + - [Bot Manager](/pt-br/documentacao/produtos/secure/firewall/bot-manager/) identifica e classifica o pedido de acordo com a análise comportamental baseada em intenção. Este add-on é a solução abrangente da Azion para gerenciamento de bots. Uma [versão lite](/pt-br/documentacao/produtos/guias/bot-manager-lite/) também está disponível no Marketplace. --- ## Implementação 1. Crie uma [aplicação](/pt-br/documentacao/produtos/guias/build/criar-uma-aplicacao/). -2. Configure um [firewall](/pt-br/documentacao/produtos/guias/secure/edge-firewall-definir-main-settings/). +2. Configure um [firewall](/pt-br/documentacao/produtos/guias/secure/firewall-definir-main-settings/). 3. Defina todas as suas regras e configurações: - - [Rules Engine rules](/pt-br/documentacao/produtos/secure/edge-firewall/rules-engine/), usando critérios e comportamentos para definir como a requisição é tratada. Inclui regras relacionadas a network lists, WAF Rules, Custom Allowed Rules, rate limits, respostas personalizadas, bloqueio e drop de requisições e execução de funções. - - [Functions](/pt-br/documentacao/produtos/secure/edge-firewall/edge-functions/), criando seu próprio código ou usando [integrações de Firewall do Marketplace](/pt-br/documentacao/produtos/marketplace/integracoes/#edge-firewall-functions). + - [Rules Engine rules](/pt-br/documentacao/produtos/secure/firewall/rules-engine/), usando critérios e comportamentos para definir como a requisição é tratada. Inclui regras relacionadas a network lists, WAF Rules, Custom Allowed Rules, rate limits, respostas personalizadas, bloqueio e drop de requisições e execução de funções. + - [Functions](/pt-br/documentacao/produtos/secure/firewall/functions/), criando seu próprio código ou usando [integrações de Firewall do Marketplace](/pt-br/documentacao/produtos/marketplace/integracoes/#edge-firewall-functions). 4. Habilite o Bot Manager: - Entre em contato com a [equipe de vendas](https://www.azion.com/pt-br/contate-vendas/) para mais detalhes sobre a subscrição do Bot Manager. - Configure o [Bot Manager Lite](/pt-br/documentacao/produtos/guias/bot-manager-lite/) se você decidiu usar esta versão. @@ -67,7 +67,7 @@ Nesse contexto, sistemas autônomos operam com mínima ou nenhuma intervenção Quando salvas, as configurações são replicadas em todos os edge nodes da rede. Sempre que uma requisição chega à plataforma da Azion, as regras e configurações são executadas, e o sistema processa a requisição conforme necessário. Você pode usar produtos Observe para monitorar e rastrear o tráfego. :::tip -Você também pode usar o [Azion Terraform provider](/pt-br/documentacao/produtos/secure/automarizar/terraform/) para tarefas de automação de segurança. +Você também pode usar o [Azion Terraform provider](/pt-br/documentacao/produtos/secure/automatizar/terraform/) para tarefas de automação de segurança. ::: --- diff --git a/src/content/docs/pt-br/pages/arquiteturas/security-modernization/security-modernization-com-edge-computing.mdx b/src/content/docs/pt-br/pages/arquiteturas/security-modernization/security-modernization-com-edge-computing.mdx index c4490329c0..5f3005a589 100644 --- a/src/content/docs/pt-br/pages/arquiteturas/security-modernization/security-modernization-com-edge-computing.mdx +++ b/src/content/docs/pt-br/pages/arquiteturas/security-modernization/security-modernization-com-edge-computing.mdx @@ -41,14 +41,14 @@ Este caso de uso é ideal para organizações que buscam construir uma forte pre ### Componentes -- [Applications](/pt-br/documentacao/produtos/build/edge-application/): sua aplicação em execução na Azion Web Platform. -- [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/): executa seus módulos e regras de segurança. - - [DDoS Protection](/pt-br/documentacao/produtos/secure/edge-firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. - - [Web Application Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/): permite que você configure a proteção contra ataques e vulnerabilidades. - - [Network Shield](/pt-br/documentacao/produtos/secure/edge-firewall/network-layer-protection/): permite que você crie listas com endereços IP ou países com comportamento suspeito e restrinja seu acesso. - - [Functions](/pt-br/documentacao/produtos/secure/edge-firewall/edge-functions/): funções sem servidor que são executadas no Azion Runtime com baixa latência, trazendo o poder operacional e o processamento de segurança mais próximos do usuário final. - - [Rules Engine](/pt-br/documentacao/produtos/secure/edge-firewall/rules-engine/): permite que você crie lógica de segurança personalizada por meio de regras para bloquear ou permitir solicitações e usuários. - - [Origin Shield](/pt-br/documentacao/produtos/secure/edge-firewall/#extensao-origin-shield): cria um perímetro de segurança para sua infraestrutura de origem. +- [Applications](/pt-br/documentacao/produtos/build/applications/): sua aplicação em execução na Azion Web Platform. +- [Firewall](/pt-br/documentacao/produtos/secure/firewall/): executa seus módulos e regras de segurança. + - [DDoS Protection](/pt-br/documentacao/produtos/secure/firewall/ddos-protection/): detecta e mitiga ataques DDoS e DoS. + - [Web Application Firewall](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/): permite que você configure a proteção contra ataques e vulnerabilidades. + - [Network Shield](/pt-br/documentacao/produtos/secure/firewall/network-shield/): permite que você crie listas com endereços IP ou países com comportamento suspeito e restrinja seu acesso. + - [Functions](/pt-br/documentacao/produtos/secure/firewall/functions/): funções sem servidor que são executadas no Azion Runtime com baixa latência, trazendo o poder operacional e o processamento de segurança mais próximos do usuário final. + - [Rules Engine](/pt-br/documentacao/produtos/secure/firewall/rules-engine/): permite que você crie lógica de segurança personalizada por meio de regras para bloquear ou permitir solicitações e usuários. + - [Origin Shield](/pt-br/documentacao/produtos/secure/firewall/#extensao-origin-shield): cria um perímetro de segurança para sua infraestrutura de origem. - [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/), [Real-Time Metrics](/pt-br/documentacao/produtos/observe/real-time-metrics/), [Real-Time Events](/pt-br/documentacao/produtos/observe/real-time-events/) e [GraphQL API](/pt-br/documentacao/devtools/graphql-api/visao-geral/): permitem que você monitore toda a atividade do Firewall e dos módulos. --- @@ -68,7 +68,7 @@ Este caso de uso é ideal para organizações que buscam construir uma forte pre - [A API da Azion](https://api.azion.com/#9c1cc0df-16a2-488e-8cfe-3f1238f47aeb) - [A Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/) -2. [Crie um firewall](/pt-br/documentacao/produtos/guias/secure/edge-firewall-definir-main-settings/) e associe-o ao domínio configurado, para que todas as regras de segurança se apliquem a esse domínio específico. +2. [Crie um firewall](/pt-br/documentacao/produtos/guias/secure/firewall-definir-main-settings/) e associe-o ao domínio configurado, para que todas as regras de segurança se apliquem a esse domínio específico. - Habilite os módulos Web Application Firewall, Network Shield e Functions. 3. [Crie um rule set do WAF](/pt-br/documentacao/produtos/guias/secure/criar-waf-rule-set/), configurando o de tipo de ameaça e os níveis de sensibilidade. 4. [Crie uma network list](/pt-br/documentacao/produtos/guias/blocklists-enderecos-ip-edge/) no Network Shield. diff --git a/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/multiple-origins.mdx b/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/multiple-origins.mdx index ae25043de5..edd1c8b131 100644 --- a/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/multiple-origins.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/multiple-origins.mdx @@ -18,19 +18,19 @@ import Code from '~/components/Code/Code.astro' -Quando você [cria uma application](/pt-br/documentacao/produtos/comecar-com-um-template/), você precisa definir uma origem. No entanto, infraestruturas mais complexas e robustas podem precisar de múltiplas origens para a mesma aplicação. O módulo [Load Balancer](/pt-br/documentacao/produtos/secure/connector/load-balancer/) permite que você use algoritmos de balanceamento de carga para gerenciar altos números de acesso e controlar os comportamentos de sua origem. +Quando você [cria uma application](/pt-br/documentacao/produtos/comecar-com-um-template/), você precisa definir uma origem. No entanto, infraestruturas mais complexas e robustas podem precisar de múltiplas origens para a mesma aplicação. O módulo [Load Balancer](/pt-br/documentacao/produtos/secure/connectors/load-balancer/) permite que você use algoritmos de balanceamento de carga para gerenciar altos números de acesso e controlar os comportamentos de sua origem. :::caution[atenção] Se o **Load Balancer** estiver ativado, a transferência de dados pode gerar custos relacionados ao uso. Verifique a [página de preços](/pt-br/documentacao/produtos/precos/) para mais informações. ::: -Existem instruções separadas para API v3 usando configurações legadas de [Origin](/pt-br/documentacao/produtos/build/edge-application/origins/) e API v4 usando o novo produto [Connector](/pt-br/documentacao/produtos/secure/edge-connector/). +Existem instruções separadas para API v3 usando configurações legadas de [Origin](/pt-br/documentacao/produtos/build/applications/origins/) e API v4 usando o novo produto [Connector](/pt-br/documentacao/produtos/secure/connectors/). :::tip Se você não tem certeza de quais etapas se aplicam à sua conta, veja [o guia Verificar migração da conta](/pt-br/documentacao/produtos/guias/verificar-migracao-conta/) para determinar se sua conta já foi migrada. ::: -Os seguintes passos irão descrever um caso de uso onde a default origin deve ser do tipo Load Balancer com o [algoritmo Round-Robin](/pt-br/documentacao/produtos/secure/connector/load-balancer/#metodo-de-balanceamento). Sinta-se à vontade para interpretar e modificar as instruções passo a passo de acordo com o seu caso de uso específico. +Os seguintes passos irão descrever um caso de uso onde a default origin deve ser do tipo Load Balancer com o [algoritmo Round-Robin](/pt-br/documentacao/produtos/secure/connectors/load-balancer/#metodo-de-balanceamento). Sinta-se à vontade para interpretar e modificar as instruções passo a passo de acordo com o seu caso de uso específico. As seguintes regras de negócio de diferentes servidores de origem devem ser configuradas com balanceamento de carga: diff --git a/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/processar-imagens.mdx b/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/processar-imagens.mdx index 2b870276c0..741ff0488e 100644 --- a/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/processar-imagens.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/configuracoes-avancadas/processar-imagens.mdx @@ -15,10 +15,10 @@ import Code from '~/components/Code/Code.astro' -Através do módulo [Image Processor](/pt-br/documentacao/produtos/build/edge-application/image-processor/), você pode ajustar tamanhos de imagem, adicionar filtros e marcas d'água, ou converter formatos para adequar a entrega de conteúdo mais eficiente, economia de largura de banda e reduzir os custos de armazenamento de objetos. Essas alterações podem ser aplicadas diretamente na URL da sua imagem, anexando queries `ims` à URL da imagem. +Através do módulo [Image Processor](/pt-br/documentacao/produtos/build/applications/image-processor/), você pode ajustar tamanhos de imagem, adicionar filtros e marcas d'água, ou converter formatos para adequar a entrega de conteúdo mais eficiente, economia de largura de banda e reduzir os custos de armazenamento de objetos. Essas alterações podem ser aplicadas diretamente na URL da sua imagem, anexando queries `ims` à URL da imagem. :::caution[atenção] -Se você deseja otimizar suas imagens, além do módulo **Image Processor**, a ativação do módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/) é recomendada para eficiência de cache. Se esses módulos estiverem ativados, imagens processadas e transferência de dados podem gerar custos relacionados ao uso. Consulte a [página de preços](/pt-br/documentacao/produtos/precos/) para mais informações. +Se você deseja otimizar suas imagens, além do módulo **Image Processor**, a ativação do módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/) é recomendada para eficiência de cache. Se esses módulos estiverem ativados, imagens processadas e transferência de dados podem gerar custos relacionados ao uso. Consulte a [página de preços](/pt-br/documentacao/produtos/precos/) para mais informações. ::: :::tip @@ -39,12 +39,12 @@ Nesse guia existem instruções separadas para API v3 e API v4. Se você não te 4. Clique no botão **Save**. 5. Navegue até a aba **Cache Settings**. 6. Clique no botão **+ Cache Setting**. -7. Na seção **Cache Expiration Policies**, configure a [política de expiração](/pt-br/documentacao/produtos/build/edge-application/cache-settings/#browser-cache-settings) para suas imagens. +7. Na seção **Cache Expiration Policies**, configure a [política de expiração](/pt-br/documentacao/produtos/build/applications/cache-settings/#browser-cache-settings) para suas imagens. - Para imagens, você pode adicionar valores de tempo de vida (TTL) maiores, como `1296000` segundos (15 dias). 1. Na seção **Advanced Cache Key**, escolha uma das seguintes opções: - **O conteúdo varia por alguns campos de Query String (Allowlist)**: se você deseja listar todos os campos na query string que identificarão suas imagens. **Image Processor** usa o campo *ims*, então este deve ser incluído na lista como um dos campos necessários para sua aplicação de gerenciamento de imagens. - **O conteúdo varia pela Query String, exceto por alguns campos (Blocklist)**: se você deseja listar apenas aqueles campos na query string que devem ser ignorados para identificar os objetos em seu cache. Neste caso, garante que o campo *ims* será removido da lista. - - **O conteúdo varia por todos os campos de Query String**: se você não sabe ou não tem certeza sobre quais campos listar na query string porque não é responsável por todo o conteúdo no cache ou não tem [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/) ativado. + - **O conteúdo varia por todos os campos de Query String**: se você não sabe ou não tem certeza sobre quais campos listar na query string porque não é responsável por todo o conteúdo no cache ou não tem [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/) ativado. 2. Clique no botão **Save**. Agora você precisa indicar o que acionará a ativação do módulo **Image Processor**. Você pode criar uma regra que identifica formatos de imagem da seguinte maneira: @@ -79,7 +79,7 @@ Para confirmar se sua imagem está sendo otimizada, [inspecione a página](https -1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar os módulos [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/) e [Image Processor](/pt-br/documentacao/produtos/build/edge-application/image-processor/): +1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar os módulos [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/) e [Image Processor](/pt-br/documentacao/produtos/build/applications/image-processor/): -1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar os módulos [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/) e [Image Processor](/pt-br/documentacao/produtos/build/edge-application/image-processor/): +1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar os módulos [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/) e [Image Processor](/pt-br/documentacao/produtos/build/applications/image-processor/): ' \ diff --git a/src/content/docs/pt-br/pages/build-jornada/contrua-uma-aplicacao/crie-uma-aplicacao.mdx b/src/content/docs/pt-br/pages/build-jornada/contrua-uma-aplicacao/crie-uma-aplicacao.mdx index 46e56bb9b5..d784fe3cd7 100644 --- a/src/content/docs/pt-br/pages/build-jornada/contrua-uma-aplicacao/crie-uma-aplicacao.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/contrua-uma-aplicacao/crie-uma-aplicacao.mdx @@ -11,7 +11,7 @@ meta_tags: >- namespace: docs_guides_build_edge_application --- -[Application](/pt-br/documentacao/produtos/build/edge-application/) permite criar novas aplicações e definir as variáveis de suas aplicações. Você também pode automatizar comportamentos no nível de requisição-resposta. +[Application](/pt-br/documentacao/produtos/build/applications/) permite criar novas aplicações e definir as variáveis de suas aplicações. Você também pode automatizar comportamentos no nível de requisição-resposta. Azion fornece uma variedade de ferramentas para criar e configurar suas applications: @@ -39,7 +39,7 @@ Após definir as configurações iniciais, você pode modificar o comportamento - **Cache settings**: [ajuste as configurações de cache](/pt-br/documentacao/produtos/guias/build/ajustar-cache-settings/) para reduzir a carga nos servidores de origem e acelerar a entrega. Defina valores como expiração de cache de browser e edge, segmentação de arquivos maiores, cache keys e entrega adaptada com base em dispositivos. - **Connectors**: [ajuste suas configurações de origem](/pt-br/documentacao/produtos/guias/build/definir-origens/) para atender às necessidades de sua aplicação e defina os valores do cabeçalho `Host` e endereço de origem. - **Device groups**: [agrupe usuários finais com base em seus dispositivos](/pt-br/documentacao/produtos/guias/build/criar-device-groups/), sistemas operacionais ou navegadores com informações fornecidas pelo cabeçalho `User-Agent`. -- **Functions**: [instancie functions](/pt-br/documentacao/produtos/guias/build/instanciar-edge-functions/) para minimizar o uso de recursos processando no edge. +- **Functions**: [instancie functions](/pt-br/documentacao/produtos/guias/build/instanciar-functions/) para minimizar o uso de recursos processando no edge. Algumas variáveis podem já ter sido criadas por padrão quando você construiu sua aplicação pela primeira vez. Você pode editar suas configurações padrão ou criar novas, se necessário. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/devtools/tools-code-editor.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/devtools/tools-code-editor.mdx index 884b7a75ec..5ab59cea9e 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/devtools/tools-code-editor.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/devtools/tools-code-editor.mdx @@ -12,7 +12,7 @@ namespace: documentation_dev_with_azion_code_editor import LinkButton from 'azion-webkit/linkbutton' - + O editor de código da Azion para functions é amigável ao usuário e baseado no editor de código Monaco, conhecido através do VS Code, o que torna fácil para aqueles familiarizados com o VS Code se adaptarem. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-angular.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-angular.mdx index c28b941a92..6f49aff062 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-angular.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-angular.mdx @@ -26,7 +26,7 @@ Saiba mais sobre o [Angular](https://angular.io/docs). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente da Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-astro.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-astro.mdx index 9a0ac5fd73..c28b73e19a 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-astro.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-astro.mdx @@ -28,7 +28,7 @@ Saiba mais sobre o [Astro](https://docs.astro.build/en/getting-started/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-docusaurus.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-docusaurus.mdx index 7e31d46144..3620e0adbf 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-docusaurus.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-docusaurus.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Docusaurus](https://docusaurus.io/docs/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-eleventy.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-eleventy.mdx index 310f3d8b67..3c5b246082 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-eleventy.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-eleventy.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Eleventy](https://www.11ty.dev/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-gatsby.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-gatsby.mdx index 9b3052c6f4..f1a7bd12da 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-gatsby.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-gatsby.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Gatsby](https://www.gatsbyjs.com/docs/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hexo.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hexo.mdx index 6163f5bb7a..f276c0ab57 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hexo.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hexo.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Hexo](https://hexo.io/docs/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hono.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hono.mdx index 6781ae2f64..783cb33c31 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hono.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hono.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Hono](https://hono.dev/docs/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hugo.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hugo.mdx index 6680cdce1a..1ce5de55b2 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hugo.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-hugo.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Hugo](https://gohugo.io/documentation/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-jekyll.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-jekyll.mdx index 0dca4616c4..125901f608 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-jekyll.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-jekyll.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Jekyll](https://jekyllrb.com/docs/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-next.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-next.mdx index 4f54f44c74..6938e7d1cf 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-next.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-next.mdx @@ -20,7 +20,7 @@ O Next.js é um framework React flexível que permite a criação de aplicaçõe Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. @@ -159,4 +159,4 @@ Aguarde alguns minutos para que a propagação ocorra e, em seguida, acesse a su - + diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-overview.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-overview.mdx index 86c29c78dd..ab2764d616 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-overview.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-overview.mdx @@ -39,6 +39,6 @@ Você pode conferir a lista completa de frameworks suportados e algumas informa - +
\ No newline at end of file diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-react.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-react.mdx index ea49362a24..bd353376de 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-react.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-react.mdx @@ -28,7 +28,7 @@ Saiba mais sobre o [React](https://react.dev/). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente da Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-svelte.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-svelte.mdx index 54a8a5edf8..9f70b69f88 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-svelte.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-svelte.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Svelte](https://svelte.dev/docs/introduction). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vite.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vite.mdx index 7dc720d443..ded923c117 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vite.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vite.mdx @@ -27,7 +27,7 @@ Saiba mais sobre o [Vite](https://vitejs.dev/) e [VitePress](https://vitepress.d Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vue.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vue.mdx index 066777b106..81d8c497fb 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vue.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-frameworks/framework-vue.mdx @@ -29,7 +29,7 @@ Saiba mais sobre o [Vue](https://vuejs.org/guide/introduction.html). Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o produto [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente do Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-javascript.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-javascript.mdx index e90057e6c6..e269261e60 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-javascript.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-javascript.mdx @@ -29,7 +29,7 @@ As functions funcionam sobre o [Azion Runtime](/pt-br/documentacao/runtime/visao ## Editor de Código -[O Functions Code Editor](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/code-editor/) fornece uma experiência de desenvolvimento semelhante à que os desenvolvedores estão acostumados. A [integração entre Functions e ChatGPT](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/ai-integration/) ajuda você a escrever, refatorar e revisar o código. +[O Functions Code Editor](/pt-br/documentacao/produtos/applications/functions/runtime-api/code-editor/) fornece uma experiência de desenvolvimento semelhante à que os desenvolvedores estão acostumados. A [integração entre Functions e ChatGPT](/pt-br/documentacao/produtos/applications/functions/runtime-api/ai-integration/) ajuda você a escrever, refatorar e revisar o código. --- @@ -44,7 +44,7 @@ Para desenvolver sua primeira function para Applications: **Escrever uma function** -Primeiro, as functions para Applications funcionam com base em um [fetch event](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-apis/javascript/fetch/). Ele é inicializado com uma função `addEventListener`, passando `fetch` como o tipo de evento e um evento. Por exemplo: +Primeiro, as functions para Applications funcionam com base em um [fetch event](/pt-br/documentacao/produtos/applications/functions/runtime-apis/javascript/fetch/). Ele é inicializado com uma função `addEventListener`, passando `fetch` como o tipo de evento e um evento. Por exemplo: ```javascript addEventListener('fetch', event => { @@ -85,7 +85,7 @@ Neste exemplo, a resposta será o conteúdo HTML, declarado anteriormente pelo c Depois de escrever suas functions, você pode visualizar a resposta e inspecionar o código. O preview simula uma requisição e essa simulação pode ser alterada para atender às necessidades do desenvolvedor. -Saiba mais sobre o [Preview Deployment](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/preview-deployment/). +Saiba mais sobre o [Preview Deployment](/pt-br/documentacao/produtos/applications/functions/runtime-api/preview-deployment/). É possível debugar as funções através de: @@ -98,6 +98,6 @@ Saiba mais sobre o [Preview Deployment](/pt-br/documentacao/produtos/edge-applic Depois de salvar sua function, é necessário instanciá-la em uma application. -Saiba mais sobre como [instanciar uma function em uma application](/pt-br/documentacao/produtos/guias/build/instanciar-edge-functions/). +Saiba mais sobre como [instanciar uma function em uma application](/pt-br/documentacao/produtos/guias/build/instanciar-functions/). --- \ No newline at end of file diff --git a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-wasm.mdx b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-wasm.mdx index 58ae8548e7..92ea39a3b1 100644 --- a/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-wasm.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/desenvolva-com-azion/guias-linguagens/lang-wasm.mdx @@ -13,7 +13,7 @@ namespace: documentation_dev_with_azion_lang_wasm -Saiba mais sobre o processo necessário para a criação de uma [function](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) que utiliza uma função originada de um arquivo [WebAssembly](https://webassembly.org/getting-started/developers-guide/). +Saiba mais sobre o processo necessário para a criação de uma [function](/pt-br/documentacao/produtos/build/applications/functions/) que utiliza uma função originada de um arquivo [WebAssembly](https://webassembly.org/getting-started/developers-guide/). 1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Functions**. 2. Clique em **+ Function**. @@ -70,7 +70,7 @@ Um [código WAT](https://developer.mozilla.org/en-US/docs/WebAssembly/Understand 6. Clique no botão **Save**. -Agora, a função está pronta para ser instanciada em uma application. Veja como [instanciar e executar as funções em sua application](/pt-br/documentacao/produtos/guias/build/instanciar-edge-functions/). +Agora, a função está pronta para ser instanciada em uma application. Veja como [instanciar e executar as funções em sua application](/pt-br/documentacao/produtos/guias/build/instanciar-functions/). A saída esperada da função recém-criada é semelhante a: diff --git a/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/cache-settings.mdx b/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/cache-settings.mdx index b3b9cf2ab4..4bb26b3d00 100644 --- a/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/cache-settings.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/cache-settings.mdx @@ -13,10 +13,10 @@ permalink: /documentacao/produtos/guias/build/ajustar-cache-settings/ import Tabs from '~/components/tabs/Tabs' -Utilize as capacidades do [Cache](/pt-br/documentacao/produtos/build/edge-application/cache-settings/) para configurar as [políticas de cache](/pt-br/documentacao/produtos/build/edge-application/cache-settings/) da sua application, incluindo valores de expiração no edge ou no navegador, otimização de arquivos grandes para dividir conteúdos em partes menores e segmentação de cache key com base em métodos HTTP, query strings, cookies ou grupos de dispositivos. +Utilize as capacidades do [Cache](/pt-br/documentacao/produtos/build/applications/cache-settings/) para configurar as [políticas de cache](/pt-br/documentacao/produtos/build/applications/cache-settings/) da sua application, incluindo valores de expiração no edge ou no navegador, otimização de arquivos grandes para dividir conteúdos em partes menores e segmentação de cache key com base em métodos HTTP, query strings, cookies ou grupos de dispositivos. :::caution[atenção] -Algumas funcionalidades de cache requerem que o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/) esteja ativo. Se o **Application Accelerator** estiver ativado, a transferência de dados pode gerar custos relacionados ao uso. Consulte a [página de preços](/pt-br/documentacao/produtos/precos/) para mais informações. +Algumas funcionalidades de cache requerem que o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/) esteja ativo. Se o **Application Accelerator** estiver ativado, a transferência de dados pode gerar custos relacionados ao uso. Consulte a [página de preços](/pt-br/documentacao/produtos/precos/) para mais informações. ::: --- @@ -57,9 +57,9 @@ Se a sua aplicação não estiver enviando cabeçalhos `Cache-Control` e `Expire 4. Adicione o TTL em segundos no campo **Max Age (seconds)**. Por exemplo: `864000` = 10 dias. :::note -Os valores máximo e padrão de TTL para o edge devem estar entre `60` e `31536000` segundos (1 ano). Se você tiver o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/) ativado, você pode definir este valor para um mínimo de `0`. Além disso, se você tiver o módulo [Cache](/pt-br/documentacao/produtos/build/edge-application/tiered-cache/) ativado e desejar manter o cache na camada de Cache, você deve definir o TTL para pelo menos `3` segundos. +Os valores máximo e padrão de TTL para o edge devem estar entre `60` e `31536000` segundos (1 ano). Se você tiver o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/) ativado, você pode definir este valor para um mínimo de `0`. Além disso, se você tiver o módulo [Cache](/pt-br/documentacao/produtos/build/applications/cache/tiered-cache/) ativado e desejar manter o cache na camada de Cache, você deve definir o TTL para pelo menos `3` segundos. -Um TTL zero não é o mesmo que um cache bypass. Para mais detalhes, leia sobre a diferença entre essas configurações na documentação [behavior Bypass Cache](/pt-br/documentacao/produtos/build/edge-application/rules-engine/#bypass-cache). +Um TTL zero não é o mesmo que um cache bypass. Para mais detalhes, leia sobre a diferença entre essas configurações na documentação [behavior Bypass Cache](/pt-br/documentacao/produtos/build/applications/rules-engine/#bypass-cache). ::: **Stale cache** @@ -68,7 +68,7 @@ A Azion oferece a capacidade de servir conteúdo obsoleto do cache quando o serv **Otimização de arquivos grandes** -Em vez de baixar um arquivo de conteúdo grande e correr o risco de timeouts ou terminações de conexão, [os arquivos podem ser divididos](/pt-br/documentacao/produtos/build/edge-application/cache-settings/#large-file-optimization) em partes menores e armazenados em cache sob demanda. +Em vez de baixar um arquivo de conteúdo grande e correr o risco de timeouts ou terminações de conexão, [os arquivos podem ser divididos](/pt-br/documentacao/produtos/build/applications/cache-settings/#large-file-optimization) em partes menores e armazenados em cache sob demanda. 5. Em **Large file optimization**, habilite o switch para ativar. 6. A camada **Cache** já está selecionada por padrão. Se você tiver o módulo **Cache** ativado, você também pode habilitar este recurso para a camada de Cache. @@ -79,10 +79,10 @@ O tamanho padrão dos fragmentos é de `1024 kB`. **Application Accelerator** -Esta seção permite que você personalize como o cache varia com base em métodos HTTP, campos de query string, cookies e grupos de dispositivos por meio de [cache keys](/pt-br/documentacao/produtos/build/edge-application/cache-settings/#advanced-cache-key). Você pode escolher segmentar as cache keys usando esses atributos para controlar como os objetos são armazenados e servidos a partir do cache. +Esta seção permite que você personalize como o cache varia com base em métodos HTTP, campos de query string, cookies e grupos de dispositivos por meio de [cache keys](/pt-br/documentacao/produtos/build/applications/cache-settings/#advanced-cache-key). Você pode escolher segmentar as cache keys usando esses atributos para controlar como os objetos são armazenados e servidos a partir do cache. :::caution[atenção] -Para habilitar todas as funcionalidades do **Application Accelerator**, você deve ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/). +Para habilitar todas as funcionalidades do **Application Accelerator**, você deve ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/). ::: Para determinar a variação de conteúdo no cache: @@ -126,7 +126,7 @@ Depois de terminar de configurar a sua cache setting: **Activating your cache setting** -A página de configurações de cache agora lista a nova instância criada. No entanto, essa nova configuração de cache não está ativa em sua aplicação. Você precisa definir o que acionará a implementação das políticas de cache em sua aplicação. Para isso, você pode usar o [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/) de sua application. +A página de configurações de cache agora lista a nova instância criada. No entanto, essa nova configuração de cache não está ativa em sua aplicação. Você precisa definir o que acionará a implementação das políticas de cache em sua aplicação. Para isso, você pode usar o [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/) de sua application. As instruções abaixo ajudarão você a criar uma regra na qual qualquer requisição de seus usuários para `xxxxxxxxxx.map.azionedge.net/cache` aplicará a configuração de cache que você criou. @@ -151,7 +151,7 @@ Para analisar como seu conteúdo está sendo armazenado em cache, você pode ver -1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` pelo seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` pelo [ID da sua application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/): +1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` pelo seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` pelo [ID da sua application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/): ```bash curl --location --request PATCH 'https://api.azionapi.net/v4/edge_application/applications/' \ @@ -234,8 +234,8 @@ curl --location 'https://api.azionapi.net/v4/edge_application/applications/ -Configure sua application para lidar com respostas de erro da origem usando [Error Responses](/pt-br/documentacao/produtos/build/edge-application/error-responses/). A Azion permite que você defina um TTL de cache para páginas de erro, um caminho personalizado ou entregue outro código HTTP na resposta sem precisar alterar o código-fonte da sua aplicação. +Configure sua application para lidar com respostas de erro da origem usando [Error Responses](/pt-br/documentacao/produtos/build/applications/error-responses/). A Azion permite que você defina um TTL de cache para páginas de erro, um caminho personalizado ou entregue outro código HTTP na resposta sem precisar alterar o código-fonte da sua aplicação. Com este guia, você irá modificar a resposta de erro padrão da sua aplicação, definindo um TTL de cache para cada erro recebido da origem. diff --git a/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/functions-instances.mdx b/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/functions-instances.mdx index adb0ee84fa..f0129fdcde 100644 --- a/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/functions-instances.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/functions-instances.mdx @@ -13,12 +13,12 @@ namespace: docs_guides_build_instantiate_edge_functions import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -Instancie [funções serverless](/pt-br/documentacao/produtos/build/edge-application/edge-functions-instances/) diretamente dentro de sua application. +Instancie [funções serverless](/pt-br/documentacao/produtos/build/applications/functions-instances/) diretamente dentro de sua application. Este guia descreve como você pode instanciar a função *Azion - Hello World*, pré-configurada em sua conta. Você pode repetir este processo usando qualquer função já disponível no [Azion Marketplace](/pt-br/documentacao/produtos/marketplace/) ou [desenvolver sua própria função](/pt-br/documentacao/produtos/guias/edge-functions/api-builder/). :::caution[Atenção] -Você deve ativar o módulo [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) para implementar funções em sua aplicação. Se **Functions** estiver ativado, o tempo de computação e as invocações podem gerar custos relacionados ao uso. Consulte a [página de preços](/pt-br/documentacao/produtos/precos/) para mais informações. +Você deve ativar o módulo [Functions](/pt-br/documentacao/produtos/build/applications/functions/) para implementar funções em sua aplicação. Se **Functions** estiver ativado, o tempo de computação e as invocações podem gerar custos relacionados ao uso. Consulte a [página de preços](/pt-br/documentacao/produtos/precos/) para mais informações. ::: --- @@ -47,7 +47,7 @@ A página de funções agora lista a nova instância criada. No entanto, esta no 14. Na seção **Criteria**, selecione a variável `${uri}`. :::note -A variável `${uri}` pode já estar selecionada por padrão se você não ativou o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/). +A variável `${uri}` pode já estar selecionada por padrão se você não ativou o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/). ::: 15. Como operador de comparação, selecione **is equal**. @@ -60,7 +60,7 @@ Para ver sua função em execução, acesse sua aplicação [usando seu domínio -1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar o módulo [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/): +1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar o módulo [Functions](/pt-br/documentacao/produtos/build/applications/functions/): -1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/): +1. Execute a seguinte requisição `PATCH` em seu terminal, substituindo `[TOKEN VALUE]` por seu [personal token](/pt-br/documentacao/produtos/guias/personal-tokens/) e a variável `` por [seu ID de application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) para ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/): + Variáveis de ambiente são um aspecto crucial do desenvolvimento e implantação de software. Elas são usadas para armazenar informações sensíveis ou configurações que não devem ser codificadas diretamente no código-fonte. diff --git a/src/content/docs/pt-br/pages/build-jornada/visao-geral/visao-geral.mdx b/src/content/docs/pt-br/pages/build-jornada/visao-geral/visao-geral.mdx index 885e205473..87fe7bc898 100644 --- a/src/content/docs/pt-br/pages/build-jornada/visao-geral/visao-geral.mdx +++ b/src/content/docs/pt-br/pages/build-jornada/visao-geral/visao-geral.mdx @@ -19,17 +19,17 @@ Os produtos Build da Azion são o seu ponto de partida para utilizar o poder do Quando você [cria uma application](/pt-br/documentacao/produtos/comecar-com-um-template/), você determina a origem do seu conteúdo e configura o domínio que será usado para entregar sua application aos usuários finais. - + Através da arquitetura de proxy reverso, o edge processa as solicitações do usuário e mantém os dados em cache, descentralizando o armazenamento de objetos e otimizando as taxas e eficiência de transferência de dados. Essa escalabilidade permite que você se adapte ao crescimento da demanda de tráfego sem sobrecarregar sua infraestrutura, reduzindo também os custos de manutenção. ![Visão geral de uma requisição/resposta através da Applications](/assets/docs/images/uploads/edge-app-overview.png) -Quando um usuário solicita conteúdo de sua application, o navegador converte o [domínio](/pt-br/documentacao/produtos/build/edge-application/domains/) solicitado em um endereço IP pré-definido via resolução DNS. +Quando um usuário solicita conteúdo de sua application, o navegador converte o [domínio](/pt-br/documentacao/produtos/build/applications/domains/) solicitado em um endereço IP pré-definido via resolução DNS. -A requisição é direcionada para um edge node, onde ocorre seu processamento. Nesta etapa, além das personalizações de segurança e observabilidade, o edge node processa a requisição e executa configurações da aplicação, como [comportamentos](/pt-br/documentacao/produtos/build/edge-application/rules-engine/) e [diretivas de cache](/pt-br/documentacao/produtos/build/edge-application/cache-settings/). +A requisição é direcionada para um edge node, onde ocorre seu processamento. Nesta etapa, além das personalizações de segurança e observabilidade, o edge node processa a requisição e executa configurações da aplicação, como [comportamentos](/pt-br/documentacao/produtos/build/applications/rules-engine/) e [diretivas de cache](/pt-br/documentacao/produtos/build/applications/cache-settings/). -Após esse processo, o sistema pode utilizar [algoritmos de balanceamento de carga](/pt-br/documentacao/produtos/secure/edge-connector/load-balancer/) para distribuir requisições entre múltiplas origens. +Após esse processo, o sistema pode utilizar [algoritmos de balanceamento de carga](/pt-br/documentacao/produtos/secure/connectors/load-balancer/) para distribuir requisições entre múltiplas origens. Qualquer conteúdo em cache no edge será entregue diretamente na resposta ao usuário sem precisar ser requisitado da origem. Após a mediação pela Azion Web Platform, a requisição chega à sua origem, que irá responder à requisição. O edge processa novamente esta resposta antes de entregá-la ao usuário. diff --git a/src/content/docs/pt-br/pages/changelog/anos-passados/anos-passados-changelog.mdx b/src/content/docs/pt-br/pages/changelog/anos-passados/anos-passados-changelog.mdx index ffe234db71..15f0706982 100644 --- a/src/content/docs/pt-br/pages/changelog/anos-passados/anos-passados-changelog.mdx +++ b/src/content/docs/pt-br/pages/changelog/anos-passados/anos-passados-changelog.mdx @@ -41,11 +41,11 @@ Acompanhe as atualizações de anos anteriores a seguir. **Edge Application** -* **Digital Certificates:** estamos agora oferecendo suporte à geração de **CSR** em nossa plataforma. Um Certificate Signing Request (CSR) é um dos primeiros passos para obter seu próprio certificado TLS com a CA (_Certificate Authority_) de sua escolha. Saiba mais sobre essa funcionalidade, [aqui](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/). +* **Digital Certificates:** estamos agora oferecendo suporte à geração de **CSR** em nossa plataforma. Um Certificate Signing Request (CSR) é um dos primeiros passos para obter seu próprio certificado TLS com a CA (_Certificate Authority_) de sua escolha. Saiba mais sobre essa funcionalidade, [aqui](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/). **Edge Firewall** -* **WAF Self-Calibration:** com a nova opção de **Tuning**, você pode visualizar insights e personalizar quais regras serão permitidas de forma rápida e fácil, com apenas alguns cliques. Leia a [documentação](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/) para mais informações. +* **WAF Self-Calibration:** com a nova opção de **Tuning**, você pode visualizar insights e personalizar quais regras serão permitidas de forma rápida e fácil, com apenas alguns cliques. Leia a [documentação](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/) para mais informações. ## Updates @@ -167,7 +167,7 @@ Acompanhe as atualizações de anos anteriores a seguir. **Edge Firewall** -* O **Web Application Firewall** tem uma nova funcionalidade: Custom Allowed Rules, que permite selecionar Rule IDs específicas, melhorando a criação e a edição de regras [WAF](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/). Além disso, o Edge Firewall ganhou dois campos: _last editor_ e _last modified_. Respectivamente, eles exibem quem criou ou editou uma regra e quando isso ocorreu. +* O **Web Application Firewall** tem uma nova funcionalidade: Custom Allowed Rules, que permite selecionar Rule IDs específicas, melhorando a criação e a edição de regras [WAF](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/). Além disso, o Edge Firewall ganhou dois campos: _last editor_ e _last modified_. Respectivamente, eles exibem quem criou ou editou uma regra e quando isso ocorreu. **Edge Functions** @@ -234,7 +234,7 @@ Acompanhe as atualizações de anos anteriores a seguir. **Edge Application** -* Adicionamos uma funcionalidade para acesso [multiportas](/pt-br/documentacao/produtos/build/edge-application/#multiport) às Edge Applications, tornando sua implementação mais flexível. +* Adicionamos uma funcionalidade para acesso [multiportas](/pt-br/documentacao/produtos/build/applications/#multiport) às Edge Applications, tornando sua implementação mais flexível. ## Updates @@ -249,7 +249,7 @@ Acompanhe as atualizações de anos anteriores a seguir. **Edge Application** * Agora, com suporte ao uso de métodos [HTTP](https://api.azion.com/) (POST, PUT, PATCH e DELETE) no Edge Functions JavaScript, seus benefícios de performance, flexibilidade e segurança estão ainda melhores; -* Também aperfeiçoamos questões de segurança em relação à criação de regras no [Rules Engine](/pt-br/documentacao/produtos/secure/edge-firewall/rules-engine/). +* Também aperfeiçoamos questões de segurança em relação à criação de regras no [Rules Engine](/pt-br/documentacao/produtos/secure/firewall/rules-engine/). **Real Time Events** @@ -383,7 +383,7 @@ Acompanhe as atualizações de anos anteriores a seguir. **Edge Application** -* Nova funcionalidade [Slice Configuration](/pt-br/documentacao/produtos/build/edge-application/edge-cache/#slice-settings). +* Nova funcionalidade [Slice Configuration](/pt-br/documentacao/produtos/build/applications/cache/#slice-settings). **Edge Orchestrator** @@ -482,8 +482,8 @@ Acompanhe as atualizações de anos anteriores a seguir. * Bugfix no produto Edge DNS. * [Lançamento da nova versão do Origin Shield](https://www.azion.com/pt-br/blog/origin-shield-disponivel-rtm-api/), com suporte à consulta da Network List via Real-Time Manager e API. -* Adicionada a funcionalidade de envio de notificação por email quando houver mudanças na Network List do produto [Origin Shield.](/pt-br/documentacao/produtos/edge-firewall/network-layer-protection#origin-shield) -* Adicionada a funcionalidade de visualizar as mudanças que ocorreram na Network List do produto [Origin Shield](/pt-br/documentacao/produtos/edge-firewall/network-layer-protection#origin-shield) por meio do *History* do RTM. +* Adicionada a funcionalidade de envio de notificação por email quando houver mudanças na Network List do produto [Origin Shield.](/pt-br/documentacao/produtos/secure/firewall/network-shield/#origin-shield) +* Adicionada a funcionalidade de visualizar as mudanças que ocorreram na Network List do produto [Origin Shield](/pt-br/documentacao/produtos/secure/firewall/network-shield/#origin-shield) por meio do *History* do RTM. * Bugfix no produto Digital Certificate. * Lançamento do Single Sign-On. @@ -526,10 +526,10 @@ Acompanhe as atualizações de anos anteriores a seguir. * Disponibilizado [API](/pt-br/documentacao/produtos/secure/edge-dns/) para gerenciamento de Zonas e Records para o produto Edge DNS. * Adicionado o gráfico referente à métrica "Data Stream Requests" do produto Data Stream, na interface do Real-Time Metrics. -* Adicionado suporte à ECC - _Elliptic Curve Cryptography_ em [Digital Certificates](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/). +* Adicionado suporte à ECC - _Elliptic Curve Cryptography_ em [Digital Certificates](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/). * Melhorias na propagação de Json args das Edge Function Instances. * Bug fix na edição de _Origins_ pela interface do Real-Time Manager. -* Bug fix no purge de _subdomain_ quando utilizado [Wildcard Purge](/pt-br/documentacao/produtos/build/edge-application/real-time-purge/). +* Bug fix no purge de _subdomain_ quando utilizado [Wildcard Purge](/pt-br/documentacao/produtos/build/applications/real-time-purge/). --- @@ -538,8 +538,8 @@ Acompanhe as atualizações de anos anteriores a seguir. * Adicionada variável "host" no Real-Time Events para o Data Source "Edge Application". * Bug fix na interface do Real-Time Events. * Adicionado o gráfico referente à métrica "Data Streamed" do produto Data Stream, na interface do Real-Time Metrics. -* Nova solução Bot Management integrada à plataforma da Azion, usando [Edge Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) no [Edge Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/). -* Adicionado componente de seleção [TLS Minimum Version](/pt-br/documentacao/produtos/build/edge-application/#minimum-tls-version), na interface da Edge Application. +* Nova solução Bot Management integrada à plataforma da Azion, usando [Edge Functions](/pt-br/documentacao/produtos/build/applications/functions/) no [Edge Firewall](/pt-br/documentacao/produtos/secure/firewall/). +* Adicionado componente de seleção [TLS Minimum Version](/pt-br/documentacao/produtos/build/applications/#minimum-tls-version), na interface da Edge Application. * Bug fix na paginação da [Api V3](https://api.azion.com/) ao listar [Edge Applications](https://api.azion.com/). --- @@ -835,7 +835,7 @@ Acompanhe as atualizações de anos anteriores a seguir. **nov/2017** -* Novos [tipos de purge](/pt-br/documentacao/produtos/build/edge-application/real-time-purge/#tipos-de-purge): purges agora podem ser feitos por URL, CacheKey ou por Wildcard. +* Novos [tipos de purge](/pt-br/documentacao/produtos/build/applications/real-time-purge/#tipos-de-purge): purges agora podem ser feitos por URL, CacheKey ou por Wildcard. * O histórico de purge agora irá mostrar o tipo, método e forma que o sistema recebeu a requisição de purge. * Bug fix para o purge em caso de URLs com Unicode. @@ -865,8 +865,8 @@ Nota: Assim como a interface foi atualizada para requerer o tipo de purge, a [AP **jul/2017** -* Integração ao Real-Time Manager da funcionalidade de IP Blocking do [Edge Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/#ip-blocking). -* Integração à API da funcionalidade de IP Blocking do [Edge Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/). +* Integração ao Real-Time Manager da funcionalidade de IP Blocking do [Edge Firewall](/pt-br/documentacao/produtos/secure/firewall/#ip-blocking). +* Integração à API da funcionalidade de IP Blocking do [Edge Firewall](/pt-br/documentacao/produtos/secure/firewall/). * Integração ao Real-Time Manager da funcionalidade que permite o download do arquivo de configurações avançadas (_locked_), quando requerido pelo cliente. --- @@ -886,7 +886,7 @@ Nota: Assim como a interface foi atualizada para requerer o tipo de purge, a [AP * Implementação do endpoint Elasticsearch no produto [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/). * Implementação de novas funcionalidades em Lua no Content Delivery para regras condicionais avançadas. * Implementação de novas funcionalidades de Device Detection para configuração de regras condicionais baseadas no dispositivo. -* Evolução da Learning Tool do produto [Web Application Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/). +* Evolução da Learning Tool do produto [Web Application Firewall](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/). --- @@ -917,7 +917,7 @@ Nota: Assim como a interface foi atualizada para requerer o tipo de purge, a [AP * Lançamento de endpoints para configuração da API do Content Delivery. * Lançamento do novo produto de [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/). -* Melhorias dos textos das opções de [Advanced Cache Key](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/#advanced-cache-key). +* Melhorias dos textos das opções de [Advanced Cache Key](/pt-br/documentacao/produtos/build/applications/application-accelerator/#advanced-cache-key). * Melhorias na amarração de comportamentos no Rules Engine, para simplificação do fluxo de criação de regras de Redirect e Access Denied. * Implementação da funcionalidade *Add Request Header* customizável no produto Adaptive Delivery. @@ -925,14 +925,14 @@ Nota: Assim como a interface foi atualizada para requerer o tipo de purge, a [AP **jan/2017** -* Renovação do [Shared Certificate](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/) da Azion junto a CA, para todos os clientes do produto. +* Renovação do [Shared Certificate](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/) da Azion junto a CA, para todos os clientes do produto. * Fix na criação/edição de Rule Engine no Real-Time Manager para tornar opcional a seleção de uma rule set de Edge Firewall. * Fix para visualização dos gráficos no Analytics que contabilizam a ocupação do bucket RawLogs no Cloud Storage. * Fix para utilização do Image Optimization em conjunto com o Cloud Storage sem necessidade de criar uma Configuration segregada. * Otimização de performance no carregamento do Real-Time Manager. * Lançamento de framework de autenticação na [API da Azion](https://api.azion.com/). * Lançamento de endpoints de consulta de dados do Analytics na API da Azion. -* Integração das funcionalidades de Advanced Cache Key (cache key por cookie e cache key por query string) do produto [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/) ao Real-Time Manager. +* Integração das funcionalidades de Advanced Cache Key (cache key por cookie e cache key por query string) do produto [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/) ao Real-Time Manager. * Lançamento de nova aba de Cache Settings e alteração do comportamento da aba Rules Engine, no Real-Time Manager, para viabilizar reuso de configurações de cache por path. --- @@ -953,8 +953,8 @@ Nota: Assim como a interface foi atualizada para requerer o tipo de purge, a [AP **ago/2016** * Suporte a HTTP/2. -* Atualização da aba Origins no Real-Time Manager para integração de funcionalidades do produto [Load Balancer](/pt-br/documentacao/produtos/secure/edge-connector/load-balancer/). -* Atualização do Real-Time Manager para inclusão da nova interface para criação de rule sets do [Web Application Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/web-application-firewall/). +* Atualização da aba Origins no Real-Time Manager para integração de funcionalidades do produto [Load Balancer](/pt-br/documentacao/produtos/secure/connectors/load-balancer/). +* Atualização do Real-Time Manager para inclusão da nova interface para criação de rule sets do [Web Application Firewall](/pt-br/documentacao/produtos/secure/firewall/web-application-firewall/). --- @@ -962,21 +962,19 @@ Nota: Assim como a interface foi atualizada para requerer o tipo de purge, a [AP * Atualização na interface de Permissões por Time, no Real-Time Manager. * Suporte a Wildcard Purge em tempo real. -* Atualização da plataforma de [Image Optimization](/pt-br/documentacao/produtos/build/edge-application/image-processor/), com ganhos superiores na otimização de imagens. +* Atualização da plataforma de [Image Optimization](/pt-br/documentacao/produtos/build/applications/image-processor/), com ganhos superiores na otimização de imagens. --- **mai/2016** -* Lançamento da nova interface para upload de [Digital Certificates](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/) no Real-Time Manager. +* Lançamento da nova interface para upload de [Digital Certificates](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/) no Real-Time Manager. * Novo ponto de presença (POP) no Rio de Janeiro. --- **abr/2016** -* Atualização da interface do [Edge Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/) para suporte a reuso de rule sets. +* Atualização da interface do [Edge Firewall](/pt-br/documentacao/produtos/secure/firewall/) para suporte a reuso de rule sets. * Atualização da interface de Custom Headers para suporte a reuso de configurações. * Lançamento de aba para configuração de Device Groups e atualização na aba Rules Engine para integração do produto Adaptive Delivery. - - diff --git a/src/content/docs/pt-br/pages/deploy-jornada/automatizar/zero-touch-provisioning/zero-touch-provisioning.mdx b/src/content/docs/pt-br/pages/deploy-jornada/automatizar/zero-touch-provisioning/zero-touch-provisioning.mdx index 1177f00f8d..469c2ff261 100644 --- a/src/content/docs/pt-br/pages/deploy-jornada/automatizar/zero-touch-provisioning/zero-touch-provisioning.mdx +++ b/src/content/docs/pt-br/pages/deploy-jornada/automatizar/zero-touch-provisioning/zero-touch-provisioning.mdx @@ -15,7 +15,7 @@ menu_namespace: deployMenu import LinkButton from 'azion-webkit/linkbutton' -[Azion Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/) é um serviço de orquestração de gerenciamento de nuvem programável e extensível e *zero-touch provisioning* construído especificamente para infraestruturas e applications. +[Azion Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/) é um serviço de orquestração de gerenciamento de nuvem programável e extensível e *zero-touch provisioning* construído especificamente para infraestruturas e applications. diff --git a/src/content/docs/pt-br/pages/deploy-jornada/avancado/explorar-uso/explorar-uso.mdx b/src/content/docs/pt-br/pages/deploy-jornada/avancado/explorar-uso/explorar-uso.mdx index 7b07baa4a1..50814237b4 100644 --- a/src/content/docs/pt-br/pages/deploy-jornada/avancado/explorar-uso/explorar-uso.mdx +++ b/src/content/docs/pt-br/pages/deploy-jornada/avancado/explorar-uso/explorar-uso.mdx @@ -14,7 +14,7 @@ menu_namespace: deployMenu import LinkButton from 'azion-webkit/linkbutton' -O [Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/) funciona baseado em um agente. Este agente é instalado no seu dispositivo, tornando o seu dispositivo, a partir deste momento, um edge node que [deve ser autorizado](/pt-br/documentacao/produtos/guias/deploy/autorizar-edge-node/) antes de iniciar a orquestração. +O [Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/) funciona baseado em um agente. Este agente é instalado no seu dispositivo, tornando o seu dispositivo, a partir deste momento, um edge node que [deve ser autorizado](/pt-br/documentacao/produtos/guias/deploy/autorizar-edge-node/) antes de iniciar a orquestração. O [Azion Orchestrator Agent](/pt-br/documentacao/produtos/guias/deploy/instalar-orchestrator-agent/) apresenta uma lista de comandos que podem ser executados no terminal e ajudam você a usar seus recursos. @@ -24,7 +24,7 @@ A lista de comandos inclui: - Ajuda com comandos gerais. - Status da execução do agente. - + Você pode [verificar os logs](/pt-br/documentacao/produtos/guias/deploy/verificar-logs/) relacionados à execução dos edge nodes acessando o arquivo `/var/log/azion/edge-orchestrator.log` e aos edge services em `/var/log/azion/edge-services.log`. diff --git a/src/content/docs/pt-br/pages/deploy-jornada/configurar-node/trabalhar-variaveis/trabalhar-com-variaveis.mdx b/src/content/docs/pt-br/pages/deploy-jornada/configurar-node/trabalhar-variaveis/trabalhar-com-variaveis.mdx index 445579c3e4..29e58b55e0 100644 --- a/src/content/docs/pt-br/pages/deploy-jornada/configurar-node/trabalhar-variaveis/trabalhar-com-variaveis.mdx +++ b/src/content/docs/pt-br/pages/deploy-jornada/configurar-node/trabalhar-variaveis/trabalhar-com-variaveis.mdx @@ -15,7 +15,7 @@ menu_namespace: deployMenu import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -Durante o processo de implantação no [Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/), você pode trabalhar com variáveis. Uma variável pode ser definida em [edge services](#variaveis-em-edge-services) e [edge nodes](#variaveis-em-edge-nodes). +Durante o processo de implantação no [Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/), você pode trabalhar com variáveis. Uma variável pode ser definida em [edge services](#variaveis-em-edge-services) e [edge nodes](#variaveis-em-edge-nodes). Você pode criar variáveis de edge node e de edge services usando: diff --git a/src/content/docs/pt-br/pages/deploy-jornada/deploy-service/deploy-service.mdx b/src/content/docs/pt-br/pages/deploy-jornada/deploy-service/deploy-service.mdx index eda29ca730..dd1902ff08 100644 --- a/src/content/docs/pt-br/pages/deploy-jornada/deploy-service/deploy-service.mdx +++ b/src/content/docs/pt-br/pages/deploy-jornada/deploy-service/deploy-service.mdx @@ -26,7 +26,7 @@ A Azion oferece duas maneiras de gerenciar edge nodes, edge services e recursos: A criação de um edge node acontece diretamente nos dispositivos quando o [Orchestrator Agent](/pt-br/documentacao/produtos/guias/deploy/instalar-orchestrator-agent/) é instalado neles. ::: - + --- @@ -80,7 +80,7 @@ Com o Agente do Orchestrator instalado no dispositivo, autorize o edge node.
- + --- diff --git a/src/content/docs/pt-br/pages/deploy-jornada/overview/overview.mdx b/src/content/docs/pt-br/pages/deploy-jornada/overview/overview.mdx index 4b0f766364..9e8ade47ef 100644 --- a/src/content/docs/pt-br/pages/deploy-jornada/overview/overview.mdx +++ b/src/content/docs/pt-br/pages/deploy-jornada/overview/overview.mdx @@ -18,7 +18,7 @@ Os produtos de **Deploy** da Azion são projetados para aumentar a eficiência n ## Orchestrator -O [Orchestrator](/pt-br/documentacao/produtos/deploy/edge-orchestrator/) é um sistema versátil para inovação em edge computing, permitindo a implantação, gerenciamento e automação eficientes de cargas de trabalho em edge networks, dispositivos remotos, locais e plataformas multi-cloud. Projetado para orquestrar suas aplicações e [edge services](/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-services/) nos [edge nodes](/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-node/), integra-se aos produtos e recursos da Azion, bem como aplicações, serviços ou recursos proprietários ou de terceiros. +O [Orchestrator](/pt-br/documentacao/produtos/deploy/orchestrator/) é um sistema versátil para inovação em edge computing, permitindo a implantação, gerenciamento e automação eficientes de cargas de trabalho em edge networks, dispositivos remotos, locais e plataformas multi-cloud. Projetado para orquestrar suas aplicações e [edge services](/pt-br/documentacao/produtos/deploy/orchestrator/edge-services/) nos [edge nodes](/pt-br/documentacao/produtos/deploy/orchestrator/edge-node/), integra-se aos produtos e recursos da Azion, bem como aplicações, serviços ou recursos proprietários ou de terceiros. O sistema fornece *criptografia de ponta a ponta* e *segurança em várias camadas*, facilitando o fluxo seguro de dados enquanto libera recursos valiosos de TI. Flexível e adaptável, pode acomodar ambientes críticos complexos e é compatível com várias arquiteturas de hardware e rede, capaz de rodar nativamente no sistema operacional, dentro de contêineres, ou em cima do [Azion Runtime da Azion ](/pt-br/documentacao/runtime/visao-geral/). @@ -28,7 +28,7 @@ Um agente do Orchestrator é instalado nos edge nodes e fornece gerenciamento re Quando o Agente do Azion Orchestrator é instalado em um dispositivo e o dispositivo é autorizado, ele agora representa um edge node. Um serviço pode ser vinculado a vários edge nodes. Quando um serviço é atualizado, ele será automaticamente implantado nos edge nodes aos quais está relacionado. ::: - + ### Edge Services @@ -37,7 +37,7 @@ O Azion **Edge Services** facilita o registro e configuração de recursos atrav Ele permite a configuração de gatilhos de instalação, desinstalação e recarregamento, e a definição de dependências de recursos para a execução do serviço de rede no edge. - + ### Edge Nodes @@ -46,5 +46,5 @@ Um edge node é um dispositivo que tem o Agente do Azion Orchestrator instalado O Orchestrator permite que os clientes gerenciem seus próprios edge nodes, independentemente da rede distribuída da Azion. Para começar a provisionar aplicações, é essencial configurar os edge nodes. - + diff --git a/src/content/docs/pt-br/pages/devtools/api-graphql/recursos/recursos-gql.mdx b/src/content/docs/pt-br/pages/devtools/api-graphql/recursos/recursos-gql.mdx index 365877305b..1c54648010 100644 --- a/src/content/docs/pt-br/pages/devtools/api-graphql/recursos/recursos-gql.mdx +++ b/src/content/docs/pt-br/pages/devtools/api-graphql/recursos/recursos-gql.mdx @@ -45,7 +45,7 @@ Quatro conjuntos de dados foram descontinuados e substituiídos por outros: | httpBreakdownMetrics | Consulte dados agregados, detalhados e em tempo real sobre [eventos de requisições HTTP bloqueadas](/pt-br/documentacao/produtos/guias/consultar-dados-httpbreakdownmetrics-com-graphql/) | | edgeDnsQueriesMetrics | Eventos de consultas realizadas no [Edge DNS](/pt-br/documentacao/produtos/secure/edge-dns/) | | imagesProcessedMetrics | Eventos de processamento de imagens do [Image Processor](/pt-br/documentacao/produtos/build/applications/image-processor/) | -| tieredCacheMetrics | Eventos de requisições registradas pelo [Tiered Cache](/pt-br/documentacao/produtos/build/applications/tiered-cache/) | +| tieredCacheMetrics | Eventos de requisições registradas pelo [Tiered Cache](/pt-br/documentacao/produtos/build/applications/cache/tiered-cache/) | | connectedUsersMetrics | Consulte o número de usuários conectados às suas aplicações, usando [Live Ingest](/pt-br/documentacao/produtos/guias/query-dados-connected-users-com-graphql/) | | botManagerMetrics | Consulte o número de requisições avaliadas e as ações realizadas pelo [Azion Bot Manager](/pt-br/documentacao/produtos/guias/consultar-dados-bot-manager-com-graphql/) (se inscrito) | | botManagerBreakdownMetrics | Consulte as URLs mais impactadas por bots maliciosos, de acordo com os dados do [Azion Bot Manager](/pt-br/documentacao/produtos/guias/consultar-dados-bot-manager-breakdown-com-graphql/) (se inscrito) | @@ -59,11 +59,11 @@ Quatro conjuntos de dados foram descontinuados e substituiídos por outros: | activityHistoryEvents | Logs de eventos de uma conta no Azion Console relacionados às atividades registradas no [Activity History](/pt-br/documentacao/produtos/gestao-de-contas/activity-history/). Armazena dados por *2 anos* e exibe dados a partir de *22 de setembro de 2023*. | | cellsConsoleEvents | Logs de eventos das aplicações usando o [Azion Runtime](/pt-br/documentacao/runtime/visao-geral/) retornados pelo Cells Console. | | dataStreamedEvents | Registros de envio de dados do [Data Stream](/pt-br/documentacao/produtos/observe/data-stream/) para o endpoint do cliente. | -| edgeFunctionsEvents | Eventos de execução do [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/). | -| httpEvents | Eventos de requisições registradas pelo [Applications](/pt-br/documentacao/produtos/build/edge-application/) e [Firewall](/pt-br/documentacao/produtos/secure/edge-firewall/). | +| edgeFunctionsEvents | Eventos de execução do [Functions](/pt-br/documentacao/produtos/build/applications/functions/). | +| httpEvents | Eventos de requisições registradas pelo [Applications](/pt-br/documentacao/produtos/build/applications/) e [Firewall](/pt-br/documentacao/produtos/secure/firewall/). | | idnsQueriesEvents | Eventos de consultas realizadas no [Edge DNS](/pt-br/documentacao/produtos/secure/edge-dns/). | -| imagesProcessedEvents | Eventos de processamento de imagens do [Image Processor](/pt-br/documentacao/produtos/build/edge-application/image-processor/). | -| l2CacheEvents | Eventos de requisições registradas pelo [Tiered Cache](/pt-br/documentacao/produtos/build/edge-application/tiered-cache/). | +| imagesProcessedEvents | Eventos de processamento de imagens do [Image Processor](/pt-br/documentacao/produtos/build/applications/image-processor/). | +| l2CacheEvents | Eventos de requisições registradas pelo [Tiered Cache](/pt-br/documentacao/produtos/build/applications/cache/tiered-cache/). | | telemetryDeviceInfoEvents | Eventos relacionados ao dispositivo sendo utilizado para acesso e registrados pelo **Azion Mobile SDK**, tanto a nível de hardware quanto de software. | | telemetrySensorsEvents | Eventos relacionados aos sensores dos dispositivos registrados pelo **Azion Mobile SDK**, como toque de tela e informações de giroscópio. | diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx index 26cee6b153..fbebb00037 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/code-editor/code-editor.mdx @@ -13,7 +13,7 @@ namespace: documentation_products_edge_functions_runtime_code_editor menu_namespace: runtimeMenu --- -O novo editor de código de [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) é a melhor maneira de começar a desenvolver suas functions na plataforma da Azion. É um editor de código baseado na web que torna mais fácil e intuitivo desenvolver na borda da rede. Ele é empoderado pelo [Monaco Code Editor](https://microsoft.github.io/monaco-editor/docs.html), usado no [VS Code](https://code.visualstudio.com/), então, se você estiver acostumado com o VS Code, você se familiarizará com ele rapidamente. Os principais recursos do Monaco Code Editor disponíveis para o **Functions Code Editor** são: +O novo editor de código de [Functions](/pt-br/documentacao/produtos/build/applications/functions/) é a melhor maneira de começar a desenvolver suas functions na plataforma da Azion. É um editor de código baseado na web que torna mais fácil e intuitivo desenvolver na borda da rede. Ele é empoderado pelo [Monaco Code Editor](https://microsoft.github.io/monaco-editor/docs.html), usado no [VS Code](https://code.visualstudio.com/), então, se você estiver acostumado com o VS Code, você se familiarizará com ele rapidamente. Os principais recursos do Monaco Code Editor disponíveis para o **Functions Code Editor** são: - Syntax Highlighting - IntelliSense @@ -29,7 +29,7 @@ O novo editor de código para functions está preparado para [suportar todos os Junto com o editor de código, é possível ver a pré-visualização da função que está sendo desenvolvida, em tempo real, proporcionando mais confiabilidade antes que o código vá para a produção. -Para saber mais sobre o preview, acesse [Azion Preview Deployment](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/preview-deployment/). +Para saber mais sobre o preview, acesse [Azion Preview Deployment](/pt-br/documentacao/produtos/applications/functions/runtime-api/preview-deployment/). ### Functions e ChatGPT @@ -40,7 +40,7 @@ Outro recurso que vem no pacote é uma integração com o [ChatGPT](https://open - Code explanation - Code generator -Acesse [Functions e ChatGPT](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/ai-integration/). +Acesse [Functions e ChatGPT](/pt-br/documentacao/produtos/applications/functions/runtime-api/ai-integration/). --- diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/nextjs.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/nextjs.mdx index eefe2a5f06..06d42caf10 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/nextjs.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/nextjs.mdx @@ -44,7 +44,7 @@ O Next.js também permite a Renderização do Lado do Servidor (SSR) na Azion We | Cosmic Next Blog | Blog | | | Cosmic Agency | E-commerce | | | Space Jelly Shop | E-commerce | | -| Nextal | Geral | | +| Nextal | Geral | | ## Realizando deploy de um template no Azion Console diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/template-showcase/nextjs/nextal.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/template-showcase/nextjs/nextal.mdx index 6a6ac39999..60317873cb 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/template-showcase/nextjs/nextal.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/frameworks/template-showcase/nextjs/nextal.mdx @@ -38,4 +38,4 @@ import Container from 'azion-webkit/container';
-Para mais informações sobre a implementação deste template, visite o [guia do template](/pt-br/documentacao/produtos/guias/nextal/). \ No newline at end of file +Para mais informações sobre a implementação deste template, visite o [guia do template](/pt-br/documentation/products/templates/nextal/). \ No newline at end of file diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/use-polyfills.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/use-polyfills.mdx index 914787d99b..b405b97101 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/use-polyfills.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/compatibilidade/use-polyfills.mdx @@ -20,7 +20,7 @@ Este guia mostrará como usar a API Buffer do Node.js através de polyfills em u Antes de começar, você deve ter: -- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o módulo [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) habilitado. +- Uma conta na [plataforma da Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/) com o módulo [Functions](/pt-br/documentacao/produtos/build/applications/functions/) habilitado. - [A versão mais recente da Azion CLI instalada](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Um editor de código. - Acesso ao terminal. diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/debugging/debugging.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/debugging/debugging.mdx index 804e95739f..6658303fc3 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/debugging/debugging.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/debugging/debugging.mdx @@ -65,13 +65,13 @@ Agora que você criou a function, deve configurar sua **application** para execu Para instanciar a função recém criada em sua aplicação, siga estas etapas: 1. No **Products Menu**, navegue até **Build** > **Applications**. -2. Clique na aplicação à qual você deseja adicionar a função ou [crie uma nova](/pt-br/documentacao/produtos/build/edge-application/primeiros-passos/). +2. Clique na aplicação à qual você deseja adicionar a função ou [crie uma nova](/pt-br/documentacao/produtos/build/applications/primeiros-passos/). 3. Vá para a aba **Function Instances** e clique em **+ Function Instance**. 4. Nomeie sua instância de função. 5. Selecione a function recém-criada no menu suspenso. 6. Clique no botão **Save**. -Agora sua function está instanciada e pronta para ser usada em sua aplicação. Você pode configurar as condições de execução e comportamentos usando o [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/): +Agora sua function está instanciada e pronta para ser usada em sua aplicação. Você pode configurar as condições de execução e comportamentos usando o [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/): 1. Ainda na página de configuração da application, navegue até a aba **Rules Engine** e clique no botão **+ Rule**. 2. Dê um nome descritivo à sua regra. diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/environment-variables-reference/environment-variables-reference.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/environment-variables-reference/environment-variables-reference.mdx index 51222b8b86..6ea4e0ab8a 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/environment-variables-reference/environment-variables-reference.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/environment-variables-reference/environment-variables-reference.mdx @@ -77,7 +77,7 @@ Você pode recuperar o valor de sua variável de ambiente configurada dentro de const apiToken = Azion.env.get('API_SERVICE_TOKEN'); ``` -Saiba mais sobre a [interface de Variáveis de Ambiente](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime/api-reference/metadata/). +Saiba mais sobre a [interface de Variáveis de Ambiente](/pt-br/documentacao/produtos/applications/functions/runtime/api-reference/metadata/). --- diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/nextjs/nextjs.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/nextjs/nextjs.mdx index f5cde91559..9f7d6dc8d8 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/nextjs/nextjs.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/nextjs/nextjs.mdx @@ -64,7 +64,7 @@ Para ajudar a melhorar a compatibilidade, incentivamos você a [relatar bugs](ht :::note As Functions da Azion têm um limite máximo de tamanho de 50 MB por função. Após compilar seu projeto, preste atenção ao tamanho comprimido (gzipped) do seu pacote de implementação — apenas o tamanho comprimido conta para esse limite. -Para mais detalhes, consulte a [documentação sobre limites de tamanho para Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/#limites). +Para mais detalhes, consulte a [documentação sobre limites de tamanho para Functions](/pt-br/documentacao/produtos/build/applications/functions/#limites). ::: ### Exemplos diff --git a/src/content/docs/pt-br/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx b/src/content/docs/pt-br/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx index 0fbf5b3940..02f1cb1841 100644 --- a/src/content/docs/pt-br/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx +++ b/src/content/docs/pt-br/pages/devtools/cli/azion-cli/azion-overview/azion-overview.mdx @@ -179,7 +179,7 @@ Para aplicações que requerem processamento no edge (compute) em vez de apenas - + --- diff --git a/src/content/docs/pt-br/pages/devtools/cli/azion-cli/comandos/update/update.mdx b/src/content/docs/pt-br/pages/devtools/cli/azion-cli/comandos/update/update.mdx index a9b967c2f5..3b989725f5 100644 --- a/src/content/docs/pt-br/pages/devtools/cli/azion-cli/comandos/update/update.mdx +++ b/src/content/docs/pt-br/pages/devtools/cli/azion-cli/comandos/update/update.mdx @@ -107,11 +107,11 @@ Exemplo dos atributos dentro de um arquivo `JSON`: ##### l2-caching -A flag `--l2-caching` especifica se a application tem o módulo [Tiered Cache](/pt-br/documentacao/produtos/build/applications/tiered-cache/) ativo. +A flag `--l2-caching` especifica se a application tem o módulo [Tiered Cache](/pt-br/documentacao/produtos/build/applications/cache/tiered-cache/) ativo. ##### load-balancer -A flag `--load-balancer` especifica se a application tem o módulo [Load Balancer](/pt-br/documentacao/produtos/secure/connector/load-balancer/) ativo. +A flag `--load-balancer` especifica se a application tem o módulo [Load Balancer](/pt-br/documentacao/produtos/secure/connectors/load-balancer/) ativo. ##### min-tls-ver diff --git a/src/content/docs/pt-br/pages/guias/conhecendo-o-azion-console/conhecendo-o-azion-console.mdx b/src/content/docs/pt-br/pages/guias/conhecendo-o-azion-console/conhecendo-o-azion-console.mdx index b8813ebae6..cf9df025d9 100644 --- a/src/content/docs/pt-br/pages/guias/conhecendo-o-azion-console/conhecendo-o-azion-console.mdx +++ b/src/content/docs/pt-br/pages/guias/conhecendo-o-azion-console/conhecendo-o-azion-console.mdx @@ -13,7 +13,7 @@ O [Azion Console](https://console.azion.com) é a interface de configuração da Através do Azion Console, você pode: - Acessar e configurar sua [conta Azion](/pt-br/documentacao/produtos/contas/criar-uma-conta/). -- Criar e implantar [applications](/pt-br/documentacao/produtos/build/edge-application/). +- Criar e implantar [applications](/pt-br/documentacao/produtos/build/applications/). - [Gerenciar suas applications](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/). - Acessar e configurar [todos os produtos e recursos da Azion](/pt-br/documentacao/). @@ -42,7 +42,7 @@ A documentação relacionada às telas do Console no **Help Center** não está 6. A seção **Get Started** inclui o botão **+ Create** para começar a usar a Azion Web Platform. Clicando nesse botão, você pode completar os primeiros passos para criar uma application usando o template que melhor atenda suas necessidades ou criando outros recursos como domínios, variáveis, functions, edge services, certificados digitais e mais. 7. Logo, há dois blocos: -- **Manage your Domains**: use este bloco para visitar a página de [domínios](/pt-br/documentacao/produtos/build/edge-application/domains/). Lá, você poderá gerenciar e adicionar domínios as suas applications. +- **Manage your Domains**: use este bloco para visitar a página de [domínios](/pt-br/documentacao/produtos/build/applications/domains/). Lá, você poderá gerenciar e adicionar domínios as suas applications. - **View Analytics**: lá, você encontrará insights com base no desempenho, disponibilidade e segurança de suas aplicações. Este link levará você ao [Real-Time Metrics](/pt-br/documentacao/produtos/observe/real-time-metrics/). 8. Seção **Invite Your Team**: esta é uma etapa opcional, mas se você estiver trabalhando constantemente com uma equipe, pode convidá-la para ajudar nas configurações e em todo o processo de trabalho. Saiba mais sobre as [permissões das equipes](/pt-br/documentacao/produtos/gestao-de-contas/teams-permissions/). diff --git a/src/content/docs/pt-br/pages/guias/data-streaming/debug-functions-dts.mdx b/src/content/docs/pt-br/pages/guias/data-streaming/debug-functions-dts.mdx index 032c47cbda..bb0ec1e21d 100644 --- a/src/content/docs/pt-br/pages/guias/data-streaming/debug-functions-dts.mdx +++ b/src/content/docs/pt-br/pages/guias/data-streaming/debug-functions-dts.mdx @@ -19,7 +19,7 @@ Verificar o código para fazer debug de functions através do [Data Stream](/pt- Antes de analisar o processo, você deve aplicar o código de debugging. Descubra mais em [Debugging functions](/pt-br/documentacao/devtools/debugging/). -Existem instruções separadas usando configurações de [Domains legados](/pt-br/documentacao/produtos/build/edge-application/domains/) e usando o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). +Existem instruções separadas usando configurações de [Domains legados](/pt-br/documentacao/produtos/build/applications/domains/) e usando o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). :::tip Se você não tem certeza de quais etapas se aplicam à sua conta, consulte [o guia Verificar Migração da Conta](/pt-br/documentacao/produtos/guias/verificar-migracao-conta/) para determinar se sua conta já foi migrada. diff --git a/src/content/docs/pt-br/pages/guias/debug-regras/debug-regras.mdx b/src/content/docs/pt-br/pages/guias/debug-regras/debug-regras.mdx index 3d14ecc295..30b4194913 100644 --- a/src/content/docs/pt-br/pages/guias/debug-regras/debug-regras.mdx +++ b/src/content/docs/pt-br/pages/guias/debug-regras/debug-regras.mdx @@ -20,9 +20,9 @@ import Tabs from '~/components/tabs/Tabs' Você pode fazer o debug de regras usando **GraphQL API**, Azion **Data Stream** e Azion **Real-Time Events**. - + -Existem instruções separadas usando configurações de [Domains legados](/pt-br/documentacao/produtos/build/edge-application/domains/) e usando o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). +Existem instruções separadas usando configurações de [Domains legados](/pt-br/documentacao/produtos/build/applications/domains/) e usando o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). :::tip Se você não tem certeza de quais etapas se aplicam à sua conta, consulte [o guia Verificar Migração da Conta](/pt-br/documentacao/produtos/guias/verificar-migracao-conta/) para determinar se sua conta já foi migrada. diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-advanced-cache-key.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-advanced-cache-key.mdx index 3f190034f6..79453046a3 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-advanced-cache-key.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-advanced-cache-key.mdx @@ -10,7 +10,7 @@ permalink: /documentacao/produtos/guias/advanced-cache-key/ og_image: /assets/docs/images/uploads/og_image_usecase-api-accelerate.png --- -O Azion **Application Accelerator** habilita a funcionalidade [Advanced Cache Key](/pt-br/documentacao/produtos/build/edge-application/cache-settings/#advanced-cache-key), que permite que você crie regras de cache com base em Query Strings da URL e Cookies. Você pode aplicar essas regras a uma aplicação dinâmica usando o [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/). +O Azion **Application Accelerator** habilita a funcionalidade [Advanced Cache Key](/pt-br/documentacao/produtos/build/applications/cache-settings/#advanced-cache-key), que permite que você crie regras de cache com base em Query Strings da URL e Cookies. Você pode aplicar essas regras a uma aplicação dinâmica usando o [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/). Para ativar a **Advanced Cache Key** para uma application: 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 39f8a98deb..6eee24f94b 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 @@ -15,7 +15,7 @@ import LinkButton from 'azion-webkit/linkbutton' O Azion **Applications** pode manter seu conteúdo armazenado em cache no edge para sustentar altos níveis de demanda sem comprometer a qualidade ou o desempenho. Isto resulta em uma melhor experiência do usuário, tempos de carregamento mais rápidos e custos de manutenção mais baixos. -Você pode otimizar seus tempos de processamento definindo o time-to-live (TTL) para conteúdo estático armazenado em cache na origem ou no navegador do usuário final, ou ignorar as configurações de cache de origem com o [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/). +Você pode otimizar seus tempos de processamento definindo o time-to-live (TTL) para conteúdo estático armazenado em cache na origem ou no navegador do usuário final, ou ignorar as configurações de cache de origem com o [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/). :::tip Para configurar políticas de cache para conteúdo dinâmico, consulte o guia [Como configurar a Advanced Cache Key para Applications](/pt-br/documentacao/produtos/guias/advanced-cache-key/). @@ -45,7 +45,7 @@ Para criar uma configuração de cache, siga as etapas: - Em **Browser Cache Settings**, selecione **Override Cache Settings** para definir por quanto tempo seu conteúdo pode ser armazenado em cache nos navegadores. - Em **Cache Settings**, selecione **Override Cache Settings** para definir por quanto tempo seu conteúdo pode ser armazenado em cache no edge. 5. Se você optou por substituir as configurações de cache, adicione o **Maximum TTL** desejado em segundos. - - Nesse momento, você também pode personalizar configurações de cache para conteúdo dinâmico relacionadas à funcionalidade [Advanced Cache Key](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/#advanced-cache-key). + - Nesse momento, você também pode personalizar configurações de cache para conteúdo dinâmico relacionadas à funcionalidade [Advanced Cache Key](/pt-br/documentacao/produtos/build/applications/application-accelerator/#advanced-cache-key). 6. Clique no botão **Save**. @@ -81,7 +81,7 @@ Se você quiser ignorar as políticas de cache de origem, você pode criar uma r Note que a funcionalidade de ignorar cache afeta apenas políticas de cache da origem, não políticas de cache do navegador. Para isso, você deve aplicar o comportamento **Set Cache Policy** descrito acima. - + --- diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-clone-edge-application.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-clone-edge-application.mdx index 6687f76686..dd6acf6098 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-clone-edge-application.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-clone-edge-application.mdx @@ -31,10 +31,10 @@ A application clonada aparecerá na lista e terá as mesmas configurações que Leia mais sobre applications na documentação com os seguintes guias: -- [Applications](/pt-br/documentacao/produtos/build/edge-application/) +- [Applications](/pt-br/documentacao/produtos/build/applications/) - [Como criar uma application](/pt-br/documentacao/produtos/guias/build/criar-uma-aplicacao/) - [Como gerenciar uma application](/pt-br/documentacao/produtos/guias/build/definir-configuracoes-principais/) -- [Como excluir uma application](/pt-br/documentacao/produtos/guias/excluir-edge-application/) +- [Como excluir uma application](/pt-br/documentacao/produtos/guias/excluir-applications/) --- diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-configure-ports/custom-ports.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-configure-ports/custom-ports.mdx index ba2cab4132..c478d5b9b2 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-configure-ports/custom-ports.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-configure-ports/custom-ports.mdx @@ -18,7 +18,7 @@ Com a Azion, você pode personalizar a porta do endereço de entrega da sua apli A escolha das portas de entrega é limitada àquelas suportadas pela Azion. No entanto, para recuperar o conteúdo de suas origens, você pode buscar seu conteúdo da porta de origem apropriada, desde que a porta exista. -Existem instruções separadas para API v3 usando configurações de [Origins legados](/pt-br/documentacao/produtos/build/edge-application/origins/) e API v4 usando o novo produto [Connectors](/pt-br/documentacao/produtos/secure/edge-connector/). +Existem instruções separadas para API v3 usando configurações de [Origins legados](/pt-br/documentacao/produtos/build/applications/origins/) e API v4 usando o novo produto [Connectors](/pt-br/documentacao/produtos/secure/connectors/). :::tip Se você não tem certeza de quais etapas se aplicam à sua conta, consulte [o guia Verificar Migração da Conta](/pt-br/documentacao/produtos/guias/verificar-migracao-conta/) para determinar se sua conta já foi migrada. diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/check-cors-permissions.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/check-cors-permissions.mdx index 6339713ffa..89857983f4 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/check-cors-permissions.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/check-cors-permissions.mdx @@ -21,7 +21,7 @@ Já requisições HTTP complexas exigem cabeçalhos adicionais. Essas são requi ## Habilite permissão CORS para requisições HTTP não complexas -A primeira etapa para permitir o acesso CORS é criar uma regra no [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/): +A primeira etapa para permitir o acesso CORS é criar uma regra no [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/): 1. Acesse o [Azion Console](https://console.azion.com). 2. Selecione **Products Menu** > **Applications**. @@ -71,7 +71,7 @@ Você pode configurar outros tipos de requisições complexas conforme desejar, ## Habilite permissão CORS para origens específicas -Para ativar o CORS em uma configuração para servidores de origem específicos, você precisará ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/edge-application/application-accelerator/): +Para ativar o CORS em uma configuração para servidores de origem específicos, você precisará ativar o módulo [Application Accelerator](/pt-br/documentacao/produtos/build/applications/application-accelerator/): 1. Acesse o [Azion Console](https://console.azion.com). 2. Selecione **Products menu** > **Applications**. diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/fix-cors-erros.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/fix-cors-erros.mdx index 983327668e..7bb1f6a50c 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/fix-cors-erros.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-cors/fix-cors-erros.mdx @@ -24,7 +24,7 @@ Mensagem de erro: Access to XMLHttpRequest at `http://a.domain.com/page-cors-subdomain-a.txt` from origin `http://b.domain.com` has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. -Para resolver esse tipo de erro, você precisa configurar o browser no **Azion Console** usando o [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/). +Para resolver esse tipo de erro, você precisa configurar o browser no **Azion Console** usando o [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/). No Google Chrome, siga os passos: diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-customize-error-responses.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-customize-error-responses.mdx index 2154d9fb10..000ca0a78d 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-customize-error-responses.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-customize-error-responses.mdx @@ -16,7 +16,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/pt/snippet.mdx' Descubra como configurar sua application da Azion para mostrar páginas de erro personalizadas para seu usuário baseadas em códigos de status de erro HTTP. Para este guia, você já deve ter uma Applications, um Connectors e um Workload configurados. -Existem instruções separadas para API v3 usando configurações de [Error Responses legados](/pt-br/documentacao/produtos/build/edge-application/error-responses/) e API v4 usando o novo produto [Custom Pages](/pt-br/documentacao/produtos/secure/custom-pages/). +Existem instruções separadas para API v3 usando configurações de [Error Responses legados](/pt-br/documentacao/produtos/build/applications/error-responses/) e API v4 usando o novo produto [Custom Pages](/pt-br/documentacao/produtos/secure/custom-pages/). :::tip Se você não tem certeza de quais etapas se aplicam à sua conta, consulte [o guia Verificar Migração da Conta](/pt-br/documentacao/produtos/guias/verificar-migracao-conta/) para determinar se sua conta já foi migrada. diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-enable-gzip.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-enable-gzip.mdx index b156612ff9..8f6eb53fc6 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-enable-gzip.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-enable-gzip.mdx @@ -24,7 +24,7 @@ Para mais informações e links úteis, consulte o [site oficial de gzip](https: ## Habilite compressão gzip usando Rules Engine -Você pode habilitar a compressão gzip para qualquer application usando o [Rules Engine para Applications](/pt-br/documentacao/produtos/build/edge-application/rules-engine/). +Você pode habilitar a compressão gzip para qualquer application usando o [Rules Engine para Applications](/pt-br/documentacao/produtos/build/applications/rules-engine/). Para habilitar a compressão gzip para sua aplicação, siga os passos: diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx index 439bd7fcff..d2b1e272dc 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-enforce-hls.mdx @@ -21,7 +21,7 @@ A Azion Web Platform permite que você [entregue conteúdo de streaming ao vivo - Uma application existente na Azion, ou [crie uma nova](/pt-br/documentacao/produtos/guias/build/criar-uma-aplicacao/). - [Um domínio associado à application](/pt-br/documentacao/produtos/guias/configurar-dominio/). - [Tiered Cache habilitado](/pt-br/documentacao/produtos/guias/billing-and-subscriptions/) em sua conta. -- Acesso ao [Object Storage da Azion](/pt-br/documentacao/produtos/store/edge-storage/) para armazenar conteúdo de vídeo. +- Acesso ao [Object Storage da Azion](/pt-br/documentacao/produtos/store/object-storage/) para armazenar conteúdo de vídeo. --- @@ -95,7 +95,7 @@ Ainda na aba **Cache Settings**: :::tip -Leia mais sobre a configuração de [cache settings](/pt-br/documentacao/produtos/build/edge-application/cache-settings/) para suas applications. +Leia mais sobre a configuração de [cache settings](/pt-br/documentacao/produtos/build/applications/cache-settings/) para suas applications. ::: ### Utilize o Object Storage da Azion para entrega de vídeos HLS @@ -195,7 +195,7 @@ Agora, crie uma regra para a playlist: Pronto! Agora você pode configurar sua fonte e codificador apontando para a Azion e transmitir seu conteúdo, implementando o cache HLS. :::tip -Acesse a documentação do [Rules Engine for Applications](/pt-br/documentacao/produtos/build/edge-application/rules-engine/) para mais detalhes. +Acesse a documentação do [Rules Engine for Applications](/pt-br/documentacao/produtos/build/applications/rules-engine/) para mais detalhes. ::: diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-mitigate-httpoxy.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-mitigate-httpoxy.mdx index 491807539a..27b4b17248 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-mitigate-httpoxy.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-mitigate-httpoxy.mdx @@ -9,7 +9,7 @@ namespace: documentation_how_to_configurations_mitigating permalink: /documentacao/produtos/guias/como-mitigar-vulnerabilidade-httpoxy/ --- -HTTPoxy é uma vulnerabilidade de aplicações web causada por requisições HTTP nocivas. Você pode configurar sua application para mitigar HTTPOxy usando o [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/). +HTTPoxy é uma vulnerabilidade de aplicações web causada por requisições HTTP nocivas. Você pode configurar sua application para mitigar HTTPOxy usando o [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/). --- 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 48d964ed55..393c6efbff 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 @@ -7,15 +7,15 @@ namespace: documentation_guides_lets_encrypt_via_api permalink: /documentacao/produtos/guias/como-gerar-um-certificado-lets-encrypt-via-api/ --- -As aplicações que utilizam o protocolo HTTPS requerem um [Digital Certificate](/pt-br/documentacao/produtos/build/edge-application/digital-certificates/). Ao direcionar seu tráfego para a Azion, você tem a opção de gerar um certificado *Let's Encrypt*™, que é uma maneira gratuita e segura de criptografar dados para sua application. A Azion automatiza a emissão, renovação e desativação deste certificado TLS através de uma solução interna de gerenciamento de certificados. +As aplicações que utilizam o protocolo HTTPS requerem um [Digital Certificate](/pt-br/documentacao/produtos/build/applications/certificate-manager/). Ao direcionar seu tráfego para a Azion, você tem a opção de gerar um certificado *Let's Encrypt*™, que é uma maneira gratuita e segura de criptografar dados para sua application. A Azion automatiza a emissão, renovação e desativação deste certificado TLS através de uma solução interna de gerenciamento de certificados. ## Desafio HTTP-01 do Let's Encrypt via API -A Azion agora oferece emissão e renovação de [certificados Let's Encrypt](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/) via API usando o desafio HTTP-01, oferecendo um processo simplificado sem a necessidade de registros TXT no DNS. Isso oferece uma solução de integração fácil e conveniente, especialmente benéfica para clientes que gerenciam diversos domínios e nomes de host. +A Azion agora oferece emissão e renovação de [certificados Let's Encrypt](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/) via API usando o desafio HTTP-01, oferecendo um processo simplificado sem a necessidade de registros TXT no DNS. Isso oferece uma solução de integração fácil e conveniente, especialmente benéfica para clientes que gerenciam diversos domínios e nomes de host. 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 [Certificate Manager](/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/firewall/certificate-manager/). --- diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-requet-lets-encrypt-certificates.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-requet-lets-encrypt-certificates.mdx index 74930ce102..04a00f89c8 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-requet-lets-encrypt-certificates.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-requet-lets-encrypt-certificates.mdx @@ -14,7 +14,7 @@ import Apiv4Rollout from '~/includes/snippets/apiv4Rollout/en/snippet.mdx' import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -As aplicações que utilizam o protocolo HTTPS requerem um [Digital Certificate](/pt-br/documentacao/produtos/build/edge-application/digital-certificates/). Ao direcionar seu tráfego para a Azion, você tem a opção de gerar um certificado *Let's Encrypt*™, que é uma maneira gratuita e segura de criptografar dados para sua application. A Azion automatiza a emissão, renovação e desativação deste certificado TLS através de uma solução interna de gerenciamento de certificados. +As aplicações que utilizam o protocolo HTTPS requerem um [Digital Certificate](/pt-br/documentacao/produtos/build/applications/certificate-manager/). Ao direcionar seu tráfego para a Azion, você tem a opção de gerar um certificado *Let's Encrypt*™, que é uma maneira gratuita e segura de criptografar dados para sua application. A Azion automatiza a emissão, renovação e desativação deste certificado TLS através de uma solução interna de gerenciamento de certificados. @@ -100,7 +100,7 @@ Agora que o desafio pode acontecer, o próximo passo é criar um domínio na Azi ## Configurando um domínio -Abaixo estãos os passos para adicionar um certificado para sua aplicação. Há instruções separadas para as configurações do [Domains legado](/pt-br/documentacao/produtos/build/edge-application/domains/) e para o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). +Abaixo estãos os passos para adicionar um certificado para sua aplicação. Há instruções separadas para as configurações do [Domains legado](/pt-br/documentacao/produtos/build/applications/domains/) e para o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). :::tip[Dica] Se você não tem certeza de quais passos se aplicam à sua conta, consulte [o guia Verifique a migração da sua conta para a API v4](/pt-br/documentacao/produtos/guias/verificar-migracao-conta/) para determinar se sua conta já foi migrada. @@ -131,7 +131,7 @@ Para criar um **Workload**, você deve primeiro ter uma application. Se você ai Para criar um domínio no **Domain** da Azion, você deve primeiro ter uma application. Se você ainda não criou uma application, vá para a [documentação sobre criar uma aplicação](/pt-br/documentacao/produtos/guias/build/criar-uma-aplicacao/). -Depois de ter uma application, você precisa [criar um domínio](/pt-br/documentacao/produtos/build/edge-application/domains/) e listar os CNAMEs que deseja proteger com o certificado Let's Encrypt. Para fazer isso, siga os passos: +Depois de ter uma application, você precisa [criar um domínio](/pt-br/documentacao/produtos/build/applications/domains/) e listar os CNAMEs que deseja proteger com o certificado Let's Encrypt. Para fazer isso, siga os passos: 1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Domains**. 2. Clique no botão **+ Domain**. @@ -184,7 +184,7 @@ Se o status **Pending** permanecer por mais de 48 horas, você deve verificar se ::: :::tip[Dica] -Para mais informações sobre a emissão de certificados Let's Encrypt, visite a [página de referência Digital Certificates para Secure](/pt-br/documentacao/produtos/secure/edge-firewall/digital-certificates/#certificado-lets-encrypt). +Para mais informações sobre a emissão de certificados Let's Encrypt, visite a [página de referência Digital Certificates para Secure](/pt-br/documentacao/produtos/secure/firewall/certificate-manager/#certificado-lets-encrypt). ::: --- @@ -202,7 +202,7 @@ Para garantir que o certificado seja renovado para domínios hospedados em servi ## Aponte seu tráfego para a Azion -Abaixo estãos os passos para apontar o seu tráfego para a Azion. Há instruções separadas para as configurações do [Domains legado](/pt-br/documentacao/produtos/build/edge-application/domains/) e para o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). +Abaixo estãos os passos para apontar o seu tráfego para a Azion. Há instruções separadas para as configurações do [Domains legado](/pt-br/documentacao/produtos/build/applications/domains/) e para o novo produto [Workloads](/pt-br/documentacao/produtos/secure/workloads). :::tip[Dica] Se você não tem certeza de quais passos se aplicam à sua conta, consulte [o guia Verifique a migração da sua conta para a API v4](/pt-br/documentacao/produtos/guias/verificar-migracao-conta/) para determinar se sua conta já foi migrada. diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-rules-engine.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-rules-engine.mdx index 36305fb6e4..0043f565e5 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-rules-engine.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-rules-engine.mdx @@ -18,7 +18,7 @@ import LinkButton from 'azion-webkit/linkbutton'; Com a arquitetura de proxy reverso da Azion **Applications**, as regras que você cria serão executadas entre a **Request phase**, que contém dados que o cliente envia para uma origem, ou a **Response phase**, que contém dados da origem que são enviados para o cliente. - + --- diff --git a/src/content/docs/pt-br/pages/guias/edge-application/ea-send-ip-through-header.mdx b/src/content/docs/pt-br/pages/guias/edge-application/ea-send-ip-through-header.mdx index fa2e1f076d..8100ede14c 100644 --- a/src/content/docs/pt-br/pages/guias/edge-application/ea-send-ip-through-header.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-application/ea-send-ip-through-header.mdx @@ -10,9 +10,9 @@ namespace: documentation_how_to_configurations_original_ip_header permalink: /documentacao/produtos/guias/ip-original-header/ --- -Quando um usuário faz uma requisição a uma aplicação, o cabeçalho HTTP `X-Forwarded-For` guarda o IP do cliente. Porém, como [edge nodes](/pt-br/documentacao/produtos/build/edge-application/) servem como uma camada para requisições para applications, além do IP do cliente, o cabeçalho também guarda outros endereços de IP na rota da requisição. +Quando um usuário faz uma requisição a uma aplicação, o cabeçalho HTTP `X-Forwarded-For` guarda o IP do cliente. Porém, como [edge nodes](/pt-br/documentacao/produtos/build/applications/) servem como uma camada para requisições para applications, além do IP do cliente, o cabeçalho também guarda outros endereços de IP na rota da requisição. -Para isolar o IP do cliente, você deve adicioná-lo a um novo cabeçalho usando a [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/) para **Applications**. +Para isolar o IP do cliente, você deve adicioná-lo a um novo cabeçalho usando a [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/) para **Applications**. Para enviar o IP original do cliente para um novo cabeçalho, siga os passos a seguir: diff --git a/src/content/docs/pt-br/pages/guias/edge-firewall/atualizar-edge-firewall.mdx b/src/content/docs/pt-br/pages/guias/edge-firewall/atualizar-edge-firewall.mdx index 8591b4a9fa..b20c32c4b8 100644 --- a/src/content/docs/pt-br/pages/guias/edge-firewall/atualizar-edge-firewall.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-firewall/atualizar-edge-firewall.mdx @@ -19,7 +19,7 @@ Os Rule Sets descontinuados do Firewall exibem um banner com a seguinte mensagem Esta documentação lhe guiará na atualização dos recursos do Firewall usados nas versões obsoletas para as mais recentes. Cada seção descreve como cada recurso funciona nos novos módulos, Network Lists e Rules Engine. - + --- diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/WebAssembly.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/WebAssembly.mdx index 2529474c3b..8b37742c8f 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/WebAssembly.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/WebAssembly.mdx @@ -10,7 +10,7 @@ og_image: >- /assets/docs/images/uploads/use-case_-creating-a-function-using-webassembly.png --- -Saiba mais sobre o processo necessário para a criação de uma [function](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) que utiliza uma função originada de um arquivo [WebAssembly](https://webassembly.org/getting-started/developers-guide/). +Saiba mais sobre o processo necessário para a criação de uma [function](/pt-br/documentacao/produtos/build/applications/functions/) que utiliza uma função originada de um arquivo [WebAssembly](https://webassembly.org/getting-started/developers-guide/). 1. Acesse o [Azion Console](/pt-br/documentacao/produtos/guias/como-acessar-o-azion-console/) > **Functions**. 2. Clique em **+ Function**. @@ -67,7 +67,7 @@ Um [código WAT](https://developer.mozilla.org/en-US/docs/WebAssembly/Understand 6. Clique no botão **Save** -Agora, a função está pronta para ser instanciada em uma application. Veja como [instanciar e executar as funções em sua application](/pt-br/documentacao/produtos/build/edge-application/edge-functions-instances/). +Agora, a função está pronta para ser instanciada em uma application. Veja como [instanciar e executar as funções em sua application](/pt-br/documentacao/produtos/build/applications/functions-instances/). A saída esperada da função recém-criada é semelhante a: diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/altcha-challenge.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/altcha-challenge.mdx index bf959dcf4f..97923efe51 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/altcha-challenge.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/altcha-challenge.mdx @@ -48,7 +48,7 @@ A função ALTCHA cria dois endpoints especiais em sua aplicação para gerencia :::note - É possível usar a Function ALTCHA de forma independente, apenas com o Firewall e proteger áreas específicas da sua aplicação por meio do desafio. -- Para usar o ALTCHA através do Bot Manager, [consulte a documentação](/pt-br/documentacao/produtos/secure/edge-firewall/bot-manager/#captcha). +- Para usar o ALTCHA através do Bot Manager, [consulte a documentação](/pt-br/documentacao/produtos/secure/firewall/bot-manager/#captcha). ::: ### Configure uma regra dentro do Firewall @@ -77,7 +77,7 @@ Pronto. Agora você tem a sua Function ALTCHA devidamente configurada. ### Crie uma regra dentro do Rules Engine -Para finalizar, você deve configurar o [Rules Engine](/pt-br/documentacao/produtos/secure/edge-firewall/rules-engine/) para definir o comportamento e os critérios para executar o ALTCHA, via Bot Manager ou independentemente com Firewall. +Para finalizar, você deve configurar o [Rules Engine](/pt-br/documentacao/produtos/secure/firewall/rules-engine/) para definir o comportamento e os critérios para executar o ALTCHA, via Bot Manager ou independentemente com Firewall. 1. Em Firewall, selecione **Rules Engine**. 2. Clique no botão **+ Rules Engine** para criar uma Rule para executar a função ALTCHA. diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-api-builder.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-api-builder.mdx index e1958af354..42529bebe8 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-api-builder.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-api-builder.mdx @@ -10,7 +10,7 @@ permalink: /documentacao/produtos/guias/edge-functions/api-builder/ -Saiba mais sobre o processo necessário para criar uma API com [Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) e [ChatGPT](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/ai-integration/), e tenha a resposta apresentada no [Azion Preview Deployment](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/preview-deployment/). +Saiba mais sobre o processo necessário para criar uma API com [Functions](/pt-br/documentacao/produtos/build/applications/functions/) e [ChatGPT](/pt-br/documentacao/produtos/applications/functions/runtime-api/ai-integration/), e tenha a resposta apresentada no [Azion Preview Deployment](/pt-br/documentacao/produtos/applications/functions/runtime-api/preview-deployment/). Para fazer isso, você precisa ter: @@ -169,11 +169,11 @@ Neste ponto, sua function deve estar semelhante a: }) ``` -Se quiser, você pode alternar o método dentro da função `PreviewProvider` e ter uma visualização em tempo real das respostas no [Azion Preview Deployment](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/preview-deployment/). +Se quiser, você pode alternar o método dentro da função `PreviewProvider` e ter uma visualização em tempo real das respostas no [Azion Preview Deployment](/pt-br/documentacao/produtos/applications/functions/runtime-api/preview-deployment/). 13. Clique no botão **Save**. -Agora, a função está pronta para ser instanciada em uma application. Veja como [instanciar e executar as funções em sua application](/pt-br/documentacao/produtos/build/edge-application/edge-functions-instances/). +Agora, a função está pronta para ser instanciada em uma application. Veja como [instanciar e executar as funções em sua application](/pt-br/documentacao/produtos/build/applications/functions-instances/). --- diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/browserless-edge-functions.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/browserless-edge-functions.mdx index 802a475be3..56b84f0847 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/browserless-edge-functions.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/browserless-edge-functions.mdx @@ -169,5 +169,5 @@ A Function browserless tipicamente inclui: --- - + diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx index c799e7dcaa..022bdf0d4b 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/file-upload-edge-functions.mdx @@ -239,5 +239,5 @@ function authenticateUser(request) { --- - - + + diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx index f5e76a99d9..e2f7e391df 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/resend-email-edge-functions.mdx @@ -250,4 +250,4 @@ Adicione capacidades de rastreamento para monitorar engajamento de email: --- - + diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx index 31a7aa0e49..c3e5d5f26a 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/restful-tasks-api-edge-functions.mdx @@ -532,5 +532,5 @@ async function getTasksPaginated(page = 1, limit = 10) { --- - - + + diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx index 7c0c0fde3c..5944bb59ff 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/edge-functions-examples/stripe-webhooks-edge-functions.mdx @@ -303,4 +303,4 @@ function logWebhookEvent(event, status, processingTime) { --- - + diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/functions-first-steps.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/functions-first-steps.mdx index 8639e4005b..198de18c04 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/functions-first-steps.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/functions-first-steps.mdx @@ -24,7 +24,7 @@ As functions funcionam sobre o [Azion Runtime](/pt-br/documentacao/runtime/visao ## Editor de Código -[O Functions Code Editor](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/code-editor/) fornece uma experiência de desenvolvimento semelhante à que os desenvolvedores estão acostumados. A [integração entre Functions e ChatGPT](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/ai-integration/) ajuda você a escrever, refatorar e revisar o código. +[O Functions Code Editor](/pt-br/documentacao/produtos/applications/functions/runtime-api/code-editor/) fornece uma experiência de desenvolvimento semelhante à que os desenvolvedores estão acostumados. A [integração entre Functions e ChatGPT](/pt-br/documentacao/produtos/applications/functions/runtime-api/ai-integration/) ajuda você a escrever, refatorar e revisar o código. --- @@ -39,7 +39,7 @@ Desenvolvendo sua primeira function para Application: ### Escrevendo uma function -Primeiro, as functions para Applications funcionam com base em um [fetch event](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-apis/javascript/fetch/). Ele é inicializado com uma função `addEventListener`, passando `fetch` como o tipo de evento e um evento. Por exemplo: +Primeiro, as functions para Applications funcionam com base em um [fetch event](/pt-br/documentacao/produtos/applications/functions/runtime-apis/javascript/fetch/). Ele é inicializado com uma função `addEventListener`, passando `fetch` como o tipo de evento e um evento. Por exemplo: ```javascript addEventListener('fetch', event => { @@ -79,7 +79,7 @@ Neste exemplo, a resposta será o conteúdo HTML, declarado anteriormente pelo c Depois de escrever suas functions, você pode visualizar a resposta e inspecionar o código. O preview simula uma solicitação e essa simulação pode ser alterada para atender às necessidades do desenvolvedor. -[Saiba mais sobre o Preview Deployment](/pt-br/documentacao/produtos/edge-application/edge-functions/runtime-api/preview-deployment/). +[Saiba mais sobre o Preview Deployment](/pt-br/documentacao/produtos/applications/functions/runtime-api/preview-deployment/). É possível depurar as funções através de: @@ -92,6 +92,6 @@ Depois de escrever suas functions, você pode visualizar a resposta e inspeciona Depois de salvar sua function, é necessário instanciá-la em uma application. -[Saiba mais sobre como instanciar uma function em uma application](/pt-br/documentacao/produtos/build/edge-application/edge-functions-instances/). +[Saiba mais sobre como instanciar uma function em uma application](/pt-br/documentacao/produtos/build/applications/functions-instances/). --- diff --git a/src/content/docs/pt-br/pages/guias/edge-functions/serverless-functions.mdx b/src/content/docs/pt-br/pages/guias/edge-functions/serverless-functions.mdx index 16e8bd3cc1..c4a6ec2efc 100644 --- a/src/content/docs/pt-br/pages/guias/edge-functions/serverless-functions.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-functions/serverless-functions.mdx @@ -12,15 +12,15 @@ import LinkButton from 'azion-webkit/linkbutton' import Tabs from '~/components/tabs/Tabs' -[Functions](/pt-br/documentacao/produtos/build/edge-application/edge-functions/) é um módulo da Azion Web Platform que permite que você programe e execute funções serverless, sem o uso de servidores. +[Functions](/pt-br/documentacao/produtos/build/applications/functions/) é um módulo da Azion Web Platform que permite que você programe e execute funções serverless, sem o uso de servidores. - + Para executar uma função, você deve: - Criar sua própria função ou usar qualquer uma das que já estão disponíveis no [Azion Marketplace](https://console.azion.com/marketplace). - Instanciar uma função em uma application. -- Definir critérios de ativação no [Rules Engine](/pt-br/documentacao/produtos/build/edge-application/rules-engine/). +- Definir critérios de ativação no [Rules Engine](/pt-br/documentacao/produtos/build/applications/rules-engine/). --- diff --git a/src/content/docs/pt-br/pages/guias/edge-sql/criar-query.mdx b/src/content/docs/pt-br/pages/guias/edge-sql/criar-query.mdx index ddee52ad53..7933460960 100644 --- a/src/content/docs/pt-br/pages/guias/edge-sql/criar-query.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-sql/criar-query.mdx @@ -17,7 +17,7 @@ import Tag from 'primevue/tag' Depois de criar seu [banco de dados SQL Database](/pt-br/documentacao/produtos/guias/gerenciar-bancos-dados-edge-sql/), você pode começar a criar tabelas e inserir dados nelas. - + --- diff --git a/src/content/docs/pt-br/pages/guias/edge-sql/gerenciar-banco.mdx b/src/content/docs/pt-br/pages/guias/edge-sql/gerenciar-banco.mdx index 1b0a21d099..3886752558 100644 --- a/src/content/docs/pt-br/pages/guias/edge-sql/gerenciar-banco.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-sql/gerenciar-banco.mdx @@ -19,7 +19,7 @@ O **SQL Database** permite que você crie e gerencie bancos de dados relacionais Após criar um banco de dados, leia [Como criar e consultar dados no SQL Database](/pt-br/documentacao/produtos/guias/criar-tabelas-edge-sql/) para popular seu banco de dados. - + --- diff --git a/src/content/docs/pt-br/pages/guias/edge-sql/listar-dados/index.mdx b/src/content/docs/pt-br/pages/guias/edge-sql/listar-dados/index.mdx index a0beb8414b..b99ed50286 100644 --- a/src/content/docs/pt-br/pages/guias/edge-sql/listar-dados/index.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-sql/listar-dados/index.mdx @@ -12,13 +12,13 @@ import LinkButton from 'azion-webkit/linkbutton' Veja como recuperar dados de um banco de dados existente com o **SQL Database** e as **Functions**. - + --- ## Requisitos -- [O módulo de Functions habilitado](/pt-br/documentacao/produtos/build/edge-application/edge-functions/). +- [O módulo de Functions habilitado](/pt-br/documentacao/produtos/build/applications/functions/). - [Um Personal Token configurado e ativo](/pt-br/documentacao/produtos/guias/personal-tokens/). --- @@ -138,7 +138,7 @@ Como este exemplo é para recuperação de dados, o método foi definido como ap Esta function foi criada para se comunicar com o SQL Database. Agora, é necessário instanciar esta função em uma application em execução: - + --- diff --git a/src/content/docs/pt-br/pages/guias/edge-sql/vector-search-guia.mdx b/src/content/docs/pt-br/pages/guias/edge-sql/vector-search-guia.mdx index 93dcb4d74e..4fdcfc26e7 100644 --- a/src/content/docs/pt-br/pages/guias/edge-sql/vector-search-guia.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-sql/vector-search-guia.mdx @@ -11,7 +11,7 @@ import LinkButton from 'azion-webkit/linkbutton' **Vector Search** é um recurso do **SQL Database da Azion** que permite aos clientes implementar mecanismos de busca semântica. Enquanto os modelos de busca tradicionais visam encontrar correspondências exatas, como correspondências de palavras-chave, os modelos de busca vetorial usam algoritmos especializados para identificar itens semelhantes com base em suas representações matemáticas, ou embeddings vetoriais. - + Como exemplo de implementação, este guia abordará a configuração da lógica de busca vetorial em uma aplicação TypeScript, com um banco de dados usando a biblioteca Langchain com OpenAI e a SQL Database API da Azion. @@ -24,7 +24,7 @@ Como exemplo de implementação, este guia abordará a configuração da lógica - Instale a [Azion CLI](/pt-br/documentacao/produtos/azion-cli/visao-geral/). - Crie uma aplicação TypeScript. - Como no exemplo, você pode usar a [Azion CLI](/pt-br/documentacao/devtools/cli/init/) para criar uma aplicação Simple Typescript Router. -- Configure o [SQL Database](/pt-br/documentacao/produtos/store/edge-sql/). +- Configure o [SQL Database](/pt-br/documentacao/produtos/store/sql-database/). - Instale as [Azion Libraries](https://github.com/aziontech/lib). --- diff --git a/src/content/docs/pt-br/pages/guias/edge-storage/bucket-actions/index.mdx b/src/content/docs/pt-br/pages/guias/edge-storage/bucket-actions/index.mdx index df8ec189a2..01c9b2cdb5 100644 --- a/src/content/docs/pt-br/pages/guias/edge-storage/bucket-actions/index.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-storage/bucket-actions/index.mdx @@ -10,7 +10,7 @@ import LinkButton from 'azion-webkit/linkbutton' O **Object Storage** da Azion permite que você crie buckets e integre seu armazenamento de objetos com sua infraestrutura do edge. Este guia abrange como fazer upload e download de objetos de um bucket usando a [API da Azion](https://api.azion.com) e [Azion Runtime](/pt-br/documentacao/runtime/api-reference/storage/). - + Consulte o guia [Como criar e modificar um bucket de Object Storage da Azion](/pt-br/documentacao/produtos/guias/criar-e-modificar-um-bucket/) para operações em buckets. @@ -141,7 +141,7 @@ addEventListener("fetch", (event) => { 6. Clique no botão **Save**. :::note -Consulte a referência [Object Storage API](/en/documentation/runtime/api-reference/storage/) para mais detalhes sobre as funções disponíveis para outros tipos de requisições. +Consulte a referência [Object Storage API](/pt-br/documentacao/runtime/api-reference/storage/) para mais detalhes sobre as funções disponíveis para outros tipos de requisições. ::: Após criar a function, você precisa criar uma application que vai intermediar o processo de upload para o bucket. diff --git a/src/content/docs/pt-br/pages/guias/edge-storage/create-object-storage/index.mdx b/src/content/docs/pt-br/pages/guias/edge-storage/create-object-storage/index.mdx index de52951b26..f0e347a655 100644 --- a/src/content/docs/pt-br/pages/guias/edge-storage/create-object-storage/index.mdx +++ b/src/content/docs/pt-br/pages/guias/edge-storage/create-object-storage/index.mdx @@ -14,7 +14,7 @@ import LinkButton from 'azion-webkit/linkbutton' O **Object Storage** da Azion permite que você crie buckets e integre seu armazenamento de objetos com sua infraestrutura no edge. Este guia abrange como criar, alterar e remover um bucket de armazenamento usando a [API da Azion](https://api.azion.com). - + Consulte o guia [Como fazer upload e download de objetos de um bucket](/pt-br/documentacao/produtos/guias/upload-e-download-de-objetos-do-bucket/) para realizar operações com objetos. 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 7e74a82f96..7fa64e4296 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 @@ -17,11 +17,11 @@ import Tabs from '~/components/tabs/Tabs' import Code from '~/components/Code/Code.astro' -**Object Storage** da Azion permite que você crie buckets e os use como fonte de conteúdo através de [Origins](/pt-br/documentacao/produtos/build/edge-application/origins/#edge-storage). Dessa forma, você pode tornar público o conteúdo do bucket. +**Object Storage** da Azion permite que você crie buckets e os use como fonte de conteúdo através de [Origins](/pt-br/documentacao/produtos/build/applications/origins/#edge-storage). Dessa forma, você pode tornar público o conteúdo do bucket. Este guia abrange como criar e servir uma aplicação estática recuperada de um bucket do Object Storage usando a [API da Azion](https://api.azion.com) e o [Azion Console](https://console.azion.com). -