• v

    victorious-dusk-75271

    1 month ago
    Does anyone know how to solve this problem?
    aws:ec2:Eip (us-data-vpc-nat-1):
        error: deleting urn:pulumi:dev::allrites-infrastructure::custom:resource:vpc$aws:ec2/vpc:Vpc$aws:ec2/subnet:Subnet$aws:ec2/eip:Eip::us-data-vpc-nat-1: 1 error occurred:
            * AuthFailure: You do not have permission to access the specified resource.
            status code: 400, request id: 3cedd0dd-f987-4eac-9c2b-ff179af491c2
    v
    v
    5 replies
    Copy to Clipboard
  • a

    ambitious-umbrella-20232

    1 month ago
    Hey all, does anyone know if it's possible to pass
    pulumi up
    a different
    aws:profile:
    value during the cli run that doesn't overwrite the value in the stack file? So like in my stack file I have this:
    config:
      aws:profile: staging
      aws:region: us-east-2
    Where
    staging
    corresponds to one of my named profiles in my
    ~/.aws/config
    file. But if someone else pulls down this code and tries to run it and their config file uses a different name for their keys to the same account can they pass a flag to
    pulumi up
    to point it there only during that run? I tried using the
    -c
    flag but it looks like that overwrites the stack file value. And yes I know this should be done all within a CICD pipeline, we're working on it 🙂
  • b

    billowy-horse-79629

    1 month ago
    Hey all, I’m deploying a new AWS WAF for my application loadbalancers and i’m pretty of new to it. I understand that using managed rules for the ACL can be very beneficial so I chose to use F5 ACL rule . Unfortunately, after reading the AWS Pulumi code carefully I couldn’t find any way to use managed rules as part of my Pulumi code. Am I missing something ? Have anyone used managed rules as part of the Pulumi code ? Thanks guys !
  • s

    steep-winter-68060

    1 month ago
    Hi all! Is it possible to set up a serverless MSK cluster with Pulumi?
    s
    1 replies
    Copy to Clipboard
  • p

    polite-window-12946

    1 month ago
    Is there a place where we can see where the awsx typescript version 1.0 will come out of beta? in the meantime is it recommended to use that or the 0.40 release, since the live docs point to the beta but everything else seems to be using 0.40?
    p
    s
    4 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    1 month ago
    can anyone from pulumi check this please? https://github.com/pulumi/pulumi-eks/issues/762
    v
    s
    4 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    1 month ago
    it is sad that
    @pulumi/eks
    is not usable. I am struggling with it since yesterday. here is for example, its adds labels on fresh stack then running up again wants to remove the labels.
    ++kubernetes:core/v1:ConfigMap: (create-replacement)
                    [id=kube-system/aws-auth]
                    [urn=urn:pulumi:dev::allrites-infrastructure::custom:resource:eks$eks:index:Cluster$kubernetes:core/v1:ConfigMap::primary-eks-eks-cluster-nodeAccess]
                    [provider: urn:pulumi:dev::allrites-infrastructure::custom:resource:eks$eks:index:Cluster$pulumi:providers:kubernetes::primary-eks-eks-cluster-eks-k8s::586e6654-9fcb-4908-9f46-53b23ae4c5c8 => urn:pulumi:dev::allrites-infrastructure::custom:resource:eks$eks:index:Cluster$pulumi:providers:kubernetes::primary-eks-eks-cluster-eks-k8s::output<string>]
                  ~ metadata  : {
                      - labels   : {
                          - <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: "pulumi"
                        }
                    }
                +-kubernetes:core/v1:ConfigMap: (replace)
                    [id=kube-system/aws-auth]
                    [urn=urn:pulumi:dev::allrites-infrastructure::custom:resource:eks$eks:index:Cluster$kubernetes:core/v1:ConfigMap::primary-eks-eks-cluster-nodeAccess]
                    [provider: urn:pulumi:dev::allrites-infrastructure::custom:resource:eks$eks:index:Cluster$pulumi:providers:kubernetes::primary-eks-eks-cluster-eks-k8s::586e6654-9fcb-4908-9f46-53b23ae4c5c8 => urn:pulumi:dev::allrites-infrastructure::custom:resource:eks$eks:index:Cluster$pulumi:providers:kubernetes::primary-eks-eks-cluster-eks-k8s::output<string>]
                  ~ metadata  : {
                      - labels   : {
                          - <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: "pulumi"
                        }
                    }
    v
    b
    2 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    1 month ago
    any idea what causing this? i am using pulumi.random and the result of that is
    DFpSfUijK8
    error: deleting urn:pulumi:dev::allrites-infrastructure::custom:component:rds:globaldb$aws:rds/cluster:Cluster::globaldb-cluster: 1 error occurred:
            * error deleting RDS Cluster (tf-20220812010823122500000001): InvalidParameterValue: The parameter DBClusterSnapshotIdentifier is not a valid identifier. Identifiers must begin with a letter; must contain only ASCII letters, digits, and hyphens; and must not end with a hyphen or contain two consecutive hyphens.
            status code: 400, request id: 92d6a0f5-2c7d-45d7-b094-bf9d91838c77
    v
    l
    4 replies
    Copy to Clipboard
  • b

    bitter-kite-21926

    1 month ago
    Hi all. I have infrastructure separated into
    common
    (where i create eks cluster and nodepool and shared things else) and per-project infrastructure (lives with code and has services/deployments/etc). How do i specify in the per-project infrastructure which eks cluster to deploy to? i have aws😛rofile specified in the stack yaml, but it looks that pulumi ignores it and deploys to current kubectl context.
    b
    1 replies
    Copy to Clipboard
  • b

    brainy-furniture-37509

    1 month ago
    Hi my cloudwatch eventRule is getting
    InvalidEventPatternException: Event pattern is not valid. Reason: Match value must be String, number, true, false, or null
    while trying to use below pattern. Is content filtering unavailable?
    Oops, false alarm.
    family
    was array silly
    eventPattern: JSON.stringify({
                    'source': ['aws.ecs'],
                    'detail-type': ['ECS Task State Change'],
                    'detail': {
                      'group': [family],
                      'lastStatus': ['STOPPED'],
                      'stoppedReason': ['Essential container in task exited'],
                      'containers': {'exitCode': [{'anything-but': 0}]}
                    }
                  })