Skip to content

Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

8 results found

  1. Support migration of existing projects, clusters, ... to be CloudFormation managed

    When MongoDB::Atlas::* resources are created and the specifed project, cluster, ... already exists, then these resources should not raise an error on resource creation but use the existing project, cluster, ... and apply the given configuration. In other words, the Create event that is initially sent by CloudFormation should be handled similar to an Update event but return the physical id of already existing resources. Apparently, this behaviour should be enabled by an opt-in flag.

    3 votes
    How important is this to you?
  2. Accept VPC peering connection when created by MongoDB::Atlas::NetworkPeering

    VPC peering connection created by CloudFormation resource MongoDB::Atlas::NetworkPeering have to accepted in AWS, using GUI, CLI etc. Would that be possible to get this done using CF only?

    2 votes
    How important is this to you?
  3. ชุมชน

    ทรัพยากร

    1 vote
    How important is this to you?
  4. ServerlessPrivateEndpoint should allow the consumer to specify a security group

    Currently, the AwsPrivateEndpointConfigurationProperties object allows the consumer to specify a VpcId and SubnetIds, but it does not allow us to specify a custom Security Group into which the AWS-side VPC Private Endpoint should be added.

    The ServerlessPrivateEndpoint custom resource also does not create a security group for the endpoint, instead just dumping it into the default security group for the VPC. I can see no way to customize this behavior.

    1 vote
    How important is this to you?
  5. Support for CDK SAM Template in Publishing Serverless Applications in AWS

    I suggest that AWS supports CDK SAM Template for publishing serverless applications. Currently, when attempting to publish a serverless application using a SAM template that includes MongoDB Atlas CloudFormation extensions, such as MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList, an error is encountered.

    Error Message:

    Error: SAM template is invalid. It cannot be deployed using AWS CloudFormation due to the following validation error: Template format error: Unrecognized resource types: [MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList]

    While deployments proceed smoothly, this error arises when attempting to publish the serverless application. It would be beneficial if AWS supports CDK SAM Template for publishing serverless applications, allowing for…

    1 vote
    How important is this to you?
  6. CDK L3 Resource for Atlas Streams Resource

    Would help my organization get started faster with Atlas Streams Processing

    1 vote
    How important is this to you?
  7. Specify allowed values for fields in AWS CDK

    Example create database user:

    It would be nice to get IntelliSense in IDEs for fields which are enums behind the scenes.

    Alternatively, allowed values should be included in error messages. That would make debugging at runtime easier at least.

    1 vote
    How important is this to you?
  8. Change write concern on the Atlas Clusters

    Atlas does not currently allow to change the default write concern at the cluster level.

    It it necessary to have a possibility to change it in order to avoid or minimize rollbackfiles during failover.

    1 vote
    How important is this to you?
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base