I'm just starting out with AWS at a medium-sized company and I've heard that JFrog can be pretty pricey on licensing. I'm considering setting up Nexus as a local artifact repository, and for our staging and production environments, I thought we could use AWS CodeArtifact since our entire infrastructure is on AWS. This setup would help us save on costs related to downloading artifacts for local use. I'm looking for insights on the pros and cons of this arrangement.
2 Answers
Absolutely! You can store your artifacts in AWS and then set up Nexus as a pull-through cache. This way, it can fetch what you need and keep your local artifacts organized while utilizing AWS for staging and production.
Can you provide more details on your use case? In many companies I've worked for, we maintained a single artifact repository across all environments. I understand the idea behind separating production and non-production, but I'm curious about why you specifically want a local setup.
I think some organizations with strict security requirements may enforce that you can only deploy to production repositories through certain processes. But generally, there isn't much need for a separate 'prod' registry since containers are usually pre-packed in secure environments.