Closed Bug 1621320 Opened 6 years ago Closed 6 years ago

Ensure artifact buckets have correct lifecycle policies

Categories

(Cloud Services :: Operations: Taskcluster, task)

Product:
Cloud Services
Component:
Operations: Taskcluster
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: brian)

Details

In the legacy deployment, we had a policy in place to transition objects in the public and private artifacts bucket to IA after 45 days.

We should have a similar thing for the artifact buckets for the new deployments. A quick scan of the cloudops repo didn't turn up any such policy, but apologies if this is already in place.

We should definitely add the IA transition. I enabled https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html on the firefoxcitc buckets to see if we can be more aggressive than 45 days.

Looking at our buckets, I wonder if they have the correct policies now.It's odd that the setup for public and private is so different. The biggest red flag to me, though, is that there is no expiration policy for either one. Dustin, at what point can we have S3 delete old artifacts?

https://github.com/mozilla-services/cloudops-infra/blob/master/projects/taskcluster/tf/modules/taskcluster/main.tf#L20-L59

Assignee: edunham → bpitts
Flags: needinfo?(dustin)
Summary: Check that older artifacts are IA → Ensure artifact buckets have correct lifecycle policies

That'd be a conversation to have with developers -- I think we've agreed that 1 year is the maximum retention in firefox-ci, but I don't think that's machine-enforced. And, we have some tasks with a longer retention in community-tc because we use their artifacts for other tests, for example. It would be an ugly surprise to find out that an important artifact with an expires property of several years from now mysteriously disappeared after 1 year because of an S3 policy.

Flags: needinfo?(dustin)

Perhaps a missing detail is, Taskcluster is careful to delete artifacts when they expire, without using a lifetime policy (since lifetimes vary greatly).

Thanks for the reminder about taskcluster handling artifact deletion itself.

For the 45-day IA transition, I have https://github.com/mozilla-services/cloudops-infra/pull/2156 up for review.

Status: NEW → ASSIGNED

I've applied this in stage. I'll check back in a day and verify it has transitioned some objects to IA, then apply it to community and firefox ci.

Stage showed some IA storage when I checked today.

I've applied this to community and firefox ci.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED

Looks like this was a ~25% cost savings in prod.

You need to log in before you can comment on or make changes to this bug.