I for one would not purchase any Intel hardware as long as AMD is around. Not that they’re bad or anything, but AMD gives me much Kore “bang for the buck”.
If you have a processor line in mind, let me know. Happy to give them another look, given my experience with AMD is 30 some years old.
And then there’s the cooling. I see you went with a radiator and fan, but I strongly suggest getting some type of liquid cooling. The prices are not that bad anymore (unlike about 10 years ago, which was insane).
I’m not tied to the cooling solution I picked. I just picked something that looked affordable and did what I wanted. I’d love to do liquid cooling so long as it isn’t a pain. I helped my friend back in high school do liquid cooling and it was a proper mess. We came close to shorting his entire rig.
As for the board, you’ll get all kinds of different suggestions. Some people swear by Asus, I’d rather go with Gigabyte (love the Aorus line), so it’ll come down to brand trust at the end of the day.
I have zero brand loyalty here. The boards I’m looking at right now all have embedded wifi with the annoying antenna…I really want bluetooth embedded so it seems like I’ll have to have wifi but just not use it.
I don’t encrypt before I push to S3. Probably bad practice on my part. I just rely on AWS encryption to secure my data. My backups are low-risk (imo). That said, I lock down the bucket so that only my account can access the objects. Compression I use tar cjf
(bzip). Protip: Once the tar file is made, run tar ljf $archiveFile > archiveFile-ls.txt
and store the resulting file along with the tar file in standard storage. That way you know what is in the archive.
Both. Restore Requests
is to copy the data out from Glacier into Standard storage. Note that I said copy. When you perform a restore, your original object stays in glacier and AWS creates a copy to somewhere in S3 that you specify. Once the restore is complete, you can then download the copied object like any S3 object, triggering the Outbound data transfer
fee.
When you go to just about any web site, your browser sets up an encrypted connection between you and the server so that anything you do on the web site can’t be observed by sniffing the traffic.
Let’s Encrypt is a suite of software developed by the Electronic Frontier Foundation to bring this security to anyone with a website (or anyone with a webservice, really). What Let’s Encrypt provides you is a fully trusted certificate chain. As a result of making the certificate free for anyone (and I mean anyone) can use, the certificate is only valid for 90 days.
You can purchase a trusted certificate that lasts longer but renewal is so easy that unless you need a higher “reputation” cert, it’s not worth it. Fun fact: cia.gov uses LE certificates!
Not sure what KanIDM is but they are probably having you use an LE certificate to create a secure connection between clients and servers. It’s free and pretty easy to set up.
Optionally, if you’re technically savvy, you can set up your own Certificate Authority and distribute it on your own. This gives you full control over your certificate linage but my guess is you won’t get the benefits of it.
I typically code a lot of back-end and processor intensive workloads. The issue I have with i5s is that they don’t seem to be as “snappy” as i7s. I’ve worked with both for good long periods of time. When I had an i5 laptop, I had to off-load a good majority of my development to the cloud because I couldn’t do containers and listen to music and run two monitors at the same time. I never had the same issue with i7 processors, even on a laptop.