ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Don't know if this is an error from AWS or something. I created an IAM user and gave it full admin policies. I then used this user to create an EKS cluster using the eksctl CLI but when I logging to AWS console with the root user I got the below error while trying to access the cluster nodes. Your current user or role does not have access to Kubernetes objec
Asked · Jan 20
answered · Feb 13
AWS supports IAM Roles for Service Accounts (IRSA) that allows cluster operators to map AWS IAM Roles to Kubernetes Service Accounts. To do so, one has to create an iamserviceaccount in an EKS cluster: eksctl create iamserviceaccount \ --name <AUTOSCALER_NAME> \ --namespace kube-system \ --cluster <CLUSTER_NAME> \ --attach-policy-arn <POLICY_A
Is there a way to conditionally add statement blocks in aws_iam_policy_document ? I'm looking for something like: data "aws_iam_policy_document" "policy" { statement { sid = "PolicyAlways" ... } if (var.enable_optional_policy) { statement { sid = "PolicySometimes" ... } } }
I have a scenario in which I want to have access to resources within one account from another one in AWS (cross-account access) in code. And I want to implement this access using NodeJs, implemented as lambda function and also as a long-running code on EC2. Reading how to do this online, I know I need temporary credentials generated by aws.STS , like this: c
I have a Step Function (Parent) created in a SAM/CloudFormation template that, among other things, calls another Step Function (Child). I'm following the instructions on calling Child, from Parent, using the service integration pattern . But I'm getting an IAM-related (I think) error I can't resolve when deploying via the CLI. (The error manifests in the CLI
kubernetes
terraform