- Monitor Your Deployments >
- Configure and Resolve Alerts >
- Resolve Alerts >
- Fix Exposed Host
Fix Exposed Host¶
On this page
The MongoDB instance running on host X
in rsY
is exposed to the
public Internet.
Alert Conditions¶
You can configure alert conditions in the project-level alert settings page to trigger alerts.
To learn more about the alert condition, see Host is exposed to the public Internet.
Common Triggers¶
- The mongod or mongos process was reached because it is not behind a firewall and does not have authentication enabled.
Fix the Immediate Problem¶
Install and configure a firewall between the public Internet and your MongoDB instance.
To review which ports need to be available to your Cloud Manager deployment, see Firewall Configuration.
Enable authentication for the instance. You can choose from the following options:
Implement a Long-Term Solution¶
mongod or mongos process behind a firewall and enable authentication.
Monitor Your Progress¶
View the following chart to monitor your progress:
Connections
Monitor connections to determine whether the current connection limits are sufficient.
To learn more, see View Deployment Metrics.