This message was deleted.
# awss
sparse-intern-71089
02/28/2021, 6:46 PMThis message was deleted.
s
square-ability-48831
02/28/2021, 7:21 PMinteresting, it took 48 minutes for the debug output to give me a
Copy code
failed getting account information via iam:GetUser: ExpiredToken: The security token included in the request is expiredsquare-ability-48831
02/28/2021, 7:25 PMforgot a
pulumi config set aws:profile namesquare-ability-48831
02/28/2021, 7:45 PMok, got the right dns zone ID, but now hanging again for 15+ minutes on
Copy code
I0228 11:28:55.823052 78069 eventsink.go:62] eventSink::Debug(<{%reset%}>Registering resource: t=aws:route53/record:Record, name=********.com, custom=true, remote=false<{%reset%}>)square-ability-48831
02/28/2021, 8:12 PMlooks like it's isolated to the ACM cert creation. commenting all but the s3 buckets allowed them to be created. now just goes silent for minutes on end after grabbing the right zone file info. been 10 minutes. is this example still the best way to get a cert and validation records set up? https://github.com/pulumi/examples/blob/master/aws-ts-static-website/index.ts#L88
i
important-appointment-55126
02/28/2021, 8:51 PMi based my own static site deployment off of that script, including the cert generation, etc.. that part is definitely the slowest and can take a few minutes at least.. though i don't think i've waited 10+
s
square-ability-48831
02/28/2021, 8:54 PMthanks, i gave in and manually created the cert and provided an ARN, which worked great. would still like to get the cert and validation into pulumi but not a huge deal at the moment, wonder if it's a module incompat with newer
pulumi/awsi
important-appointment-55126
02/28/2021, 8:58 PMi haven't tried mine for a little bit; will have to see if that's the case when i have a bit of free time
w
white-balloon-205
03/01/2021, 7:30 AM
The cert taking >15 mins is expected on AWS - though we should likely make that not the default in that example (or warn about how long it will take!).
The hang when you have expired credentials is something we would definitely like to fix - it’s due to the issue tracked in https://github.com/pulumi/pulumi-aws/issues/814#issuecomment-597991455.
👍 1
2 Views