Artifactory是否支持将制品归档至AWS S3？及场景需求咨询

Hey Jared, great question—Artifactory is built exactly for these kinds of hybrid storage workflows, and checking all your boxes is totally doable with its built-in features. Let’s break down how to set each part up:

1. Auto-Delete Temporary Artifacts (7-Day Retention) #

• Head to your target repository's settings (Admin > Repositories > Local Repositories > [Your Repo])
• Under the Retention tab, create a new retention rule:
  • Set the rule to delete artifacts older than 7 days
  • Add an exception filter if you want to preserve specific artifacts (e.g., artifacts tagged with keep-long-term or linked to stable builds)
• Enable the rule and set a schedule (e.g., daily at midnight) to run cleanup jobs automatically

2. Long-Term Retention for Low-Frequency Artifacts on AWS S3 #

Artifactory's Smart Storage Tiering lets you offload cold artifacts to S3 while keeping metadata local for fast access:

• First, configure an S3 binary store:
  • Go to Admin > Storage > Binary Stores > Add Store
  • Select Amazon S3 as the provider, enter your AWS credentials (or use IAM roles if running on EC2/EKS), and specify your bucket details
• Create a storage policy to move low-access artifacts:
  • Navigate to Admin > Storage > Storage Policies > Add Policy
  • Define a rule like: "If artifact hasn't been accessed in 90 days, move to [Your S3 Binary Store]"
  • Attach this policy to your repositories—Artifactory will automatically migrate qualifying artifacts to S3, and pull them back to local storage if accessed again

3. Auto-Migrate to S3 When Local Storage Overflows #

Pair storage quotas with tiering rules to handle local storage saturation seamlessly:

• Set a local storage quota:
  • Go to Admin > Storage > Quotas > Add Quota
  • Target your local binary store, set the quota to your X GB limit, and configure a threshold (e.g., 90% of X GB) to trigger actions
• Link the quota to your storage policy:
  • In the quota settings, enable "Automatically migrate artifacts to remote storage when threshold is reached"
  • Configure migration priority to first move artifacts that exceed the 7-day retention window, then low-access artifacts, to prioritize temporary cleanup first

Key Notes to Avoid Headaches #

• Test all rules in a staging repository first to ensure they behave as expected
• Use IAM roles instead of static access keys for S3 to improve security
• Enable storage usage alerts (Admin > Alerts > Add Alert) to get notified before quotas are hit, so you can manually intervene if needed

内容的提问来源于stack exchange，提问作者JaredC