I'm new to AWS and learning the ropes at my medium-sized company. I've heard that JFrog licenses can be quite expensive, so I'm considering using Nexus as a local artifactory. For staging and production, I thought about utilizing AWS CodeArtifact since our entire system is based in AWS. My main goal here is to cut down on costs associated with downloading from CodeArtifact for local cases. I'd love to hear the pros and cons of this setup from anyone with experience.
2 Answers
Absolutely, you can do that! Just store your artifacts in AWS and set up a pull-through cache in Nexus to streamline things.
Can you share more about your use case? From my experience, most companies stick to a single artifact repository for all environments. While I see the point in separating non-production and production, I'm curious why you'd want a dedicated repository for local needs.
Good point! I guess companies with strict security policies might enforce pushing to production repositories only through specific processes. Generally, though, if you're packaging things for containers, a separate 'prod' registry may not be needed. Plus, I'd avoid using Nexus for images as it adds risk when scaling.