AWS
AWS development for applications that need a UAE or regional home
We design and run applications on AWS when it is the right platform for the workload or the one your company already standardised on. Region choice, identity, and a pipeline come before a diagram full of services you do not need.
- Application platforms
- Delivery pipelines
- Migration
- Cost and access hygiene
What we actually use
Compute and databases sized to the product, object storage for files, a queue when work is asynchronous, and identity that is not a shared root key. The UAE region is available when latency or a residency decision calls for it. Using it is a design choice we record, not a badge.
Migration
A move onto AWS includes what is not worth moving. We cut over with a rollback and a check that backups restore. Lifting every unused server is not a migration strategy.
AWS for the account you will own
We put on AWS
- The app account in your name
- The few services the release needs
- Logs, backups, and a rollback
Not a landing-zone programme
- Every AWS product
- A multi-account estate for one service
- A design your team cannot explain
What changes an AWS setup
The region
Where the data may live is a requirement, not a default we pick in silence.
The bill
A service you will not watch should not be in the first diagram.
The access
Humans use roles. Keys do not live in the repository.
Before an AWS account is used
- 01
Ownership
The company account and a named admin.
- 02
Region
Where the data may live.
- 03
The few services
Only what this release will actually run.
- 04
Rollback
How a bad release comes back.
Marks an AWS account can be run
- 01
The company’s account
The estate sits in an account the company owns.
- 02
A service has an owner
Each running piece has a person who will notice if it stops.
- 03
Cost is visible
A week of spend can be read before the architecture grows.
- 04
Rollback was tried
Returning to the previous release is a step that has been run.
What we build
Application platforms
The runtime, data, and network boundary for one product, in an account you own.
Delivery pipelines
Build and deploy with separate environments and a practised rollback.
Migration
A sequenced move with a weekend plan that assumes something will fail.
Cost and access hygiene
Budgets, least privilege, and the removal of idle experiments.
Questions we hear
Do you use the AWS UAE region?
When the product needs it. Some workloads are fine in another region the business has already approved. We do not treat region as legal advice.
Can you work in our organisation?
Yes, with roles we do not keep after the engagement. The account stays yours.
Will you propose every AWS service?
No. A short list you can operate beats a reference architecture poster.