Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

dc app performance toolkit setup error

Eldan Vaknin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 26, 2023

I'm trying to run the app performance toolkit according to this guide.

It seems to work up to the point of creating the cluster and then it fails in creating an EKS Node Group.
I use an admin account for my AWS, and checked specifically that I have full access permissions for EKS, but the error looks like a permissions error.

Has anyone encountered anything like this?

Error: creating EKS Node Group (atlas-bamboo-build2secure-cluster:appNode-m5_2xlarge-20231126084423785900000011): InvalidRequestException: You are not authorized to launch instances with this launch template.

1 answer

1 vote
Khushboo Gupta
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 8, 2024

Hello @Eldan Vaknin 

Welcome to the Atlassian Community!

Based on the error message you've shared, it appears the issue is with launching instances using a specified launch template, rather than with EKS (Elastic Kubernetes Service) permissions directly. This can happen due to a few reasons, even if you're using an admin account. Here are steps and aspects to check and potentially rectify the problem:

  • Even though you're using an admin account, it's worth double-checking the IAM  policies attached to your user or role. Specifically, ensure that the permissions include actions related to EC2 instances and launch templates.

  • The error specifically mentions an issue with the launch template.
    • Verify that the IAM role or user has permissions to use the specified launch template.
    • Ensure the launch template referred to by your EKS Node Group actually exists.
  • If the launch template specifies a custom AMI (Amazon Machine Image), ensure that your account has the permissions to use this AMI.

Incase the everything seems to be correctly configured, Check AWS CloudTrail logs for the failed operation. And Try manually creating an instance using the problematic launch template via the AWS CLI or AWS Management Console. This can help isolate whether the issue is with the launch template itself or the way EKS is attempting to use it.

Hope it helps!

Regards,

Khushboo Gupta

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events