DataArts Lake Formation
DataArts Lake Formation
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- Developer Guide
-
API Reference
- Before You Start
- API Overview
- API Calling
-
API
-
Console
- Instance Management
- Job Management
-
Service Authorization Management
- Granting Permissions for Accessing Other Cloud Services
- Querying Cloud Service Access Permissions
- Registering a Tenant Agreement
- Querying whether a Tenant Has Registered an Agreement
- Deleting a Tenant Agreement
- Registering a Tenant Agreement
- Querying whether a Tenant Has Registered an Agreement
- Deleting a Tenant Agreement
- Querying the Current System Agreement
- OBS Management
- Access Management
- Specification Management
- Quota Management Service
- Tag Management Service
- Agency Management
- Alarm Management
- Metadata Management
- Location
-
LakeCat
- Function Management
- Catalog Management
- Database Management
- Table Management
- Data Table Statistics
- Zone-based Management
- Partition Statistics
- Authorization Management
- User Group Management
- Metadata Statistics
-
Role Management
- Creating a Role
- Listing Roles on Different Pages by Condition
- Deleting a Role
- Obtaining a Role
- Modifying a Role
- Listing All Role Names
- Querying the Users or User groups Under a Role
- Adding One or More Users or User Groups to a Role
- Removing One or More Users or User Groups from a Role
- Updating the Entities in a Role
- Credential Management
- Configuration Management
- User
-
Console
- Application Examples
- Permissions and Supported Actions
- Appendix
- FAQs
- General Reference
On this page
Help Center/
DataArts Lake Formation/
Service Overview/
Security/
Asset Identification and Management
Copied.
Asset Identification and Management
Asset Identification
- Asset information: metadata and data permission policy information.
- Account information: Users are unaware of the account information in LakeFormation.
- API mapping table: For details, see API Reference.
- Tenant resources: LakeFormation needs to read user group and user information, create and delete OBS file directories, and access OBS tag permission APIs.
Recommended Security Configuration
N/A
Infrastructure Security
- LakeFormation instances run in a cross-AZ cluster. The failure of a single AZ does not affect the running of LakeFormation instances.
- LakeFormation instances use cross-AZ highly reliable storage media to store data persistently. The failure of a single AZ does not cause data loss of LakeFormation instances.
Parent topic: Security
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot