Martin S. looks like a good fit?
We can organize an interview with Aldin or any of our 25,000 available candidates within 48 hours. How would you like to proceed?
Schedule Interview NowMartin S. Cloud, DevOps and General Development
My name is Martin S. and I have over 2 years of experience in the tech industry. I specialize in the following technologies: Amazon Web Services, Docker, Jenkins, CI/CD, Ansible, etc.. I hold a degree in Bachelor of Science (BS). Some of the notable projects I’ve worked on include: Hosted Zone Association Maintenance Lambda, EC2 Security Posture Reporter, OIDC Gitlab Runners, Central Internet Access, AWS Lambda Packager, etc.. I am based in Newcastle upon Tyne, United Kingdom. I've successfully completed 7 projects while developing at Softaims.
I approach every technical challenge with a mindset geared toward engineering excellence and robust solution architecture. I thrive on translating complex business requirements into elegant, efficient, and maintainable outputs. My expertise lies in diagnosing and optimizing system performance, ensuring that the deliverables are fast, reliable, and future-proof.
The core of my work involves adopting best practices and a disciplined methodology, focusing on meticulous planning and thorough verification. I believe that sustainable solution development requires discipline and a deep commitment to quality from inception to deployment. At Softaims, I leverage these skills daily to build resilient systems that stand the test of time.
I am dedicated to making a tangible difference in client success. I prioritize clear communication and transparency throughout the development lifecycle to ensure every deliverable exceeds expectations.
Main technologies
Cloud, DevOps and General Development
2 years
Amazon Web Services
1 Year
Docker
1 Year
Jenkins
1 Year
Additional skills
Direct hire
Potentially possible
Previous Company
Micro Focus
Experience Highlights
Hosted Zone Association Maintenance Lambda
The client had established that having automated the process of attaching VPCs to a central Transit Gateway service and associating the VPCs with numerous R53 Hosted Zones, VPCs that went on to be deleted were not disassociated from the Hosted Zones. This led to artificially high association numbers and prematurely reaching AWS limits. A Python-based maintenance process was created using AWS Config and CloudWatch Logs from the automated TGW attachment process to establish which VPC IDs were redundant and disassociate them to reduce the risk of hitting AWS limits.
EC2 Security Posture Reporter
The client had established that tracking the security posture of EC2 instances had become complex The various security tools and configurations in place led to multiple reporting interfaces being needed to confirm any instance's current status, and non-compliant instances often easily went unnoticed. The project implemented a collection of Lambda functions in a fan-out architecture that uses AWS APIs to retrieve a list of EC2 instances across multiple AWS accounts. and AWS SSM to remotely execute commands in those instances to establish their security status.
OIDC Gitlab Runners
The client had established that disparate engineering teams used various mechanisms to authenticate their Gitlab CICD Runners with AWS during their pipeline deployment processes The project aimed to standardise the approach across all teams by providing a mechanism to easily enable OIDC authentication between Gitlab and AWS, allowing the teams to easily grant specific permissions to particular AWS accounts on a per Gitlab repo basis via YAML config files.
Central Internet Access
The client had established that disparate departments were procuring internet access for their public cloud environments in various ways, with differing levels of logging, monitoring and security The project aimed to centralise all internet connectivity for all departments, enabling a standardised approach to logging, monitoring and security for all internet connectivity.
AWS Lambda Packager
The client had established that a number of developers who were unfamiliar with AWS Lambda were experiencing problems producing Lambda Functions that relied on external software dependencies Hardware and software limitations, along with inexperience with AWS Lambda itself, were creating longer-than-expected development cycles.
Education
Newcastle University, Newcastle upon Tyne
Bachelor of Science (BS) in Information Systems
2003-01-01-2006-01-01
Languages
- English
Github