Question

create a high-level diagram in Microsoft® Visio® of the resilient aspects of the system provided by AWS. The diagram should cover the system architecture in the AWS environment. Specific AWS (e.g., AWS Availability Zones, Elastic Load Balancing, Amazon CloudFront, etc.) that will provide reliability, availability, and continuity across the migrated environment need to be included. Also, ensure you include the following:

-Costs

-Specific

-AWS Connectivity across multiple availability zones

-At least one AWS that will support your design for fault tolerance (if one system were to fail)

Answer 1

Elastic Load Balancing distributes incoming application or network traffic across multiple targets, such as Amazon EC2 instances, containers, and IP addresses, in multiple Availability Zones. Elastic Load Balancing scales your load balancer as traffic to your application changes over time, and can scale to the vast majority of workloads automatically.

You can create, access, and manage your load balancers using any of the following interfaces:

• AWS Management Console— Provides a web interface that you can use to access Elastic Load Balancing.

• AWS Command Line Interface (AWS CLI) — Provides commands for a broad set of AWS services, including Elastic Load Balancing, and is supported on Windows, Mac, and Linux. For more information, see AWS Command Line Interface.

• AWS SDKs — Provides language-specific APIs and takes care of many of the connection details, such as calculating signatures, handling request retries, and error handling. For more information, see AWS SDKs.

• Query API— Provides low-level API actions that you call using HTTPS requests. Using the Query API is the most direct way to access Elastic Load Balancing, but it requires that your application handle low-level details such as generating the hash to sign the request, and error handling.