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.
Please contact your Service Delivery Management or the commercial team at cegedim.cloud.
ITCare authentication is based on an e-mail address and a password that comply with the standards of the cegedim security policy.
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.
ITCare privileges are broken down into roles assigned to profiles.
Profiles are assigned to users.
MFA must be configured and is mandatory for the following roles:
Manage maintenances
Modify resources
Manage resources
This non-exhaustive table describes the basic actions allowed by profile:
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
Here is the list of regions available to our customers:
A resource is an infrastructure or middleware component deployed in the cegedim.cloud Information System.
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.
Here are the possible statuses of a resource that are visible by the web UI or returned by the API:
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.
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
The Services do not allow the application of user rights restrictions.
In ITCare, the Services have dedicated pages that allow you to easily consult all the resources attached to them.