aws-lambda-layer-kubectl | AWS Lambda Layer with kubectl and Helm | AWS library
kandi X-RAY | aws-lambda-layer-kubectl Summary
kandi X-RAY | aws-lambda-layer-kubectl Summary
This sample code is made available under the MIT-0 license. See the LICENSE file.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of aws-lambda-layer-kubectl
aws-lambda-layer-kubectl Key Features
aws-lambda-layer-kubectl Examples and Code Snippets
Community Discussions
Trending Discussions on aws-lambda-layer-kubectl
QUESTION
I'm trying to build a cloudformation template that will deploy an EKS cluster, nodegroup and workload.
Using the following lambda layer, I've created a function that can interact with the EKS cluster; however, this only works if the function assumes the role of the user that created the cluster.
One issue I've found with this is that it isn't possible to assume the role of an SSO user in an SSO environment as AWS manages the trust policy. If I assume another role before creating the cluster and let lambda assume that role, the function works.
Unfortunately, it isn't possible to pass in a specific role to be used to create the cluster, RoleArn only provides permission for the control plane to interact with other AWS services.
I'm wondering if it would be possible to create a nested stack structure what would do something like this?
- In the main stack create a role
- Then call a nested template assuming the new role
- In the child stack a EKS cluster would be created
- In the main stack a lambda function would be created and invoked
Is this technically possible?
For reference this is what the function is currently doing.
...ANSWER
Answered 2021-Apr-19 at 08:53I was able to workaround this issue by creating and invoking a lambda function in the main stack which created a child stack after assuming the role of the eks cluster admin.
To avoid creating IAM roles in the child stack I created all of these in the main stack and then passed the ARNs into the child stack.
I hope this might be useful to someone else should they need to do something similar
Main Stack
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install aws-lambda-layer-kubectl
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page