Evolve¶
Clarity Transform generates a download-ready AWS Optimization and Licensing Assessment manual import workbook from its own discovery, SQL metadata and rightsizing data.
Where to find it¶
Go to Discover → Integrations, then select the Evolve card. The card's category label is Export. The integration's page has the Endpoints and History tabs; Integrations describes the page, its grid and its row actions.
Why we do this¶
Clarity already holds the discovery, the SQL Server metadata and the rightsizing output the workbook asks for.
So this is a formatting exercise rather than a data exercise, and treating it as one removes a week of spreadsheet work from an engagement that is usually already behind.
What we collect¶
Nothing. This is an output rather than a source. It reads Clarity's own data and produces a workbook.
- Discovery data: the devices and their configuration
- SQL Server metadata, which the assessment treats separately for licensing
- Rightsizing data, where a rightsizing exercise has been run
What it adds¶
A hand-assembled version drifts from Discover → Application Mapping and from the move groups and events on Plan → Move Groups and Plan → Events, and the divergence is usually discovered in a meeting.
What is deliberately not inferred¶
- Nothing is sent to AWS. The workbook is downloaded by the user; Clarity does not transmit it or contact any AWS service.
- The endpoint form has a Credential select. Whether Evolve uses a credential is not shown.
- The workbook is only as complete as the data behind it. Where rightsizing has not been run or SQL Server discovery has not covered an instance, the corresponding cells are empty rather than estimated.
What we require¶
The Evolve endpoint form has a Credential select. Whether Evolve uses a credential, and so whether a customer has anything to provision, is not shown.
Verification before handover¶
- Confirm the underlying data is complete first. The workbook exposes gaps rather than filling them.
- Confirm the workbook version matches what the assessment expects. The manual import format changes. Check the expected version before handing the file over rather than after it is rejected.
Configuring the endpoint¶
On the integration's Endpoints tab, select the add icon (Create New Integration Endpoints). The Create new entry form opens with these fields, in this order:
| Field | Value |
|---|---|
| Name | A name for the endpoint |
| Credential | A select on the form; whether Evolve uses it is not shown |
| Job Schedule | Optional. A five-field cron expression |
| Enabled | Ticked. The box is unticked when the form opens |
The help texts: Credential "Credentials can be configured under Settings/Identity and Access Management/Credentials."; Job Schedule "Cron schedule – Use five fields: 〈mm〉 〈hh〉 〈day-of-month〉 〈month〉 〈weekday〉".
The Credential list offers the credentials stored under Settings → Identity & Access Management → Credentials.
The endpoint form has no End Point field, although the Endpoints grid has an End Point column.
No field is marked as required. Technology is set by the card and is hidden in the form. Select Save to create the endpoint, or Cancel to close the form. The edit icon opens the same fields as Edit entry.
Evolve is the only integration whose endpoints are export jobs rather than discovery jobs. View Details on an Evolve endpoint shows Execution Kind Export and Result Mode Browser Download; other integrations show Discovery and Status Only. The Endpoints grid itself has no download button.
Removing the access¶
Nothing to remove. No account, no connectivity and no external system is involved.
Troubleshooting¶
| Symptom | Cause |
|---|---|
| Empty columns in the workbook | The underlying data is incomplete. Check SQL Server coverage and whether rightsizing has been run. |
| The assessment rejects the file | The manual import format has changed. Check the expected version. |
| Figures disagree with the Rightsizing tab on Infrastructure Discovery | Both read the same data, so a difference is a stale generation. Regenerate the workbook. |