Application hosting considerations and restrictions

On this page


1. Provisions

1.1 These provisions are issued by the GC CIO under the authority of the Directive on Service and Digital.

2. General application deployment considerations

2.1 As set out in the Standard on At-Risk Technology, unsupported technologies cannot be deployed to the public cloud or Shared Services Canada (SSC) data centres. Departmental planning processes must include migration plans for all deployed applications that use unsupported technologies.

3. Cloud deployment considerations

3.1 All Cloud intake requests for Public Services and Procurement Canada and SSC cloud services must be submitted to GC Cloud Brokering Services.

3.2 All applications deployed to public cloud must be identified in the SSC-managed Configuration Management Database (CMDB) using the application identification from the TBS-managed Application Portfolio Management inventory.

4. Requirements for enterprise data centres

4.1 In dedicated enclave environments, partner growth of existing and new virtual servers is permitted up to installed physical capacity levels.

4.2 New stand-alone physical server installation must be pre-approved by SSC. Such installation will apply when:

5. Restrictions and considerations for legacy data centres without a planned closure date

5.1 Growth of existing and new virtual servers is permitted, up to existing physical capacity levels.

5.2 New physical capacity installations within virtualized platforms are permitted, subject to facility constraints.

5.3 New stand-alone physical server installations must be pre-approved by SSC.

6. Restrictions and considerations for legacy data centres with a planned closure date

6.1 Growth of existing and new virtual servers is permitted, up to installed physical capacity levels.

6.2 No new physical capacity installation is permitted.

Page details

Date modified: