Friends, we have been working hard on testing internally but we are glad to say that AWSx is in a great state for you to take for a test drive 🙂 We would love the feedback based on the scenarios we cover - you can find a lot of examples in the

examples

folder. We really welcome any feedback 🙂

Is it possible to mix aws and awsx components? I have a cluster in awsx, and a vpc defined the old way.. I'm looking for a way to tell the new cluster to use the existing vpc (it's not the default one) and I'm not totally sure how to do it.

@acoustic-spring-42110 Of course you can do so! At the end of the day they are both talking to the same Resources Manager API. Are your cluster/vpc living in two different stacks?

The same stack! And I think I discovered that I can just import the

vpc

and wrap it like this (typescript):

const vpc = new awsx.ec2.Vpc("vpc", {vpc: infraRef.getOutput("vpc") as any})

any side-effects of doing it that way?

If it's working then all good, it shouldn't have any side-effect! You need to make sure it doesn't create a new vpc tho

After upgrading to

pulumi-aws-5.5.0

I started getting this error during venv initialization

TypeError: Descriptors cannot not be created directly.
    If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
    If you cannot immediately regenerate your protos, some other possible workarounds are:
     1. Downgrade the protobuf package to 3.20.x or lower.
     2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).
    More information: <https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates>

After rolling back to

pulumi-aws-5.4.0

in my project requirements[.]txt it goes away.

I'm having quota issues with my Lambda functions because they all pull in the whole

node_modules

folder. One function might use one package while another doesn't but function serialization doesn't discriminate what packages are being used. This means that they all grow in size as more packages are included in the stack/project. Has anyone ran across this issue? The compressed zip can't be over 50MB and when uncompressed, over 250MB. I know you can instead utilize a container to run the Lambda function, but how would you call aws functions inside of it (like

s3.putObject

) without just importing the aws-cli and executing it?

facing the same issue, if someone has a clue

Hi there 👋🏼 how do I have pulumi use the instance profile for the ec2 instance it's running on? Unfortunately my google-fu is failing me 😔 I expect y'all are delegating to the go client; I'm under the impression that will fallback to the meta data url but that doesn't seem to be happening.

Hi all. From the AWS console, it’s easy to create a new IAM Role with an AWS service as a trusted entity, without having to type in a trust policy document. However, I’m having trouble figuring out how to do this in Pulumi — every example has the trusted entities policy document as a string literal (into assumeRolePolicy). This is very undesirable, as it essentially requires that you create the Role by hand first, using the AWS console, so that you know what the Service name needs to be. Is there any way to just have Pulumi look this up automatically like the console does?

Hi, how do I create a Dashboard widget with filtered logs from logs Insight. I have managed to do by clicking around in the console, but can’t find out how to do it using pulumi :/. Disse the widget JSON that is created by clicking.

{
  “widgets”: [
    {
      “type”: “log”,
      “x”: 0,
      “y”: 0,
      “width”: 24,
      “height”: 17,
      “properties”: {
        “query”: “SOURCE ‘/aws/lambda/log-group-name | filter LogLevel = \“Error\” | limit 10",
        “region”: “eu-west-1",
        “stacked”: false,
        “title”: “Errors”,
        “view”: “table”
      }
    }
  ]
}

👋 I’m trying to create a Global Aurora Postgre DB with the

aws classic

provider of pulumi. For some reason, even if I add

dependsOn

my primary

RDSCluster

to point to the

GlobalCluster

it seems that pulumi never really wait that the cluster has been created. So instead of having a cluster with multiple regions, we god cluster that are separated and never linked together. Any idea of what I’m doing wrong?

Anyone had issues where removing a property doesn't actually see it being removed. I have removed

KeyName

from an ec2 instance created and it refuses to see it being deleted. Even if I do a refresh on the state. I am able to change it and it knows it has changed.

What is even more bizarre, is if I remove the field and it recreates the instance, it still attaches the KeyName of what was deleted

Hello everyone, trying to port some changes from Terraform to Pulumi and run into an issue: This is EC2 instance spec in terraform. I have a templated bash script into which I inject loadbalancer DNS name.

user_data                   = base64encode(
    templatefile("../templates/bash_script.sh.tftpl", {
        internal_lb_dns_name = aws_lb.aws-internal-load-balancer.dns_name
      }
    )
  )

