chilly-hairdresser-56259
05/08/2020, 9:12 PMhundreds-lizard-14182
05/08/2020, 9:18 PMchilly-hairdresser-56259
05/08/2020, 9:22 PMhundreds-lizard-14182
05/08/2020, 9:28 PMbillowy-army-68599
white-balloon-205
us-east-1
, you should set the region to us-east-1
and pulumi destroy
to cleanly tear down what you had (partially) deployed thre.
Then you can re-deploy into another region by creating a new stack that is targetting the new region.
Note that you can also create an instance of aws.Provider
targeting a specific region, so you can have a stack with resources deployed to multiple regions. You could alternatively use that to create the new resources in the new region while allowing the old resources to still access the old region (and thus be destroyed cleanly).
As for failing faster when you tried to get in this situation we have https://github.com/pulumi/pulumi-aws/issues/879 tracking some improvements we hope to be able to make here.billowy-army-68599
aws.Provider
is region specific. You could also remove the old bucket from your pulumi state using pulumi state delete <urn>
and rerun, which would then create a new bucket for youhundreds-lizard-14182
05/11/2020, 3:26 PMbillowy-army-68599
breezy-hamburger-69619
05/11/2020, 7:02 PMus-east-1
— I’ve personally hit this in the AWS console a handful of times as well in that region, where as us-east-2
or us-west-2
have better successhundreds-lizard-14182
05/12/2020, 1:55 PM