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

Anyone work with Databricks yet? I'm getting the following error

cannot create mws vpc endpoint: ENDPOINT_NOT_FOUND: Invalid endpoint

for my vpc, when using

databricks.MwsVpcEndpoint()

... but that same endpoint works with

aws.ec2.VpcEndpoint.get()

Hello, I'm getting the following error whenever I try any

pulumi-cli

commands like refresh or preview:

error: Preview failed: 1 error occurred:
        * error configuring Terraform AWS Provider: failed to load shared config file, /Users/user/.aws/config, invalid state with ASTKind  and TokenType none

Any idea what might be causing this?

Hello, I’m getting following error whenever I am trying to run Pulumi commands even though my AWS CLI is working fine and I used these steps

<https://pulumi.io/install/aws.html>

for setting up my pulumi ERROR:

Preview failed: unable to validate AWS AccessKeyID and/or SecretAccessKey - see <https://pulumi.io/install/aws.html> for details on configuration

Hi all, I am getting this error after running

pulumi up

. I am using

@pulumi/aws-apigateway

and there is only a

pulumi-resource-aws-apigateway.cmd

in the folder mentioned below

Diagnostics:
  pulumi:providers:aws-apigateway (default_0_0_9):
    error: failed to load plugin C:\Users\jzhou2\.pulumi\plugins\resource-aws-apigateway-v0.0.9\pulumi-resource-aws-apigateway.exe: exec: "C:\\Users\\jzhou2\\.pulumi\\plugins\\resource-aws-apigateway-v0.0.9\\pulumi-resource-aws-apigateway.exe": file does not exist

Hi Team, Is there a

eksctl

equivalent package in pulumi ? e.g.

eksctl create iamserviceaccount

implements many components behind the scenes, is there a equivalent component ?

Hello all, getting started here and trying to get an EKS cluster up from the example. Im’ having problems with permissions, from the docs it says

...ensure it has sufficient permissions to deploy and manage your program's resources.

But what are those permissions? Is there a list similar to the one

kOps

has in it’s docs https://kops.sigs.k8s.io/getting_started/aws/#setup-iam-user ?

Hey Folks, I'm looking for an example/doc to autoscale

ECS Fargate services

through

CloudWatch

Alarms based on the

CPU-Utilization/Memory-Consumption

I'm trying to create an ingress for an application using

new k8s.networking.v1.Ingress

and am failing the

pulumi up

with this error:

kubernetes:<http://networking.k8s.io/v1:Ingress|networking.k8s.io/v1:Ingress> (api-ingress):
    error: resource test/api-ingress was not successfully created by the Kubernetes API server : admission webhook "vingress.elbv2.k8s.aws" denied the request: invalid ingress class: <http://IngressClass.networking.k8s.io|IngressClass.networking.k8s.io> "alb" not found

The way I have set it up is extremely similar to this blog post: https://www.pulumi.com/blog/kubernetes-ingress-with-aws-alb-ingress-controller-and-pulumi-crosswalk/ Does anyone have any idea what is going wrong? Ultimately I'd like to have it set up where the ALB Controller auto creates an ALB when detecting an ingress, I'm not completely sure its even the ingress creation that is the issue.

Is someone from the Pulumi team able to help with this? https://pulumi-community.slack.com/archives/CRH5ENVDX/p1654498884552529 It seems that Paul has gone on holidays or something

Hey everyone! Sorry if it's double posting, but though it'd be more appropriate to ask here. Is it possible to create an EKS managed node group via

eks.ManagedNodeGroup

from

@pulumi/eks

in a separate project from where the cluster was created (via

eks.Cluster

from

@pulumi/eks

)? From what it looks like in the API docs and the code itself, ManagedNodeGroup requires a direct cluster object, and its various properties, as well as it uses the same cluster for the

parent

property. I have tried a magnitude of things to simulate this behaviour via

StackReference

kubeconfig and providers, but to no avail. I am at my wit's end quite frankly. references: https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/nodegroup.ts#L842 https://www.pulumi.com/docs/guides/crosswalk/aws/eks/

I created an EKS cluster on

VPC-1

, but I want to move that EKS cluster into

default-VPC

- is it as simple as 1. remove VPC-related codes from pulumi 2. import VPC ID - https://www.pulumi.com/registry/packages/aws/api-docs/ec2/vpc/#import Or is it more complicated than that?

Hello. I feel like this is probably really straight forward, but I’m not getting it 🙂 does somebody have an example of an

s3.BucketTagArrayInput

with go?

Is it possible to create

Web identity

IAM role type (as shown on the screenshot below) using Pulumi? I don’t see type option under the RoleArgs. I need to create web identity role type and select custom identity provider needed to enable eks cluster autoscaling

