Skip to content

Commit 80f51fb

Browse files
authored
Merge pull request #62577 from EricPonvelle/OSDOCS-6130_IMDS-OSD
OSDOCS-6130: Added IMDS information to OSD
2 parents e7128f2 + 3d17d8d commit 80f51fb

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

modules/osd-create-cluster-ccs.adoc

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,6 +166,23 @@ PVs created by using any other storage class are still encrypted, but the PVs ar
166166
After your cluster is created, you can change the number of compute nodes in your cluster, but you cannot change the compute node instance type in a machine pool. The number and types of nodes available to you depend on your {product-title} subscription.
167167
====
168168

169+
. Choose your preference for the Instance Metadata Service (IMDS) type, either using both IMDSv1 and IMDSv2 types or requiring your EC2 instances to use only IMDSv2. You can access instance metadata from a running instance in two ways:
170+
+
171+
* Instance Metadata Service Version 1 (IMDSv1) - a request/response method
172+
* Instance Metadata Service Version 2 (IMDSv2) - a session-oriented method
173+
+
174+
[IMPORTANT]
175+
====
176+
The Instance Metadata Service settings cannot be changed after your cluster is created.
177+
====
178+
+
179+
[NOTE]
180+
====
181+
IMDSv2 uses session-oriented requests. With session-oriented requests, you create a session token that defines the session duration, which can range from a minimum of one second to a maximum of six hours. During the specified duration, you can use the same session token for subsequent requests. After the specified duration expires, you must create a new session token to use for future requests.
182+
====
183+
+
184+
For more information regarding IMDS, see link:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html[Instance metadata and user data] in the AWS documentation.
185+
169186
. Optional: Expand *Edit node labels* to add labels to your nodes. Click *Add label* to add more node labels and select *Next*.
170187

171188
. On the *Network configuration* page, select *Public* or *Private* to use either public or private API endpoints and application routes for your cluster.

0 commit comments

Comments
 (0)