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:
Go to '...'
Click on '....'
Scroll down to '....'
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.
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:
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.