Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] INSTANCE_PROFILE_NAME is empty because no prefix matches #522

Closed
ysdongAmazon opened this issue Feb 6, 2023 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@ysdongAmazon
Copy link
Contributor

Important note on security disclosures: If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.

Describe the bug
in eks iam policy attachment GitHub examples, seems INSTANCE_PROFILE_NAME is generated empty because the right ec2 instance profile name does not start with eksctl-appmeshtest-nodegroup-ng (INSTANCE_PROFILE_PREFIX here).
I can make it work by manually attach the iam within console, just not sure it is only a special case for me or bug in the instruction.
https://github.com/aws/aws-app-mesh-examples/blob/main/walkthroughs/eks/o11y-xray.md

Platform
EKS, ECS, EC2, etc.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Config files, and API responses
If applicable config files and responses from our API.

Additional context
Add any other context about the problem here.

@ysdongAmazon ysdongAmazon added the bug Something isn't working label Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant