{"id":28034,"date":"2025-09-12T17:53:43","date_gmt":"2025-09-12T15:53:43","guid":{"rendered":"https:\/\/blog.mi.hdm-stuttgart.de\/?p=28034"},"modified":"2025-09-12T17:53:45","modified_gmt":"2025-09-12T15:53:45","slug":"naniwa-not-actually-nutzlos-image-converter-with-aws","status":"publish","type":"post","link":"https:\/\/blog.mi.hdm-stuttgart.de\/index.php\/2025\/09\/12\/naniwa-not-actually-nutzlos-image-converter-with-aws\/","title":{"rendered":"NANIWA – Not Actually Nutzlos Image-converter With AWS"},"content":{"rendered":"\n

Introduction<\/strong><\/p>\n\n\n\n

This is written as part of the assignment for Software Development for Cloud Computing.<\/p>\n\n\n\n

NANIWA, which stands for Not Actually Nutzlos Image-converter With AWS, or the name of the region which would become the city of Osaka today, is an image-conversion service hosted solely on Amazon Web Services. It utilizes multiple features on the cloud-computing service platform to give access to anyone at anytime its functionality, but not its source code, and at a price that would be lower than hosting a server for it personally or at the company itself.<\/p>\n\n\n\n

The idea stemmed from my internship at Syntegon Technology K.K. (Saitama, Japan) where I was working at the R&D division of the Visual Inspection Department. For the high-speed cameras in the inspection machines, which could inspect up to 600 samples per minute, an image format i3<\/strong><\/em> was created in-house. However, due to time-constraints at the time (over 10 years ago), not much was developed when it comes to working with the i3 format outside of the inspection machines. Last year in 2024, I am still having to develop a shell extension that adds functionality to Windows Explorer for i3 formatted images, which included showing previews and creating icons of the images.<\/p>\n\n\n\n

The<\/strong> Problem and the proposed solution<\/strong><\/p>\n\n\n\n

One such problems of working with the i3 format, that was at the time yet unsolved, was with regard to the conversion of the i3 format images into more common image formats, such as jpg or png. As inspection images are vital when writing reports, whether it be Syntegon\u2019s own engineers or the customers, an accessible and easy-to-use i3 image converter would be very handy and would genuinely boost productivity. Especially when it renders the current troublesome way of converting the images obsolete, and if it does not cost a lot to provide such utility.<\/p>\n\n\n\n

As such, I have decided to use a tutorial from a LinkedIn post that I found to develop an image-conversion service hosted on AWS. As I do not have access to the i3 format libraries anymore, this proof-of-concept project would be converting from jpg to png instead. Link to said tutorial: https:\/\/www.linkedin.com\/pulse\/how-i-built-serverless-aws-document-converter-from-villanueva-mjmfe\/<\/a><\/p>\n\n\n\n

Architecture<\/strong>

Courtesy of the writer of the tutorial, Frank Kevin V., I am spared from creating an entirely new architecture diagram myself.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Project architecture diagram (source: LinkedIn post by Frank Kevin V.)<\/p>\n\n\n\n

The AWS services utilized are as follows:<\/p>\n\n\n\n