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

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
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
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
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
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
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
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
Users say an application is extremely slow.
EC2 CPU is only 25 percent.
Would you resize the instance?
I wouldn’t yet. CPU is only one part of the story.
What would you check next?
#AWS #EmmanueleTech
Changing five things at once might fix a problem, but you may never know what actually fixed it.
I prefer to narrow the issue down, test one reasonable change and observe the result.
#Troubleshooting #EmmanueleTech
Bluesky Morning
A slow application doesn’t automatically need a bigger server.
I’d check CPU, memory, disk, network and the application itself before changing capacity.
Troubleshoot from evidence, not assumptions.
#CloudOperations #EmmanueleTech
A simple IT question:
Who actually has access to what right now?
If that answer is unclear, the access probably needs reviewing.
#AccessManagement #EmmanueleTech
Access should not be permanent by default.
People change roles, projects end and old permissions remain.
Good access management includes knowing when to remove access, not just when to grant it.
#CloudSecurity #EmmanueleTech
Some infrastructure problems come from things nobody reviewed for months.
Old accounts. Expired certificates. Forgotten rules. Outdated systems.
Regular reviews catch small issues before they become bigger ones.
#CloudOperations #EmmanueleTech
Building infrastructure is only the beginning.
Servers need updates, permissions need reviews, certificates expire and configurations change.
A system can be online and still need attention.
#CloudInfrastructure #EmmanueleTech
Infrastructure documentation matters more when something goes wrong.
Months after a deployment, I still want to know why a configuration exists and what depends on it.
Infrastructure shouldn’t depend on memory.
#CloudInfrastructure #EmmanueleTech