Skip to content

Commit 501ac64

Browse files
nupurg-ibmNupur Goyal
nupurg-ibm
and
Nupur Goyal
authored
fix: Rocky Linux support for ldap<br>* New custom image for lsf fix (#179)
* updating public repo with private repo code * updating ssh under config file --------- Co-authored-by: Nupur Goyal <[email protected]>
1 parent b843834 commit 501ac64

File tree

24 files changed

+1521
-1302
lines changed

24 files changed

+1521
-1302
lines changed

‎.tekton/scripts/common_utils.sh‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,5 +33,6 @@ go version
3333
python3 -m pip install --upgrade pip
3434
python3 -m pip install --pre --upgrade requests==2.20.0
3535
python3 -m pip install --pre --upgrade ibm-cos-sdk==2.0.1
36+
ibmcloud plugin install key-protect -f
3637

3738
echo "************************************************"

‎.tekton/scripts/suites.sh‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ pr_ubuntu_suite() {
7979
# commit based suite on rhel-suite-1
8080
rhel_suite_1() {
8181
suite=rhel-suite-1
82-
test_cases="TestRunBasic,TestRunAppCenter,TestRunNoKMSAndHTOff"
82+
test_cases="TestRunBasic,TestRunAppCenter,TestRunNoKMSAndHTOff,TestRunCosAndVpcFlowLogs"
8383
new_line="${test_cases//,/$'\n'}"
8484
echo "************** Going to run ${suite} ${new_line} **************"
8585
common_suite "${test_cases}" "${suite}" "${compute_image_name_rhel:?}"
@@ -88,7 +88,7 @@ rhel_suite_1() {
8888
# commit based suite on rhel-suite-2
8989
rhel_suite_2() {
9090
suite=rhel-suite-2
91-
test_cases="TestRunLDAP,TestRunLDAPAndPac,TestRunCustomRGAsNonDefault"
91+
test_cases="TestRunLDAP,TestRunLDAPAndPac,TestRunCustomRGAsNonDefault,TestRunUsingExistingKMSInstanceIDAndWithoutKey"
9292
new_line="${test_cases//,/$'\n'}"
9393
echo "************** Going to run ${suite} ${new_line} **************"
9494
common_suite "${test_cases}" "${suite}" "${compute_image_name_rhel:?}"
@@ -124,7 +124,7 @@ ubuntu_suite_2() {
124124
# commit based suite on ubuntu-suite-3
125125
ubuntu_suite_3() {
126126
suite=ubuntu-suite-3
127-
test_cases="TestRunBasic,TestRunNoKMSAndHTOff"
127+
test_cases="TestRunBasic,TestRunNoKMSAndHTOff,TestRunExistingLDAP,TestRunExistingPACEnvironment"
128128
new_line="${test_cases//,/$'\n'}"
129129
echo "************** Going to run ${suite} ${new_line} **************"
130130
common_suite "${test_cases}" "${suite}" "${compute_image_name_ubuntu:?}"
@@ -142,7 +142,7 @@ regions_suite() {
142142
# negative based suite on negative-suite
143143
negative_suite() {
144144
suite=negative-suite
145-
test_cases="TestRunWithoutMandatory,TestRunInvalidReservationIDAndContractID,TestRunInvalidLDAPServerIP,TestRunInvalidLDAPUsernamePassword,TestRunInvalidAPPCenterPassword,TestRunInvalidDomainName,TestRunKMSInstanceNameAndKMSKeyNameWithInvalidValue,TestRunExistSubnetIDVpcNameAsNull"
145+
test_cases="TestRunWithoutMandatory,TestRunInvalidReservationIDAndContractID,TestRunInvalidLDAPServerIP,TestRunInvalidLDAPUsernamePassword,TestRunInvalidAPPCenterPassword,TestRunInvalidDomainName,TestRunKMSInstanceNameAndKMSKeyNameWithInvalidValue,TestRunExistSubnetIDVpcNameAsNull,TestRunInvalidSshKeysAndRemoteAllowedIP,TestRunInvalidSubnetCIDR"
146146
new_line="${test_cases//,/$'\n'}"
147147
echo "************** Going to run ${suite} ${new_line} **************"
148148
common_suite "${test_cases}" "${suite}" "${compute_image_name_rhel:?}"

‎modules/landing_zone_vsi/configuration_steps/compute_user_data_fragment.sh‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -233,13 +233,13 @@ cat /opt/ibm/lsf/conf/hosts >> /etc/hosts
233233
if [ "$enable_ldap" = "true" ]; then
234234

235235
# Detect the operating system
236-
if grep -q "NAME=\"Red Hat Enterprise Linux\"" /etc/os-release; then
236+
if grep -q "NAME=\"Red Hat Enterprise Linux\"" /etc/os-release || grep -q "NAME=\"Rocky Linux\"" /etc/os-release; then
237237

238-
# Detect RHEL version
239-
rhel_version=$(grep -oE 'release [0-9]+' /etc/redhat-release | awk '{print $2}')
238+
# Detect RHEL or Rocky version
239+
version=$(grep -oE 'release [0-9]+' /etc/redhat-release | awk '{print $2}')
240240

241-
if [ "$rhel_version" == "8" ]; then
242-
echo "Detected RHEL 8. Proceeding with LDAP client configuration...." >> $logfile
241+
if [ "$version" == "8" ]; then
242+
echo "Detected as RHEL or Rocky 8. Proceeding with LDAP client configuration...." >> $logfile
243243

244244
# Allow Password authentication
245245
sed -i 's/PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
@@ -294,7 +294,7 @@ EOF
294294
echo ". ${LSF_CONF}/profile.lsf" >> /etc/bashrc
295295
source /etc/bashrc
296296
else
297-
echo "This script is designed for RHEL 8. Detected RHEL version: $rhel_version. Exiting." >> $logfile
297+
echo "This script is intended for RHEL 8 or Rocky Linux 8. Detected version: $version. Exiting." >> $logfile
298298
exit 1
299299
fi
300300

‎modules/landing_zone_vsi/configuration_steps/configure_management_vsi.sh‎

Lines changed: 21 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,7 @@ LSF_TOP_VERSION="$LSF_TOP/10.1"
4949
LSF_SUITE_TOP="/opt/ibm/lsfsuite"
5050
LSF_SUITE_GUI="${LSF_SUITE_TOP}/ext/gui"
5151
LSF_SUITE_GUI_CONF="${LSF_SUITE_GUI}/conf"
52+
LSF_SUITE_GUI_WORK="${LSF_SUITE_GUI}/work"
5253
LSF_SUITE_PERF="${LSF_SUITE_TOP}/ext/perf"
5354
LSF_SUITE_PERF_CONF="${LSF_SUITE_PERF}/conf"
5455
LSF_SUITE_PERF_BIN="${LSF_SUITE_PERF}/1.2/bin"
@@ -265,7 +266,10 @@ EOT
265266
"ca-tor": "https://ca-tor.iaas.cloud.ibm.com/v1",
266267
"jp-osa": "https://jp-osa.iaas.cloud.ibm.com/v1",
267268
"jp-tok": "https://jp-tok.iaas.cloud.ibm.com/v1",
268-
"br-sao": "https://br-sao.iaas.cloud.ibm.com/v1"
269+
"br-sao": "https://br-sao.iaas.cloud.ibm.com/v1",
270+
"us-south": "https://us-south.iaas.cloud.ibm.com/v1",
271+
"eu-de": "https://eu-de.iaas.cloud.ibm.com/v1",
272+
"us-east": "https://us-east.iaas.cloud.ibm.com/v1"
269273
}
270274
}
271275
EOT
@@ -674,6 +678,7 @@ mount_nfs_with_retries() {
674678
if [ -n "${nfs_server_with_mount_path}" ]; then
675679
echo "File share ${nfs_server_with_mount_path} found"
676680
nfs_client_mount_path="/mnt/lsf"
681+
nfs_client_mount_pac_path="${nfs_client_mount_path}/pac"
677682
if mount_nfs_with_retries "${nfs_server_with_mount_path}" "${nfs_client_mount_path}"; then
678683
# Move stuff to shared fs
679684
for dir in conf work das_staging_area; do
@@ -688,15 +693,22 @@ if [ -n "${nfs_server_with_mount_path}" ]; then
688693
done
689694

690695
# Sharing the lsfsuite.conf folder
691-
if [ "$on_primary" == "true" ]; then
692-
rm -rf "${nfs_client_mount_path}/gui-conf"
693-
mv "${LSF_SUITE_GUI_CONF}" "${nfs_client_mount_path}/gui-conf"
694-
chown -R lsfadmin:root "${nfs_client_mount_path}/gui-conf"
695-
else
696-
rm -rf "${LSF_SUITE_GUI_CONF}"
696+
if [ "$on_primary" == "true" ] && [ "$enable_app_center" == "true" ] && [ "$app_center_high_availability" == "true" ]; then
697+
# Create pac folder if it does not exist
698+
[ ! -d "${nfs_client_mount_pac_path}" ] && mkdir -p "${nfs_client_mount_pac_path}"
699+
700+
# Remove the original folder and create symlink for gui-conf
701+
[ -d "${nfs_client_mount_pac_path}/gui-conf" ] && rm -rf "${nfs_client_mount_pac_path}/gui-conf"
702+
mv "${LSF_SUITE_GUI_CONF}" "${nfs_client_mount_pac_path}/gui-conf"
703+
chown -R lsfadmin:root "${nfs_client_mount_pac_path}/gui-conf" && chown -R lsfadmin:lsfadmin "${LSF_SUITE_GUI_CONF}"
704+
ln -fs "${nfs_client_mount_pac_path}/gui-conf" "${LSF_SUITE_GUI_CONF}"
705+
706+
# Remove the original folder and create symlink for gui-work
707+
[ -d "${nfs_client_mount_pac_path}/gui-work" ] && rm -rf "${nfs_client_mount_pac_path}/gui-work"
708+
mv "${LSF_SUITE_GUI_WORK}" "${nfs_client_mount_pac_path}/gui-work"
709+
chown -R lsfadmin:root "${nfs_client_mount_pac_path}/gui-work" && chown -R lsfadmin:lsfadmin "${LSF_SUITE_GUI_WORK}"
710+
ln -fs "${nfs_client_mount_pac_path}/gui-work" "${LSF_SUITE_GUI_WORK}"
697711
fi
698-
ln -fs "${nfs_client_mount_path}/gui-conf" "${LSF_SUITE_GUI_CONF}"
699-
chown -R lsfadmin:root "${LSF_SUITE_GUI_CONF}"
700712

701713
# Create a data directory for sharing HPC workload data
702714
if [ "$on_primary" == "true" ]; then
@@ -705,14 +717,6 @@ if [ -n "${nfs_server_with_mount_path}" ]; then
705717
chown -R lsfadmin:root "$LSF_TOP/work/data"
706718
fi
707719

708-
# Sharing the 10.1 folder
709-
if [ "$on_primary" == "true" ]; then
710-
rm -rf "${nfs_client_mount_path}/10.1"
711-
mv "${LSF_TOP_VERSION}" "${nfs_client_mount_path}"
712-
ln -s "${nfs_client_mount_path}/10.1" "${LSF_TOP_VERSION}"
713-
chown -R lsfadmin:root "${LSF_TOP_VERSION}"
714-
fi
715-
716720
# VNC Sessions
717721
if [ "$on_primary" == "true" ]; then
718722
mkdir -p "${nfs_client_mount_path}/repository-path"

‎modules/landing_zone_vsi/image_map.tf‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
locals {
22
image_region_map = {
3-
"hpcaas-lsf10-rhel88-v9" = {
4-
"us-east" = "r014-d2b18006-c0c4-428f-96f3-e033b970c582"
5-
"eu-de" = "r010-3bf3f57e-1985-431d-aefe-e9914ab7919c"
6-
"us-south" = "r006-7b0aa90b-f52c-44b1-bab7-ccbfae9f1816"
3+
"hpcaas-lsf10-rhel88-v10" = {
4+
"us-east" = "r014-c425251e-b7b5-479f-b9cf-ef72a0f51b5a"
5+
"eu-de" = "r010-ce6dac2b-57e4-4a2f-a77d-8b0e549b2cae"
6+
"us-south" = "r006-c8fefef3-645d-4b5a-bad0-2250c6ddb627"
77
},
8-
"hpcaas-lsf10-rhel88-compute-v5" = {
9-
"us-east" = "r014-deb34fb1-edbf-464c-9af3-7efa2efcff3f"
10-
"eu-de" = "r010-2d04cfff-6f54-45d1-b3b3-7e259083d71f"
11-
"us-south" = "r006-236ee1f4-38de-4845-b7ec-e2ffa7df5d08"
8+
"hpcaas-lsf10-rhel88-compute-v6" = {
9+
"us-east" = "r014-f4c0dd0f-3bd0-4e2f-bbda-bbbc75a8c33b"
10+
"eu-de" = "r010-0217f13b-e6e5-4500-acd4-c170f111d43f"
11+
"us-south" = "r006-15514933-925c-4923-85dd-3165dcaa3180"
1212
},
13-
"hpcaas-lsf10-ubuntu2204-compute-v5" = {
14-
"us-east" = "r014-ecbf4c89-16a3-472e-8bab-1e76d744e264"
15-
"eu-de" = "r010-9811d8bf-a7f8-4ee6-8342-e5af217bc513"
16-
"us-south" = "r006-ed76cb75-f086-48e9-8090-e2dbc411abe7"
13+
"hpcaas-lsf10-ubuntu2204-compute-v6" = {
14+
"us-east" = "r014-ab2e8be8-d75c-4040-a337-7f086f3ce153"
15+
"eu-de" = "r010-027f5d54-9360-4d1f-821b-583329d63855"
16+
"us-south" = "r006-628b6dbe-e0d4-4c25-bc0f-f554f5523f2e"
1717
}
1818
}
1919
}

‎samples/configs/hpc_catalog_values.json‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@
2020
"enable_cos_integration" : "false",
2121
"cos_instance_name" : "__NULL__",
2222
"enable_fip" : "true",
23-
"management_image_name" : "hpcaas-lsf10-rhel88-v9",
24-
"compute_image_name" : "hpcaas-lsf10-rhel88-compute-v5",
25-
"login_image_name" : "hpcaas-lsf10-rhel88-compute-v5",
23+
"management_image_name" : "hpcaas-lsf10-rhel88-v10",
24+
"compute_image_name" : "hpcaas-lsf10-rhel88-compute-v6",
25+
"login_image_name" : "hpcaas-lsf10-rhel88-compute-v6",
2626
"login_node_instance_type" : "bx2-2x8",
2727
"management_node_instance_type" : "bx2-16x64",
2828
"management_node_count" : "3",

‎samples/configs/hpc_schematics_values.json‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -197,25 +197,25 @@
197197
},
198198
{
199199
"name": "management_image_name",
200-
"value": "hpcaas-lsf10-rhel88-v9",
200+
"value": "hpcaas-lsf10-rhel88-v10",
201201
"type": "string",
202202
"secure": false,
203203
"description": "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
204204
},
205205
{
206206
"name": "compute_image_name",
207-
"value": "hpcaas-lsf10-rhel88-compute-v5",
207+
"value": "hpcaas-lsf10-rhel88-compute-v6",
208208
"type": "string",
209209
"secure": false,
210-
"description": "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster dynamic compute nodes. By default, the solution uses a RHEL 8-6 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v5). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
210+
"description": "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster dynamic compute nodes. By default, the solution uses a RHEL 8-8 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v6). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
211211

212212
},
213213
{
214214
"name": "login_image_name",
215215
"value": "hpcaas-lsf10-rhel88-compute-v5",
216216
"type": "string",
217217
"secure": false,
218-
"description": "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-6 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v5). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
218+
"description": "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-8 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v6). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
219219
},
220220
{
221221
"name": "login_node_instance_type",
@@ -324,7 +324,7 @@
324324
"value": "true",
325325
"type": "bool",
326326
"secure": false,
327-
"description": "Enable Activity tracker service instance connected to Cloud Object Storage (COS). All the events will be stored into COS so that customers can connect to it and read those events or ingest them in their system."
327+
"description": "Enable Activity tracker service instance connected to Cloud Object Storage (COS). All the events will be stored in COS so customers can retrieve or ingest them in their system. While multiple Activity Tracker instances can be created, only one tracker is needed to capture all events. Creating additional trackers is unnecessary if an existing Activity Tracker is already integrated with a COS bucket. In such cases, set the value to false, as all events can be monitored and accessed through the existing Activity Tracker."
328328
},
329329
{
330330
"name": "enable_ldap",

‎solutions/hpc/variables.tf‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -176,21 +176,21 @@ variable "login_node_instance_type" {
176176
}
177177
variable "management_image_name" {
178178
type = string
179-
default = "hpcaas-lsf10-rhel88-v9"
179+
default = "hpcaas-lsf10-rhel88-v10"
180180
description = "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
181181

182182
}
183183

184184
variable "compute_image_name" {
185185
type = string
186-
default = "hpcaas-lsf10-rhel88-compute-v5"
187-
description = "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster dynamic compute nodes. By default, the solution uses a RHEL 8-8 base OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v5). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
186+
default = "hpcaas-lsf10-rhel88-compute-v6"
187+
description = "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster dynamic compute nodes. By default, the solution uses a RHEL 8-8 base OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v6). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
188188
}
189189

190190
variable "login_image_name" {
191191
type = string
192-
default = "hpcaas-lsf10-rhel88-compute-v5"
193-
description = "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-8 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v5). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
192+
default = "hpcaas-lsf10-rhel88-compute-v6"
193+
description = "Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster login node. By default, the solution uses a RHEL 8-8 OS image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). The solution also offers, Ubuntu 22-04 OS base image (hpcaas-lsf10-ubuntu2204-compute-v6). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering."
194194
}
195195

196196
variable "management_node_instance_type" {
@@ -296,7 +296,7 @@ variable "cos_instance_name" {
296296
variable "observability_atracker_on_cos_enable" {
297297
type = bool
298298
default = true
299-
description = "Enable Activity tracker service instance connected to Cloud Object Storage (COS). All the events will be stored into COS so that customers can connect to it and read those events or ingest them in their system."
299+
description = "Enable Activity tracker service instance connected to Cloud Object Storage (COS). All the events will be stored in COS so customers can retrieve or ingest them in their system. While multiple Activity Tracker instances can be created, only one tracker is needed to capture all events. Creating additional trackers is unnecessary if an existing Activity Tracker is already integrated with a COS bucket. In such cases, set the value to false, as all events can be monitored and accessed through the existing Activity Tracker."
300300
}
301301

302302
variable "enable_vpc_flow_logs" {

0 commit comments

Comments
 (0)