AWS has 200+ services. Most companies use about 15. The same ones show up in every project: EC2, S3, Lambda, RDS, DynamoDB, API Gateway, CloudFront, SQS, SNS, CloudWatch.
That handles 80% of everything. Wrote a guide covering just the ones that matter.

#aws #cloud #infrastructure #EC2 #IAM #S3 #RDS #DynamoDB #Lambda #APIGateway #CloudFront #Route53 #SQS #SNS #CloudWatch #EKS #CDN

https://heyjoshlee.medium.com/the-80-20-of-aws-the-services-that-actually-matter-13509ff90115

Learn how to provision AWS EKS clusters with secure IAM architecture using Terraform — complete with IRSA (IAM Roles for Service Accounts), OIDC provider setup, IMDSv2-enforced node groups, and KMS encryption. Includes ready-to-use Terraform modules.

https://iamdevbox.com/posts/orchestrating-kubernetes-and-iam-with-terraform-a-comprehensive-guide/?utm_source=mastodon&utm_medium=social&utm_campaign=blog_post

#keycloak #terraform #kubernetes #eks #aws

My dear #fediverse, does someone has a nice #ansible repo to setup an #EKS on aws? If I can avoid to start from scratch 😅

#sysadmin #devops #linux #opensource #foss

I wrote up a quick how-to for running data backups inside a Kubernetes cluster using CronJobs. I wish it was as simple as a crontab + bash script like the olden days, but it works well enough. It is nice how declarative and stateless it is though!

https://nbailey.ca/post/backup-k8s-cronjob/

#kubernetes #backup #backups #cronjob #postgres #postgresql #kafka #aws #s3 #eks #bash #terraform #sysadmin #linux #blog #blogpost

So, like, #AWS #EKS.. the kernel defaults for the EKS nodes are by in large, consistent with 10mbps half duplex networking on a workstation. Judging by how many hoops you need to jump through to manage sysctl's on EKS and #K8S in general, I can only see one of two possible explanations:

1) There's some magic kernel module installed for EKS or K8S that obviates the need to tune the kernel for server workloads.

2) We stopped caring about synchronizing the network stack to the network it's connected to and the use of the server because it's cloud and/or K8S and wasting resources is just what we do for the convenience of buying Bezos a new spaceship or super yacht.

I see a ton of network implicated slowdowns in pipelines on EKS.There's a fuckton of dropped packets, retransmits, and context switches. We can tell the kernel to spend a bit more time per cycle on processing network packets. We can increase the default and max buffer sizes for TCP and UDP sockets which are transmitting MASSIVE amounts of data for "15GBps" bursts. We can adjust the TCP timeout to match the AWS network to prevent half-open connections. We can increase the kernel backlog depth for busy services. Maybe, I mean, **I** can. It's a twisted, gnarly, and wholly undocumented nightmare for K8S and EKS mostly involving logging into the EKS nodes and manually setting the sysctls one at a time.. Does anyone have a better way? I've yet to read something that demonstrated how to do this in some sane manner.. FWIW, it was one `file` and one `exec` resource in Puppet to adjust an entire fleet consistently.