Security Management #
Cluster Eco-tool Security #
SphereEx-Boot Security #
Install using a non-root user.。
SphereEx-Console Security #
- Installed using a non-root user.
- HTTPS access support.
- Link to the user permission system.
Cluster Component Security #
- Installed with a non-root user.
- Access to components without permission restrictions.
Cluster Security #
- Installed with a non-root user.
- Cluster access security: link to compute node run logs.
- Link to cluster privilege system.
Data security #
Security of tools, components, configuration data storage data of the cluster
| Tools/Components | Data Storage Security |
|---|---|
| SphereEx-Boot | No data storage |
| SphereEx-Console | Storage is the underlying database, master-slave configuration is recommended |
| Governance Center | High availability guarantee for the component itself |
| Log Center | High availability guarantee for the component itself |
| Monitoring Center | High availability guarantee for the component itself |
| Computing Nodes | Stateless without high availability |
| Storage Nodes | High availability guarantee for the component itself |
Access Security #
Supports SSL access from APP to SphereEx-DBPlusEngine-Proxy. Supports SSL configuration from SphereEx-DBPlusEngine-Proxy to the database. URL configuration example: jdbc:mysql://localhost:3306/testdb?useSSL=false. SSL is not supported for cluster access from Apps. Access to SphereEx-Console supports HTTPS, and users need to provide their own certificates. Supports SSL access from SphereEx-Console to SphereEx-DBPlusEngine-Proxy.