CCM-15541: Gateway Cluster Deployment

[jamesthompson26-nhs]

Description

• Removes the original ASG and related resources.
• Removes several unused SSM params which were originally intended to support automated deployments via service principal.
• Brings dev/nonprod in line with production gateway config for testing purposes.
• Tidy up the powershell script in the user-data to remove version pinning of the gateway software(which doesn't work anyway with the on premises gateway).
• Moves the Athena ODBC driver download URL to a variable.
• Remove version pinning of PowerBI Gateway as this is always overridden at install time by the msi itself and always results in the latest version being installed.
• Removed the PowerBI client.

Context

Required preparation to migrate off the incorrectly deployed Production instance.

My proposal is we should set up the 2 currently unused standalone instances as NEW Gateway cluster in the PowerBI service and migrate the reports to use this and then remove the existing cluster and underlying un-managed instance.

We cannot replicate accurately the state of Production currently so I'm proposing this as a way to parallel run with the existing Prod gateway and safely test the migration of reports onto the new logical gateway cluster. This should hopefully bring parity between NonProd and Prod, fix the patching schedule (1 instance in the cluster is patched on a Weds, 1 on a Sunday) and moving forward, Gateway software updates can be done via the PowerBI service console.

Next Steps

Once merged and deployed into Dev/NonProd we'll need Ross to configure the gateway in the PowerBI Service. it would then be good if we could get Grace to create 1 or more reports (I appreciate the data is nonsense) so that we can firstly test the gateway functionality, but also use them for PTL testing in the future.

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming
• If I have used the 'skip-trivy-package' label I have done so responsibly and in the knowledge that this is being fixed as part of a separate ticket/PR.

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud