AWS nova documentation change
Summary
Specified that SageMaker HyperPod execution roles require tagging for Nova Forge access and updated infrastructure setup instructions
Security assessment
Clarifies role tagging requirements without changing security controls or documenting security features; operational guidance only.
Diff
diff --git a/nova/latest/nova2-userguide/nova-forge-access.md b/nova/latest/nova2-userguide/nova-forge-access.md index 28837f5c3..1cad873ef 100644 --- a//nova/latest/nova2-userguide/nova-forge-access.md +++ b//nova/latest/nova2-userguide/nova-forge-access.md @@ -40 +40 @@ To get the Nova Forge documents follow the below steps: - 4. Tag your execution role with the `forge-subscription` tag. This tag is required to access Nova Forge features and checkpoints. Add the following tag to your execution role: + 4. Tag your SageMaker HyperPod execution role with the `forge-subscription` tag. This tag is required to access Nova Forge features and checkpoints. Add the following tag to your execution role: @@ -153 +153 @@ Flow: The account user must reach out to the account admin to request admin acce -Set up the necessary infrastructure by following the [workshop instructions](https://catalog.us-east-1.prod.workshops.aws/workshops/dcac6f7a-3c61-4978-8344-7535526bf743/en-US) for configuring the environment with Forge-enabled features. +Set up the necessary SageMaker HyperPod infrastructure by following the [workshop instructions](https://catalog.us-east-1.prod.workshops.aws/workshops/dcac6f7a-3c61-4978-8344-7535526bf743/en-US) for configuring the environment with Forge-enabled features.