iiinova — where your digital self keeps evolving

An employee changes departments but still has access to their old department’s systems. Nothing is broken. But is that still a security issue? I think it is. #ITSecurity #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 13h

Access shouldn’t be permanent just because it was appropriate when it was granted. Roles change. Responsibilities change. Permissions should be reviewed too. #AccessManagement #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 19h

Creating a user account is easy. The bigger responsibility is managing that access as the person's role changes and eventually removing it when it is no longer needed. #ITAdministration #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 30/09/2026

An application slows down every weekday around 9 AM, then recovers 30 minutes later. I wouldn’t immediately resize the server. That timing is a clue. I’d investigate what regularly happens during that window. #Troubleshooting #EmmanueleTech

001

Emmanuel Egede @emmanueletech.com · 29/09/2026

A metric is more useful when you know what normal looks like. CPU at 70 percent means more when you know whether the workload normally runs at 20 percent or 65 percent. Baselines matter. #CloudOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 29/09/2026

When an application struggles, adding more CPU or memory might help. But I first want to know why it is struggling. More resources can sometimes hide the real problem. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 28/09/2026

Good infrastructure shouldn’t depend on one person remembering everything. Another engineer should be able to understand the environment, the major decisions and how it is managed. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 28/09/2026

Users suddenly can’t access an application. I wouldn’t start making random changes. Confirm the impact, check logs and metrics, review recent changes and communicate while investigating. Calm troubleshooting matters. #IncidentResponse #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 27/09/2026

Incident response isn’t only technical. While you investigate the problem, people also need to know what is happening. You may not have the answer yet, but you can communicate what you know. #ITOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 27/09/2026

Five people need access to the same system. Would you make all five administrators? I wouldn’t. I’d first understand what each person actually needs to do and assign access around those responsibilities. #CloudSecurity #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 26/09/2026

I don’t think everyone needs administrator access just because it makes things easier. Access should match responsibility. Give people what they need to do their work without giving away unnecessary control. #AccessManagement #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 26/09/2026

I prefer individual accounts over shared credentials. When everyone has their own identity, it becomes easier to understand who has access, who made a change and whose access should be removed. #CloudSecurity #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 26/09/2026

You inherit an AWS environment you didn’t build. Everything works. Would you start changing things? I wouldn’t. First I’d understand the architecture and trace how traffic, routing and access work. Understand before you optimize. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 25/09/2026

I like asking why before how. How do I configure it? Important. Why does the architecture need it? Just as important. Knowing how helps you build. Understanding why helps you design. #CloudEngineering #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 25/09/2026

Knowing the tool and understanding the system are different things. I don’t only want to know how to create infrastructure. I want to understand how the pieces work together and what happens when something fails. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 25/09/2026

I inherit several servers with public IPs. I wouldn’t immediately change everything. First I’d understand why each one is public and what depends on that access. Secure the environment, but understand it first. #CloudInfrastructure #EmmanueleTech

001

Emmanuel Egede @emmanueletech.com · 24/09/2026

Does this resource actually need to be public? It is a simple question, but I think it should be asked more often. Public access should have a reason. #CloudSecurity #CloudNetworking

000

Emmanuel Egede @emmanueletech.com · 24/09/2026

Morning I prefer thinking about security before deployment. Who needs access? What needs to be public? Which ports are actually required? Security works better when it is part of the design. #CloudSecurity #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 24/09/2026

Dashboard is green. Servers are healthy. But users cannot complete an important action. I wouldn’t ignore the users because the metrics look normal. A healthy server doesn’t always mean a healthy service. #CloudOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 23/09/2026

A healthy server doesn’t always mean a healthy service. The infrastructure can look normal while users are still having problems. I want to know what the system sees and what the user experiences. #CloudOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 23/09/2026

Two servers were configured the same way. One works. The other behaves differently. Before rebuilding anything, I’d compare their configurations and recent changes. Sometimes the problem is configuration drift. #CloudEngineering #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 22/09/2026

Two environments can start identical and slowly become different as manual changes happen over time. Consistency matters. When you know what the configuration should be, troubleshooting becomes much easier. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 22/09/2026

What is the single point of failure? It is one of the questions I like asking when reviewing infrastructure. You don’t make failure impossible. You design so the failures that matter don’t take everything down. #CloudInfrastructure #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 21/09/2026

When reviewing infrastructure, I like asking: What happens if this component disappears? Reliability starts with accepting that things can fail and designing around the failures that matter. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 21/09/2026

The website loads normally, but submitting data fails. I wouldn’t immediately restart the web server. I’d follow the request and check what happens between the application and its dependencies. Where would you start? #Troubleshooting #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 20/09/2026

One question helps me a lot when troubleshooting: What does this system depend on? Once you understand the dependencies, you can test them instead of guessing. #CloudEngineering #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 20/09/2026

