About MCaaS
Getting Started
Onboarding
New Tenant
If you are a new tenant and are being onboarded to the MCaaS platform for the first time, please submit an FCS Onboarding Request
You will be asked for the following information:
MCaaS Terminology | Description |
---|---|
host | documentdb host url |
Tenant name/short code | Used by the MCaaS team to create your AWS account and tag your backend resources. The short code is the tenant acronym (if applicable) |
Module(s) | <p> A module is a grouping of related applications. You can opt to have a single module called core for all of your applications to be grouped under. </p> <p>Each module will be assigned 4 EKS clusters representing the development, test, staging, production environments (test is optional; let us know if you do not wish to have a test cluster)</p> |
Application(s) | <p>Applications are software components that may be comprised of one of more services.</p> <p>Services belonging to the same application will be deployed in the same namespace in the EKS cluster</p> |
Service(s) | Services define the granular components that together define an application (i.e. microservices) |
New Developer
If you are a new developer and are being onboarded to the MCaaS platform for the first time, follow these steps to Request an FCS Account
This request will provide you access to:
- Jenkins
- Github
- Datadog
In addition, you can submit a request for access to SecOps tooling
Next Steps
- Read our documentation on your Initial MCaaS Setup
- Read our documentation on the Application Lifecycle
- See our Available MCaaS Services
- On this page: