[DOCS-10637] Limitations of Atlas vs. Cloud Manager/Self-managed. Created: 04/Aug/17  Updated: 29/Oct/23  Resolved: 25/Sep/18

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Jeffrey Numark Assignee: Jonathan DeStefano
Resolution: Fixed Votes: 0
Labels: change
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.atlas.mongodb.com/create-new-cluster/


Participants:
Days since reply: 5 years, 48 weeks, 5 days ago
Epic Link: DOCSP-1743
Story Points: 0.1

 Description   

In https://docs.atlas.mongodb.com/create-new-cluster/ we don't mention common items that are configurable in self-managed / Cloud Manager today that are not yet available in Atlas. This has caused some pain during "Atlas Migration Consulting" packages. The customers expect that they will be able to have a seamless migration, but then find out that there will be some work involved to make their application configurable on Atlas.

For example:

  • You must enable TLS / SSL
  • You cannot select your region for backups or restore them with APIs
  • You cannot have multiple VPCs per group


 Comments   
Comment by Ravind Kumar (Inactive) [ 09/Mar/18 ]

Note, with Cloud Provider Snapshots rolling out this year, the parity of regional backups is upcoming.

For the moment I'm going to highlight the TLS/SSL requirement on the create a cluster page.

I'm also going to update https://docs.atlas.mongodb.com/faq/#service-fullname-or-cloud-manager to point out that Atlas requires TLS encryption and is beginning to roll out cloud provider snapshots for regional backups. I think that should resolve confusion moving forward.

Comment by Ravind Kumar (Inactive) [ 05/Feb/18 ]

backup / restoration API is inbound for 20180213. However you still cannot choose your backup region. We can mention this here so that users see this important point as soon as they look at the documentation for enabling backup.

TLS/SSL is mentioned on the landing page, but we can call it out in the introductory paragraph to this page to emphasize the point.

Generated at Thu Feb 08 08:01:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.