The component showing the error isn’t always the component causing it. When something fails, I like following the request through its dependencies until I find where it stops. #Troubleshooting #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 19/09/2026

The last error you see may not be where the problem started. I like building a timeline. What happened first? What changed next? That sequence can tell you more than one error message. #Troubleshooting #EmmanueleTech

011

Emmanuel Egede @emmanueletech.com · 19/09/2026

An error on the screen rarely tells the whole story. When something fails, I want to know what the system recorded before and during the failure. Logs help turn guessing into investigation. #CloudOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 19/09/2026

Two architectures meet the same security, availability and performance requirements. One is much more complex than the other. Would complexity influence your choice? For me, it needs to solve a real problem. #CloudEngineering #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 18/09/2026

If someone asks why a resource exists in an environment, there should be an answer. Good infrastructure shouldn’t only make sense to the person who built it. #CloudArchitecture #EmmanueleTech

001

Emmanuel Egede @emmanueletech.com · 18/09/2026

More complex doesn’t automatically mean better infrastructure. Every additional component has to be configured, secured, monitored and maintained. I prefer adding complexity when it solves a real problem. #CloudInfrastructure #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 18/09/2026

Before automating a process, I want to understand it manually. Inputs, expected results and possible failures. Otherwise, automation can just make the wrong process happen faster. #Automation #EmmanueleTech

030

Emmanuel Egede @emmanueletech.com · 17/09/2026

I don’t automate something just because I can. When a task becomes repetitive and predictable, automation starts making sense. The goal is consistency, not automation for its own sake. #Automation #EmmanueleTech

010

Emmanuel Egede @emmanueletech.com · 16/09/2026

Good cloud architecture should make technical sense and business sense. Cost optimization isn’t about choosing the cheapest option. It’s about paying for what the workload actually needs. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 16/09/2026

Traffic doubles. CPU stays high and response time starts increasing. Would you immediately resize the instances? I’d investigate the workload and scaling options first. More capacity isn’t always the whole answer. #CloudEngineering #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 15/09/2026

Auto Scaling is more useful when the metric behind it makes sense. A short CPU spike and sustained high utilization are not necessarily the same problem. Understand normal behavior before automating the response. #CloudOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 15/09/2026

More traffic doesn’t automatically mean I need a bigger server. I want to understand the workload first and decide whether scaling up or scaling out makes more sense. Capacity should follow the workload. #CloudInfrastructure #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 15/09/2026

An application goes down. You restart the service and everything works again. Incident closed? Not for me. I’d still check logs, resources, dependencies and recent changes to understand what happened. #CloudOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 14/09/2026

Building infrastructure is one part of the job. Operating it changes how you think. Once people depend on a system, availability, monitoring, recovery and maintenance become just as important as deployment. #CloudOperations #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 13/09/2026

When one server works and another doesn’t, I compare them before changing anything. Routes, subnets, security rules, DNS and network paths. The working system can help you understand the broken one. #Troubleshooting #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 13/09/2026

A private server may still need outbound connectivity. The question I ask is not simply whether it can reach the internet. I want to know what it actually needs to reach and why. #CloudNetworking #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 13/09/2026

Private EC2 instance. No public IP. No inbound SSH from the internet. You still need administrative access. Would you expose the server, or use another approach? #CloudSecurity #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 12/09/2026

Private does not mean disconnected. A private server can still have the connectivity it needs without being directly exposed to the internet. The important question is which paths it actually needs and why. #CloudNetworking #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 12/09/2026

I don’t want to expose SSH to the internet just because I need to manage a server. If an EC2 instance can stay private while I manage it securely through Systems Manager, I prefer that design. #CloudSecurity #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 12/09/2026

I’m learning that cloud engineering isn’t about memorizing AWS services. It’s about knowing where to look when something stops working. Route table? Security Group? NACL? DNS? Subnet? That troubleshooting mindset is what I’m working on every day. What helped you get better at troubleshooting?

000

Emmanuel Egede @emmanueletech.com · 11/09/2026

The more I build with AWS, the more I realize that creating a VPC is the easy part. The real skill is understanding how traffic actually moves. Subnets → Route Tables → NAT Gateway → Security Groups → Resources. Build it. Break it. Troubleshoot it. Fix it. That’s where the learning happens. #AWS

000

Emmanuel Egede @emmanueletech.com · 11/09/2026

You change one line of Terraform. The plan now wants to replace an existing resource. Would you apply? I’d first understand why it needs replacement and what depends on that resource. #Terraform #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 10/09/2026

Infrastructure as Code is not just about automation for me. I also want infrastructure I can read, review and reproduce without depending on memory. That is one reason I use Terraform. #Terraform #EmmanueleTech

000

Emmanuel Egede @emmanueletech.com · 09/09/2026

Before changing a working system, I want to know what I’m changing, what could be affected and how I’ll reverse it if something goes wrong. A rollback plan is part of the change, not an afterthought. #CloudOperations

000