@@ -17,17 +17,19 @@ Automation
17
17
.. contents:: On this page
18
18
:local:
19
19
:backlinks: none
20
- :depth: 2
20
+ :depth: 3
21
21
:class: onecol
22
22
23
23
|service-fullname| provides an easy way to host and manage your data in
24
- the cloud. It includes tools that automate the deployment, scaling, and
25
- maintenance of your {+service+} {+clusters+} to streamline operations,
26
- reduce manual interventions, and ensure consistent, policy-compliant
27
- deployments. These tools offer you the flexibility to work with
28
- |service| through direct scripting (such as scripts that call the
29
- {+atlas-admin-api+}), a Kubernetes-native workflow, or
30
- using Infrastructure as Code (IaC) tools like Terraform.
24
+ the cloud. It includes tools that enable programmatic management of the
25
+ deployment, scaling, and maintenance of your {+service+} {+clusters+} to
26
+ streamline operations, reduce manual interventions, and ensure
27
+ consistent, policy-compliant deployments. These tools offer you the
28
+ flexibility to work with {+service+} through direct scripting (such as
29
+ scripts that use the GoSDK Client or call the {+atlas-admin-api+}
30
+ directly), or Infrastructure as Code (IaC) tooling that uses declarative
31
+ configuration, like our Kubernetes Operator, Terraform, Cloud Formation
32
+ or AWS CDK.
31
33
32
34
{+service+} Features and Recommendations for Automation
33
35
-------------------------------------------------------
@@ -38,8 +40,7 @@ Features
38
40
You can automate the management, provisioning, and configuration of
39
41
|service| building blocks like database users and roles, |service|
40
42
{+clusters+}, projects and organizations. Additionally, you can automate
41
- temporary access list entries that expire after a user-defined period, and
42
- setting up and managing of additional {+clusters+} resources, including
43
+ setting up and managing additional {+clusters+} resources, including
43
44
enabling auto-scaling compute and storage, creating and updating
44
45
multi-cloud {+clusters+}, monitoring {+cluster+} performance and health,
45
46
automating backups and restores, defining backup policies, and many more.
@@ -74,14 +75,8 @@ To learn more, see :ref:`Atlas Go SDK <atlas-admin-sdk>`.
74
75
75
76
.. _arch-center-iac:
76
77
77
- Infrastructure as Code (IaC) Integrations
78
- `````````````````````````````````````````
79
-
80
- The integrations with the following :abbr:`IaC (Infrastructure as Code)`
81
- tools automate the deployment of |service| resources.
82
-
83
78
HashiCorp Terraform MongoDB Atlas Provider
84
- ##########################################
79
+ ``````````````````````````````````````````
85
80
86
81
Provisions |service| resources across cloud providers (|aws|, |azure|,
87
82
|gcp|) in the workflow of your choice. It allows you to integrate
@@ -98,7 +93,7 @@ To learn more, see :ref:`getting-started-terraform` and the
98
93
Cluster<arch-center-hierarchy>` examples to get started.
99
94
100
95
CloudFormation Resources
101
- ########################
96
+ ````````````````````````
102
97
103
98
Resources to manage |service| include:
104
99
@@ -115,8 +110,8 @@ To learn more, see `Deploy MongoDB Atlas with AWS CloudFormation <https://www.mo
115
110
{+atlas-cli+}
116
111
`````````````
117
112
118
- Enables you to create, manage, and automate tasks related to |service|
119
- resources from a unified command line tool.
113
+ Enables you to manually or programmatically create, manage, and automate
114
+ tasks related to |service| resources from a unified command line tool.
120
115
121
116
To learn more, see the following resources:
122
117
@@ -144,18 +139,21 @@ Recommendations
144
139
If you already have an existing tool integrated into your deployment
145
140
workflow that you use today, we recommend that you use that tool for
146
141
automation. For example, if your developers and operations team are
147
- used to building custom resource definitions for Kubernetes for
148
- deployment, use the |ak8so| and Kubernetes for automation in
149
- {+service+}.
150
-
151
- If you don't already have an existing tool integrated into your development workflow, we recommend an :ref:`IaC tool <arch-center-iac>`
152
- because they provide more robust options for infrastructure provisioning and state management.
153
- If you instead call the {+atlas-admin-api+} directly or use the GoSDK, which wraps the {+atlas-admin-api+}, you might need to recreate your
154
- infrastructure provisioning each time to match your needs across
155
- environments.
142
+ already deploying to Kubernetes, apply {+service+} configurations through
143
+ the same tooling and pipelines and use the |ak8so| to automate updating
144
+ {+service+}.
145
+
146
+ If you don't already have an existing tool integrated into your
147
+ development workflow, we recommend an :ref:`IaC tool <arch-center-iac>`
148
+ because they provide more robust options for infrastructure provisioning
149
+ and state management. If you instead call the {+atlas-admin-api+}
150
+ directly or use the GoSDK, which wraps the {+atlas-admin-api+}, you
151
+ might need to recreate your infrastructure provisioning each time to
152
+ match your needs across environments.
156
153
157
154
You can also use a combination of multiple tools. For example, use IaC
158
- tool for provisioning and state management, and leverage the {+atlas-admin-api+}, GoSDK, and {+atlas-cli+} for quick administrative
155
+ tool for provisioning and state management, and leverage the
156
+ {+atlas-admin-api+}, GoSDK, and {+atlas-cli+} for quick administrative
159
157
tasks that are ephemeral in nature. The {+atlas-cli+} is great for
160
158
local development as well as integration into a suite of tests as part
161
159
of your CI/CD pipeline for application development because it improves
0 commit comments