Compute & Serverless

Dedicated Instances run in a VPC on hardware dedicated to a single customer, ensuring isolation at the host hardware level. Dedicated Hosts also provide physical isolation but add socket/core-level visibility and licensing control (BYOL), which is not required in this scenario.

AWS Fargate allows you to run containers without managing the underlying EC2 instances, providing a serverless compute engine for containers.

Amazon EKS is a fully managed Kubernetes service that allows you to run Kubernetes workloads on AWS without needing to manage the Kubernetes control plane.

AWS Elastic Beanstalk allows you to deploy applications like Python web apps while retaining full control over the underlying AWS resources. It provides automated management, making it suitable for this scenario.

AWS Lambda (Option B) is a serverless compute service that runs code without requiring the provisioning or management of servers. AWS Step Functions (Option C) is a serverless orchestration service that lets you coordinate multiple AWS services (including Lambda functions) into visual workflows with built-in error handling, retries, and conditional logic. EC2 and Elastic Beanstalk involve server provisioning, and Batch is designed for batch computing workloads.

Dedicated Hosts (Option B) are physical servers with EC2 instance capacity fully dedicated to a single customer, providing visibility into physical sockets and cores. This hardware-level visibility is strictly required to utilize Bring Your Own License (BYOL) (Option C) for software licenses bound to specific physical hardware configurations (like Windows Server or SQL Server). Dedicated Instances (Option A) run on single-tenant hardware but do not provide the socket/core visibility required for BYOL.

Amazon Lightsail offers a simple VPS solution with predictable flat-rate monthly pricing, making it ideal for hosting a WordPress site with minimal configuration.

Amazon EC2 Auto Scaling automatically adjusts the number of EC2 instances based on demand, ensuring that the application can handle traffic spikes without manual intervention. AWS Direct Connect and Amazon Route 53 do not provide automatic scaling capabilities, and Network Load Balancer is used for distributing traffic, not scaling instances.