Skip to content

Moraph for clients

Sign in

Getting started

Getting started with Public Cloud Infrastructure

What Public Cloud Infrastructure is for, who uses it, what you need before you start, and your first steps.

Applies to Public Cloud Infrastructure as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 2 min readReport a problem
On this page
  1. What it is for
  2. Who uses it
  3. Before you start
  4. Steps to get started
  5. Where to go next

Moraph resells, sets up and runs Amazon Web Services environments for banks, credit unions, lenders and investment firms. We build a multi-account structure with preventive and detective guardrails written as policy as code, so storage holding consumer data cannot be made public, encryption and logging are required, and every exception is approved and recorded. AWS operates the cloud itself; Moraph operates your configuration of it; your organization keeps the decisions about risk, data and access.

What it is for

Financial institutions move workloads to AWS faster than their controls follow. Accounts are created by different teams with different settings, storage buckets are opened for a quick data transfer and never closed, and logging and encryption depend on whoever built the workload. Security teams find misconfigurations after the fact, and when examiners ask how the institution prevents consumer data from being exposed in the cloud, the answer is a mix of console screenshots, wiki pages and good intentions.

  • Accounts and workloads are configured by hand, so settings drift from the agreed baseline
  • A single storage bucket made public can expose consumer financial data
  • Guardrails exist on paper but are not enforced before a change reaches production
  • Evidence of cloud controls for examiners and auditors is assembled by hand

Who uses it

  • Banks, credit unions, lenders and investment firms running or moving workloads to AWS
  • CISOs and security teams who answer for cloud controls
  • Infrastructure and platform teams who want an operated landing zone rather than building one
  • Application teams who need cloud accounts quickly without bypassing controls
  • Internal audit, third-party risk and examiners reviewing cloud governance

Before you start

  • Your organization uses Public Cloud Infrastructure as a managed platform from Moraph, under an agreement that covers it.
  • Licences for AWS Financial Services, bought through Moraph or under your own agreement with the vendor.
  • A Moraph account in your organization for each person who works with Moraph on the service.
  • Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

  1. Agree the scope of the managed service for Public Cloud Infrastructure with Moraph, including which environments and teams it covers.

  2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

  3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

  4. Confirm how users will sign in, through your identity provider where the platform supports it.

  5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.