Abdel SGHIOUAR

If a secret is misconfigured on the cloud, it can easily take down systems or block critical services before anyone has time to react. Mattias Fjellström just published a great deep dive on AWS Secrets Manager and how to manage it with Terraform. It goes beyond the simple setup and shows how to avoid the real-world issues that teams run into when secrets are managed across multiple environments. Here are a few highlights from the post: 🔐 How to configure secrets with Terraform without exposing values in your state file ♻️ Setting up automated rotation using AWS Lambda 🌍 Replicating secrets across regions for availability 🔁 Avoiding issues when secrets are shared across Terraform configurations 🧠 Why context matters when managing infrastructure changes This is the kind of nuance we deal with every day at Anyshift. We built it to give teams a full view of how their cloud infrastructure is connected, so they can make safe decisions before hitting apply. #AWS #Terraform #DevOps

19

1 kommentar

Why does sustainability start at the network layer? 🍃 In Kubernetes environments, inefficiencies in networking can grow quickly, inflating costs and increasing energy use and carbon emissions. Cilium changes that by optimizing network paths, removing unnecessary components, and providing granular observability. Read more about how organizations like ECCO, Kakao, and Seznam are reclaiming resources, cutting bills, and improving sustainability: https://lnkd.in/exP4vNxi

6

One RPC provider is simple. Until it goes down and your app stops working. Multi-provider routing trades simplicity for resilience: • Eliminates single points of failure • Routes traffic to the best-performing providers That’s how production systems should be built.

9

Unlocking Observability by Design With Inferred Schemas Observability systems generate massive telemetry, but schema drift creates friction. Learn how inferred schemas and OpenTelemetry Weaver restore structure.

1

When you scale with Karpenter, you gain speed and flexibility in your EKS cluster. The challenge: monitoring nodes that don’t rely on auto-scaling groups. 👉 At Teracloud, we built a Terraform module that automates the creation and deletion of CloudWatch alarms for every EC2 instance managed by Karpenter. Here’s what you get: ✅​ Proactive visibility into scale events ✅​ Less manual effort, more reliability ✅​ Seamless integration with your EKS environment With this open and adaptable solution, you turn complexity into operational simplicity. 📖 Read the blog and see how to optimize your Karpenter monitoring: https://lnkd.in/d-rFjPYw

7