How to achieve similar results with pulumi? If it was not a templated file it would be easy, namely:

UserData:            pulumi.StringPtr(base64.StdEncoding.EncodeToString(bashScriptContent))

However, I need to inject some variables into that script that will be known once some resources got created. Any help would be appreciated, this is a part of my Master's Degree thesis and it would be a shame that this cannot be solved in Pulumi 😄 //EDIT, I'm writing in Golang

is there a way to explicitly set the provider version?

pulumi plugin ls

as well as dumping

requirements.txt

(and checking my venv by activating it and running

pip freeze

) all report

pulumi-aws

as

5.6.0

however when i try to

pulumi up

it keeps trying to use

default_5_4_0

which is no bueno

not really sure i understand why it's trying to use an older provider version when it doesn't exist in the host environment

I was wondering it someone it that problem. I create an

aws.rds.GlobalCluster

resource. I assign it to my

aws.rds.Cluster

using the outputs of the first resource. For some reason, pulumi create the Global cluster but seems to never pass the

globalClusterIdentifier

to the

aws.rds.Cluster

resulting at having regional cluster.

HI, I have a series of SSM parameters that are using a KMS key id that is being referenced from another stack. In pseudo below.

export const appSettingsKeyArn = environmentStackRef.getOutput("appSettingsKeyArn");

var param = new aws.ssm.Parameter('name', {
  name: 'name',
  type: 'String',
  value: 'value',
  keyId: appSettingsKeyArn,
});

Everything in the stack is created fine, the system is working as it should be. However, everytime I run

pulumi up

it is attempting to update the SSM parameter resources with a new

keyId

Looking in the details of the plan, I can see that the key id is never stored in state, so pulumi is constantly trying to update it. Does anybody know why this is happening?

Hi Folks! I was wondering if there is a way to set up an ECS Fargate Scheduled Task?

what would be the recommended way to use aws-sdk v3 within a

aws.lambda.CallbackFunction

? learning pulumi and found i can use the lambda runtime’s v2 sdk through `aws.sdk`(from

@pulumi/aws

)

this is with a typescript project

👋 Hello, team! Evaluating Pulumi for a largely serverless organization that has had some issues with SAM. In the context of Pulumi, I'm running into issues installing dependencies in python. Is there are pattern to do this with Pulumi? AWS Lambda documentation is recommending essentially vendoring the packages at the root of the codebase. I still find it strange that Lambda doesn't manage dependencies at all. If anyone has recommendations on how to handle this (as long as layers) I'd be very interested!

@broad-dog-22463 You replied to my message on GitHub about awsx and

ephemeralStorage

. I have updated to

@pulumi/awsx:1.0.0-beta.7

so that I can try to leverage support for ephemeral storage. I'm running into an issue when provisioning:

error: Error: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: 1 error occurred:
        * no matching EC2 VPC found

// snipped

Error: failed to register new resource REDACTED [awsx:ecs:FargateService]: 2 UNKNOWN: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: 1 error occurred:
        * no matching EC2 VPC found

Neither one of

awsx.ecs.FargateService

or

aws.ecs.Cluster

can receive a

vpc

property.

The classic versions do take a

vpc

property. So I'm a bit lost here

Hi all, I’m trying to merge two zip files but AssetArchive doesn’t seem to support this. Is there an alternative way to merge two

pulumi.FileArchive

at the same path?

Hello, I'm using Pulumi to setup all my AWS account, sometimes I'd like to tweak a small setting for example a Policy but when I

pulumi up

it will also build and deploy a new docker image. As expected from my pulumi script, but my intention this time it just to tweak the setting not to deploy a new docker image of the same code, what is the recommended way to handle such a case ?

im using this to build my image

// Step 3: Build and publish a Docker image to a private ECR registry.
const ApiImage = awsx.ecs.Image.fromDockerBuild('api-image', {
  context: path.resolve(__dirname, '../../../../'),
  dockerfile: path.resolve(__dirname, '../../', 'Dockerfile'),
});

Is there a way to make it build a new docker image only if the content of the context has changed ? like storing a SHA256 hash of the folder contents and checking against it to decide to build or reuse last one ?

It would prevent an incredible waste of resource locally, on Docker registries and on CI pipelines