Hacker News new | ask | show | jobs
by greyskull 2197 days ago
I think CodeArtifact loses value when you aren't using a package manager; the benefit is an api-compatible service with various controls and audits built on top.

Out of curiosity, what would you want from this service for the "plain binary" use-case when S3 already exists?

2 comments

I think mainly the ease of having security dealt with around who can access etc really. Ofc you can just upload files and serve them over http, but I'd like something that's as easy to setup and use as nexus for these files - and something that forces a structure for how they are organised. Stops arguments and people doing whatever they want.
>> I think mainly the ease of having security dealt with around who can access etc really. Ofc you can just upload files and serve them over http,

This is where S3 really shines. You can give developers access through group membership while servers using instance profiles. We have implemented a fine grained access control for the S3 repos that works really well. Of course you access the content via HTTPS.

Fair enough, I dislike having the idea of having disparate systems where one type of the same thing is stored on a different system from a second type of the same thing.

IAM is on the AWS repo aswell isn't it? I guess it wouldn't be so bad then.

It’s nice having the metadata around the push available versus raw blobs to s3.
Objects in S3 can have custom metadata associated with them. Look at the returned data for the HeadObject call.[0]

It's not advertised in the documentation, but HeadObject(Bucket, Key)['Metadata'] is a neat dictionary of custom values.

0: https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObje...

S3 supports metadata (see https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-o...).

Perhaps I don't understand what you're saying fully though--as I don't fully understand your comment.