You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a python project about Route 53 Failover Record with Health Check that resolve#789 (#1053)
* route53 failover record
* Reorganized stack structure
* Adding alias record based health check for failover record
* Changed container image of sample workload from personal sample app to managed sample app
* Changed personal information to example information
* Updated README file
* Added instruction to use pre-made Route 53 HostedZone
* Fixed the code to be deployed without previous resources.
Extracted hosted zone and pass it as parameter to health check stacks
example.com is reserved.
Changes domain name to different name
* Updated architecture diagram
Move the email icon to outside of the region
Added CloudWatch metrics that make alarm
---------
Co-authored-by: Kihoon Kown <[email protected]>
Co-authored-by: Junseong Jang <[email protected]>
Co-authored-by: Michael Kaiser <[email protected]>
This sample project demonstrates how to create a Failover DNS record in Route 53 using a CDK application. It leverages the Route 53 Health Check feature to monitor the status of endpoints and automatically fail over to a backup endpoint in case of failure. Additionally, it configures SNS notifications to alert administrators when a failover event occurs, ensuring prompt awareness and response.
4
+
5
+
## Architecture
6
+
7
+
The architecture of this solution is illustrated in the following diagram:
8
+
9
+

10
+
11
+
The key components of the architecture are:
12
+
13
+
1.**Primary Endpoint**: The main endpoint that serves traffic under normal circumstances.
14
+
2.**Secondary Endpoint**: The backup endpoint that takes over traffic when the primary endpoint fails.
15
+
3.**Route 53 Hosted Zone**: The DNS hosted zone where the Failover DNS record is created.
16
+
4.**Route 53 Health Checks**: Health checks that monitor the availability of the primary and secondary endpoints.
17
+
5.**Route 53 Failover DNS Record**: The DNS record that routes traffic to the primary endpoint by default, but automatically switches to the secondary endpoint when the primary endpoint fails the health check.
18
+
6.**SNS Topic**: The Simple Notification Service (SNS) topic that publishes notifications when a failover event occurs.
19
+
7.**SNS Subscription**: The subscription to the SNS topic, which can be configured to deliver notifications via email or other channels.
20
+
21
+
## Getting Started
22
+
23
+
To get started with this project, follow these steps:
24
+
25
+
1. Clone the repository.
26
+
2. Install the required dependencies using `npm install`.
27
+
3. Configure the necessary AWS credentials and environment variables.
28
+
4. Select a Route 53 HostedZone that can be used for this project.
29
+
5.**Provide the required context values in the `cdk.json` file, including `domain` refering the HostedZone, `email` to get notifications, `primaryRegion`, and `secondaryRegion` to deploy the sample application.**
30
+
6. Deploy the CDK application using `cdk deploy`.
31
+
32
+
Refer to the project's documentation for more detailed instructions and configuration options.
0 commit comments