Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
SecMaster
SecMaster
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Buying SecMaster
- Authorizing SecMaster
- Viewing Security Overview
- Workspaces
- Viewing Purchased Resources
- Security Situation
- Resource Manager
- Risk Prevention
- Threat Operations
- Security Orchestration
-
Playbook Overview
- Ransomware Incident Response Solution
- Attack Link Analysis Alert Notification
- HSS Isolation and Killing of Malware
- Automatic Renaming of Alert Names
- Auto High-Risk Vulnerability Notification
- Automatic Notification of High-Risk Alerts
- Auto Blocking for High-risk Alerts
- Real-time Notification of Critical Organization and Management Operations
-
Settings
- Data Integration
-
Log Data Collection
- Data Collection Overview
- Adding a Node
- Configuring a Component
- Adding a Connection
- Creating and Editing a Parser
- Adding and Editing a Collection Channel
- Managing Connections
- Managing Parsers
- Managing Collection Channels
- Viewing Collection Nodes
- Managing Nodes and Components
- Partitioning a Disk
- Logstash Configuration Description
- Connector Rules
- Parser Rules
- Upgrading the Component Controller
- Customizing Directories
- Permissions Management
- Key Operations Recorded by CTS
-
Best Practices
-
Log Access and Transfer Operation Guide
- Solution Overview
- Resource Planning
- Process Flow
-
Procedure
- (Optional) Step 1: Buy an ECS
- (Optional) Step 2: Buy a Data Disk
- (Optional) Step 3: Attach a Data Disk
- Step 4: Create a Non-administrator IAM User
- Step 5: Configure Network Connection
- Step 6: Install the Component Controller (isap-agent)
- Step 7: Install the Log Collection Component (Logstash)
- (Optional) Step 8: Creating a Log Storage Pipeline
- Step 9: Configure a Connector
- (Optional) Step 10: Configure a Log Parser
- Step 11: Configure a Log Collection Channel
- Step 12: Verify Log Access and Transfer
- Credential Leakage Response Solution
-
Log Access and Transfer Operation Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Alert Management
- Incident Management
- Indicator Management
- Playbook Management
- Alert Rule Management
- Playbook Version Management
- Playbook Rule Management
- Playbook Instance Management
- Playbook Approval Management
- Playbook Action Management
- Incident Relationship Management
- Data Class Management
- Workflow Management
- Data Space Management
- Pipelines
- Workspace Management
- Metering and Billing
- Metric Query
- Baseline Inspection
- Appendix
- FAQs
On this page
How Do I Release an ECS or VPC Endpoint?
Updated on 2024-12-26 GMT+08:00
To enable log data collection, you are required to buy ECSs for collecting logs and configure VPC endpoints for establishing connections with and managing collection nodes.
- ECSs are billed. For details about ECS pricing, see Billing Overview.
- VPC endpoints are billed. For details, see VPC Endpoint User Guide.
If you no longer need log data collection or unsubscribe from SecMaster, you need to manually release the ECSs and VPC endpoints you create for log data collection, or they will continue to be billed. Perform the following steps:
Releasing ECS and VPC Endpoint Resources
- Log in to the management console.
- Click
in the upper left corner of the management console and select a region or project.
- Release the ECS used for log data collection.
- In the upper left corner of the page, click
and choose Compute > Elastic Cloud Server.
- In the resource list, locate the row that contains the target ECS, choose More > Unsubscribe or More > Delete in the Operation column.
Figure 1 Unsubscribing from an ECS
- In the dialog box displayed, unsubscribe from or delete the ECS as prompted.
- In the upper left corner of the page, click
- Release the VPC endpoints used to connect and manage collection nodes.
- Click
in the upper left corner of the page and choose Security & Compliance > SecMaster.
- In the navigation pane on the left, choose Workspaces > Management. In the workspace list, click the name of the target workspace.
- In the navigation pane on the left, choose Settings > Components.
- Deregister a node.
- On the Nodes tab, locate the row that contains the target node and click Deregister in the Operation column.
- In the displayed dialog box, click OK.
- Delete the VPC endpoint.
- On the Nodes page, click Create. On the Create Node slide-out panel, select a network node.
- In the network channel list, click Delete.
Figure 2 Deleting a node
- In the displayed dialog box, click OK.
- Check whether there are unreleased VPC endpoints created by SecMaster for log data collection.
- In the upper left corner of the page, click
and choose Networking > VPC Endpoint.
- In the VPC endpoint search box, enter isap and press Enter to search for VPC endpoints related to SecMaster data collection.
- Check whether there are unreleased VPC endpoints created by SecMaster for log data collection.
- In the upper left corner of the page, click
- Check whether there are any VPC endpoints related to SecMaster are still being charged.
- If yes, contact technical support.
- If no, no further action is required.
- Click
Parent topic: Data Collection
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.