> For the complete documentation index, see [llms.txt](https://academy.cegedim.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.cegedim.cloud/itcare/what-is-itcare/get-started-with-itcare.md).

# Get started with ITCare

## How do I connect to ITCare? <a href="#gestiondecompte-howdoiconnecttoitcare" id="gestiondecompte-howdoiconnecttoitcare"></a>

It is not possible to create your own ITCare account to access the platform.

To receive an ITCare account, your organization's security representative must submit an account creation request.

## How do I request an ITCare account? <a href="#gestiondecompte-howdoirequestanitcareaccount" id="gestiondecompte-howdoirequestanitcareaccount"></a>

Please contact your Service Delivery Management or the commercial team at cegedim.cloud.

## How is ITCare authentication handled? <a href="#gestiondecompte-howisitcareauthenticationhandled" id="gestiondecompte-howisitcareauthenticationhandled"></a>

ITCare authentication is based on an e-mail address and a password that comply with the standards of the cegedim security policy.

API accounts use the OpenID protocol. More information about the ITCare API can be found at [Authentication](/itcare-api/itcare-api-authentication.md).

## Is multi-factor authentication available? <a href="#gestiondecompte-ismulti-factorauthenticationavailable" id="gestiondecompte-ismulti-factorauthenticationavailable"></a>

Multi-factor authentication is available and mandatory for certain high privilege actions.

During the on-boarding process, you will be provided with all the information necessary to properly configure the MFA.

## What are the possible privileges in ITCare? <a href="#gestiondecompte-whatarethepossibleprivilegesinitcare" id="gestiondecompte-whatarethepossibleprivilegesinitcare"></a>

ITCare privileges are broken down into roles assigned to profiles.

Profiles are assigned to users.

### The roles <a href="#gestiondecompte-theroles" id="gestiondecompte-theroles"></a>

<table><thead><tr><th width="247">Roles</th><th>Description</th></tr></thead><tbody><tr><td>See resources</td><td>See all the resources and their informations. Read only</td></tr><tr><td>Manage maintenances</td><td>Ability to manage maintenances</td></tr><tr><td>Modify resources</td><td>Ability to modify resources except creation and deletion</td></tr><tr><td>Manage resources</td><td>Complete resource management</td></tr></tbody></table>

{% hint style="warning" %}
MFA must be configured and is mandatory for the following roles:

* Manage maintenances
* Modify resources
* Manage resources
  {% endhint %}

### The profiles <a href="#gestiondecompte-theprofiles" id="gestiondecompte-theprofiles"></a>

<table data-full-width="true"><thead><tr><th>Profiles</th><th data-type="checkbox">See resources</th><th data-type="checkbox">Manage maintenances</th><th data-type="checkbox">Modify resources</th><th data-type="checkbox">Manage resources</th></tr></thead><tbody><tr><td>Standard (STD)</td><td>true</td><td>false</td><td>false</td><td>false</td></tr><tr><td>Maintenance (DTM)</td><td>true</td><td>true</td><td>false</td><td>false</td></tr><tr><td>Operator (OPE)</td><td>true</td><td>true</td><td>true</td><td>false</td></tr><tr><td>Power (POW)</td><td>true</td><td>true</td><td>true</td><td>true</td></tr></tbody></table>

### Privilege Matrix <a href="#gestiondecompte-privilegematrix" id="gestiondecompte-privilegematrix"></a>

This non-exhaustive table describes the basic actions allowed by profile:

<table data-full-width="true"><thead><tr><th>Features</th><th>Label</th><th>Available for</th></tr></thead><tbody><tr><td>Bodies</td><td>create-instance</td><td>POW</td></tr><tr><td>start-instance</td><td>OPE</td><td></td></tr><tr><td>stop-instance</td><td>OPE</td><td></td></tr><tr><td>reset-instance</td><td>OPE</td><td></td></tr><tr><td>resize-compute-instance</td><td>OPE</td><td></td></tr><tr><td>delete-instance</td><td>POW</td><td></td></tr><tr><td>Instance monitoring</td><td>enable-monitoring-instance</td><td>OPE</td></tr><tr><td>disable-monitoring-instance</td><td>OPE</td><td></td></tr><tr><td>Snapshot of instances</td><td>create-snapshot</td><td>MNT</td></tr><tr><td>recover-snapshot</td><td>MNT</td><td></td></tr><tr><td>delete-snapshot</td><td>MNT</td><td></td></tr><tr><td>DNS aliases of instances</td><td>create-dns</td><td>OPE</td></tr><tr><td>delete-dns</td><td>OPE</td><td></td></tr><tr><td>LoadBalancers</td><td>create-lb</td><td>POW</td></tr><tr><td>start-lb</td><td>OPE</td><td></td></tr><tr><td>stop-lb</td><td>OPE</td><td></td></tr><tr><td>delete-lb</td><td>POW</td><td></td></tr><tr><td>Monitoring of LoadBalancers</td><td>enable-monitoring-lb</td><td>OPE</td></tr><tr><td>disable-monitoring-lb</td><td>OPE</td><td></td></tr><tr><td>Manage LoadBalancers</td><td>add-member-lb</td><td>OPE</td></tr><tr><td>delete-member-lb</td><td>OPE</td><td></td></tr><tr><td>update-member-state</td><td>OPE</td><td></td></tr><tr><td>DNS alias of LoadBalancers</td><td>create-dns-lb</td><td>OPE</td></tr><tr><td>delete-dns-lb</td><td>OPE</td><td></td></tr><tr><td>Manage maintenance</td><td>create-maintenance</td><td>MNT</td></tr><tr><td>delete-maintenance</td><td>MNT</td><td></td></tr><tr><td>Indicators</td><td>create-indicator</td><td>POW</td></tr><tr><td>update-indicator</td><td>POW</td><td></td></tr><tr><td>delete-indicator</td><td>POW</td><td></td></tr><tr><td>SMS</td><td>subscribe-vortext</td><td>POW</td></tr><tr><td>Storage Object</td><td>create-object-stores</td><td>POW</td></tr><tr><td>update-object-stores</td><td>OPE</td><td></td></tr><tr><td>delete-object-stores</td><td>POW</td><td></td></tr><tr><td>Storage Object - Users</td><td>create-user-objectstores</td><td>POW</td></tr><tr><td>update-user-objectstores</td><td>POW</td><td></td></tr><tr><td>delete-user-objectstores</td><td>POW</td><td></td></tr><tr><td>K8S Clusters</td><td>create-cluster</td><td>POW</td></tr><tr><td>create-cluster-namespace</td><td>OPE</td><td></td></tr><tr><td>delete-cluster-namespace</td><td>OPE</td><td></td></tr><tr><td>create-cluster-nodes</td><td>POW</td><td></td></tr><tr><td>delete-cluster-nodes</td><td>POW</td><td></td></tr></tbody></table>

## What are the Regions and Availability Zones in ITCare? <a href="#presentationitcare-whataretheregionsandavailabilityzonesinitcare" id="presentationitcare-whataretheregionsandavailabilityzonesinitcare"></a>

The topology of the cegedim.cloud hosting platform is divided into:

* **Regions**: a group of low latency data centers ( < 1 ms)
* **Availability zones**: a set of dedicated infrastructure components in a data center

```mermaid
graph LR
    subgraph region["🚩 Region"]
        direction LR
        subgraph dc1["Datacenter"]
            subgraph az1["Availability zone"]
                i1["📦 Instances"]
            end
        end
        subgraph dc2["Datacenter"]
            subgraph az2["Availability zone"]
                i2["📦 Instances"]
            end
        end
        subgraph dc3["Datacenter"]
            subgraph az3["Availability zone"]
                i3["📦 Instances"]
            end
        end
    end

    i1 ~~~ i2 ~~~ i3

    style region fill:#cfe2ff,stroke:#0066cc,stroke-width:2px,color:#000
    style dc1 fill:#3a3a3a,stroke:#000,stroke-width:2px,color:#fff
    style dc2 fill:#3a3a3a,stroke:#000,stroke-width:2px,color:#fff
    style dc3 fill:#3a3a3a,stroke:#000,stroke-width:2px,color:#fff
    style az1 fill:#1abc9c,stroke:#0e6655,stroke-width:2px,color:#000
    style az2 fill:#1abc9c,stroke:#0e6655,stroke-width:2px,color:#000
    style az3 fill:#1abc9c,stroke:#0e6655,stroke-width:2px,color:#000
    style i1 fill:#dde8f5,stroke:#000,stroke-width:2px,color:#000
    style i2 fill:#dde8f5,stroke:#000,stroke-width:2px,color:#000
    style i3 fill:#dde8f5,stroke:#000,stroke-width:2px,color:#000
```

### What regions are available? <a href="#presentationitcare-whatregionsareavailable" id="presentationitcare-whatregionsareavailable"></a>

Here is the list of regions available to our customers:

<table><thead><tr><th width="134.33333333333331">Region</th><th width="173">Description</th><th>Datacenters</th></tr></thead><tbody><tr><td>EB</td><td>Paris area</td><td><p>EB3 : Boulogne-Billancourt</p><p>EB4 : Boulogne-Billancourt</p><p>EB5 : Magny-les-Hameaux</p></td></tr><tr><td>ET</td><td>Toulouse area</td><td><p>ET1 : Labège</p><p>ET2 : Balma</p></td></tr></tbody></table>

### What Availability Zones are available? <a href="#presentationitcare-whataretheavailableareas" id="presentationitcare-whataretheavailableareas"></a>

#### EB Region <a href="#presentationitcare-ebregion" id="presentationitcare-ebregion"></a>

<table><thead><tr><th width="180.33333333333331">Availability Zone</th><th width="342">Description</th><th>Datacenter</th></tr></thead><tbody><tr><td>EB-HDS-A</td><td>Client zone</td><td>EB4</td></tr><tr><td>EB-HDS-B</td><td>Client zone</td><td>EB3</td></tr><tr><td>EB-HDS-C</td><td>Client zone</td><td>EB5</td></tr><tr><td>EB-A</td><td>Area reserved for the cegedim group</td><td>EB4</td></tr><tr><td>EB-B</td><td>Area reserved for the cegedim group</td><td>EB3</td></tr><tr><td>EB-C</td><td>Area reserved for the cegedim group</td><td>EB5</td></tr></tbody></table>

#### ET Region <a href="#presentationitcare-regionand" id="presentationitcare-regionand"></a>

<table><thead><tr><th width="186.33333333333331">Availability Zone</th><th width="360">Description</th><th>Datacenter</th></tr></thead><tbody><tr><td>ET-HDS-A</td><td>Client zone</td><td>ET1</td></tr><tr><td>ET-HDS-B</td><td>Client zone</td><td>ET1</td></tr><tr><td>ET-HDS-C</td><td>Client zone</td><td>ET2</td></tr><tr><td>ET-A</td><td>Area reserved for the cegedim group</td><td>ET1</td></tr><tr><td>ET-B</td><td>Area reserved for the cegedim group</td><td>ET1</td></tr><tr><td>ET-C</td><td>Area reserved for the cegedim group</td><td>ET2</td></tr></tbody></table>

## What is an ITCare resource? <a href="#presentationitcare-whatisanitcareresource" id="presentationitcare-whatisanitcareresource"></a>

A resource is an infrastructure or middleware component deployed in the **cegedim.cloud** Information System.

It can only belong to one Service (see [#presentationitcare-howaremyitcareresourcesorganized](#presentationitcare-howaremyitcareresourcesorganized "mention") for the definition of a Service)

A resource is systematically defined by the following properties:

* an **id**: unique identifier of the resource.
* a **type**: the type of the resource e.g. virtual instance, Kubernetes cluster, etc.
* a **name**: more convenient to handle than an id.
* a **status**: defines the state of the resource (active, inactive).
* an **environment**: defines the type of environment of the resource (production, qa, dev, test, etc.).
* **tags**: allows you to tag your resources with customizable keys/values that are queryable.

## What are the possible statuses for resources? <a href="#presentationitcare-whatarethepossiblestatusesforresources" id="presentationitcare-whatarethepossiblestatusesforresources"></a>

Here are the possible statuses of a resource that are visible by the web UI or returned by the API:

<table><thead><tr><th width="144.33333333333331">Status</th><th width="453">Description</th><th>API code</th></tr></thead><tbody><tr><td>Active</td><td>The resource is active and the service is available.</td><td>ACTIVE</td></tr><tr><td>Preparation</td><td>The resource is being installed or configured.<br>The service is not yet available.</td><td>PREPARATION</td></tr><tr><td>Inactive</td><td>The resource is inactive and the service is unavailable.</td><td>INACTIVE</td></tr></tbody></table>

## How are my ITCare resources organized? <a href="#presentationitcare-howaremyitcareresourcesorganized" id="presentationitcare-howaremyitcareresourcesorganized"></a>

Each cegedim.cloud customer has an **Organization** that materializes its existence within our IS.

Multiple **Clouds** can be created within an organization. These allow partitioning of resources and user rights.

{% hint style="info" %}
By default, only one Cloud is defined for a new Organization.\
Additional Clouds can be created upon request.
{% endhint %}

You can therefore define, at the level of a Cloud, who has access to what and what actions can be performed.

It is therefore possible, for example, to have a Cloud that gives full power to your development teams so as not to disrupt production. Within a Cloud, resources are then grouped into **Services**.

The Services allow you to group your resources in a logical way according to several free criteria:

* The scope of an application
* By environment
* Any other free criteria: by customer for example

{% hint style="warning" %}
The Services do not allow the application of user rights restrictions.
{% endhint %}

In ITCare, the Services have dedicated pages that allow you to easily consult all the resources attached to them.

```mermaid
graph TD
    subgraph org["🏢 Organization"]
        subgraph cloud["☁️ Cloud"]
            subgraph service["🌐 Service"]
                r1["📦 Resources"]
            end
        end
    end

    style org fill:#faf6e9,stroke:#000,stroke-width:2px,color:#000
    style cloud fill:#1abc9c,stroke:#0e6655,stroke-width:2px,color:#000
    style service fill:#cfe2ff,stroke:#0066cc,stroke-width:2px,color:#000
    style r1 fill:#dde8f5,stroke:#000,stroke-width:2px,color:#000
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.cegedim.cloud/itcare/what-is-itcare/get-started-with-itcare.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.