---
title: "Discussion on \"Storing Build Artifacts in AWS S3 and Nexus Repository Manager via Jenkins\" | Hashnode"
description: "Discussion on \"Storing Build Artifacts in AWS S3 and Nexus Repository Manager via Jenkins\". After Jenkins builds your Java application and produces a WAR file, that artifact needs to go somewhere safe and retrievable. Leaving it in the Jenkins workspace is not a real option, workspaces get cleaned, servers get terminated, and builds get replaced. Every time a new build runs, the previous artifact is overwritten.\n\nThis post covers two artifact storage options: AWS S3 (simple, cloud-native) and Nexus Repository Manager (enterprise-grade, self-hosted). Both integrate with Jenkins, and understanding both gives you flexibility to use whichever fits your project's needs."
url: "https://hashnode.com/posts/storing-build-artifacts-in-aws-s3-and-nexus-repository-manager-via-jenkins/6a2a760d42b9e3c6b364d1d5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Storing Build Artifacts in AWS S3 and Nexus Repository Manager via Jenkins](https://saipraneethbhattu.hashnode.dev/storing-build-artifacts-in-aws-s3-and-nexus-repository-manager-via-jenkins?utm_source=hashnode&utm_medium=feed)

After Jenkins builds your Java application and produces a WAR file, that artifact needs to go somewhere safe and retrievable. Leaving it in the Jenkins workspace is not a real option, workspaces get cleaned, servers get terminated, and builds get replaced. Every time a new build runs, the previous artifact is overwritten. This post covers two artifact storage options: AWS S3 (simple, cloud-native) and Nexus Repository Manager (enterprise-grade, self-hosted). Both integrate with Jenkins, and understanding both gives you flexibility to use whichever fits your project's needs.

Jun 11 · 9 min read · saipraneethbhattu.hashnode.dev  
Read the article

-   [#artifacts](https://hashnode.com/tag/artifacts)
-   [#nexus-repository](https://hashnode.com/tag/nexus-repository)
-   [#aws-s3](https://hashnode.com/tag/aws-s3)
-   [#jenkins-devops](https://hashnode.com/tag/jenkins-devops)
-   [#jenkins-pipeline](https://hashnode.com/tag/jenkins-pipeline)

## Written by

[SAI PRANEETH BHATTU](https://hashnode.com/@saipraneethbhattu)

@saipraneethbhattu · Detroit, Michigan

  
[View profile](https://hashnode.com/@saipraneethbhattu)

DevOps & Cloud Enthusiast

Passionate about Cloud and DevOps engineering. I write structured technical notes and beginner-friendly articles on AWS, Linux, CI/CD, networking, system architecture and modern software delivery workflows.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.