turbot/mongodbatlas
steampipe plugin install mongodbatlas

Table: mongodbatlas_container - Query MongoDB Atlas Containers using SQL

MongoDB Atlas Containers are isolated environments that hold your data and are the base building blocks of MongoDB Atlas clusters. Containers are typically used to store data for a specific project or team. They provide isolation and security for your data, while also allowing for easy scalability and performance tuning.

Table Usage Guide

The mongodbatlas_container table provides insights into the containers within MongoDB Atlas. As a database administrator, you can explore container-specific details through this table, including its configuration, status, and associated metadata. Utilize it to uncover information about containers, such as their capacity, region, and current usage, aiding in efficient management and optimization of your MongoDB Atlas resources.

Examples

Basic info

Explore the provider's name and associated network block information in your MongoDB Atlas resources. This can help you manage and organize your resources more effectively.

select
id,
provider_name,
atlas_cidr_block
from
mongodbatlas_container;
select
id,
provider_name,
atlas_cidr_block
from
mongodbatlas_container;

List all peered containers in a specific cloud provider

Explore which containers in a specific cloud provider are peered. This is particularly useful for understanding your cloud network's configuration and identifying any potential security risks.

select
id,
provider_name,
atlas_cidr_block
from
mongodbatlas_container
where
provider_name = 'aws';
select
id,
provider_name,
atlas_cidr_block
from
mongodbatlas_container
where
provider_name = 'aws';

Schema for mongodbatlas_container

NameTypeOperatorsDescription
_ctxjsonbSteampipe context in JSON form, e.g. connection_name.
atlas_cidr_blockcidrCIDR block that Atlas uses for your clusters.
azure_subscription_idtextUnique identifer of the Azure subscription in which the VNet resides.
gcp_project_idtextUnique identifier of the Google Cloud project in which the network peer resides. Returns null until a peering connection is created.
idtext=Unique identifier for the container.
network_nametextUnique identifier of the Network Peering connection in the Atlas project. Returns null until a peering connection is created.
project_idtext=Unique identifier for the project.
provider_nametext=Cloud provider for this Network Peering connection.
provisionedbooleanFlag that indicates if the project has clusters deployed in the Network Peering container or Azure VNet.
regiontextAWS region where the VCP resides or Azure region where the VNet resides.
titletextTitle of the resource.
vnet_nametextUnique identifier of your Azure VNet. The value is null if there are no network peering connections in the container.
vpc_idtextUnique identifier of the project's Network Peering container.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- mongodbatlas

You can pass the configuration to the command with the --config argument:

steampipe_export_mongodbatlas --config '<your_config>' mongodbatlas_container