Skip to content

AdminAndrew Davidson (VP, Cloud Products, MongoDB)

My feedback

184 results found

  1. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Renato,

    A few notes: MongoDB Atlas database users do have the concept of an expiration time (we call these temporary users).

    It's true that for MongoDB's SCRAM user/pass authentication option, Atlas does not allow you to define password rules: You can however look at using our Vault secrets engine integration which can do a lot of this for you: https://www.vaultproject.io/docs/secrets/databases/mongodbatlas

    Separately Atlas does support three other authentication options:
    - Passwordless X.509 client side certificates
    - LDAP which allows you to bring your own identity provider which can have its own rules (this model requires that Atlas cluster nodes be able to reach your LDAP service over the network, however)
    - and finally, with the introduction of MongoDB 4.4 beta: AWS IAM User/Role based authentication.

    Cheers
    -Andrew

  2. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Juan,

    Have you looked at running mongomirror yourself? This gives you the ability to "push" the data from your VPC to Atlas, and mongomirror is what powers Live Migration. For completeness, this model works for replica sets but not sharded clusters. https://docs.atlas.mongodb.com/import/mongomirror/

    -Andrew

  3. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Gotcha, and Splunk can't be configured to receive an alert notification in-bound using a "lower tech" method like email or SMS?

    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 
  4. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Connell,

    Being intellectually honest with you, bringing a true SaaS-style experience to Azure Stack, Google Anthos, or AWS Outposts that compares with Atlas is unfortunately a very large undertaking.

    However, where you cannot take advantage of a pure-play public cloud region on one of the big three, we do offer an alternative: MongoDB Cloud Manager offers software that helps you monitor, automate, and backup your self-managed MongoDB databases https://www.mongodb.com/cloud/cloud-manager While Cloud Manager certainly does require more work for you than Atlas, it at least offers that true flexibility you're seeking for when you need to reach regions that Atlas cannot yet reach. You can use our Kubernetes operator in this model by the way, which at least offers a standard orchestration tie-in for non-public cloud contexts.

    -Andrew

  5. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Todd,

    We'd love to see you provide this feedback to Splunk too. We do plan to introduce a push-based destination for logs to S3 in the future which will open up more options.

    Otherwise, in the interim we have pull-based integrations from jSonar (they can in fact route to Splunk) and Sumo Logic.

    Cheers
    -Andrew

  6. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    We definitely look forward to building a better way to manage billing contexts in the future, likely involving tagging, as well as to making Atlas cluster tags more visible within the UI in some capacity in the future. We are working on a number of other priorities right now so this will not be something we'll see for a while, unfortunately.

    -Andrew

  7. 41 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Atlas » Autoscaling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hear you there: we are working on designing a very different higher level of abstraction offering that aims to deliver to what you want here. This is going to take time but definitely appreciate the feedback.

    -Andrew

    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Babak,

    One of the challenges is that it's significantly more expensive to opt into Provisioned IOPS even when not using too many of them -- Can you confirm whether you would be comfortable using Provisioned IOPS all the time (there is a significant premium cost to doing so) in order to leverage auto-scaling for IOPS?

    Further, what kinds of indicators for your workload would you see as canonical drivers of needing to scale IOPS? We want to learn from you since this is nuanced and difficult to get right.

    -Andrew

  8. 20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Martel,

    One option available today is configure identity federation (https://docs.atlas.mongodb.com/security/federated-authentication/) and then use the auditing that your IdP offers.

    Note that Atlas audits any material action taken within the MongoDB Cloud UI (cluster configuration changes, security configuration changes, data explorer usage, etc).

    -Andrew

  9. 19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    It is possible to use the generic Webhooks endpoint to push to ServiceNow: We are working to get a tutorial documented.

    -Andrew

  10. 28 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Compass » General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Neelakantan,

    Have you seen both the data explorer (found under the "Collections" button on the Atlas cluster) which offers a query browser and aggregation pipeline builder, and MongoDB Charts which offers beautiful native visualizations on top of data in your MongoDB Atlas clusters?

    Cheers
    -Andrew

  11. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Colin,

    Thanks for flagging: we hear you loud and clear here and will be working on this in a few months, after we complete some projects in flight. We'll be mindful to ensure that we don't break programmatic users of our APIs when making this change.

    -Andrew

  12. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Shaun,

    Have you looked into enabling Atlas cluster auto-scaling? This will allow you to rely on Atlas' built in algorithm for doing this scaling, which will take into account whether downscaling is appropriate. Learn more here: https://docs.atlas.mongodb.com/cluster-autoscaling/

    Cheers
    -Andrew

  13. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas Search  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Jan,

    The great thing about aggregations is that you're pushing down to the database engine to do the heavy lifting. However where you wish to have workload isolation so that your operational workload is not fighting for resources with your analytical/heavy aggregations, we recommend you explore Atlas Analytics Nodes -- these are special replicas that you target for isolated queries using a read preference tag. Learn more here: https://docs.atlas.mongodb.com/workload-isolation/#analytics-nodes-for-workload-isolation

    Cheers
    -Andrew

  14. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Krishna,

    Is it possible that you did not open up the inbound network access from the MongoDB Atlas Live Migration service to the secondary node that your cluster failed over to?

    -Andrew

  15. 130 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    27 comments  ·  Atlas » Backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Thirumalaisamy,

    We have some guidelines in the green box on this docs page that describe how to speed up a backup restore:
    https://docs.atlas.mongodb.com/backup/cloud-backup/restore/#restore-your-snapshot-to-an-atlas-cluster

    I am going to get this updated to be even more precise: For the fastest possible restore, restore to a cluster in the same Atlas Project, in the same region, with the exact same storage size as that of the cluster the Cloud Backup snapshot was taken from.

    If you do this, you will have the fastest possible restore (irrespective of data size) -- from there you can very easily remove any collections/databases you don't need.

    Cheers
    -Andrew

    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Thirumalaisamy,

    One option is to simply restore the full backup and then cull everything you don't need -- this can all be driven programmatically. Can you share whether this would work for you?

    Cheers
    -Andrew

  16. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Kyle,

    While we do not plan to introduce a greater than 72 hours heads up, you can always defer maintenance for a week up to two times. You can also select your preferred hour of the week for our heads up to go out 72 hours. If Monday is sub-optimal, why not move your window back int he week? This gives you the power to decide when the optimal time for you is.

    -Andrew

    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Kyle,

    Thanks for reaching out: importantly, Atlas maintenance is performed in a rolling manner and should only manifest as a replica-set level election from a client perspective. This means that an application with built-in retry logic (MongoDB offers retryable writes and retryable reads since 4.2) generally need not worry about maintenance.

    We have the "Test Failover" capability in the cluster's "..." menu in the Atlas UI for testing your resilience posture.

    We introduced maintenance windows so that our customers that are less election-tolerant could have more control into the preferred time the maintenance would occur. You should not need to schedule downtime with your end customers, and if maintenance is causing you downtime we would like to provide you assistance to ensure there isn't a driver bug at play.

    -Andrew

  17. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi AYMERIC,

    Being transparent with you, it would be a massive architectural change to contemplate something like this and as a result not something that is going to happen any time soon.

    However, slightly orthogonal but hopefully directionally helpful: we are looking at making it possible to use a smaller CIDR for the Atlas-side VPC at the Project-level on GCP in the future. The reason we use a wide CIDR on GCP is that GCP VPCs are global (an awesome feature) and we wanted to leave headroom for you to grow into any region over time. However in practice we realize there's a middle ground compromise here to be found.

    -Andrew

  18. 41 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Atlas » IAM  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Greg, Can you comment on whether the new Cross-Org Billing capability I mentioned earlier may suffice for your needs? It allows you to use multiple Organizations for different groups to isolate authorization but still share a billing subscription.

    Cheers
    -Andrew

    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Michael,

    We hear you loud and clear on needing to have more flexibility and have long term plans to do so.

    Importantly, we also just released a new capability for Atlas customers on annual subscriptions: Cross-Org Billing. With Cross-Org Billing you can link other Atlas Orgs to your "Paying Atlas Org" and have them pay through that subscription.

    One of the key drivers for creating this was to give customers more flexibility so that they can have authorization-level isolation across different Orgs, while maintaining a loose coupling for a shared Billing environment. By the way, you can move Projects between Orgs if you're an Org Owner of both orgs -- doing so is a no-downtime purely logical/mapping change. This might allow you to give folks their own Org and then from there they can set up their own Teams/Projects as they wish?

    More detail here: https://docs.atlas.mongodb.com/billing/#cross-organization-billing

    Cheers
    -Andrew

  19. 413 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  52 comments  ·  Atlas » IAM  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Greg,

    We do plan to enable a database user to be granted multiple custom roles in the future. This remains a number of quarters out, however. Apologies for the friction in the meantime. Note that this particular suggestion was originally scoped to the slightly orthogonal context of the MongoDB Cloud control plane users (e.g. instead of database users).

    Addressing Kico's original intent, note that annual subscription customers can now take advantage of Cross-Organization billing (see docs https://docs.atlas.mongodb.com/billing/#cross-organization-billing) which allows you to more easily use distinct Organizations for authorization-level isolation while maintaining a loose coupling for billing centralization. I think this will open up a degree of flexibility that was previously lacking in our control plane authorization experience.

    Nevertheless, we hear you loud and clear on wanting to be able to express finer grained control plane privileged actions and roles, and do plan to address this over the long term.

    Cheers
    -Andrew

    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Michael,

    Thanks for flagging all of issues: we definitely want to improve on all of them.

    You may want to take advantage of new functionality that we just launched for annual subscription customers: Cross-Org Billing. See https://docs.atlas.mongodb.com/billing/#cross-organization-billing for more information.

    With this capability you can move some Projects to other Organizations (this can be done without downtime via a purely logical backend move), giving you a loose-coupling with authorization-level isolation, but a shared billing subscription. Organization-scoped users can only see the billing usage associated with their respective Organization.

    Cheers
    -Andrew

  20. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    (I ask because in our upcoming MongoDB 4.4 we will have an exciting new capability coming to MongoDB Atlas that I think will be very compelling to you)

    An error occurred while saving the comment
    AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented  · 

    Hi Daniel,

    Can you clarify what you mean: are you looking to authenticate a Lambda function directly to a MongoDB Atlas cluster using AWS IAM for authentication?

    Cheers
    -Andrew

Feedback and Knowledge Base