Jefferson Frank’s Post

Quite often the work that I do on a project goes a bit unnoticed by the non technical people around me and I mostly don't care about that. I don't have much of an ego and don't ask for a lot in the way of endorsements and the like. The flip side of this is that I have to demonstrate value whilst I'm searching for a new #contract as an Senior AWS Platform Engineer. I was reminded of a previous client who had a public facing website where the #sslcertificates were going to expire soon. Unfortunately, the #Terraform code had been written to couple the certificates for the staging and production environments together. (Don't ask why, I didn't). This was using #AWS Certificate Manager and renewal had been set to email rather than DNS. I rewrote this to decouple the dependencies between environments and certificates to auto renew and of course use DNS. There's some clear tech aspects to this but it's important to remember the impact on the company if this had gone wrong, production website being unavailable is the obvious one but how about the PR impact, that really doesn't look very professional. #outsideir35 #contracts #aws #platformengineering #opentowork #neverenoughcoffee

1Password appears to be down right now on their Login API. I'm dead in the water on several things if I can't get to my passwords. This is the definition of vendor lock-in. Guess I should look for something more abstracted right? Maybe even run my own? Wrong! All the time saved, energy applied elsewhere allowed me to ship more value by not having to focus on personal password management strategy. Same thing can be said for #Serverless and #AWS. Let them do the heavy lifting that doesn't add value to my delivery and I'll continue to focus on the things that matter. And if I do have bumps along the way, it'll be WAY FEWER bumps than if I'd decided to run it myself.

Is it only me that think AWS Technical Support should be much better than what they currently have? 90% of the time I go with support they don’t know the issue and they start searching as much as I did before opening the support case. In the end, either I fix while searching with them or they say we will search and reply to the case and doesn’t give a solution. I should be talking to a technical support engineer who know this area I am asking about and ready to answer me or knows at least where the problem may occur from. #aws #aws_support #inquiry

🌟 Attention all IT professionals and cloud computing enthusiasts! 🌟 Are you ready to take your career to the next level? 🚀 Look no further, because we have the ultimate guide for you on becoming an AWS System Administrator! 💻🔥 👉🏾 Check out this video to discover the power of AWS and the crucial role of an AWS System Administrator. 💪 You'll also learn about the essential skills and tools needed for this position, as well as the challenges and opportunities that come with it. 🎯 🗝️ And the best part? This video is tailored to meet the needs of both seasoned IT professionals and those interested in breaking into the cloud computing field. 🌤️ So, whether you're looking to upskill or start a new career, this guide has got you covered. 👀 Don't miss out on this valuable resource! Watch the video, like, and share it with your friends. 💬 And if you have any questions or want to share your own experiences on the topic, let us know in the comments. 🤝 🤩 Ready to embark on an exciting journey towards becoming an AWS System Administrator? 🚀 Then click the link below and let's get started! ⬇️ 🔗 https://lnkd.in/eGnZvZJw 🌐 Want more career tips and advice? Check out our playlists on interview questions and workplace improvement. 📚 And don't forget to connect with us on LinkedIn, Twitter, TikTok, and Instagram for more valuable content and job opportunities. 🌟 Let's grow together! 💼

Have you tried our Jobs by Email service? Receive alerts on the latest AWS jobs matching your search parameters – try it out and let me know what you think!

Have you tried our Jobs by Email service? Receive alerts on the latest AWS jobs matching your search parameters – try it out and let me know what you think!

Have you tried our Jobs by Email service? Receive alerts on the latest AWS jobs matching your search parameters – try it out and let me know what you think!

Have you tried our Jobs by Email service? Receive alerts on the latest AWS jobs matching your search parameters – try it out and let me know what you think!

Have you tried our Jobs by Email service? Receive alerts on the latest AWS jobs matching your search parameters – try it out and let me know what you think!

A Real-tech Lesson on the Importance of Diversifying Your Technology Stack & platform One of my clients had their entire infrastructure on AWS for almost 4 years. Everything was running smoothly until one day, disaster struck. The business team notified me that the sites and associated applications were down. When we investigated further, we found that every checkpoint notification on the AWS console had failed. Shockingly, the AWS account had been suspended without any prior notice—no emails, no warnings, nothing. We immediately opened a support ticket, but the first response came 24 hours later. The reason? Another AWS account had been opened with the same name (by someone else), and due to AWS policy, no further details could be shared. This situation was beyond frustrating: 1. Lack of Transparency: AWS provided no actionable information, leaving us in the dark. It felt like booking a flight and being denied boarding because someone else booked a ticket under your name—but due to policy, the airline refuses to tell you who did it. 2. Worst Support: Despite opening multiple support tickets, each was put on hold. The only advice we received was to identify and resolve the issue with the other account, with no further guidance due to policy restrictions. How could someone else open an account with same business name? Also, the steps to verify this from AWS Side is still unknown. Toppings to frustration: 1. No support over Email/Phone, the only option was using web support. 2. Although RM was already assigned, there was no option to connect with them. The AWS Support executive who was responding to the web tickets sent out a link to request call back from the RM, but less that he knew was that it was a sales call back form :| 3. Even the option to purchase priority support was disabled due to the account suspension. Imagine this: You log into the AWS console only to be greeted by a message that your account has been suspended. Following the advice to contact support, you find that general support offers no useful information. Frustrated, you try to upgrade to paid support, only to be blocked with a message that the page is inaccessible—because your account is suspended. Key Takeaways: No matter how robust and sophisticated your backup strategy is, it’s meaningless if everything is tied to a single vendor. This incident was a harsh reminder of the critical importance of decentralization and diversified backup policies, even for small to mid-sized organizations.