Skip to main content

AWS Amplify as low-code for infrastructure

[PLACEHOLDER]

Low-code development platforms are dominating many conversations lately. Many believe that low-code development platforms will account for millions of USD in revenue in the next five (5) years. An article by Forbes highlights that “it will account for more than 65% of application development activity by 2024”. Some believe it will be the answer to all their development needs.


 But low-code is not a new concept. The difference now is that its audience has amplified. For developers (or even advanced users) who have been in the Microsoft  ecosystem for a while have already experienced the assembly of software solutions with little effort using tools such as Microsoft Excel, Access, Visual Studio (assembling forms) and others.

Putting Microsoft aside, and prior to this “low-code revolution” which has reached high altitude in the last couple of years, there have been many online veterans which allow a user to assemble simple to medium complexity applications in different areas:

  • Marketing automation with low to no code
  • Websites
  • Database management
  • AI
  • Work management
  • e-commerce
  • Others
- Microsoft, Mendix, Salesforce, Wix -
-   Zoho, outsystems, Stripe, Shopify  -

 

Before we go any further with this article let us answer the question of what is a low-code/no-code platform? 

Low-code/no-code is a platform that provides non-technical, and technical users the tools to develop applications that are operational (at least at a “vanilla state”), or require additional coding for specific elements, with less effort (and knowledge) that is needed for the traditional way of producing code. The LCDP (Low Code Development Platforms) creates applications using a graphical interface, which the consumer uses for assembling the desired functionalities.

The focus of this article

In this article I will focus on one of my own experiences under the low-code umbrella where I leveraged cloud computing services. I chose Amazon AWS services in the space of “code as infrastructure”. The three (3) items I would like to highlight before we start:

  1. This falls into the low-code end that requires expertise
  2. We are focusing on “code as infrastructure”, with fewer lines of code possible. This is to accelerate and facilitate the DevOps for some app use cases
  3. If you are looking for the no code/low code solutioning, similar to Microsoft PowerApps from Amazon AWS then I suggest to look at Amazon HoneyCode

The problem statement in our hands was to build a webapp (mobile first) as a gift to our colleagues. The pandemic has brought many challenges around the globe and we wanted to let our team members abroad know that we were here for them. Without going into details, the solution was inspired by the #virtualhug movement. As we continued working on our concept, we landed on the following paragraph that defined the app: “A virtual hug a day, keeps the sorrow away! Just the act of imagining that you are hugging someone can make you feel positive, empathetic and less stressed.” 

The premise was to deliver this webapp in seven (7) days, easy to deploy, but without spending too much time on setting the deployment architecture. There was no Content Management System (CMS) system in place, but it should be quick and easy to make content updates. Those updates should reflect on production relatively quickly for our audience to view on the webapp.

We had a core team of three (3) people for this delivery: 

  1. A project manager (PM) for coordination
  2. A designer, to help me in bringing the concept into the webapp Minimum Viable Product (MVP)
  3. Me as the sponsor and developer

As I said before, I needed to reduce efforts on the development and the deployment. Therefore I turned to Amazon AWS for a "serverless" approach, and with the hope to find my answers for an easy deployment process.

The stack that we ended up using was:

  • NuxtJS
  • AWS S3
  • AWS Amplify
  • AWS CloudFormation
  • Microsoft Visual Code as the editor

The hero of this article is AWS Amplify, which took care of many lines of code, which without a tool like this, I would have had to write in order to set up “code as infrastructure” and host the webapp.

Note: This is not a blog for teaching AWS Amplify and Cloudformation. If you are looking for that then I would recommend the ThemePark course provided by Amazon AWS: https://www.eventbox.dev/published/lesson/innovator-island/0-introduction/1-overview.html 

Checkpoint...

If you have reached this point of the article then you might be thinking “this looks advanced, where is the low-code in this stack!?”. I want to remind you that this article is focusing on the DevOps aspect. I hope things are a bit clearer as you read the next few paragraphs.

What is AWS Amplify?

Based on Amazon AWS definition: “AWS Amplify is a set of tools and services that can be used together or on their own, to help front-end web and mobile developers build scalable full stack applications, powered by AWS. With Amplify, you can configure app backends and connect your apps in minutes, deploy static web apps in a few clicks, and easily manage app content outside the AWS console. Amplify supports popular web frameworks including JavaScript, React, Angular, Vue, Next.js, and mobile platforms including Android, iOS, React Native, Ionic, Flutter.”

