• f

    famous-leather-72830

    3 months ago
    Hey everyone! Sorry if it's double posting, but though it'd be more appropriate to ask here. Is it possible to create an EKS managed node group via
    eks.ManagedNodeGroup
    from
    @pulumi/eks
    in a separate project from where the cluster was created (via
    eks.Cluster
    from
    @pulumi/eks
    )? From what it looks like in the API docs and the code itself, ManagedNodeGroup requires a direct cluster object, and its various properties, as well as it uses the same cluster for the
    parent
    property. I have tried a magnitude of things to simulate this behaviour via
    StackReference
    kubeconfig and providers, but to no avail. I am at my wit's end quite frankly. references:https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/nodegroup.ts#L842 https://www.pulumi.com/docs/guides/crosswalk/aws/eks/
    f
    1 replies
    Copy to Clipboard
  • w

    wide-finland-25364

    3 months ago
    I created an EKS cluster on
    VPC-1
    , but I want to move that EKS cluster into
    default-VPC
    - is it as simple as 1. remove VPC-related codes from pulumi 2. import VPC ID - https://www.pulumi.com/registry/packages/aws/api-docs/ec2/vpc/#import Or is it more complicated than that?
    w
    1 replies
    Copy to Clipboard
  • m

    mammoth-planet-78700

    3 months ago
    Hello. I feel like this is probably really straight forward, but I’m not getting it 🙂 does somebody have an example of an
    s3.BucketTagArrayInput
    with go?
    m
    g
    4 replies
    Copy to Clipboard
  • s

    sparse-spring-91820

    3 months ago
    Is it possible to create
    Web identity
    IAM role type (as shown on the screenshot below) using Pulumi? I don’t see type option under the RoleArgs. I need to create web identity role type and select custom identity provider needed to enable eks cluster autoscaling
    s
    1 replies
    Copy to Clipboard
  • v

    victorious-engine-64347

    3 months ago
    I am getting this error. I created new aws account and tried to deploy same app and there is no error for new aws account. I think I should do something in my aws account.
    v
    b
    3 replies
    Copy to Clipboard
  • t

    thousands-hairdresser-72380

    3 months ago
    Hello! I’m consistently getting a Fargate Task Definition marked as needing replacement although nothing has changed. When I inspect the details, it just shows:
    ++aws:ecs/taskDefinition:TaskDefinition: (create-replacement)
                        [id=[REDACTED]-fg-task-def-47240670]
                        [urn=urn:pulumi:[REDACTED]::app::[REDACTED]:[REDACTED]$[REDACTED]:project$awsx:x:ecs:FargateTaskDefinition$aws:ecs/taskDefinition:TaskDefinition::[REDACTED]-fg-task-def]
                        [provider=urn:pulumi:[REDACTED]::app::pulumi:providers:aws::default_4_33_0::ac3e215e-84ad-45ed-a381-3d1b538f794b]
                      ~ containerDefinitions: [secret] => [secret]
                    +-aws:ecs/taskDefinition:TaskDefinition: (replace)
                        [id=[REDACTED]-fg-task-def-47240670]
                        [urn=urn:pulumi:[REDACTED]::app::[REDACTED]:[REDACTED]$[REDACTED]:[REDACTED]$awsx:x:ecs:FargateTaskDefinition$aws:ecs/taskDefinition:TaskDefinition::[REDACTED]-fg-task-def]
                        [provider=urn:pulumi:[REDACTED]::app::pulumi:providers:aws::default_4_33_0::ac3e215e-84ad-45ed-a381-3d1b538f794b]
                      ~ containerDefinitions: [secret] => [secret]
    I’ve also tried
    --diff -j
    , but all I got was
    "[secret]"
    under
    containerDefinitions
    . I then tried
    -v 11 --logtostderr --logflow
    , but the output was a bit hard to use. Any help would be greatly appreciated. Thank you!
  • r

    rich-analyst-97500

    3 months ago
    Hi, how to fix the error:
    InvalidParameterValue: No Environment found for EnvironmentId = xxx
    ? I have an application so far and it true that there’s no environments in AWS console. Is there anything I’ve missed? The following is my env setting
    elasticbeanstalk.NewEnvironment(ctx, "EBEnv", &elasticbeanstalk.EnvironmentArgs{
    		Application:       eb.Name,
    		SolutionStackName: pulumi.String("64bit Amazon Linux 2 v5.5.3 running Node.js 16"),
    		Settings: elasticbeanstalk.EnvironmentSettingArray{
    			&elasticbeanstalk.EnvironmentSettingArgs{
    				Namespace: pulumi.String("aws:ec2:vpc"),
    				Name:      pulumi.String("VPCId"),
    				Value:     vpc.ID(),
    			},
    			&elasticbeanstalk.EnvironmentSettingArgs{
    				Namespace: pulumi.String("aws:ec2:vpc"),
    				Name:      pulumi.String("Subnets"),
    				Value:     sn[0].ID(),
    			},
    			&elasticbeanstalk.EnvironmentSettingArgs{
    				Namespace: pulumi.String("aws:autoscaling:launchconfiguration"),
    				Name:      pulumi.String("IamInstanceProfile"),
    				Value:     pulumi.String("aws-elasticbeanstalk-ec2-role"),
    			},
    		},
    		Tags: pulumi.StringMap{
    			"Name": pulumi.String("pulumi-eb-env"),
    		},
    		Name: pulumi.String("pulumi-eb-env"),
    		Tier: pulumi.String("WebServer"),
    	})
  • p

    prehistoric-london-9917

    3 months ago
    Sorry if this is the wrong place, but I don’t see a “Crosswalk for AWS” channel. I’m currently using
    @pulumi/awsx
    v0.40.0 for TypeScript. We’re messing a bit with the Python SDK, and we pulled
    pulumi_awsx
    v1.0.0b8 and noticed some pretty big differences. Looking more closely, it looks like v1.0.0b8 for TypeScript is a pretty big change from 0.40.0, too. My question is: Is there an upgrade path from TypeScript AWSX v0.40.0 to TypeScript AWSX v1.0? For example, SubnetSpecArgs is quite a bit more limited than SubnetArgs.
    p
    1 replies
    Copy to Clipboard
  • a

    acoustic-spring-42110

    3 months ago
    Trying to update a Wafv2.. It's got some existing manual rules (which I deleted).. but running pulumi locally with the rules configured always returns this error:
    Error updating WAFv2 WebACL, resource has changed since last refresh please run a new plan before applying again: WAFOptimisticLockException: AWS WAF couldn't save your changes because someone changed the resource after you started to edit it. Reapply your changes.
    a
    l
    5 replies
    Copy to Clipboard
  • w

    worried-xylophone-86184

    3 months ago
    Hi all ! Is there a way to provision Private EKS clusters (EKS clusters within private subnets having NAT Gateways attached to them) using the Pulumi EKS package. I am able to bring up the cluster but it fails with the below traceback and does not forward with NodeGroup provisioning.
    error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "<https://URL.eks.amazonaws.com/openapi/v2?timeout=32s>": dial tcp 10.1.3.211:443: i/o timeout
    w
    b
    +1
    8 replies
    Copy to Clipboard