When you export an Amazon Web Services visibility job, Cloud Discovery & Visibility (CDV) exports the file as an unencrypted JSON configuration file. The JSON code below illustrates the style and format of the exported file.
You can use an exported configuration file as a template that you edit to create new
visibility jobs that you can import into CDV. When doing so, note that all keys in the
options section are required, though you can edit the values as needed.
Attention: If you wan to run visibility jobs in another CDV instance, BlueCat
recommends stopping any running visibility jobs in the old CDV instance before importing and
running the visibility jobs in the new CDV instance.
{
"Amazon Web Services": [
{
"aws_account": "430667896580",
"aws_region": "us-east-1",
"aws_user_arn": "test_user",
"bam_configuration": "test",
"bam_url": "1.1.1.1",
"bam_username": "test",
"id": 1,
"options": {
"authentication": {
"aws_access_key": "AKPO6HEUVUIA5VOYDAWY",
"aws_role_arn": "",
"aws_secret_key": "<secret_key_encryption>",
"region_name": "us-east-1"
},
"auto_create_subzone": false,
"bluecat_configuration": "",
"create_separate_configuration": false,
"device_external_view": "",
"device_internal_view": "",
"dns_private_view": "",
"dns_public_view": "",
"dynamic_update": false,
"external_name_resolution": false,
"internal_name_resolution": false,
"load_balancers": false,
"override_configuration": true,
"private_dns_zones": false,
"private_endpoint_view": "AWS VPC Endpoints View",
"private_endpoints": false,
"private_networks": true,
"public_dns_zones": false,
"public_networks": false,
"target_domain": "",
"virtual_machines": false,
"k8s_service": false,
"visibility": {
"aws_access_key": "AKPO6HEUVUIA5VOYDAWY",
"aws_role_arn": "",
"aws_secret_key": "<secret_key_encryption>",
"bam_password": "<bam_password_encryption>",
"bam_username": "bam_user",
"selective_deployment": false
}
},
"visibility_end_time": "10/11/2021 07:52:16",
"visibility_start_time": "10/11/2021 07:52:55",
"visibility_status": "running"
}
]
}