Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
m
microscopic-painting-1312
09/26/2022, 6:33 PMI’m having some issues with awsx.ecs.FargateTaskDefinition in python.
1. pulumi creates a log group but doesn’t actually use that group. I end up having to manually pass a log_configuration to FargateTaskDefinition, which results in a second log group (the first with pulumi’s auto-naming doesn’t get used).
2. I have to pass a policy to execution_role in FargateTaskDefinition to allow CreateLogGroup, CreateLogStream, and PutLogEvents
Not sure if these are related or if they are issues on my end
If I don’t do those steps, I get this error:
ResourceInitializationError: failed to validate logger args: create stream has been retried 7 times: failed to create Cloudwatch log stream: RequestError: send request failed caused by: Post https://logs.undefined.amazonaws.com/: dial tcp: lookup logs.undefined.amazonaws.com on 172.31.0.2:53: no such host : exit status 1
s
stocky-restaurant-98004
09/26/2022, 7:02 PMThis sounds like a bug in AWSX. Can you file a GH issue?
👍 1
m
microscopic-painting-1312
09/26/2022, 8:56 PMActually, it looks like it’s already resolved. I reinitialized my pulumi project (in the process of trying to make the bug reproducible) and it went away!!
I think it had something to do with not defining my region