You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`--region`| TEXT | No | AWS region of the stack |
129
130
|`--debug`| FLAG | No | Enable debug logging |
130
131
132
+
133
+
#### Delete Cluster Stack
134
+
135
+
Delete a HyperPod cluster stack. Removes the specified CloudFormation stack and all associated AWS resources. This operation cannot be undone.
136
+
137
+
```bash
138
+
hyp delete cluster-stack <stack-name>
139
+
```
140
+
141
+
| Option | Type | Description |
142
+
|--------|------|-------------|
143
+
|`--region <region>`| Required | The AWS region where the stack exists. |
144
+
|`--retain-resources S3Bucket-TrainingData,EFSFileSystem-Models`| Optional | Comma-separated list of logical resource IDs to retain during deletion (only works on DELETE_FAILED stacks). Resource names are shown in failed deletion output, or use AWS CLI: `aws cloudformation list-stack-resources STACK_NAME --region REGION`. |
145
+
|`--debug`| Optional | Enable debug mode for detailed logging. |
146
+
147
+
131
148
## hyp list-cluster
132
149
133
150
List SageMaker HyperPod clusters with capacity information.
Copy file name to clipboardExpand all lines: doc/cli/inference/cli_inference.md
+37-4Lines changed: 37 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,8 @@
4
4
5
5
Complete reference for SageMaker HyperPod inference parameters and configuration options.
6
6
7
-
```{note}
8
-
**Region Configuration**: For commands that accept the `--region` option, if no region is explicitly provided, the command will use the default region from your AWS credentials configuration.
Copy file name to clipboardExpand all lines: doc/cli/training/cli_training.md
+38-4Lines changed: 38 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,8 @@
5
5
6
6
Complete reference for SageMaker HyperPod PyTorch training job parameters and configuration options.
7
7
8
-
```{note}
9
-
**Region Configuration**: For commands that accept the `--region` option, if no region is explicitly provided, the command will use the default region from your AWS credentials configuration.
The following is a step-by-step guide of creating a jumpstart endpoint with `hyp-jumpstart-endpoint` template for init experience. In order to create a custom endpoint, you can use `hyp-custom-endpoint` template during the init command call. The init experience is the same across templates.
22
+
23
+
### 1. Start with a Clean Directory
24
+
25
+
It\'s recommended to start with a new and clean directory for each
26
+
endpoint configuration:
27
+
28
+
```bash
29
+
mkdir my-endpoint
30
+
cd my-endpoint
31
+
```
32
+
33
+
### 2. Initialize a New Endpoint Configuration
34
+
35
+
36
+
`````{tab-set}
37
+
````{tab-item} CLI
38
+
``` bash
39
+
hyp init hyp-jumpstart-endpoint
40
+
```
41
+
````
42
+
`````
43
+
18
44
```{note}
19
-
**Region Configuration**: For commands that accept the `--region` option, if no region is explicitly provided, the command will use the default region from your AWS credentials configuration.
45
+
In order to create custom endpoint, you can simply use `hyp init hyp-custom-endpoint`.
20
46
```
21
47
22
-
## Creating Inference Endpoints
48
+
This creates three files:
49
+
50
+
-`config.yaml`: The main configuration file you\'ll use to customize
51
+
your endpoint
52
+
-`k8s.jinja`: A reference template for parameters mapping in kubernetes payload
53
+
-`README.md`: Usage guide with instructions and examples
54
+
55
+
56
+
57
+
### 3. Configure Your Endpoint
58
+
59
+
You can configure your endpoint in two ways:
60
+
61
+
**Option 1: Edit config.yaml directly**
62
+
63
+
The config.yaml file contains key parameters like:
64
+
65
+
```yaml
66
+
template: hyp-jumpstart-endpoint
67
+
version: 1.0
68
+
model_id:
69
+
instance_type:
70
+
endpoint_name:
71
+
```
72
+
73
+
**Option 2: Use CLI command (Pre-Deployment)**
74
+
75
+
`````{tab-set}
76
+
````{tab-item} CLI
77
+
``` bash
78
+
hyp configure --endpoint-name your-endpoint-name
79
+
```
80
+
````
81
+
`````
82
+
83
+
```{note}
84
+
The `hyp configure` command only modifies local configuration files. It
85
+
does not affect existing deployed endpoints.
86
+
```
87
+
88
+
### 4. Create the Endpoint
89
+
90
+
`````{tab-set}
91
+
````{tab-item} CLI
92
+
``` bash
93
+
hyp create
94
+
```
95
+
````
96
+
`````
97
+
98
+
This will:
99
+
100
+
- Validate your configuration
101
+
- Create a timestamped folder in the `run` directory
102
+
- Initialize the endpoint creation process
103
+
104
+
105
+
106
+
## Creating Inference Endpoints -- CLI/SDK
23
107
24
108
You can create inference endpoints using either JumpStart models or custom models:
0 commit comments