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
Encountering an issue when trying to launch an hyperpod eks cluster with the automated shell script. It was a due to a cfn reference issue here:
We have references to PrivateRouteTable, but the instance itself is named PrivateRouteTable1.
I was able to fix it by renaming this line to PrivateRouteTable1or renaming all references to PrivateRouteTable1 to PrivateRouteTable.
Hi team,
Encountering an issue when trying to launch an hyperpod eks cluster with the automated shell script. It was a due to a cfn reference issue here:
We have references to
PrivateRouteTable
, but the instance itself is named PrivateRouteTable1.I was able to fix it by renaming this line to
PrivateRouteTable1
or renaming all references toPrivateRouteTable1
toPrivateRouteTable
.aws-do-hyperpod/Container-Root/hyperpod/impl/eks/src/cfn/hyperpod-eks-full-stack.yaml
Line 630 in 1695c1f
The text was updated successfully, but these errors were encountered: