Managing multiple Kubernetes clusters is a daily reality for DevOps and SRE teams. Whether switching between development, staging, and production environments, or working across multiple cloud providers, safe and efficient Kubernetes context management is critical to avoid operational mistakes.
Working with multiple AWS accounts is common in modern cloud environments, especially when following multi-account strategies for security, compliance, or environment separation (e.g., dev, staging, prod).
However, switching between these accounts in the AWS CLI can quickly become painful if you rely only on raw profiles. Fortunately, there are tools and tricks that make account switching much more convenient and efficient.
An EKS-optimized AMI with a custom kernel can be valuable when you require the AWS-tuned EKS base image for Kubernetes while also needing kernel-level optimizations or features not included in the default Amazon Linux kernel.
I use Pritunl to connect to the office VPN. It needs entering a two-factor authentication token generated by okta app on my phone. All below run on macOS however, can be adopted on linux as well.
AWS encourages users to migrate from gp2 to gp3 for better performance and lower costs.
Amazon EC2 provides access to spare EC2 compute capacity in the AWS Cloud through Spot Instances at savings of up to 90% compared to On-Demand prices. The only difference between On-Demand Instances and Spot Instances is that Spot Instances can be interrupted by Amazon EC2, with two minutes of notice, if Amazon EC2 needs to reclaim the capacity.
