Hyperpod EKS cfn stack reference issue

Open Beginner friendly
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
62/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
aws, shell
Domain
cloud, infrastructure

Research direction

Open Container-Root/hyperpod/impl/eks/src/cfn/hyperpod-eks-full-stack.yaml around line 630 and inspect the PrivateRouteTable references against the declared resource name. Apply the consistent naming correction, then run the automated shell launch for an HyperPod EKS cluster to confirm the CloudFormation reference error is resolved.

Written by the indexing model from the issue text.

Description

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 PrivateRouteTable1or renaming all references to PrivateRouteTable1 to PrivateRouteTable.

https://github.com/aws-samples/aws-do-hyperpod/blob/1695c1fd07c714b4fff216443d873a6367802085/Container-Root/hyperpod/impl/eks/src/cfn/hyperpod-eks-full-stack.yaml#L630

Dominant language
Shell
Stars
26
Forks
9
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/aws-do-hyperpod

All issues in aws-samples/aws-do-hyperpod

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.