• v

    victorious-church-57397

    2 months ago
  • b

    busy-helicopter-97413

    2 months ago
    Hey all! I am running some automation in golang that involves retrieving AMIs that breaks on certain occasions but not on others. Specifically, the error message I'm getting is
    rpc error: code = Unknown desc = invocation of aws:ec2/getAmi:getAmi returned an error: unrecognized data function (Invoke): aws:ec2/getAmi:getAmi
    I am thinking the reason why is that there are two versions of
    getAMI
    as one is deprecated (https://www.pulumi.com/registry/packages/aws/api-docs/getami/ vs https://www.pulumi.com/registry/packages/aws/api-docs/ec2/getami/) I am running this automation on multiple versions of k8s, so is it possible that somehow the wrong implementation of getAMI is being called depending on the version?
  • a

    adorable-summer-21974

    2 months ago
    Hey, does anyone know if its possible to add an origin to an existing cloudfront distribution using pulumi? Thanks!
    a
    1 replies
    Copy to Clipboard
  • a

    aloof-dress-1001

    2 months ago
    Hey, Why can’t i run “nodejs16.x” runtime from pulumi when creating a lambda function?
  • g

    glamorous-spring-30202

    1 month ago
    Hi, I recently started using
    registerAutoTags
    as described here. After that I notice that my lambda resources are losing its policies, and I am puzzled as to why this is happening. I use pulumi to create a lambda, add a role, and policy attachments to it. After a successful
    pulumi up
    , after a few seconds my lambdas do not work, permission issues. I go look in AWS console, and they do not have my custom policy attachment anymore. If I
    pulumi refresh
    , I see the removed policies/attachments, and if I
    pulumi up
    again, it will create them. But on next re-deploy, the lambdas lose their policies again. I am thinking that there is something going on with the stack transformations I am trying to apply, but honestly, I have no good idea why this is happening, apart from the only change before this started, being the tagging. If anyone ever faced this issue or has some pointers on where I should look, it would be much appreciated. Thank you
  • r

    rhythmic-branch-12845

    1 month ago
    hi, I am importing an EC2 instance (using
    pulumi import
    ) and then pasting the code into my file, and when I try to run
    pulumi up
    again using the same code, Pulumi claims that there is a diff in the user data when the strings are the same?
    Type                 Name        Plan       Info
         pulumi:pulumi:Stack  test-dev
     ~   └─ aws:ec2:Instance  api         update     [diff: ~userData]
    
    Resources:
        ~ 1 to update
        1 unchanged
    
    Do you want to perform this update? details
      pulumi:pulumi:Stack: (same)
        [urn=urn:pulumi:dev::test::pulumi:pulumi:Stack::test-dev]
        ~ aws:ec2/instance:Instance: (update) 🔒
            [id=i-0a1fd51cf5f02a8b4]
            [urn=urn:pulumi:dev::test::aws:ec2/instance:Instance::api]
            [provider=urn:pulumi:dev::test::pulumi:providers:aws::default_5_10_0::bdc3a497-cbed-47f9-98ef-99acbed1740f]
          ~ userData: "85de5fdec580fbc6617d9b2bfbddbae346a45ef4" => "85de5fdec580fbc6617d9b2bfbddbae346a45ef4"
    r
    l
    2 replies
    Copy to Clipboard
  • r

    rough-jewelry-40643

    1 month ago
    Hi all, I have a question about deploying multi region resources. In general we use AWS us-east-2. I need to build a stack which contains CloudFront and some CloudFront associated lamda fucntions. B/c cloudfront is global the lambda fucntions must be in us-east-1. Is there a way in pulumi to specify this, without changing my overall
    Pulumi.stack.yml
    and thus building all the stack resources in us-east-1?
    r
    s
    3 replies
    Copy to Clipboard
  • m

    most-lighter-95902

    1 month ago
    Hi, I’m getting the following error even though my aws credentials are set as env variables as per the doc:
  • m

    most-lighter-95902

    1 month ago
    error: Running program '/app' failed with an unhandled exception:
    Error: invocation of aws:index/getCallerIdentity:getCallerIdentity returned an error: unable to validate AWS credentials
  • h

    helpful-account-44059

    1 month ago
    Am I asking a stupid question?