Amazon AWS technical services

Cloud hosting and architecture

• Region selection, VPC, subnets, NAT, bastion.
• Site and app hosting: S3 + CloudFront, Amplify, Elastic Beanstalk, ECS/Fargate, EC2 — by job, not by habit.
• Databases: RDS (PostgreSQL/MySQL), Aurora, DynamoDB.
• Files and CDN, cache, HTTPS certificates.
• DNS on Route 53, mail records, redirects.
• Environments: dev / staging / prod.

Outcome: a diagram of how it works, a live production environment, and clear stages.

Product development and launch

• Landing pages, corporate sites, dashboards. HTML or Vue/React — whatever the client job needs.
• Serverless: Lambda, API Gateway, SQS queues, EventBridge.
• Integrations: payments, CRM, email, webhooks.
• CI/CD: GitHub Actions or CodePipeline, auto-deploy, preview environments.

Outcome: not “we set up a server,” but a live URL with a pipeline.

Migrations

• From shared hosting, a VPS, or another cloud onto AWS.
• From a monolith onto managed services with as little downtime as possible.
• Domains, certificates, mail, and redirects moved with a rollback plan.

Outcome: a migration checklist, a rollback plan, and an agreed change window.

Reliability and operations

• Backups and restore tests — not just a checkbox left on.
• CloudWatch monitoring, alerts to Slack, email, or SMS.
• Logs, tracing, optional status page.
• Autoscaling for peaks: campaigns, season, ad spikes.
• Incidents: a runbook and on-call coverage under a retainer.

Outcome: you learn about a problem before the customer does.

Security and access

• IAM: roles instead of shared keys, MFA, least privilege.
• Secrets in Secrets Manager or Parameter Store.
• WAF and Shield when needed, admin surface locked down.
• Audit of open ports, leftover users, public S3 buckets.

Outcome: a closed perimeter and a clear access model. ISO certification is a separate engagement, not part of the base offer.

Cloud finance

• AWS bill teardown: what is actually spending money.
• Budgets and alerts.
• Turn off unused resources. Reserved / Savings Plans only after the facts.
• Resource tags by project and environment.

Outcome: a more predictable bill, without a surprise at month-end.

AWS retainer

Monthly package: patches, spend review, backups, small changes, a report.