AWS Solutions Architectural diagram: High availability use case - Multi-vpc | multiple gateway endpoints | interface endpoint | AWS PrivateLink

 The following AWS architectural diagram serves as a use case for the following case scenario - high availability.



- High availability: Distribution of AWS resources across multiple VPC's help to minimise the impact of downtime and promotes high availability. Should the need arise, the interface and gateway endpoints may be configured to direct traffic to healthy resources in the event of a failure.

Gateway endpoints ensures network traffic stays within the AWS network as well as improving performance and security.

The following AWS resource provides information on how to monitor the health and performance of resources and what resources may be monitored:

Route 53 health checks help to monitor the health of resources and automatically failover traffic to healthy endpoints in the event resources are not available in a given AZ (Availability Zone).

Creating Amazon Route 53 health checks and configuring DNS failover - Amazon Route 53


High availability general use case: 

VPC components for a high availability network diagram are as follows:

- Subnets: They help to organise the VPC resources and instances in the VPC and enable traffic isolation between different network layers.

- Elastic Load Balancers: ELB's distribute incoming traffic to multiple instances in multiple Availability Zones to achieve high availability and fault tolerance.

- Route tables: Determine the routing path for network traffic within the VPC.

- Internet Gateways (IG): IG's provide a gateway for traffic between the VPC and the internet.

- Elastic IP addresses: Provides a static IP address which you may associate with an instance, due to the fact that if you choose to keep the dynamic public IP address given to the instance--this may change at any time and clients may not be able to reach the company URL.

- VPC endpoints: Allow for secure communication between resources in the VPC and with AWS services without using public IP's.  The significance of this is that, this may greatly reduce data transfer costs.

Tip:

- Use Auto-Scaling Groups (ASG's) to automatically scale resources up or down based on demand, which helps to effectively manage cost of the resources as well as ensuring that the network is able to handle sudden spikes in traffic without interruption. 






- 

Comments

Post a Comment

Popular posts from this blog

Developer's Arsenal: How HashiCorp unites cloud securite and upholds the AWS Well-Architected Framework when implementing Policy as Code using Sentinel One.

Image
This summary highlights the compelling impact of Sentinel One on Infrastructure as Code (IaC) by: automating policies ensuring seamless adherence to infrastructure requirements (aka AWS Well-Architected Framework) significantly slashing response times for developers throughout the code submission process This blog post references the following video on Sentinel One by HashiCorp.: Video: Introduction to Sentinel, Policy as Code Framework (hashicorp.com) Armon Dadgar's discussion on policy as code, with a focus on HashiCorp's Sentinel, offers valuable insights for cloud architects, especially in the context of adhering to industry best practices like the AWS Well-Architected Framework. Sentinel is designed to be a high-level language for non-programming experts to author the policies. Dadgar begins by emphasising the benefits of infrastructure as code, aligning the principles advocated by the AWS Well-Architected Framework. By integrating the Terraform Enterprise, Sentinel One en
Read more

C++ code base - Cloud provider services menu using if/else, switch/case. 2023.

Image
 Note: I would appreciate your support of this blog by going to the link below to "Buy me a pizza" so that I may continue to provide educational scripts, resources and general tech stuff. 🍕 Thank you. https://www.buymeacoffee.com/infosec_coder ----------------------------------------------------------------------------------------- This program was created using Visual Studio for the IDE. Screenshot I Screenshot II Screenshot III CODE BASE  NOTE:   (Desktop users): To view the sections below clearly > right click > Open image in new tab. > Should give a crosshair "+" symbol > Click on that and it will zoom in on the image. OR Left click on the image. > Will open image on page. > use CTRL + scroll up or down (on mouse) to zoom in. I. II. III. IV.  V.   VI. VII. VIII. IX. X.  
Read more

AWS - Amazon Customer Outreach Ecommerce diagram with notes

Image
  Note: I would appreciate your support of this blog by going to the link below to "Buy me a pizza" so that I may continue to provide educational scripts, resources and general tech stuff. 🍕 Thank you. https://www.buymeacoffee.com/infosec_coder =====================================================  The following is a replica of the diagram from the link below with additional notes for certain steps to understand the diagram. Amazon Personalize customer outreach on your ecommerce platform | AWS Architecture Blog The screenshot below will not zoom in clearly, therefore I went ahead and took screenshots of each section. Screenshot I Screenshot II Screenshot III Screenshot IV Screenshot V Screenshot VI For the screenshot below, you may try right clicking on the image > Open image in new tab > and then CTRL + scroll up on mouse to zoom in if needed. Screenshot VII Screenshot VIII
Read more