ENATIV Logo
ENATIV
Back
© 2026 ENATIV
ProjectsServicesKnowledge hubContact
contact@enativ.pl
  1. Knowledge hub
  2. ›
  3. Cloud & DevOps
  4. ›
  5. AWS

AWS

S3, Lambda, AppSync, Cognito, CDK and SST: AWS as managed services instead of a server of my own.

Cloud & DevOpsUsing since 2020 · Featured project: Hollywood Budgets / TPH Global (in the Code & Pepper team)

Category
Cloud & DevOps
Using since
2020
Featured project
Hollywood Budgets / TPH Globalin the Code & Pepper team

In practice

I pick AWS when an app should use ready-made services instead of a server of its own: files in S3, functions in Lambda, sign-in in Cognito. The backend of Little Birdie runs on AWS, and SST describes the infrastructure of TPH Global. When one server is enough, I skip the cloud.

What is AWS?

AWS is the cloud of Amazon: managed services you rent instead of running servers of your own. Amazon S3 is object storage, with files in buckets. AWS Lambda runs code without you managing servers. Amazon Cognito keeps a directory of users and handles their sign-in, and AWS AppSync exposes a GraphQL API.

Infrastructure can be described in code. AWS CDK is an open-source framework where you define resources in TypeScript and CloudFormation deploys them. SST describes the whole app, buckets and queues included, in one sst.config.ts file. Terraform does not belong to one cloud.

How I work with AWS

I start from what the app has to do and who will run it, not from a list of services. I add a service only when it replaces something I would rather not write or operate myself.

  1. Services matched to the job

    Files go to S3, logic that reacts to events goes to Lambda, users go to Cognito. When a mobile app should ask for data through one endpoint, I consider AppSync, as in Little Birdie.

  2. Infrastructure in the repository

    I do not click resources together in the console. I describe them in code, so a change goes through review. On Little Birdie that is AWS CDK, on TPH Global it is SST.

  3. Permissions and the account

    Every function and user gets only the access it needs, and the AWS account is created by the project owner, not by me.

When it fits, and when it doesn't

AWS makes sense when a project should use ready-made services, not just a machine to run the app on.

A good fit when

  • A mobile app with a backend and no servers of its own: API, functions and sign-in as services.
  • User files that should live outside the app server, in S3 for example.
  • A client project that already has an AWS account and people who know it.

Not a fit when

  • A simple company site that is fine on ordinary hosting.
  • A single app with a database on a VPS of your own, where Docker is enough.
  • A project where nobody will watch permissions and the bill.

When a project already runs on Google Cloud, I do not move it to AWS just because I know AWS better.

AWS or Google Cloud?

Both clouds offer a similar set of services, so I compare them only where I have met them in projects. I leave prices out.

AWS and Google Cloud compared
CriterionAWSGoogle Cloud
FilesAmazon S3: objects in bucketsCloud Storage: objects in buckets
Code without serversLambda: event and API functionsCloud Run: HTTP and event functions
User sign-inCognito: directory and OAuth 2.0 tokensIdentity Platform: sign-in services and SDKs
Infrastructure as codeAWS CDK, deployed through CloudFormationInfrastructure Manager, Terraform configurations
Terraform supportAWS provider in the Terraform registryGoogle provider in the Terraform registry

Choose AWS when

the project already runs on it or should use several services together, such as S3 and Lambda. You pay with time spent on permissions and the bill.

Choose Google Cloud when

the team or the client already uses it and the app should stay close to its services. Moving costs more than the difference between the clouds.

AWS is in the stack of Little Birdie and TPH Global, and GCP in Gaia Lens and CAS Marketplace.

Frequently asked questions

It does not have to. The backend can be made of managed services: AppSync exposes the API and Lambda runs the logic. That is how Little Birdie works. The price is vendor lock-in, so before the start I settle what stays portable, such as the data schema.
The project owner, under the company name. I get permissions to do the work, while the account and the data stay with you. A change of contractor then does not mean moving infrastructure, and you can see what runs and what you pay for.
A change lands in the repository as an ordinary commit, and a tool such as AWS CDK deploys it through CloudFormation. You can tell who changed a resource and when, and a test environment can be rebuilt from the same code. A manual change in the console is hard to read later, so I avoid it.

On this page

  • In practice
  • What is AWS?
  • How I work with AWS
  • When it fits, and when it doesn't
  • AWS or Google Cloud?
  • Frequently asked questions

Related topics

  • AWS
  • Terraform
  • Docker
  • PostgreSQL
  • Next.js

Related services

  • Web ApplicationsModern, fast and scalable web applications using React and Next.js.

Not sure this is an AWS project?

Write what data and users the app has and who will look after it after launch. I will answer which services make sense here.

Describe your projectSee Hollywood Budgets / TPH Global