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: README.md
+22Lines changed: 22 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,8 @@ Migrates your visiblity information in cloudconformity.com to cloudone.trendmicr
41
41
```
42
42
**Note:** Once you finish the tool configuration once, a file called **user-config.yml** with the settings you configured will be generated in the same folder, in case you need to re-run the tool.
43
43
44
+
For Cloud One Conformity API endpoints, you can use the format: ```https://conformity.{region}.cloudone.trendmicro.com/api/```, here you can find more information about [Cloud One Regions](https://cloudone.trendmicro.com/docs/identity-and-account-management/c1-regions/).
45
+
44
46
7) If you have AWS accounts to migrate, you can either manually update your Conformity Stack's `ExternalID` parameter during migration on the next step or you can run this command `conformity-migration-aws` first before migration.
45
47
46
48
Run this command to see all the available options:
@@ -82,6 +84,24 @@ Migrates your visiblity information in cloudconformity.com to cloudone.trendmicr
82
84
conformity-migration run --skip-aws-prompt
83
85
```
84
86
87
+
9) In case you need to only migrate one or a few accounts, you can create a CSV file containing accounts that will be the only ones included in migration. In the CSV file, each row should consists of 2 fields: first is the account name and second is the environment as they appear on Conformity Dashboard. An empty file means the tool won't include any account in the migration. Here's an example:
88
+
89
+
```
90
+
my-aws-account-name,production
91
+
my-azure-subscription-name,development
92
+
```
93
+
94
+
To excute the migration simply execute:
95
+
96
+
```
97
+
conformity-migration run --include-accounts-file file.csv
98
+
```
99
+
100
+
The same concept apply to exclude accounts from the migration:
101
+
102
+
```
103
+
conformity-migration run --exclude-accounts-file file.csv
104
+
```
85
105
86
106
## Migration support
87
107
### Cloud Types
@@ -97,6 +117,7 @@ Migrates your visiblity information in cloudconformity.com to cloudone.trendmicr
97
117
- **Note**: The tool will display other users that needs to be invited by the admin to CloudOne Conformity.
98
118
- [X] Groups
99
119
- [X] Communication channel settings
120
+
- **Note**: The tool cannot migrate Jira, ServiceNow or ZenDesk Communication Settings, for these, it has to be migrated manually.
100
121
- [X] Profiles
101
122
- [X] Report Configs
102
123
@@ -109,6 +130,7 @@ Migrates your visiblity information in cloudconformity.com to cloudone.trendmicr
109
130
- [X] Account Rule settings
110
131
- **Limitation:** The API only allows writing a single note to the rule so the tool won't be able to preserve the history of notes. The tool will instead combine history of notes into a single note before writing it.
111
132
- [X] Communication channel settings
133
+
- **Note**: The tool cannot migrate Jira, ServiceNow or ZenDesk communication settings, for these, it has to be migrated manually.
112
134
- [X] Checks
113
135
- **Limitation:** The API only allows writing a single note to the check so the tool won't be able to preserve the history of notes. In addition to that, API only allows a maximum of 200 characters of note. The tool will only get the most recent note and truncate it to 200 characters before writing it.
0 commit comments