Hey everyone! 👋 I’m trying to create an EKS cluster in a specific region, but I can’t see where to specify the region… 🤔 I thought maybe we had to create a VPC explicitly with that region, but even then I can’t figure how to specify the region for the VPC. Any hint? 😁

Hello folks, i am running into issue of

raise error_class(parsed_response, operation_name)
    botocore.errorfactory.LoadBalancerNotFoundException: An error occurred (LoadBalancerNotFound) when calling the DescribeLoadBalancers operation: Load balancers '[test-lb]' not found
    error: an unhandled error occurred: Program exited with non-zero exit code: 1

where i am running load balancer creating api and running boto call to get an ARN of that load balancer as

load_balancer = aws.lb.LoadBalancer(  # type: ignore
    "Test-LoadBalancer",
    name=stacktname + "-lb",
    load_balancer_type="network",
    internal="true",
    subnets=subnets,
    enable_deletion_protection=True,
)

nlb_name = stackname + "-lb"
try:
    client = boto3.client("elbv2")
except botocore.exceptions.ClientError as error:
    raise error
nlb_response = client.describe_load_balancers(Names=[nlb_name])

loadbal_arn = nlb_response["LoadBalancers"][0]["LoadBalancerArn"]

Is there any way to handle this situation in pulumi or exception?

Hi folks I've been trying to figure something out of this idea: is it possible to have a Resoure ID from one deployment to another? The reason i'm looking for this is, since SES'

Template.get

requires both the name and the id, i cannot find a way to verify if a template exists already. Any ideas? Thanks

Hi there. Are there plans to support localstack? Or, is there a working example showing how to configure pulumi with a localstack provider?

Hi, is there any way to run some pulumi code only when the event "destroy" is running? I would like to detect this "event" to run an extra code.

I have an existing EKS cluster with an unmanaged nodegroup created using the

createNodeGroup

function. I changed the

desiredCapacity

and then looked at the Details of what

pulumi up

wanted to change. I notice the templateBody for the Cloudformation stack has data like this

AWSTemplateFormatVersion: '2010-09-09'
                Outputs:
                    NodeGroup:
                        Value: !Ref NodeGroup
                Resources:
                    NodeGroup:
                        Type: AWS::AutoScaling::AutoScalingGroup
                        Properties:
                          DesiredCapacity: 7
                          LaunchConfigurationName: ...
                          MinSize: 7
                          MaxSize: 10
                          VPCZoneIdentifier: [...]
                          Tags:
                          ...
                        UpdatePolicy:
                          AutoScalingRollingUpdate:
                            MinInstancesInService: '1'
                            MaxBatchSize: '1'

Some details are redacted with

...

. My question... how do we change the

UpdatePolicy

listed at the bottom? I need

MinInstancesInService

to be much higher, but I don't see it as an option to pass when I look at

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/eks/#NodeGroupOptions>

hello friends. I have a basic EKS service set up using the typescript example. What's the shortest way to get a certificate and route53 domain associated with the service ip?

Hey, Anyone knows when this milestone will be released https://github.com/pulumi/pulumi-eks/milestone/34

Hey everyone, does anyone know if there's a way to create an ec2 KeyPair without specifying the public key using pulumi, similar to how you would in the AWS CLI or AWS console? It's currently required for the the pulumi_aws.ec2.KeyPair object to take in a public_key. https://www.pulumi.com/docs/reference/pkg/aws/ec2/keypair/

I noticed that the passwordPolicy of cognito is recognized as changed everytime I update the stack, while actually it is not. Is this a design on purpose? or bug?

Hi! I have this error 

error configuring Terraform AWS Provider: Error creating AWS session: SharedConfigErr: only one credential type may be specified per profile: source profile, credential source, credential process, web identity token, or sso

 when I try to create rds.Instance ...someone could help me?

Hey, Is there an open issue about Pulumi stuck on running… / destroying… / refreshing… when using token to authenticate with AWS? I’m using onelogin-aws-cli-assume-role too to authenticate and there is no error when token has expired it just keeps retrying endlessly…

I get this error

AWS states that: The 

AmazonEC2ContainerServiceFullAccess

 managed IAM policy is being deprecated on January 29, 2021 in response to a security finding with the 

iam:passRole

What can we do to fix this

When creating a

aws.lambda.CallbackFunction

is there a way to manually include node modules? I want to include a module that contains a binary in one of my functions, but I don't want it to subsequently be included in all other lambda functions

Is it possible to use NVME disk on EKS nodes? Is there anything built in?

I'm trying to set up a bucket for cloudtrail logs and the docs seem wrong: https://www.pulumi.com/docs/reference/pkg/aws/cloudtrail/trail/. The bucket name in the policy (

tf-test-trail

) isn't going to match the bucket name that pulumi picks (

foo-<id>

), right? What's the right way to do that? Is there anything like

current

that would let me get the bucket name so I can set the policy correctly?

One other problem. When I'm creating the actual cloudtrail, it is failing with

InvalidCloudWatchLogsRoleArnException: You must specify a role ARN as well as a log group.

did the aws stuff change so that creating a provider no longer uses the like "default" stuff? i now get this error when trying to create a provider in another region:

providerCredentialOpts and an AWS provider instance must be set together

i very much want to not configure the auth options for the provider, just like is the case for the default aws provider

(if this is the case, the example snippet in the docs would be incorrect)

hey folks! 👋 I’m trying to import an existing

aws.ec2.Route

, however I can’t seem to figure the “ID” to feed into the

import:

property. For all other types of resources, the ID is always pretty obvious to figure, but routes don’t seem to have an existence of their own outside the route table, they don’t seem to have an ARN, etc… So how could I import them? 🤔

Hey everyone, I'm looking to deploy a auoscaling group to aws and I'm trying to use the "DetachInstances" action available in the aws doc (https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_DetachInstances.html) but I didn't find anything in the pulumi doc, so i was wondering if it's possible to use it with pulumi 🤔

Hey, Is there a guide for Cluster-Autoscaler using Pulumi?

Is there a way to not wait for a SNS topic subscription to be confirmed? Or, if does timeout, it doesn't prevent the other stack items from processing

Somehow i accidentally removed route table associations from my infrastructure. Was able to re-associate the subnets with the route tables in the AWS console, but now

pulumi refresh

wants to delete them from my state, while

pulumi preview

shows that state matches the code (including import IDs), and isn't trying to create any new ones. Any ideas what's going on here?

Given the following code, how can ensure that my outputs are evaluated prior to the resource creation that relies on it. The following does not appear to work..

export const evaluateEnvironmentVariables = (services: Services, variables: Map<string, Output<string>>): void => {
    for (const service of services) {
        for (const envVar of service.environment) {
            const envVarName = envVar.name.toString();
            const replacementValue = variables.get(envVarName);

            if (replacementValue) {
                replacementValue.apply(value => {
                    envVar.value = value; // envVar.value is Input<string>, value is Output<string>
                });
            }
        }
    }
};

services.evaluateEnvironmentVariables(allServices, variables);

// Create resource that depends on these updated environment variables (KeyValuePair)

Does anyone know how to set the

Concurrent batches per shard

on a lambda’s DDB trigger? I’m using

new aws.lambda.Permission

to create the trigger for a lambda, but I don’t see options on how to increase the batch sizes…