I am getting this error. I created new aws account and tried to deploy same app and there is no error for new aws account. I think I should do something in my aws account.

Hello! I’m consistently getting a Fargate Task Definition marked as needing replacement although nothing has changed. When I inspect the details, it just shows:

++aws:ecs/taskDefinition:TaskDefinition: (create-replacement)
                    [id=[REDACTED]-fg-task-def-47240670]
                    [urn=urn:pulumi:[REDACTED]::app::[REDACTED]:[REDACTED]$[REDACTED]:project$awsx:x:ecs:FargateTaskDefinition$aws:ecs/taskDefinition:TaskDefinition::[REDACTED]-fg-task-def]
                    [provider=urn:pulumi:[REDACTED]::app::pulumi:providers:aws::default_4_33_0::ac3e215e-84ad-45ed-a381-3d1b538f794b]
                  ~ containerDefinitions: [secret] => [secret]
                +-aws:ecs/taskDefinition:TaskDefinition: (replace)
                    [id=[REDACTED]-fg-task-def-47240670]
                    [urn=urn:pulumi:[REDACTED]::app::[REDACTED]:[REDACTED]$[REDACTED]:[REDACTED]$awsx:x:ecs:FargateTaskDefinition$aws:ecs/taskDefinition:TaskDefinition::[REDACTED]-fg-task-def]
                    [provider=urn:pulumi:[REDACTED]::app::pulumi:providers:aws::default_4_33_0::ac3e215e-84ad-45ed-a381-3d1b538f794b]
                  ~ containerDefinitions: [secret] => [secret]

I’ve also tried

--diff -j

, but all I got was

"[secret]"

under

containerDefinitions

. I then tried

-v 11 --logtostderr --logflow

, but the output was a bit hard to use. Any help would be greatly appreciated. Thank you!

Hi, how to fix the error:

InvalidParameterValue: No Environment found for EnvironmentId = xxx

? I have an application so far and it true that there’s no environments in AWS console. Is there anything I’ve missed? The following is my env setting

elasticbeanstalk.NewEnvironment(ctx, "EBEnv", &elasticbeanstalk.EnvironmentArgs{
		Application:       eb.Name,
		SolutionStackName: pulumi.String("64bit Amazon Linux 2 v5.5.3 running Node.js 16"),
		Settings: elasticbeanstalk.EnvironmentSettingArray{
			&elasticbeanstalk.EnvironmentSettingArgs{
				Namespace: pulumi.String("aws:ec2:vpc"),
				Name:      pulumi.String("VPCId"),
				Value:     vpc.ID(),
			},
			&elasticbeanstalk.EnvironmentSettingArgs{
				Namespace: pulumi.String("aws:ec2:vpc"),
				Name:      pulumi.String("Subnets"),
				Value:     sn[0].ID(),
			},
			&elasticbeanstalk.EnvironmentSettingArgs{
				Namespace: pulumi.String("aws:autoscaling:launchconfiguration"),
				Name:      pulumi.String("IamInstanceProfile"),
				Value:     pulumi.String("aws-elasticbeanstalk-ec2-role"),
			},
		},
		Tags: pulumi.StringMap{
			"Name": pulumi.String("pulumi-eb-env"),
		},
		Name: pulumi.String("pulumi-eb-env"),
		Tier: pulumi.String("WebServer"),
	})

Sorry if this is the wrong place, but I don’t see a “Crosswalk for AWS” channel. I’m currently using

@pulumi/awsx

v0.40.0 for TypeScript. We’re messing a bit with the Python SDK, and we pulled

pulumi_awsx

v1.0.0b8 and noticed some pretty big differences. Looking more closely, it looks like v1.0.0b8 for TypeScript is a pretty big change from 0.40.0, too. My question is: Is there an upgrade path from TypeScript AWSX v0.40.0 to TypeScript AWSX v1.0? For example, SubnetSpecArgs is quite a bit more limited than SubnetArgs.

Trying to update a Wafv2.. It's got some existing manual rules (which I deleted).. but running pulumi locally with the rules configured always returns this error:

Error updating WAFv2 WebACL, resource has changed since last refresh please run a new plan before applying again: WAFOptimisticLockException: AWS WAF couldn't save your changes because someone changed the resource after you started to edit it. Reapply your changes.

Hi all ! Is there a way to provision Private EKS clusters (EKS clusters within private subnets having NAT Gateways attached to them) using the Pulumi EKS package. I am able to bring up the cluster but it fails with the below traceback and does not forward with NodeGroup provisioning.

