• e

    elegant-smartphone-60282

    1 month ago
    Hey i have this code
    public_subnets = dis_stack.get_output("public_subnets")
    
    subnets_list = public_subnets.apply(lambda id: id)
    but it returns an output object, how can i do that i get a list ?
    e
    s
    +1
    3 replies
    Copy to Clipboard
  • b

    bitter-france-47214

    4 weeks ago
    My
    aws:cloudfront:Distribution
    is failing because of following error:
    error creating CloudFront Distribution: InvalidArgument: The parameter Origin DomainName does not refer to a valid S3 bucket. status code: 400, request id: 59...eb1
    I assume that this originates to following parts of the arguments:
    origins: [
            {
                originId: contentBucket.arn,
                domainName: contentBucket.websiteEndpoint,
                s3OriginConfig: {
                    originAccessIdentity: originAccessIdentity.cloudfrontAccessIdentityPath,
                },
            },
        ],
    Especially
    contentBucket.websiteEndpoint
    . I assume this is the problem. Pulumi outputs this as
    <http://myDomain.app.s3-website.eu-central-1.amazonaws.com/>
    which works fine so I don't quite know what the problem is. Can anybody help?
    b
    s
    2 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    4 weeks ago
    why i am keep getting this error randomly?
    pulumi:pulumi:Stack (laravel-application-eu-dev):
        error: Running program '/home/k1ng/projects/allrites-laravel/devops' failed with an unhandled exception:
        /home/k1ng/projects/allrites-laravel/devops/node_modules/@pulumi/aws/s3/routingRules.js:1
        b�  �s�a7�1��9^��p�%б��!<>�`��k�/`cx���sĶ��� W�u�Z�Wٺn�֪Y�O3M��V*"�.�x,���Y_�{������~�H7��F*�gQW|��bu ��2A1�(�c�(ѪIj���E���6b�
    
    
        SyntaxError: Invalid or unexpected token
            at Object.compileFunction (node:vm:353:18)
            at wrapSafe (node:internal/modules/cjs/loader:1040:15)
            at Module._compile (node:internal/modules/cjs/loader:1076:27)
            at Object.Module._extensions..js (node:internal/modules/cjs/loader:1166:10)
            at Module.load (node:internal/modules/cjs/loader:988:32)
            at Function.Module._load (node:internal/modules/cjs/loader:834:12)
            at Module.require (node:internal/modules/cjs/loader:1012:19)
            at require (node:internal/modules/cjs/helpers:102:18)
            at Object.<anonymous> (/home/k1ng/projects/allrites-laravel/devops/node_modules/@pulumi/s3/index.ts:43:1)
            at Module._compile (node:internal/modules/cjs/loader:1112:14)
    v
    1 replies
    Copy to Clipboard
  • s

    strong-helmet-83704

    4 weeks ago
    I’m confused about why Pulumi still tries to delete my VPC after i added
    retain_on_delete=True
    to the ResourceOptions. My understanding was that it would only remove it from the stack and not perform the API call to delete. What part of this flow am i misunderstanding?
    s
    s
    7 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    4 weeks ago
    does anyone know how to get the global RDS cluster write forwarding endpoint? https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html
    v
    s
    2 replies
    Copy to Clipboard
  • s

    square-ability-48831

    4 weeks ago
    I'm looking at building an Aurora Postgres Serverless V2 cluster in a non-default VPC, but I do not see an apparent way to specify which VPC the cluster should be created in—no option in ClusterArgs or ClusterInstanceArgs—is it just missing? Seems like it's choosing the default VPC - but I really don't want this.
    error creating RDS cluster: InvalidParameterCombination: The DB instance and EC2 security group are in different VPCs. The DB instance is in vpc-088d910645c61f340 (Default VPC) and the EC2 security group is in vpc-064aba8b2279cfa50 (my custom Data VPC where I want the cluster to reside)
    how do I tell pulumi to put this cluster in my dataVPC and not the default VPC?
    s
    v
    8 replies
    Copy to Clipboard
  • v

    victorious-dusk-75271

    4 weeks ago
    I am trying to create latency based records and AWS getting this error.
    * [ERR]: Error building changeset: InvalidChangeBatch: [Tried to create resource record set [name='xxxxxxxx.io.', type='CNAME', set-identifier='latency'] but it already exists]
    return new aws.route53.Record('admin', {
            name: 'admin',
            zoneId: zone.then(z => z.zoneId),
            type: 'CNAME',
            setIdentifier: 'latency',
            records: [loadBalancer],
            ttl: 60,
            latencyRoutingPolicies: [{ region: i.region }]
        })
    v
    f
    3 replies
    Copy to Clipboard
  • h

    helpful-account-44059

    4 weeks ago
    Hi, i have a eks cluster constructed by pulumi, recently when i typed pulumi preview or pulumi up, it always failed with below errors: i have updated the aws cli and kubectl
    h
    s
    +1
    8 replies
    Copy to Clipboard
  • g

    great-library-25724

    3 weeks ago
    Hi, does now pulumi supports all aws modules with yaml method ?
    g
    1 replies
    Copy to Clipboard