From 4aef2b9cd1a01153f380cc9e0846d1d45e4f6420 Mon Sep 17 00:00:00 2001 From: Marcus Souza Date: Tue, 29 Sep 2026 22:43:48 -0300 Subject: [PATCH] feat(fundamentals): rebuild Fundamentals as its own level, with the Platform resources topology and a Performance group MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fundamentals becomes its own sidebar level. Its overview is redrawn as the Platform resources topology on the Console's expandable cards, the request path becomes a text diagram and a table named in the resource nomenclature, the use-case list reads from one catalog module, and a Performance group adds three how-to pages. Squashed from: - feat(fundamentals): rebuild Fundamentals as its own sidebar level Fundamentals stops being an inline dropdown in the root sidebar and opens its own level: Overview, How Azion works, Get started, Management, Billing, Security, Reference, and Agent resources. Platform keeps the nine resource rows and loses the How Azion works page, which moves here together with First deploy and the HTTP status codes page (six permalink moves, with their rows in cicd/massive-redirect). The Organization, Workspace, Usage metering, and Agent resources placeholders leave the nav; Agent resources returns as a dropdown holding Agent setup and the section's llms.txt. Pages: the Overview is rewritten around an interactive deployment topology (a webkit Flow island, src/components/webkit/DeploymentTopology*); How Azion works gets a request-path island, a product table keyed by resource, and use cases from the catalog; a new concept page, Accounts, teams, and users; Create an account and Migrate to Azion rewritten as task pages with DocSteps; HTTP status codes retitled; 21 existing pages swept to the platform taxonomy, in English and Portuguese. Nav: a new `llms` row kind resolves to the owning section's llms.txt, and the MDX wrapper policy allows `~/data/` copy modules. - feat(fundamentals): redraw the overview as the platform resources topology The Overview diagram now shows how the platform's resources connect instead of one example deployment: no instance names, every card is a resource, a product, or a platform feature with its taxonomy class, and the graph has two rows. The request row goes Edge DNS, DDoS Protection, and Certificate Manager into the workload, then firewall, application, and custom pages side by side, WAF on the firewall and Cache on the application, and the connector to the origin server or Object Storage. A second row shows what a function can call: AI Inference, SQL Database, KV Store. The webkit Flow pairs adjacent columns in order and a terminal card sends no line, so the connectors draw the true attachments. The island is renamed PlatformTopology with its data module, the section is "Platform resources topology" (PT "Topologia dos Recursos de Plataforma"), and a text twin of the graph sits under the walkthrough in a native disclosure wrapper (DocDisclosure), kept in the DOM while closed so the markdown twin carries it. - refactor(fundamentals): replace the request path island with a text diagram How Azion works describes the request path with a mermaid fence, rendered as a code block like every other fence on the site, so agents reading the markdown twin get the diagram as text. The RequestPath island and its data module are removed. - docs(fundamentals): name the request path table by platform resources The section is "Platform resources on the request path" (PT "Recursos de plataforma no caminho da requisição"): the documentation writes in the Platform Resource nomenclature, and the table is already keyed by resource. - feat(fundamentals): read the use-case list from one catalog module "What you can build" on How Azion works renders its lists from src/data/use-cases, which carries the 27 catalogued use cases under their five Solutions, with `featured` marking the selection the page shows and a link only where a page implements the use case. A future Use cases section reads the same module, so a changed use case is edited once. The Solution headings stay in the MDX so the right rail keeps them. - feat(fundamentals): add the Performance group with three how-to pages Test speed (Edge Pulse and Real-Time Metrics, with a before-and-after comparison through the hosts file), Minimize downtime (go live without a gap, a backup origin with Load Balancer, stale cache, a custom 503 page), and Maintenance mode (a request-phase rule that redirects or serves a maintenance page from a bucket, with an exception for your own address), in English and Portuguese, sourced from the product references and guides they link. - feat(fundamentals): redraw the topology on the Console's expandable cards The Overview diagram takes the Console's workload topology as its model: neutral cards with a header (icon, kind, chevron), an identity row, and a body that opens in place, each card on its own. The skeleton is Workload, then Firewall, Application, and Custom Pages side by side, then Store and AI above the Connector, then Origin; the products live inside the card they attach to and appear only when it opens, as links to their references. The open body holds the requirement tag, those links, and the reference link; no paragraph, no field rows, no item tags. Card width follows the diagram's container, a quarter of it less the flow's padding and gaps, clamped between 132px and the Console's 224px, so four columns fill the article at any width and never force a horizontal scroll. Connector to Store and AI, the one edge the Flow cannot draw, is a data-declared link painted in the Flow's connector style and re-measured when a card opens. The "diagram as text" disclosure and its wrapper component are removed. - fix(fundamentals): keep the Connector to Store and AI link on the cards The link was measured only when the diagram's container resized, and a card animating shut stops resizing the container as soon as a taller column takes over while the cards below it keep moving, so the last measurement was taken mid-transition. The svg also unmounted after one empty measurement. The svg now stays mounted, the two endpoint cards are observed as well, and the end of every transition triggers a final measurement that also makes the Flow re-measure its own lines. - docs(fundamentals): write the request path table in the resource nomenclature In documentation the taxonomy's nomenclature is the Platform Resource one, so the table's Products column becomes Reference, linking each entry to its reference page, and every other product mention on How Azion works and on the Overview now says what you enable or create on a resource. The four catalog categories sentence stays. English and Portuguese. --- cicd/massive-redirect/en.json | 12 + cicd/massive-redirect/pt-br.json | 12 + scripts/eslint-rules/mdx-policy.mjs | 3 + src/components/webkit/PlatformTopology.vue | 187 +++++++++++++++ .../webkit/PlatformTopologyNode.vue | 109 +++++++++ src/components/webkit/UseCaseList.vue | 42 ++++ .../docs/en/pages/agent-setup/claude-code.mdx | 4 +- .../docs/en/pages/agent-setup/codex.mdx | 4 +- .../docs/en/pages/agent-setup/cursor.mdx | 4 +- .../docs/en/pages/agent-setup/gemini-cli.mdx | 4 +- .../en/pages/agent-setup/github-copilot.mdx | 4 +- .../docs/en/pages/agent-setup/opencode.mdx | 4 +- .../docs/en/pages/agent-setup/windsurf.mdx | 4 +- .../azion-edge-runtime/overview/overview.mdx | 2 +- .../en/pages/first-deploy/first-deploy.mdx | 37 +-- .../troubleshooting/basic-troubleshooting.mdx | 2 +- .../migrate-to-azion/migrate-to-azion.mdx | 213 ++++++++++++------ .../use-a-template.mdx | 2 +- .../en/pages/main-menu/compliance/pci-dss.mdx | 10 +- .../en/pages/main-menu/compliance/soc-2.mdx | 10 +- .../get-started/azion-platform-overview.mdx | 161 +++++++------ .../main-menu/get-started/fundamentals.mdx | 51 ++++- .../get-started/start-with-a-template.mdx | 2 +- .../manage-accounts/create-accountd.mdx | 105 +++++---- .../performance/maintenance-mode.mdx | 133 +++++++++++ .../performance/minimize-downtime.mdx | 158 +++++++++++++ .../main-menu/performance/test-speed.mdx | 104 +++++++++ .../en/pages/main-menu/pricing/pricing.mdx | 2 +- .../accounts/account-lockout-policy.mdx | 4 +- .../reference/accounts/account-settings.mdx | 14 +- .../accounts/accounts-teams-and-users.mdx | 64 ++++++ .../reference/accounts/activity-history.mdx | 4 +- .../main-menu/reference/accounts/billing.mdx | 8 +- .../main-menu/reference/accounts/clients.mdx | 6 +- .../accounts/multi-factor-authentication.mdx | 4 +- .../reference/accounts/personal-tokens.mdx | 8 +- .../reference/accounts/social-login.mdx | 2 +- .../reference/accounts/sso-integration.mdx | 4 +- .../reference/accounts/teams-permissions.mdx | 22 +- .../accounts/user-session-timeout.mdx | 8 +- .../reference/accounts/users-management.mdx | 16 +- .../reference/accounts/your-settings.mdx | 10 +- .../reference/secure/api-v4-migration.mdx | 48 ++-- .../web-application-firewall.mdx | 2 +- .../support/http-error-status-codes.mdx | 60 ++--- .../shared-responsibility.mdx | 12 +- .../pt-br/pages/agent-setup/claude-code.mdx | 4 +- .../docs/pt-br/pages/agent-setup/codex.mdx | 4 +- .../docs/pt-br/pages/agent-setup/cursor.mdx | 4 +- .../pt-br/pages/agent-setup/gemini-cli.mdx | 4 +- .../pages/agent-setup/github-copilot.mdx | 4 +- .../docs/pt-br/pages/agent-setup/opencode.mdx | 4 +- .../docs/pt-br/pages/agent-setup/windsurf.mdx | 4 +- .../visao-geral/visao-geral-runtime.mdx | 2 +- .../troubleshooting/basic-troubleshooting.mdx | 2 +- .../menu-principal/compliance/pci-dss.mdx | 8 +- .../pages/menu-principal/compliance/soc.mdx | 4 +- .../gerencie-contas/criar-conta.mdx | 105 +++++---- .../performance/minimizar-o-downtime.mdx | 158 +++++++++++++ .../performance/modo-de-manutencao.mdx | 133 +++++++++++ .../performance/testar-a-velocidade.mdx | 104 +++++++++ .../comecar-com-um-template.mdx | 2 +- .../ponto-de-partida/fundamentos.mdx | 53 ++++- .../ponto-de-partida/visao-geral-da-azion.mdx | 144 +++++++----- .../pages/menu-principal/pricing/pricing.mdx | 4 +- .../migrar-para-a-azion.mdx | 213 ++++++++++++------ .../usar-um-template-via-rtm.mdx | 2 +- .../contas/account-lockout-policy.mdx | 6 +- .../referencia/contas/activity-history.mdx | 2 +- .../referencia/contas/clientes.mdx | 2 +- .../referencia/contas/configuracoes-conta.mdx | 8 +- .../contas/contas-equipes-e-usuarios.mdx | 64 ++++++ .../contas/multi-factor-authentication.mdx | 4 +- .../referencia/contas/personal-tokens.mdx | 7 +- .../referencia/contas/social-login.mdx | 9 +- .../referencia/contas/teams-permissions.mdx | 2 +- .../contas/user-session-timeout.mdx | 6 +- .../referencia/contas/users-management.mdx | 4 +- .../referencia/contas/your-settings.mdx | 10 +- .../referencia/secure/api-v4-migration.mdx | 44 ++-- .../web-application-firewall.mdx | 2 +- .../servicos/http-error-status-codes.mdx | 14 +- .../pages/primeiro-deploy/primeiro-deploy.mdx | 14 +- .../responsabilidade-compartilhada.mdx | 2 +- src/data/architectures-home/en.ts | 2 +- src/data/architectures-home/pt-br.ts | 2 +- src/data/devtools-home/en.ts | 2 +- src/data/devtools-home/pt-br.ts | 2 +- src/data/docs-home/en.ts | 8 +- src/data/docs-home/pt-br.ts | 8 +- src/data/platform-topology/en.ts | 165 ++++++++++++++ src/data/platform-topology/index.ts | 18 ++ src/data/platform-topology/pt-br.ts | 165 ++++++++++++++ src/data/platform-topology/types.ts | 67 ++++++ src/data/use-cases/en.ts | 186 +++++++++++++++ src/data/use-cases/index.ts | 12 + src/data/use-cases/pt-br.ts | 187 +++++++++++++++ src/data/use-cases/types.ts | 30 +++ src/i18n/en/footer.ts | 2 +- src/i18n/pt-br/footer.ts | 2 +- src/nav/exempt.json | 3 +- src/nav/resolve.ts | 22 +- src/nav/schema.ts | 16 +- src/nav/trees/fundamentals.json | 176 +++++++++++---- src/nav/trees/platform.json | 66 +++--- src/nav/trees/support.json | 3 - 106 files changed, 3243 insertions(+), 744 deletions(-) create mode 100644 src/components/webkit/PlatformTopology.vue create mode 100644 src/components/webkit/PlatformTopologyNode.vue create mode 100644 src/components/webkit/UseCaseList.vue create mode 100644 src/content/docs/en/pages/main-menu/performance/maintenance-mode.mdx create mode 100644 src/content/docs/en/pages/main-menu/performance/minimize-downtime.mdx create mode 100644 src/content/docs/en/pages/main-menu/performance/test-speed.mdx create mode 100644 src/content/docs/en/pages/main-menu/reference/accounts/accounts-teams-and-users.mdx create mode 100644 src/content/docs/pt-br/pages/menu-principal/performance/minimizar-o-downtime.mdx create mode 100644 src/content/docs/pt-br/pages/menu-principal/performance/modo-de-manutencao.mdx create mode 100644 src/content/docs/pt-br/pages/menu-principal/performance/testar-a-velocidade.mdx create mode 100644 src/content/docs/pt-br/pages/menu-principal/referencia/contas/contas-equipes-e-usuarios.mdx create mode 100644 src/data/platform-topology/en.ts create mode 100644 src/data/platform-topology/index.ts create mode 100644 src/data/platform-topology/pt-br.ts create mode 100644 src/data/platform-topology/types.ts create mode 100644 src/data/use-cases/en.ts create mode 100644 src/data/use-cases/index.ts create mode 100644 src/data/use-cases/pt-br.ts create mode 100644 src/data/use-cases/types.ts diff --git a/cicd/massive-redirect/en.json b/cicd/massive-redirect/en.json index c0befb8e27..dd65b4dd90 100644 --- a/cicd/massive-redirect/en.json +++ b/cicd/massive-redirect/en.json @@ -1926,5 +1926,17 @@ { "from": "https://www.azion.com/en/documentation/store/sql-database/quickstart-api/", "moved": "https://www.azion.com/en/documentation/store/sql-database/quickstart/" + }, + { + "from": "https://www.azion.com/en/documentation/platform/", + "moved": "https://www.azion.com/en/documentation/fundamentals/how-it-works/" + }, + { + "from": "https://www.azion.com/en/documentation/support/http-error-status-codes/", + "moved": "https://www.azion.com/en/documentation/fundamentals/http-status-codes/" + }, + { + "from": "https://www.azion.com/en/documentation/first-deploy/", + "moved": "https://www.azion.com/en/documentation/fundamentals/first-deploy/" } ] diff --git a/cicd/massive-redirect/pt-br.json b/cicd/massive-redirect/pt-br.json index 4d7d8ee421..e1b315692a 100644 --- a/cicd/massive-redirect/pt-br.json +++ b/cicd/massive-redirect/pt-br.json @@ -1950,5 +1950,17 @@ { "from": "https://www.azion.com/pt-br/documentacao/produtos/devtools/", "moved": "https://www.azion.com/pt-br/documentacao/devtools/" + }, + { + "from": "https://www.azion.com/pt-br/documentacao/plataforma/", + "moved": "https://www.azion.com/pt-br/documentacao/fundamentos/como-funciona/" + }, + { + "from": "https://www.azion.com/pt-br/documentacao/suporte/http-error-status-codes/", + "moved": "https://www.azion.com/pt-br/documentacao/fundamentos/codigos-de-status-http/" + }, + { + "from": "https://www.azion.com/pt-br/documentacao/primeiro-deploy/", + "moved": "https://www.azion.com/pt-br/documentacao/fundamentos/primeiro-deploy/" } ] diff --git a/scripts/eslint-rules/mdx-policy.mjs b/scripts/eslint-rules/mdx-policy.mjs index 0e01506acc..1d979b9312 100644 --- a/scripts/eslint-rules/mdx-policy.mjs +++ b/scripts/eslint-rules/mdx-policy.mjs @@ -55,6 +55,9 @@ const WRAPPER_ALLOWED = [ /^@aziontech\/icons$/, // the icon font side-effect import /^\.\/[^/]+\.vue$/, // a sibling wrapper, relative /^~\/components\/webkit\/[^/]+\.vue$/, // a sibling wrapper, aliased + // A copy module under src/data: structured content with no UI dependency, the same + // argument the MDX rule makes for .md partials. + /^~\/data\/[^/]+$/, // The docs search is an Algolia client; the dialog around it is webkit. A functional // dependency, not a UI one — the single named exception. /^algoliasearch(\/.+)?$/, diff --git a/src/components/webkit/PlatformTopology.vue b/src/components/webkit/PlatformTopology.vue new file mode 100644 index 0000000000..5568c97bea --- /dev/null +++ b/src/components/webkit/PlatformTopology.vue @@ -0,0 +1,187 @@ + + + diff --git a/src/components/webkit/PlatformTopologyNode.vue b/src/components/webkit/PlatformTopologyNode.vue new file mode 100644 index 0000000000..3d3309ec6a --- /dev/null +++ b/src/components/webkit/PlatformTopologyNode.vue @@ -0,0 +1,109 @@ + + + diff --git a/src/components/webkit/UseCaseList.vue b/src/components/webkit/UseCaseList.vue new file mode 100644 index 0000000000..13b0d1c321 --- /dev/null +++ b/src/components/webkit/UseCaseList.vue @@ -0,0 +1,42 @@ + + + diff --git a/src/content/docs/en/pages/agent-setup/claude-code.mdx b/src/content/docs/en/pages/agent-setup/claude-code.mdx index c74e1ffcfc..fec6165af1 100644 --- a/src/content/docs/en/pages/agent-setup/claude-code.mdx +++ b/src/content/docs/en/pages/agent-setup/claude-code.mdx @@ -213,13 +213,13 @@ Each of these exercises a different half of the connection — the documentation "headline": "Connectors", "tip": "Where an application fetches content from — a bucket, an origin server, a live stream. Called Origins before v4, which is why a model trained earlier still asks for one.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" }, "workload": { "headline": "Workloads", "tip": "The public entry point that binds a domain and its TLS to an application. Called Domains before v4.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" } }} items={[ diff --git a/src/content/docs/en/pages/agent-setup/codex.mdx b/src/content/docs/en/pages/agent-setup/codex.mdx index f0b50629b0..3ec04c8163 100644 --- a/src/content/docs/en/pages/agent-setup/codex.mdx +++ b/src/content/docs/en/pages/agent-setup/codex.mdx @@ -208,13 +208,13 @@ Each of these exercises a different half of the connection — the documentation "headline": "Connectors", "tip": "Where an application fetches content from — a bucket, an origin server, a live stream. Called Origins before v4, which is why a model trained earlier still asks for one.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" }, "workload": { "headline": "Workloads", "tip": "The public entry point that binds a domain and its TLS to an application. Called Domains before v4.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" } }} items={[ diff --git a/src/content/docs/en/pages/agent-setup/cursor.mdx b/src/content/docs/en/pages/agent-setup/cursor.mdx index b9ad916277..d3fb651069 100644 --- a/src/content/docs/en/pages/agent-setup/cursor.mdx +++ b/src/content/docs/en/pages/agent-setup/cursor.mdx @@ -205,13 +205,13 @@ Each of these exercises a different half of the connection — the documentation "headline": "Connectors", "tip": "Where an application fetches content from — a bucket, an origin server, a live stream. Called Origins before v4, which is why a model trained earlier still asks for one.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" }, "workload": { "headline": "Workloads", "tip": "The public entry point that binds a domain and its TLS to an application. Called Domains before v4.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" } }} items={[ diff --git a/src/content/docs/en/pages/agent-setup/gemini-cli.mdx b/src/content/docs/en/pages/agent-setup/gemini-cli.mdx index 9dffb904fd..dac85d7cac 100644 --- a/src/content/docs/en/pages/agent-setup/gemini-cli.mdx +++ b/src/content/docs/en/pages/agent-setup/gemini-cli.mdx @@ -215,13 +215,13 @@ Each of these exercises a different half of the connection — the documentation "headline": "Connectors", "tip": "Where an application fetches content from — a bucket, an origin server, a live stream. Called Origins before v4, which is why a model trained earlier still asks for one.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" }, "workload": { "headline": "Workloads", "tip": "The public entry point that binds a domain and its TLS to an application. Called Domains before v4.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" } }} items={[ diff --git a/src/content/docs/en/pages/agent-setup/github-copilot.mdx b/src/content/docs/en/pages/agent-setup/github-copilot.mdx index 8f9ce333be..267f7743b4 100644 --- a/src/content/docs/en/pages/agent-setup/github-copilot.mdx +++ b/src/content/docs/en/pages/agent-setup/github-copilot.mdx @@ -206,13 +206,13 @@ Each of these exercises a different half of the connection — the documentation "headline": "Connectors", "tip": "Where an application fetches content from — a bucket, an origin server, a live stream. Called Origins before v4, which is why a model trained earlier still asks for one.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" }, "workload": { "headline": "Workloads", "tip": "The public entry point that binds a domain and its TLS to an application. Called Domains before v4.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" } }} items={[ diff --git a/src/content/docs/en/pages/agent-setup/opencode.mdx b/src/content/docs/en/pages/agent-setup/opencode.mdx index cb5b96dc46..7011fc6183 100644 --- a/src/content/docs/en/pages/agent-setup/opencode.mdx +++ b/src/content/docs/en/pages/agent-setup/opencode.mdx @@ -216,13 +216,13 @@ Each of these exercises a different half of the connection — the documentation "headline": "Connectors", "tip": "Where an application fetches content from — a bucket, an origin server, a live stream. Called Origins before v4, which is why a model trained earlier still asks for one.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" }, "workload": { "headline": "Workloads", "tip": "The public entry point that binds a domain and its TLS to an application. Called Domains before v4.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" } }} items={[ diff --git a/src/content/docs/en/pages/agent-setup/windsurf.mdx b/src/content/docs/en/pages/agent-setup/windsurf.mdx index b6660a4d19..f4ace47072 100644 --- a/src/content/docs/en/pages/agent-setup/windsurf.mdx +++ b/src/content/docs/en/pages/agent-setup/windsurf.mdx @@ -205,13 +205,13 @@ Each of these exercises a different half of the connection — the documentation "headline": "Connectors", "tip": "Where an application fetches content from — a bucket, an origin server, a live stream. Called Origins before v4, which is why a model trained earlier still asks for one.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" }, "workload": { "headline": "Workloads", "tip": "The public entry point that binds a domain and its TLS to an application. Called Domains before v4.", "cta": "Platform overview", - "href": "/en/documentation/platform/" + "href": "/en/documentation/fundamentals/how-it-works/" } }} items={[ 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 efe456c822..458152a236 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 @@ -54,7 +54,7 @@ Learn more about [Strict mode](https://developer.mozilla.org/en-US/docs/Web/Java Every ceiling one invocation runs inside, and what happens past each one. The `active` field, which stops an instance from running without deleting it. What an application enables before a function can run on it. - Where the code physically executes. + Where the code physically executes. The support and community channels. diff --git a/src/content/docs/en/pages/first-deploy/first-deploy.mdx b/src/content/docs/en/pages/first-deploy/first-deploy.mdx index 7b24533097..00eeae2c61 100644 --- a/src/content/docs/en/pages/first-deploy/first-deploy.mdx +++ b/src/content/docs/en/pages/first-deploy/first-deploy.mdx @@ -3,7 +3,7 @@ title: First deploy in a few minutes description: By the end of this tutorial, an application will be live on the Azion Web Platform, answering HTTP 200 on its own Azion domain. It takes a few minutes. meta_tags: 'first deploy, getting started, templates, github, cli' namespace: documentation_first_deploy -permalink: /documentation/first-deploy/ +permalink: /documentation/fundamentals/first-deploy/ --- import DocCard from '@aziontech/webkit/doc-card'; @@ -19,7 +19,7 @@ import DocItem from '@aziontech/webkit/doc-item'; Three complete paths get you there. Pick one. They all end in the same place: - You're starting from scratch and want a ready-made project. + You are starting from scratch and want a ready-made project. Your project already lives in a GitHub repository. Your project is on your machine and you prefer the terminal. @@ -28,24 +28,24 @@ Three complete paths get you there. Pick one. They all end in the same place: ## Before you start -All you need is an Azion account. You can create one for free, and it doesn't ask for a credit card. Anything path-specific is listed in the path itself. +All you need is an Azion account. You can create one for free, and it does not ask for a credit card. Anything path-specific is listed in the path itself. ## Deploy a template via Console -Templates are ready-made projects (e-commerce, blogs, APIs, full-stack SSR) that go live in a few clicks. You don't need any local tooling. +Templates are ready-made projects (e-commerce, blogs, APIs, full-stack SSR) that go live in a few clicks. You do not need any local tooling. -Some templates are integrated with third-party services, so you may need to create accounts, generate tokens, or activate Azion products before deploying. Templates integrated with GitHub ask you to connect your account: click Connect with GitHub when prompted and confirm the connection in the pop-up. Each template's guide lists its specific prerequisites. +Some templates are integrated with third-party services, so you may need to create accounts, generate tokens, or activate Azion products before deploying. Templates integrated with GitHub ask you to connect your account: select Connect with GitHub when prompted and confirm the connection in the window that opens. Each template's guide lists its specific prerequisites. - + - + -Follow the deploy through the logs window. When it finishes, the page shows your application's name, its deploy logs, and its Azion domain. Some templates also create a function and apply pre-defined configurations to optimize your application's performance. The template's guide lists what's included. +Follow the deploy through the logs window. When it finishes, the page shows your application's name, its deploy logs, and its Azion domain. Some templates also create a function and apply pre-defined configurations to optimize your application's performance. The template's guide lists what is included. ### Test it @@ -58,14 +58,14 @@ curl -I https:// Open the same URL in the browser to see your application running. -New URLs can take a few minutes to propagate to Azion's edge locations. If you get an error right after deploying, wait a moment and try again. +New URLs can take a few minutes to propagate to Azion's data centers. If you get an error right after deploying, wait a moment and try again. ## Import a project from GitHub You need a GitHub account and a repository using one of the supported frameworks. - + @@ -75,7 +75,7 @@ Open the same URL in the browser to see your application running. - + ### Test it @@ -85,7 +85,7 @@ curl -I https:// # HTTP/2 200 ``` -Open the Azion domain in the browser to see your application running. If you get an error right away, wait a few minutes: new URLs take a moment to propagate to Azion's edge locations. +Open the Azion domain in the browser to see your application running. If you get an error right away, wait a few minutes: new URLs take a moment to propagate to Azion's data centers. ## Deploy with Azion CLI @@ -117,7 +117,7 @@ Open the Azion domain in the browser to see your application running. If you get azion link ``` - The CLI guides you from there: confirm the linking, accept or change the suggested application name, and pick a preset matching your framework. When it asks `Do you want to deploy your project?`, answer yes. (If you answer no, run `azion deploy` when you're ready.) + The CLI guides you from there: confirm the linking, accept or change the suggested application name, and pick a preset matching your framework. When it asks `Do you want to deploy your project?`, answer yes. (If you answer no, run `azion deploy` when you are ready.) At the end of the deploy, the CLI prints your application's Azion domain. @@ -129,14 +129,14 @@ Open the Azion domain in the browser to see your application running. If you get # HTTP/2 200 ``` - If you get an error right away, wait a few minutes: new URLs take a moment to propagate to Azion's edge locations. + If you get an error right away, wait a few minutes: new URLs take a moment to propagate to Azion's data centers. ## What you built -You deployed an application to Azion's global network and confirmed it answers on its own domain. The workflow is the same one you'll use for production projects. +You deployed an application to Azion's distributed infrastructure and confirmed it answers on its own domain. The workflow is the same one you will use for production projects. ## Next steps @@ -146,13 +146,14 @@ You deployed an application to Azion's global network and confirmed it answers o Follow metrics and events in real time. -## Related products +## Related resources The object you just created: the rules, the origins and the locations that answer for your domain. - Run your own JavaScript at the edge, on the request or on the response, in the same application. - Decide what the edge answers from memory, for how long, and by which key. + Run your own JavaScript on Azion's distributed infrastructure, on the request or on the response, in the same application. + Decide what Azion answers from cache, for how long, and by which key. Link, deploy and roll back a project from the terminal you already have open. + Follow the request you just served through Azion's distributed infrastructure to your origin. diff --git a/src/content/docs/en/pages/guides/troubleshooting/basic-troubleshooting.mdx b/src/content/docs/en/pages/guides/troubleshooting/basic-troubleshooting.mdx index d0897db3ad..aa1ece397a 100644 --- a/src/content/docs/en/pages/guides/troubleshooting/basic-troubleshooting.mdx +++ b/src/content/docs/en/pages/guides/troubleshooting/basic-troubleshooting.mdx @@ -64,7 +64,7 @@ How can you find out exactly why this request was blocked? For the steps below, copy the **Request ID** displayed on the page. :::tip -The **Request ID** is the same identifier shown on the Azion error page under **Error Details**. For a description of all fields on that page and what each HTTP status code means, see [HTTP Error Status Codes](/en/documentation/support/http-error-status-codes/). +The **Request ID** is the same identifier shown on the Azion error page under **Error Details**. For a description of all fields on that page and what each HTTP status code means, see [HTTP Error Status Codes](/en/documentation/fundamentals/http-status-codes/). ::: ### In Real Time Events 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 9d4d3ceb82..7a5a925b41 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 @@ -1,126 +1,201 @@ --- -title: How to migrate your application to Azion -description: Learn how you can bring your applications and infrastructure to Azion. -meta_tags: 'azion, migrate, domains, distributed architecture' +title: Migrate an application to Azion +description: >- + Move an application from another provider to Azion, from the connector and + the workload to the DNS change, with a test before the switch. +meta_tags: 'azion, migrate, migration, connector, workload, custom domain, dns' namespace: documentation_migrate_to_azion permalink: /documentation/fundamentals/migrate-to-azion/ --- -import DocButton from '~/components/webkit/DocButton.vue'; -This guide provides a step-by-step path for migrating existing applications to Azion. It outlines the necessary requirements and details the steps for a successful transfer of applications from other services to a distributed architecture. +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' +import Code from '~/components/webkit/CodeBlock.vue' + +An application that runs on another provider has an origin, a domain, and rules that shape its traffic. Migrating it to Azion means rebuilding that chain on the platform and moving the domain last, so the application keeps serving while you work. You register the origin as a [connector](/en/documentation/platform/connectors/), serve it through an [application](/en/documentation/platform/applications/), expose it on a [workload](/en/documentation/platform/workloads/), and point the domain at the workload. + +If you are leaving one of the providers below, follow its guide instead. Each one maps the provider's services to their Azion equivalents. + +| Provider | The guide covers | +| --- | --- | +| [Akamai](/en/documentation/guides/platform/migration/akamai-migration-guide/) | Content delivery, application security, functions, key-value storage, traffic rules, DNS, traffic management, object storage, log streaming, monitoring, and DDoS protection | +| [AWS](/en/documentation/guides/platform/migration/aws-migration-guide/) | Content delivery, functions, object storage, key-value storage, DNS, WAF, DDoS protection, and observability | +| [Cloudflare](/en/documentation/guides/platform/migration/cloudflare-migration-guide/) | Functions, key-value storage, object storage, SQL database, DNS, WAF, and more | +| [Fastly](/en/documentation/guides/platform/migration/fastly-migration-guide/) | Content delivery, functions, key-value storage, object storage, WAF, logging, and observability | +| [Vercel](/en/documentation/guides/platform/migration/vercel-migration-guide/) | Projects, preview deployments, functions, object storage, configuration storage, firewall, web analytics, and observability | --- -## Migrating from other platforms +## Prerequisites -If you're migrating from a specific platform, Azion provides dedicated migration guides: +- An Azion account. To open one, refer to [Create an account](/en/documentation/fundamentals/creating-account/). +- The address of the current origin: a host name, an IPv4 or IPv6 address, or an [Object Storage](/en/documentation/store/object-storage/) bucket. +- Access to the DNS records of the domain at your DNS provider. +- (Optional) The [Azion CLI](/en/documentation/devtools/cli/), for local development and deployment. -- **Akamai**: [Akamai to Azion migration guide](/en/documentation/guides/platform/migration/akamai-migration-guide/) - covers Ion, App & API Protector, EdgeWorkers, EdgeKV, Cloudlets, Edge DNS, Global Traffic Management, NetStorage, DataStream, mPulse, and Prolexic -- **AWS**: [AWS to Azion migration guide](/en/documentation/guides/platform/migration/aws-migration-guide/) - covers CloudFront, Lambda, S3, DynamoDB, Route 53, WAF, DDoS protection, and observability -- **Cloudflare**: [Cloudflare to Azion migration guide](/en/documentation/guides/platform/migration/cloudflare-migration-guide/) — covers Workers, KV, R2, D1, DNS, WAF, and more -- **Fastly**: [Fastly to Azion migration guide](/en/documentation/guides/platform/migration/fastly-migration-guide/) - covers Full-Site Delivery, Compute, Edge Data Storage, Object Storage, WAF, logging, and observability -- **Vercel**: [Vercel to Azion migration guide](/en/documentation/guides/platform/migration/vercel-migration-guide/) - covers Projects, Preview Deployments, Functions, Blob, Edge Config, Firewall, Web Analytics, and observability +:::note +With the **Business** support plan or higher, [Integration Services](/en/documentation/services/integration-services/) gives you access to Azion specialists during the migration. For the plans, refer to [Azion Support](https://www.azion.com/en/professional-services/). +::: --- -## Why migrate to Azion +## Register the origin as a connector -Migrating to Azion Web Platform provides distinct advantages for modern applications: +A connector tells Azion where to fetch the content and code of the application. To create it in Azion Console: -**Performance** -- Cold-start-free execution on a distributed architecture -- Instant deploys with zero-downtime updates -- Global points of presence that execute logic close to your users + + -**Cost efficiency** -- Zero egress fees for data transfer over Azion's infrastructure -- Predictable pricing without hidden bandwidth charges + Access [Azion Console](https://console.azion.com/) > **Connectors**. -**Platform unification** -- Build, secure, store, and observe in one integrated environment -- Consistent APIs and configuration patterns across all capabilities -- Single platform for applications, functions, storage, databases, and security + + + -:::note -If you're subscribed to **Business Support** or higher, you have access to specialists via [Integration Services](/en/documentation/services/integration-services/). For more detailed information, see [Azion Support](https://www.azion.com/en/professional-services/). -::: + In **Connector Type**, select _HTTP_ for a host name or an IP address, or _Object Storage_ for a bucket. + + + + + In **Address**, enter the origin address. If the origin answers to a virtual host that differs from that address, enter it in **Host Header**. + + + + + +The connector is ready to be set as the origin of the application. For the remaining connection options, refer to [Connectors](/en/documentation/platform/connectors/). --- -## Prerequisites +## Create the application -Before starting the migration, ensure you have the following: +The application holds the rules, the cache settings, and the functions that serve the content. To start from a template, open [Templates and Integrations](/en/documentation/marketplace/templates-and-integrations-overview/) and deploy one; the [Azion Starter Kit](/en/documentation/guides/application-development/frameworks/azion-starter-kit/) gives you a basic project to explore the platform, and the [full list of templates](/en/documentation/guides/#azion-templates) covers the common frameworks. To start from your own code, refer to [Build an application](/en/documentation/guides/application-development/getting-started/build-an-application/). -- **Azion account**: Create a free account at [Azion Console](https://console.azion.com/). You'll need access to the Console to create applications and configure domains. - +To route the application to the connector: -- **Azion CLI** (optional but recommended): Install the CLI for local development and deployment. The CLI provides a streamlined workflow for building, testing, and deploying applications. - + + ---- + Access [Azion Console](https://console.azion.com/) > **Applications** > **your application**. -## Before you begin + + + -Before you migrate applications to Azion, there are two major variables that must exist: + Edit the default rule, or add a rule for the request phase. -1. **Connector**: the source server of the application. This entry point takes the form of either a host, an IPv4, or an IPv6 address of a storage service or an existing application. - + + -2. **Workload**: the target domain of the application. This output takes the form of an Azion domain, which can be pointed to a custom domain. - + In **Criteria**, set **If `${uri}` starts with `/`**, so the rule covers the whole application. -Most applications need a connector from which Azion retrieves the content and code that make them up. That application passes through Azion's global points of presence for it to be delivered to users through a domain address associated with a workload. + + - + In **Behavior**, select **Set Connector** and select the connector. + + + + + +Requests that reach the application are now fetched from the connector. For the other settings, refer to [Applications](/en/documentation/platform/applications/). --- -## Step 1: Create an application +## Expose the application on a workload -You can start by creating an application using a basic template. A recommended option is the [Azion Starter Kit](/en/documentation/guides/application-development/frameworks/azion-starter-kit/) template, which helps you create a basic edge stack to explore the platform. +A workload gives the application its Azion domain and receives the custom domain later. To create it: - + + -See the [full list of available templates](/en/documentation/guides/#azion-templates). + Access [Azion Console](https://console.azion.com/) > **Workloads**. ---- + + + -## Step 2: Test locally + Enter a **Name**. In **Infrastructure**, select _Production_. This choice cannot be changed after the workload is saved. -Before fully deploying the application, the recommendation is to [stage your application through the hosts file](/en/documentation/guides/application-development/getting-started/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. + + ---- + In **Subdomain** and **Domain**, enter the host name the application answers to. For example: `www` and `example.com`. -## Step 3: Point the domain to a workload + + -The final step to fully migrate your application to Azion is to point your custom domain to the Azion's workload. By doing so, you allow users to access your application through its domain, reducing latency and processing costs on the origin. + In **Applications**, select the application. - + + + + In **Firewall**, select the firewall that protects the application. + + + + + In **Digital Certificate**, select the certificate for the domain, or the Azion SAN certificate to use the workload domain. + + + + + +Azion generates the workload domain, in the format `xxxxxxxxxx.map.azionedge.net`. It is the address the custom domain will point to. --- -## After migration +## Test the application before moving the domain -Once your application is running on Azion, configure these essential features: +While the public DNS still points to the current provider, your computer can reach the application on Azion through its `hosts` file. This is where a misconfiguration from the migration shows up before any user sees it. To stage the application: -### Configure observability +1. Resolve the workload domain to find the addresses that serve it: -Monitor your application's performance and behavior in real time: + -- **[Real-Time Metrics](/en/documentation/platform/real-time-metrics/)** — View requests, bandwidth, latency, and cache hit ratios through dashboards and GraphQL API -- **[Real-Time Events](/en/documentation/observe/real-time-events/)** — Access detailed logs for requests, functions, WAF events, and more for troubleshooting + The response lists the domain and one or more addresses: -### Enable security features + ```bash + xxxxxxxxxx.map.azionedge.net has address 200.0.0.0 + ``` + +2. In the `hosts` file of your computer, add a line that maps the custom domain to one of those addresses. +3. Open the custom domain in a private browser window, so a cached DNS answer does not send you to the current provider. + +The application loads from Azion under its own domain. For the location of the `hosts` file on each operating system, refer to [How to stage an application through the hosts file](/en/documentation/guides/application-development/getting-started/stage-applications-through-hosts-file/). + +--- -Protect your application with Azion's security capabilities: +## Point the domain to the workload -- **[Web Application Firewall](/en/documentation/secure/waf/)** — Guard against SQL injection, XSS, and other application-layer attacks -- **[DDoS Protection](/en/documentation/platform/ddos-protection/)** — Automatic protection against volumetric and protocol attacks +The DNS change is the switch: once the domain resolves to the workload, users reach the application through Azion. To point the domain: -### Continue learning +1. Sign in to your DNS provider and open the records of the domain. +2. Create or edit the CNAME record of the subdomain, pointing it to the workload domain: + + | Name | Value | Type | + | --- | --- | --- | + | `www` | `xxxxxxxxxx.map.azionedge.net` | CNAME | + +3. Save the record. + +DNS changes take time to propagate. To check what the resolvers answer, refer to [How to look up DNS servers with Dig command](/en/documentation/guides/application-security/dns/run-the-dig-command/). + +:::note +A domain apex cannot hold a CNAME record at every provider. To point the apex, [migrate the nameservers to Azion](/en/documentation/guides/platform/migration/migrate-ns-to-azion/). For the Console settings of the custom domain, refer to [How to point a domain to Azion](/en/documentation/guides/platform/migration/point-domain-to-azion/). +::: + +--- -Explore the documentation to get the most from Azion Web Platform: +## Next steps -- [Applications documentation](/en/documentation/platform/applications/) -- [Functions documentation](/en/documentation/build/functions/) -- [Rules Engine documentation](/en/documentation/platform/applications/rules-engine/) + + + + + + + + diff --git a/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/use-a-template.mdx b/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/use-a-template.mdx index 0a1d73dd89..4c1c5d6a74 100644 --- a/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/use-a-template.mdx +++ b/src/content/docs/en/pages/main-menu/additional-resources/templates-and-integrations/use-a-template.mdx @@ -67,7 +67,7 @@ After the deployment, each template creates a new application and its Azion doma Go to the [guides page](https://www.azion.com/en/documentation/guides/#azion-templates) and check more details on the specific template you're willing to use. :::tip -To know more on how to edit and customize your application's main settings, go to the [Configuring main settings](/en/documentation/guides/application-development/getting-started/configure-main-settings/) guide. You can also [Go live with Azion](/en/documentation/products/go-live-with-azion/), adding a custom domain and poiting your traffic. +To know more on how to edit and customize your application's main settings, go to the [Configuring main settings](/en/documentation/guides/application-development/getting-started/configure-main-settings/) guide. You can also [Go live with Azion](/en/documentation/fundamentals/), adding a custom domain and poiting your traffic. ::: diff --git a/src/content/docs/en/pages/main-menu/compliance/pci-dss.mdx b/src/content/docs/en/pages/main-menu/compliance/pci-dss.mdx index 20fe62909c..9036b2dc88 100644 --- a/src/content/docs/en/pages/main-menu/compliance/pci-dss.mdx +++ b/src/content/docs/en/pages/main-menu/compliance/pci-dss.mdx @@ -2,7 +2,7 @@ title: PCI Compliance description: >- As a PCI-DSS 4.0 Level 1 Service Provider, Azion keeps your valuable data - secure across all edge locations, without compromising your site's + secure across all data centers, without compromising your site's performance. meta_tags: 'Azion, edge computing, compliance, payment card, data security and privacy' namespace: documentation_compliance_pci @@ -13,7 +13,7 @@ As part of the ongoing compliance efforts, Azion is always improving the interna --- -## What's PCI +## PCI DSS **PCI DSS (Payment Card Industry Data Security Standard)** is a certification issued by the **PCI Security Standards Council** that defines the international security requirements necessary for companies in the payment card sector and their service providers to operate reliably, adequately protecting both their technology systems and their customers' data and operations. @@ -25,9 +25,9 @@ Although PCI certification is required for e-commerce, all digital businesses ca --- -## What this means for Azion customers +## Implications for Azion customers -As a **PCI-DSS 4.0.1 Level 1 Service Provider**, Azion keeps your valuable data secure across all edge locations, without compromising your site's performance. +As a **PCI-DSS 4.0.1 Level 1 Service Provider**, Azion keeps your valuable data secure across all data centers, without compromising your site's performance. As a result, you can: @@ -51,7 +51,7 @@ Azion contracted a [Qualified Security Assessor (QSA)](https://listings.pcisecur - **Which regions and products are covered?** -Azion's PCI compliance extends across the entire Azion Web Platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), covering all regions where it's deployed. Presently, Azion is deployed in six continents. +Azion's PCI compliance extends across the entire Azion Web Platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), covering all regions where it is deployed. Presently, Azion is deployed in six continents. - **How long is Azion's Attestation of Compliance (AOC) valid for?** diff --git a/src/content/docs/en/pages/main-menu/compliance/soc-2.mdx b/src/content/docs/en/pages/main-menu/compliance/soc-2.mdx index f01cc7eaef..cabf1c78e4 100644 --- a/src/content/docs/en/pages/main-menu/compliance/soc-2.mdx +++ b/src/content/docs/en/pages/main-menu/compliance/soc-2.mdx @@ -12,9 +12,9 @@ Azion consistently strives to enhance internal security controls to assure custo --- -## What are SOC 2 Type II and SOC 3? +## SOC 2 Type II and SOC 3 -**SOC 2** is an auditing procedure developed by the **American Institute of Certified Public Accountants (AICPA)** to ensure that service providers are taking the necessary steps to maintain data security and privacy. SOC 2 attests to the trustworthiness of services provided by the organization, and it's composed of five “trust service principles” that serve as a backbone for secure data management. +**SOC 2** is an auditing procedure developed by the **American Institute of Certified Public Accountants (AICPA)** to ensure that service providers are taking the necessary steps to maintain data security and privacy. SOC 2 attests to the trustworthiness of services provided by the organization, and it is composed of five “trust service principles” that serve as a backbone for secure data management. --- @@ -24,13 +24,13 @@ Azion is evaluated on two different trust principles: **Security** and **Availab This third-party evaluation assesses the platform's ability to prevent unauthorized access, security breaches, and security-related issues that might impact availability. -Azion's **SOC 2 Type 2** attestation applies to the entire Azion Web Platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), covering all regions where it's deployed. Azion invested effort into attesting the entire Platform for mainly one reason: performance. Flawless experiences demand that apps and data are processed and delivered as close to end users as possible, and certifying less than the entire network and Platform would lead to a performance tradeoff. +Azion's **SOC 2 Type 2** attestation applies to the entire Azion Web Platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), covering all regions where it is deployed. Azion invested effort into attesting the entire Platform for mainly one reason: performance. Flawless experiences demand that apps and data are processed and delivered as close to end users as possible, and certifying less than the entire network and Platform would lead to a performance tradeoff. Additionally, Azion has gone a step further, gaining **SOC 3** attestation for customers with the most stringent regulatory and compliance needs. The SOC 3 report, attested by the same auditors who verified Azion's controls for SOC 2 Type 2, outlines information related to Azion's internal controls for security and availability, and can be obtained by Azion customers by reaching out to the **Azion Support Team**. --- -## What this means for Azion customers? +## Implications for Azion customers SOC 2 Type 2 and SOC 3 designations can be used to simplify your audits and to ensure the security level of the Azion Web Platform services you use. @@ -48,7 +48,7 @@ Azion's SOC 2 and SOC 3 reports are issued annually. Customers with **Enterprise - **Which Azion products and world regions are covered?** -Azion's SOC 2 and SOC 3 reports cover the entire web platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), in all regions where it's deployed. Presently, Azion is deployed on six continents. +Azion's SOC 2 and SOC 3 reports cover the entire web platform, which includes the Applications product and its add-ons (Application Accelerator, Cache, Functions, and Load Balancer) and the Firewall product and its add-ons (DDoS Protection, Network Shield, Web Application Firewall - WAF, and Origin Shield), in all regions where it is deployed. Presently, Azion is deployed on six continents. - **Does Azion have certificates of SOC 2 and SOC 3 compliance?** 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 4ad1a20537..e513de6580 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 @@ -1,107 +1,122 @@ --- -title: "How Azion works" +title: How Azion works description: >- - This documentation introduces the Azion Web Platform, which unifies app development, security, and observability on a global infrastructure so you can ship faster with performance and control. + Follow a request from the user through Azion's distributed infrastructure to + your origin, and see what each resource on the path adds along the way. meta_tags: >- - Azion, application, Azion Web Platform, developer platform, application platform, modern application platform, global web platform, serverless platform, serverless computing, serverless functions, functions, application development, application security, API security, web application firewall, WAF, DDoS protection, DDoS mitigation + Azion, Azion Platform, how Azion works, distributed infrastructure, request path, data center, serverless, WAF, DDoS protection, cache, observability, Console, CLI, API, Terraform namespace: documentation_azion_platform_overview -permalink: /documentation/platform/ +permalink: /documentation/fundamentals/how-it-works/ --- +import UseCaseList from '~/components/webkit/UseCaseList.vue' +import FrameBox from '@aziontech/webkit/frame-box' +import ItemList from '@aziontech/webkit/item-list' +import DocItem from '@aziontech/webkit/doc-item' -**Azion Web Platform** is a fully managed **developer platform** to **build, secure, and scale** modern applications on a **global distributed infrastructure**, which includes operating and monitoring them: fast deploys, no cold starts, and real-time visibility. +A request for your application does not travel to a server you run. It reaches the data center of Azion's distributed infrastructure with the best route to it, and the configuration you saved decides what happens next: whether the request is blocked, answered from cache, handled by your code, or forwarded to your origin. **Azion Platform** is the integrated technology and the set of interfaces where that configuration lives, and where you build, secure, and scale applications, which includes operating and monitoring them. -Azion Web Platform unifies **serverless**, **security**, **content delivery/acceleration**, **storage**, and **real-time observability** so teams can ship applications worldwide with consistent performance. Trusted by global leaders such as Prime Video, Neon, Global Fashion Group, and Radware, Azion provides the fastest path to modern applications. Discover how Azion can transform your digital experiences at [www.azion.com](https://www.azion.com/). +Azion includes content delivery and caching, but it is broader than a CDN. The same infrastructure runs application code with no server to provision, filters the traffic that reaches your applications and APIs, stores the data they read, and reports every request in real time. This page covers where the platform runs, the path a request takes, what you enable on each resource of that path, and the interfaces you manage it through. --- -## What the platform includes -Use Azion to: -- Run **applications and serverless code** across a distributed global network -- Protect apps and APIs with **WAF, DDoS mitigation, and bot protection** -- Store and access data with **distributed storage** and database options -- Monitor everything with **real-time metrics and events** -- Build AI-powered experiences using Azion’s **AI capabilities** on the same platform +## Distributed infrastructure ---- +Azion runs your configuration in data centers spread across the world, and each request is served by the data center with the best route to it. The route is chosen by latency, network conditions, and load at the moment the request arrives, so two users in different countries requesting the same page are each served nearby, from the same configuration. Compute and data sit close to the user, which reduces latency and improves reliability. Deploys are fast, functions run with no cold starts, and visibility into traffic is real time. For the list of data centers, refer to [Our Network](https://www.azion.com/en/products/our-network/). + +## Request path + +The diagram shows the path of one request, from the user to your origin and back. Inside Azion Platform, the request is routed to a data center, where the resources you configured run, and content that the data center cannot answer is fetched through the delivery layer: -## Core Concepts +```mermaid +flowchart LR + user([User]) --> routing[Routing] + subgraph platform [Azion Platform] + routing --> dc + subgraph dc [Data center] + firewall[Firewall] + applications[Applications] + cache[Cache] + accelerator[Application Accelerator] + functions[Functions] + image[Image Processor] + end + dc --> delivery[Tiered Cache and Load Balancer] + end + delivery --> origin[(Origin)] +``` -### Distributed computing -Azion runs workloads across multiple locations worldwide to reduce latency and improve reliability. This approach places compute and data closer to where they're needed—near your users on a global network of points of presence. +Requests travel from left to right. Responses return along the same path. -### Platform characteristics -A platform designed for distributed workloads should provide: -- One workflow for **build, security, deployment, and observability** -- **Self-service** with automation-first operations (NoOps) -- **Open standards** and API-first management -- Continuous monitoring with actionable telemetry -- Performance controls for traffic, caching, and routing -- Global coverage with smart traffic steering +1. The user's request reaches Azion. Azion selects the best route and forwards the request to the nearest data center, based on latency, network conditions, and load. +2. At that data center, Azion applies your configuration and logic: the workload that owns the domain, the security policies of its firewall, the caching behavior and rules of its application, and the code of the functions they run. +3. When the cache cannot answer the request, the application fetches the content from your origin through its connector. [Tiered Cache](/en/documentation/build/cache/) adds a second cache layer between the data centers and your origin, and [Load Balancer](/en/documentation/platform/load-balancer/) spreads the fetch across several addresses. +4. The response is delivered to the user, and the request appears in your metrics, events, and streams. + +The resources on that path bind to one another: a workload binds a firewall, an application, and a custom page set, and the application fetches through a connector. For the interactive diagram and what each resource attaches to, refer to [Platform resources topology](/en/documentation/fundamentals/#platform-resources-topology). --- -## How Azion Web Platform handles a request +## Platform resources on the request path -**Azion Web Platform** routes each request through its global network to serve users from the best available location. +Everything you enable or create lives on the resources of the request path. Some of it is enabled on a resource you already have, such as a rule set applied to the firewall or a switch on the application; the rest are resources you create on their own, such as a bucket or a DNS zone. The table lists each one by the resource it attaches to, with a link to its reference: -![Graphic about how Azion works](/assets/docs/images/uploads/request_flow.png) +| Resource | What you enable or create on it | Reference | +| --- | --- | --- | +| Workload | The TLS certificate bound to the workload, and DDoS mitigation, which applies to every workload with nothing to enable. | [Certificate Manager](/en/documentation/platform/certificate-manager/), [DDoS Protection](/en/documentation/platform/ddos-protection/) | +| Firewall | A WAF rule set applied to the firewall, a Bot Manager instance running on it, and the network lists its rules reference. | [WAF](/en/documentation/secure/waf/), [Bot Manager](/en/documentation/secure/bot-manager/), [Network Shield](/en/documentation/secure/network-shield/) | +| Application | Cache settings, the Application Accelerator and Image Processor switches, the functions instantiated on the application, and the custom page set assigned to it. | [Cache](/en/documentation/build/cache/), [Application Accelerator](/en/documentation/build/application-accelerator/), [Image Processor](/en/documentation/build/image-processor/), [Custom Pages](/en/documentation/platform/custom-pages/) | +| Connector | Load balancing across several addresses, and Origin Shield, which lets only Azion's IP ranges reach the origin. | [Load Balancer](/en/documentation/platform/load-balancer/), [Origin Shield](/en/documentation/secure/origin-shield/) | +| Resources you create on their own | Functions, buckets, databases, key-value namespaces, DNS zones, streams, and the infrastructure you run yourself with Orchestrator. | [Functions](/en/documentation/build/functions/), [Object Storage](/en/documentation/store/object-storage/), [SQL Database](/en/documentation/store/sql-database/), [KV Store](/en/documentation/store/kv-store/), [Edge DNS](/en/documentation/secure/edge-dns/), [Data Stream](/en/documentation/observe/data-stream/), [Orchestrator](/en/documentation/build/orchestrator/) | +| Inside a function | The models your code calls, and the adapters you fine-tune for them. | [AI Inference](/en/documentation/build/ai-inference/), [LoRA Fine-Tune](/en/documentation/build/ai-inference/lora-fine-tune/) | +| Everything above | The raw events, metrics, and real-user measurements that report what the platform did with each request. | [Real-Time Events](/en/documentation/observe/real-time-events/), [Real-Time Metrics](/en/documentation/platform/real-time-metrics/), [Edge Pulse](/en/documentation/observe/edge-pulse/) | -1. A user request reaches a service running on **Azion Web Platform**. Azion selects the best route and forwards it to the **nearest location** based on latency, network conditions, and load. -2. At that location, Azion applies your **configuration and logic** (security policies, caching behavior, application code, and other rules) to generate a response. - - If needed, Azion fetches content from your origin and returns the result. -3. The response is delivered to the user. +Every control in the table can be automated through the API and infrastructure as code. Azion's catalog groups everything in the table into four categories, Build, Store, Secure, and Observe; the [pricing page](/en/documentation/fundamentals/pricing/) is organized that way. ---- +## What you can build -## What you can build with Azion +The same chain of resources serves very different workloads. Azion organizes them into five solutions, and the use cases below are the ones teams most often start from. Each one links to the architecture that implements it, or, where no architecture is published yet, to the reference it starts from. -Products are organized in four categories: +### Build and run applications -| Category | What it covers | Products | -| --- | --- | --- | -| Build | Run code and serve content from Azion's distributed infrastructure: functions, AI models, caching and delivery optimizations, and the infrastructure you run yourself with Orchestrator. | [Functions](/en/documentation/build/functions/), [AI Inference](/en/documentation/build/ai-inference/), [LoRA Fine-Tune](/en/documentation/build/ai-inference/lora-fine-tune/), [Cache](/en/documentation/build/cache/), [Application Accelerator](/en/documentation/build/application-accelerator/), [Image Processor](/en/documentation/build/image-processor/), [Orchestrator](/en/documentation/build/orchestrator/) | -| Store | Keep files, relational data, and key-value pairs next to the functions that read them. | [Object Storage](/en/documentation/store/object-storage/), [SQL Database](/en/documentation/store/sql-database/), [KV Store](/en/documentation/store/kv-store/) | -| Secure | Filter application-layer attacks, bots, and unwanted networks before traffic reaches the application, and resolve and balance that traffic on the way. | [WAF](/en/documentation/secure/waf/), [Bot Manager](/en/documentation/secure/bot-manager/), [Network Shield](/en/documentation/secure/network-shield/), [Origin Shield](/en/documentation/secure/origin-shield/), [Edge DNS](/en/documentation/secure/edge-dns/), [Load Balancer](/en/documentation/platform/load-balancer/) | -| Observe | See what the platform does with every request: raw events, metrics, log streams, and real-user measurements. | [Real-Time Events](/en/documentation/observe/real-time-events/), [Real-Time Metrics](/en/documentation/platform/real-time-metrics/), [Data Stream](/en/documentation/observe/data-stream/), [Edge Pulse](/en/documentation/observe/edge-pulse/) | - -Common use cases: - -- Build and deploy [applications](/en/documentation/platform/applications/) on Azion’s global infrastructure. -- Speed up delivery with [templates and integrations](/en/documentation/marketplace/templates-and-integrations-overview/). -- Adopt [zero trust architectures](/en/documentation/guides/) for apps and content. -- Improve delivery on a [highly distributed network](https://www.azion.com/en/products/our-network/). -- Configure [caching rules](/en/documentation/build/cache/) and advanced optimizations. -- Monitor performance with [real-time metrics](/en/documentation/platform/real-time-metrics/). -- Improve [performance](/en/documentation/architectures/improve-performance-and-reliability/content-delivery/) and reduce bandwidth and operational costs. -- Develop with [supported frameworks and languages](/en/documentation/guides/). -- [Migrate your architecture and content](/en/documentation/fundamentals/migrate-to-azion/). -- Meet regulatory needs with Azion [compliance](https://www.azion.com/en/compliance/). + ---- +### Improve application performance and reliability + + -## Manage Azion -Manage **Azion Web Platform** via UI, APIs, and automation tools: +### Build and run AI workloads -- [Azion Console](/en/documentation/guides/platform/account-and-billing/getting-to-know-azion-console/): configure products, provisioning, billing, and permissions -- [Azion CLI](/en/documentation/devtools/cli/): manage services via terminal (Go-based, open source) -- [Azion API](https://api.azion.com/): REST API over HTTPS for integration and automation -- [Azion Terraform Provider](/en/documentation/devtools/terraform/): manage Azion resources as code + -Tip: For fundamentals on distributed architectures, watch the [Introduction to Platform Foundations](https://www.youtube.com/watch?v=ZBC8h-0l1FQ&list=PL02NW2s3y10N0SQ-2mWL9WN-RWHE8atMp) playlist. +### Secure applications and networks -## FAQ -### What is Azion Web Platform? -Azion Web Platform is a fully managed developer platform to build, secure, and scale modern applications on a distributed global infrastructure, which includes operating and monitoring them. + -### Is Azion a CDN? -Azion includes content delivery and caching capabilities, but it is broader than a CDN: it also provides application execution (including serverless), security, storage, and real-time observability. +### Deliver media and streaming content -### What security features does Azion provide? -Azion provides protections for applications and APIs, including WAF, DDoS mitigation, and bot protection, plus policy-driven controls you can automate via API and IaC. + + +[Templates and integrations](/en/documentation/marketplace/templates-and-integrations-overview/) give many of these a deployable starting point, the [guides](/en/documentation/guides/) cover frameworks and step-by-step tasks, and [Migrate to Azion](/en/documentation/fundamentals/migrate-to-azion/) covers moving an application that already runs elsewhere. + +--- + +## Interfaces + +You manage the Platform yourself, through interfaces that expose the same resources. [Azion Console](/en/documentation/guides/platform/account-and-billing/getting-to-know-azion-console/) configures resources, provisioning, billing, and permissions in the browser. [Azion CLI](/en/documentation/devtools/cli/) manages services from the terminal and is open source, written in Go. The [Azion API](https://api.azion.com/) is a REST API over HTTPS for integration and automation, and the [Azion Terraform Provider](/en/documentation/devtools/terraform/) manages Azion resources as code. + +Some origins accept connections only from known addresses. To allow Azion's data centers through your origin's firewall, refer to [How to retrieve Azion IP ranges for origin server allowlisting](/en/documentation/guides/application-security/bots-and-network/retrieve-azion-ip-ranges/). + +For the fundamentals of distributed architectures, watch the [Introduction to Platform Foundations](https://www.youtube.com/watch?v=ZBC8h-0l1FQ&list=PL02NW2s3y10N0SQ-2mWL9WN-RWHE8atMp) playlist. + +--- -### How do I automate Azion? -You can automate Azion using Azion API, Azion CLI, and the Azion Terraform Provider. +## Related resources -### Where does Azion run? -Azion runs across multiple locations worldwide through a distributed global network to improve performance and reliability for end users. + + + Open the account that holds every resource you create. + Put an application on the request path in a few minutes. + Bring an existing application and its infrastructure to Azion. + + diff --git a/src/content/docs/en/pages/main-menu/get-started/fundamentals.mdx b/src/content/docs/en/pages/main-menu/get-started/fundamentals.mdx index 2fc0a0fc6c..c97c393452 100644 --- a/src/content/docs/en/pages/main-menu/get-started/fundamentals.mdx +++ b/src/content/docs/en/pages/main-menu/get-started/fundamentals.mdx @@ -1,28 +1,59 @@ --- title: Fundamentals description: >- - Create an Azion account, add the people who work in it, keep it secure, and - understand what you are charged for. + Understand how the resources you deploy on Azion connect into one chain that + serves traffic, how your account is organized, and where to start. meta_tags: >- - account, fundamentals, billing, subscriptions, permissions, teams, security, compliance, single sign-on, multi-factor authentication + fundamentals, Azion Platform, platform resources topology, workload, application, firewall, connector, account, teams, permissions, billing, security namespace: documentation_fundamentals permalink: /documentation/fundamentals/ --- +import PlatformTopology from '~/components/webkit/PlatformTopology.vue' import DocCardGroup from '@aziontech/webkit/doc-card-group' import DocCard from '@aziontech/webkit/doc-card' -Everything you build on Azion lives inside an account. This section covers the account itself: how you create one, who else can work in it and with which permissions, how usage becomes an invoice, and the controls that keep the account secure. +A web platform is a service you build on instead of a stack you operate. You write the application and describe how it should behave, and the provider runs it on infrastructure it owns, filters the traffic that reaches it, and shows you what happened to every request. The servers, the routing, and the scaling stop being your work. -Looking for what the platform does instead? Start with [How Azion works](/en/documentation/platform/). +**Azion Platform** is that service on Azion's globally distributed infrastructure: the integrated technology and the interfaces where you build, secure, and scale applications, which includes operating and monitoring them. Use Azion Platform to run an application close to its users, block the traffic it should not receive, store the data it reads, and watch every request it serves. + + +--- + +## Platform resources topology + +Everything that serves traffic on Azion is a set of Platform Resources bound to one another, with what you enable listed inside the resource it attaches to. The diagram shows how they connect: what the workload binds, what each resource holds, where the application fetches from, and what a function can call. Select a card to open it and read what it is and what it holds. + + + +1. A [workload](/en/documentation/platform/workloads/) receives the traffic for its domains. It holds the [domains](/en/documentation/platform/workloads/domains/) and the certificate from [Certificate Manager](/en/documentation/platform/certificate-manager/), and it binds, side by side, a firewall, an application, and a custom page set. +2. A [firewall](/en/documentation/platform/firewall/) inspects each request before the application. You apply a [WAF](/en/documentation/secure/waf/) rule set, [Bot Manager](/en/documentation/secure/bot-manager/), [Network Shield](/en/documentation/secure/network-shield/) lists, and functions to it. [DDoS Protection](/en/documentation/platform/ddos-protection/) is always on, with or without a firewall. +3. An [application](/en/documentation/platform/applications/) serves the content. Its [Rules Engine](/en/documentation/platform/applications/rules-engine/) applies behaviors, [Cache](/en/documentation/build/cache/) answers repeat requests from a stored copy, [Image Processor](/en/documentation/build/image-processor/) resizes images on the way, and [Functions](/en/documentation/build/functions/) run your code in the request path. +4. A [custom page set](/en/documentation/platform/custom-pages/) replaces the default error responses with pages you control. +5. When the cache cannot answer, the application fetches the content through a [connector](/en/documentation/platform/connectors/): from your origin server, or from an Object Storage bucket. [Load Balancer](/en/documentation/platform/load-balancer/) and [Origin Shield](/en/documentation/secure/origin-shield/) are enabled on the connector. +6. Functions call what the Store and AI card holds: [SQL Database](/en/documentation/store/sql-database/), [KV Store](/en/documentation/store/kv-store/), [AI Inference](/en/documentation/build/ai-inference/), and [Object Storage](/en/documentation/store/object-storage/), which a storage connector can also use as the origin. + +To move an application that already runs elsewhere onto this chain, refer to [Migrate to Azion](/en/documentation/fundamentals/migrate-to-azion/). + +## Interfaces + +You create and manage every resource in the chain through the Platform's interfaces. [Azion Console](/en/documentation/guides/platform/account-and-billing/getting-to-know-azion-console/) is the web interface, [Azion CLI](/en/documentation/devtools/cli/) drives the same operations from a terminal, the [Azion API](https://api.azion.com/) exposes them over HTTPS for integrations, and the [Azion Terraform Provider](/en/documentation/devtools/terraform/) declares them as code. Azion's catalog groups what you enable on those resources into four categories: Build, Store, Secure, and Observe. For the request path and the table of what each resource holds, refer to [How Azion works](/en/documentation/fundamentals/how-it-works/). + +--- + +## Your account + +Everything you build on Azion lives inside an [account](/en/documentation/fundamentals/account-settings/). The account holds the resources, the people who work on them, the billing profile, and the security controls that apply to every sign-in. Each person signs in as a user of the account. The account owner creates teams and sets their permissions, and each user belongs to one or more teams that decide which resources they can view or change. A Group account also holds [client accounts](/en/documentation/fundamentals/accounts/), each with its own owner. Usage is metered per account and becomes an invoice on the [Billing](/en/documentation/fundamentals/billing-and-subscriptions/) page. + +If you do not have an account yet, refer to [Create an account](/en/documentation/fundamentals/creating-account/). For the full model, refer to [Accounts, teams, and users](/en/documentation/fundamentals/accounts-teams-and-users/). --- +## Next steps + - - + + + - - - diff --git a/src/content/docs/en/pages/main-menu/get-started/start-with-a-template.mdx b/src/content/docs/en/pages/main-menu/get-started/start-with-a-template.mdx index 812b57bd76..8a0d92fb03 100644 --- a/src/content/docs/en/pages/main-menu/get-started/start-with-a-template.mdx +++ b/src/content/docs/en/pages/main-menu/get-started/start-with-a-template.mdx @@ -21,6 +21,6 @@ You have these ways to start building with a template: -Once you've built your application with the preferred method, you can come back to follow your journey and [Go live with Azion](/en/documentation/products/go-live-with-azion/). +Once you've built your application with the preferred method, you can come back to follow your journey and [Go live with Azion](/en/documentation/fundamentals/). diff --git a/src/content/docs/en/pages/main-menu/manage-accounts/create-accountd.mdx b/src/content/docs/en/pages/main-menu/manage-accounts/create-accountd.mdx index d744f1e5d0..fe1c7bba52 100644 --- a/src/content/docs/en/pages/main-menu/manage-accounts/create-accountd.mdx +++ b/src/content/docs/en/pages/main-menu/manage-accounts/create-accountd.mdx @@ -1,73 +1,102 @@ --- -title: How to create an account on Azion +title: Create an account description: >- - Basic setups to create an account on Azion using an email address and through - Social Login. -meta_tags: 'edge computing, azion, create account, email, social login, sign up' + Sign up for Azion with a work email or a GitHub or Google account, then sign + in to Azion Console for the first time. +meta_tags: 'azion, create account, sign up, work email, social login, github, google' namespace: documentation_creating_account permalink: /documentation/fundamentals/creating-account/ --- -To begin using Azion Web Platform and all the available products, you need to complete the sign-up process and log in to the configuration interface. +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' -You can use two methods to create your Azion account: *email* and *Social Login*. The next sections will provide more information on the sign-up process. +You can create an Azion account from the [sign-up page](https://console.azion.com/signup) with a work email or with [Social Login](/en/documentation/fundamentals/social-login/). Social Login accepts a GitHub or a Google account. The account is where every resource you create lives, and you reach it through [Azion Console](https://console.azion.com/). To add a person to an account that already exists, refer to [Users management](/en/documentation/fundamentals/users-management/). --- -## Creating an account using your email address +## Sign up with a work email -To create an account with your email address, proceed as follows: +To sign up with a work email: -1. On the [sign-up page](https://console.azion.com/signup), click the **Sign Up with Work Email** button; new fields will open. -2. Fill in the following required fields: - - **Work Email** - - **Password** + + -- You automatically agree to the [Customer Agreement Terms of Service](/en/documentation/agreements/customer-agreement/) and [Privacy Policy](/en/documentation/agreements/privacy-policy/) by proceeding with the registration process. + Access the [Azion Console sign-up page](https://console.azion.com/signup). -3. Click the **Sign Up** button. + + -To confirm your account creation, you must verify your email. Check your inbox and look for the verification email. + The **Work Email** and **Password** fields open. -:::note -In the message, you'll find instructions to confirm your email address. Click the URL link to activate your account. This link is only valid for *24 hours*. + + + + In **Work Email**, enter the address for the account. In **Password**, enter the password for it. + + + + + When you select **Sign Up**, you accept the [Terms of Service](/en/documentation/agreements/customer-agreement/) and the [Privacy Policy](/en/documentation/agreements/privacy-policy/). + + + -If you don't receive the email, check your *Spam* folder. +Azion sends a verification email to the address you entered. The link in it is valid for 24 hours. -If you have any questions, [contact the sales team](https://www.azion.com/en/contact/). +:::note +If the email is not in your inbox, check the *Spam* folder. For help with the sign-up, [contact Azion](https://www.azion.com/en/contact/). ::: -By clicking on the link sent by email, the [Azion Console](https://console.azion.com) page will open. To sign in: +To confirm the address and sign in: -1. Enter your email and click **Next**. -2. Enter your password and click the **Sign In** button. -3. Complete the form to personalize your experience, according to your preferences. -4. Click the **Submit** button. + + -You're now able to access **Azion Console** and start building your applications. Check the [build an application](/en/documentation/guides/application-development/getting-started/build-an-application/) page to continue your onboarding journey. + The link activates the account and opens [Azion Console](https://console.azion.com/). ---- + + + + + + -## Creating an account using Social Login +Azion Console opens on its home page, and the account is ready for its first resources. -Azion also allows you to create your account through Social Login. Currently, the platform supports **GitHub** and **Google** accounts. +--- -To create an account using a Social Login, proceed as follows: +## Sign up with a GitHub or Google account -1. From the [sign-up page](https://console.azion.com/signup), click the *Social Login* option of your choice: +With Social Login, the provider has already validated your email, so Azion sends no verification email. To sign up with a GitHub or a Google account: -- **Continue with GitHub** -- **Continue with Google** + + -2. If requested, enter your username and password according to the chosen *Social Login* option. + Access the [Azion Console sign-up page](https://console.azion.com/signup). - - In some cases, you'll need to complete a few more steps, such as proceeding with authorization options. + + + -3. Complete the form to personalize your experience, according to your preferences. -4. Click the **Submit** button. + If the provider asks, enter the username and password of that account and authorize the access. -By choosing to create your account via Social Login, there's no need to verify your email. + + + + -You're now able to access **Console** and start building your applications. Check [build an application](/en/documentation/guides/application-development/getting-started/build-an-application/) page to continue your onboarding journey. +Azion Console opens on its home page, and the account is ready for its first resources. --- + +## Next steps + + + + + + + diff --git a/src/content/docs/en/pages/main-menu/performance/maintenance-mode.mdx b/src/content/docs/en/pages/main-menu/performance/maintenance-mode.mdx new file mode 100644 index 0000000000..ba147d0b05 --- /dev/null +++ b/src/content/docs/en/pages/main-menu/performance/maintenance-mode.mdx @@ -0,0 +1,133 @@ +--- +title: Put an application in maintenance mode +description: >- + Show a maintenance page to every visitor while you change the application, + keep your own access open, and return to normal by removing one rule. +meta_tags: 'azion, maintenance mode, maintenance page, rules engine, redirect, object storage' +namespace: documentation_fundamentals_maintenance_mode +permalink: /documentation/fundamentals/maintenance-mode/ +--- + +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' + +You put an application in maintenance mode with a request-phase rule on its [rules engine](/en/documentation/platform/applications/rules-engine/). The rule answers every visitor with a maintenance page and ends the request before it reaches the origin. Removing the rule returns the application to normal, with no deploy. To change what visitors see when the origin itself returns an error, refer to [Custom Pages](/en/documentation/platform/custom-pages/). + +--- + +## Prerequisites + +- An application on Azion, bound to a workload. +- A maintenance page reachable by URL: a page on another site, or an object in an [Object Storage](/en/documentation/store/object-storage/) bucket served by its own connector. +- Your public IP address, to keep your own access open. + +--- + +## Redirect every visitor to the maintenance page + +To send visitors to a page hosted elsewhere: + + + + + Access [Azion Console](https://console.azion.com/) > **Applications** > **your application** > **Rules Engine** tab. + + + + + + Enter a **Name**, for example `maintenance`, and select **Request Phase**. + + + + + In **Criteria**, set **If `${uri}` starts with `/`**, so the rule matches every request. + + + + + In **Behaviors**, select **Redirect To (302 Found)** and enter the URL of the maintenance page. The 302 tells browsers and search engines that the move is temporary. + + + + + +Every request to the application now answers with a 302 to the maintenance page, and nothing reaches the origin. + +--- + +## Serve the maintenance page from your own domain + +To keep visitors on your domain, serve the page from an Object Storage bucket instead of redirecting. **Rewrite Request** requires [Application Accelerator](/en/documentation/build/application-accelerator/) on the application. + + + + + For the steps, refer to [Upload and download objects](/en/documentation/guides/application-development/data/upload-and-download-objects-from-bucket/). + + + + + In **Connectors**, create a connector of type _Object Storage_ that points at the bucket. + + + + + Access [Azion Console](https://console.azion.com/) > **Applications** > **your application** > **Rules Engine** tab. + + + + + Select **Add Rule**, select **Request Phase**, and set **If `${uri}` starts with `/`** in **Criteria**. + + + + + In **Behaviors**, add **Set Connector** with the storage connector, then **Rewrite Request** with `/maintenance.html`. + + + + + +Every request answers with the maintenance page from the bucket, under your own domain. + +--- + +## Keep your own access open + +To keep working on the application while visitors see the maintenance page, exclude your address from the rule: + + + + + Access [Azion Console](https://console.azion.com/) > **Applications** > **your application** > **Rules Engine** tab, and select the rule. + + + + + In **Criteria**, add **and** `${remote_addr}` **is not equal** your public IP address. + + + + + +Requests from your address reach the application as usual. Every other request still gets the maintenance page. + +--- + +## End the maintenance + +To return the application to normal, delete the maintenance rule. The remaining rules keep working as before. + +--- + +## Next steps + + + + + + + diff --git a/src/content/docs/en/pages/main-menu/performance/minimize-downtime.mdx b/src/content/docs/en/pages/main-menu/performance/minimize-downtime.mdx new file mode 100644 index 0000000000..6ce99ae45a --- /dev/null +++ b/src/content/docs/en/pages/main-menu/performance/minimize-downtime.mdx @@ -0,0 +1,158 @@ +--- +title: Minimize downtime for an application +description: >- + Go live on Azion without a gap in service, and keep the application answering + when an origin fails, with Load Balancer, stale cache, and a custom page. +meta_tags: 'azion, downtime, availability, load balancer, backup origin, stale cache, custom pages, go live' +namespace: documentation_fundamentals_minimize_downtime +permalink: /documentation/fundamentals/minimize-downtime/ +--- + +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' + +Downtime comes from two places: the switch that brings traffic to Azion, and an origin that stops answering later. You avoid the first by finishing the setup before the DNS change. You limit the second with a backup origin, an expired copy from cache, and your own error page. + +--- + +## Prerequisites + +- A workload, an application, and a connector on Azion. To set them up, refer to [Migrate an application to Azion](/en/documentation/fundamentals/migrate-to-azion/). +- Access to the DNS records of the domain at your DNS provider. + +--- + +## Go live without a gap + +Users notice only the DNS change, so everything else comes first: + + + + + In the workload's **Digital Certificate** field, select a certificate that covers the custom domain. Without it, HTTPS fails as soon as the domain resolves to Azion. + + + + + In **Subdomain** and **Domain**, enter the host name users type. + + + + + Load the application from your own computer before any user does. For the steps, refer to [How to stage an application through the hosts file](/en/documentation/guides/application-development/getting-started/stage-applications-through-hosts-file/). + + + + + At your DNS provider, point the CNAME record at the workload domain. For the steps, refer to [How to point a domain to Azion](/en/documentation/guides/platform/migration/point-domain-to-azion/). + + + + +Users reach the application on Azion as their resolvers pick up the change. Until then, the previous provider keeps answering them, so keep it running through the propagation. + +--- + +## Keep answering when an origin fails + +[Load Balancer](/en/documentation/platform/load-balancer/), a feature of the connector, spreads requests across several origin addresses. It skips an address that returns a 4xx or 5xx error or exceeds the connector's timeouts. To add a backup origin: + + + + + Access [Azion Console](https://console.azion.com/) > **Connectors** > **your connector**. + + + + + In **Addresses**, add the address of the backup origin. + + + + + Set its **Server Role** to _Backup_, so it receives requests only when every _Primary_ address fails. + + + + + In **Balancing Method**, select _Round-Robin_ or _Least Connections_. **Server Role** applies to these two methods. + + + + + +When the primary origin fails, requests go to the backup origin instead of returning an error. A connector holds up to 10 addresses with Load Balancer active. + +:::note +To take an origin out for maintenance, turn off the **Active** switch of its address. At least one address must stay active. +::: + +--- + +## Answer from cache while the origin recovers + +A cache setting with **Stale cache** on lets Azion serve an expired copy when the origin fails, instead of an error. The Console turns it on when you create a setting; the API and the CLI leave it off. To check it: + + + + + Access [Azion Console](https://console.azion.com/) > **Applications** > **your application** > **Cache Settings** tab. + + + + + + + +While the origin is down, requests for content Azion has already cached are answered with the last copy. + +--- + +## Show your own page instead of an error + +When the origin fails for content that is not in cache, a custom page set replaces the 5xx response with a page you host. Serve that page from a connector that stays up when the origin fails, such as an [Object Storage](/en/documentation/store/object-storage/) bucket. To create the set: + + + + + Access [Azion Console](https://console.azion.com/) > **Custom Pages**. + + + + + + Select **+ Custom Page Code** and, in **Page Code**, select _503_. + + + + + Select the **Connector** that serves the page and, in **Page Path**, enter its path. For example: `/errors/503.html`. + + + + + In **Response TTL**, enter the seconds the page stays in cache. + + + + + + Access **Workloads** > **your workload**. In **Deployment Settings**, select the custom page set, then select **Save**. + + + + +A 503 from the origin now returns your page. The status code stays 503 unless you set **Response Custom Status Code**. + +--- + +## Next steps + + + + + + + diff --git a/src/content/docs/en/pages/main-menu/performance/test-speed.mdx b/src/content/docs/en/pages/main-menu/performance/test-speed.mdx new file mode 100644 index 0000000000..e3c493511d --- /dev/null +++ b/src/content/docs/en/pages/main-menu/performance/test-speed.mdx @@ -0,0 +1,104 @@ +--- +title: Test the speed of an application +description: >- + Measure how fast an application answers from Azion with real-user data from + Edge Pulse and the request metrics of Real-Time Metrics. +meta_tags: 'azion, speed test, performance, edge pulse, real user monitoring, real-time metrics, latency' +namespace: documentation_fundamentals_test_speed +permalink: /documentation/fundamentals/test-speed/ +--- + +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' + +You can measure the speed of an application on Azion from two sides. [Edge Pulse](/en/documentation/observe/edge-pulse/) collects what real users' browsers see, and [Real-Time Metrics](/en/documentation/platform/real-time-metrics/) charts what Azion served for every request. To compare a page before and after the move to Azion, refer to the last section. + +--- + +## Prerequisites + +- An application served by a workload on Azion. To set them up, refer to [Migrate an application to Azion](/en/documentation/fundamentals/migrate-to-azion/) or [First deploy](/en/documentation/fundamentals/first-deploy/). +- Access to the HTML of the pages you want to monitor, to add the Edge Pulse tag. + +--- + +## Measure what real users see with Edge Pulse + +Edge Pulse is Real User Monitoring. A JavaScript tag in your pages collects navigation, availability, latency, and bandwidth data from real visitors' browsers. Each browser tests three addresses of Azion's infrastructure at a time, once every 30 minutes. The collection does not burden the visitor. To add the tag: + + + + + Access [Azion Console](https://console.azion.com/) > **Edge Pulse**. + + + + + Select **Copy to Clipboard** on the tag you need. The **Default Tag** runs after the page loads. The **Pre-loading Tag** is for pages whose Content Security Policy blocks inline JavaScript. + + + + + Paste it in the HTML of each page, before the closing `body` tag. + + + + + +The browsers of your visitors start sending measurements, and the collected data is available in [Real-Time Events](/en/documentation/observe/real-time-events/). + +:::note +Edge Pulse respects the Do Not Track setting of the browser. With it on, a new identifier is generated on every visit. +::: + +--- + +## Read the request metrics in Real-Time Metrics + +Real-Time Metrics charts every request Azion served, in near real time. For speed, the useful number is how much of the traffic the cache answered without waiting for your origin. To open the charts: + + + + + Access [Azion Console](https://console.azion.com/) > **Real-Time Metrics**. + + + + + + In the **Data Transferred** subtab, compare **Saved Data** with **Missed Data**. The first is what the cache answered. The second is what reached your origin. + + + + + Use the time filters to compare the window before a change with the window after it. + + + + +A larger share of saved data after a change means fewer requests waited for your origin. + +--- + +## Compare a page before and after the move + +Before you point the domain to Azion, your own computer can reach the application through the `hosts` file. Everyone else still reaches the current provider, so you get the same page from both places. To compare: + +1. Load the page from the current provider and note the load time your browser's developer tools report. +2. Stage the application through the `hosts` file. For the steps, refer to [How to stage an application through the hosts file](/en/documentation/guides/application-development/getting-started/stage-applications-through-hosts-file/). +3. Load the same page twice in a private browser window and keep the second time. The first load fills the cache. The second is what visitors get. + +The difference between the two times is what Azion adds for that page. Repeat it with the pages your users open most. + +--- + +## Next steps + + + + + + + diff --git a/src/content/docs/en/pages/main-menu/pricing/pricing.mdx b/src/content/docs/en/pages/main-menu/pricing/pricing.mdx index 0c81158f9f..b9d548173d 100644 --- a/src/content/docs/en/pages/main-menu/pricing/pricing.mdx +++ b/src/content/docs/en/pages/main-menu/pricing/pricing.mdx @@ -25,7 +25,7 @@ The tables on this page list the billing metrics of each product, the usage tier ## On-Demand Pricing -Our On-Demand billing model utilizes monthly tiered pricing. You only pay for what you use during the month, and your unit cost automatically decreases as your operation grows. +Our On-Demand billing model uses monthly tiered pricing. You only pay for what you use during the month, and your unit cost automatically decreases as your operation grows. - + Understand where each setting lives on Azion: your user profile, the account, + the client accounts of a group, and the teams that grant permissions. +meta_tags: >- + account, account owner, users, teams, permissions, client accounts, group account, personal token, activity history, multi-factor authentication +namespace: documentation_fundamentals_accounts_teams_users +permalink: /documentation/fundamentals/accounts-teams-and-users/ +--- + +import FrameBox from '@aziontech/webkit/frame-box' +import ItemList from '@aziontech/webkit/item-list' +import DocItem from '@aziontech/webkit/doc-item' + +Everything you build on Azion lives inside an account, and every person who works on it signs in as a user of that account. What a person can see and change is decided by three things that fit inside one another: their own user profile, the account and its owner, and the teams the owner places them in. A Group account adds one more level, the client accounts of its affiliates, each with its own owner. This page covers the user profile, the account, client accounts, teams and permissions, and the personal tokens that reach the account from outside Azion Console. + +--- + +## User profile + +A user profile holds what belongs to one person: first and last name, the timezone that sets the time displayed on pages such as Activity History, the email used to sign in, a phone number, and the password. The interface language is English and cannot be changed. When you change your email, Azion sends a confirmation to the new address, and the change applies only after you confirm it. From the next sign-in you use the new email, even through Social Login, and the former address becomes free for a new account. + +Multi-Factor Authentication (MFA) has a personal side and an account side. When the account does not enforce MFA and your user has the permission, you can turn it on for your own sign-in. When the account already enforces it, the option is locked for you, because the account owner decided it for everyone. For the fields, refer to [Your settings](/en/documentation/fundamentals/your-settings/). + +## The account + +The account is the container: it owns the resources you deploy, the users and teams that work on them, the billing profile, and the security controls that apply to every sign-in. Its profile carries the account ID, the account name, the company name and its unique identifier, and the billing emails, up to 256 characters separated by semicolons. The address fields are mandatory, because they belong to the billing account, and a change on the page is saved only when all of them are filled. + +One user is the *Account Owner*. Only the owner can change the authentication settings and delete the account. Turning on Social Login lets every user of the account sign in with GitHub or Google. Enforcing MFA makes it mandatory for every user except the owner. The tradeoff is scope: enforcing MFA at the account protects everyone at once, while leaving it to each user protects only those who turn it on. After the owner deletes the account, Azion sends an email confirming the deletion and keeps the account information, and a new account can be created at any time. + +Every action taken in the account by any user is recorded in the Activity History for the last 30 days, with the user who performed it, and older logs are available from the Support team. The same log can be streamed to your own tools through Data Stream. For the fields, refer to [Account settings](/en/documentation/fundamentals/account-settings/) and [Activity history](/en/documentation/fundamentals/activity-history/). + +## Client accounts + +An account of the *Group* type can create separate accounts, called *Clients*, for each affiliate in the group. Each client account has its own Account Owner, its own address and billing emails, and is managed independently under the group. Creating a client needs the Account Owner of the group or the permissions **View client list** and **Change clients**. + +When the client is registered, its owner receives an activation email that stays valid for 14 days. If the account is not activated in that period, the owner is removed from the Platform. An **Active Client** switch on each client turns its operation on or off without deleting it. For the fields, refer to [Accounts](/en/documentation/fundamentals/accounts/). + +## Teams and permissions + +Permissions are granted to teams, never to a user directly. The Account Owner creates the teams and sets what each one can view or change; every other user is a non-owner whose access is the sum of the teams they belong to. Owners have access to every setting and every team without being placed in one. Permissions come in pairs: an **Edit** permission always requires the matching **View** permission, and some pairs require a third, such as **View Bills** for the billing permissions. + +A user in more than one team receives the permissions of all of them, which is the tradeoff of the model: a wider set of teams means fewer blocked pages and more settings within reach. For example, a team with **View Applications** but not **Edit Applications** can audit every application configuration and change none, and a user who opens a page without the required permission receives a *403 Forbidden* error page. Adding users needs the Account Owner or the **View Users** and **Edit Users** permissions, and each new user is created with a profile, a timezone, and the teams they belong to. For the full permission table, refer to [Teams permissions](/en/documentation/fundamentals/teams-permissions/); for adding and removing users, refer to [Users management](/en/documentation/fundamentals/users-management/). + +## Personal tokens + +A personal token is a string of characters that authenticates your user outside Azion Console, in the [Azion API](https://api.azion.com/) and the [Azion CLI](/en/documentation/devtools/cli/). You create it with a name, an optional description, and an expiration of 1, 7, 15, 30, or 90 days, 1 year, or a custom date. The token is shown once, when you create it, and cannot be seen, copied, or modified afterwards; the list shows only its scope, last modified date, and expiration date. Treat it like a password: a long-lived token is convenient for automation and needs the same care as the credential it replaces. For the fields, refer to [Personal tokens](/en/documentation/fundamentals/personal-tokens/). + +--- + +## Related resources + + + + The account profile, address, authentication settings, and deletion. + The fields of your user profile, contact information, and security settings. + Every permission a team can grant and what it unlocks. + Add, edit, and remove the users of the account. + Create client accounts for the affiliates of a Group account. + Set up an authenticator app for your sign-in. + Sign in through your own identity provider. + + diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/activity-history.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/activity-history.mdx index 6bd1f22f40..938fcf8a06 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/activity-history.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/activity-history.mdx @@ -8,9 +8,9 @@ namespace: documentation_accounts_activity_history permalink: /documentation/fundamentals/activity-history/ --- -On Azion, you can access the **Activity History** associated with your account. This feature provides insights into the actions carried out within your account by all connected users. +On Azion, you can access the **Activity History** associated with your account. Activity History records the actions carried out within your account by all connected users. -Once you open the page, you'll see the history from the most recent to the oldest activity of the account. In the *search field*, you can filter the results by activity performed or by a user, for example. +Once you open the page, you will see the history from the most recent to the oldest activity of the account. In the *search field*, you can filter the results by activity performed or by a user, for example. The **Activity History** helps you: diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/billing.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/billing.mdx index 1943a9c638..59b0f55326 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/billing.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/billing.mdx @@ -8,9 +8,9 @@ permalink: /documentation/fundamentals/billing-and-subscriptions/ import DocButton from '~/components/webkit/DocButton.vue'; -The Billing page provides a comprehensive view of your usage-based pricing model. It's where you see your charges based on how much you use Azion products. +The Billing page provides a comprehensive view of your usage-based pricing model. It is where you see your charges based on how much you use Azion products. -When you first sign up to use Azion's Edge Computing platform, you receive an amount in credit. After using the received credit, you have to pay as you go. +When you first sign up to use Azion Platform, you receive an amount in credit. After using the received credit, you have to pay as you go. You can visit the [pricing](https://www.azion.com/en/pricing/) page to check prices for Azion products and services and saving plans. @@ -18,9 +18,9 @@ You can visit the [pricing](https://www.azion.com/en/pricing/) page to check pri ## Start for Free -When you first sign up to use Azion Web Platform, you start for free. You get *$300* in credit to use within *365 days*, which is called a *trial period*. Once the given amount of credit is used or the time period for use expires, you'll be billed according to your usage. +When you first sign up to use Azion Web Platform, you start for free. You get *$300* in credit to use within *365 days*, which is called a *trial period*. Once the given amount of credit is used or the time period for use expires, you will be billed according to your usage. -During the sign up process, you aren't obligated to insert your credit card information. Feel free to make the best use of your credit within the time limit. +During the sign up process, you are not obligated to insert your credit card information. Feel free to make the best use of your credit within the time limit. --- diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/clients.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/clients.mdx index 345e147bb2..326216e641 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/clients.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/clients.mdx @@ -22,7 +22,7 @@ The Clients feature is only available for accounts of the Group type. ## Client accounts -When you click the **Add client** button, three sections are displayed: **Main settings**, **Address information**, and **Account Owner**. +When you select the **Add client** button, three sections are displayed: **Main settings**, **Address information**, and **Account Owner**. Fields marked with an asterisk are required. @@ -30,7 +30,7 @@ Fields marked with an asterisk are required. In this section, you can fill in the affiliate details. -- **Account name**: name of the affiliated company; it's the *Client* type account. +- **Account name**: name of the affiliated company; it is the *Client* type account. - **Company name**: corporate name. @@ -64,4 +64,4 @@ These fields refer to the *Client Owner*. - **Email**: email address of the user who will be the Account owner of that account. The Account owner will use this email as login information. -After confirming the registration, the Account owner receives an automatic email to activate the account, which will be available for *14 days*. If it isn't activated within that period, the Account owner will be automatically removed from Azion's platform. +After confirming the registration, the Account owner receives an automatic email to activate the account, which will be available for *14 days*. If it is not activated within that period, the Account owner will be automatically removed from Azion's platform. diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/multi-factor-authentication.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/multi-factor-authentication.mdx index acb3405b42..797defad3a 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/multi-factor-authentication.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/multi-factor-authentication.mdx @@ -8,7 +8,7 @@ namespace: documentation_accounts_multi_factor permalink: /documentation/fundamentals/multi-factor-authentication/ --- -**Multi-Factor Authentication (MFA)** is an electronic verification method used to secure logins. With MFA, the user must provide at least two pieces of identity evidence to be able to login into their account. In this case, it's a combination of a password and a third-party authenticator application on a mobile device. +**Multi-Factor Authentication (MFA)** is an electronic verification method used to secure logins. With MFA, the user must provide at least two pieces of identity evidence to be able to login into their account. In this case, it is a combination of a password and a third-party authenticator application on a mobile device. Advantages of setting MFA in your account: - Enhance security, making unauthorized access more difficult for malicious actors. @@ -25,7 +25,7 @@ MFA activation is optional but highly recommended for added account security. Us ## Error treatment -- **Incorrect pairing**: errors may occur if the authenticator app isn't correctly paired with the Azion account. +- **Incorrect pairing**: errors may occur if the authenticator app is not correctly paired with the Azion account. - **Time Synchronization**: inaccurate time settings on the mobile device and the authenticator app can lead to authentication failures. diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/personal-tokens.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/personal-tokens.mdx index bb3f41ff08..05cd15bed4 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/personal-tokens.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/personal-tokens.mdx @@ -10,9 +10,9 @@ permalink: /documentation/fundamentals/personal-tokens/ **Personal Tokens** are a string of characters used to authenticate your user and access to certain interfaces and tools. You can create a long-lived authentication personal token in Azion to call [Azion APIs](https://api.azion.com/) or to execute commands in the [command-line interface (CLI)](/en/documentation/devtools/cli/). -While creating a personal token, you'll have to provide: +While creating a personal token, you will have to provide: -- **Personal Token name**: descriptive and easy-to-remember name. +- **Personal Token name**: a descriptive name you will recognize later. - **Expires in**: date of expiration for the token. You can choose the token expiration date between *1*, *7*, *15*, *30*, *90 days*, *1 year*, or a *custom date*. - **Personal Token description** (optional): description to help you remember why the token was created and/or what it was created for. @@ -20,6 +20,6 @@ While creating a personal token, you'll have to provide: The Personal Token's expiration date should be chosen according to your project needs and duration. For use with APIs and CLI, for example, you can create a long-lived authentication token for practicality but you may have to be more careful and take extra security measures. ::: -You can only see your token when you first create it. After confirming, your token *can no longer be seen or copied* and you won't be able to access it again. Treat your tokens like passwords and save them in a safe place right after you create them. +You can only see your token when you first create it. After confirming, your token *can no longer be seen or copied* and you will not be able to access it again. Treat your tokens like passwords and save them in a safe place right after you create them. -You can create as many personal tokens as you like and you can view them under the **Personal Tokens** option in the **Account Menu**, located in the top-right corner of Azion's interface. You can't modify a token once it's created, but you'll be able to see its *scope*, *last modified date*, and *expiration date*. +You can create as many personal tokens as you like and you can view them under the **Personal Tokens** option in the **Account Menu**, located in the top-right corner of Azion's interface. You cannot modify a token once it is created, but you will be able to see its *scope*, *last modified date*, and *expiration date*. diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/social-login.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/social-login.mdx index 7c1ad60899..c440a05dec 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/social-login.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/social-login.mdx @@ -20,7 +20,7 @@ permalink: /documentation/fundamentals/social-login/ In addition, it helps prevent users from providing false data or forgetting their login information. :::note -Currently, Azion supports Social Login with GitHub and Google accounts. +Azion supports Social Login with GitHub and Google accounts. ::: To find out more about signing up to Azion with **Social Login**, visit the [creating an account page](/en/documentation/fundamentals/creating-account/). diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/sso-integration.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/sso-integration.mdx index 4c348ce499..30edd585f6 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/sso-integration.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/sso-integration.mdx @@ -17,7 +17,7 @@ By using SSO, you can: - Reduce password-related issues. - Enhance security, minimizing potential vulnerabilities. - Reduce support requests, since the user manages fewer passwords. -- Enable seamless navigation between apps. +- Navigate between apps without signing in again. --- @@ -48,7 +48,7 @@ Azion, in this context, is the service provider configured as an application in Azion SSO supports X.509 certificate-based authentication as an additional authentication method. When configured, users can authenticate using X.509 digital certificates issued by your organization's Certificate Authority. -The authentication flow works identically for all types of X.509 certificates. Users don't need to perform any special configuration or different actions to use X.509 certificate authentication—the process integrates seamlessly with your existing SSO setup. +The authentication flow works identically for all types of X.509 certificates. Users do not need to perform any special configuration or different actions to use X.509 certificate authentication—the process integrates with your existing SSO setup. To configure an X.509 certificate on Azion, see [How to configure an X.509 certificate](/en/documentation/platform/certificate-manager/for-firewall/#how-to-configure-an-x509-certificate) in the Certificate Manager documentation. diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/teams-permissions.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/teams-permissions.mdx index f99afd702b..994921e6f7 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/teams-permissions.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/teams-permissions.mdx @@ -31,31 +31,31 @@ In this table, you can find what each permission grants access to: | Edit Content Delivery Settings | Grants permission to edit the cache settings list. It also requires the permission **View Content Delivery Settings**. Permission for the products Web Performance, Real Time Purge, Analytics and Analytics Standard. | | Real-Time Purge | Grants permission to add a new purge to Real-Time Purge. | | View Real-Time Analytics | Grants permission to view and generate reports on Real-Time Analytics. *Deprecated product*. | -| View Security Settings | Grants permission to view WAF Rule Sets and Certificate Manager (with the exception of the private key), but doesn't allow creation, removal, or modifications. | +| View Security Settings | Grants permission to view WAF Rule Sets and Certificate Manager (with the exception of the private key), but does not allow creation, removal, or modifications. | | Edit Security Settings | Grants permission to view, create, edit, and remove WAF Rule Sets and Certificate Manager. It also requires the permission **View Security Settings**. | -| View Subscriptions | Grants permission to view the account subscriptions, but doesn't allow modifications. It also requires the permission **View Bills**. +| View Subscriptions | Grants permission to view the account subscriptions, but does not allow modifications. It also requires the permission **View Bills**. | Edit Subscriptions | Grants permission to modify the account subscriptions. It also requires the permissions **View Bills** and **View Subscriptions**. | | View Payment Methods | Grants permission to view the active payment methods and payment history. It also requires the permission **View Bills**. | | Edit Payment Methods | Grants permission to create, edit, and remove payment methods. It also requires the permissions **View Bills** and **View Payment Methods**. | | View Bills | Grants permission to view the **Billing** tab in **Billing & Subscriptions**. Viewing the Payment Methods and Payment History require the **View Payment Methods** permission. | | Edit Multi-Factor Authentication | Grants permission edit the option **Multi-Factor Authentication** on the **Account Settings** page. | -| View Applications | Grants permission to view the configurations, but it doesn't allow modifications, creation, or removal. | +| View Applications | Grants permission to view the configurations, but it does not allow modifications, creation, or removal. | | Edit Applications | Grants permission to edit, create, and remove applications. It also requires the permission **View Applications**. | -| View Domains | Grants permission to view existing domains, but it doesn't allow creation, removal, or modifications. | +| View Domains | Grants permission to view existing domains, but it does not allow creation, removal, or modifications. | | Edit Domains | Grants permission to create, edit, and remove domains. It also requires the permission **View Domains**. | | View Real-Time Events | Grants permission to view and filter by data source. | -| View Users | Grants permission to view the users' account on the Users Management page, but it doesn't allow creation, removal, or modifications. | +| View Users | Grants permission to view the users' account on the Users Management page, but it does not allow creation, removal, or modifications. | | Edit Users | Grants permission to create, edit, and remove users on the account. It also requires the permission **View Users**. | | Wildcard Purge | Grants permission to select the purge type **Wildcard** in **Real Time-Purge**. It also requires the permission **Real Time-Purge**. | -| View Edge DNS | Grants permission to view the zones created on the account. It doesn't allow creation or removal. | +| View Edge DNS | Grants permission to view the zones created on the account. It does not allow creation or removal. | | Edit Edge DNS | Grants permission to create, edit, and remove zones. It also requires the permission **View Edge DNS**. | -| View Data Stream | Grants permission to view the account's streams. It doesn't allow creation, modification, or removal. | +| View Data Stream | Grants permission to view the account's streams. It does not allow creation, modification, or removal. | | Edit Data Stream | Grants permission to create, edit, and remove streams. It also requires the permission **View Data Stream**. | -| View Network Lists | Grants permission to view Network Lists, but doesn't allow creation, removal, or modification. | +| View Network Lists | Grants permission to view Network Lists, but does not allow creation, removal, or modification. | | Edit Network Lists | Grants permission to view, create, edit, and remove Network Lists. It also requires the permission **View Network Lists**. | -| View Firewall | Grants permission to view firewall, but doesn't allow creation, removal, or modification. | +| View Firewall | Grants permission to view firewall, but does not allow creation, removal, or modification. | | Edit Firewall | Grants permission to view, create, edit, and remove firewall. It also requires the permission **View Firewall**. | -| View Functions | Grants permission to view, but it doesn't allow creation, removal, or modifications. | +| View Functions | Grants permission to view, but it does not allow creation, removal, or modifications. | | Edit Functions | Grants permission to create, edit, and remove functions. It also requires the permission **View Functions**. | | View Storage Bucket | Grants permission to view Object Storage buckets using the Azion API. | | Edit Storage Bucket | Grants permission to create and edit Object Storage buckets using the Azion API. | @@ -63,7 +63,7 @@ In this table, you can find what each permission grants access to: | View Storage Object | Grants permission to view the metadata of objects and download objects from Object Storage buckets using the Azion API. | | Edit Storage Object | Grants permission to create and edit objects in Object Storage buckets using the Azion API. | | Delete Storage Object | Grants permission to remove objects in Object Storage buckets using the Azion API. | -| View client list | Grants permission to view clients list. It doesn't allow creation, modifications, or removal of clients. The Clients feature is only available for accounts of the Group type. | +| View client list | Grants permission to view clients list. It does not allow creation, modifications, or removal of clients. The Clients feature is only available for accounts of the Group type. | | Change clients | Grants permission to create, edit or remove Clients. It also requires the permission **View Client list**. | | View SQL Database | Grants permission to view the created databases and their data using the Azion API. | | Edit SQL Database | Grants permission to create and edit databases and their data using the Azion API. | diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/user-session-timeout.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/user-session-timeout.mdx index dce863262f..c9bd376f2f 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/user-session-timeout.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/user-session-timeout.mdx @@ -13,7 +13,7 @@ import Tag from '~/components/webkit/Tag.vue'; The **User Session Timeout** feature allows you to define a **maximum idle time**, ensuring that sessions are automatically terminated after a period of inactivity. It also allows you to define a **maximum session time** to avoid sessions staying open indefinitely. This implementation increases the platform's security, protecting sensitive user data and preventing unauthorized access due to prolonged sessions. -By using this feature, you're able to: +With User Session Timeout, you can: - Configure a maximum idle time and session timeout to attend to compliance and security policies. - Guarantee users' sessions and data are protected. @@ -21,7 +21,7 @@ By using this feature, you're able to: :::note When an organization sets up the User Session Timeout, it applies to all account levels. -This feature is available for customers of all [Azion Support](https://www.azion.com/en/professional-services/) services. +User Session Timeout is available for customers of all [Azion Support](https://www.azion.com/en/professional-services/) services. ::: ## Implementation @@ -44,7 +44,7 @@ A session timeout policy determines the maximum idle time for session terminatio ### Maximum idle time -**Maximum idle time** refers to the period of inactivity after which a session is automatically terminated. It's defined by any API call or interface interaction within a session; if the time since the last access meets or exceeds the configured idle time, the session the session will expire, and the user will be logged out. +**Maximum idle time** refers to the period of inactivity after which a session is automatically terminated. It is defined by any API call or interface interaction within a session; if the time since the last access meets or exceeds the configured idle time, the session the session will expire, and the user will be logged out. If the idle time setting is updated, active sessions will automatically conform to the new policy. For instance, if the idle time is reduced, sessions created before the update must follow the new duration and may be terminated if needed. @@ -54,7 +54,7 @@ By default, the maximum idle time allowed is *1440 minutes*, equivalent to *1* d ### Session time -**Maximum session time** limits the total time a session can remain active, regardless of activity, ensuring sessions don't stay open indefinitely. +**Maximum session time** limits the total time a session can remain active, regardless of activity, ensuring sessions do not stay open indefinitely. If the maximum session time setting is updated, active sessions will automatically conform to the new policy. For instance, if the maximum session time is reduced, sessions created before the update must follow the new duration and may be terminated if needed. diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/users-management.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/users-management.mdx index 8bcef2fa5a..d3acccda04 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/users-management.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/users-management.mdx @@ -8,7 +8,7 @@ namespace: documentation_accounts_users_management permalink: /documentation/fundamentals/users-management/ --- -The **Users Management** functionality on Azion gives you tools to efficiently manage users in your account. This feature enables you to add, modify, and delete users, granting you control over who has access to your Azion account and its associated resources. +**Users Management** on Azion is where you add, modify, and delete users, which gives you control over who has access to your Azion account and its associated resources. To add users to the account, you need to have *Account Owner* privilegies or have the permissions to **View Users** and **Edit Users**. @@ -24,18 +24,18 @@ With **Users Management**, you can: ## User profile -In this section, you're able to fill in the new user's personal information. +In this section, you are able to fill in the new user's personal information. - **First name**: new user first name. - **Last name**: new user last name. - **Timezone**: select the timezone where the new user is located. Choosing the correct timezone guarantees precision when accessing data and metrics on Azion. -- **Language**: English is the only language currently available on Azion. +- **Language**: English is the only language available on Azion. --- ## Contact information -In this section, you're able to provide the new user's contact information. +In this section, you are able to provide the new user's contact information. - **Email**: new user email address. The user will apply the provided email address as a login credential. - **Mobile**: new user mobile number. @@ -44,18 +44,18 @@ In this section, you're able to provide the new user's contact information. ## Security settings -Here, you're able to set security measures to the new user's account. +Here, you are able to set security measures to the new user's account. -- **Account owner**: by enabling this function, the new user will be set as an Account owner. They'll be allowed access to all configurations, including the management of solutions and all accounts. +- **Account owner**: by enabling this function, the new user will be set as an Account owner. They will be allowed access to all configurations, including the management of solutions and all accounts. When this function is disabled, the user will be set as a non-owner, with restricted access according to the permission settings defined in Teams. - **Teams**: teams have different access permissions. Thus, you must select a team to allocate non-owners, unlike account owners, who have permission to access all teams. :::note -Non-owner access permissions depend on the permissions granted to the team they're allocated to. +Non-owner access permissions depend on the permissions granted to the team they are allocated to. ::: You can also allocate non-owners to more than one team, which expands the permission possibilities for the same user. See [Team Permissions](/en/documentation/fundamentals/teams-permissions/) for more details. -- **Multi-Factor Authentication**: this option enables/disables Multi-factor Authentication (MFA). MFA is a verification method that ensures better account security when it's activated. +- **Multi-Factor Authentication**: this option enables/disables Multi-factor Authentication (MFA). MFA is a verification method that ensures better account security when it is activated. diff --git a/src/content/docs/en/pages/main-menu/reference/accounts/your-settings.mdx b/src/content/docs/en/pages/main-menu/reference/accounts/your-settings.mdx index c1e31645dc..ffc4704449 100644 --- a/src/content/docs/en/pages/main-menu/reference/accounts/your-settings.mdx +++ b/src/content/docs/en/pages/main-menu/reference/accounts/your-settings.mdx @@ -8,7 +8,7 @@ permalink: /documentation/fundamentals/your-settings/ On the **Your Settings** page, you can edit and manage your personal information, preferences, and security settings within Azion's platform. -To read about the general information of the account, check the [Account Settings](/en/documentation/fundamentals/your-settings/) page. +To read about the general information of the account, check the [Account Settings](/en/documentation/fundamentals/account-settings/) page. --- @@ -16,10 +16,10 @@ To read about the general information of the account, check the [Account Setting - **First name** (mandatory): the name you want to be identified by. You can edit your name as you wish. - **Last name** (mandatory): the surname you want to be identified by. You can edit your surname as you wish. -- **Timezone** (mandatory): the timezone you want to use on Azion data. You can edit it according to your preferences. It'll change the time displayed on the interface in places such as the **Activity History** page. +- **Timezone** (mandatory): the timezone you want to use on Azion data. You can edit it according to your preferences. It will change the time displayed on the interface in places such as the **Activity History** page. :::note -**Language**: Azion's platform is only available in English. You can't edit this field. +**Language**: Azion's platform is only available in English. You cannot edit this field. ::: --- @@ -29,7 +29,7 @@ To read about the general information of the account, check the [Account Setting - **Email** (mandatory): email used to log in to your Azion account. :::note -When changes are made in this field, a confirmation email is sent to your new address. You need to confirm it to apply the changes. You'll have to use the new email on your next login, even if you log in through Social Login. Your former email address will be available to be used in a new account. +When changes are made in this field, a confirmation email is sent to your new address. You need to confirm it to apply the changes. You will have to use the new email on your next login, even if you log in through Social Login. Your former email address will be available to be used in a new account. ::: - **Phone** (mandatory): phone number you wish to be contacted through. You can edit this field as you wish. @@ -42,5 +42,5 @@ When changes are made in this field, a confirmation email is sent to your new ad - **Multi-Factor Authentication (MFA)**: this is an extra layer of security you can activate in your account. :::note -If the main account doesn't have the MFA enabled and your user has this permission, you can only enable it for use in your login. However, if the MFA is already enabled, you can't edit this option. See more about it on the [Multi-Factor Authentication](/en/documentation/fundamentals/multi-factor-authentication/) page. +If the main account does not have the MFA enabled and your user has this permission, you can only enable it for use in your login. However, if the MFA is already enabled, you cannot edit this option. See more about it on the [Multi-Factor Authentication](/en/documentation/fundamentals/multi-factor-authentication/) page. ::: 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 56ef7fac86..1b1a574f34 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 @@ -16,7 +16,7 @@ Azion is rolling out API v4 in the coming months to improve platform performance API v4 features a new asynchronous, event-driven architecture designed for higher performance and resilience. The new Workload resource model centralizes configuration, making it easier to manage, reuse, and scale your applications. Connectors enables more flexible and secure backend integrations. -Azion API v4 is now available in `Preview` for new developer plan accounts and will be released in waves for `General Availability (GA)` according to your service plan. +Azion API v4 is available in `Preview` for new developer plan accounts and will be released in waves for `General Availability (GA)` according to your service plan. **Key points about the migration**: @@ -86,7 +86,7 @@ With the introduction of Workloads, the **Requests** and **Data Transfer** metri | Data Transfer | Metered per Application | Metered per Workload | :::tip -After migration, you'll see Requests and Data Transfer metrics in your Workload's dashboard and billing reports. The measured values remain the same as before migration. +After migration, you will see Requests and Data Transfer metrics in your Workload's dashboard and billing reports. The measured values remain the same as before migration. ::: ### Connectors and Load Balancer @@ -110,7 +110,7 @@ The Firewall request metering model has been updated: |--------|--------|--------| | Firewall Requests | Only firewalls with Network Shield enabled | All firewalls (all requests passing through) | -- **API v3**: Firewall requests were metered only for firewalls with the Network Shield module enabled. +- **API v3**: Firewall requests were metered only for firewalls with Network Shield enabled. - **API v4**: Firewall meters all requests that pass through it, including: - Requests processed by WAF - Requests processed by Network Shield @@ -122,17 +122,17 @@ This consolidated approach means you may see an increase in Firewall request cou ### Origin Shield -With the introduction of Connectors in API v4, a new billing metric is now available: +With the introduction of Connectors in API v4, a new billing metric applies: | Metric | API v3 | API v4 | |--------|--------|--------| | Shielded Connectors | Not available | Number of Connectors with Origin Shield enabled | - **API v3**: Origin Shield was available as a separate Add-On with a Subscription. No Shielded Connectors were metered. -- **API v4**: Connectors with Origin Shield module enabled are counted as Shielded Connectors and appear in your billing reports. +- **API v4**: Connectors with Origin Shield enabled are counted as Shielded Connectors and appear in your billing reports. :::tip -This is a new metric. If you enable Origin Shield on your Connectors, you'll see Shielded Connectors in your billing reports after migration. +This is a new metric. If you enable Origin Shield on your Connectors, you will see Shielded Connectors in your billing reports after migration. ::: --- @@ -185,7 +185,7 @@ In API v3, **Domains** were a single resource that connected an Application to u | Delete | `DELETE /domains/{domain_id}` | `DELETE /workspace/workloads/{workload_id}` | | Bind to Application | Embedded in Domain creation | `POST /workspace/workloads/{workload_id}/deployments` | -#### Request Payload: Create Domain/Workload +#### Request payload to create a workload **API v3 (Domains):** @@ -224,7 +224,7 @@ In API v3, **Domains** were a single resource that connected an Application to u } ``` -#### Request Payload: Bind to Application (Deployment) +#### Request payload to bind to an application **API v3:** Binding occurs automatically during Domain creation via the `edge_application_id` field. @@ -314,7 +314,7 @@ In API v3, **Origins** were nested resources under Applications. In API v4, **Co | Update | `PATCH /edge_applications/{app_id}/origins/{origin_key}` | `PATCH /edge_connector/connectors/{connector_id}` | | Delete | `DELETE /edge_applications/{app_id}/origins/{origin_key}` | `DELETE /edge_connector/connectors/{connector_id}` | -#### Request Payload: Create Origin/Connector +#### Request payload to create a connector **API v3 (Origins - Single Origin):** @@ -468,16 +468,16 @@ In API v3, **Origins** were nested resources under Applications. In API v4, **Co |--------|--------|--------| | Resource scope | Nested under Application | Independent top-level resource | | Reusability | One Origin per Application | One Connector can serve multiple Applications | -| Type distinction | `origin_type: "single_origin"` or `"load_balancer"` | `type: "http"` with `load_balancer` module enabled for multiple addresses | +| Type distinction | `origin_type: "single_origin"` or `"load_balancer"` | `type: "http"` with `load_balancer` enabled for multiple addresses | | Protocol policy | `origin_protocol_policy` | `connection_options.transport_policy` | | Host header | `host_header` | `connection_options.host` | | Path | `origin_path` | `connection_options.path_prefix` | | Timeouts | `connection_timeout`, `timeout_between_bytes` | `modules.load_balancer.config.connection_timeout`, `read_write_timeout` | -| HMAC Auth | Direct fields on Origin | Requires `origin_shield` module | +| HMAC Auth | Direct fields on Origin | Requires `origin_shield` enabled | | Ports | Not configurable | `http_port`, `https_port` per address | | Identifier | `origin_key` used for updates | `id` used for all operations | -#### Activating a Connector/Origin in an Application +#### Activate a connector in an application **API v3 - Rules Engine:** @@ -873,15 +873,15 @@ When using the Console, this association is created automatically when you selec For more information about the API parameters visit the [Workloads API reference](https://api.azion.com/v4#/operations/GetWorkspaceWorkloads). ::: -### What happens to my existing Domains? +### Existing Domains Domains will be automatically converted to Workloads in phases, ensuring compatibility with the original configurations. The migration will occur in waves. -After your account is migrated you'll not be able to create new Domains. +After your account is migrated you will not be able to create new Domains. ### Required action -If you have an automation that currently uses the **Domains** API endpoints you must update it to use v4 **Workloads** endpoints. +If you have an automation that uses the **Domains** API endpoints you must update it to use v4 **Workloads** endpoints. ### New Features @@ -924,11 +924,11 @@ All settings previously managed in Applications **Origins** tab are now organize - **Connector Type** - *Previous behavior*: Options included `Single Origin` and `Load Balancer`. This defined whether you could configure one or multiple origins. - - *New behavior*: `Single Origin` and `Load Balancer` types have been unified into the `HTTP` type. When using multiple origins, you must enable the **Load Balancer Module** to add more origins. + - *New behavior*: `Single Origin` and `Load Balancer` types have been unified into the `HTTP` type. When using multiple origins, you must enable **Load Balancer** to add more origins. - **HMAC Authentication** - *Previous behavior*: Availiable when configuring an Origin. - - *New behavior*: Now you must enable the **Origin Shield Module** when configuring an `HTTP` type connector. + - *New behavior*: You must enable **Origin Shield** when configuring an `HTTP` type connector. - **Timeouts** - *Previous behavior*: `Connection Timeout` and `Between Bytes Timeout` had fixed values. @@ -1006,13 +1006,13 @@ You can manage **Connectorss** and their configuration through the API using the For more information about the API parameters visit the [Connectors API reference](https://api.azion.com/v4#/operations/GetEdgeConnectorConnectors). ::: -### What happens to my existing Origins? +### Existing Origins Existing Origins will be migrated according to a schedule, which will be communicated for each case. The migration will occur in phases. ### Required action -If you have an automation that currently uses the **Applications - Origins** API endpoints you must update it to use v4 endpoints. +If you have an automation that uses the **Applications - Origins** API endpoints you must update it to use v4 endpoints. ### New Features @@ -1022,7 +1022,7 @@ If you have an automation that currently uses the **Applications - Origins** API ### Migration Benefits - **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. +- **Future-Ready Architecture**: **Connectors** provides the foundation for upcoming Azion Web Platform features and optimizations, ensuring your Applications are ready to use new capabilities as they become available. @@ -1119,7 +1119,7 @@ To use a **Custom Page**, you must link it to a **Workload** using the **Workloa For more information about the API parameters visit the [Custom Pages API reference](https://api.azion.com/v4#/operations/GetWorkspaceCustomPages). ::: -### What happens to my existing Error Responses? +### Existing Error Responses Existing Error Responses will be automatically converted to **Custom Pages** in phases, maintaining compatibility with the original configurations. The migration will occur in waves. @@ -1161,14 +1161,14 @@ Here are recommended actions to ensure a smooth migration: --- ## Q&A -### How can I test the new features? +### Test the new features New Developer accounts will have access to the updated features. To evaluate these features, you can create a personal account that is not associated with your organization's account. This allows you to test the new functionality independently. -### Do I have to do something? +### Required actions Most users will not need to take any action, as the migration process is automatic and preserves existing configurations. However, if you use custom automation, scripts, or CI/CD pipelines that interact with the previous API endpoints, you must update them to use the new v4 endpoints. Review your integrations to ensure compatibility after migration. -## What should I do if I need assistance? +## Assistance You can contact our [support team](/en/documentation/support/) or ask [Azion Copilot](https://console.azion.com/copilot). 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 c307d1e7a5..36cf41fd44 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 @@ -90,7 +90,7 @@ A rule set that no rule names never runs, however carefully its families are set - **What a blocked request receives**: `400` and Azion's default error page. Nothing in that response names WAF, the rule that matched, or the score, so a block is identified by the `x-azion-request-id` header on it and looked up afterwards. - **Exceptions**: an exception exempts one part of a request from one internal rule, or from all of them, without lowering the sensitivity for the rest of the traffic. Azion Console calls the object an allowed rule. For every field and all fifteen match zones, refer to [WAF Exceptions](/en/documentation/secure/waf/custom-allowed-rules/#fields). - **Interfaces**: you create and manage rule sets and exceptions in **Azion Console**, which lists rule sets under **WAF Rules**, with [Azion CLI](/en/documentation/devtools/cli/), and through the Azion API under `https://api.azion.com/v4/workspace/wafs`. For the API and CLI surfaces, refer to [WAF Rule Sets](/en/documentation/secure/waf/rules-set/#api) and [WAF Exceptions](/en/documentation/secure/waf/custom-allowed-rules/#api). -- **Observability**: a match leaves nothing in the response, so every question about one is answered from a reporting surface. [Real-Time Metrics](/en/documentation/platform/real-time-metrics/#waf) reports requests processed and requests blocked over time, [Real-Time Events](/en/documentation/observe/real-time-events/) returns one row per request with the rules that matched and the score each family reached, and [Data Stream](/en/documentation/observe/data-stream/) ships those events to a system outside Azion. The same event data is queried through the [GraphQL API Overview](/en/documentation/devtools/graphql/overview/), and [How to integrate WAF with SIEMs](/en/documentation/products/secure/automate/integrate-siems/) covers sending it to a SIEM. +- **Observability**: a match leaves nothing in the response, so every question about one is answered from a reporting surface. [Real-Time Metrics](/en/documentation/platform/real-time-metrics/#waf) reports requests processed and requests blocked over time, [Real-Time Events](/en/documentation/observe/real-time-events/) returns one row per request with the rules that matched and the score each family reached, and [Data Stream](/en/documentation/observe/data-stream/) ships those events to a system outside Azion. The same event data is queried through the [GraphQL API Overview](/en/documentation/devtools/graphql/overview/), and [How to integrate WAF with SIEMs](/en/documentation/guides/) covers sending it to a SIEM. - **Bounds**: WAF parses a request body in five content types, and a request whose body passes 131,072 bytes, which is 128 KiB, is refused rather than inspected. A rule set carries one `thresholds` entry per threat family, and a Tuning query reaches back a fixed window. For every bound, the response past it, and the usage each service plan includes, refer to [WAF limits](/en/documentation/secure/waf/limits/). - **Billing**: WAF is billed on Requests, Rule Sets, and Exceptions. For the rate past the amount a plan includes, refer to [Pricing](/en/documentation/fundamentals/pricing/#web-application-firewall). diff --git a/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx b/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx index 1d0d15163f..a23204c4c4 100644 --- a/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx +++ b/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx @@ -1,16 +1,16 @@ --- -title: Azion HTTP Error Status Codes -description: These are the most common web and server errors and how to solve them. +title: HTTP status codes +description: The HTTP status codes Azion returns when a request fails, what causes each one, and how to solve it. meta_tags: 'services, support, documentation, system error' namespace: documentation_error_status_codes -permalink: /documentation/support/http-error-status-codes/ +permalink: /documentation/fundamentals/http-status-codes/ --- When accessing applications hosted on the Azion Web Platform, you may encounter common HTTP errors. These errors can be related to a bad request or missing content, authentication issues, or servers malfunctioning. -If you're the application owner and need to investigate why a specific error was returned to your users, see [Basic troubleshooting on Azion Web Platform](/en/documentation/guides/application-development/getting-started/basic-troubleshooting/). +If you are the application owner and need to investigate why a specific error was returned to your users, see [Basic troubleshooting on Azion Web Platform](/en/documentation/guides/application-development/getting-started/basic-troubleshooting/). -To inform you of these errors, you'll receive a message similar to this: +To inform you of these errors, you will receive a message similar to this: ![Example - HTTP Error Status Codes](/assets/docs/images/uploads/http-error-status-codes.png?v=2) @@ -18,7 +18,7 @@ To inform you of these errors, you'll receive a message similar to this: - The **Error Details** section provides you the information related to the error, including: - **Timestamp**: the date and time when the error occurred and the response was returned to the user. - **URL**: the page (URL) accessed by the user that generated the Error Status Code. - - **Your IP**: the public IP of the client that connected to the edge. + - **Your IP**: the public IP of the client that connected to Azion. - **Request ID**: a unique identifier for your request. It can be used for further investigation or support. - **Status Code**: the HTTP status code that indicates the specific type of error encountered, related to the page's title. - **Edge Location**: the Azion data center location that processed your request, identified by the official location code published on the [Azion Status Page](https://status.azion.com). This value is returned via the `X-Azion-Edge-Location` response header and is always present, regardless of debug mode. @@ -27,17 +27,17 @@ To inform you of these errors, you'll receive a message similar to this: The `X-Azion-Edge-Pop` header, which previously appeared in all responses, now returns only when the `Pragma: azion-debug-cache` header is included in the request. Use it for advanced debugging alongside other cache-related headers. ::: -When Azion's system returns an error page, it could be related to configurations, authorization mechanisms, or a failing connection with the third-party web services you're using. For example, when your bank or e-commerce application is hosted on Azion. To check Azion Web Platform health status, access [Azion status page](https://status.azion.com "Status page"). +When Azion's system returns an error page, it could be related to configurations, authorization mechanisms, or a failing connection with the third-party web services you are using. For example, when your bank or e-commerce application is hosted on Azion. To check Azion Web Platform health status, access [Azion status page](https://status.azion.com "Status page"). --- -## What do Azion system errors mean? +## Azion system errors These are the most common web and server errors and how to solve them. ### 400 Bad Request -This error indicates that the server can't or won't process the request due to a client error. Some common cases are malformed syntax, invalid request message framing, or misleading request routing. Summarizing, the server couldn't understand the request due to incorrect formatting or invalid data provided. +This error indicates that the server cannot or will not process the request due to a client error. Some common cases are malformed syntax, invalid request message framing, or misleading request routing. Summarizing, the server could not understand the request due to incorrect formatting or invalid data provided. Some common examples: @@ -59,7 +59,7 @@ Content-Length: 9 12345678901234 ``` -- Two spaces between the URL and the protocol specification. In the following example, there's an extra space between `sample` and `page`. +- Two spaces between the URL and the protocol specification. In the following example, there is an extra space between `sample` and `page`. ``` GET /sample page HTTP/1.1 @@ -74,21 +74,21 @@ Host: example.com ### 403 Forbidden -This error typically happens when access is restricted to authenticated users or when you don't have the required permissions to access the requested resource. In this case, the server understands the request but refuses to authorize it. +This error typically happens when access is restricted to authenticated users or when you do not have the required permissions to access the requested resource. In this case, the server understands the request but refuses to authorize it. #### How to solve it Some ways to troubleshoot this error: -- Check if the URL you're trying to access is correct and doesn't contain typing errors. -- Verify if the page or application requires authentication and if you're logged in with the correct credentials. +- Check if the URL you are trying to access is correct and does not contain typing errors. +- Verify if the page or application requires authentication and if you are logged in with the correct credentials. - Clear your browser cookies and cached data. - Disable any browser extensions that could block or interfere with your request. - As the access is restricted, contact the site owner for assistance. ### 404 Not Found -This error indicates that the server couldn't find the content or resource you're looking for. This usually happens because: +This error indicates that the server could not find the content or resource you are looking for. This usually happens because: ​​- The URL is typed incorrectly. - The resource has been moved or deleted. @@ -98,22 +98,22 @@ This error indicates that the server couldn't find the content or resource you'r Some ways to troubleshoot this error: -- Check if the URL you're trying to access is correct and doesn't contain typing errors. +- Check if the URL you are trying to access is correct and does not contain typing errors. - Refresh the page to see if it resolves the issue. -- Ensure that the link is current and hasn't been altered. -- If you're looking for specific content, try searching for it using the website's search function or a search engine. This can help you find the resource if it has been relocated. +- Ensure that the link is current and has not been altered. +- If you are looking for specific content, try searching for it using the website's search function or a search engine. This can help you find the resource if it has been relocated. - Clear your browser cookies and cached data. - If the issue persists, contact the site owner. ### 406 Not Acceptable -In this case, the server can't generate the response as requested by the user. Generally, it's related to the content types or languages specified in the `Accept` headers. For example: the user requests a specific type of content (like JSON or XML) or language, but the server can't provide that type or language. +In this case, the server cannot generate the response as requested by the user. Generally, it is related to the content types or languages specified in the `Accept` headers. For example: the user requests a specific type of content (like JSON or XML) or language, but the server cannot provide that type or language. #### How to solve it Some ways to troubleshoot this error: -- Check the URL you're accessing and any parameters you might be passing along with the request. +- Check the URL you are accessing and any parameters you might be passing along with the request. - Use a different browser or device. Browser-specific issues or device configurations can lead to unexpected errors. - Wait and retry. Occasionally, the server might be temporarily unable to fulfill requests due to maintenance or other issues. - Clear your browser cookies and cached data. @@ -121,14 +121,14 @@ Some ways to troubleshoot this error: ### 410 Gone -This error states that the requested resource existed previously but has been deliberately removed, with no forwarding address, and won't be available again. For example: if you're looking for a section on an e-commerce and get a 410 error, it means the page has been shut down for good and it won't be available again. +This error states that the requested resource existed previously but has been deliberately removed, with no forwarding address, and will not be available again. For example: if you are looking for a section on an e-commerce and get a 410 error, it means the page has been shut down for good and it will not be available again. #### How to solve it Some ways to troubleshoot this error: -- Check if the URL you're trying to access is correct and doesn't contain any typos. -- If you're looking for specific content, try searching for it using the website's search function or a search engine. This can help you find the resource if it has been relocated. +- Check if the URL you are trying to access is correct and does not contain any typos. +- If you are looking for specific content, try searching for it using the website's search function or a search engine. This can help you find the resource if it has been relocated. - Frequently, there is no immediate resolution available because the resource is no longer accessible. - If the issue persists, contact the site owner for further information. @@ -142,7 +142,7 @@ The simplest solution is to wait a few minutes and then retry your request. This ### 500 Internal Server Error -This error means that something has gone wrong on the server's end while trying to process your request but it can't specify what the exact problem is or it doesn't know how to handle it. It could also be unexpected handling by the application on the origin (backend). +This error means that something has gone wrong on the server's end while trying to process your request but it cannot specify what the exact problem is or it does not know how to handle it. It could also be unexpected handling by the application on the origin (backend). This status code is a generic error message that often indicates issues with server configurations, code errors, or unexpected conditions that prevent the server from fulfilling the request properly. @@ -154,28 +154,28 @@ A 500 Internal Server Error usually requires action on the server's end to be fi If your application is configured to redirect HTTP requests to HTTPS via **Rules Engine**, but the origin is also redirecting HTTPS back to HTTP, this creates a redirect loop that results in a 500 error. To resolve this, apply one or both of the following fixes: -**To enforce HTTP between the edge and your origin:** +**To enforce HTTP between Azion and your origin:** 1. Access [Azion Console](https://console.azion.com) > **Applications**. 2. Select your application. -3. Navigate to the **Origins** tab. +3. Go to the **Origins** tab. 4. Select the origin you want to configure. 5. Under **Protocol Policy**, select **Enforce HTTP**. -6. Click **Save**. +6. Select **Save**. **To remove the Redirect HTTP to HTTPS behavior from Rules Engine:** 1. Access [Azion Console](https://console.azion.com) > **Applications**. 2. Select your application. -3. Navigate to the **Rules Engine** tab. -4. Locate the rule that contains the **Redirect HTTP to HTTPS** behavior and click it to edit. +3. Go to the **Rules Engine** tab. +4. Locate the rule that contains the **Redirect HTTP to HTTPS** behavior and select it to edit. 5. In the **Behaviors** section, remove the **Redirect HTTP to HTTPS** behavior. -6. Click **Save**. +6. Select **Save**. If the issue persists, contact the site owner to confirm that the system is stable or lacking exception handling. :::note -If you're the site owner and migrating to Azion, a protocol mismatch between your origin and the Rules Engine can cause 500 errors. Check the **Protocol Policy** settings in [Connectors](/documentation/platform/connectors/) to ensure the protocol used to connect to your origin matches your application's requirements. +If you are the site owner and migrating to Azion, a protocol mismatch between your origin and the Rules Engine can cause 500 errors. Check the **Protocol Policy** settings in [Connectors](/en/documentation/platform/connectors/) to ensure the protocol used to connect to your origin matches your application's requirements. ::: ### 502 Bad Gateway diff --git a/src/content/docs/en/pages/shared-responsibility/shared-responsibility.mdx b/src/content/docs/en/pages/shared-responsibility/shared-responsibility.mdx index 6f1738522e..147cde3a0d 100644 --- a/src/content/docs/en/pages/shared-responsibility/shared-responsibility.mdx +++ b/src/content/docs/en/pages/shared-responsibility/shared-responsibility.mdx @@ -48,7 +48,7 @@ This shared model can help relieve the customer’s operational burden as Azion ### Azion's Responsibilities -“Security of the Edge Platform” - Azion develops, operates, protects, and controls the infrastructure that runs its Products and Services when offered as-a-service, and is responsible for the following aspects of its security: +“Security of the Platform” - Azion develops, operates, protects, and controls the infrastructure that runs its Products and Services when offered as-a-service, and is responsible for the following aspects of its security: - Physical security. - Secure software development. @@ -67,9 +67,9 @@ Customers can use Azion compliance documents to perform any required Azion contr ### Customer's Responsibilities -“Security in the Edge Platform” – Customer responsibility will be determined by the Azion Product and Service that a customer selects. This determines the amount of configuration work the customer must perform as part of their security responsibilities. +“Security in the Platform” – Customer responsibility will be determined by the Azion Product and Service that a customer selects. This determines the amount of configuration work the customer must perform as part of their security responsibilities. -For abstracted Products and Services on a as-a-service or serverless model, which uses Azion Global Network, Azion develops, operates, protects, and controls the infrastructure, while customers access the Products and Service interfaces to store, manage, and retrieve data. Customers are responsible for items such as: +For abstracted Products and Services on a as-a-service or serverless model, which use Azion's distributed infrastructure, Azion develops, operates, protects, and controls the infrastructure, while customers access the Products and Service interfaces to store, manage, and retrieve data. Customers are responsible for items such as: - Correct configuration of Azion Products and Services. - Configuration change control. @@ -92,8 +92,8 @@ Customers that deploy Products and Services on their own premises, remote device Shared Controls – Azion and customer work collaboratively to enhance the overall security and compliance of resources, which apply to both Azion and customers, but in completely separate contexts or perspectives: -- Log Management – While Azion requires you to have its Real-Time Events product to provide access to short-term logs for debugging purposes, it's the customer's responsibility to set up log drains with Azion Data Stream for long-term log retention, data auditing, or additional visibility into their application's performance and security. +- Log Management – While Azion requires you to have its Real-Time Events product to provide access to short-term logs for debugging purposes, it is the customer's responsibility to set up log drains with Azion Data Stream for long-term log retention, data auditing, or additional visibility into their application's performance and security. - Patch Management – Azion is responsible for patching and fixing flaws within its Edge Platform, but customers are responsible for patching their own code and applications. -- Authentication – Customers must guarantee their authentication information — password, tokens, credentials, etc. — meets general security criteria and are kept safe. Azion must guarantee the platform's security and protection regarding authentication. +- Authentication – Customers must guarantee their authentication information — such as passwords, tokens, and credentials — meets general security criteria and are kept safe. Azion must guarantee the platform's security and protection regarding authentication. -Note that this Shared Responsibility Model is a generalized framework, and the specific responsibilities and offerings may vary based on the exact services and solutions you contracted. It's advisable to consult directly with Azion's team for more specific details, when needed. Also, Azion provides responsibility matrices to help customers comply with PCI DSS and other specific regulations while using Azion Products and Services. Please refer to our [Support Team](/en/documentation/support/#service-channels) in oder to access such information. +This Shared Responsibility Model is a generalized framework, and the specific responsibilities and offerings may vary based on the exact services and solutions you contracted. It is advisable to consult directly with Azion's team for more specific details, when needed. Also, Azion provides responsibility matrices to help customers comply with PCI DSS and other specific regulations while using Azion Products and Services. refer to our [Support Team](/en/documentation/support/#service-channels) in oder to access such information. diff --git a/src/content/docs/pt-br/pages/agent-setup/claude-code.mdx b/src/content/docs/pt-br/pages/agent-setup/claude-code.mdx index 879b880693..fc0e24326b 100644 --- a/src/content/docs/pt-br/pages/agent-setup/claude-code.mdx +++ b/src/content/docs/pt-br/pages/agent-setup/claude-code.mdx @@ -213,13 +213,13 @@ Cada um destes exercita uma parte diferente da conexão — a busca na documenta "headline": "Connectors", "tip": "De onde uma aplicação busca conteúdo — um bucket, um servidor de origem, uma transmissão ao vivo. Chamados Origins antes da v4, por isso um modelo treinado antes ainda pede por um.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" }, "workload": { "headline": "Workloads", "tip": "O ponto de entrada público que liga um domínio e seu TLS a uma aplicação. Chamados Domains antes da v4.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" } }} items={[ diff --git a/src/content/docs/pt-br/pages/agent-setup/codex.mdx b/src/content/docs/pt-br/pages/agent-setup/codex.mdx index 7aa8bd66ed..4a8022fb44 100644 --- a/src/content/docs/pt-br/pages/agent-setup/codex.mdx +++ b/src/content/docs/pt-br/pages/agent-setup/codex.mdx @@ -208,13 +208,13 @@ Cada um destes exercita uma parte diferente da conexão — a busca na documenta "headline": "Connectors", "tip": "De onde uma aplicação busca conteúdo — um bucket, um servidor de origem, uma transmissão ao vivo. Chamados Origins antes da v4, por isso um modelo treinado antes ainda pede por um.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" }, "workload": { "headline": "Workloads", "tip": "O ponto de entrada público que liga um domínio e seu TLS a uma aplicação. Chamados Domains antes da v4.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" } }} items={[ diff --git a/src/content/docs/pt-br/pages/agent-setup/cursor.mdx b/src/content/docs/pt-br/pages/agent-setup/cursor.mdx index cd0c162115..49caa698cf 100644 --- a/src/content/docs/pt-br/pages/agent-setup/cursor.mdx +++ b/src/content/docs/pt-br/pages/agent-setup/cursor.mdx @@ -205,13 +205,13 @@ Cada um destes exercita uma parte diferente da conexão — a busca na documenta "headline": "Connectors", "tip": "De onde uma aplicação busca conteúdo — um bucket, um servidor de origem, uma transmissão ao vivo. Chamados Origins antes da v4, por isso um modelo treinado antes ainda pede por um.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" }, "workload": { "headline": "Workloads", "tip": "O ponto de entrada público que liga um domínio e seu TLS a uma aplicação. Chamados Domains antes da v4.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" } }} items={[ diff --git a/src/content/docs/pt-br/pages/agent-setup/gemini-cli.mdx b/src/content/docs/pt-br/pages/agent-setup/gemini-cli.mdx index 839673c79f..5440fc7a1f 100644 --- a/src/content/docs/pt-br/pages/agent-setup/gemini-cli.mdx +++ b/src/content/docs/pt-br/pages/agent-setup/gemini-cli.mdx @@ -215,13 +215,13 @@ Cada um destes exercita uma parte diferente da conexão — a busca na documenta "headline": "Connectors", "tip": "De onde uma aplicação busca conteúdo — um bucket, um servidor de origem, uma transmissão ao vivo. Chamados Origins antes da v4, por isso um modelo treinado antes ainda pede por um.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" }, "workload": { "headline": "Workloads", "tip": "O ponto de entrada público que liga um domínio e seu TLS a uma aplicação. Chamados Domains antes da v4.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" } }} items={[ diff --git a/src/content/docs/pt-br/pages/agent-setup/github-copilot.mdx b/src/content/docs/pt-br/pages/agent-setup/github-copilot.mdx index 4b3caffe31..ec474286ce 100644 --- a/src/content/docs/pt-br/pages/agent-setup/github-copilot.mdx +++ b/src/content/docs/pt-br/pages/agent-setup/github-copilot.mdx @@ -206,13 +206,13 @@ Cada um destes exercita uma parte diferente da conexão — a busca na documenta "headline": "Connectors", "tip": "De onde uma aplicação busca conteúdo — um bucket, um servidor de origem, uma transmissão ao vivo. Chamados Origins antes da v4, por isso um modelo treinado antes ainda pede por um.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" }, "workload": { "headline": "Workloads", "tip": "O ponto de entrada público que liga um domínio e seu TLS a uma aplicação. Chamados Domains antes da v4.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" } }} items={[ diff --git a/src/content/docs/pt-br/pages/agent-setup/opencode.mdx b/src/content/docs/pt-br/pages/agent-setup/opencode.mdx index 6eeb48a928..677f177553 100644 --- a/src/content/docs/pt-br/pages/agent-setup/opencode.mdx +++ b/src/content/docs/pt-br/pages/agent-setup/opencode.mdx @@ -216,13 +216,13 @@ Cada um destes exercita uma parte diferente da conexão — a busca na documenta "headline": "Connectors", "tip": "De onde uma aplicação busca conteúdo — um bucket, um servidor de origem, uma transmissão ao vivo. Chamados Origins antes da v4, por isso um modelo treinado antes ainda pede por um.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" }, "workload": { "headline": "Workloads", "tip": "O ponto de entrada público que liga um domínio e seu TLS a uma aplicação. Chamados Domains antes da v4.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" } }} items={[ diff --git a/src/content/docs/pt-br/pages/agent-setup/windsurf.mdx b/src/content/docs/pt-br/pages/agent-setup/windsurf.mdx index 5f1a0643a0..933309768e 100644 --- a/src/content/docs/pt-br/pages/agent-setup/windsurf.mdx +++ b/src/content/docs/pt-br/pages/agent-setup/windsurf.mdx @@ -205,13 +205,13 @@ Cada um destes exercita uma parte diferente da conexão — a busca na documenta "headline": "Connectors", "tip": "De onde uma aplicação busca conteúdo — um bucket, um servidor de origem, uma transmissão ao vivo. Chamados Origins antes da v4, por isso um modelo treinado antes ainda pede por um.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" }, "workload": { "headline": "Workloads", "tip": "O ponto de entrada público que liga um domínio e seu TLS a uma aplicação. Chamados Domains antes da v4.", "cta": "Visão geral da plataforma", - "href": "/pt-br/documentacao/plataforma/" + "href": "/pt-br/documentacao/fundamentos/como-funciona/" } }} items={[ diff --git a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/visao-geral/visao-geral-runtime.mdx b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/visao-geral/visao-geral-runtime.mdx index d0f3b90447..11a96ac789 100644 --- a/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/visao-geral/visao-geral-runtime.mdx +++ b/src/content/docs/pt-br/pages/devtools/azion-edge-runtime/visao-geral/visao-geral-runtime.mdx @@ -55,7 +55,7 @@ Saiba mais sobre o [Strict mode](https://developer.mozilla.org/en-US/docs/Web/Ja Todos os tetos dentro dos quais uma invocação roda, e o que acontece além de cada um. O campo `active`, que impede uma instância de rodar sem apagá-la. O que uma aplicação habilita antes de uma função poder rodar nela. - Onde o código é executado fisicamente. + Onde o código é executado fisicamente. Os canais de suporte e de comunidade. diff --git a/src/content/docs/pt-br/pages/guias/troubleshooting/basic-troubleshooting.mdx b/src/content/docs/pt-br/pages/guias/troubleshooting/basic-troubleshooting.mdx index f1b30a7a8c..fdc45ff3cb 100644 --- a/src/content/docs/pt-br/pages/guias/troubleshooting/basic-troubleshooting.mdx +++ b/src/content/docs/pt-br/pages/guias/troubleshooting/basic-troubleshooting.mdx @@ -64,7 +64,7 @@ Como você pode descobrir exatamente por que essa requisição foi bloqueada? Para os passos abaixo, copie o **Request ID** exibido na página. :::tip -O **Request ID** é o mesmo identificador exibido na página de erro da Azion, na seção **Error Details**. Para uma descrição de todos os campos dessa página e o significado de cada código de status HTTP, consulte [Códigos de Status de Erro HTTP](/pt-br/documentacao/suporte/http-error-status-codes/). +O **Request ID** é o mesmo identificador exibido na página de erro da Azion, na seção **Error Details**. Para uma descrição de todos os campos dessa página e o significado de cada código de status HTTP, consulte [Códigos de Status de Erro HTTP](/pt-br/documentacao/fundamentos/codigos-de-status-http/). ::: ### No Real-Time Events diff --git a/src/content/docs/pt-br/pages/menu-principal/compliance/pci-dss.mdx b/src/content/docs/pt-br/pages/menu-principal/compliance/pci-dss.mdx index 81e15c5b0d..eef0b3a9ac 100644 --- a/src/content/docs/pt-br/pages/menu-principal/compliance/pci-dss.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/compliance/pci-dss.mdx @@ -2,7 +2,7 @@ title: Compliance PCI description: >- Como prestadora de serviços PCI-DSS 4.0 Nível 1, a Azion mantém seus dados - seguros em todas as suas edge locations sem comprometer a performance do seu + seguros em todos os seus data centers sem comprometer a performance do seu site. meta_tags: >- Azion, edge computing, compliance, cartões de pagamento, segurança e @@ -15,7 +15,7 @@ Como parte dos esforços contínuos de compliance, a Azion está sempre aprimora --- -## O que é PCI? +## PCI DSS **PCI DSS** (Payment Card Industry Data Security Standard, *padrão de segurança de dados da indústria de cartões de pagamento*) é uma certificação emitida pelo **PCI Security Standards Council** (Conselho de Normas de Segurança da PCI). Ela define os requisitos internacionais de segurança necessários para que as empresas do setor de cartões de pagamento e seus provedores de serviços operem de forma confiável, protegendo adequadamente seus sistemas de tecnologia, bem como os dados e operações dos seus clientes. @@ -27,9 +27,9 @@ Embora a certificação PCI seja uma exigência para o e-commerce, todas as empr --- -## Como isso afeta os clientes da Azion? +## Implicações para os clientes da Azion -Como prestadora de serviços **PCI-DSS 4.0 Nível 1**, a Azion mantém seus dados seguros em todas as suas edge locations sem comprometer a performance do seu site. +Como prestadora de serviços **PCI-DSS 4.0 Nível 1**, a Azion mantém seus dados seguros em todos os seus data centers sem comprometer a performance do seu site. Dessa forma, você pode: diff --git a/src/content/docs/pt-br/pages/menu-principal/compliance/soc.mdx b/src/content/docs/pt-br/pages/menu-principal/compliance/soc.mdx index 110f2cad51..0d870c4040 100644 --- a/src/content/docs/pt-br/pages/menu-principal/compliance/soc.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/compliance/soc.mdx @@ -12,7 +12,7 @@ A Azion aprimora os controles internos de segurança constantemente para garanti --- -## O que são o SOC 2 Tipo 2 e o SOC 3? +## SOC 2 Tipo 2 e SOC 3 **SOC 2** é um procedimento de auditoria desenvolvido pelo **Instituto Americano de Contadores Públicos Certificados (American Institute of Certified Public Accountants - AICPA)** para garantir que os provedores de serviços tomem sempre as medidas necessárias para manter a segurança e a privacidade dos dados. O SOC 2 atesta a confiabilidade dos serviços prestados pela organização, sendo composto por cinco “princípios de serviço de confiança” que servem como base para o gerenciamento seguro de dados. @@ -30,7 +30,7 @@ Mas isso não é tudo: a Azion deu um passo além, conquistando para os clientes --- -## Como isso afeta os clientes da Azion? +## Implicações para os clientes da Azion As designações **SOC 2 Tipo 2** e **SOC 3** podem ser usadas para simplificar suas auditorias e garantir o nível de segurança dos serviços da plataforma de edge que você usa. diff --git a/src/content/docs/pt-br/pages/menu-principal/gerencie-contas/criar-conta.mdx b/src/content/docs/pt-br/pages/menu-principal/gerencie-contas/criar-conta.mdx index 79e6fd5266..d0382458aa 100644 --- a/src/content/docs/pt-br/pages/menu-principal/gerencie-contas/criar-conta.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/gerencie-contas/criar-conta.mdx @@ -1,73 +1,102 @@ --- -title: Como criar uma conta na Azion +title: Criar uma conta description: >- - Configurações básicas para criar uma conta na Azion usando um endereço de - email e através do Social Login. -meta_tags: 'edge computing, azion, criar conta, email, social login, signup' + Crie uma conta na Azion com um e-mail de trabalho ou uma conta GitHub ou + Google e faça o primeiro login no Azion Console. +meta_tags: 'azion, create account, sign up, work email, social login, github, google' namespace: documentation_creating_account permalink: /documentacao/fundamentos/criar-uma-conta/ --- -Para começar a usar a Azion Web Platform e todos os produtos disponíveis, você precisa completar o processo de sign-up e fazer login na interface de configuração. +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' -Você pode usar dois métodos para criar sua conta Azion: *email* e *Social Login*. As próximas seções fornecerão mais informações sobre o processo de sign-up. +Você pode criar uma conta Azion na [página de cadastro](https://console.azion.com/signup) com um e-mail de trabalho ou com [Social Login](/pt-br/documentacao/fundamentos/social-login/). Social Login aceita uma conta GitHub ou Google. A conta é onde vive cada recurso que você cria, e você a acessa pelo [Azion Console](https://console.azion.com/). Para adicionar uma pessoa a uma conta que já existe, consulte [Gerenciamento de usuários](/pt-br/documentacao/fundamentos/users-management/). --- -## Criando uma conta usando seu endereço de email +## Cadastre-se com um e-mail de trabalho -Para criar uma conta com seu endereço de email, proceda da seguinte maneira: +Para se cadastrar com um e-mail de trabalho: -1. Na [página de sign-up](https://console.azion.com/signup), clique no botão **Sign Up with Work Email**; novos campos serão abertos. -2. Preencha os seguintes campos obrigatórios: - - **Work Email** - - **Password** + + -- Você concorda automaticamente com os [Termos de Serviço do Acordo do Cliente](/pt-br/documentacao/contratos/contrato-de-cliente/) e a [Política de Privacidade](/pt-br/documentacao/contratos/politica-de-privacidade/) ao prosseguir com o processo de sign-up. + Acesse a [página de cadastro do Azion Console](https://console.azion.com/signup). -3. Clique no botão **Sign Up**. + + -Para confirmar a criação de sua conta, você deve verificar seu email. Verifique sua caixa de entrada e procure pelo email de verificação. + Os campos **Work Email** e **Password** são exibidos. -:::note -Na mensagem, você encontrará instruções para confirmar seu endereço de email. Clique no link URL para ativar sua conta. Este link é válid por apenas *24 horas*. + + -Se você não receber o email, verifique sua pasta *Spam*. + Em **Work Email**, insira o endereço da conta. Em **Password**, insira a senha dela. -Se você tiver alguma dúvida, [contate a equipe de vendas](https://www.azion.com/pt-br/contato/). + + + + Ao selecionar **Sign Up**, você aceita os [Termos de Serviço](/pt-br/documentacao/contratos/contrato-de-cliente/) e a [Política de Privacidade](/pt-br/documentacao/contratos/politica-de-privacidade/). + + + + +A Azion envia um e-mail de verificação para o endereço informado. O link nele é válido por 24 horas. + +:::note[nota] +Se o e-mail não estiver na caixa de entrada, verifique a pasta *Spam*. Para ajuda com o cadastro, [entre em contato com a Azion](https://www.azion.com/pt-br/contato/). ::: -Ao clicar no link enviado por email, a página do [Azion Console](https://console.azion.com) será aberta. Para fazer login: +Para confirmar o endereço e fazer login: -1. Insira seu email e clique em **Next**. -2. Insira sua senha e clique no botão **Sign In**. -3. Complete o formulário para personalizar sua experiência, de acordo com suas preferências. -4. Clique no botão **Submit**. + + -Agora você pode acessar o **Azion Console** e começar a construir suas applications. Verifique a página sobre [criar uma aplicação](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/criar-uma-aplicacao/) para continuar sua jornada. + O link ativa a conta e abre [Azion Console](https://console.azion.com/). ---- + + + + + + -## Criando uma conta usando Social Login +Azion Console abre na página inicial, e a conta fica pronta para os primeiros recursos. -A Azion também permite que você crie sua conta através do Social Login. Atualmente, a plataforma suporta contas **GitHub** e **Google**. +--- -Para criar uma conta usando um Social Login, proceda da seguinte maneira: +## Cadastre-se com GitHub ou Google -1. Na [página de sign-up](https://console.azion.com/signup), clique na opção *Social Login* de sua escolha: +Com Social Login, o provedor já validou seu e-mail, então a Azion não envia e-mail de verificação. Para se cadastrar com uma conta GitHub ou Google: -- **Continue with GitHub** -- **Continue with Google** + + -2. Se solicitado, insira seu nome de usuário e senha de acordo com a opção *Social Login* escolhida. + Acesse a [página de cadastro do Azion Console](https://console.azion.com/signup). - - Em alguns casos, você precisará completar algumas etapas adicionais, como prosseguir com opções de autorização. + + + -3. Complete o formulário para personalizar sua experiência, de acordo com suas preferências. -4. Clique no botão **Submit**. + Se o provedor pedir, insira o nome de usuário e a senha dessa conta e autorize o acesso. -Ao escolher criar sua conta via Social Login, não há necessidade de verificar seu email. + + + + -Agora você pode acessar o **Console** e começar a construir suas applications. Verifique a página sobre [criar uma aplicação](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/criar-uma-aplicacao/) para continuar sua jornada. +Azion Console abre na página inicial, e a conta fica pronta para os primeiros recursos. --- + +## Próximos passos + + + + + + + diff --git a/src/content/docs/pt-br/pages/menu-principal/performance/minimizar-o-downtime.mdx b/src/content/docs/pt-br/pages/menu-principal/performance/minimizar-o-downtime.mdx new file mode 100644 index 0000000000..a17d80d727 --- /dev/null +++ b/src/content/docs/pt-br/pages/menu-principal/performance/minimizar-o-downtime.mdx @@ -0,0 +1,158 @@ +--- +title: Minimizar o downtime de uma aplicação +description: >- + Entre no ar na Azion sem interrupção do serviço e mantenha a aplicação + respondendo quando uma origem falha, com Load Balancer, stale cache e uma custom page. +meta_tags: 'azion, downtime, availability, load balancer, backup origin, stale cache, custom pages, go live' +namespace: documentation_fundamentals_minimize_downtime +permalink: /documentacao/fundamentos/minimizar-o-downtime/ +--- + +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' + +O downtime vem de dois lugares: a virada que traz o tráfego para a Azion, e uma origem que para de responder depois. Você evita o primeiro concluindo a configuração antes da mudança de DNS. Você limita o segundo com uma origem de backup, uma cópia expirada do cache e a sua própria página de erro. + +--- + +## Pré-requisitos + +- Um workload, uma aplicação e um connector na Azion. Para configurá-los, consulte [Migrar uma aplicação para a Azion](/pt-br/documentacao/fundamentos/migrar-para-a-azion/). +- Acesso aos registros DNS do domínio no seu provedor de DNS. + +--- + +## Entre no ar sem interrupção + +Os usuários só percebem a mudança de DNS, então todo o resto vem antes: + + + + + No campo **Digital Certificate** do workload, selecione um certificado que cubra o domínio personalizado. Sem ele, o HTTPS falha assim que o domínio passa a resolver para a Azion. + + + + + Em **Subdomain** e **Domain**, insira o nome de host que os usuários digitam. + + + + + Carregue a aplicação do seu próprio computador antes de qualquer usuário. Para os passos, consulte [Faça staging de uma app pelo arquivo hosts](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/testar-edge-application-atraves-do-arquivo-hosts/). + + + + + No seu provedor de DNS, aponte o registro CNAME para o domínio do workload. Para os passos, consulte [Como apontar um domínio para a Azion](/pt-br/documentacao/guias/plataforma/migracao/apontar-dominio-para-a-azion/). + + + + +Os usuários alcançam a aplicação na Azion à medida que os resolvers captam a mudança. Até lá, o provedor anterior continua respondendo a eles, então mantenha-o no ar durante a propagação. + +--- + +## Continue respondendo quando uma origem falha + +O [Load Balancer](/pt-br/documentacao/plataforma/load-balancer/), uma funcionalidade do connector, distribui as requisições entre vários endereços de origem. Ele pula um endereço que retorna um erro 4xx ou 5xx ou que excede os timeouts do connector. Para adicionar uma origem de backup: + + + + + Acesse [Azion Console](https://console.azion.com/) > **Connectors** > **seu connector**. + + + + + Em **Addresses**, adicione o endereço da origem de backup. + + + + + Defina o **Server Role** dele como _Backup_, para que receba requisições apenas quando todos os endereços _Primary_ falharem. + + + + + Em **Balancing Method**, selecione _Round-Robin_ ou _Least Connections_. O **Server Role** se aplica a esses dois métodos. + + + + + +Quando a origem primária falha, as requisições vão para a origem de backup em vez de retornar um erro. Um connector comporta até 10 endereços com o Load Balancer ativo. + +:::note[nota] +Para tirar uma origem do ar para manutenção, desligue o interruptor **Active** do endereço dela. Pelo menos um endereço precisa continuar ativo. +::: + +--- + +## Responda do cache enquanto a origem se recupera + +Uma configuração de cache com **Stale cache** ligado permite que a Azion sirva uma cópia expirada quando a origem falha, em vez de um erro. O Console o liga quando você cria uma configuração; a API e a CLI o deixam desligado. Para conferir: + + + + + Acesse [Azion Console](https://console.azion.com/) > **Applications** > **sua aplicação** > aba **Cache Settings**. + + + + + + + +Enquanto a origem está fora do ar, as requisições por conteúdo que a Azion já armazenou em cache são respondidas com a última cópia. + +--- + +## Mostre a sua própria página em vez de um erro + +Quando a origem falha para um conteúdo que não está no cache, um conjunto de custom pages substitui a resposta 5xx por uma página que você hospeda. Sirva essa página de um connector que continua no ar quando a origem falha, como um bucket do [Object Storage](/pt-br/documentacao/store/object-storage/). Para criar o conjunto: + + + + + Acesse [Azion Console](https://console.azion.com/) > **Custom Pages**. + + + + + + Selecione **+ Custom Page Code** e, em **Page Code**, selecione _503_. + + + + + Selecione o **Connector** que serve a página e, em **Page Path**, insira o caminho dela. Por exemplo: `/errors/503.html`. + + + + + Em **Response TTL**, insira os segundos que a página fica em cache. + + + + + + Acesse **Workloads** > **seu workload**. Em **Deployment Settings**, selecione o conjunto de custom pages e, em seguida, selecione **Save**. + + + + +Um 503 da origem agora retorna a sua página. O código de status continua 503, a menos que você defina **Response Custom Status Code**. + +--- + +## Próximos passos + + + + + + + diff --git a/src/content/docs/pt-br/pages/menu-principal/performance/modo-de-manutencao.mdx b/src/content/docs/pt-br/pages/menu-principal/performance/modo-de-manutencao.mdx new file mode 100644 index 0000000000..8f776b5673 --- /dev/null +++ b/src/content/docs/pt-br/pages/menu-principal/performance/modo-de-manutencao.mdx @@ -0,0 +1,133 @@ +--- +title: Colocar uma aplicação em modo de manutenção +description: >- + Mostre uma página de manutenção a todos os visitantes enquanto altera a + aplicação, mantenha o seu próprio acesso aberto e volte ao normal removendo uma regra. +meta_tags: 'azion, maintenance mode, maintenance page, rules engine, redirect, object storage' +namespace: documentation_fundamentals_maintenance_mode +permalink: /documentacao/fundamentos/modo-de-manutencao/ +--- + +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' + +Você coloca uma aplicação em modo de manutenção com uma regra de fase de requisição no [rules engine](/pt-br/documentacao/plataforma/applications/rules-engine/) dela. A regra responde a todo visitante com uma página de manutenção e encerra a requisição antes que ela chegue à origem. Remover a regra devolve a aplicação ao normal, sem deploy. Para mudar o que os visitantes veem quando a própria origem retorna um erro, consulte [Custom Pages](/pt-br/documentacao/plataforma/custom-pages/). + +--- + +## Pré-requisitos + +- Uma aplicação na Azion, vinculada a um workload. +- Uma página de manutenção alcançável por URL: uma página em outro site, ou um objeto em um bucket do [Object Storage](/pt-br/documentacao/store/object-storage/) servido pelo seu próprio connector. +- O seu endereço IP público, para manter o seu próprio acesso aberto. + +--- + +## Redirecione todo visitante para a página de manutenção + +Para enviar os visitantes a uma página hospedada em outro lugar: + + + + + Acesse [Azion Console](https://console.azion.com/) > **Applications** > **sua aplicação** > aba **Rules Engine**. + + + + + + Insira um **Name**, por exemplo `maintenance`, e selecione **Request Phase**. + + + + + Em **Criteria**, defina **If `${uri}` starts with `/`**, para que a regra corresponda a toda requisição. + + + + + Em **Behaviors**, selecione **Redirect To (302 Found)** e insira a URL da página de manutenção. O 302 informa a navegadores e mecanismos de busca que a mudança é temporária. + + + + + +Toda requisição à aplicação agora responde com um 302 para a página de manutenção, e nada chega à origem. + +--- + +## Sirva a página de manutenção do seu próprio domínio + +Para manter os visitantes no seu domínio, sirva a página de um bucket do Object Storage em vez de redirecionar. **Rewrite Request** exige o [Application Accelerator](/pt-br/documentacao/build/application-accelerator/) na aplicação. + + + + + Para os passos, consulte [Fazer upload e download de objetos](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/dados/upload-e-download-de-objetos-do-bucket/). + + + + + Em **Connectors**, crie um connector do tipo _Object Storage_ que aponte para o bucket. + + + + + Acesse [Azion Console](https://console.azion.com/) > **Applications** > **sua aplicação** > aba **Rules Engine**. + + + + + Selecione **Add Rule**, selecione **Request Phase** e defina **If `${uri}` starts with `/`** em **Criteria**. + + + + + Em **Behaviors**, adicione **Set Connector** com o connector de storage e, em seguida, **Rewrite Request** com `/maintenance.html`. + + + + + +Toda requisição responde com a página de manutenção do bucket, sob o seu próprio domínio. + +--- + +## Mantenha o seu próprio acesso aberto + +Para continuar trabalhando na aplicação enquanto os visitantes veem a página de manutenção, exclua o seu endereço da regra: + + + + + Acesse [Azion Console](https://console.azion.com/) > **Applications** > **sua aplicação** > aba **Rules Engine** e selecione a regra. + + + + + Em **Criteria**, adicione **and** `${remote_addr}` **is not equal** o seu endereço IP público. + + + + + +As requisições do seu endereço chegam à aplicação normalmente. Toda outra requisição continua recebendo a página de manutenção. + +--- + +## Encerre a manutenção + +Para devolver a aplicação ao normal, exclua a regra de manutenção. As demais regras continuam funcionando como antes. + +--- + +## Próximos passos + + + + + + + diff --git a/src/content/docs/pt-br/pages/menu-principal/performance/testar-a-velocidade.mdx b/src/content/docs/pt-br/pages/menu-principal/performance/testar-a-velocidade.mdx new file mode 100644 index 0000000000..85d29ea24b --- /dev/null +++ b/src/content/docs/pt-br/pages/menu-principal/performance/testar-a-velocidade.mdx @@ -0,0 +1,104 @@ +--- +title: Testar a velocidade de uma aplicação +description: >- + Meça a velocidade com que uma aplicação responde na Azion com dados de + usuários reais do Edge Pulse e as métricas de requisição do Real-Time Metrics. +meta_tags: 'azion, speed test, performance, edge pulse, real user monitoring, real-time metrics, latency' +namespace: documentation_fundamentals_test_speed +permalink: /documentacao/fundamentos/testar-a-velocidade/ +--- + +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' + +Você pode medir a velocidade de uma aplicação na Azion por dois lados. [Edge Pulse](/pt-br/documentacao/observe/edge-pulse/) coleta o que os navegadores de usuários reais veem, e [Real-Time Metrics](/pt-br/documentacao/plataforma/real-time-metrics/) mostra em gráficos o que a Azion serviu em cada requisição. Para comparar uma página antes e depois da migração para a Azion, consulte a última seção. + +--- + +## Pré-requisitos + +- Uma aplicação servida por um workload na Azion. Para configurá-los, consulte [Migrar uma aplicação para a Azion](/pt-br/documentacao/fundamentos/migrar-para-a-azion/) ou [Primeiro deploy](/pt-br/documentacao/fundamentos/primeiro-deploy/). +- Acesso ao HTML das páginas que você quer monitorar, para adicionar a tag do Edge Pulse. + +--- + +## Meça o que os usuários reais veem com o Edge Pulse + +Edge Pulse é Real User Monitoring. Uma tag JavaScript nas suas páginas coleta dados de navegação, disponibilidade, latência e bandwidth dos navegadores de visitantes reais. Cada navegador testa três endereços da infraestrutura da Azion por vez, uma vez a cada 30 minutos. A coleta não sobrecarrega o visitante. Para adicionar a tag: + + + + + Acesse [Azion Console](https://console.azion.com/) > **Edge Pulse**. + + + + + Selecione **Copy to Clipboard** na tag de que você precisa. A **Default Tag** executa depois que a página carrega. A **Pre-loading Tag** é para páginas cuja Content Security Policy bloqueia JavaScript inline. + + + + + Cole a tag no HTML de cada página, antes da tag `body` de fechamento. + + + + + +Os navegadores dos seus visitantes começam a enviar medições, e os dados coletados ficam disponíveis no [Real-Time Events](/pt-br/documentacao/observe/real-time-events/). + +:::note[nota] +Edge Pulse respeita a configuração Do Not Track do navegador. Com ela ativa, um novo identificador é gerado a cada visita. +::: + +--- + +## Leia as métricas de requisição no Real-Time Metrics + +Real-Time Metrics mostra em gráficos cada requisição que a Azion serviu, em tempo quase real. Para velocidade, o número útil é quanto do tráfego o cache respondeu sem esperar pela sua origem. Para abrir os gráficos: + + + + + Acesse [Azion Console](https://console.azion.com/) > **Real-Time Metrics**. + + + + + + Na subaba **Data Transferred**, compare **Saved Data** com **Missed Data**. O primeiro é o que o cache respondeu. O segundo é o que chegou à sua origem. + + + + + Use os filtros de tempo para comparar a janela anterior a uma mudança com a janela posterior. + + + + +Uma parcela maior de dados salvos depois de uma mudança significa que menos requisições esperaram pela sua origem. + +--- + +## Compare uma página antes e depois da migração + +Antes de apontar o domínio para a Azion, o seu próprio computador pode alcançar a aplicação pelo arquivo `hosts`. Todos os outros ainda alcançam o provedor atual, então você obtém a mesma página dos dois lugares. Para comparar: + +1. Carregue a página no provedor atual e anote o tempo de carregamento que as ferramentas de desenvolvedor do navegador informam. +2. Faça o staging da aplicação pelo arquivo `hosts`. Para os passos, consulte [Faça staging de uma app pelo arquivo hosts](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/testar-edge-application-atraves-do-arquivo-hosts/). +3. Carregue a mesma página duas vezes em uma janela privada do navegador e guarde o segundo tempo. O primeiro carregamento preenche o cache. O segundo é o que os visitantes recebem. + +A diferença entre os dois tempos é o que a Azion acrescenta para essa página. Repita com as páginas que os seus usuários mais abrem. + +--- + +## Próximos passos + + + + + + + diff --git a/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/comecar-com-um-template.mdx b/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/comecar-com-um-template.mdx index ee2356febd..b16fd4b593 100644 --- a/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/comecar-com-um-template.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/comecar-com-um-template.mdx @@ -19,7 +19,7 @@ Você tem as seguintes maneiras de começar a construir com templates: -Depois de criar uma application com seu método preferido, volte para continuar sua jornada e [activá-la em produção](/pt-br/documentacao/produtos/ative-em-producao/). +Depois de criar uma application com seu método preferido, volte para continuar sua jornada e [activá-la em produção](/pt-br/documentacao/fundamentos/). diff --git a/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/fundamentos.mdx b/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/fundamentos.mdx index b0b9cd2043..efd6806762 100644 --- a/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/fundamentos.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/fundamentos.mdx @@ -1,28 +1,59 @@ --- title: Fundamentos description: >- - Crie uma conta na Azion, adicione as pessoas que trabalham nela, mantenha a - conta segura e entenda o que é cobrado. + Entenda como os recursos que você implanta na Azion se conectam em uma cadeia + que serve tráfego, como sua conta é organizada e por onde começar. meta_tags: >- - conta, fundamentos, faturamento, assinaturas, permissões, times, segurança, conformidade, single sign-on, autenticação multifator + fundamentals, Azion Platform, platform resources topology, workload, application, firewall, connector, account, teams, permissions, billing, security namespace: documentation_fundamentals permalink: /documentacao/fundamentos/ --- +import PlatformTopology from '~/components/webkit/PlatformTopology.vue' import DocCardGroup from '@aziontech/webkit/doc-card-group' import DocCard from '@aziontech/webkit/doc-card' -Tudo o que você constrói na Azion fica dentro de uma conta. Esta seção trata da própria conta: como criá-la, quem mais pode trabalhar nela e com quais permissões, como o uso vira uma fatura e quais controles mantêm a conta segura. +Uma plataforma web é um serviço sobre o qual você constrói, em vez de uma pilha que você opera. Você escreve a aplicação e descreve como ela deve se comportar, e o provedor a executa em uma infraestrutura própria, filtra o tráfego que chega até ela e mostra o que aconteceu com cada requisição. Os servidores, o roteamento e a escala deixam de ser trabalho seu. -Procura o que a plataforma faz? Comece por [Como a Azion funciona](/pt-br/documentacao/plataforma/). +**Azion Platform** é esse serviço na infraestrutura globalmente distribuída da Azion: a tecnologia integrada e as interfaces onde você constrói, protege e escala aplicações, o que inclui operá-las e monitorá-las. Use Azion Platform para executar uma aplicação perto dos usuários, bloquear o tráfego que ela não deve receber, armazenar os dados que ela lê e observar cada requisição que ela serve. + + +--- + +## Topologia dos Recursos de Plataforma + +Tudo o que serve tráfego na Azion é um conjunto de recursos de plataforma vinculados uns aos outros, com o que você habilita listado dentro do recurso ao qual se anexa. O diagrama mostra como eles se conectam: o que o workload vincula, o que cada recurso guarda, de onde a aplicação busca o conteúdo e o que uma função pode chamar. Selecione um card para abri-lo e ler o que ele é e o que guarda. + + + +1. Um [workload](/pt-br/documentacao/plataforma/workloads/) recebe o tráfego dos seus domínios. Ele guarda os [domínios](/pt-br/documentacao/plataforma/workloads/domains/) e o certificado do [Certificate Manager](/pt-br/documentacao/plataforma/certificate-manager/), e vincula, lado a lado, um firewall, uma aplicação e um conjunto de custom pages. +2. Um [firewall](/pt-br/documentacao/plataforma/firewall/) inspeciona cada requisição antes da aplicação. Você aplica a ele um rule set de [WAF](/pt-br/documentacao/secure/waf/), [Bot Manager](/pt-br/documentacao/secure/bot-manager/), listas do [Network Shield](/pt-br/documentacao/secure/network-shield/) e funções. [DDoS Protection](/pt-br/documentacao/plataforma/ddos-protection/) está sempre ativa, com ou sem firewall. +3. Uma [aplicação](/pt-br/documentacao/plataforma/applications/) serve o conteúdo. O [Rules Engine](/pt-br/documentacao/plataforma/applications/rules-engine/) aplica behaviors, [Cache](/pt-br/documentacao/build/cache/) responde requisições repetidas a partir de uma cópia armazenada, [Image Processor](/pt-br/documentacao/build/image-processor/) redimensiona imagens no caminho e [Functions](/pt-br/documentacao/build/functions/) executa seu código no caminho da requisição. +4. Um conjunto de [custom pages](/pt-br/documentacao/plataforma/custom-pages/) substitui as respostas de erro padrão por páginas que você controla. +5. Quando o cache não consegue responder, a aplicação busca o conteúdo por um [connector](/pt-br/documentacao/plataforma/connectors/): no seu servidor de origem ou em um bucket do Object Storage. [Load Balancer](/pt-br/documentacao/plataforma/load-balancer/) e [Origin Shield](/pt-br/documentacao/secure/origin-shield/) são habilitados no connector. +6. As funções chamam o que o card Store e AI guarda: [SQL Database](/pt-br/documentacao/store/sql-database/), [KV Store](/pt-br/documentacao/store/kv-store/), [AI Inference](/pt-br/documentacao/build/ai-inference/) e [Object Storage](/pt-br/documentacao/store/object-storage/), que um connector de storage também pode usar como origem. + +Para mover para essa cadeia uma aplicação que já roda em outro lugar, consulte [Migrar para a Azion](/pt-br/documentacao/fundamentos/migrar-para-a-azion/). + +## Interfaces + +Você cria e gerencia cada recurso da cadeia pelas interfaces da plataforma. [Azion Console](/pt-br/documentacao/guias/plataforma/conta-e-billing/conhecendo-o-azion-console/) é a interface web, [Azion CLI](/pt-br/documentacao/devtools/cli/) executa as mesmas operações a partir do terminal, a [Azion API](https://api.azion.com/) as expõe por HTTPS para integrações e o [Azion Terraform Provider](/pt-br/documentacao/devtools/terraform/) as declara como código. O catálogo da Azion agrupa o que você habilita nesses recursos em quatro categorias: Build, Store, Secure e Observe. Para o caminho da requisição e a tabela do que cada recurso guarda, consulte [Como a Azion funciona](/pt-br/documentacao/fundamentos/como-funciona/). + +--- + +## Sua conta + +Tudo o que você constrói na Azion vive dentro de uma [conta](/pt-br/documentacao/fundamentos/account-settings/). A conta guarda os recursos, as pessoas que trabalham neles, o perfil de faturamento e os controles de segurança que se aplicam a cada login. Cada pessoa entra como um usuário da conta. O proprietário da conta cria as equipes e define suas permissões, e cada usuário pertence a uma ou mais equipes que decidem quais recursos ele pode ver ou alterar. Uma conta do tipo Group também guarda [contas de clientes](/pt-br/documentacao/fundamentos/contas/), cada uma com o próprio proprietário. O uso é medido por conta e vira uma fatura na página de [Faturamento](/pt-br/documentacao/fundamentos/billing-and-subscriptions/). + +Se você ainda não tem uma conta, consulte [Criar uma conta](/pt-br/documentacao/fundamentos/criar-uma-conta/). Para o modelo completo, consulte [Contas, equipes e usuários](/pt-br/documentacao/fundamentos/contas-equipes-e-usuarios/). --- +## Próximos passos + - - - - - - + + + + diff --git a/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/visao-geral-da-azion.mdx b/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/visao-geral-da-azion.mdx index 5b2a254b6d..4f2ae0e0d3 100644 --- a/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/visao-geral-da-azion.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/visao-geral-da-azion.mdx @@ -1,96 +1,122 @@ --- title: Como a Azion funciona description: >- - Esta documentação apresenta a Azion Web Platform e conceitos-chave para ajudar a entender melhor a arquitetura distribuída. -meta_tags: 'Azion, application, jornada, onboarding, templates, domínios, tráfego' + Acompanhe uma requisição do usuário pela infraestrutura distribuída da Azion + até a sua origem e veja o que cada recurso do caminho acrescenta. +meta_tags: >- + Azion, Azion Platform, how Azion works, distributed infrastructure, request path, data center, serverless, WAF, DDoS protection, cache, observability, Console, CLI, API, Terraform namespace: documentation_azion_platform_overview -permalink: /documentacao/plataforma/ +permalink: /documentacao/fundamentos/como-funciona/ --- +import UseCaseList from '~/components/webkit/UseCaseList.vue' +import FrameBox from '@aziontech/webkit/frame-box' +import ItemList from '@aziontech/webkit/item-list' +import DocItem from '@aziontech/webkit/doc-item' -A **Azion Web Platform** permite que você implemente seus projetos instantaneamente na rede global mais confiável, proteja suas aplicações com segurança avançada e escale do zero ao pico sem cold starts. +Uma requisição para a sua aplicação não viaja até um servidor que você opera. Ela chega ao data center da infraestrutura distribuída da Azion com a melhor rota até ele, e a configuração que você salvou decide o que acontece em seguida: se a requisição é bloqueada, respondida do cache, tratada pelo seu código ou encaminhada para a sua origem. **Azion Platform** é a tecnologia integrada e o conjunto de interfaces onde essa configuração vive, e onde você constrói, protege e escala aplicações, o que inclui operá-las e monitorá-las. -A Azion é a plataforma web líder que permite que empresas construam, protejam e escalem aplicações modernas em uma infraestrutura global totalmente gerenciada. Com um conjunto robusto de soluções para desenvolvimento de aplicações, cibersegurança e AI, a Azion possibilita que desenvolvedores e empresas entreguem experiências digitais de alto desempenho e seguras no mundo todo. Com a confiança de líderes globais como Prime Video, Neon, Global Fashion Group e Radware, oferecemos o caminho mais rápido para a criação de aplicações modernas. Descubra como a Azion pode transformar suas experiências digitais em [www.azion.com](https://www.azion.com/). +A Azion inclui entrega de conteúdo e cache, mas é mais ampla que uma CDN. A mesma infraestrutura executa código de aplicação sem servidor para provisionar, filtra o tráfego que chega às suas aplicações e APIs, armazena os dados que elas leem e reporta cada requisição em tempo real. Esta página cobre onde a plataforma roda, o caminho que uma requisição percorre, o que você habilita em cada recurso desse caminho e as interfaces pelas quais você a gerencia. --- -## Conceitos básicos +## Infraestrutura distribuída -### O que é arquitetura distribuída? +A Azion executa a sua configuração em data centers espalhados pelo mundo, e cada requisição é servida pelo data center com a melhor rota até ela. A rota é escolhida por latência, condições de rede e carga no momento em que a requisição chega, então dois usuários em países diferentes que pedem a mesma página são atendidos perto de onde estão, a partir da mesma configuração. Computação e dados ficam perto do usuário, o que reduz a latência e melhora a confiabilidade. Os deploys são rápidos, as funções rodam sem cold start e a visibilidade do tráfego é em tempo real. Para a lista de data centers, consulte [Our Network](https://www.azion.com/pt-br/produtos/our-network/). -**Arquitetura distribuída** é um paradigma de computação altamente distribuída que visa aproximar a computação e o armazenamento de dados do local onde é necessário, normalmente próximo aos usuários, em pontos de presença globais. +## Caminho da requisição -Esse paradigma permite a construção e o gerenciamento de [aplicações modernas](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/criar-uma-aplicacao/), capazes de atender à crescente demanda por processamento em tempo real, latência reduzida, melhor privacidade de dados e a capacidade de lidar com a enorme quantidade de dados gerados hoje em dia. +O diagrama mostra o caminho de uma requisição, do usuário até a sua origem e de volta. Dentro da Azion Platform, a requisição é roteada para um data center, onde os recursos que você configurou são executados, e o conteúdo que o data center não consegue responder é buscado pela camada de entrega: +```mermaid +flowchart LR + user([Usuário]) --> routing[Roteamento] + subgraph platform [Azion Platform] + routing --> dc + subgraph dc [Data center] + firewall[Firewall] + applications[Applications] + cache[Cache] + accelerator[Application Accelerator] + functions[Functions] + image[Image Processor] + end + dc --> delivery[Tiered Cache e Load Balancer] + end + delivery --> origin[(Origem)] +``` -## O que é uma plataforma com arquitetura distribuída? +As requisições vão da esquerda para a direita. As respostas voltam pelo mesmo caminho. -Uma **plataforma com arquitetura distribuída** deve ser projetada para operar de forma eficiente em uma rede global de pontos de presença. A plataforma deve possuir várias características e funcionalidades importantes para atender aos desafios e requisitos exclusivos que demanda a computação distribuída: +1. A requisição do usuário chega à Azion. A Azion seleciona a melhor rota e encaminha a requisição para o data center mais próximo, com base em latência, condições de rede e carga. +2. Nesse data center, a Azion aplica a sua configuração e lógica: o workload dono do domínio, as políticas de segurança do seu firewall, o comportamento de cache e as regras da sua aplicação, e o código das funções que eles executam. +3. Quando o cache não consegue responder à requisição, a aplicação busca o conteúdo na sua origem através do seu connector. O [Tiered Cache](/pt-br/documentacao/build/cache/) acrescenta uma segunda camada de cache entre os data centers e a sua origem, e o [Load Balancer](/pt-br/documentacao/plataforma/load-balancer/) distribui a busca entre vários endereços. +4. A resposta é entregue ao usuário, e a requisição aparece nas suas métricas, eventos e streams. -- Experiência superior para desenvolvimento de aplicações, segurança, orquestração e observabilidade. -- NoOps e uma abordagem de autoatendimento. -- Padrões abertos. -- Monitoramento e observabilidade contínuos. -- Ferramentas de otimização de desempenho para otimizar a alocação de recursos e o desempenho das aplicações. -- Ampla cobertura geográfica e estratégias de otimização de tráfego. +Os recursos nesse caminho se vinculam uns aos outros: um workload vincula um firewall, uma aplicação e um conjunto de custom pages, e a aplicação busca o conteúdo por um connector. Para o diagrama interativo e a que cada recurso se anexa, consulte [Topologia dos Recursos de Plataforma](/pt-br/documentacao/fundamentos/#topologia-dos-recursos-de-plataforma). --- -## Como a plataforma da Azion atende uma requisição +## Recursos de plataforma no caminho da requisição -A **Azion Web Platform** é construída sobre uma infraestrutura robusta composta por vários componentes-chave, bem como lógica e regras de negócios que permitem oferecer um serviço confiável, escalável e de alto desempenho. +Tudo o que você habilita ou cria vive nos recursos do caminho da requisição. Parte disso é habilitada em um recurso que você já tem, como um rule set aplicado ao firewall ou um interruptor na aplicação; o restante são recursos que você cria por conta própria, como um bucket ou uma zona de DNS. A tabela lista cada item pelo recurso ao qual se anexa, com um link para a sua referência: -Aproveitando sua rede distribuída e infraestrutura descentralizada, a plataforma atende rapidamente as requisições com baixa latência e menor consumo de largura de banda, otimizando a entrega de conteúdo e aprimorando a experiência do usuário. +| Recurso | O que você habilita ou cria nele | Referência | +| --- | --- | --- | +| Workload | O certificado TLS vinculado ao workload e a mitigação de DDoS, que se aplica a todo workload sem nada a habilitar. | [Certificate Manager](/pt-br/documentacao/plataforma/certificate-manager/), [DDoS Protection](/pt-br/documentacao/plataforma/ddos-protection/) | +| Firewall | Um rule set de WAF aplicado ao firewall, uma instância do Bot Manager executada nele e as network lists que suas regras referenciam. | [WAF](/pt-br/documentacao/secure/waf/), [Bot Manager](/pt-br/documentacao/secure/bot-manager/), [Network Shield](/pt-br/documentacao/secure/network-shield/) | +| Aplicação | As configurações de cache, os interruptores de Application Accelerator e Image Processor, as funções instanciadas na aplicação e o conjunto de custom pages atribuído a ela. | [Cache](/pt-br/documentacao/build/cache/), [Application Accelerator](/pt-br/documentacao/build/application-accelerator/), [Image Processor](/pt-br/documentacao/build/image-processor/), [Custom Pages](/pt-br/documentacao/plataforma/custom-pages/) | +| Connector | O balanceamento entre vários endereços e o Origin Shield, que permite que só os ranges de IP da Azion alcancem a origem. | [Load Balancer](/pt-br/documentacao/plataforma/load-balancer/), [Origin Shield](/pt-br/documentacao/secure/origin-shield/) | +| Recursos que você cria por conta própria | Funções, buckets, bancos de dados, namespaces de chave-valor, zonas de DNS, streams e a infraestrutura que você mesmo opera com o Orchestrator. | [Functions](/pt-br/documentacao/build/functions/), [Object Storage](/pt-br/documentacao/store/object-storage/), [SQL Database](/pt-br/documentacao/store/sql-database/), [KV Store](/pt-br/documentacao/store/kv-store/), [Edge DNS](/pt-br/documentacao/secure/edge-dns/), [Data Stream](/pt-br/documentacao/observe/data-stream/), [Orchestrator](/pt-br/documentacao/build/orchestrator/) | +| Dentro de uma função | Os modelos que o seu código chama e os adaptadores que você ajusta para eles. | [AI Inference](/pt-br/documentacao/build/ai-inference/), [LoRA Fine-Tune](/pt-br/documentacao/build/ai-inference/lora-fine-tune/) | +| Tudo acima | Os eventos brutos, as métricas e as medições de usuários reais que reportam o que a plataforma fez com cada requisição. | [Real-Time Events](/pt-br/documentacao/observe/real-time-events/), [Real-Time Metrics](/pt-br/documentacao/plataforma/real-time-metrics/), [Edge Pulse](/pt-br/documentacao/observe/edge-pulse/) | -A plataforma da Azion funciona, em alto nível, da seguinte forma: +Todo controle da tabela pode ser automatizado pela API e por infraestrutura como código. O catálogo da Azion agrupa tudo o que está na tabela em quatro categorias, Build, Store, Secure e Observe; a [página de preços](/pt-br/documentacao/fundamentos/precos/) é organizada assim. -![Gráfico sobre como a Azion funciona](/assets/docs/images/uploads/request_flow.png) +## O que você pode construir -1. Uma requisição é enviada para um serviço web em execução na **Azion Web Platform**. A plataforma define, usando roteamento definido por software, o melhor caminho para a requisição e a redireciona para o data center *mais próximo*. -- Neste contexto, *mais próximo* refere-se ao **ponto de presença** que pode atender a requisição do usuário mais rapidamente, com base em uma variedade de fatores, como localização geográfica, condições de rede, carga do servidor, entre outros. -2. Dentro do **ponto de presença**, a requisição é processada por vários módulos funcionais antes de enviar de volta uma resposta apropriada ao usuário. Isso ocorre para aplicar toda a lógica de negócios, configurações e parâmetros adequados à requisição. Através dos [produtos Azion](/pt-br/documentacao/), os clientes podem implementar, controlar, monitorar, dimensionar e automatizar recursos na plataforma, em tempo real. -- A requisição é redirecionada para a origem apenas no caso de o ponto de presença não ter uma resposta apropriada. -3. A resposta é enviada para o usuário ou dispositivo. +A mesma cadeia de recursos serve workloads muito diferentes. A Azion os organiza em cinco soluções, e os casos de uso abaixo são aqueles por onde as equipes mais costumam começar. Cada um leva à arquitetura que o implementa ou, quando ainda não há arquitetura publicada, à referência por onde ele começa. ---- +### Construir e executar aplicações -## O quê você pode fazer com a Azion? + -Os produtos da Azion são organizados em quatro categorias: +### Melhorar a performance e a confiabilidade das aplicações -| Categoria | O que cobre | Produtos | -| --- | --- | --- | -| Build | Execute código e entregue conteúdo a partir da infraestrutura distribuída da Azion: funções, modelos de AI, cache e otimizações de entrega, e a infraestrutura que você mesmo opera com o Orchestrator. | [Functions](/pt-br/documentacao/build/functions/), [AI Inference](/pt-br/documentacao/build/ai-inference/), [LoRA Fine-Tune](/pt-br/documentacao/build/ai-inference/lora-fine-tune/), [Cache](/pt-br/documentacao/build/cache/), [Application Accelerator](/pt-br/documentacao/build/application-accelerator/), [Image Processor](/pt-br/documentacao/build/image-processor/), [Orchestrator](/pt-br/documentacao/build/orchestrator/) | -| Store | Mantenha arquivos, dados relacionais e pares chave-valor ao lado das funções que os leem. | [Object Storage](/pt-br/documentacao/store/object-storage/), [SQL Database](/pt-br/documentacao/store/sql-database/), [KV Store](/pt-br/documentacao/store/kv-store/) | -| Secure | Filtre ataques na camada de aplicação, bots e redes indesejadas antes que o tráfego chegue à aplicação, e resolva e balanceie esse tráfego no caminho. | [WAF](/pt-br/documentacao/secure/waf/), [Bot Manager](/pt-br/documentacao/secure/bot-manager/), [Network Shield](/pt-br/documentacao/secure/network-shield/), [Origin Shield](/pt-br/documentacao/secure/origin-shield/), [Edge DNS](/pt-br/documentacao/secure/edge-dns/), [Load Balancer](/pt-br/documentacao/plataforma/load-balancer/) | -| Observe | Veja o que a plataforma faz com cada requisição: eventos brutos, métricas, streams de logs e medições de usuários reais. | [Real-Time Events](/pt-br/documentacao/observe/real-time-events/), [Real-Time Metrics](/pt-br/documentacao/plataforma/real-time-metrics/), [Data Stream](/pt-br/documentacao/observe/data-stream/), [Edge Pulse](/pt-br/documentacao/observe/edge-pulse/) | - -Isto inclui poder completar tarefas como: - -- Criação e implantação de [aplicações](/pt-br/documentacao/plataforma/applications/) que são executadas diretamente na rede global. -- Uso de [templates e integrações](/pt-br/documentacao/marketplace/visao-geral-templates-e-integracoes/) para acelerar seu desenvolvimento e testar soluções pré-construídas. -- Criação de [arquiteturas zero trust](/pt-br/documentacao/guias/) para proteger seu conteúdo e aplicações. -- Melhora da entrega de conteúdo confiando em uma [rede altamente distribuída](https://www.azion.com/pt-br/produtos/nossa-rede/). -- Definição de [regras de cache](/pt-br/documentacao/build/cache/), otimizações personalizadas e configurações avançadas. -- Monitoramento de applications com [dados em tempo real](/pt-br/documentacao/plataforma/real-time-metrics/). -- Melhora no [desempenho](/pt-br/documentacao/arquiteturas/melhorar-performance-e-confiabilidade/content-delivery/), com menor latência e uso de largura de banda, ao mesmo tempo em que reduz os custos operacionais. -- Desenvolvimento com diferentes [frameworks e linguagens suportadas](/pt-br/documentacao/guias/). -- [Migração de sua arquitetura e conteúdo](/pt-br/documentacao/fundamentos/migrar-para-a-azion/) para a plataforma da Azion. -- Cumprimentos das [leis de conformidade](https://www.azion.com/pt-br/compliance/). + + +### Construir e executar workloads de AI + + + +### Proteger aplicações e redes + + + +### Entregar mídia e conteúdo de streaming + + + +[Templates e integrações](/pt-br/documentacao/marketplace/visao-geral-templates-e-integracoes/) dão a muitos desses casos um ponto de partida implantável, os [guias](/pt-br/documentacao/guias/) cobrem frameworks e tarefas passo a passo, e [Migrar para a Azion](/pt-br/documentacao/fundamentos/migrar-para-a-azion/) cobre a mudança de uma aplicação que já roda em outro lugar. --- -## Gestão da plataforma +## Interfaces -A Azion desenvolveu um painel de controle e um conjunto de APIs usadas pelos clientes e pela equipe da Azion para gerenciar a **Azion Web Platform**. Isso é executado na plataforma e aproveita uma arquitetura de microsserviços e uma estrutura de front-end proprietária, garantindo segurança e alta disponibilidade. +Você gerencia a plataforma por conta própria, por interfaces que expõem os mesmos recursos. [Azion Console](/pt-br/documentacao/guias/plataforma/conta-e-billing/conhecendo-o-azion-console/) configura recursos, provisionamento, faturamento e permissões no navegador. [Azion CLI](/pt-br/documentacao/devtools/cli/) gerencia os serviços a partir do terminal e é open source, escrita em Go. A [Azion API](https://api.azion.com/) é uma API REST sobre HTTPS para integração e automação, e o [Azion Terraform Provider](/pt-br/documentacao/devtools/terraform/) gerencia recursos da Azion como código. -Você pode acessá-lo e obter uma experiência de usuário simples e rápida através de: +Algumas origens aceitam conexões só de endereços conhecidos. Para liberar os data centers da Azion no firewall da sua origem, consulte [Como obter os ranges de IP da Azion para allowlisting no servidor de origem](/pt-br/documentacao/guias/seguranca-de-aplicacoes/bots-e-rede/obter-ranges-ip-azion/). + +Para os fundamentos de arquiteturas distribuídas, assista à playlist [Introduction to Platform Foundations](https://www.youtube.com/watch?v=ZBC8h-0l1FQ&list=PL02NW2s3y10N0SQ-2mWL9WN-RWHE8atMp). + +--- -- [Azion Console](/pt-br/documentacao/guias/plataforma/conta-e-billing/como-acessar-o-azion-console/): é a interface de configuração. Com o Azion Console, você tem acesso a todos os produtos e serviços fornecidos pela Azion, podendo criá-los e gerenciá-los. O Azion Console também permite o provisionamento de recursos, bem como o gerenciamento da sua conta, faturamento e permissões de usuário. -- [Azion CLI](/pt-br/documentacao/devtools/cli/): é uma ferramenta de código aberto que permite o gerenciamento de serviços usando um terminal. A Azion CLI é construída em Go. -- [API da Azion](https://api.azion.com/): é uma API RESTful baseada em requisições HTTPS. Ela permite que você integre seus sistemas à plataforma da Azion e crie novas aplicações e serviços, além de verificar, remover ou atualizar as configurações existentes. -- [Azion Terraform Provider](/pt-br/documentacao/devtools/terraform/): o Terraform se comunica com as APIs da Azion, para que você possa gerenciar sua infraestrutura hospedada na plataforma da Azion, localmente, como código. +## Recursos relacionados -:::tip[dica] -Para obter mais detalhes sobre os fundamentos da arquitetura distribuída e da Azion Web Platform, assista essa playlist com os [fundamentos da plataforma](https://www.youtube.com/watch?v=7OihCEBhqDQ&list=PL02NW2s3y10NCJ2LrrDyeFPUFB6VD4ywh). -::: \ No newline at end of file + + + Abra a conta que reúne todos os recursos que você cria. + Coloque uma aplicação no caminho da requisição em poucos minutos. + Traga uma aplicação existente e a sua infraestrutura para a Azion. + + diff --git a/src/content/docs/pt-br/pages/menu-principal/pricing/pricing.mdx b/src/content/docs/pt-br/pages/menu-principal/pricing/pricing.mdx index 3bd85ec6cb..9cc1c93698 100644 --- a/src/content/docs/pt-br/pages/menu-principal/pricing/pricing.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/pricing/pricing.mdx @@ -1557,12 +1557,12 @@ O plano **Mission Critical** é ideal para clientes cuja presença online é cr | **Best Practices Review**
Análise aprofundada da sua configuração para ajudar a desbloquear todo o potencial do seu ambiente digital | --- | Add-on pago | 20 horas/ano inclusas | 40 horas/ano inclusas | | **Instructor-Led Training**
Análise aprofundada da sua configuração para ajudar a desbloquear todo o potencial do seu ambiente digital | --- | --- | Add-on pago | Add-on pago | | **Business Events Support**
Suporte e assistência fornecidos para ajudar os clientes durante eventos em tempo real | --- | --- | 1 evento por ano | Incluso | -| **Technical Account Manager**
Um profissional que oferece orientação técnica estratégica para ajudar a acelerar sua transformação digital e sua jornada de edge computing | --- | --- | Add-on pago | Incluso | +| **Technical Account Manager**
Um profissional que oferece orientação técnica estratégica para ajudar a acelerar sua adoção da Azion | --- | --- | Add-on pago | Incluso | | **Managed Configurations**
Azion gerencia configurações para melhor desempenho, segurança e conformidade no edge | --- | --- | Add-on pago | Add-on pago | | **Security Response Team**
Equipe de especialistas em segurança para detectar, mitigar e responder prontamente a ameaças à segurança | --- | --- | Add-on pago | Add-on pago | | **Slack Channel**
Comunicação em tempo real, suporte e trabalho em equipe em um único local | --- | --- | Add-on pago | Add-on pago | -:::caution[atenção] +:::caution[Atenção] Horário comercial é geralmente definido como das **09:00 AM às 06:00 PM**, no país em que a Azion foi contratada, excluindo feriados e fins de semana. Esses horários podem variar em países com múltiplos fusos horários. ::: */} diff --git a/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/migrar-para-a-azion/migrar-para-a-azion.mdx b/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/migrar-para-a-azion/migrar-para-a-azion.mdx index ecc17ecfde..3d01813680 100644 --- a/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/migrar-para-a-azion/migrar-para-a-azion.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/migrar-para-a-azion/migrar-para-a-azion.mdx @@ -1,126 +1,201 @@ --- -title: Como migrar sua aplicação para a Azion -description: Aprenda como você pode trazer suas aplicações e infraestrutura para a Azion. -meta_tags: 'azion, migrar, domains, staging, domínio' +title: Migrar uma aplicação para a Azion +description: >- + Mova uma aplicação de outro provedor para a Azion, do connector e do workload + à mudança de DNS, com um teste antes da troca. +meta_tags: 'azion, migrate, migration, connector, workload, custom domain, dns' namespace: documentation_migrate_to_azion permalink: /documentacao/fundamentos/migrar-para-a-azion/ --- -import DocButton from '~/components/webkit/DocButton.vue'; -Este guia fornece um passo a passo para migrar aplicações existentes para a Azion. Ele descreve os requisitos necessários e detalha os passos para uma transferência bem-sucedida de aplicações de outros serviços para uma arquitetura distribuída. +import DocSteps from '@aziontech/webkit/doc-steps' +import DocStep from '@aziontech/webkit/doc-step' +import DocCardGroup from '@aziontech/webkit/doc-card-group' +import DocCard from '@aziontech/webkit/doc-card' +import Code from '~/components/webkit/CodeBlock.vue' + +Uma aplicação que roda em outro provedor tem uma origem, um domínio e regras que moldam o seu tráfego. Migrá-la para a Azion significa reconstruir essa cadeia na plataforma e mover o domínio por último, para que a aplicação continue servindo enquanto você trabalha. Você registra a origem como um [connector](/pt-br/documentacao/plataforma/connectors/), a serve por uma [aplicação](/pt-br/documentacao/plataforma/applications/), a expõe em um [workload](/pt-br/documentacao/plataforma/workloads/) e aponta o domínio para o workload. + +Se você está saindo de um dos provedores abaixo, siga o guia dele. Cada um mapeia os serviços do provedor para os equivalentes na Azion. + +| Provedor | O guia cobre | +| --- | --- | +| [Akamai](/pt-br/documentacao/guias/plataforma/migracao/akamai-guia-migracao/) | Entrega de conteúdo, segurança de aplicações, funções, armazenamento chave-valor, regras de tráfego, DNS, gerenciamento de tráfego, armazenamento de objetos, streaming de logs, monitoramento e proteção DDoS | +| [AWS](/pt-br/documentacao/guias/plataforma/migracao/aws-guia-migracao/) | Entrega de conteúdo, funções, armazenamento de objetos, armazenamento chave-valor, DNS, WAF, proteção DDoS e observabilidade | +| [Cloudflare](/pt-br/documentacao/guias/plataforma/migracao/cloudflare-guia-migracao/) | Funções, armazenamento chave-valor, armazenamento de objetos, banco de dados SQL, DNS, WAF e mais | +| [Fastly](/pt-br/documentacao/guias/plataforma/migracao/fastly-guia-migracao/) | Entrega de conteúdo, funções, armazenamento chave-valor, armazenamento de objetos, WAF, logging e observabilidade | +| [Vercel](/pt-br/documentacao/guias/plataforma/migracao/vercel-guia-migracao/) | Projetos, preview deployments, funções, armazenamento de objetos, armazenamento de configuração, firewall, web analytics e observabilidade | --- -## Migrando de outras plataformas +## Pré-requisitos -Se você está migrando de uma plataforma específica, a Azion oferece guias de migração dedicados: +- Uma conta Azion. Para abrir uma, consulte [Criar uma conta](/pt-br/documentacao/fundamentos/criar-uma-conta/). +- O endereço da origem atual: um nome de host, um endereço IPv4 ou IPv6 ou um bucket do [Object Storage](/pt-br/documentacao/store/object-storage/). +- Acesso aos registros DNS do domínio no seu provedor de DNS. +- (Opcional) A [Azion CLI](/pt-br/documentacao/devtools/cli/), para desenvolvimento local e deploy. -- **Akamai**: [Guia de migração da Akamai para a Azion](/pt-br/documentacao/guias/plataforma/migracao/akamai-guia-migracao/) - cobre Ion, App & API Protector, EdgeWorkers, EdgeKV, Cloudlets, Edge DNS, Global Traffic Management, NetStorage, DataStream, mPulse e Prolexic -- **AWS**: [Guia de migração da AWS para a Azion](/pt-br/documentacao/guias/plataforma/migracao/aws-guia-migracao/) - cobre CloudFront, Lambda, S3, DynamoDB, Route 53, WAF, proteção DDoS e observabilidade -- **Cloudflare**: [Guia de migração da Cloudflare para a Azion](/pt-br/documentacao/guias/plataforma/migracao/cloudflare-guia-migracao/) — cobre Workers, KV, R2, D1, DNS, WAF e mais -- **Fastly**: [Guia de migração da Fastly para a Azion](/pt-br/documentacao/guias/plataforma/migracao/fastly-guia-migracao/) - cobre Full-Site Delivery, Compute, Edge Data Storage, Object Storage, WAF, logging e observabilidade -- **Vercel**: [Guia de migração da Vercel para a Azion](/pt-br/documentacao/guias/plataforma/migracao/vercel-guia-migracao/) - cobre Projects, Preview Deployments, Functions, Blob, Edge Config, Firewall, Web Analytics e observabilidade +:::note[nota] +Com o plano de suporte **Business** ou superior, o [Integration Services](/pt-br/documentacao/servicos/integration-services/) dá acesso a especialistas da Azion durante a migração. Para os planos, consulte os [Serviços de Suporte da Azion](https://www.azion.com/pt-br/servicos-profissionais/). +::: --- -## Por que migrar para a Azion +## Registre a origem como um connector -Migrar para a Azion Web Platform oferece vantagens distintas para aplicações modernas: +Um connector informa à Azion de onde buscar o conteúdo e o código da aplicação. Para criá-lo no Azion Console: -**Performance** -- Execução sem cold starts em uma arquitetura distribuída -- Deploys instantâneos com atualizações sem downtime -- Pontos de presença globais que executam lógica próxima aos seus usuários + + -**Eficiência de custos** -- Zero taxas de egresso para transferência de dados pela infraestrutura da Azion -- Preços previsíveis sem cobranças ocultas de bandwidth + Acesse [Azion Console](https://console.azion.com/) > **Connectors**. -**Unificação de plataforma** -- Build, secure, store e observe em um ambiente integrado -- APIs e padrões de configuração consistentes em todas as capacidades -- Plataforma única para aplicações, functions, storage, databases e segurança + + + -:::note -Se sua conta está sob o suporte **Business** ou superior, você tem acesso a especialistas por meio dos [Integration Services](/pt-br/documentacao/servicos/integration-services/). Para mais informações detalhadas, veja os [Serviços de Suporte da Azion](https://www.azion.com/pt-br/servicos-profissionais/). -::: + Em **Connector Type**, selecione _HTTP_ para um nome de host ou um endereço IP, ou _Object Storage_ para um bucket. + + + + + Em **Address**, insira o endereço da origem. Se a origem responde a um virtual host diferente desse endereço, insira-o em **Host Header**. + + + + + +O connector está pronto para ser definido como origem da aplicação. Para as demais opções de conexão, consulte [Connectors](/pt-br/documentacao/plataforma/connectors/). --- -## Pré-requisitos +## Crie a aplicação -Antes de iniciar a migração, certifique-se de ter o seguinte: +A aplicação guarda as regras, as configurações de cache e as funções que servem o conteúdo. Para partir de um template, abra [Templates e integrações](/pt-br/documentacao/marketplace/visao-geral-templates-e-integracoes/) e faça o deploy de um; o [Azion Starter Kit](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/frameworks/azion-starter-kit/) oferece um projeto básico para explorar a plataforma, e a [lista completa de templates](/pt-br/documentacao/guias/#azion-templates) cobre os frameworks mais comuns. Para partir do seu próprio código, consulte [Criar uma aplicação](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/criar-uma-aplicacao/). -- **Conta Azion**: Crie uma conta gratuita no [Azion Console](https://console.azion.com/). Você precisará de acesso ao Console para criar aplicações e configurar domínios. - +Para rotear a aplicação para o connector: -- **Azion CLI** (opcional, mas recomendado): Instale a CLI para desenvolvimento local e deploy. A CLI oferece um fluxo de trabalho simplificado para construir, testar e implantar aplicações. - + + ---- + Acesse [Azion Console](https://console.azion.com/) > **Applications** > **sua aplicação**. -## Antes de começar + + + -Antes de migrar aplicações para a Azion, existem duas variáveis principais que devem existir: + Edite a regra padrão ou adicione uma regra para a fase de requisição. -1. **Connector**: o servidor de origem da aplicação. Este ponto de entrada assume a forma de um host, um endereço IPv4 ou IPv6 de um serviço de armazenamento ou uma aplicação existente. - + + -2. **Workload**: o domínio alvo da aplicação. Esta saída assume a forma de um domínio Azion, que pode ser apontado para um domínio personalizado. - + Em **Criteria**, defina **If `${uri}` starts with `/`**, para que a regra cubra toda a aplicação. -A maioria das aplicações precisa de um connector do qual a Azion recupera o conteúdo e o código que as compõem. Essa aplicação passa pelos pontos de presença globais da Azion para ser entregue aos usuários através de um domínio associado a um workload. + + - + Em **Behavior**, selecione **Set Connector** e selecione o connector. + + + + + +As requisições que chegam à aplicação agora são buscadas no connector. Para as demais configurações, consulte [Applications](/pt-br/documentacao/plataforma/applications/). --- -## Passo 1: Crie uma application +## Exponha a aplicação em um workload -Você pode começar criando uma application usando um template básico. Uma opção recomendada é o template [Azion Starter Kit](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/frameworks/azion-starter-kit/), que ajuda a criar uma stack de edge básica para explorar a plataforma. +Um workload dá à aplicação o seu domínio Azion e recebe o domínio personalizado depois. Para criá-lo: - + + -Veja a [lista completa de templates disponíveis](/pt-br/documentacao/guias/#azion-templates). + Acesse [Azion Console](https://console.azion.com/) > **Workloads**. ---- + + + -## Passo 2: Teste localmente + Insira um **Name**. Em **Infrastructure**, selecione _Production_. Essa escolha não pode ser alterada depois que o workload é salvo. -Antes de implantar a aplicação, a recomendação é [fazer o staging da aplicação através do arquivo hosts](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/testar-edge-application-atraves-do-arquivo-hosts/) para garantir que tudo está funcionando corretamente. Este passo ajuda a identificar e resolver quaisquer erros de configuração ou problemas causados pela migração. + + ---- + Em **Subdomain** e **Domain**, insira o nome de host ao qual a aplicação responde. Por exemplo: `www` e `example.com`. -## Passo 3: Aponte o domínio para um workload + + -O passo final para migrar totalmente sua aplicação para a Azion é apontar seu domínio personalizado para o workload da Azion. Ao fazer isso, você permite que os usuários acessem sua application através de seu domínio, reduzindo a latência e os custos de processamento na origem. + Em **Applications**, selecione a aplicação. - + + + + Em **Firewall**, selecione o firewall que protege a aplicação. + + + + + Em **Digital Certificate**, selecione o certificado do domínio, ou o certificado SAN da Azion para usar o domínio do workload. + + + + + +A Azion gera o domínio do workload, no formato `xxxxxxxxxx.map.azionedge.net`. É o endereço para o qual o domínio personalizado vai apontar. --- -## Após a migração +## Teste a aplicação antes de mover o domínio + +Enquanto o DNS público ainda aponta para o provedor atual, o seu computador pode alcançar a aplicação na Azion pelo arquivo `hosts`. É aqui que um erro de configuração da migração aparece antes que qualquer usuário o veja. Para fazer o staging da aplicação: + +1. Resolva o domínio do workload para encontrar os endereços que o servem: + + -Depois que sua aplicação estiver rodando na Azion, configure estas funcionalidades essenciais: + A resposta lista o domínio e um ou mais endereços: -### Configure observabilidade + ```bash + xxxxxxxxxx.map.azionedge.net has address 200.0.0.0 + ``` -Monitore a performance e o comportamento da sua aplicação em tempo real: +2. No arquivo `hosts` do seu computador, adicione uma linha que mapeia o domínio personalizado para um desses endereços. +3. Abra o domínio personalizado em uma janela privada do navegador, para que uma resposta de DNS em cache não leve você ao provedor atual. -- **[Real-Time Metrics](/pt-br/documentacao/plataforma/real-time-metrics/)** — Visualize requisições, bandwidth, latência e taxas de cache hit através de dashboards e GraphQL API -- **[Real-Time Events](/pt-br/documentacao/observe/real-time-events/)** — Acesse logs detalhados de requisições, functions, eventos de WAF e mais para troubleshooting +A aplicação carrega da Azion sob o seu próprio domínio. Para a localização do arquivo `hosts` em cada sistema operacional, consulte [Faça staging de uma app pelo arquivo hosts](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/testar-edge-application-atraves-do-arquivo-hosts/). -### Habilite funcionalidades de segurança +--- + +## Aponte o domínio para o workload + +A mudança de DNS é a virada: quando o domínio passa a resolver para o workload, os usuários alcançam a aplicação pela Azion. Para apontar o domínio: + +1. Faça login no seu provedor de DNS e abra os registros do domínio. +2. Crie ou edite o registro CNAME do subdomínio, apontando-o para o domínio do workload: -Proteja sua aplicação com as capacidades de segurança da Azion: + | Name | Value | Type | + | --- | --- | --- | + | `www` | `xxxxxxxxxx.map.azionedge.net` | CNAME | -- **[Web Application Firewall](/pt-br/documentacao/secure/waf/)** — Proteção contra SQL injection, XSS e outros ataques de camada de aplicação -- **[DDoS Protection](/pt-br/documentacao/plataforma/ddos-protection/)** — Proteção automática contra ataques volumétricos e de protocolo +3. Salve o registro. -### Continue aprendendo +Mudanças de DNS levam tempo para propagar. Para verificar o que os resolvers respondem, consulte [Encontre servidores DNS com o comando DIG](/pt-br/documentacao/guias/seguranca-de-aplicacoes/dns/executar-o-comando-dig/). + +:::note[nota] +Nem todo provedor aceita um registro CNAME no ápice do domínio. Para apontar o ápice, [migre os nameservers para a Azion](/pt-br/documentacao/guias/plataforma/migracao/migrar-ns-para-a-azion/). Para as configurações do domínio personalizado no Console, consulte [Como apontar um domínio para a Azion](/pt-br/documentacao/guias/plataforma/migracao/apontar-dominio-para-a-azion/). +::: + +--- -Explore a documentação para aproveitar ao máximo a Azion Web Platform: +## Próximos passos -- [Documentação de Applications](/pt-br/documentacao/plataforma/applications/) -- [Documentação de Functions](/pt-br/documentacao/build/functions/) -- [Documentação de Rules Engine](/pt-br/documentacao/plataforma/applications/rules-engine/) + + + + + + + + diff --git a/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/templates-e-integracoes/usar-um-template-via-rtm.mdx b/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/templates-e-integracoes/usar-um-template-via-rtm.mdx index 7ff139857a..5d4c8cb9c3 100644 --- a/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/templates-e-integracoes/usar-um-template-via-rtm.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/recursos-adicionais/templates-e-integracoes/usar-um-template-via-rtm.mdx @@ -64,7 +64,7 @@ Após a implantação, cada template cria uma nova application e seu domínio Az Vá para a [página de guias](/pt-br/documentacao/guias/#azion-templates) e verifique mais detalhes sobre o template específico que você quer usar. :::tip[dica] -Para saber mais sobre como editar e personalizar as configurações principais de sua aplicação, acesse o guia sobre [configuração](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/definir-configuracoes-principais/) das applications. Você também pode [rodar na rede da Azion](/pt-br/documentacao/produtos/ative-em-producao/), adicionando um domínio personalizado e direcionando seu tráfego. +Para saber mais sobre como editar e personalizar as configurações principais de sua aplicação, acesse o guia sobre [configuração](/pt-br/documentacao/guias/desenvolvimento-de-aplicacoes/primeiros-passos/definir-configuracoes-principais/) das applications. Você também pode [rodar na rede da Azion](/pt-br/documentacao/fundamentos/), adicionando um domínio personalizado e direcionando seu tráfego. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/account-lockout-policy.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/account-lockout-policy.mdx index a9cdbe822c..a7a06fc867 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/account-lockout-policy.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/account-lockout-policy.mdx @@ -1,5 +1,5 @@ --- -title: Account Lockout Policy +title: Política de bloqueio de conta description: O recurso de Account Lockout Policy protege contas contra acesso não autorizado, incluindo ataques de força bruta. meta_tags: account management, security, brute force attacks, Azion Account Lockout Policy, política de bloqueio de conta namespace: documentation_products_account_lockout_policy @@ -23,7 +23,7 @@ Ao implementar a **Account Lockout Policy**, você pode: - Autorizar manualmente um usuário bloqueado a fazer login novamente antes de completar o período de bloqueio, em casos excepcionais. - Monitorar as tentativas de acesso não autorizado e tome as ações necessárias. -:::note +:::note[nota] Quando uma organização configura a Account Lockout Policy, a política se aplica a todos os níveis de conta. Este recurso está disponível por padrão para clientes com o [suporte](https://www.azion.com/pt-br/servicos-profissionais/) **Enterprise** e **Mission Critical**. @@ -43,7 +43,7 @@ Este recurso está disponível por padrão para clientes com o [suporte](https:/ ## Principais configurações -:::note +:::note[nota] Para configurar a Account Lockout Policy, você deve ter privilégios de *Account Owner*. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/activity-history.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/activity-history.mdx index 5dab88b575..c3d16bee3e 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/activity-history.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/activity-history.mdx @@ -1,5 +1,5 @@ --- -title: Activity History +title: Histórico de atividades description: >- Na Azion, você pode acessar o histórico de todas as atividades realizadas na conta por todos os usuários conectados a ela desde a criação da conta. diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/clientes.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/clientes.mdx index 4d08f9a40f..f59badff35 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/clientes.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/clientes.mdx @@ -14,7 +14,7 @@ Você precisa ser **Account owner** ou ter as permissões **View client list** e Dessa forma, este recurso proporciona a gestão independente das contas do grupo, com Account Owners diferentes, para agilizar ainda mais os seus processos do dia a dia. -:::note +:::note[nota] A funcionalidade Clients está disponível apenas para contas do tipo Groups. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/configuracoes-conta.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/configuracoes-conta.mdx index eca6190654..e324de3f08 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/configuracoes-conta.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/configuracoes-conta.mdx @@ -12,7 +12,7 @@ A página de **Account Settings** permite que você gerencie e personalize as in Para editar suas informações pessoais, abra o **Account menu**, localizado no menu superior direito da plataforma da Azion e selecione a opção **Your Settings**. -:::note +:::note[nota] Apenas o *Account Owner* pode editar a parte de **Authentication Settings** e excluir a conta. ::: @@ -55,7 +55,7 @@ Os campos de endereço são relacionados aos dados de faturamento: Se você é o dono da conta (*Account Owner*), você pode ativar e desativar a funcionalidade de **Social Login** utilizando o switch. Quando ativado, os usuários conectados à conta podem se autenticar na plataforma da Azion usando as redes sociais disponíveis. Do contrário, eles terão que fazer login utilizando email e senha. Veja mais sobre o assunto na página de [Social Login](/pt-br/documentacao/fundamentos/social-login/) -:::note +:::note[nota] Ao ativar o **Social Login**, ele será aplicado a todos os usuários da conta. ::: @@ -67,7 +67,7 @@ Atualmente, a Azion disponibiliza Social Login com contas do GitHub e do Google. O **Multi-Factor Authentication (MFA)** fornece um nível extra de segurança para proteger as credenciais dos usuários. Apenas o dono da conta (*Account Owner*) pode ativar essas configurações. -:::note +:::note[nota] Ao ativar o MFA, ele será obrigatório para todos os usuário da conta, com exceção do **Account owner**. ::: @@ -83,7 +83,7 @@ Apenas o dono da conta (*Account Owner*) pode excluí-la. Se tiver privilégios Após excluir com sucesso sua conta, você receberá um email confirmando a exclusão. Caso queira dar um feedback sobre sua experiência com a Azion, contate a equipe por [esse email](mailto:feedback@azion.com). -:::note +:::note[nota] Seus dados de conta permanecem armazenados e disponíveis para futuras verificações. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/contas-equipes-e-usuarios.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/contas-equipes-e-usuarios.mdx new file mode 100644 index 0000000000..083b8f564a --- /dev/null +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/contas-equipes-e-usuarios.mdx @@ -0,0 +1,64 @@ +--- +title: Contas, equipes e usuários +description: >- + Entenda onde cada configuração vive na Azion: seu perfil de usuário, a conta, + as contas de clientes de um grupo e as equipes que concedem permissões. +meta_tags: >- + account, account owner, users, teams, permissions, client accounts, group account, personal token, activity history, multi-factor authentication +namespace: documentation_fundamentals_accounts_teams_users +permalink: /documentacao/fundamentos/contas-equipes-e-usuarios/ +--- + +import FrameBox from '@aziontech/webkit/frame-box' +import ItemList from '@aziontech/webkit/item-list' +import DocItem from '@aziontech/webkit/doc-item' + +Tudo o que você constrói na Azion vive dentro de uma conta, e cada pessoa que trabalha nela entra como um usuário dessa conta. O que uma pessoa pode ver e alterar é decidido por três coisas que se encaixam uma dentro da outra: o próprio perfil de usuário, a conta e seu proprietário, e as equipes em que o proprietário a coloca. Uma conta do tipo Group acrescenta um nível, as contas de clientes das suas afiliadas, cada uma com o próprio proprietário. Esta página cobre o perfil de usuário, a conta, as contas de clientes, as equipes e permissões e os personal tokens que alcançam a conta de fora de Azion Console. + +--- + +## Perfil de usuário + +Um perfil de usuário guarda o que pertence a uma pessoa: nome e sobrenome, o fuso horário que define a hora exibida em páginas como o histórico de atividades, o e-mail usado para entrar, um número de telefone e a senha. O idioma da interface é o inglês e não pode ser alterado. Quando você altera o e-mail, a Azion envia uma confirmação para o novo endereço, e a alteração só vale depois que você confirma. A partir do próximo login você usa o novo e-mail, mesmo pelo Social Login, e o endereço anterior fica livre para uma nova conta. + +A autenticação multifator (MFA) tem um lado pessoal e um lado da conta. Quando a conta não exige MFA e seu usuário tem a permissão, você pode ativá-la para o seu próprio login. Quando a conta já a exige, a opção fica bloqueada para você, porque o proprietário da conta decidiu por todos. Para os campos, consulte [Suas configurações](/pt-br/documentacao/fundamentos/your-settings/). + +## A conta + +A conta é o contêiner: ela é dona dos recursos que você implanta, dos usuários e equipes que trabalham neles, do perfil de faturamento e dos controles de segurança que se aplicam a cada login. O perfil da conta carrega o ID, o nome da conta, a razão social e seu identificador único, e os e-mails de faturamento, com até 256 caracteres separados por ponto e vírgula. Os campos de endereço são obrigatórios, porque pertencem à conta de faturamento, e uma alteração na página só é salva quando todos estão preenchidos. + +Um usuário é o *Account Owner*. Só o proprietário pode alterar as configurações de autenticação e excluir a conta. Ativar o Social Login permite que todo usuário da conta entre com GitHub ou Google. Exigir MFA a torna obrigatória para todo usuário, exceto o proprietário. O custo é o alcance: exigir MFA na conta protege todos de uma vez, enquanto deixar a decisão para cada usuário protege só quem a ativa. Depois que o proprietário exclui a conta, a Azion envia um e-mail confirmando a exclusão e mantém as informações da conta, e uma nova conta pode ser criada a qualquer momento. + +Toda ação feita na conta por qualquer usuário é registrada no histórico de atividades pelos últimos 30 dias, com o usuário que a executou, e registros mais antigos estão disponíveis com a equipe de suporte. O mesmo registro pode ser enviado às suas próprias ferramentas pelo Data Stream. Para os campos, consulte [Configurações de conta](/pt-br/documentacao/fundamentos/account-settings/) e [Histórico de atividades](/pt-br/documentacao/fundamentos/activity-history/). + +## Contas de clientes + +Uma conta do tipo *Group* pode criar contas separadas, chamadas *Clients*, para cada afiliada do grupo. Cada conta de cliente tem o próprio Account Owner, o próprio endereço e e-mails de faturamento, e é gerenciada de forma independente dentro do grupo. Criar um cliente exige o Account Owner do grupo ou as permissões **View client list** e **Change clients**. + +Quando o cliente é cadastrado, o proprietário recebe um e-mail de ativação válido por 14 dias. Se a conta não for ativada nesse período, o proprietário é removido da plataforma. Um interruptor **Active Client** em cada cliente liga ou desliga sua operação sem excluí-lo. Para os campos, consulte [Contas](/pt-br/documentacao/fundamentos/contas/). + +## Equipes e permissões + +As permissões são concedidas a equipes, nunca a um usuário diretamente. O Account Owner cria as equipes e define o que cada uma pode ver ou alterar; todo outro usuário é um não proprietário cujo acesso é a soma das equipes a que pertence. Proprietários têm acesso a toda configuração e a toda equipe sem precisar estar em uma. As permissões vêm em pares: uma permissão **Edit** sempre exige a permissão **View** correspondente, e alguns pares exigem uma terceira, como **View Bills** para as permissões de faturamento. + +Um usuário em mais de uma equipe recebe as permissões de todas elas, e esse é o custo do modelo: um conjunto maior de equipes significa menos páginas bloqueadas e mais configurações ao alcance. Por exemplo, uma equipe com **View Applications** mas sem **Edit Applications** pode auditar a configuração de toda aplicação e não alterar nenhuma, e um usuário que abre uma página sem a permissão necessária recebe uma página de erro *403 Forbidden*. Adicionar usuários exige o Account Owner ou as permissões **View Users** e **Edit Users**, e cada novo usuário é criado com um perfil, um fuso horário e as equipes a que pertence. Para a tabela completa de permissões, consulte [Permissões de equipes](/pt-br/documentacao/fundamentos/teams-permissions/); para adicionar e remover usuários, consulte [Gerenciamento de usuários](/pt-br/documentacao/fundamentos/users-management/). + +## Personal tokens + +Um personal token é uma sequência de caracteres que autentica seu usuário fora de Azion Console, na [Azion API](https://api.azion.com/) e na [Azion CLI](/pt-br/documentacao/devtools/cli/). Você o cria com um nome, uma descrição opcional e uma validade de 1, 7, 15, 30 ou 90 dias, 1 ano ou uma data personalizada. O token é exibido uma única vez, quando você o cria, e não pode ser visto, copiado nem modificado depois; a lista mostra só o escopo, a data da última modificação e a data de expiração. Trate-o como uma senha: um token de longa duração é prático para automação e exige o mesmo cuidado que a credencial que ele substitui. Para os campos, consulte [Tokens pessoais](/pt-br/documentacao/fundamentos/personal-tokens/). + +--- + +## Recursos relacionados + + + + O perfil da conta, o endereço, as configurações de autenticação e a exclusão. + Os campos do seu perfil de usuário, informações de contato e configurações de segurança. + Toda permissão que uma equipe pode conceder e o que ela libera. + Adicione, edite e remova os usuários da conta. + Crie contas de clientes para as afiliadas de uma conta do tipo Group. + Configure um aplicativo autenticador para o seu login. + Entre pelo seu próprio provedor de identidade. + + diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/multi-factor-authentication.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/multi-factor-authentication.mdx index ea2c7a2869..bff336989f 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/multi-factor-authentication.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/multi-factor-authentication.mdx @@ -1,5 +1,5 @@ --- -title: Multi-Factor Authentication +title: Autenticação multifator description: >- Multi-Factor Authentication (MFA) é um método eletrônico de verificação usado para proteger acessos de login. @@ -17,7 +17,7 @@ Vantagens de ativar MFA em sua conta: Antes de ativar essa configuração na Azion, certifique-se de que seu dispositivo móvel seja compatível com um aplicativo MFA, como o Google Authenticator ou o Microsoft Authenticator, disponíveis na App Store no iOS, Google Play no Android ou outras lojas de aplicativos. -:::note +:::note[nota] A ativação do MFA é opcional, mas altamente recomendada para maior segurança da conta. Os usuários são incentivados a habilitar o MFA, especialmente aqueles com privilégios de acesso elevados. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/personal-tokens.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/personal-tokens.mdx index 21ae3dfa4d..2788c2c184 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/personal-tokens.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/personal-tokens.mdx @@ -1,9 +1,8 @@ --- -title: Personal Tokens +title: Tokens pessoais description: >- - Você pode criar um Personal Token de autenticação de longa duração na Azion - para chamar as APIs da Azion ou para executar comandos na command-line - interface (CLI). + Crie um personal token de longa duração para chamar as APIs da Azion ou + executar comandos na Azion CLI. meta_tags: personal token namespace: documentation_personal_tokens permalink: /documentacao/fundamentos/personal-tokens/ diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/social-login.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/social-login.mdx index f995a8e64b..020c955723 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/social-login.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/social-login.mdx @@ -1,9 +1,8 @@ --- -title: Social Login +title: Login social description: >- - O Social Login é uma forma de login único que usa informações existentes de - uma rede social para entrar em sites de terceiros sem que haja a necessidade - de criar uma nova conta de login. + Entre na Azion com sua conta do GitHub ou do Google, sem uma senha separada, + quando o Social Login está ativado na conta. meta_tags: 'social login, contas, autenticação de usuários' namespace: documentation_accounts_social_login permalink: /documentacao/fundamentos/social-login/ @@ -20,7 +19,7 @@ O **Social Login** pode trazer diversas vantagens, como, por exemplo: Além disso, ele ajuda a evitar que usuários forneçam dados falsos ou esqueçam suas informações de login. -:::note +:::note[nota] Atualmente, a Azion permite que o Social Login seja feito com contas GitHub e Google. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx index 8307a62b1f..2e7ece4f5e 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/teams-permissions.mdx @@ -1,5 +1,5 @@ --- -title: Teams Permissions +title: Permissões de equipes description: >- Na página Team Permissions, você pode criar e gerenciar equipes, controlar e configurar direitos de acesso para equipes distintas em sua empresa. diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/user-session-timeout.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/user-session-timeout.mdx index 710033c89f..fba390105b 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/user-session-timeout.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/user-session-timeout.mdx @@ -1,5 +1,5 @@ --- -title: User Session Timeout +title: Tempo limite de sessão do usuário description: O recurso User Session Timeout permite que você defina um tempo máximo de sessão para os usuários em sua organização. meta_tags: gerenciamento de contas, Azion User Session Timeout, políticas de segurança namespace: documentation_products_user_session_timeout @@ -18,7 +18,7 @@ Ao usar esse recurso, você pode: - Configurar um tempo máximo de inatividade e timeout de sessão para atender às políticas de conformidade e segurança. - Garantir que as sessões e os dados dos usuários estejam protegidos. -:::note +:::note[nota] Quando uma organização configura o User Session Timeout, a política se aplica a todos os níveis de conta. Este recurso está disponível para clientes de todos os [Serviços de Suporte da Azion](https://www.azion.com/pt-br/servicos-profissionais/). @@ -34,7 +34,7 @@ Este recurso está disponível para clientes de todos os [Serviços de Suporte d ## Principais configurações -:::note +:::note[nota] Para configurar o User Session Timeout, você deve ter privilégios de *Account Owner*. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/users-management.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/users-management.mdx index 428b79f698..d526c57e71 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/users-management.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/users-management.mdx @@ -1,5 +1,5 @@ --- -title: Users Management +title: Gerenciamento de usuários description: >- Nesta documentação, você encontra orientações sobre como gerenciar usuários na Azion. @@ -52,7 +52,7 @@ Quando essa função estiver desativada, o usuário será definido como não pro - **Teams**: times têm diferentes permissões de acesso. Portanto, você deve selecionar um time para alocar não proprietários, ao contrário dos proprietários de conta, que têm permissão para acessar todas as equipes. -:::note +:::note[nota] As permissões de acesso de não proprietários dependem das permissões concedidas ao time em que estão alocados. ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/your-settings.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/your-settings.mdx index ddd25e8400..3eac17be02 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/contas/your-settings.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/contas/your-settings.mdx @@ -1,5 +1,5 @@ --- -title: Your Settings +title: Suas configurações description: 'Na página Your Settings, você pode editar suas informações pessoais na Azion.' meta_tags: 'edge computing, azion, account, your settings, security settings' namespace: documentation_accounts_your_settings @@ -8,7 +8,7 @@ permalink: /documentacao/fundamentos/your-settings/ Na página **Your Settings**, você pode editar e gerenciar suas informações pessoais, preferências e configurações de segurança na platforma da Azion. -Para saber sobre as informações gerais da conta, confira a documentação de [Account Settings](/pt-br/documentacao/fundamentos/account-settings/). +Para saber sobre as informações gerais da conta, confira a documentação de [Configurações de conta](/pt-br/documentacao/fundamentos/account-settings/). --- @@ -18,7 +18,7 @@ Para saber sobre as informações gerais da conta, confira a documentação de [ - **Last name** (obrigatório): sobrenome pelo qual você quer se identificar. Você pode editar o sobrenome como preferir. - **Timezone** (obrigatório): o fuso horário que você quer usar nos dados da Azion. Você pode editar de acordo com as suas preferências. O fuso horário será modificado na interface em páginas como a de **Activity History**. -:::note +:::note[nota] **Language**: a plataforma da Azion está disponível apenas em inglês. Não é possível editar este campo. ::: @@ -28,7 +28,7 @@ Para saber sobre as informações gerais da conta, confira a documentação de [ - **Email** (obrigatório): email utilizado para logar em sua conta na Azion. -:::note +:::note[nota] Ao editar esse campo, um email de confirmação é enviado para o novo endereço de email. Você precisa confirmar o email para que as mudanças sejam feitas. Em seu próximo login, você deverá usar o novo email, mesmo que você utilize o Login Social. Seu email anterior ficará disponível para ser usado em uma nova conta. ::: @@ -41,6 +41,6 @@ Ao editar esse campo, um email de confirmação é enviado para o novo endereço - **Password**: a senha utilizada para logar na plataforma da Azion. Você pode redefini-la a qualquer momento. - **Multi-Factor Authentication (MFA)**: camada extra de segurança que você pode ativar em sua conta. -:::note +:::note[nota] Se a conta principal não tiver MFA ativado e seu usuário tiver permissão, você pode ativá-lo apenas para uso em seu login. No entanto, se já estiver ativado, você não poderá editar essa opção. Veja mais informações na documentação de [Multi-Factor Authentication](/pt-br/documentacao/fundamentos/multi-factor-authentication/). ::: diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx index b1884fdb11..fc7b6a936f 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/api-v4-migration.mdx @@ -28,7 +28,7 @@ A API v4 da Azion já está disponível em `Preview` para novas contas do suport A API v4 representa um avanço tecnológico, fornecendo a base para futuras funcionalidades e maior eficiência operacional em toda a Azion Web Platform. -:::note +:::note[nota] As alterações descritas neste documento serão aplicadas à sua conta somente após a migração da sua conta. ::: @@ -84,7 +84,7 @@ Com a introdução dos Workloads, as métricas de **Requests** e **Data Transfer | Requests | Medidas por Application | Medidas por Workload | | Data Transfer | Medidas por Application | Medidas por Workload | -:::tip +:::tip[dica] Após a migração, você verá as métricas de Requests e Data Transfer no dashboard e nos relatórios de faturamento do seu Workload. Os valores medidos permanecem os mesmos de antes da migração. ::: @@ -109,13 +109,13 @@ O modelo de mensuração de requests do Firewall foi atualizado: |---------|--------|--------| | Firewall Requests | Apenas firewalls com Network Shield habilitado | Todos os firewalls (todas as requests que passam) | -- **API v3**: Requests do Firewall eram mensuradas apenas para firewalls com o módulo Network Shield habilitado. +- **API v3**: Requests do Firewall eram mensuradas apenas para firewalls com Network Shield habilitado. - **API v4**: O Firewall mede todas as requests que passam por ele, incluindo: - Requests processadas pelo WAF - Requests processadas pelo Network Shield - Todas as requests que transitam pelo Firewall -:::note +:::note[nota] Essa abordagem consolidada significa que você pode ver um aumento na contagem de requests do Firewall após a migração, pois todas as requests que passam por qualquer Firewall agora são medidas, não apenas aquelas com Network Shield habilitado. ::: @@ -128,9 +128,9 @@ Com a introdução dos Connectors na API v4, uma nova métrica de cobrança est | Shielded Connectors | Não disponível | Número de Connectors com Origin Shield habilitado | - **API v3**: Origin Shield estava disponível como um Add-On separado com uma Subscription. Nenhum Shielded Connector era medido. -- **API v4**: Connectors com o módulo Origin Shield habilitado são contabilizados como Shielded Connectors e aparecem nos seus relatórios de faturamento. +- **API v4**: Connectors com Origin Shield habilitado são contabilizados como Shielded Connectors e aparecem nos seus relatórios de faturamento. -:::tip +:::tip[dica] Esta é uma nova métrica. Se você habilitar Origin Shield nos seus Connectors, verá Shielded Connectors nos seus relatórios de faturamento após a migração. ::: @@ -184,7 +184,7 @@ Na API v3, **Domains** eram um recurso único que conectava uma Application ao t | Deletar | `DELETE /domains/{domain_id}` | `DELETE /workspace/workloads/{workload_id}` | | Vincular à Application | Incorporado na criação do Domain | `POST /workspace/workloads/{workload_id}/deployments` | -#### Payload de Requisição: Criar Domain/Workload +#### Payload de requisição para criar um workload **API v3 (Domains):** @@ -223,7 +223,7 @@ Na API v3, **Domains** eram um recurso único que conectava uma Application ao t } ``` -#### Payload de Requisição: Vincular à Application (Deployment) +#### Payload de requisição para vincular a uma application **API v3:** A vinculação ocorre automaticamente durante a criação do Domain através do campo `edge_application_id`. @@ -313,7 +313,7 @@ Na API v3, **Origins** eram recursos aninhados sob Applications. Na API v4, **Co | Atualizar | `PATCH /edge_applications/{app_id}/origins/{origin_key}` | `PATCH /edge_connector/connectors/{connector_id}` | | Deletar | `DELETE /edge_applications/{app_id}/origins/{origin_key}` | `DELETE /edge_connector/connectors/{connector_id}` | -#### Payload de Requisição: Criar Origin/Connector +#### Payload de requisição para criar um connector **API v3 (Origins - Single Origin):** @@ -467,12 +467,12 @@ Na API v3, **Origins** eram recursos aninhados sob Applications. Na API v4, **Co |---------|--------|--------| | Escopo do recurso | Aninhado sob Application | Recurso independente de nível superior | | Reutilização | Uma Origin por Application | Um Connector pode servir múltiplas Applications | -| Distinção de tipo | `origin_type: "single_origin"` ou `"load_balancer"` | `type: "http"` com módulo `load_balancer` habilitado para múltiplos endereços | +| Distinção de tipo | `origin_type: "single_origin"` ou `"load_balancer"` | `type: "http"` com `load_balancer` habilitado para múltiplos endereços | | Política de protocolo | `origin_protocol_policy` | `connection_options.transport_policy` | | Host header | `host_header` | `connection_options.host` | | Path | `origin_path` | `connection_options.path_prefix` | | Timeouts | `connection_timeout`, `timeout_between_bytes` | `modules.load_balancer.config.connection_timeout`, `read_write_timeout` | -| HMAC Auth | Campos diretos na Origin | Requer módulo `origin_shield` | +| HMAC Auth | Campos diretos na Origin | Requer `origin_shield` habilitado | | Portas | Não configuráveis | `http_port`, `https_port` por endereço | | Identificador | `origin_key` usado para updates | `id` usado para todas as operações | @@ -866,11 +866,11 @@ Ao utilizar o Console, essa associação é criada automaticamente ao selecionar }' `} /> -:::tip +:::tip[dica] Para mais informações sobre os parâmetros da API, visite a [referência da API de Workloads](https://api.azion.com/v4#/operations/GetWorkspaceWorkloads). ::: -### O que acontece com meus Domains existentes? +### Domains existentes Os Domains serão automaticamente convertidos em Workloads em fases, garantindo compatibilidade com as configurações originais. A migração ocorrerá em ondas. @@ -921,11 +921,11 @@ Todas as configurações anteriormente gerenciadas na aba **Origins** das Applic - **Connector Type** - *Comportamento anterior*: As opções incluíam `Single Origin` e `Load Balancer`. Isso definia se era possível configurar uma ou múltiplas origens. - - *Novo comportamento*: Os tipos `Single Origin` e `Load Balancer` foram unificados no tipo `HTTP`. Ao usar múltiplas origens, é necessário habilitar o **Load Balancer Module** para adicionar mais origens. + - *Novo comportamento*: Os tipos `Single Origin` e `Load Balancer` foram unificados no tipo `HTTP`. Ao usar múltiplas origens, é necessário habilitar **Load Balancer** para adicionar mais origens. - **HMAC Authentication** - *Comportamento anterior*: Disponível ao configurar uma Origin. - - *Novo comportamento*: Agora é necessário habilitar o **Origin Shield Module** ao configurar um connector do tipo `HTTP`. + - *Novo comportamento*: É necessário habilitar **Origin Shield** ao configurar um connector do tipo `HTTP`. - **Timeouts** - *Comportamento anterior*: `Connection Timeout` e `Between Bytes Timeout` tinham valores fixos. @@ -1000,11 +1000,11 @@ Você pode gerenciar **Connectors** e suas configurações pela API utilizando o }' `} /> -:::tip +:::tip[dica] Para mais informações sobre os parâmetros da API, visite a [referência da API de Connectors](https://api.azion.com/v4#/operations/GetEdgeConnectorConnectors). ::: -### O que acontece com meus Origins existentes? +### Origins existentes As Origins existentes serão migradas de acordo com um cronograma, que será comunicado para cada caso. A migração ocorrerá em fases. @@ -1111,11 +1111,11 @@ Para utilizar uma **Custom Page**, é necessário vinculá-la a um **Workload** }' `} /> -:::tip +:::tip[dica] Para mais informações sobre os parâmetros da API, visite a [referência da API de Custom Pages](https://api.azion.com/v4#/operations/GetWorkspaceCustomPages). ::: -### O que acontece com meus Error Responses existentes? +### Error Responses existentes Os Error Responses existentes serão automaticamente convertidos em **Custom Pages** em fases, mantendo a compatibilidade com as configurações originais. A migração ocorrerá em ondas. @@ -1158,14 +1158,14 @@ Aqui estão ações recomendadas para garantir uma migração tranquila: ## Perguntas e Respostas -### Como posso testar as novas funcionalidades? +### Testar as novas funcionalidades Novas contas Developer terão acesso aos recursos atualizados. Para avaliar essas funcionalidades, você pode criar uma conta pessoal que não esteja associada à conta da sua organização. Isso permite testar as novas funcionalidades de forma independente. -### Preciso fazer alguma coisa? +### Ações necessárias A maioria dos usuários não precisará tomar nenhuma ação, pois o processo de migração é automático e preserva as configurações existentes. No entanto, se você utiliza automações personalizadas, scripts ou pipelines de CI/CD que interagem com os endpoints antigos da API, será necessário atualizá-los para utilizar os novos endpoints da v4. Revise suas integrações para garantir a compatibilidade após a migração. -## O que devo fazer se precisar de assistência? +## Assistência Você pode entrar em contato com nossa [equipe de suporte](/pt-br/documentacao/suporte/#canais-de-atendimento) ou perguntar diretamente ao [Azion Copilot](https://console.azion.com/copilot). diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx index 4f6c395336..1ea90b7140 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/secure/edge-firewall/web-application-firewall/web-application-firewall.mdx @@ -90,7 +90,7 @@ Um rule set que nenhuma regra nomeia nunca é executado, por mais cuidadosamente - **O que uma requisição bloqueada recebe**: `400` e a página de erro padrão da Azion. Nada nessa resposta nomeia o WAF, a regra que correspondeu ou o score, portanto um bloqueio é identificado pelo header `x-azion-request-id` nela e consultado depois. - **Exceções**: uma exceção isenta uma parte de uma requisição de uma regra interna, ou de todas elas, sem baixar a sensibilidade para o resto do tráfego. O Azion Console chama o objeto de allowed rule. Para cada campo e todas as quinze match zones, consulte [WAF Exceptions](/pt-br/documentacao/secure/waf/custom-allowed-rules/). - **Interfaces**: você cria e gerencia rule sets e exceções no **Azion Console**, que lista rule sets em **WAF Rules**, com a [Azion CLI](/pt-br/documentacao/devtools/cli/) e pela API da Azion em `https://api.azion.com/v4/workspace/wafs`. Para as superfícies de API e de CLI, consulte [WAF Rule Sets](/pt-br/documentacao/secure/waf/rule-sets/) e [WAF Exceptions](/pt-br/documentacao/secure/waf/custom-allowed-rules/). -- **Observabilidade**: uma correspondência não deixa nada na resposta, portanto toda pergunta sobre ela é respondida a partir de uma superfície de reporte. O [Real-Time Metrics](/pt-br/documentacao/plataforma/real-time-metrics/#waf) reporta requisições processadas e requisições bloqueadas ao longo do tempo, o [Real-Time Events](/pt-br/documentacao/observe/real-time-events/) retorna uma linha por requisição com as regras que corresponderam e o score que cada família alcançou, e o [Data Stream](/pt-br/documentacao/observe/data-stream/) envia esses eventos para um sistema fora da Azion. Os mesmos dados de evento são consultados pela [API GraphQL](/pt-br/documentacao/devtools/graphql/visao-geral/), e [Como integrar WAF com SIEMs](/pt-br/documentacao/produtos/secure/automatizar/integrar-siems/) cobre o envio deles para um SIEM. +- **Observabilidade**: uma correspondência não deixa nada na resposta, portanto toda pergunta sobre ela é respondida a partir de uma superfície de reporte. O [Real-Time Metrics](/pt-br/documentacao/plataforma/real-time-metrics/#waf) reporta requisições processadas e requisições bloqueadas ao longo do tempo, o [Real-Time Events](/pt-br/documentacao/observe/real-time-events/) retorna uma linha por requisição com as regras que corresponderam e o score que cada família alcançou, e o [Data Stream](/pt-br/documentacao/observe/data-stream/) envia esses eventos para um sistema fora da Azion. Os mesmos dados de evento são consultados pela [API GraphQL](/pt-br/documentacao/devtools/graphql/visao-geral/), e [Como integrar WAF com SIEMs](/pt-br/documentacao/guias/) cobre o envio deles para um SIEM. - **Limites**: o WAF faz o parsing do corpo de uma requisição em cinco content types, e uma requisição cujo corpo ultrapassa 131.072 bytes, que são 128 KiB, é recusada em vez de inspecionada. Um rule set carrega uma entrada de `thresholds` por família de ameaças, e uma consulta de Tuning alcança uma janela fixa para trás. Para cada limite, a resposta acima dele e o uso que cada plano de serviço inclui, consulte [Limites de WAF](/pt-br/documentacao/secure/waf/limites/). - **Cobrança**: o WAF é cobrado por Requests, Rule Sets e Exceptions. Para a taxa acima da quantidade que um plano inclui, consulte [Preços](/pt-br/documentacao/fundamentos/precos/#web-application-firewall). diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/servicos/http-error-status-codes.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/servicos/http-error-status-codes.mdx index 31b197dd67..f8dd2a1799 100644 --- a/src/content/docs/pt-br/pages/menu-principal/referencia/servicos/http-error-status-codes.mdx +++ b/src/content/docs/pt-br/pages/menu-principal/referencia/servicos/http-error-status-codes.mdx @@ -1,9 +1,9 @@ --- -title: Códigos de Status de Erro HTTP da Azion -description: Estes são os erros mais comuns em servidores web e como resolvê-los. +title: Códigos de status HTTP +description: Os códigos de status HTTP que a Azion retorna quando uma requisição falha, a causa de cada um e como resolver. meta_tags: 'serviços, suporte, documentação, erro de sistema' namespace: documentation_error_status_codes -permalink: /documentacao/suporte/http-error-status-codes/ +permalink: /documentacao/fundamentos/codigos-de-status-http/ --- Ao acessar aplicações hospedadas na Azion Web Platform, você pode encontrar erros HTTP comuns. Esses erros podem estar relacionados a uma requisição inválida, falta de conteúdo, problemas de autenticação ou mau funcionamento de servidores. @@ -23,7 +23,7 @@ Para lhe informar sobre esses erros, você receberá uma mensagem semelhante a e - **Status Code**: o código de status HTTP que indica o tipo específico de erro encontrado, relacionado ao título da página. - **Edge Location**: o data center da Azion que processou sua requisição, identificado pelo código de localização oficial publicado na [Página de Status da Azion](https://status.azion.com). Esse valor é retornado pelo header de resposta `X-Azion-Edge-Location` e está sempre presente, independentemente do modo de debug. -:::note +:::note[nota] O header `X-Azion-Edge-Pop`, que anteriormente aparecia em todas as respostas, agora é retornado somente quando o header `Pragma: azion-debug-cache` é incluído na requisição. Utilize-o para debugging avançado junto com outros headers relacionados ao cache. ::: @@ -31,7 +31,7 @@ Quando o sistema da Azion retorna uma página de erro, a razão pode estar relac --- -## O que significam os erros de sistema da Azion? +## Erros de sistema da Azion Estes são os erros mais comuns em servidores web e como resolvê-los. @@ -154,8 +154,8 @@ Um 500 Internal Server Error geralmente requer ação no servidor para ser corri Se o problema persistir, entre em contato com o proprietário do site para confirmar que o sistema está estável ou falta tratamento de exceção. -:::note -Se você é o proprietário do site e está migrando para a Azion, uma incompatibilidade de protocolo entre sua origem e o Rules Engine pode causar erros 500. Verifique as configurações de **Protocol Policy** em [Connectors](/documentacao/plataforma/connectors/) para garantir que o protocolo usado para se conectar à sua origem corresponde aos requisitos da sua aplicação. +:::note[nota] +Se você é o proprietário do site e está migrando para a Azion, uma incompatibilidade de protocolo entre sua origem e o Rules Engine pode causar erros 500. Verifique as configurações de **Protocol Policy** em [Connectors](/pt-br/documentacao/plataforma/connectors/) para garantir que o protocolo usado para se conectar à sua origem corresponde aos requisitos da sua aplicação. ::: ### 502 Bad Gateway diff --git a/src/content/docs/pt-br/pages/primeiro-deploy/primeiro-deploy.mdx b/src/content/docs/pt-br/pages/primeiro-deploy/primeiro-deploy.mdx index 701524040a..2982fc2e32 100644 --- a/src/content/docs/pt-br/pages/primeiro-deploy/primeiro-deploy.mdx +++ b/src/content/docs/pt-br/pages/primeiro-deploy/primeiro-deploy.mdx @@ -3,7 +3,7 @@ title: Primeiro deploy em poucos minutos description: Ao final deste tutorial, uma aplicação estará no ar na Azion Web Platform, respondendo HTTP 200 no seu próprio domínio Azion. Leva poucos minutos. meta_tags: 'primeiro deploy, primeiros passos, templates, github, cli' namespace: documentation_first_deploy -permalink: /documentacao/primeiro-deploy/ +permalink: /documentacao/fundamentos/primeiro-deploy/ --- import DocCard from '@aziontech/webkit/doc-card'; @@ -34,7 +34,7 @@ Tudo o que você precisa é de uma conta Azion. Você pode criar uma gratuitamen Templates são projetos prontos (e-commerce, blogs, APIs, SSR full-stack) que entram no ar em poucos cliques. Você não precisa de nenhuma ferramenta local. -Alguns templates são integrados a serviços de terceiros, então você pode precisar criar contas, gerar tokens ou ativar produtos Azion antes do deploy. Templates integrados ao GitHub pedem para conectar sua conta: clique em Connect with GitHub quando solicitado e confirme a conexão no pop-up. O guia de cada template lista seus pré-requisitos específicos. +Alguns templates são integrados a serviços de terceiros, então você pode precisar criar contas, gerar tokens ou ativar produtos Azion antes do deploy. Templates integrados ao GitHub pedem para conectar sua conta: selecione Connect with GitHub quando solicitado e confirme a conexão na janela que se abre. O guia de cada template lista seus pré-requisitos específicos. @@ -58,7 +58,7 @@ curl -I https:// Abra a mesma URL no navegador para ver sua aplicação rodando. -URLs novas podem levar alguns minutos para se propagar até as edge locations da Azion. Se você receber um erro logo após o deploy, aguarde um momento e tente de novo. +URLs novas podem levar alguns minutos para se propagar até os data centers da Azion. Se você receber um erro logo após o deploy, aguarde um momento e tente de novo. ## Importe um projeto do GitHub @@ -85,7 +85,7 @@ curl -I https:// # HTTP/2 200 ``` -Abra o domínio Azion no navegador para ver sua aplicação rodando. Se você receber um erro de imediato, aguarde alguns minutos: URLs novas levam um momento para se propagar até as edge locations da Azion. +Abra o domínio Azion no navegador para ver sua aplicação rodando. Se você receber um erro de imediato, aguarde alguns minutos: URLs novas levam um momento para se propagar até os data centers da Azion. ## Faça o deploy com a Azion CLI @@ -129,7 +129,7 @@ Abra o domínio Azion no navegador para ver sua aplicação rodando. Se você re # HTTP/2 200 ``` - Se você receber um erro de imediato, aguarde alguns minutos: URLs novas levam um momento para se propagar até as edge locations da Azion. + Se você receber um erro de imediato, aguarde alguns minutos: URLs novas levam um momento para se propagar até os data centers da Azion. @@ -146,13 +146,13 @@ Você publicou uma aplicação na rede global da Azion e confirmou que ela respo Acompanhe métricas e eventos em tempo real. -## Produtos relacionados - +## Recursos relacionados O objeto que você acabou de criar: as regras, as origens e as localidades que respondem pelo seu domínio. Execute seu próprio JavaScript no edge, na requisição ou na resposta, na mesma aplicação. Decida o que o edge responde da memória, por quanto tempo e por qual chave. Vincule, publique e reverta um projeto do terminal que você já tem aberto. + Acompanhe a requisição que você acabou de servir pela infraestrutura distribuída da Azion até a sua origem. diff --git a/src/content/docs/pt-br/pages/responsabilidade-compartilhada/responsabilidade-compartilhada.mdx b/src/content/docs/pt-br/pages/responsabilidade-compartilhada/responsabilidade-compartilhada.mdx index d8cb3cc8eb..52c54d6214 100644 --- a/src/content/docs/pt-br/pages/responsabilidade-compartilhada/responsabilidade-compartilhada.mdx +++ b/src/content/docs/pt-br/pages/responsabilidade-compartilhada/responsabilidade-compartilhada.mdx @@ -94,6 +94,6 @@ Controles Compartilhados – Azion e cliente trabalham colaborativamente para me - Gerenciamento de Logs – Enquanto a Azion exige que você tenha seu produto Real-Time Events para fornecer acesso a logs de curto prazo para fins de depuração, é responsabilidade do cliente configurar drenos de log com o Azion Data Stream para retenção de log de longo prazo, auditoria de dados ou visibilidade adicional no desempenho e segurança de sua aplicação. - Gerenciamento de Patches – A Azion é responsável por corrigir e corrigir falhas em sua Plataforma de Edge, mas os clientes são responsáveis por corrigir seu próprio código e aplicações. -- Autenticação – Os clientes devem garantir que suas informações de autenticação — senha, tokens, credenciais, etc. — atendam aos critérios gerais de segurança e sejam mantidas em segurança. A Azion deve garantir a segurança e proteção da plataforma em relação à autenticação. +- Autenticação – Os clientes devem garantir que suas informações de autenticação — como senha, tokens e credenciais — atendam aos critérios gerais de segurança e sejam mantidas em segurança. A Azion deve garantir a segurança e proteção da plataforma em relação à autenticação. Note que este Modelo de Responsabilidade Compartilhada é um framework generalizado, e as responsabilidades e ofertas específicas podem variar com base nos serviços e soluções exatos que você contratou. É aconselhável consultar diretamente com a equipe da Azion para obter detalhes mais específicos, quando necessário. Além disso, a Azion fornece matrizes de responsabilidade para ajudar os clientes a cumprir o PCI DSS e outras regulamentações específicas ao usar os Produtos e Serviços da Azion. Consulte nossa [equipe de suporte](/pt-br/documentacao/suporte/#canais-de-atendimento) para acessar estas informações. diff --git a/src/data/architectures-home/en.ts b/src/data/architectures-home/en.ts index c8ed6026b8..ba6955b1df 100644 --- a/src/data/architectures-home/en.ts +++ b/src/data/architectures-home/en.ts @@ -26,7 +26,7 @@ export const en: ArchitecturesHomeContent = { prefix: 'Also useful:', links: [ { label: 'Guides', href: '/en/documentation/guides/' }, - { label: 'How Azion works', href: '/en/documentation/platform/' }, + { label: 'How Azion works', href: '/en/documentation/fundamentals/how-it-works/' }, { label: 'architectures llms.txt', href: '/en/documentation/architectures/llms.txt' }, ], }, diff --git a/src/data/architectures-home/pt-br.ts b/src/data/architectures-home/pt-br.ts index f708c5364c..ea69b97912 100644 --- a/src/data/architectures-home/pt-br.ts +++ b/src/data/architectures-home/pt-br.ts @@ -26,7 +26,7 @@ export const ptBr: ArchitecturesHomeContent = { prefix: 'Também útil:', links: [ { label: 'Guias', href: '/pt-br/documentacao/guias/' }, - { label: 'Como a Azion funciona', href: '/pt-br/documentacao/plataforma/' }, + { label: 'Como a Azion funciona', href: '/pt-br/documentacao/fundamentos/como-funciona/' }, { label: 'llms.txt das arquiteturas', href: '/pt-br/documentacao/arquiteturas/llms.txt' }, ], }, diff --git a/src/data/devtools-home/en.ts b/src/data/devtools-home/en.ts index 677dadaad5..08fb9382f1 100644 --- a/src/data/devtools-home/en.ts +++ b/src/data/devtools-home/en.ts @@ -8,7 +8,7 @@ export const en: DevtoolsHomeContent = { description: 'Connect a coding agent, run a project locally, deploy it, and automate the platform with Azion CLI, APIs, Go SDK, and the MCP server.', buttonLabel: 'Deploy your site', - buttonLink: '/en/documentation/first-deploy/', + buttonLink: '/en/documentation/fundamentals/first-deploy/', }, promptPreview: { diff --git a/src/data/devtools-home/pt-br.ts b/src/data/devtools-home/pt-br.ts index 16fbdd0af0..8e6819b990 100644 --- a/src/data/devtools-home/pt-br.ts +++ b/src/data/devtools-home/pt-br.ts @@ -8,7 +8,7 @@ export const ptBr: DevtoolsHomeContent = { description: 'Conecte um agente de código, execute um projeto localmente, faça o deploy e automatize a plataforma com Azion CLI, APIs, Go SDK e o servidor MCP.', buttonLabel: 'Faça o deploy do seu site', - buttonLink: '/pt-br/documentacao/primeiro-deploy/', + buttonLink: '/pt-br/documentacao/fundamentos/primeiro-deploy/', }, promptPreview: { diff --git a/src/data/docs-home/en.ts b/src/data/docs-home/en.ts index efa586bb22..d7041f04f9 100644 --- a/src/data/docs-home/en.ts +++ b/src/data/docs-home/en.ts @@ -26,7 +26,7 @@ export const en: DocsHomeContent = { description: 'We make every application fast and reliable. Deploy on a global network, with enterprise-grade security and no cold starts.', buttonLabel: 'Get started', - buttonLink: '/en/documentation/first-deploy/', + buttonLink: '/en/documentation/fundamentals/first-deploy/', note: 'The prompt hands your coding agent the CLI, live docs over MCP, and this project linked.', prompt: AGENT_PROMPT, promptLabel: 'Copy prompt', @@ -89,7 +89,7 @@ export const en: DocsHomeContent = { { icon: 'ai ai-build-pillar', title: 'Build your application', - href: '/en/documentation/first-deploy/', + href: '/en/documentation/fundamentals/first-deploy/', body: 'Deploy from a template, a repo, or the CLI.', }, { @@ -174,7 +174,7 @@ export const en: DocsHomeContent = { footer: { prefix: 'Also useful:', links: [ - { label: 'First deploy', href: '/en/documentation/first-deploy/' }, + { label: 'First deploy', href: '/en/documentation/fundamentals/first-deploy/' }, { label: 'Frameworks compatibility', href: '/en/documentation/devtools/runtime/frameworks/frameworks-compatibility/', @@ -228,7 +228,7 @@ export const en: DocsHomeContent = { { icon: 'pi pi-arrow-right-arrow-left', title: 'Stream to SIEM', - href: '/en/documentation/products/secure/automate/integrate-siems/', + href: '/en/documentation/guides/', class: 'sm:col-span-2 lg:col-span-3', body: 'Stream WAF and firewall events where your team watches.', }, diff --git a/src/data/docs-home/pt-br.ts b/src/data/docs-home/pt-br.ts index 4b44127c23..713664ea8c 100644 --- a/src/data/docs-home/pt-br.ts +++ b/src/data/docs-home/pt-br.ts @@ -25,7 +25,7 @@ export const ptBr: DocsHomeContent = { description: 'Tornamos toda aplicação rápida e confiável. Faça o deploy em uma rede global, com segurança de nível corporativo e sem cold starts.', buttonLabel: 'Começar', - buttonLink: '/pt-br/documentacao/primeiro-deploy/', + buttonLink: '/pt-br/documentacao/fundamentos/primeiro-deploy/', note: 'O prompt entrega ao seu agente de código a CLI, a documentação ao vivo via MCP e este projeto vinculado.', prompt: AGENT_PROMPT, promptLabel: 'Copiar prompt', @@ -88,7 +88,7 @@ export const ptBr: DocsHomeContent = { { icon: 'ai ai-build-pillar', title: 'Construa sua aplicação', - href: '/pt-br/documentacao/primeiro-deploy/', + href: '/pt-br/documentacao/fundamentos/primeiro-deploy/', body: 'Faça o deploy a partir de um template, de um repositório ou da CLI.', }, { @@ -173,7 +173,7 @@ export const ptBr: DocsHomeContent = { footer: { prefix: 'Também útil:', links: [ - { label: 'Primeiro deploy', href: '/pt-br/documentacao/primeiro-deploy/' }, + { label: 'Primeiro deploy', href: '/pt-br/documentacao/fundamentos/primeiro-deploy/' }, { label: 'Compatibilidade de frameworks', href: '/pt-br/documentacao/devtools/runtime/frameworks/compatibilidade-frameworks/', @@ -227,7 +227,7 @@ export const ptBr: DocsHomeContent = { { icon: 'pi pi-arrow-right-arrow-left', title: 'Envie para um SIEM', - href: '/pt-br/documentacao/produtos/secure/automatizar/integrar-siems/', + href: '/pt-br/documentacao/guias/', class: 'sm:col-span-2 lg:col-span-3', body: 'Transmita eventos do WAF e do firewall para onde sua equipe acompanha.', }, diff --git a/src/data/platform-topology/en.ts b/src/data/platform-topology/en.ts new file mode 100644 index 0000000000..ea16c4bca9 --- /dev/null +++ b/src/data/platform-topology/en.ts @@ -0,0 +1,165 @@ +import type { PlatformTopologyContent } from './types'; + +// Keep in sync with the "Platform resources topology" walkthrough on the Fundamentals overview +// (src/content/docs/en/pages/main-menu/get-started/fundamentals.mdx). +const REQUIRED = { label: 'Required', severity: 'info' } as const; +const OPTIONAL = { label: 'Optional', severity: 'secondary' } as const; + +export const en: PlatformTopologyContent = { + lang: 'en', + ariaLabel: 'Platform resources topology', + referenceLabel: 'Read the reference', + links: [{ from: 'connector', to: 'store-ai' }], + columns: [ + [ + { + id: 'workload', + icon: 'ai ai-workloads', + kind: 'Workload', + tag: REQUIRED, + role: 'Receives traffic', + items: [ + { + id: 'domains', + label: 'Domains', + href: '/en/documentation/platform/workloads/domains/', + }, + { + id: 'certificate-manager', + label: 'Certificate Manager', + href: '/en/documentation/platform/certificate-manager/', + }, + ], + href: '/en/documentation/platform/workloads/', + }, + ], + [ + { + id: 'firewall', + icon: 'ai ai-edge-firewall', + kind: 'Firewall', + tag: OPTIONAL, + role: 'Filters requests', + terminal: true, + items: [ + { id: 'waf', label: 'WAF', href: '/en/documentation/secure/waf/' }, + { + id: 'ddos-protection', + label: 'DDoS Protection', + href: '/en/documentation/platform/ddos-protection/', + }, + { + id: 'bot-manager', + label: 'Bot Manager', + href: '/en/documentation/secure/bot-manager/', + }, + { + id: 'network-shield', + label: 'Network Shield', + href: '/en/documentation/secure/network-shield/', + }, + ], + href: '/en/documentation/platform/firewall/', + }, + { + id: 'application', + icon: 'ai ai-edge-application', + kind: 'Application', + tag: REQUIRED, + role: 'Serves content', + items: [ + { + id: 'functions', + label: 'Functions', + href: '/en/documentation/build/functions/', + }, + { + id: 'rules-engine', + label: 'Rules Engine', + href: '/en/documentation/platform/applications/rules-engine/', + }, + { id: 'cache', label: 'Cache', href: '/en/documentation/build/cache/' }, + { + id: 'image-processor', + label: 'Image Processor', + href: '/en/documentation/build/image-processor/', + }, + ], + href: '/en/documentation/platform/applications/', + }, + { + id: 'custom-pages', + icon: 'ai ai-custom-pages', + kind: 'Custom Pages', + tag: OPTIONAL, + role: 'Error pages', + terminal: true, + href: '/en/documentation/platform/custom-pages/', + }, + ], + [ + { + id: 'store-ai', + icon: 'ai ai-store', + kind: 'Store and AI', + tag: OPTIONAL, + role: 'Data and models', + terminal: true, + items: [ + { + id: 'sql-database', + label: 'SQL Database', + href: '/en/documentation/store/sql-database/', + }, + { + id: 'kv-store', + label: 'KV Store', + href: '/en/documentation/store/kv-store/', + }, + { + id: 'ai-inference', + label: 'AI Inference', + href: '/en/documentation/build/ai-inference/', + }, + { + id: 'object-storage', + label: 'Object Storage', + href: '/en/documentation/store/object-storage/', + }, + ], + href: '/en/documentation/build/functions/', + }, + { + id: 'connector', + icon: 'ai ai-edge-connectors', + kind: 'Connector', + tag: REQUIRED, + role: 'HTTP or storage', + items: [ + { + id: 'load-balancer', + label: 'Load Balancer', + href: '/en/documentation/platform/load-balancer/', + }, + { + id: 'origin-shield', + label: 'Origin Shield', + href: '/en/documentation/secure/origin-shield/', + }, + ], + href: '/en/documentation/platform/connectors/', + }, + ], + [ + { + id: 'origin', + icon: 'pi pi-server', + kind: 'Origin', + tag: { label: 'Yours', severity: 'contrast' }, + role: 'Your server', + terminal: true, + href: '/en/documentation/platform/connectors/origins/', + }, + ], + ], +}; diff --git a/src/data/platform-topology/index.ts b/src/data/platform-topology/index.ts new file mode 100644 index 0000000000..fd8d7e7751 --- /dev/null +++ b/src/data/platform-topology/index.ts @@ -0,0 +1,18 @@ +import type { Lang } from '~/data/docs-home/types'; + +import { en } from './en'; +import { ptBr } from './pt-br'; +import type { PlatformTopologyContent } from './types'; + +export type { + PlatformTopologyContent, + TopologyItem, + TopologyLink, + TopologyNode, + TopologyNodeId, +} from './types'; + +export const platformTopology: Record = { + en, + 'pt-br': ptBr, +}; diff --git a/src/data/platform-topology/pt-br.ts b/src/data/platform-topology/pt-br.ts new file mode 100644 index 0000000000..d910155add --- /dev/null +++ b/src/data/platform-topology/pt-br.ts @@ -0,0 +1,165 @@ +import type { PlatformTopologyContent } from './types'; + +// Manter em sincronia com o passo a passo de "Topologia dos Recursos de Plataforma" na visão +// geral de Fundamentos (src/content/docs/pt-br/pages/menu-principal/ponto-de-partida/fundamentos.mdx). +const OBRIGATORIO = { label: 'Obrigatório', severity: 'info' } as const; +const OPCIONAL = { label: 'Opcional', severity: 'secondary' } as const; + +export const ptBr: PlatformTopologyContent = { + lang: 'pt-br', + ariaLabel: 'Topologia dos Recursos de Plataforma', + referenceLabel: 'Ler a referência', + links: [{ from: 'connector', to: 'store-ai' }], + columns: [ + [ + { + id: 'workload', + icon: 'ai ai-workloads', + kind: 'Workload', + tag: OBRIGATORIO, + role: 'Recebe o tráfego', + items: [ + { + id: 'domains', + label: 'Domínios', + href: '/pt-br/documentacao/plataforma/workloads/domains/', + }, + { + id: 'certificate-manager', + label: 'Certificate Manager', + href: '/pt-br/documentacao/plataforma/certificate-manager/', + }, + ], + href: '/pt-br/documentacao/plataforma/workloads/', + }, + ], + [ + { + id: 'firewall', + icon: 'ai ai-edge-firewall', + kind: 'Firewall', + tag: OPCIONAL, + role: 'Filtra requisições', + terminal: true, + items: [ + { id: 'waf', label: 'WAF', href: '/pt-br/documentacao/secure/waf/' }, + { + id: 'ddos-protection', + label: 'DDoS Protection', + href: '/pt-br/documentacao/plataforma/ddos-protection/', + }, + { + id: 'bot-manager', + label: 'Bot Manager', + href: '/pt-br/documentacao/secure/bot-manager/', + }, + { + id: 'network-shield', + label: 'Network Shield', + href: '/pt-br/documentacao/secure/network-shield/', + }, + ], + href: '/pt-br/documentacao/plataforma/firewall/', + }, + { + id: 'application', + icon: 'ai ai-edge-application', + kind: 'Aplicação', + tag: { label: 'Obrigatória', severity: 'info' }, + role: 'Serve o conteúdo', + items: [ + { + id: 'functions', + label: 'Functions', + href: '/pt-br/documentacao/build/functions/', + }, + { + id: 'rules-engine', + label: 'Rules Engine', + href: '/pt-br/documentacao/plataforma/applications/rules-engine/', + }, + { id: 'cache', label: 'Cache', href: '/pt-br/documentacao/build/cache/' }, + { + id: 'image-processor', + label: 'Image Processor', + href: '/pt-br/documentacao/build/image-processor/', + }, + ], + href: '/pt-br/documentacao/plataforma/applications/', + }, + { + id: 'custom-pages', + icon: 'ai ai-custom-pages', + kind: 'Custom Pages', + tag: OPCIONAL, + role: 'Páginas de erro', + terminal: true, + href: '/pt-br/documentacao/plataforma/custom-pages/', + }, + ], + [ + { + id: 'store-ai', + icon: 'ai ai-store', + kind: 'Store e AI', + tag: OPCIONAL, + role: 'Dados e modelos', + terminal: true, + items: [ + { + id: 'sql-database', + label: 'SQL Database', + href: '/pt-br/documentacao/store/sql-database/', + }, + { + id: 'kv-store', + label: 'KV Store', + href: '/pt-br/documentacao/store/kv-store/', + }, + { + id: 'ai-inference', + label: 'AI Inference', + href: '/pt-br/documentacao/build/ai-inference/', + }, + { + id: 'object-storage', + label: 'Object Storage', + href: '/pt-br/documentacao/store/object-storage/', + }, + ], + href: '/pt-br/documentacao/build/functions/', + }, + { + id: 'connector', + icon: 'ai ai-edge-connectors', + kind: 'Connector', + tag: OBRIGATORIO, + role: 'HTTP ou storage', + items: [ + { + id: 'load-balancer', + label: 'Load Balancer', + href: '/pt-br/documentacao/plataforma/load-balancer/', + }, + { + id: 'origin-shield', + label: 'Origin Shield', + href: '/pt-br/documentacao/secure/origin-shield/', + }, + ], + href: '/pt-br/documentacao/plataforma/connectors/', + }, + ], + [ + { + id: 'origin', + icon: 'pi pi-server', + kind: 'Origem', + tag: { label: 'Sua', severity: 'contrast' }, + role: 'Seu servidor', + terminal: true, + href: '/pt-br/documentacao/plataforma/connectors/origins/', + }, + ], + ], +}; diff --git a/src/data/platform-topology/types.ts b/src/data/platform-topology/types.ts new file mode 100644 index 0000000000..021381a1cc --- /dev/null +++ b/src/data/platform-topology/types.ts @@ -0,0 +1,67 @@ +import type { Lang } from '~/data/docs-home/types'; + +/** Severity values the webkit Tag accepts. */ +export type TopologyTagSeverity = + | 'primary' + | 'secondary' + | 'success' + | 'info' + | 'warning' + | 'danger' + | 'accent' + | 'contrast'; + +export type TopologyNodeId = + | 'workload' + | 'firewall' + | 'application' + | 'custom-pages' + | 'store-ai' + | 'connector' + | 'origin'; + +/** A product or feature listed inside a card once it is open. */ +export interface TopologyItem { + id: string; + label: string; + /** Language-prefixed permalink of the item's reference page. */ + href: string; +} + +/** One card of the diagram. Its header names the resource; its body opens in place. */ +export interface TopologyNode { + id: TopologyNodeId; + /** Icon-font class, for example `ai ai-workloads`. */ + icon: string; + /** Header: the resource kind. */ + kind: string; + /** Body tag: whether the resource is required, optional, or yours. */ + tag: { label: string; severity: TopologyTagSeverity }; + /** Identity row: what the resource does, in two or three words. */ + role: string; + /** Body: what you enable or create on the resource, each linking to its reference. */ + items?: TopologyItem[]; + /** Language-prefixed permalink of the resource's reference page. */ + href: string; + /** Ends its branch: the card receives a connector and originates none. */ + terminal?: boolean; +} + +/** A connector the flow cannot draw by itself: from the top edge of one card to the bottom + * edge of the card above it in the same column. */ +export interface TopologyLink { + from: TopologyNodeId; + to: TopologyNodeId; +} + +export interface PlatformTopologyContent { + lang: Lang; + /** Accessible name of the diagram. */ + ariaLabel: string; + /** Label of the link that closes every card body. */ + referenceLabel: string; + /** Left to right. Adjacent columns pair their cards in order, so the order inside a column is + * the wiring; a `terminal` card sends nothing to the next column. */ + columns: TopologyNode[][]; + links: TopologyLink[]; +} diff --git a/src/data/use-cases/en.ts b/src/data/use-cases/en.ts new file mode 100644 index 0000000000..8c81fbb716 --- /dev/null +++ b/src/data/use-cases/en.ts @@ -0,0 +1,186 @@ +import type { UseCaseCatalogContent } from './types'; + +// The 27 entries and their Solutions follow the Use Case catalog (2026-09-25). `featured` marks +// the selection How Azion works shows; a link is set only where a page implements the use case. +export const en: UseCaseCatalogContent = { + lang: 'en', + solutions: { + 'build-and-run-applications': 'Build and run applications', + 'improve-performance-and-reliability': 'Improve application performance and reliability', + 'build-and-run-ai-workloads': 'Build and run AI workloads', + 'secure-applications-and-networks': 'Secure applications and networks', + 'deliver-media-and-streaming': 'Deliver media and streaming content', + }, + useCases: [ + { + id: 'build-and-run-marketing-websites', + solution: 'build-and-run-applications', + title: 'Build and run marketing websites', + href: '/en/documentation/architectures/build-and-run-applications/deploy-jamstack-applications/', + }, + { + id: 'deploy-full-stack-applications-globally', + solution: 'build-and-run-applications', + title: 'Deploy full-stack applications globally', + href: '/en/documentation/architectures/build-and-run-applications/edge-native-applications/', + }, + { + id: 'build-rest-and-graphql-apis', + solution: 'build-and-run-applications', + title: 'Build REST and GraphQL APIs', + href: '/en/documentation/architectures/build-and-run-applications/serverless-applications/', + featured: true, + }, + { + id: 'build-event-driven-apis', + solution: 'build-and-run-applications', + title: 'Build event-driven APIs', + }, + { + id: 'modernize-a-monolithic-application-without-a-rewrite', + solution: 'build-and-run-applications', + title: 'Modernize a monolithic application without a rewrite', + href: '/en/documentation/architectures/build-and-run-applications/application-modernization/', + }, + { + id: 'build-e-commerce-storefronts', + solution: 'build-and-run-applications', + title: 'Build e-commerce storefronts', + href: '/en/documentation/store/object-storage/', + featured: true, + }, + { + id: 'deploy-frontend-applications', + solution: 'build-and-run-applications', + title: 'Deploy frontend applications', + href: '/en/documentation/store/object-storage/', + featured: true, + }, + { + id: 'run-multi-tenant-saas-applications', + solution: 'build-and-run-applications', + title: 'Run multi-tenant SaaS applications', + }, + { + id: 'migrate-an-application-to-a-new-origin-without-downtime', + solution: 'build-and-run-applications', + title: 'Migrate an application to a new origin without downtime', + }, + { + id: 'accelerate-websites-and-apis-with-a-cdn', + solution: 'improve-performance-and-reliability', + title: 'Accelerate websites and APIs with a CDN', + href: '/en/documentation/architectures/improve-performance-and-reliability/application-acceleration/', + }, + { + id: 'keep-an-application-online-when-an-origin-fails', + solution: 'improve-performance-and-reliability', + title: 'Keep an application online when an origin fails', + href: '/en/documentation/platform/load-balancer/', + featured: true, + }, + { + id: 'optimize-images-for-websites-and-mobile-apps', + solution: 'improve-performance-and-reliability', + title: 'Optimize images for websites and mobile apps', + href: '/en/documentation/architectures/improve-performance-and-reliability/image-processing/', + featured: true, + }, + { + id: 'monitor-website-and-api-performance', + solution: 'improve-performance-and-reliability', + title: 'Monitor website and API performance', + href: '/en/documentation/observe/edge-pulse/', + featured: true, + }, + { + id: 'route-users-to-regional-origins', + solution: 'improve-performance-and-reliability', + title: 'Route users to regional origins', + }, + { + id: 'build-and-run-customer-support-ai-assistants', + solution: 'build-and-run-ai-workloads', + title: 'Build and run customer support AI assistants', + href: '/en/documentation/architectures/build-and-run-ai-workloads/ai-agent-copilot-assistant/', + featured: true, + }, + { + id: 'add-ai-features-to-existing-applications', + solution: 'build-and-run-ai-workloads', + title: 'Add AI features to existing applications', + href: '/en/documentation/architectures/build-and-run-ai-workloads/ai-inference-architecture/', + featured: true, + }, + { + id: 'build-ai-agents', + solution: 'build-and-run-ai-workloads', + title: 'Build AI agents', + href: '/en/documentation/architectures/build-and-run-ai-workloads/ai-agent-third-party-llm/', + featured: true, + }, + { + id: 'deploy-remote-mcp-servers', + solution: 'build-and-run-ai-workloads', + title: 'Deploy remote MCP servers', + }, + { + id: 'govern-access-to-multiple-ai-models', + solution: 'build-and-run-ai-workloads', + title: 'Govern access to multiple AI models', + }, + { + id: 'protect-web-applications-from-owasp-top-10-and-zero-day-attacks', + solution: 'secure-applications-and-networks', + title: 'Protect web applications from OWASP Top 10 and zero-day attacks', + href: '/en/documentation/architectures/secure-applications-and-networks/web-application-and-api-protection-waap/', + featured: true, + }, + { + id: 'protect-public-apis-from-abuse', + solution: 'secure-applications-and-networks', + title: 'Protect public APIs from abuse', + href: '/en/documentation/architectures/secure-applications-and-networks/implement-api-gateways-security/', + featured: true, + }, + { + id: 'block-account-takeover-on-login-and-checkout-flows', + solution: 'secure-applications-and-networks', + title: 'Block account takeover on login and checkout flows', + href: '/en/documentation/architectures/secure-applications-and-networks/online-fraud-prevention/', + featured: true, + }, + { + id: 'block-attackers-automatically-from-siem-detections', + solution: 'secure-applications-and-networks', + title: 'Block attackers automatically from SIEM detections', + href: '/en/documentation/architectures/secure-applications-and-networks/security-automation-with-edge-computing/', + }, + { + id: 'screen-file-uploads-for-malicious-content', + solution: 'secure-applications-and-networks', + title: 'Screen file uploads for malicious content', + href: '/en/documentation/architectures/build-and-run-ai-workloads/autonomous-security-ai-agent/', + }, + { + id: 'prepare-regulated-web-applications-for-security-audits', + solution: 'secure-applications-and-networks', + title: 'Prepare regulated web applications for security audits', + href: '/en/documentation/architectures/secure-applications-and-networks/governance-risk-compliance/', + }, + { + id: 'stream-live-events-to-large-audiences', + solution: 'deliver-media-and-streaming', + title: 'Stream live events to large audiences', + href: '/en/documentation/architectures/deliver-media-and-streaming/live-streaming-delivery-with-hls/', + featured: true, + }, + { + id: 'deliver-an-on-demand-video-library', + solution: 'deliver-media-and-streaming', + title: 'Deliver an on-demand video library', + href: '/en/documentation/store/object-storage/', + featured: true, + }, + ], +}; diff --git a/src/data/use-cases/index.ts b/src/data/use-cases/index.ts new file mode 100644 index 0000000000..a63301b203 --- /dev/null +++ b/src/data/use-cases/index.ts @@ -0,0 +1,12 @@ +import type { Lang } from '~/data/docs-home/types'; + +import { en } from './en'; +import { ptBr } from './pt-br'; +import type { UseCaseCatalogContent } from './types'; + +export type { UseCase, UseCaseCatalogContent, UseCaseSolutionId } from './types'; + +export const useCaseCatalog: Record = { + en, + 'pt-br': ptBr, +}; diff --git a/src/data/use-cases/pt-br.ts b/src/data/use-cases/pt-br.ts new file mode 100644 index 0000000000..a31f025828 --- /dev/null +++ b/src/data/use-cases/pt-br.ts @@ -0,0 +1,187 @@ +import type { UseCaseCatalogContent } from './types'; + +// As 27 entradas e as suas Solutions seguem o catálogo de Use Cases (2026-09-25). `featured` marca +// a seleção que Como a Azion funciona mostra; um link só existe onde uma página implementa o use case. +export const ptBr: UseCaseCatalogContent = { + lang: 'pt-br', + solutions: { + 'build-and-run-applications': 'Construir e executar aplicações', + 'improve-performance-and-reliability': + 'Melhorar a performance e a confiabilidade das aplicações', + 'build-and-run-ai-workloads': 'Construir e executar workloads de AI', + 'secure-applications-and-networks': 'Proteger aplicações e redes', + 'deliver-media-and-streaming': 'Entregar mídia e conteúdo de streaming', + }, + useCases: [ + { + id: 'build-and-run-marketing-websites', + solution: 'build-and-run-applications', + title: 'Criar e operar sites de marketing', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-aplicacoes/implantacao-aplicacoes-jamstack/', + }, + { + id: 'deploy-full-stack-applications-globally', + solution: 'build-and-run-applications', + title: 'Implantar aplicações full-stack globalmente', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-aplicacoes/aplicacoes-edge-native/', + }, + { + id: 'build-rest-and-graphql-apis', + solution: 'build-and-run-applications', + title: 'Criar APIs REST e GraphQL', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-aplicacoes/serverless-applications/', + featured: true, + }, + { + id: 'build-event-driven-apis', + solution: 'build-and-run-applications', + title: 'Criar APIs orientadas a eventos', + }, + { + id: 'modernize-a-monolithic-application-without-a-rewrite', + solution: 'build-and-run-applications', + title: 'Modernizar uma aplicação monolítica sem reescrevê-la', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-aplicacoes/modernizacao-de-aplicacoes/', + }, + { + id: 'build-e-commerce-storefronts', + solution: 'build-and-run-applications', + title: 'Criar vitrines de e-commerce', + href: '/pt-br/documentacao/store/object-storage/', + featured: true, + }, + { + id: 'deploy-frontend-applications', + solution: 'build-and-run-applications', + title: 'Implantar aplicações front-end', + href: '/pt-br/documentacao/store/object-storage/', + featured: true, + }, + { + id: 'run-multi-tenant-saas-applications', + solution: 'build-and-run-applications', + title: 'Executar aplicações SaaS multi-tenant', + }, + { + id: 'migrate-an-application-to-a-new-origin-without-downtime', + solution: 'build-and-run-applications', + title: 'Migrar uma aplicação para uma nova origem sem downtime', + }, + { + id: 'accelerate-websites-and-apis-with-a-cdn', + solution: 'improve-performance-and-reliability', + title: 'Acelerar sites e APIs com uma CDN', + href: '/pt-br/documentacao/arquiteturas/melhorar-performance-e-confiabilidade/application-acceleration/', + }, + { + id: 'keep-an-application-online-when-an-origin-fails', + solution: 'improve-performance-and-reliability', + title: 'Manter uma aplicação no ar quando uma origem falha', + href: '/pt-br/documentacao/plataforma/load-balancer/', + featured: true, + }, + { + id: 'optimize-images-for-websites-and-mobile-apps', + solution: 'improve-performance-and-reliability', + title: 'Otimizar imagens para sites e aplicações móveis', + href: '/pt-br/documentacao/arquiteturas/melhorar-performance-e-confiabilidade/processamento-de-imagens/', + featured: true, + }, + { + id: 'monitor-website-and-api-performance', + solution: 'improve-performance-and-reliability', + title: 'Monitorar a performance de sites e APIs', + href: '/pt-br/documentacao/observe/edge-pulse/', + featured: true, + }, + { + id: 'route-users-to-regional-origins', + solution: 'improve-performance-and-reliability', + title: 'Rotear usuários para origens regionais', + }, + { + id: 'build-and-run-customer-support-ai-assistants', + solution: 'build-and-run-ai-workloads', + title: 'Criar e executar assistentes de IA para suporte ao cliente', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-workloads-de-ai/agente-ai-assistente-copilot/', + featured: true, + }, + { + id: 'add-ai-features-to-existing-applications', + solution: 'build-and-run-ai-workloads', + title: 'Adicionar funcionalidades de IA a aplicações existentes', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-workloads-de-ai/ai-inference-architecture/', + featured: true, + }, + { + id: 'build-ai-agents', + solution: 'build-and-run-ai-workloads', + title: 'Criar agentes de IA', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-workloads-de-ai/ai-agent-third-party-llm/', + featured: true, + }, + { + id: 'deploy-remote-mcp-servers', + solution: 'build-and-run-ai-workloads', + title: 'Implantar servidores MCP remotos', + }, + { + id: 'govern-access-to-multiple-ai-models', + solution: 'build-and-run-ai-workloads', + title: 'Governar o acesso a múltiplos modelos de IA', + }, + { + id: 'protect-web-applications-from-owasp-top-10-and-zero-day-attacks', + solution: 'secure-applications-and-networks', + title: 'Proteger aplicações web contra ataques do OWASP Top 10 e zero-day', + href: '/pt-br/documentacao/arquiteturas/proteger-aplicacoes-e-redes/web-application-and-api-protection-waap/', + featured: true, + }, + { + id: 'protect-public-apis-from-abuse', + solution: 'secure-applications-and-networks', + title: 'Proteger APIs públicas contra abuso', + href: '/pt-br/documentacao/arquiteturas/proteger-aplicacoes-e-redes/implementar-seguranca-api-gateways/', + featured: true, + }, + { + id: 'block-account-takeover-on-login-and-checkout-flows', + solution: 'secure-applications-and-networks', + title: 'Bloquear account takeover em fluxos de login e checkout', + href: '/pt-br/documentacao/arquiteturas/proteger-aplicacoes-e-redes/prevencao-fraudes-online/', + featured: true, + }, + { + id: 'block-attackers-automatically-from-siem-detections', + solution: 'secure-applications-and-networks', + title: 'Bloquear atacantes automaticamente a partir de detecções do SIEM', + href: '/pt-br/documentacao/arquiteturas/proteger-aplicacoes-e-redes/automacao-da-seguranca-com-edge-computing/', + }, + { + id: 'screen-file-uploads-for-malicious-content', + solution: 'secure-applications-and-networks', + title: 'Inspecionar uploads de arquivos em busca de conteúdo malicioso', + href: '/pt-br/documentacao/arquiteturas/construir-e-executar-workloads-de-ai/ai-agent-seguranca-autonoma/', + }, + { + id: 'prepare-regulated-web-applications-for-security-audits', + solution: 'secure-applications-and-networks', + title: 'Preparar aplicações web reguladas para auditorias de segurança', + href: '/pt-br/documentacao/arquiteturas/proteger-aplicacoes-e-redes/governanca-risco-conformidade/', + }, + { + id: 'stream-live-events-to-large-audiences', + solution: 'deliver-media-and-streaming', + title: 'Transmitir eventos ao vivo para grandes audiências', + href: '/pt-br/documentacao/arquiteturas/entregar-midia-e-streaming/live-streaming-delivery-com-hls/', + featured: true, + }, + { + id: 'deliver-an-on-demand-video-library', + solution: 'deliver-media-and-streaming', + title: 'Entregar uma biblioteca de vídeos sob demanda', + href: '/pt-br/documentacao/store/object-storage/', + featured: true, + }, + ], +}; diff --git a/src/data/use-cases/types.ts b/src/data/use-cases/types.ts new file mode 100644 index 0000000000..a1d31eaf55 --- /dev/null +++ b/src/data/use-cases/types.ts @@ -0,0 +1,30 @@ +import type { Lang } from '~/data/docs-home/types'; + +/** The five Solutions the Use Case catalog files every entry under. */ +export type UseCaseSolutionId = + | 'build-and-run-applications' + | 'improve-performance-and-reliability' + | 'build-and-run-ai-workloads' + | 'secure-applications-and-networks' + | 'deliver-media-and-streaming'; + +/** One catalogued Use Case. The catalog is the source of the names; this module carries every entry + * so that the pages listing use cases read one source, and `featured` picks the few a page shows. */ +export interface UseCase { + id: string; + solution: UseCaseSolutionId; + /** The Use Case name, as the catalog states it. */ + title: string; + /** Language-prefixed permalink of the page that implements it, when one is published. */ + href?: string; + /** Listed by the pages that show a selection, such as How Azion works. */ + featured?: boolean; +} + +export interface UseCaseCatalogContent { + lang: Lang; + /** Solution names, keyed by id. */ + solutions: Record; + /** Catalog order. */ + useCases: UseCase[]; +} diff --git a/src/i18n/en/footer.ts b/src/i18n/en/footer.ts index 7942fc4176..da7699286f 100644 --- a/src/i18n/en/footer.ts +++ b/src/i18n/en/footer.ts @@ -58,7 +58,7 @@ const listData = [ }, { title: 'How to start', - link: '/en/documentation/platform/', + link: '/en/documentation/fundamentals/how-it-works/', }, { title: 'Pricing', diff --git a/src/i18n/pt-br/footer.ts b/src/i18n/pt-br/footer.ts index 81aa1775da..4da5e7f54e 100644 --- a/src/i18n/pt-br/footer.ts +++ b/src/i18n/pt-br/footer.ts @@ -58,7 +58,7 @@ const listData = [ }, { title: 'Visão geral da plataforma', - link: '/pt-br/documentacao/produtos/visao-geral-da-plataforma-da-azion/', + link: '/pt-br/documentacao/fundamentos/como-funciona/', }, { title: 'Preços', diff --git a/src/nav/exempt.json b/src/nav/exempt.json index 0e33996ae4..58b45e351a 100644 --- a/src/nav/exempt.json +++ b/src/nav/exempt.json @@ -1,4 +1,3 @@ { - "documentation_coming_soon": "the shared landing page every not-yet-written section points at", - "documentation_first_deploy": "reached from the home call to action, not listed in the sidebar" + "documentation_coming_soon": "the shared landing page every not-yet-written section points at" } diff --git a/src/nav/resolve.ts b/src/nav/resolve.ts index 68bc28547f..080481eb58 100644 --- a/src/nav/resolve.ts +++ b/src/nav/resolve.ts @@ -159,7 +159,7 @@ function nodeLabel(data: NavData, node: NavNode, lang: Lang): string { return node.tree ?? node.page ?? ''; } -function nodeHref(data: NavData, node: NavNode, lang: Lang): string | undefined { +function nodeHref(data: NavData, node: NavNode, lang: Lang, owner?: NavTree): string | undefined { // A row may land on a section of its target page: `hash` carries the heading's // slug, which rehype-slug derives from the heading text and keeps identical in // both locales when the heading is a product name. Order matters: path?query#hash. @@ -171,6 +171,7 @@ function nodeHref(data: NavData, node: NavNode, lang: Lang): string | undefined }; if (node.href) return node.href; + if (node.llms) return owner ? `${treeBase(owner, lang)}llms.txt` : undefined; if (node.tree) { const tree = data.trees.get(node.tree); if (!tree) return undefined; @@ -190,15 +191,21 @@ export function pageHref(data: NavData, namespace: string, lang: Lang): string | return undefined; } +/** The section's URL base: where its llms.txt and its rootless index live. */ +function treeBase(tree: NavTree, lang: Lang): string { + return `/${lang}/${DOCS_BASE[lang]}/${trimSlashes(text(tree.path, lang) ?? tree.id)}/`; +} + export function treeHref(data: NavData, tree: NavTree, lang: Lang): string | undefined { if (tree.root) return pageHref(data, tree.root, lang); - return `/${lang}/${DOCS_BASE[lang]}/${trimSlashes(text(tree.path, lang) ?? tree.id)}/`; + return treeBase(tree, lang); } function nodeIdentity(node: NavNode, lang: Lang, index: number): string { if (node.page) return node.page; if (node.tree) return `tree:${node.tree}`; if (node.href) return `href:${slugify(node.href)}`; + if (node.llms) return 'llms'; const label = text(node.label, lang); return label ? slugify(label) : `row-${index}`; } @@ -286,7 +293,7 @@ function openedTree( href: string | undefined, ctx: MenuContext ): string | undefined { - if (node.href || node.placeholder || !href) return undefined; + if (node.href || node.llms || node.placeholder || !href) return undefined; const target = ctx.index.get(normalize(href))?.treeId; if (!target || target === ctx.treeId) return undefined; return data.trees.get(target)?.inline ? undefined : target; @@ -307,7 +314,8 @@ function toMenuNodes( lang: Lang, parentId: string, ctx: MenuContext, - ancestors: string[] + ancestors: string[], + owner: NavTree | undefined = ctx.treeId ? data.trees.get(ctx.treeId) : undefined ): MenuNode[] { const out: MenuNode[] = []; @@ -318,10 +326,10 @@ function toMenuNodes( const inlined = inlineTree(data, node); const rows = inlined ? inlined.groups.flatMap((group) => group.items) : node.items; - const href = inlined ? undefined : nodeHref(data, node, lang); - const external = Boolean(node.href); + const href = inlined ? undefined : nodeHref(data, node, lang, owner); + const external = Boolean(node.href || node.llms); const children = rows?.length - ? toMenuNodes(data, rows, lang, id, ctx, [...ancestors, id]) + ? toMenuNodes(data, rows, lang, id, ctx, [...ancestors, id], inlined ?? owner) : undefined; const claimsActive = Boolean(href) && href !== ctx.comingSoonHref; diff --git a/src/nav/schema.ts b/src/nav/schema.ts index 8df83999c4..6aac25d0de 100644 --- a/src/nav/schema.ts +++ b/src/nav/schema.ts @@ -47,6 +47,8 @@ const baseNode = z.object({ tag: z.string().min(1).optional(), segment: localizedSegment.optional(), linkOnly: z.boolean().optional(), + /** The owning section's llms.txt: the row links the index the section publishes for agents. */ + llms: z.boolean().optional(), placeholder: z.boolean().optional(), products: z.array(z.string().min(1)).optional(), kind: guideKind.optional(), @@ -56,12 +58,16 @@ export type NavNode = z.infer & { items?: NavNode[] }; export const navNode: z.ZodType = baseNode .extend({ items: z.lazy(() => z.array(navNode)).optional() }) - .refine((n) => [n.page, n.tree, n.href].filter(Boolean).length <= 1, { - message: 'a row points at a page, a tree or an href — never more than one', - }) - .refine((n) => Boolean(n.page || n.tree || n.href || n.items?.length || n.placeholder), { - message: 'a row needs a destination or children', + .refine((n) => [n.page, n.tree, n.href, n.llms].filter(Boolean).length <= 1, { + message: + 'a row points at a page, a tree, an href or the section llms.txt — never more than one', }) + .refine( + (n) => Boolean(n.page || n.tree || n.href || n.llms || n.items?.length || n.placeholder), + { + message: 'a row needs a destination or children', + } + ) .refine((n) => Boolean(n.label || n.page || n.tree), { message: 'a row with no page or tree needs an explicit label', }); diff --git a/src/nav/trees/fundamentals.json b/src/nav/trees/fundamentals.json index 9acde08eb9..8e56a4e7d9 100644 --- a/src/nav/trees/fundamentals.json +++ b/src/nav/trees/fundamentals.json @@ -5,7 +5,7 @@ "pt-br": "Fundamentos" }, "description": { - "en": "Accounts, billing, permissions and account security" + "en": "How the platform fits together, your account, billing and account security" }, "parent": "root", "path": { @@ -13,7 +13,6 @@ "pt-br": "fundamentos" }, "root": "documentation_fundamentals", - "inline": true, "groups": [ { "items": [ @@ -25,66 +24,94 @@ } }, { - "page": "documentation_creating_account", + "page": "documentation_azion_platform_overview", "label": { - "en": "Get started", - "pt-br": "Comece aqui" + "en": "How Azion works", + "pt-br": "Como a Azion funciona" + }, + "slug": { + "en": "how-it-works", + "pt-br": "como-funciona" } }, { "label": { - "en": "Accounts", - "pt-br": "Contas" + "en": "Get started", + "pt-br": "Comece aqui" }, "items": [ { - "page": "documentation_accounts_account_settings" - }, - { - "page": "documentation_accounts_clients" + "page": "documentation_creating_account", + "label": { + "en": "Create an account", + "pt-br": "Criar uma conta" + } }, { - "page": "documentation_accounts_activity_history" + "page": "documentation_first_deploy", + "label": { + "en": "First deploy", + "pt-br": "Primeiro deploy" + }, + "slug": { + "en": "first-deploy", + "pt-br": "primeiro-deploy" + } }, { - "page": "documentation_accounts_your_settings" + "page": "documentation_migrate_to_azion", + "label": { + "en": "Migrate to Azion", + "pt-br": "Migrar para a Azion" + } } ] }, { "label": { - "en": "Organization", - "pt-br": "Organização" - }, - "placeholder": true - }, - { - "label": { - "en": "Workspace" - }, - "placeholder": true - }, - { - "label": { - "en": "Members and Permissions", - "pt-br": "Membros e Permissões" + "en": "Management", + "pt-br": "Gerenciamento" }, "items": [ { - "page": "documentation_accounts_teams_permissions" + "page": "documentation_fundamentals_accounts_teams_users" }, { - "page": "documentation_accounts_users_management" + "label": { + "en": "Accounts", + "pt-br": "Contas" + }, + "items": [ + { + "page": "documentation_accounts_account_settings" + }, + { + "page": "documentation_accounts_clients" + }, + { + "page": "documentation_accounts_activity_history" + }, + { + "page": "documentation_accounts_your_settings" + } + ] + }, + { + "label": { + "en": "Members and permissions", + "pt-br": "Membros e permissões" + }, + "items": [ + { + "page": "documentation_accounts_teams_permissions" + }, + { + "page": "documentation_accounts_users_management" + } + ] } ] }, - { - "label": { - "en": "Usage Metering", - "pt-br": "Medição de uso" - }, - "placeholder": true - }, { "label": { "en": "Billing" @@ -105,31 +132,67 @@ }, "items": [ { - "page": "documentation_products_account_lockout_policy" + "page": "documentation_accounts_multi_factor" }, { - "page": "documentation_accounts_multi_factor" + "page": "documentation_accounts_federated_authentication" }, { - "page": "documentation_compliance_pci" + "page": "documentation_accounts_social_login" }, { "page": "documentation_personal_tokens" }, { - "page": "docs_shared_responsibility" + "page": "documentation_products_account_lockout_policy" }, { - "page": "documentation_accounts_federated_authentication" + "page": "documentation_products_user_session_timeout" }, { - "page": "documentation_compliance_soc" + "label": { + "en": "Compliance" + }, + "items": [ + { + "page": "documentation_compliance_pci" + }, + { + "page": "documentation_compliance_soc" + }, + { + "page": "docs_shared_responsibility" + } + ] + } + ] + }, + { + "label": { + "en": "Performance", + "pt-br": "Performance" + }, + "items": [ + { + "page": "documentation_fundamentals_test_speed", + "label": { + "en": "Test speed", + "pt-br": "Testar a velocidade" + } }, { - "page": "documentation_accounts_social_login" + "page": "documentation_fundamentals_minimize_downtime", + "label": { + "en": "Minimize downtime", + "pt-br": "Minimizar o downtime" + } }, { - "page": "documentation_products_user_session_timeout" + "page": "documentation_fundamentals_maintenance_mode", + "label": { + "en": "Maintenance mode", + "pt-br": "Modo de manutenção" + } } ] }, @@ -140,19 +203,34 @@ }, "items": [ { - "page": "documentation_products_apiv4_migration" + "page": "documentation_error_status_codes", + "slug": { + "en": "http-status-codes", + "pt-br": "codigos-de-status-http" + } }, { - "page": "documentation_migrate_to_azion" + "page": "documentation_products_apiv4_migration" } ] }, { "label": { - "en": "Agent Resources", + "en": "Agent resources", "pt-br": "Recursos para agentes" }, - "placeholder": true + "items": [ + { + "tree": "agent-setup" + }, + { + "label": { + "en": "llms.txt", + "pt-br": "llms.txt" + }, + "llms": true + } + ] } ] } diff --git a/src/nav/trees/platform.json b/src/nav/trees/platform.json index 77ef2543f8..24c08c507f 100644 --- a/src/nav/trees/platform.json +++ b/src/nav/trees/platform.json @@ -12,52 +12,40 @@ "en": "platform", "pt-br": "plataforma" }, - "root": "documentation_azion_platform_overview", "inline": true, "groups": [ { + "label": { + "en": "Core services", + "pt-br": "Serviços principais" + }, "items": [ { - "page": "documentation_azion_platform_overview", - "label": { - "en": "How Azion works", - "pt-br": "Como a Azion funciona" - } + "tree": "applications" }, { - "label": { - "en": "Core services", - "pt-br": "Serviços principais" - }, - "items": [ - { - "tree": "applications" - }, - { - "tree": "firewall" - }, - { - "tree": "connectors" - }, - { - "tree": "workloads" - }, - { - "tree": "real-time-metrics" - }, - { - "tree": "ddos-protection" - }, - { - "tree": "custom-pages" - }, - { - "tree": "certificate-manager" - }, - { - "tree": "load-balancer" - } - ] + "tree": "firewall" + }, + { + "tree": "connectors" + }, + { + "tree": "workloads" + }, + { + "tree": "real-time-metrics" + }, + { + "tree": "ddos-protection" + }, + { + "tree": "custom-pages" + }, + { + "tree": "certificate-manager" + }, + { + "tree": "load-balancer" } ] } diff --git a/src/nav/trees/support.json b/src/nav/trees/support.json index 2c8ca5b5de..b3396ff844 100644 --- a/src/nav/trees/support.json +++ b/src/nav/trees/support.json @@ -25,9 +25,6 @@ }, { "page": "documentation_get_help" - }, - { - "page": "documentation_error_status_codes" } ] }