Now, I'm going to clear my terminal and navigate back to sadcloud.
If you executed Terraform to create a sadcloud environment,
you will be paying for those resources.
What we want to do is run terraform destroy,
which will erase everything that was created for sadcloud.
However,
when we run that, it fails miserably, and it does so
because the environment variables are now set to the Scout
Suite account that is read only.
So I'm simply going to re‑export my AWS access key ID and my AWS secret
access key to keys that have root privileges. I'm going to clear my
terminal so I don't have to keep blurring,
and I am going to run terraform destroy.
It's asking us if we're sure we want to destroy everything.
And as you can see, it's going to destroy 43 things,
even though 45 were created, but that's because in the
demo I deleted 2 of them. So I say yes,
and now it's going through my Amazon account and it's making sure
all these objects that it created are gone.
So now all these vulnerable objects are gone,
but I can also go into my IAM configuration and make sure I enable
multi‑factor authentication for my root account, and all of that which I
hadn't done because this was just a demo account.
So don't forget this step if you created the environment with
sadcloud; otherwise, you'll be paying for these resources and you
might also get your Amazon account hacked,
which could allow someone to spin up a bunch of really expensive
different instances to mine Bitcoin or Litecoin,
for example.