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
Copy file name to clipboardExpand all lines: components/docs-chef-io/content/automate/create_amazon_rds.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,58 +30,58 @@ Before proceeding, make sure you have the following prerequisites in place:
30
30
## Step 1: Sign in to the AWS Management Console
31
31
32
32
1. Open your preferred web browser and go to the [AWS Management Console](https://console.aws.amazon.com/).
33
-
1. Sign in to your AWS account using your credentials.
33
+
2. Sign in to your AWS account using your credentials.
34
34
35
35
## Step 2: Navigate to the Amazon RDS Dashboard
36
36
37
37
1. Once logged in to the AWS Management Console, search for **RDS** in the search bar at the top of the page.
38
-
1. Click on the **Amazon RDS** service from the search results to open the Amazon RDS dashboard.
38
+
2. Click on the **Amazon RDS** service from the search results to open the Amazon RDS dashboard.
39
39
40
40
## Step 3: Create a New Amazon RDS PostgreSQL Instance
41
41
42
42
1. Click on **Create database** button in the Amazon RDS dashboard.
43
-
1. On the **Choose a database creation method** page, select the **Standard Create** option.
44
-
1. Under the **Engine options** section, select **PostgreSQL** as the database engine.
45
-
1. Choose **PostgreSQL 13.18-R1**.
46
-
1. Under the **Templates** section, select the template that suits your needs or choose the default template.
47
-
1. In the **Settings** section, provide the following information:
43
+
2. On the **Choose a database creation method** page, select the **Standard Create** option.
44
+
3. Under the **Engine options** section, select **PostgreSQL** as the database engine.
45
+
4. Choose **PostgreSQL 13.22-R2**.
46
+
5. Under the **Templates** section, select the template that suits your needs or choose the default template.
47
+
6. In the **Settings** section, provide the following information:
48
48
-**DB instance identifier**: Enter a unique identifier for your RDS instance.
49
49
-**Master username**: Specify the username for the master user account.
50
50
-**Master password**: Set a secure password for the master user account.
51
-
1. In the **Instance configuration** section, select the appropriate instance size for your needs.
52
-
1. In the **Connectivity** section,
51
+
7. In the **Instance configuration** section, select the appropriate instance size for your needs.
52
+
8. In the **Connectivity** section,
53
53
- In **Compute resource**, select **Don't connect to an EC2 compute resource**.
54
54
- Select **Network type** as per your requirements.
55
55
- In **Virtual private cloud**, select the VPC you want to use for your Automate cluster.
56
56
- In **DB subnet group**, choose any private subnet available in your VPC.
57
57
- In **Public Access** select **NO**
58
-
1. Configure the remaining settings as per your requirements.
59
-
1. Review all the settings and make sure they are accurate.
60
-
1. Click on the **Create database** button to start the creation process.
58
+
9. Configure the remaining settings as per your requirements.
59
+
10. Review all the settings and make sure they are accurate.
60
+
11. Click on the **Create database** button to start the creation process.
61
61
62
62
## Step 4: Wait for the Amazon RDS Instance to be Created
63
63
64
64
1. The RDS instance creation process may take a few minutes. Wait for the process to complete.
65
-
1. You can monitor the progress of the instance creation on the Amazon RDS dashboard.
65
+
2. You can monitor the progress of the instance creation on the Amazon RDS dashboard.
66
66
67
67
## Step 5: Open the port in the RDS security group
68
68
69
69
1. Go to the Amazon RDS dashboard.
70
-
1. Find and select your newly created PostgreSQL instance from the list.
71
-
1. In the instance details view, navigate to the **Connectivity & security** tab.
72
-
1. Open the Security Group under **VPC security groups**.
73
-
1. Under **Inbound Rules**, edit and select **Type** as **PostgreSQL**.
74
-
1. Select **Source** as **custom** and give appropriate cidr block for your VPC.
75
-
1. Click on **Save Rules**.
70
+
2. Find and select your newly created PostgreSQL instance from the list.
71
+
3. In the instance details view, navigate to the **Connectivity & security** tab.
72
+
4. Open the Security Group under **VPC security groups**.
73
+
5. Under **Inbound Rules**, edit and select **Type** as **PostgreSQL**.
74
+
6. Select **Source** as **custom** and give appropriate cidr block for your VPC.
75
+
7. Click on **Save Rules**.
76
76
77
77
## Step 6: Retrieve Connection Details
78
78
79
79
Once the Amazon RDS PostgreSQL instance is created successfully, you can obtain the necessary connection details.
80
80
81
81
1. Go to the Amazon RDS dashboard.
82
-
1. Find and select your newly created PostgreSQL instance from the list.
83
-
1. In the instance details view, navigate to the **Connectivity & security** tab.
84
-
1. Here, you will find the following connection details:
82
+
2. Find and select your newly created PostgreSQL instance from the list.
83
+
3. In the instance details view, navigate to the **Connectivity & security** tab.
84
+
4. Here, you will find the following connection details:
85
85
-**Instance URL**: This is the endpoint or hostname of your RDS instance. It will look something like `my-rds-instance.abcdefg12345.us-east-1.rds.amazonaws.com`.
86
86
-**Port**: The port number your PostgreSQL instance listens to. The default port is usually `5432`.
87
87
-**Username**: The username of the master user account you specified during instance creation.
- Adding a new PostgreSQL node to the cluster may lead to increased replication lag on follower nodes, as multiple nodes will concurrently attempt to sync data from the leader.
102
103
{{< /note >}}
103
104
104
105
Once the command executes, it will add the supplied nodes to your automate setup. The changes might take a while.
Copy file name to clipboardExpand all lines: components/docs-chef-io/content/automate/ha_remove_single_node_from_cluster.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Chef Automate HA comes with five different types of deployment flows. This page
19
19
20
20
{{< warning >}}
21
21
22
-
- We do not recommend removing any node from the backend cluster, but replacing it is recommended. To learn more, see the [replace node in automate ha cluster](#replace-node-in-automate-ha-cluster) section.
22
+
- We do not recommend removing any node from the backend cluster, but replacing it is recommended. To replace a backend node, first [**add a node to the cluster**](/automate/ha_add_nodes_to_the_deployment/) and then [**remove the node from the cluster**](/automate/ha_remove_single_node_from_cluster/) that you wish to discard.
23
23
24
24
- Removal of nodes for PostgreSQL or OpenSearch is at your own risk and may result in data loss. Consult your database administrator before trying to delete PostgreSQL or OpenSearch nodes.
25
25
- Below process can be done for `chef-server` and `automate`.
The above command will trigger the `config.toml` file with config, the one you want to deploy.
35
35
36
+
To view detailed debug logs in the console, you can use the debug flag:
37
+
38
+
```bash
39
+
chef-automate verify --config config.toml -d
40
+
```
41
+
36
42
The post deployment CLI command is as follows:
37
43
38
44
```bash
@@ -75,4 +81,28 @@ An example of a checks performed are shown in the below image:
75
81
76
82
The above image shows the checks performed for Automate node. The checks in the above image are also performed on all the nodes in Automate HA, i.e., Chef Server, PostgreSQL, OpenSearch, and Chef Automate (the one showed above).
77
83
78
-
THe verify command checks all the nodes in Automate HA and with that it also provides the remediation steps for failures.
84
+
The verify command checks all the nodes in Automate HA and with that it also provides the remediation steps for failures.
85
+
86
+
## Additional Verification via System Logs
87
+
88
+
In addition to running the chef-automate verify command, you can inspect system logs for deeper insights into the verification service.
89
+
90
+
### On the Bastion Host
91
+
92
+
To view logs related to the automate-verify service on the bastion host, use:
93
+
94
+
```bash
95
+
journalctl -u automate-verify
96
+
```
97
+
98
+
This helps identify which API checks may have failed during verification.
99
+
100
+
### On Individual Nodes
101
+
102
+
Based on the failed API identified from the bastion logs, you can run the same command on the corresponding node to validate the service response:
103
+
104
+
```bash
105
+
journalctl -u automate-verify
106
+
```
107
+
108
+
This provides node-level visibility into the verification process and helps in troubleshooting specific failures.
0 commit comments