I'm afraid you are wrong and maybe suffering a bit from AWS Stockholm syndrome. Vanilla Kubernetes is far easier to setup and far faster to deploy/update than any AWS solution involving a pig/alb/vpc/sg/ec2/ECS/etc. The only downside is that you'll have to forego AWS's global deployments and redundancy as well as higher-level service offerings such as logging, alarms, tracing, etc. Nevertheless, that downside is countered by the drastic reduction in operational cost resulting from not being price gouged by AWS.
Re:Docker container security cheat sheet
by peakaboo on Tuesday August 03, 2021 @10:50AM
(#28049878)
Hmm. Every company I've been where they had internal kubernetes, it was a complete mess and constant production issues.
Is it easier (and safer) than AWS Lambda/SQS/SNS/DynamoDB/S3? Because that's the alternative I'm considering.
I'm concerned with foregoing AWS's security hardening and redundancy more than global deployments and alarms (at the moment)
What accounts for "drastic reduction in operational cost" in using vanilla kubernates vs ec2? (Is it elb/alb data throughput?)
Re:Docker container security cheat sheet
by ohthehugemanate on Tuesday August 03, 2021 @01:54AM
(#28046081)
use AWS managed Kubernetes. All (most?) of the cloud agnosticism, none of the management complexity.
managing k8s yourself on bare metal is hard. Managed k8s on any provider is a real value.
I 100% agree that offloading to AWS (or Azure or GCP) managed Kubernetes is better than bare metal. Maybe it's worth moving to bare metal later.
I'm more concerned with moving to Docker images, with the associated increase in needing to manage the whole container, vs. Lambda/S3/DynamoDB. I'm especially worried about misconfiguring the images and suddenly some security threats that were handled by Amazon's services are suddenly my responsibility and I fail.
Re:Docker container security cheat sheet
by DeepYogurt on Tuesday August 03, 2021 @12:46AM
(#28045796)
The complexity has to go somewhere
But am I totally wrong?