# airec-deploy

Part of **AIREC**

<!-- intent-backlink:auto -->

> 💡 **Path Selection**: This skill is one implementation path for [Deploy AIRec service](../../intent/airec-deploy-service/SKILL.md). If you're unsure which path to take, check the routing skill first.

# AIRec Deployment Console Guide

## Operations Overview

| Operation | Console Entry | Prerequisites | Description |
|----------|---------------|---------------|-------------|
| Deploy AIRec Service via ASI Console | Console > AIRec > Deployments > Create Deployment | - An active Apsara Stack ASI account<br>- Valid permissions to create and manage deployments<br>- Network access to the ASI console | Launch a new AIRec service instance using predefined or custom deployment templates |

## Operations Steps

### Deploy AIRec Service via ASI Console

**Navigation**: Console > AIRec > Deployments > Create Deployment

**Prerequisites**:
- An active Apsara Stack ASI account
- Valid permissions to create and manage deployments
- Network access to the ASI console

1. Navigate to the Deployments page and click the **Create Deployment** button in the top-right corner  
   - Element: **Create Deployment** (button) — top-right corner of the Deployments page  
   - Notes: A new configuration form will open in the main content area

2. Select a deployment template from the **Deployment Template** dropdown  
   - Element: **Deployment Template** (dropdown) — main content area  
   - Notes: Available options include Standard, High Availability, and Custom configurations

3. Enter a unique name in the **Deployment Name** field and select a region from the **Region** dropdown  
   - Element: **Deployment Name** (text_input) — form fields section  
   - Element: **Region** (dropdown) — form fields section  
   - Notes: The selected region must support AIRec services. Supported regions include China (Hangzhou), International (Singapore), and China (Shanghai)

4. Review the configuration summary at the bottom of the form and click **Confirm and Deploy**  
   - Element: **Confirm and Deploy** (button) — bottom of form  
   - Notes: Deployment may take several minutes to complete. Do not close the browser during this process

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Deployment Name | text_input | Yes | — | Unique identifier for the deployment instance |
| Deployment Template | dropdown | Yes | Standard, High Availability, Custom | Predefined configuration for deployment setup |
| Region | dropdown | Yes | China (Hangzhou), International (Singapore), China (Shanghai) | Geographic location where the deployment will be hosted |

## FAQ

Q: Where can I find the Deployments page in the ASI console?  
A: From the console homepage, navigate to AIRec > Deployments in the left-side menu.

Q: What happens if I leave the Deployment Name field empty?  
A: The **Confirm and Deploy** button will remain disabled until a valid name is entered, as this field is required.

Q: Can I change the deployment template after clicking Confirm and Deploy?  
A: No. Once deployment starts, the template cannot be modified. You must delete the deployment and create a new one to use a different template.

Q: Do I need special permissions to deploy AIRec services?  
A: Yes. Your account must have permissions to create and manage deployments in the target region.

Q: How long does a deployment typically take?  
A: Deployment usually completes within several minutes. The exact time depends on the selected template and system load.

## Pricing & Billing

### Billing Model
Billing is based on per-instance-hour usage. Charges accrue only while the deployment is running.

### Price Reference

| Tier | Input Price | Output Price |
|------|-------------|--------------|
| Standard | 0.05 / | 0.08 / |
| High Availability | 0.12 / | 0.15 / |

### Free Tier
Monthly free trial quota of 10 hours.

### Billing Notes
- Billed by actual runtime, with a minimum billing unit of 1 hour  
- Charges stop immediately when the deployment is stopped  
- Each account can have up to 5 active deployments simultaneously