error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "<https://URL.eks.amazonaws.com/openapi/v2?timeout=32s>": dial tcp 10.1.3.211:443: i/o timeout

Hi all, I’m running into an issue on aws with SSO enabled where pulumi cannot find the logs for the current stack, but the log group exist. Is this a known issue and is there a solution ?

Hi all is anyone else having issues after pulumi installs

[resource plugin aws-5.7.2] installing

? I ran a

pulumi  up

which had previously worked just fine. Pulumi ran update above and now I get the following error...

Diagnostics:
  pulumi:pulumi:Stack (core-app-services-base-target-accounts-devtest):
    error: preview failed
 
  aws:ecs:Cluster (core-app-services):
    error: Preview failed: 1 error occurred:
        * error configuring Terraform AWS Provider: failed to get shared config profile, target

Hi all, new to Pulumi here, your patience is appreciated, coming from tf. I'm using an example from the website, using awsx.ec2.Vpc to create a VPC. When I run pulumi up once, it works, when I run pulumi up a second time, the typescript compiler complains and fails.

import * as pulumi from "@pulumi/pulumi";    
import * as aws from "@pulumi/aws";    
import * as awsx from "@pulumi/awsx";    
    
const vpc = new awsx.ec2.Vpc("custom", {    
  subnetSpecs:[    
    {    
      type: awsx.ec2.SubnetType.Public,    
      cidrMask: 22,    
    },    
    {    
      type: awsx.ec2.SubnetType.Private,    
      cidrMask: 20,    
    },    
  ],    
});

The errors i'm receiving are:

Diagnostics:
  pulumi:pulumi:Stack (vpc-dev):
    error: Running program '/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc' failed with an unhandled exception:
    TSError: ⨯ Unable to compile TypeScript:
    index.ts(6,3): error TS2345: Argument of type '{ subnetSpecs: { type: any; cidrMask: number; }[]; }' is not assignable to parameter of type 'VpcArgs | ExistingVpcArgs | ExistingVpcIdArgs'.
      Object literal may only specify known properties, and 'subnetSpecs' does not exist in type 'VpcArgs | ExistingVpcArgs | ExistingVpcIdArgs'.
    index.ts(8,22): error TS2339: Property 'SubnetType' does not exist on type 'typeof import("/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc/node_modules/@pulumi/awsx/ec2/index")'.
    index.ts(12,22): error TS2339: Property 'SubnetType' does not exist on type 'typeof import("/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc/node_modules/@pulumi/awsx/ec2/index")'.
    
        at createTSError (/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc/node_modules/ts-node/src/index.ts:261:12)
        at getOutput (/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc/node_modules/ts-node/src/index.ts:367:40)
        at Object.compile (/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc/node_modules/ts-node/src/index.ts:558:11)
        at Module.m._compile (/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc/node_modules/ts-node/src/index.ts:439:43)
        at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
        at Object.require.extensions.<computed> [as .ts] (/mnt/storage/Cody/projects/grizzlyforce/pulumi/vpc/node_modules/ts-node/src/index.ts:442:12)
        at Module.load (node:internal/modules/cjs/loader:981:32)
        at Function.Module._load (node:internal/modules/cjs/loader:822:12)
        at Module.require (node:internal/modules/cjs/loader:1005:19)
        at require (node:internal/modules/cjs/helpers:102:18)

https://github.com/pulumi/pulumi-aws/issues/1655 it seems crazy to me that this hasn’t been fixed yet, surely a wiring issue? re: default tags, the behaviour in terraform is as expected

Hello to everyone. I am using ecr Repository for my apps. It creates and deploys a new image each time, but instead of creating it each time, I only want to create a new image whenever there is a change. Is this possible? If it is not possible to watch the files in Pulumi, there is an option to define a version number for the Repository instance and increase that number when I want to get a new build.

Hey folks! I'm deploying to an ECS Cluster within a Private Subnet. To communicate with my ECR I've set up private links (endpoints) as you can see below. Everything was working properly, then I got this random error

ResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to retrieve ecr registry auth: service call has been retried 5 time(s): RequestError: send request failed caused by: Post <https://api.ecr.us-east-2.amazonaws.com/>: dial tcp: lookup <http://api.ecr.us-east-2.amazonaws.com|api.ecr.us-east-2.amazonaws.com> on 10.0.0.2:53: no such host

Any clue what's going on?

Hey all! Is there a provider/component that people use for managing postgres users, roles and permissions within an RDS instance?

Hello, it looks like awsx.ec2.Vpc.fromExistingIds creates a new VPC (as opposed to what is stated in the doc); am I the only one experimenting this behaviour?

Hi there, anyone with a more serious production-adjacent/ready EKS cluster Pulumi project?