AWS architecture and consulting
I've been designing AWS environments for more than eight years, for companies of every size, from startups to large enterprises, including banks and insurers. I've built architectures that need to scale and can't go down. More and more of my work is now generative AI: from first experiments to use cases running in production.
How I can help
These are the areas I work in. Most projects touch two or three of them.
Architecture design
You have a new system or module that needs to run on AWS.
- An architecture diagram with a description of each service
- Two or three options, with the reasoning behind each decision
- Reliability, high availability and security built in
- Infrastructure as code from day one
Architecture review
Your environment works, but nobody is sure it works well.
- A review against the AWS Well-Architected Framework, all six pillars
- A prioritised list of risks, separating real threats from theoretical ones
- Recommendations split into quick fixes and changes that need planning
Cost optimisation
Your AWS bill is growing faster than your business.
- What you pay for and whether you need it: Cost Explorer, Cost and Usage Reports, tagging
- Right-sizing, Savings Plans, S3 storage classes, data transfer
- Architecture decisions that cost more than they should
- A savings plan with estimated amounts and an order of work
AI agents
You want AI in your product, not another demo.
- Where an agent makes sense and where a simple model call is enough
- Amazon Bedrock and AgentCore, RAG with Knowledge Bases, tools over MCP
- Agent permissions, Guardrails and tracing of every step
- Token costs and a fallback for when the model gets it wrong
Security and governance
Get your accounts in order before they turn into a mess.
- AWS Organizations, IAM Identity Center, CloudTrail, SCPs
- Separate accounts for dev, test and prod
- AWS Budgets, cost alerts and anomaly detection
- CloudArmor, a starter package for companies setting up AWS from scratch
Migration to AWS
Moving from your own servers or another cloud provider.
- An inventory and a migration strategy (the 7 Rs) for each workload
- Order, dependencies, risks and a rollback plan
- Hands-on support during the migration, not just a plan on paper
How we'll work together
Four steps. The first one is free.
- 01
A first call
We meet online. You tell me what you have and what you need, and I tell you whether I can help and how. This call is free.
- 02
Scope and quote
You get a short summary: what we'll do, what you'll get, how long it takes and what it costs. It could be a day, a week or ongoing part-time work.
- 03
The work
Workshops with your team, read-only access to your environment, a review of your infrastructure code. I ask a lot of questions, because I'd rather understand your business than guess.
- 04
Recommendations and rollout
We go through the report or design together in a meeting, not just as a PDF in your inbox, because the best questions come up at the whiteboard. If you like, I stay on during implementation to make sure the team is on track.
Who it's for
- Companies that have been on AWS for years, where nobody remembers why things are set up the way they are
- Teams building a new product who don't want to rebuild it a year from now
- CTOs and tech leads who want a second opinion before a big decision
- Startups that want to launch on a proper multi-account setup, not a single root account
- Companies that want AI in their product but don't know where to start or what it will cost
Common questions
How do we work together?
On a B2B basis: a one-off engagement, a project with a fixed scope, or ongoing part-time support. Full-time is possible too, but I rarely have the capacity.
Do you need access to our AWS environment?
For a review, read-only access is enough, ideally through a dedicated IAM role we set up together. I never make changes in production.
Do you work with anything other than AWS?
AWS is my focus, and I'll tell you straight when something isn't my area. If your project needs it, I'll recommend someone who knows it well.
Will you sign an NDA?
Yes, that's standard. Send me yours or we can use mine.
Can you train our team as well?
Yes. I run my own AWS training courses, and official AWS courses through AWS training partners. An architecture review often ends with a workshop for the team. It's the fastest way to make sure the recommendations actually get used.
Last updated: 19 September 2026
What can I help you with?
Tell me what you need. I'll take a look and come back with how I'd approach it.
hello@lukado.euWant to build your team's skills first? Have a look at my AWS training courses, from the basics to building GenAI apps.