The AWS services I design, run and troubleshoot for Adobe Commerce, Magento and WordPress, each linked to the case studies and articles where they did the real work.
Amazon CloudWatchCloudWatch metrics and alarms for memory, evictions, connections and the other signals that show trouble early.1 write-up
Amazon EC2Running Adobe Commerce, Magento and WordPress on Amazon EC2: right-sized instances behind a load balancer, current instance generations and stateless application servers.5 write-ups
Amazon EFSShared storage on Amazon EFS so every application instance sees the same media files.1 write-up
Amazon ElastiCacheElastiCache for Redis as Magento cache and session storage, kept separate so cache evictions never log customers out.1 write-up
Amazon RDSManaged MySQL on Amazon RDS for commerce and WordPress: sizing for peak connections, Performance Insights, supported engine versions and tested restores.4 write-ups
Amazon S3Amazon S3 for media and customer uploads, keeping web servers stateless and easy to scale.2 write-ups
AWS CodeDeployRepeatable deployments with AWS CodeDeploy and Bitbucket Pipelines, including recovery from failed rollouts.1 write-up
AWS IAMAccess through IAM roles instead of shared credentials, including cross-account role switching for client AWS accounts.1 write-up
AWS WAFAWS WAF rules to filter bots and attacks before they reach Magento, including virtual patching during zero-days.1 write-up
EC2 Auto ScalingAuto Scaling groups that add capacity before a campaign rather than during it, with clean-up after failed deployments.2 write-ups
Elastic Load BalancingLoad balancers with health checks and connection draining, so releases and instance failures don't interrupt customers.2 write-ups
Also see the platforms and integrations I work with, or talk to me about your AWS setup.