SageMaker HyperPod Cluster Not in a VPC
The cluster runs outside your network controls, so its traffic is not subject to the rules everything else is held to.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Move SageMaker cluster into a VPC subnet.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- SageMaker Clusters on AWS
- The fix, by hand
- HyperPod VPC is set at cluster creation and cannot be changed in place.
- Create a new cluster with VpcConfig pointing at private subnets + a restrictive security group.
- Use VPC endpoints (S3, SageMaker API) to keep traffic on the AWS network.
- Migrate workloads to the VPC-attached cluster and delete the old one.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1627- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.