How did we leverage AWS Amplify for the deployment, in a low-code approach?

I followed the vanilla commands after creating the required AWS Role using the AWS Management Console, and installing the AWS Amplify-CLI on my laptop, where my project resided. With it I was able to have within minutes:

  1. Continuous Integration/Continuous Deployment (CI/CD) pipeline
  2. CI/CD connected to my code repository, which is on Bitbucket (outside of AWS)
  3. Hosting the app in an UAT environment leveraging the AWS S3 bucket
  4. The CloudFormation which is used for the “code as infrastructure” for the provisioning

The provisioning, and the many scripts, and the integrations, were all made with just a few command line prompts removing hours of me putting together this code pipeline.




 Finally, it was great to see that we exceeded our expectations as we were able to successfully deploy the webapp to production two (2) days earlier, shrinking our timeline from seven (7) to five (5) days.


Trending posts

Rethinking Canadian Economic Sovereignty Amid Foreign Acquisitions

About a year ago, I attended the Elevate Festival in Toronto, which I recommend if you haven't had the chance to experience it. The event was very inspiring because of its focus on business, technology, and entrepreneurship. It was interesting to see people at various stages of their careers; some executives, others developing their startups, a few in between, and some simply there to gain insights and knowledge. There was a unique atmosphere, influenced by the current political situation between Canada and the US. Many discussions centred around data sovereignty, cloud infrastructure independence, and ensuring that Canadians' data remained safe and secure within the country's borders or trusted allies. Building trust requires considerable effort, yet it can be shattered very quickly… and once broken, repairing it becomes extremely difficult, if not impossible. Considering the current geopolitical landscape, it is unclear where we go from here... but it seems the rules hav...

Reimagining Digital Experience Management: How Agentic AI is Transforming Adobe Experience Manager

 Adobe Experience Manager (AEM) has introduced powerful new Agentic AI capabilities designed to continuously improve and adapt digital experiences at the speed of AI. By integrating advanced AI orchestrators through Agent-to-Agent (A2A) and Model Control Protocol (MCP) tools, AEM enables brands to automate complex workflows and enforce compliance seamlessly across enterprise ecosystems. Through a suite of specialized agents, teams can transition from manual, weeks-long processes into fast, AI-assisted workflows powered by simple natural language prompts. Photo by Tunahan KALAYCI via Pexels   Here is a breakdown of the key agents driving AEM’s new Agentic capabilities, their value propositions, their guardrails, and their current availability status. 1. Brand Experience Agent. Overview. The Brand Experience Agent accelerates digital modernization through specialized sub-agents—the Experience Modernization Agent, Experience Production Agent, and Experience Development Agent. Tog...

Steer for a talent transformation strategy (and avoiding AI fatigue)

 There was a debate on whether to feature the term “AI” in the title of this article. Honestly, a key motivation for pursuing the research that led to this post was sparked by the widespread excitement about AI appearing constantly in our LinkedIn feed, to the point of feeling the fatigue, and even a bit disappointed in the algorithm of this, and the others, social media and content curated apps.  We soon discovered that there is an entire concept called "AI fatigue", not exactly how we were feeling it, but more about the mixed emotions people in the workforce have regarding the use of AI tools. Photo by Mart Production via Pexels (background updated with AI and Adobe  tech) From micro blog posts to video podcasts, lately, most of the tech content we encounter revolves around AI. They often sound or read very similar, usually mentioning the same few top providers. The articles (and social posts... at least the popular ones with paid-campaigns behind it) tend to focus less...

AI Beyond the Hype: Responsible Adoption for Lasting Impact

 These days, simply mentioning “AI” isn’t going to win anyone over. Clients expect authentic, data-driven results—not just bold claims or industry jargon. The expanding reach of AI brings some real concerns with it, such as errors, bias, and privacy risks are all in the mix. If those issues aren’t addressed, trust can erode quickly. It also affects an organisation’s dynamics, operations, and culture—regardless of size—including shifts in client relationships as expectations evolve. What can set a tech-consulting firm apart, among other things, is the dedication to building AI solutions on foundational values like fairness, transparency, accountability, privacy, security, and reliability. In other words, Responsible AI can be hard work, and it is a genuine differentiator. If an organisation can ensure the solutions implemented are ethical, clear, and consistently trustworthy, then it is likely it will foster customer confidence and loyalty. Photo by Google DeepMind from Pexels ...

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed