aloof-dress-1001
05/01/2022, 11:35 AMeks_node_group = aws.eks.NodeGroup(
'eks-node-group',
cluster_name=eks_cluster,
node_group_name='pulumi-eks-nodegroup',
node_role_arn=iam.ec2_role.arn,
opts=pulumi.ResourceOptions(depends_on=[eks_cluster]),
subnet_ids=[
vpc.subnet_ids[1],
vpc.subnet_ids[2],
],
tags={
'Name': 'pulumi-cluster-nodeGroup',
},
scaling_config=aws.eks.NodeGroupScalingConfigArgs(
desired_size=2,
max_size=10,
min_size=1,
),
)
as of now, the scaling does not happen when the node reaches high cpu usage, so we need to add one node manually. can someone help me figure out how to create the scaling the right way? in a managed node group im not using any launch templates that are using an auto scaling group.kind-keyboard-17263
05/01/2022, 4:46 PMnew aws.kinesis.Stream("events", {
shardCount: 1
});
Of course I was already using aws
via import * as aws from "@pulumi/aws
. The problem is that I have the following error while I try to execute the lambda:
ERROR Uncaught Exception {"errorType":"Runtime.ImportModuleError","errorMessage":"Error: Cannot find module '@pulumi/aws/kinesis/index.js'\nRequire stack:\n- /var/task/__index.js\n- /var/runtime/UserFunction.js\n- /var/runtime/index.js","stack":["Runtime.ImportModuleError: Error: Cannot find module '@pulumi/aws/kinesis/index.js'","Require stack:","- /var/task/__index.js","- /var/runtime/UserFunction.js","- /var/runtime/index.js"," at _loadUserApp (/var/runtime/UserFunction.js:100:13)"," at Object.module.exports.load (/var/runtime/UserFunction.js:140:17)"," at Object.<anonymous> (/var/runtime/index.js:43:30)"," at Module._compile (internal/modules/cjs/loader.js:999:30)"," at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)"," at Module.load (internal/modules/cjs/loader.js:863:32)"," at Function.Module._load (internal/modules/cjs/loader.js:708:14)"," at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)"," at internal/main/run_main_module.js:17:47"]}
To the best of my understanding it's not finding the kinesis
module, but I have nothing to install, or I am wrong ?billowy-laptop-45963
05/02/2022, 3:33 PMicy-controller-6092
05/04/2022, 3:24 AMpurple-answer-54279
05/04/2022, 10:39 AMConflictException: Route with key $disconnect already exists for this API
. Is there any full example on how to create this kind of gateway? Thanks for the help🤞brave-processor-54742
05/04/2022, 2:57 PMgreen-daybreak-91402
05/05/2022, 1:43 PMacoustic-island-63332
05/05/2022, 8:26 PMgreen-daybreak-91402
05/06/2022, 2:24 AMnew aws.iam.RolePolicy(
pulumi.interpolate`${this.service.taskDefinition.executionRole.name}-ssm-policy`,
{
might be giving this error?
Argument of type ‘Output<string>’ is not assignable to parameter of type ‘string’victorious-engine-64347
05/06/2022, 12:54 PMproud-art-41399
05/06/2022, 2:06 PM$ pulumi import aws:ec2/launchTemplate:LaunchTemplate internal-services lt-xxxxx
Previewing import (internal-services-dev):
Type Name Plan Info
pulumi:pulumi:Stack internal-services-internal-services-dev
= └─ aws:ec2:LaunchTemplate internal-services import 3
Diagnostics:
aws:ec2:LaunchTemplate (internal-services):
warning: One or more imported inputs failed to validate. This is almost certainly a bug in the `aws` provider. The import will still proceed, but you will need to edit the generated code after copying it into your program.
warning: aws:ec2/launchTemplate:LaunchTemplate resource 'internal-services' has a problem: expected metadata_options.0.http_protocol_ipv6 to be one of [disabled enabled], got . Examine values at 'LaunchTemplate.MetadataOptions.HttpProtocolIpv6'.
warning: aws:ec2/launchTemplate:LaunchTemplate resource 'internal-services' has a problem: expected metadata_options.0.instance_metadata_tags to be one of [disabled enabled], got . Examine values at 'LaunchTemplate.MetadataOptions.InstanceMetadataTags'.
Do you want to perform this import?
When I copy/paste the generated code, it doesn't pass the validations during pulumi up
because of these values:
...
metadata_options=aws.ec2.LaunchTemplateMetadataOptionsArgs(
http_endpoint="enabled",
http_protocol_ipv6="", <-- needs to be either "disabled" or "enabled"
instance_metadata_tags="", <-- needs to be either "disabled" or "enabled"
)
...
I'm not sure how to proceed. I'd manually change the values for existing launch template, but there doesn't seem to be an option to specify these values in AWS console nor using AWS CLI. So I'd either need to bypass the Pulumi checks for matching inputs with the existing resource's values (while specifying `enabled`/`disabled` for the corresponding metadata options) or disable validations using pulumi up
(while leaving the metadata options empty to match the existing resource's values). Is any of these possible or is there any other way how to proceed?few-easter-31331
05/06/2022, 5:25 PMpulumi
with aws-ssm
. I am creating the resource for the Parameter store in SSM but pulumi keeps adding extra unique identification number to the name of the resource and hence changes the name of the key
in the Parameter store. How can I get rid of the extra (unique id attached to each resource's name)?
eg. my key would be "/abc/def"
but pulumi adds this resource instead "/abc/def-aj39872"
, so it becomes impossible to get the key-value pair from the parameter storepolite-napkin-90098
05/06/2022, 9:04 PMaws-native:efs:AccessPoint (TestinfluxAP):
error: operation CREATE failed with "InvalidRequest": Invalid request
I'll post my code in the thread.millions-furniture-75402
05/07/2022, 12:25 PMpulumi-aws
provider with MFA enforce assume roles?
We use a wrapper script that sets the AWS environment variables based on the ~/.aws/sso/
cache (https://github.com/pulumi/pulumi-aws/issues/1366). Works just fine with 4.x
but with the new MAJOR, I receive:
error configuring Terraform AWS Provider: loading configuration: assume role with MFA enabled, but AssumeRoleTokenProvider session option not set
miniature-leather-36855
05/08/2022, 8:08 AMenough-pager-36335
05/08/2022, 12:47 PMalert-spoon-97538
05/09/2022, 3:23 AMup
. How would I go about adding that conditional?victorious-engine-64347
05/09/2022, 9:07 AMdelightful-monkey-90700
05/09/2022, 1:30 PMnode.addEnvironment('ENDPOINT_API', `https://${loadbalancerDomain}/api`);
What's the equivalent in Pulumi ? The node
object is an instance of a Lambda Functiondelightful-monkey-90700
05/09/2022, 2:23 PMconst restAPI = new AWSAPIGateway.LambdaRestApi(stack, 'restAPI', {
handler: nodeAlias,
proxy: true,
restApiName: `xxx-http-${environment}`,
deploy: true,
deployOptions: {
stageName: 'api'
},
endpointConfiguration: {
types: [AWSAPIGateway.EndpointType.REGIONAL]
}
});
I tried using @pulumi/aws-apigateway
but I can't figure out how to make the handler refer to a Lambda Function's alias, and also how to make it a regional APImillions-furniture-75402
05/09/2022, 3:13 PMambitious-forest-23664
05/09/2022, 4:01 PMpulumi:providers:aws default_5_2_0 error: no resource plugin 'pulumi-resource-aws' found in the workspace at version v5.2.0 or on your $PATH, install the plugin using `pulumi plugin install resource aws v5.2.0`
Knowing that at the start of the deploy I have this message
Logged in to ubuntu as ubuntu (<s3://xxx>)
Previewing update (xxxx.staging):
[resource plugin aws-5.4.0] installing
I can clearly see the mismatch but I have no clue why it happensmammoth-oyster-21227
05/10/2022, 11:46 AMpowerful-furniture-83753
05/10/2022, 12:47 PMcurved-pharmacist-41509
05/11/2022, 9:38 AMminiature-leather-36855
05/11/2022, 3:38 PMglamorous-printer-66548
05/11/2022, 9:03 PMwitty-monitor-96481
05/11/2022, 9:33 PMref = pulumi.StackReference('eks_cluster', cluster_name)
core = ref.get_output('core')
eks.ManagedNodeGroup(
'mng',
cluster=core,
node_role=ec2_role,
node_group_name=...
I get this error:
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "Cannot read properties of undefined (reading 'map')"
debug_error_string = "{"created":"@1652304221.921855000","description":"Error received from peer ipv4:127.0.0.1:49189","file":"src/core/lib/surface/call.cc","file_line":953,"grpc_message":"Cannot read properties of undefined (reading 'map')","grpc_status":2}"
Do I need to set parent
to the cluster Output from the reference? or am I missing something?wet-fall-68417
05/12/2022, 11:29 AMerror creating API Gateway v2 route: ConflictException: Route with key $connect already exists for this API
The problem is when i create the aws.apigatewayv2.Api
resource, The $connect route creates automatically.
The only way to create an integration request to a route, is to create the aws.apigatewayv2.Route
resource in pulumi, and set the integration resource in it.
But again, i can’t create the route, because it is already exist.
const exampleApi = new aws.apigatewayv2.Api("exampleApi", {protocolType: "WEBSOCKET"});
const exampleIntegration = new aws.apigatewayv2.Integration("exampleIntegration", {
apiId: exampleApi.id,
integrationType: "HTTP_PROXY",
integrationMethod: "ANY",
integrationUri: "<https://example.com/{proxy}>",
});
const exampleRoute = new aws.apigatewayv2.Route("exampleRoute", {
apiId: exampleApi.id,
routeKey: "$connect",
target: pulumi.interpolate`integrations/${exampleIntegration.id}`,
});
me and @purple-answer-54279 looking for answers for a long time without any feedback! last time @great-queen-39697 managed to help us.
How can we solve it?bored-spoon-83710
05/12/2022, 4:45 PM