AWS decision-guides documentation change
Summary
Replaced 'AWS Elastic Load Balancing' with 'AWS ELB' and 'Elastic Load Balancing' with 'ELB' for terminology consistency
Security assessment
The change only abbreviates service names without altering security context. The existing security reference to AWS PrivateLink remains unchanged.
Diff
diff --git a/decision-guides/latest/fargate-or-lambda/fargate-or-lambda.md b/decision-guides/latest/fargate-or-lambda/fargate-or-lambda.md index fe1ea95fe..abf373746 100644 --- a//decision-guides/latest/fargate-or-lambda/fargate-or-lambda.md +++ b//decision-guides/latest/fargate-or-lambda/fargate-or-lambda.md @@ -169 +169 @@ When you deploy tasks in **Fargate** , they run in an Amazon VPC (Amazon Virtual -Fargate supports advanced networking features such as load balancing (using AWS Elastic Load Balancing), VPC peering, and direct access to other AWS services within the VPC. You can also use AWS PrivateLink for secure, private connectivity to supported AWS services, without traversing the internet. +Fargate supports advanced networking features such as load balancing (using AWS ELB), VPC peering, and direct access to other AWS services within the VPC. You can also use AWS PrivateLink for secure, private connectivity to supported AWS services, without traversing the internet. @@ -182 +182 @@ Pricing model -**Fargate** pricing is based on the resources allocated to your containers, specifically the vCPU and memory you select for each task. You are billed per second, with a one-minute minimum charge, for the CPU and memory that your containers use. The costs are directly tied to the resources your application consumes, meaning you pay for what you provision, regardless of whether the application is actively processing requests. Fargate is well-suited for predictable workloads where you need specific resource configurations and can optimize costs by adjusting the allocated resources. Additionally, there might be additional charges for related services, such as data transfer, storage, and networking (for example, VPC, Elastic Load Balancing). +**Fargate** pricing is based on the resources allocated to your containers, specifically the vCPU and memory you select for each task. You are billed per second, with a one-minute minimum charge, for the CPU and memory that your containers use. The costs are directly tied to the resources your application consumes, meaning you pay for what you provision, regardless of whether the application is actively processing requests. Fargate is well-suited for predictable workloads where you need specific resource configurations and can optimize costs by adjusting the allocated resources. Additionally, there might be additional charges for related services, such as data transfer, storage, and networking (for example, VPC, ELB).