Skip to main content

Identity & Access Management

Control panel

In Selectel, you can manage user access to the infrastructure. This is accomplished by using Identity and Access Management (IAM), which checks every request and ensures that only authorized users perform operations on resources.

User access permissions to resources are set at the level of user types and roles. Only the Account Owner or users with the iam_admin role can manage users: add them, modify their data and roles. To simplify user management, you can combine them into groups.

By default, two-factor authentication is enabled for all users after registration and profile completion. With two-factor authentication, you need to enter your password and a one-time confirmation code to log in to your account. The confirmation code can be received through the authenticator app or by email to the address you specified in your profile. Two-factor authentication can only be disabled by the Account Owner. We do not recommend disabling two-factor authentication to avoid risks associated with account compromise.

You can also configure authentication in the control panel using Single Sign-On (SSO). To do this, use federations — a centralized service for managing organizational structure, setting up integration with the employee directory, and controlling user access to company resources. When using federations, user data is stored with your identity provider — Identity Provider (e.g., Keycloak, ADFS, and other SAML-compliant providers).

By default, access to the control panel is allowed from any IP address. However, the Account Owner and users with the iam.admin role can set restrictions — users will be able to log in to the account only from IP addresses and subnets that have been added to the allowed list.

If you need to share access to the control panel or resources with someone, do not share your credentials. The Account Owner and users with the iam.admin role can create an additional user for control panel access or a service user for programmatic access. For more details, see the General access management in Selectel products guide.

Cloud and dedicated servers

You can connect to cloud servers via the console in the control panel, and to dedicated servers — via the KVM console. If you connect to the server via other CLIs, to ensure secure remote access to the infrastructure, connect to the server:

  • via SSH — if you have a Linux server;
  • or via RDP — if you have a Windows server.

Configure SSH connection

For secure connection to a cloud or dedicated Linux server, use SSH keys instead of a login and password. This is a key pair: a private key and a public key. The private key is stored on your local computer, while the public key is placed on the server. After configuring the SSH connection and disabling password access, only devices storing the private key will be able to connect to the server, and the server will be protected from brute-force attacks (bruteforce).

For each administrator, you need to create an SSH key pair and place the public key on the cloud or dedicated server. When creating the key, specify a passphrase (passphrase) for additional security.

After creating the SSH keys, create a user and configure the SSH connection — when creating a server using user data or for an existing server via CLI. If you use servers with a public IP address, the safest strategy is to configure security settings at the server creation stage using user data.

You can specify user data for a cloud and dedicated server.

Example of creating a user and configuring SSH connection using user data for Ubuntu 24.04 LTS 64-bit.

#cloud-config
users:
- name: admin
sudo: ['ALL=(ALL) NOPASSWD:ALL']
groups: sudo
shell: /bin/bash
lock_passwd: true
ssh_authorized_keys:
- <<public_ssh_key> admin@test
ssh_pwauth: false

package_update: true

packages:
- ufw

runcmd:
- sed -i 's/^#Port 22/Port 2222/' /etc/ssh/sshd_config
- sed -i 's/^#PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config
- sed -i 's/^PermitRootLogin prohibit-password/PermitRootLogin no/' /etc/ssh/sshd_config
- sed -i 's/^#PubkeyAuthentication yes/PubkeyAuthentication yes/' /etc/ssh/sshd_config
- systemctl restart ssh
- ufw allow 2222/tcp
- ufw --force enable
- reboot

Where:

  • name: admin — creates the admin user;
  • sudo: ['ALL=(ALL) NOPASSWD:ALL'] — allows the user to run commands via sudo without a password prompt;
  • groups: sudo — adds the user to the sudo group;
  • lock_passwd: true — blocks password login for the admin user;
  • <public_ssh_key> admin@test in the ssh_authorized_keys section — adds the public SSH key you created earlier. Starts with ssh-rsa.
  • ssh_pwauth: false — disables password login for all users. Server access will only be possible via an SSH key, and password authentication will be completely disabled;
  • package_update: true — updates the apt library;
  • packages: ufw — installs the UFW (Uncomplicated Firewall) firewall, which is needed to restrict access to the SSH port;
  • commands with sed -i in the runcmd section — change the standard port 22 to 2222, disable password login and root user connection, and enable key-based authentication.

Recommendations for using RDP connection

To securely connect via RDP to a cloud or dedicated server running Windows, do not use a public IP address. We recommend using a VPN for access to such servers — for example, OpenVPN, WireGuard, or IKEv2/IPsec. To do this, place cloud and dedicated servers in private subnets that are accessible through a separate VPN gateway, or deploy a VPN gateway on the same server.

Use a separate account for each server administrator.

Additional security tools

To protect servers from unauthorized access, we recommend using additional security tools. Examples of free tools:

Certified security features

To further protect servers and comply with regulatory requirements if necessary, you can use additional certified tools for protection against unauthorized access, provided as part of a separate service:

Two-factor authentication

To protect your services from unauthorized access, we recommend using two-factor authentication for additional user identity verification. The service is provided as licenses for using the Multifactor solution.

The Multifactor solution meets regulatory requirements:

  • is included in the Unified Register of Russian Software (No. 7046);
  • complies with the international PCI DSS standard;
  • has an FSTEC certificate (No. 5039).

Managed Kubernetes

In a Managed Kubernetes cluster, you can manage access to virtual resources using the RBAC Authorization (RBAC) mechanism. RBAC allows you to assign user roles — create different namespaces for different applications and configure user access to pods in the corresponding namespace.

Managed Databases

In all DBMSs except Redis, you can manage database users and their privileges. Read more about user management in the instructions for PostgreSQL, PostgreSQL for 1C, PostgreSQL TimescaleDB, PostgreSQL PGVector, MySQL semi-sync, MySQL sync, and Kafka.

One user is automatically created for the Redis DBMS. The password for this user is set when creating the cluster, and after the cluster is created, it can be changed.

S3

Access to S3 resources is regulated by:

When an S3 action request is received, access is first checked against the role model. If the role model allows access, the access policy is checked; if not, access is denied. An access policy denies everything that is not explicitly allowed by the policy rules.

For access via API or FTP, issue keys.

To access objects in a bucket via a custom domain over HTTPS, you need to add a TLS (SSL) certificate. You can issue a certificate with any provider. You can manage certificates through the control panel or Object Storage API .