Unit 2: Initializing OU

Congratulations! Now you’ve logged into the EnOS Management Console. You can now initialize your OU to make it ready for your project, including OU profile and security settings, user and permission management, environment information, resource planning, and purchasing applications.

Managing OU Profile and Security Settings

After logging in the EnOS Management Console with the administrator account, you can go to the IAM > Organization Profile page to edit the basic information of your OU and change your user name as needed. For more information, see Managing the Organization Information and Organization Accounts.

To change the security settings for your organization, go to the IAM > Security Setting page and update the password policy, login IP restrictions, and session expiration time as needed. For more information, see Setting the Security Options.

Managing Users and Permissions

To enable collaboration with multiple users, you can create 3 user account types, ordinary users (internal users within the OU), external users (imported from another OU), and LDAP users. To secure your assets and data, EnOS enforces access control of users:

  • At the service level, so that a user would need to request proper access from the OU administrator to be able to read, write, or control objects in a service.
  • At the asset level, so that a user can only access the assets that are authorized to the user.

Go to the IAM > User page to create user accounts and assign access permission for users. For information about how to manage users and user permissions, , see Creating and Managing Users.

Getting Environment Information

To connect your devices to EnOS through MQTT, consume the subscribed asset data, or invoke API service, you will need to get the environment information of EnOS.

The environment information of EnOS varies with the cloud region and instance where EnOS is deployed. Log in EnOS Management Console and go to Help > Environment List in the upper right corner to get the environment information.

Planning Resource

Before you start your project on EnOS, you will first need to evaluate your volume of devices, data to be uploaded into EnOS, and the computing scale you need. This would help you determine how much computing and storage resource you will need to request to support your project.

Based on your business requirement, you can plan for the following resources:

Resource Name Function Description
Stream Data Processing The specification of the Stream Data Processing resource is defined by the calculation capacity of the streaming engine, which refers to the number of data points that can be processed every second. By estimating the number of connected devices and measuring points, you can decide how much computing resource you will need to apply for.
Time Series Database To store time series data that is ingested from devices for processing or application development, you need to apply for Time Series Database resource, which includes the write capacity and the storage space.
Batch Data Processing Computing capability for offline data analytics jobs. More specifically, Batch Data Processing resource is for data warehouse processing, such as hive/spark/mapreduce tasks in Data IDE. Batch Data Processing resource can be requested based on computing unit (CU), with two kinds of computing specifications (computing intensive and memory intensive).
Data Warehouse Storage A subject-oriented and integrated data storage for Hive tables that are created in the data warehouse. Select the appropriate storage size according to actual business requirements (10 ~ 1,000G).
Data Explorer Before using the data explorer notebook to develop scripts for data processing and analysis, you will need to request the data explorer sandbox resource. Currently, you can request 3 data explorer sandbox instances for different data analysis scenarios.
File Storage HDFS HDFS is used for big data analysis and storage scenarios. Data stored in File Storage HDFS can be accessed through creating Hive external tables. Select the appropriate storage size according to actual business requirements (10 ~ 1,000G).

For details about the computing and storage resource specification, see Resource Specification.