| section | description | topics | contentType | useCase |
|---|---|---|---|---|
private-cloud |
Differences between the two Managed Private Cloud deployment options and the Customer-Hosted RACI |
managed-private-cloud |
concept |
private-cloud |
The customer-hosted Managed Private Cloud provides you with everything you need to run Auth0 in your Amazon Web Services environment.
| Auth0-Hosted | Customer-Hosted on AWS | |
| Public-Facing? | Yes | Can be configured to be public-facing or not |
| Service and Uptime Reporting | Auth0 responsible for monitoring | Customer responsible for monitoring |
| Infrastructure and Backup Responsibility | Auth0 responsible for backups | Customer responsible for backups |
| PCI Compliance Add-On | Available | Not available |
| Breached Password Detection | Available | Not available |
| AWS Costs | Not applicable | Customer responsible for all AWS costs associated with running the infrastructure required for a customer-hosted deployment |
Auth0 is responsible for:
- The initial installation
- General maintenance
- Installation of patches and updates
The subscriber/customer is responsible for supplying and monitoring the infrastructure on which the Private Cloud runs. This includes, but is not limited to:
- The EC2 hosts
- Data storage
- Network resources
- Any required dependencies
The following RACI Matrix provides an in-depth summary of the roles and responsibilities that will be allocated between Auth0 and the customer/subscriber.
RACI:
- Responsible: the assigned party who is responsible for executing the task
- Accountable: the assigned party who is accountable for the task being completed
- Consulted: the party/parties whose opinions are requested and with whom there is two-way communication
- Informed: the party/parties who are kept up-to-date with regards to progress and with whom there is one-way communication
| Private Cloud-Related Tasks or Deliverables | Auth0 | Customer/Subscriber | Notes |
| Preparing AWS Infrastructure (including memory, storage, processors, load balances, networks, SSL certificates, DNS records, SMTP servers, enabling Auth0 access via Jumphost/VPN) | C | R, A (the subscriber's infrastructure engineer) | The subscriber will contact Auth0 when the AWS environment is ready and the infrastructure requirements are met |
| Set up Development and Production environments | R, A (the Managed Services Engineer (MSE)) | I | The Auth0 Managed Service Engineer will SSH into the AWS environment and deploy the Auth0 Private Cloud |
| Configure Development and Production environments | C | R | The Auth0 Managed Service Engineer will show the subscriber's infrastructure engineer how to upload the SSL certificates, enter the SMTP credentials, and add administrators |
| Operations Handover | R | C | The Auth0 Managed Service Engineer and Technical Account Managers will hold an Operations Handover meeting to review information regarding Private Cloud monitoring, backup, and updates and to answer questions |
| Monitoring | I | R, A | The subscriber is responsible for monitoring the Private Cloud Deployment |
| Backing Up | I (in the event there are issues) | R, A | The subscriber is responsible for backing up the Private Cloud deployment using the Command-Line Tools |
| User Migration (if required) | C, I (in the event there are issues) | R, A | The subscriber is responsible for migrating users where appropriate |
| Updates | R | R, A | The Auth0 Managed Service Engineers will partner with the subscriber's infrastructure engineers to update the Private Cloud Deployment on an agreed-upon basis. The subscriber is responsible for taking AMI snapshot(s) prior to the update, providing access to the Private Cloud deployment, and being present during the update. Auth0 is responsible for running manual scripts (if required) and informing the subscriber on the status of the update |
| Testing Updates in Non-Production Environment(s) | C, I (in the event that there are questions/issues) | R, A | The subscriber will test the Private Cloud after the Development node has been updated and inform Auth0 of any issues |
| Testing Updates in Production | C, I (in the event that there are questions/issues) | R, A | The subscriber will test the Private Cloud after the Production node has been updated and inform Auth0 of any issues |
| Issue Identification and Support Ticket Submission | C | R, A | The subscriber is responsible for submitting issues via the Support Center |
| Issue Resolution | R, C | C | Auth0 will provide support for issues within the *core* of the Auth0 product. Auth0 will consult on issues pertaining to integration with the Auth0 product |