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
Copy file name to clipboardExpand all lines: docs/docs/explanations/advanced-provider-configuration.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,14 +117,20 @@ amazon_web_services:
117
117
max_nodes: 5
118
118
gpu: false # Set to true if using GPU instances
119
119
launch_template:
120
-
ami_id: ami-0abcdef1234567890 # Replace with your custom AMI ID
121
-
pre_bootstrap_command: "echo 'Hello, World!'" # Command to run before the node joins the cluster
120
+
# Replace with your custom AMI ID
121
+
ami_id: ami-0abcdef1234567890
122
+
# Command to run before the node joins the cluster
123
+
pre_bootstrap_command: "echo 'Hello, World!'"
122
124
```
123
125
124
126
**Parameters:**
125
127
126
128
- `ami_id` (Optional): The ID of the custom AMI to use for the nodes in this group. If specified, the `ami_type` is automatically set to `CUSTOM`.
127
-
- `pre_bootstrap_command` (Optional): A command or script to execute on the node before it joins the Kubernetes cluster. This can be used for custom setup or configuration tasks.
129
+
- `pre_bootstrap_command` (Optional): A command or script to execute on the node before
130
+
it joins the Kubernetes cluster. This can be used for custom setup or configuration
131
+
tasks. The format should be a single string in conformation with the shell syntax.
132
+
This command is injected in the `user_data` field of the launch template. For more
133
+
information, see [User Data](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html).
128
134
129
135
:::note
130
136
If an `ami_id` is not provided, AWS will use the default Amazon Linux 2 AMI for the
0 commit comments