@broad-dog-22463 Dude, you’re getting trolled.

??

Sorry, that was no way to start a conversation, I apologize.

I want to store configuration files in an EBS volume, the configuration files content is generated at build time from pulumi. What's the best way to copy to configuration file to the EBS volume? Any sample I can look at?

I’m using

aws.s3.Bucket.get()

and receiving a strange error that seems to indicate it’s somehow related to stack references (which I’m not using in this project:

registered twice (read and read)

I’ve tried getting my Bucket 3 different ways:

aws.s3.Bucket.get(bucketName, bucketName, { name: bucketName });
aws.s3.Bucket.get(bucketName, bucketName);
aws.s3.Bucket.get(bucketName);

Furthermore, it breaks the update, and tells me to import an exported stack. Now I have some buckets with 2-3 extra

-[a-z0-9]{7}

suffixes

Anyone ever run into this when making an Event Source Mapping?

Unsupported 'maximumBatchingWindowInSeconds' parameter for given event source

Hello, I have a question how to register servicediscovery instance ?

Hi, just want to know if there is a good example for deploy stack on every pull-request using Github Actions. Thanks for sharing it!

Hi everyone, Austin here from Panther Labs. We have over 13,000 lines of CloudFormation and I'm very excited to try to replace it with Pulumi! However, all of our deployment/automation infrastructure relies on CloudFormation, and it's not feasible to change that right now (we don't control some of the accounts). Has anyone managed to run Pulumi from within CloudFormation, e.g. as a CFN custom resource? I'm picturing the following migration strategy: 1. Add a custom resource (Python Lambda function) to our CFN stacks which runs Pulumi, storing the statefile in S3 in each account 2. Slowly migrate resources from CFN to Pulumi, deleting them from CFN as we go along 3. Eventually, the CFN stack becomes just a thin wrapper around Pulumi 4. When we're ready, we can remove CFN entirely, move the statefile to the Pulumi web service, and our deployment automation invokes pulumi directly

Think I've run into issues starting with delete before create for vpc related resources created by crosswalk. I manually edited the stack after deleting suggested resources. However, I might have exacerbated the problem by removing too many resources before destroying my stack. Is there a way to sidestep the failure and delete the other resources that it can find? I don't see any suggestion here regarding a stack export.

Resources:
    - 22 to delete

Do you want to perform this destroy? yes
Destroying (dev):
     Type                        Name               Status                  Info
     pulumi:pulumi:Stack         pulumi-vpc-ts-dev  **failed**              1 error
 -   └─ aws:ec2:InternetGateway  clientVpc1         **deleting failed**     1 error
 
Diagnostics:
  aws:ec2:InternetGateway (clientVpc1):
    error: deleting urn:pulumi:dev::pulumi-vpc-ts::awsx:x:ec2:Vpc$awsx:x:ec2:InternetGateway$aws:ec2/internetGateway:InternetGateway::clientVpc1: 1 error occurred:
        * Error waiting for internet gateway (igw-07bf9c311ca705fe8) to detach: couldn't find resource (31 retries)
 
  pulumi:pulumi:Stack (pulumi-vpc-ts-dev):
    error: update failed

Hi, I keep getting

update     [diff: ~viewerCertificate]

even if I didn't make any change to my cloudfront configuration, is there any way to avoid this? there's nothing fancy over there, it's just a cloudfront domain without route53, pointing to an s3 bucket

viewerCertificate: {
   cloudfrontDefaultCertificate: true,
   sslSupportMethod: 'sni-only',
},

const myVpc = new aws.ec2.Vpc("myVpc", {     cidrBlock: "10.0.0.0/16",     tags: {         Name: "DemoVpc",     }, }); const mySubnet = new aws.ec2.Subnet("mySubnet", {     vpcId: myVpc.id,     cidrBlock: "10.0.0.0/16",     tags: {         Name: "DemoSubnet",     }, }); const fooNetworkInterface = new aws.ec2.NetworkInterface("ExcelNetworkInterface", {     subnetId: mySubnet.id,     privateIps: ["10.0.0.100"],     tags: {         Name: "primary_network_interface",     }, }); const fooInstance = new aws.ec2.Instance("fooInstance", {     ami: "ami-008806d238cf70838",     instanceType: "t2.micro",     networkInterfaces: [{         networkInterfaceId: fooNetworkInterface.id,         deviceIndex: 0,     }],     creditSpecification: {         cpuCredits: "unlimited",     }, });

How can I get the Image URI of a Docker container I pushed to an ECR? I can't use the awsx package for building and pushing the ECR image for a Lambda (because Localstack doesn't support Lifecycle Policies yet) - so I'm trying to wire everything without awsx (Thanks!)

does anybody have problems with DMS replication tasks and logging? It seems that if we enable logging, pulumi will always try to update the task settings because of cloudwatch log group/log stream

Anyone know how I can get the AWS account number of the current provider for a ComponentResource

Something like:

export const { accountId } = pulumi.output(aws.getCallerIdentity());

Is there a way to force pulumi to wait when the autoscaling group is refreshing the instance? Right now the change has been made in aws but the rolling is beeing execute and pulumi already finish

Hi, is there a way to add tag to the existing resources like subnet? Thanks for the help.

Hey, I have an RDS Aurora Postgres Cluster Question (in thread)…

I'm stumped and could use some help. I am getting this error on one of my Pulumi projects, but not others

error: Preview failed: 1 error occurred:
        * error configuring Terraform AWS Provider: no valid credential sources for Terraform AWS Provider found.

I followed a recent thread and set a bunch of config variables, but that doesn't help

aws:profile                    xxxxxx
aws:region                     us-east-1
aws:skipCredentialsValidation  false
aws:skipGetEc2Platforms        false
aws:skipMetadataApiCheck       false
aws:skipRegionValidation       false

I'm using Pulumi 2.23.1. Tried going back a few versions, but that didn't help either. I know the credentials from the aws:profile work because I can use them with awscli.

Hey guys, I'm trying to create an EKS managed node group with taints. I've added the taints to the nodeGroupOptions argument of the cluster. But when I create a managed node group with eks.createManagedNodeGroup, the taints don't appear on the nodes. Any hints? I'm using typescript. Thanks

Reposting in channel, since I got no response… I want to create a cluster with a role that gives it access to s3 for import/export.  When I include the role in the 

iamRoles

 property I get an error saying:

DBClusterRoleNotFound: Role ARN arn:aws:iam::xxx:role/xxx-xxx cannot be found for DB Cluster: xxx. Verify your role ARN and try again. You might need to include the feature-name parameter.

if I use 

RoleAssociation

 which has feature name I get an error like:

error associating RDS DB Instance (api-rds-cluster-dev) IAM Role (arn:aws:iam::xxx:role/xxx): DBInstanceNotFound: DBInstance not found: xxx

What’s a good working example of creating an RDS cluster with a role associated to it?

Using AWS and Typescript. Is there any way to enumerate a list of IAM users from an existing IAM group? I can use the

aws.iam.Group.get

method to get the group, but I'm not sure how to actually access the existing group membership.

Hello folks, I have a pulumi stack where the launch template triggers the Autoscaling group instance refresh updates. When i am changing the ami parameter of the Launch template through Pulumi to trigger the asg instance refresh, it doesn’t detect anything. The asg api for launch template trigger is as

instance_refresh=aws.autoscaling.GroupInstanceRefreshArgs(
                strategy="Rolling",
                preferences=aws.autoscaling.GroupInstanceRefreshPreferencesArgs(
                    instance_warmup=120,
                    min_healthy_percentage=50,
                ),
                triggers=["launch_template"],
            ),

Can someone please help and guide?

I’m in the process of implementing Managed Node Groups and I’m having trouble getting updates to work the way I’d like. With regard to the scaling config, I’m setting a min of 3 hosts and a max of 100. I’d like the cluster-autoscaler to do it’s thing and be able to scale way down if we don’t need the capcity. This becomes a problem considering

desiredSize

is a required value. This size will clobber whatever the cluster-autoscaler has landed on. I’ve tried using

ignoreChanges: ['scalingConfig.desiredSize']

but this option seems to be completely ignored. I’ve tried searching through the docs, it seems like this example is missing some key functionality, unless I’m not seeing something obvious.

Hi there, I am having issue with one of my engineers , we all have M1 Macs and she's the only one with this issue:

```Previewing update (tam):
     Type                     Name            Plan       Info
 +   pulumi:pulumi:Stack      link-tam        create     
     └─ pulumi:providers:aws  default_3_31_0             1 error
 
Diagnostics:
  pulumi:providers:aws (default_3_31_0):
    error: no resource plugin 'aws-v3.31.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource aws v3.31.0`

```

the stack is brand new and she's using the pulumi built for M1 ... No idea why is tying to load that version of the plugin. In other stacks we are on 3.34.1. I solved this for another engineer by changing the version in the json in the state .. but here I am stuck as there's no state yet. Thanks

FYI, I’ve implemented a typescript package for creating and validating AWS IAM Policy documents. It also parses JSON policy documents and serialises to JSON policy documents. At this stage, it is just the bare minimum that I needed. https://github.com/thinkinglabs/aws-iam-policy

I've got an application listener which I'm trying to add a rule to which has both host header and path pattern condition blocks. This should be supported, however I'm getting the following error:

Only one of host_header, http_header, http_request_method, path_pattern, query_string or source_ip can be set in a condition block

This was an issue in Terraform that was resolved Dec 2019 https://github.com/hashicorp/terraform-provider-aws/issues/11323