# es-document

Part of **ES**

# Elasticsearch Data Ingestion and Management Console Guide

## Operations Overview

| Operation | Console Entry | Prerequisites | Description |
|----------|---------------|---------------|-------------|
| Push Documents | Console > OpenSearch > Apps > [App Name] > Tables > Push Documents | AccessKey ID/Secret as environment variables, OpenSearch app and table created, C# dev environment | Navigate to document push interface for programmatic ingestion (SDK-based workflow initiated from console context) |
| Push Documents Batch | Console > OpenSearch > Applications > [Application Name] > Actions > More > Upload File | OpenSearch High-Performance Search Edition app with configured table, RAM user with required permissions | Upload a formatted file to push multiple documents in a single batch operation via the console |

## Operation Steps

### Push Documents

**Navigation**: Console > OpenSearch > Apps > [App Name] > Tables > Push Documents

**Prerequisites**:
- AccessKey ID and AccessKey secret configured as environment variables
- OpenSearch app and table already created
- C# development environment set up with .NET SDK

1. Log on to the **OpenSearch console**
   - Element: **Log on to the OpenSearch console** (link) — top navigation bar
   - Notes: Ensure you are logged in with an account that has permissions to manage OpenSearch applications.

2. In the left navigation panel, click **Apps**
   - Element: **Apps** (link) — left navigation panel

3. Find your target application in the list and click its name
   - Element: **[App Name]** (link) — applications table row

4. Navigate to **Tables** under the application details
   - Element: **Tables** (tab) — application detail header

5. Click **Push Documents** to access the ingestion interface
   - Element: **Push Documents** (button) — top-right corner of the tables page
   - Notes: This action does not open a new form in the console; it directs you to documentation or SDK setup context. Actual document pushing is performed via C# SDK as described in associated guides.

**Form Fields**:  
*Not applicable — this operation leads to SDK-based implementation rather than a console form.*

### Push Documents Batch

**Navigation**: Console > OpenSearch > Applications > [Application Name] > Actions > More > Upload File

**Prerequisites**:
- An OpenSearch High-Performance Search Edition application with a configured table
- A RAM user with the required permissions — see AliyunServiceRoleForOpenSearch and Access authorization rules

1. Log on to the **OpenSearch console**
   - Element: **Log on to the OpenSearch console** (link) — top navigation bar

2. In the left navigation panel, click **Applications**
   - Element: **Applications** (link) — left navigation panel

3. Locate your target application in the table and find the **Actions** column
   - Element: **Actions** (section) — right side of the application row

4. Click the **More** menu in the Actions column
   - Element: **More** (menu) — Actions column
   - Notes: A dropdown menu appears with additional options.

5. Select **Upload File** from the **More** menu
   - Element: **Upload File** (link) — within the More dropdown
   - Notes: A dialog opens where you can download a sample file template and upload your data file.

6. (Optional) Download the sample file to understand the required format
   - Element: **Download sample file** (link) — inside upload dialog
   - Notes: The sample file shows the correct JSON or CSV structure for batch document ingestion.

7. Choose your local file and click **Upload**
   - Element: **Choose File** (button) — file input control
   - Element: **Upload** (button) — bottom of dialog
   - Notes: After upload, the system processes the batch asynchronously. Wait for confirmation message.

**Form Fields**:  
*Not applicable — file upload uses a standard browser file picker without configurable form fields in the console.*

## FAQ

Q: Where do I find the "Push Documents" option in the console?
A: It appears under **Apps > [Your App] > Tables**, but note that this link primarily provides context for SDK-based ingestion rather than a direct upload form.

Q: Can I push documents directly through the console without using an SDK?
A: For batch operations, yes—use **Applications > [App] > Actions > More > Upload File** to submit a formatted file. Single-document pushes typically require SDKs.

Q: What file format is required for batch document upload?
A: The console provides a downloadable sample file that demonstrates the expected structure—usually JSON lines or a specific delimited format matching your table schema.

Q: Do I need special permissions to upload documents via the console?
A: Yes. Your RAM user must have permissions aligned with the **AliyunServiceRoleForOpenSearch** and explicit access to the target application and table.

Q: Can I modify documents after they’ve been pushed?
A: Yes, by pushing new documents with the same primary key and using the **UPDATE** or **DELETE** command in subsequent batch uploads or SDK calls.

## Pricing & Billing

### Billing Model
Per-request billing: each document push request is billed as one unit, regardless of the number of documents in the batch.

### Price Reference

| Tier | Input Price |
|------|-------------|
| default | 0.001 / |
| standard | 0.0001 / |

### Free Tier
 1000 

### Billing Notes

- Quota limit: 10 requests per second per account (for C# SDK path); batch uploads support up to 1000 documents per request