https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# getting-started
s
This message was deleted.
s
Are you creating an explicit provider (
new aws.Provider
in TS) instead of using the default?
b
No.
This is quite strange, the change of behaviour was from one day to another, the operation that is giving me this error is pulumi up
The same with pulumi refresh
s
Ah, "no such host"... hmm. What happens if you try to curl that URL?
b
Open AWS page
s
Yeah, I'm seeing the same.
b
Not sure if pulumi does any kind of test but if I run pulumi login against the s3 bucket is goes successful …
s
OH
Are you using S3 to store your state file?
b
I’m trying to, yes
but this situation was also happening with pulumi cloud as a backend
That’s why I’ve moved to S3
s
You shouldn't have to store your state file in S3 unless you want to. Pulumi should never give you an AWS-related message that is not related to the program itself unless you're using AWS for secrets or state file storage.
b
Sorry, I’m a little bit lost here, (also a new to pulumi), from my understand the sts phase if for allowing the deploy of the stack into the provider, so why secrets here, unless I’ve had enable some feature within pulumi without knowing
If is for fetching the state file, then the export and import did not went well…
s
STS would never get hit if you were using Pulumi Cloud as your backend and were not creating AWS resources.
b
Can I delete the state file from the bucket and make a recovery with the resource already created?
s
You should be able to recreate any resources using 
pulumi import
if you delete your state file, but you should delete your state file only as a last resort. If possible tear down the stack (
pulumi destroy
) rather than deleting the state file.
b
I can go back and import the state file into pulumi cloud again, if that’s the problem…. but that was my previous setup when this messages started to popup and preventing the deploy of resources
Yeah, more or less, one of the resources that I built was an member account of the organization, and deleting that is a mess in AWS!
s
If you're learning Pulumi, it's best to stick with Pulumi Cloud as your backend. It's free for individual use forever, and it's easier than managing state file or secrets yourself.
b
And since that fails, the rest will fail also
I understand that point, but having the state file out of a controlled environment is hard to sell to security …
s
Yeah, accounts in AWS do not play so well with IaC because they can't be deleted in the same way. I recommend that you create AWS accounts outside of Pulumi (or any other IaC tool) and then use creds for the new account to mange resources.
Pulumi is SOC2 compliant for what it's worth, but as long as you're learning how to use Pulumi on your own and it's ok with your organization, use Pulumi Cloud just to get comfortable with writing Pulumi programs. When you're looking at organizational adoption, then try using S3/KMS for statefile/secrets.
b
ok
Thank for the help! Awesome
w
Hi guys, I'm facing the same issue but I don't have the option of moving my state fi;es to Pulumi Cloud. could you guys guide me? I did not understand why the error is be thrown. Also, one of my resources uses the 
getCallerIdentity
method which fails, so even if I set the 
skipCredentialsValidation
flag it keeps throwing the error
400 Views
Open in Slack
PreviousNext
Powered by