• v

    victorious-dusk-75271

    1 month ago
    aws:ec2:VpcPeeringConnection (primary-eks-vpc-peer-to-us-eks-vpc):
        error: 1 error occurred:
            * creating urn:pulumi:dev::allrites-infrastructure::custom:resource:vpc$aws:ec2/vpcPeeringConnection:VpcPeeringConnection::primary-eks-vpc-peer-to-us-eks-vpc: 1 error occurred:
            * Unable to modify EC2 VPC Peering Connection Options. EC2 VPC Peering Connection (pcx-031d18fcc4929fecd) is not active (current status: pending-acceptance). Please set the `auto_accept` attribute to `true` or activate the EC2 VPC Peering Connection manually.
    v
    l
    11 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    1 month ago
    any idea why i am getting this error?
  • v

    victorious-dusk-75271

    1 month ago
    i have accepter setup
  • v

    victorious-dusk-75271

    1 month ago
    new aws.ec2.VpcPeeringConnectionAccepter(`${this.name}-peer-to-${peerName}-accepter`, {
                vpcPeeringConnectionId: peering.id,
                autoAccept: true,
                tags: { ...this.baseTags, Name: `${this.name} VPC connection accepter`, Side: 'Accepter' }
            }, { provider: args.peerVpc.opts.provider, parent: this })
  • a

    ambitious-agent-35343

    1 month ago
    Anyone familiar with adding ECR credentials/secret as in imagePullSecrets with a Pulumi deployment?
  • l

    little-cartoon-10569

    1 month ago
    Would anyone know which library creates this error message? I know the restriction is at the AWS API, but I can't find the source code for the message anywhere.
    error: could not make instance of 'aws:elasticache/replicationGroup:ReplicationGroup': name 'really-long-name-that-causes-this-error-' plus 7 random chars is longer than maximum length 40
    Wondering if it comes from Pulumi core, Pulumi AWS, code generated from the TF schema, or something else...
    l
    b
    5 replies
    Copy to Clipboard
  • b

    bitter-france-47214

    1 month ago
    apigateway
    lambda
    invocation
    Code In the code, I am using
    pulumi.interpolate
    and
    signup.invokeArn
    to setup the apigateway integration with the lambda defined further up. Though, I am getting an Error (see below) and don't know why. Can anybody help?
    const signup = new aws.lambda.Function("sign-up", { ... });
    
    
    const api = new aws.apigateway.RestApi("freedev-api", {
      body: JSON.stringify({
        ...
        paths: {
          ...
          "x-amazon-apigateway-integration": {
            httpMethod: "POST",
            type: "AWS_PROXY",
            uri: pulumi.interpolate `arn:aws:apigateway:eu-central-1:lambda:path/2015-03-31/functions/${signup.invokeArn}/invocations`,
           },
    Error
    Error creating API Gateway Deployment: BadRequestException: No integration defined for method
  • d

    damp-school-17708

    1 month ago
    I’ve just hit this issue as well
    d
    3 replies
    Copy to Clipboard
  • b

    breezy-laptop-42679

    1 month ago
    while defining security group id iam getting an error : Object is possibly 'undefined'. here is the example code I have to edit :
  • b

    breezy-laptop-42679

    1 month ago
    const allowPostgresSgRule =
          env === 'prod' &&
          tfCCCRdsPostgresSg &&
          new aws.ec2.SecurityGroupRule('ccc-postgres-access-rule', {
            type: 'ingress',
            fromPort: 5432,
            toPort: 5432,
            protocol: 'tcp',
            sourceSecurityGroupId: sg.id,
            securityGroupId: tfCCCRdsPostgresSg.id,
          });
       // NOTE: Sunguard GP VPN
       const allowLocalAccessGPSgRule = new aws.ec2.SecurityGroupRule('allow-gp-access-rule', {
        type: 'ingress',
        fromPort: 5432,
        toPort: 5432,
        protocol: 'tcp',
        cidrBlocks: ['XXX.XX.0.0/19'],
        securityGroupId: XXXXXRdsPostgresSg.id,
      });
      // NOTE: Bethpage GP VPN
      const allowLocalAccessGPBPSgRule = new aws.ec2.SecurityGroupRule('allow-gp-bp-access-rule', {
        type: 'ingress',
        fromPort: 5432,
        toPort: 5432,
        protocol: 'tcp',
        cidrBlocks: ['XXX.XX.X.0/24'],
        securityGroupId: XXXXRdsPostgresSg.id,
      });
    b
    l
    3 replies
    Copy to Clipboard