wide-jackal-86020
03/25/2021, 1:39 AMconst helloService = new awsx.ecs.FargateService(...)
2. Load balancer const alb = new <http://awsx.lb|awsx.lb>.ApplicationLoadBalancer(...)
3. Listener export const backendListener = alb.createListener(...)
4. Target groups const helloTarget = alb.createTargetGroup()
5. Listener Rules: const helloRule = new <http://aws.lb|aws.lb>.ListenerRule()
My question is how can I connect the helloRule
to the helloService
?
For example, helloService1
should response to requests matches hellowRule1
, and helloService2
should response to requests matches helloRule2
.victorious-sugar-42620
03/25/2021, 5:41 PMwhite-secretary-18260
03/25/2021, 6:54 PMOutput<T>
(in typescript) to use a generated bucket name new-bucket-[the magic hash number]
in a previous task as a string value in an IAM policy in a later script:
const importPolicy = {
Version: '2012-10-17',
Statement: [
{
Sid: 's3Import',
Action: [
's3:GetObject',
's3:ListBucket'
],
Effect: 'Allow',
Resource: [
`arn:aws:s3:::${newS3.bucket}`, // <-- does not work
`arn:aws:s3:::${newS3.bucket}/*` // <-- does not work
]
}
]
}
white-secretary-18260
03/25/2021, 6:55 PMnewS3
is an aws.s3.Bucket
.square-dress-80180
03/25/2021, 10:44 PMwide-jackal-86020
03/25/2021, 10:53 PMtargetGroup
does not have an associated load balancer. The target groups are created with alb.createTargetGroup()
Diagnostics:
aws:ecs:Service (backend-nginx): error: 1 error occurred:
* InvalidParameterException: The target group with targetGroupArn arn:aws:elasticloadbalancing:us-west-2:617706700270:targetgroup/backend-nginx-tg-041ec1c/55dd1342456346aa does
not have an associated load balancer. "backend-nginx-5a1a7c5"
pulumi:pulumi:Stack (ingenio-backend-dev):
error: update failed
awsx:x:ecs:FargateTaskDefinition (backend-hello):
warning: WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
<https://docs.docker.com/engine/reference/commandline/login/#credentials-store>
aws:ecs:Service (backend-hello):
error: 1 error occurred: * InvalidParameterException: The target group with targetGroupArn arn:aws:elasticloadbalancing:us-west-2:617706700270:targetgroup/backend-hello-tg-6614d94/57f5672e4de31767 does
not have an associated load balancer. "backend-hello-9844a6d"
bulky-continent-73012
03/26/2021, 1:10 PMstack export
and find the "pending_operations".
Now i have a json file which indicate k8scicd-eks-cluster-08ef97b:k8scicd-eks-nodegroup"
is in pending_operations.
How can i resolve this issue?broad-dog-22463
03/26/2021, 2:00 PMpurple-jelly-68780
03/28/2021, 11:15 PMpulumi up
has been running for about 25 minutes now while pushing my image to ECR. From the diag logs in the console I can tell it is making progress but this seems like an inordinate amount of time to takeacceptable-stone-35112
03/29/2021, 7:32 AM* error creating ElastiCache Cache Cluster: CacheSubnetGroupNotFoundFault: Cache Subnet Group redis-subnet-group-ec90733 does not exist.
status code: 400
adding dependencies explicitly doesn't help
const subnetGroup = new SubnetGroup("redis-subnet-group", { subnetIds: sids.ids })
const nsg = new SecurityGroup("sgredis", {
vpcId: vpc.id,
ingress: [{
fromPort: redisConfig.port,
toPort: redisConfig.port,
protocol: "tcp",
cidrBlocks: [vpc.cidrBlock]
}]
})
const cluster = new elasticache.Cluster("redis-cluster", {
preferredAvailabilityZones: redisConfig.availabilityZones,
nodeType: redisConfig.nodeType,
numCacheNodes: 1,
subnetGroupName: subnetGroup.name,
engine: "redis",
securityGroupIds: [nsg.id]
}, { dependsOn: [subnetGroup, nsg] })
silly-address-30441
03/29/2021, 5:16 PMerror modifying DB Instance (read-replicaf4d753f): InvalidParameterCombination: Cannot change master user password on an RDS postgres Read Replica because it uses physical replication and therefore cannot differ from its parent
even though the replica was created and visible in the console. Is there a trick I'm missing?white-secretary-18260
03/29/2021, 7:26 PMFargate Task Definitions
in an ECS cluster
with an Event Rule
with cron
? If so what’s a good example?chilly-magazine-6129
03/30/2021, 1:52 AMwonderful-napkin-50018
03/30/2021, 1:06 PMmysterious-oyster-86659
03/30/2021, 4:49 PMCloudWatch
metric (i.e. PercentDiskSpaceUsed
) and alarm to. This is achievable via the console and - to an extent - with Pulumi.
I can generate the alarm easily via aws.cloudwatch.MetricAlarm
, but it seems that the association part of "attaching" that metric to the cluster is unclear.
Is there a way to do this? I feel like I'm missing something quite obvious despite a lot of research...😅broad-hairdresser-1495
03/30/2021, 6:08 PMpulumi import
when storing this in local file
after this command pulumi import aws:ec2/instance:Instance myInstanceName i-0ba17989210ad396a
i get this output (and a .pulumi/aws_test.json file with whole EC2 instance):
import pulumi
import pulumi_aws as aws
eu1tst_rhtestloadgen002 = aws.ec2.Instance("eu1tst-rhtestloadgen002",
ami="ami-04c89a19fea29f1f0",
ebs_optimized=True,
get_password_data=False,
instance_type="c4.2xlarge",
source_dest_check=True,
tags={
"Name": "eu1tst-rhtestloadgen002"
},
opts=pulumi.ResourceOptions(protect=True))
this works fine when running pulumi up
and i get no changes.
but how do i make volume changes on existing AWS EC2 instance after import?flat-oil-27395
03/30/2021, 7:23 PMicy-jordan-58549
03/31/2021, 4:08 PMwonderful-napkin-50018
03/31/2021, 4:54 PMfull-artist-27215
03/31/2021, 4:58 PMtriggers
parameter for API Gateway deployments? Best I can find is https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/api_gateway_deploymentwide-journalist-154
03/31/2021, 7:21 PMpurple-jelly-68780
03/31/2021, 7:46 PMchilly-hairdresser-56259
03/31/2021, 9:30 PMbroad-hairdresser-1495
04/01/2021, 12:02 PMpulumi import aws:ebs/volume:Volume id vol-049df61146c4d7901
Previewing import (aws_import):
Type Name Plan Info
pulumi:pulumi:Stack aws_import-aws_import 1 error
= └─ aws:ebs:Volume id import 3 errors
Diagnostics:
pulumi:pulumi:Stack (aws_import-aws_import):
error: preview failed
aws:ebs:Volume (id):
error: aws:ebs/volume:Volume resource 'id' has a problem: AtLeastOne: "size": one of `size,snapshot_id` must be specified. Examine values at 'Volume.Size'.
error: aws:ebs/volume:Volume resource 'id' has a problem: AtLeastOne: "snapshot_id": one of `size,snapshot_id` must be specified. Examine values at 'Volume.SnapshotId'.
error: Preview failed: one or more inputs failed to validate
is there another way of importing ebs volumes and manage them?
used this guide:
https://www.pulumi.com/docs/reference/pkg/aws/ebs/volume/#importlimited-pager-46264
04/01/2021, 1:55 PMwarning: security_groups is deprecated: Use of `securityGroups` is discouraged as it does not allow for changes and will force your instance to be replaced if changes are made. To avoid this, use `vpcSecurityGroupIds` which allows for updates.
When creating instances using python, am I supposed to use vpcSecurityGroupIds
instead of security_groups
?limited-pager-46264
04/01/2021, 2:06 PMbumpy-laptop-30846
04/01/2021, 2:10 PMType Name Status Info
pulumi:pulumi:Stack poc-us-1-dev **failed** 1 error
- └─ aws:ec2:SecurityGroup poc-us-1-eksClusterSecurityGroup **deleting failed** 1 error
- └─ aws:ec2:SecurityGroup poc-us-1-eksClusterSecurityGroup deleting... completing deletion from previous update
Diagnostics:
aws:ec2:SecurityGroup (poc-us-1-eksClusterSecurityGroup):
error: deleting urn:pulumi:dev::xxx:ec2/securityGroup:SecurityGroup::xxxlusterSecurityGroup: 1 error occurred:
* Error deleting security group: DependencyViolation: resource xxx has a dependent object
status code: 400, request id: xxx
pulumi:pulumi:Stack (poc-us-1-dev):
error: update failed
The previous update is actually finished.
Even pulumi destroy does not work. I am blocked.
Do you see a ‘clean’ way out ?gifted-terabyte-92288
04/01/2021, 6:22 PMpulumi up
or `pulumi refresh`:
error: Preview failed: unable to discover AWS AccessKeyID and/or SecretAccessKey - see <https://pulumi.io/install/aws.html> for details on configuration
Neither command will get past this point. I have the AWS profile configured and it has worked up until this morning. The AWS CLI still works as expected. Any insights into how I can track down the issue?agreeable-ram-97887
04/01/2021, 7:24 PMmysterious-wolf-74677
04/01/2021, 9:57 PMAll attributes must be indexed.
mysterious-wolf-74677
04/01/2021, 9:57 PMAll attributes must be indexed.