> For the complete documentation index, see [llms.txt](https://docs.scepman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scepman.com/es/despliegue-de-scepman/deployment-guides.md).

# Primeros pasos

Para comenzar con SCEPman, hemos preparado dos guías que abordan diferentes requisitos y alcances para su escenario de despliegue.

**Utilice la tabla siguiente**, para decidir cuál de las dos guías es la más adecuada para su escenario.

## Matriz de decisión

{% hint style="info" %}
En caso de que tenga convenciones de nomenclatura de recursos de Azure, o requisitos de alta disponibilidad o autoescalado que también le gustaría probar, comience directamente con **Guía extendida** - incluso para su Prueba/PoC. Esto le permitirá reutilizar la implementación en producción más adelante.
{% endhint %}

| Requisito / Alcance                                                       |                                                          Guía estándar                                                          |       Guía extendida       |
| ------------------------------------------------------------------------- | :-----------------------------------------------------------------------------------------------------------------------------: | :------------------------: |
| Estoy usando SCEPman Community Edition                                    | <p><span data-gb-custom-inline data-tag="emoji" data-code="2611">☑️</span></p><p>(no todas las funciones están disponibles)</p> |                            |
| Prueba o PoC                                                              |     <p><span data-gb-custom-inline data-tag="emoji" data-code="2611">☑️</span></p><p>(solo <strong>paso</strong> pasos)</p>     |                            |
| Implementación de producción estándar                                     |                                                    :ballot\_box\_with\_check:                                                   |                            |
| Debo respetar las convenciones de nomenclatura de recursos de Azure       |                                                                                                                                 | :ballot\_box\_with\_check: |
| Alta disponibilidad / redundancia                                         |                                                                                                                                 | :ballot\_box\_with\_check: |
| Autoescalado                                                              |                                                                                                                                 | :ballot\_box\_with\_check: |
| implementación de Terraform                                               |                                                                                                                                 | :ballot\_box\_with\_check: |
| Estoy en una región de nube de Azure Government (GCC High, 21Vianet, ...) |                                                                                                                                 | :ballot\_box\_with\_check: |

{% content-ref url="/pages/5b8592e64c883267eca270ef03e3721cd4e1366a" %}
[Guía estándar](/es/despliegue-de-scepman/deployment-guides/community-guide.md)
{% endcontent-ref %}

{% content-ref url="/pages/c0b0eec8d1a98c5d3b469edd3b7dcb2a4e01dc23" %}
[Guía extendida](/es/despliegue-de-scepman/deployment-guides/enterprise-guide-1.md)
{% endcontent-ref %}

## Vídeos

{% embed url="<https://www.youtube.com/watch?v=Q1DTVlxLSoU>" %}
Implementación de SCEPman 2.0
{% endembed %}

## Escenarios

Para ver ejemplos de configuración de escenarios específicos que implican certificados emitidos por SCEPman, consulte la siguiente sección:

{% content-ref url="/pages/a6780f410b4da662f6fd6b8b0b36adc8ef5246c7" %}
[Escenarios](/es/despliegue-de-scepman/deployment-guides/scenarios.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scepman.com/es/despliegue-de-scepman/deployment-guides.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
