hello - when running

pulumi preview

in our Github action we're seeing the following error:

pulumi:providers:aws default_3_26_1  error: no resource plugin 'aws-v3.26.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource aws v3.26.1`

the stack otherwise runs when using the cli locally

Hi. What is the best practice to create a table in dynamodb-local based on the infra created with pulumi?

Now I just manage a json file separately to use with aws cli, but I am wondering if there is any best work flow for this task.

If I enable the OIDC provider detailed here- https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/eks/#ClusterOptions-createOidcProvider How do I then create a new iam role for a given service account?

Folks, i am getting this error while creating load balancer. The load balancer attribute for vpcid is coming as a string from aws cli as a str.

error: 1 error occurred:
    	* Error creating LB Target Group: ValidationError: 1 validation error detected: Value 'vpc-012345678abc
    ' at 'targetGroup.vpcId' failed to satisfy constraint: Member must satisfy regular expression pattern: (?i)vpc-[a-zA-Z0-9]+
    	status code: 400, request id: bb8f4f52-***

it works when i am using hardcoded vpcid value, but fails while retrieving using dynamic way. Not sure why it’s failing.

@alert-raincoat-81485 there looks to be spacing issues there

Look at the start ‘ and end ‘ on the validation error

APIGW Crosswalk won't deploy to localstack but deploying non-crosswalk components works and having a hard time figuring out why. Any help would be greatly appreciated. https://github.com/pulumi/pulumi-awsx/issues/635

Anyone using pulumi+eks managed nodes with taints?

I'm getting an error creating a policy document:

error: 1 error occurred:
        * Error putting IAM role policy app-services-instance-sns-write-server-sent-events-8a49b9c: LimitExceeded: Maximum policy size of 10240 bytes exceeded for role ecs-use1-stage-app-services-instance-role-cebf8d5
        status code: 409, request id: bd737292-329c-4a82-81e5-7b81da9abc75

The policy document appears to be correct, and does not exceed the byre limit. Any ideas?

I'm seeing a new stack stuck on first deployment. It's been

creating

a

aws:elastictranscoder:Pipeline

for going on 15 minutes now, which historically takes a second or so. Thoughts?

Hello folks, I am trying to run the user_data while provisioning the instance, but it doesn’t run anything. The format i am using is

user_data = """
#!/bin/bash
set -eux
sudo aws s3 cp s3://<bucket-name>/<script>.sh /tmp/
"""

Instances = aws.ec2.Instance(
                instance_name,
                ami=ami,
                instance_type=size,
                subnet_id=subnets[1],
                user_data_base64=user_data,
                security_groups=[securitygroup]
            )

If anyone can help to review!

hello, i've got a stack into a bad state and would love some help to get it into any sort of different state (I can't destroy or make changes to the stack currently). I'm getting the error:

error: pre-step event returned an error: failed to verify snapshot: resource urn:pulumi:dev::<my-stack>::aws:cognito/userPool:UserPool::<my-user-pool> dependency  refers to missing resource

Hi, is it possible to configure service auto scaling with Pulumi for tasks running on Fargate? To achieve what's described here - https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-autoscaling-targettracking.html. I haven't been able to find any example.

Hi folks! I’m provisioning an NLB using the AWS K8S Service annotations. The workload gets loaded in after the NLB is provisioned. Is there some way to ignore that no pods are connected?

I’m trying to create a basic ALB with a ASG for some web instances… Always getting that error

aws:autoscaling:Group (resource1):
    error: aws:autoscaling/group:Group resource 'resource1' has a problem: Attribute should be a list

does someone has an idea?

Hi, I'm trying to create an EKS cluster with only private endpoint IPs and subsequent tasks (creating SGs) are hanging waiting for the cluster endpoint to be accessible. Suggestions?

Anyone have a strategy to get the region a

pulumi.ComponentResource

is currently deploying in? The best I can come up with is something like this:

const provider = this.getProvider('aws::') as any;
      (provider.region as pulumi.Output<string>).apply(console.log);

However

getProvider('aws::')

does not seem to work when the resource is just using the default provider. I mentioned this here as well: https://github.com/pulumi/pulumi/issues/2246

[RESOLVED] Hi there - I'm trying to create an EKS cluster, but getting the following error:

"Cannot create cluster 'eks-cluster-eksCluster-ffabc7f' because us-east-1e, the targeted availability zone, does not currently have sufficient capacity to support the cluster. Retry and choose from these availability zones: us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1f"

How can I configure Pulumi to use the AZs in which capacity is available? I don't want to create the cluster in another region for performance concerns.

Hi, Is AWS firehose is not a supported protocol for an SNS topic subscription?

Hi, I have this class returning a pulumi.Output<vpc>

class Vpc {

....

cidr = getCidr() // get a cidr from database

...

const vpc = pulumi.all([cidr]).apply(cidr)=>

{

return new vpcConfig('vpc',{cidr})

}

....

this.vpc=vpc

}

I need to return only type <vpc> ( I could do it without using pulumi.all inside of this class), otherwide I have to use another pulumi.all when using it

const vpc = new Vpc(.....)

pulumi.all([vpc]).apply(vpc) =>

{

new eks.cluster('.....', vpc)

}

is there any way to avoid using too much pulumi.all and get only the object type that I need( <vpc> in this case ) ? thanks in advance

Hi all, I'm trying to work out how to use Sentry with Pulumi, to add error logging to my API Gateway

Is there a Pulumi interface to Terraforms

aws_ami_ids

data source?

Hi everyone, I need some help. I’ve got an AWS API Gateway crosswalk setup. I noticed that by following the tutorials, the crosswalk module ends up creating catch all {proxy+} routes for all HTTP verbs. I documented the problem and minimal example here - https://github.com/pulumi/pulumi-awsx/issues/634 Has anyone been able to use AWS api gateway crosswalk successfully without running into this issue? If you did, what was your workaround? Thank you

I'm creating a RDS mysql instance from a snapshot. The original instance the snapshot was created from was not encrypted. On the new instance

storage_encrypted

is set to

True.

However the new instance does not get encrypted (no errors or warnings) and this results in a replacement loop as pulumi trys to set the

storage_encrypted

value on each run. Am I missing something here or is it not possible to enable encryption in this scenario?

Has anyone done NAT instances before on pulumi? Willing to share the code? NAT Instances can save a lot of money compared to NAT gateway, but it’s a bit more tedious to setup. https://www.kabisa.nl/tech/cost-saving-with-nat-instances/

New to pulumi and I was looking at the aws-stackreference-architecture example and it's currently broken? https://github.com/pulumi/examples/blob/master/aws-stackreference-architecture/networking/src/index.ts#L36

src/index.ts(36,43): error TS2339: Property 'names' does not exist on type 'Promise<GetAvailabilityZonesResult>'.

hello! when will you all push the next release for pulumi/awsx in typescript?