The last firewall pattern we will discuss will be an elaboration on the operational firewall pattern. If we look back at this pattern, we will see that we not only grouped the instances by function, but also by what outside operation or customer it was relevant to. This might work if we had client-specific web pages, but that is rarely the case when it comes to an application. It might also be noted that if we terminate SSL somewhere else, upstream it saves some computation time (arguably low). AWS-provided load balancers allow us to specify the certificate information thereby allowing us to terminate the SSL connection in an AWS service, potentially saving us some computation cycles and configuration headaches. Refer to the following diagram:

In this example, we have a single web instance that communicates over native HTTP (port 80) and allows connections from the load balancers (which have client, customer, or organization-specific Security Groups: sg-1 and...