Hacker News Reader

Comment by artwr | Hacker News Reader

One of the other question is whether you have to delete all data / close your account 60 days after you transfer out without fee: https://twitter.com/QuinnyPig/status/1765102310563500521

Probably obeying the letter of the European Data Act, but obviously not great if true.

View on HN

> Probably obeying the letter of the European Data Act, but obviously not great if true.

Does it really matter? As long as they are upfront about the price and there is no vendor lock in, what's the big deal? AWS is overpriced - everyone knows that, but i don't think its morally wrong to be overpriced as long as you aren't deceptive about it.

This is addressed in the article. The answer is no.

Nope

> We don’t require you to close your account or change your relationship with AWS in any way. You’re welcome to come back at any time. We will, of course, apply additional scrutiny if the same AWS account applies multiple times for free DTO.

Then compare that statement with their FAQ,https://aws.amazon.com/ec2/faqs/#Data_transfer_fees_when_mov...

> After your move away from AWS services, within the 60-day period, you must delete all remaining data and workloads from your AWS account, or you can close your AWS account.

If you manage to delete everything and make the billing to be zero dollars, then there's no need to close the account...

In many cases, this is way harder than it sounds.

If someone manages that, they're a god.

Beginner here, but shouldn't `terraform destroy` make this very easy? Assuming you deploy everything with IaC.

I don’t think terraform will recursively delete everything in your S3 bucket.

Iterate over all S3 buckets in your terraform files and add `force_destroy` to them [1], then apply and destroy.

There could probably be an automated tool for this that wouldn't be too complex.

[1] https://registry.terraform.io/providers/hashicorp/aws/latest...

Does that take care of deleting the files inside the bucket? That's an API call ($). Depending on the data that could be quite a bit.

Delete API calls are free, listing the objects in a bucket to know what to delete is not.

There can be resources created implicitly, even when using IaC tools. One example, create a lambda, without an explicit log group, one will be automatically created for you outside of the tracked state.

So the lambda function will survive, but billing will still go to zero when the lambda's last execution finishes, right?

The function would be destroyed (guessing running instances would finish their handlers and then no longer be accessible) but the log group it created would still be present, holding logs from the dead function.

That sounds stupid, thanks. Guess I'll be careful when I set up lambdas.

Is this true? I know it's not true when using terraform for things like ECS. I suppose I can just test this myself.

Some things are impossible to destroy immediately. KMS keys take 60 days to remove.

You can also start the close account process which takes 60 days and just pay the fees for anything not torn down and then it all gets nuked at the end of that period.

Reply on news.ycombinator.com