AWS amazonswf documentation change
Summary
Minor grammatical change from 'Since' to 'Because' in architecture explanation
Security assessment
Change is purely grammatical with no security implications. Describes existing security architecture without modifying security-related content.
Diff
diff --git a/amazonswf/latest/awsflowguide/awsflow-basics-scalable.md b/amazonswf/latest/awsflowguide/awsflow-basics-scalable.md index 8b7194c84..1d0b44735 100644 --- a//amazonswf/latest/awsflowguide/awsflow-basics-scalable.md +++ b//amazonswf/latest/awsflowguide/awsflow-basics-scalable.md @@ -16 +16 @@ Amazon SWF has two key features that make it easy to scale a workflow applicatio -Amazon SWF schedules tasks by posting them to dynamically allocated task lists, not by communicating directly with workflow and activity workers. Instead, the workers use HTTP requests to poll their respective lists for tasks. This approach loosely couples task scheduling to task execution and allows workers to run on any suitable system, including Amazon EC2 instances, corporate data centers, client computers, and so on. Since the HTTP requests originate with the workers, there is no need for externally visible ports, which enables workers to even run behind a firewall. +Amazon SWF schedules tasks by posting them to dynamically allocated task lists, not by communicating directly with workflow and activity workers. Instead, the workers use HTTP requests to poll their respective lists for tasks. This approach loosely couples task scheduling to task execution and allows workers to run on any suitable system, including Amazon EC2 instances, corporate data centers, client computers, and so on. Because the HTTP requests originate with the workers, there is no need for externally visible ports, which enables workers to even run behind a firewall.