Awesome

This component is responsible for creating an administrative stack and its corresponding child stacks in the Spacelift organization.

The component uses a series of context_filters to select atmos component instances to manage as child stacks.

Usage

Stack Level: Global

The following are example snippets of how to use this component. For more on Spacelift admin stack usage, see the Spacelift README

First define the default configuration for any admin stack:

# stacks/catalog/spacelift/admin-stack.yaml
components:
  terraform:
    admin-stack/default:
      metadata:
        type: abstract
        component: spacelift/admin-stack
      settings:
        spacelift:
          administrative: true
          autodeploy: true
          before_apply:
            - spacelift-configure-paths
          before_init:
            - spacelift-configure-paths
            - spacelift-write-vars
            - spacelift-tf-workspace
          before_plan:
            - spacelift-configure-paths
          drift_detection_enabled: true
          drift_detection_reconcile: true
          drift_detection_schedule:
            - 0 4 * * *
          manage_state: false
          policies: {}
      vars:
        # Organization specific configuration
        branch: main
        repository: infrastructure
        worker_pool_name: "acme-core-ue1-auto-spacelift-worker-pool"
        runner_image: 111111111111.dkr.ecr.us-east-1.amazonaws.com/infrastructure:latest
        spacelift_spaces_stage_name: "root"
        # These values need to be manually updated as external configuration changes
        # This should match the version set in the Dockerfile and be updated when the version changes.
        terraform_version: "1.3.6"
        # Common configuration
        administrative: true # Whether this stack can manage other stacks
        component_root: components/terraform

Then define the root-admin stack:

# stacks/orgs/acme/spacelift.yaml
import:
  - mixins/region/global-region
  - orgs/acme/_defaults
  - catalog/terraform/spacelift/admin-stack
  - catalog/terraform/spacelift/spaces

# These intentionally overwrite the default values
vars:
  tenant: root
  environment: gbl
  stage: spacelift

components:
  terraform:
    # This admin stack creates other "admin" stacks
    admin-stack:
      metadata:
        component: spacelift/admin-stack
        inherits:
          - admin-stack/default
      settings:
        spacelift:
          root_administrative: true
          labels:
            - root-admin
            - admin
      vars:
        enabled: true
        root_admin_stack: true # This stack will be created in the root space and will create all the other admin stacks as children.
        context_filters: # context_filters determine which child stacks to manage with this admin stack
          administrative: true # This stack is managing all the other admin stacks
          root_administrative: false # We don't want this stack to also find itself in the config and add itself a second time
        labels:
          - admin
        # attachments only on the root stack
        root_stack_policy_attachments:
          - TRIGGER Global administrator
        # this creates policies for the children (admin) stacks
        child_policy_attachments:
          - TRIGGER Global administrator

Finally, define any tenant-specific stacks:

# stacks/orgs/acme/core/spacelift.yaml
import:
  - mixins/region/global-region
  - orgs/acme/core/_defaults
  - catalog/terraform/spacelift/admin-stack

vars:
  tenant: core
  environment: gbl
  stage: spacelift

components:
  terraform:
    admin-stack:
      metadata:
        component: spacelift/admin-stack
        inherits:
          - admin-stack/default
      settings:
        spacelift:
          labels: # Additional labels for this stack
            - admin-stack-name:core
      vars:
        enabled: true
        context_filters:
          tenants: ["core"]
        labels: # Additional labels added to all children
          - admin-stack-name:core # will be used to automatically create the `managed-by:stack-name` label
        child_policy_attachments:
          - TRIGGER Dependencies

Requirements

Name	Version
<a name="requirement_terraform"></a> terraform	>= 1.3
<a name="requirement_aws"></a> aws	>= 4.0
<a name="requirement_null"></a> null	>= 3.0
<a name="requirement_spacelift"></a> spacelift	>= 0.1.31
<a name="requirement_utils"></a> utils	>= 1.14.0

Providers

Name	Version
<a name="provider_null"></a> null	>= 3.0
<a name="provider_spacelift"></a> spacelift	>= 0.1.31

Modules

Name	Source	Version
<a name="module_all_admin_stacks_config"></a> all_admin_stacks_config	cloudposse/cloud-infrastructure-automation/spacelift//modules/spacelift-stacks-from-atmos-config	1.5.0
<a name="module_child_stack"></a> child_stack	cloudposse/cloud-infrastructure-automation/spacelift//modules/spacelift-stack	1.6.0
<a name="module_child_stacks_config"></a> child_stacks_config	cloudposse/cloud-infrastructure-automation/spacelift//modules/spacelift-stacks-from-atmos-config	1.5.0
<a name="module_root_admin_stack"></a> root_admin_stack	cloudposse/cloud-infrastructure-automation/spacelift//modules/spacelift-stack	1.6.0
<a name="module_root_admin_stack_config"></a> root_admin_stack_config	cloudposse/cloud-infrastructure-automation/spacelift//modules/spacelift-stacks-from-atmos-config	1.5.0
<a name="module_spaces"></a> spaces	cloudposse/stack-config/yaml//modules/remote-state	1.5.0
<a name="module_this"></a> this	cloudposse/label/null	0.25.0

Resources

Name	Type
null_resource.child_stack_parent_precondition	resource
null_resource.public_workers_precondition	resource
null_resource.spaces_precondition	resource
null_resource.workers_precondition	resource
spacelift_policy_attachment.root	resource
spacelift_policies.this	data source
spacelift_stacks.this	data source
spacelift_worker_pools.this	data source

Inputs

Name	Description	Type	Default	Required
<a name="input_additional_tag_map"></a> additional_tag_map	Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`.<br/>This is for some rare cases where resources want additional configuration of tags<br/>and therefore take a list of maps with tag key, value, and additional configuration.	`map(string)`	`{}`	no
<a name="input_admin_stack_label"></a> admin_stack_label	Label to use to identify the admin stack when creating the child stacks	`string`	`"admin-stack-name"`	no
<a name="input_allow_public_workers"></a> allow_public_workers	Whether to allow public workers to be used for this stack	`bool`	`false`	no
<a name="input_attributes"></a> attributes	ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`,<br/>in the order they appear in the list. New attributes are appended to the<br/>end of the list. The elements of the list are joined by the `delimiter`<br/>and treated as a single ID element.	`list(string)`	`[]`	no
<a name="input_autodeploy"></a> autodeploy	Controls the Spacelift 'autodeploy' option for a stack	`bool`	`false`	no
<a name="input_autoretry"></a> autoretry	Controls the Spacelift 'autoretry' option for a stack	`bool`	`false`	no
<a name="input_aws_role_arn"></a> aws_role_arn	ARN of the AWS IAM role to assume and put its temporary credentials in the runtime environment	`string`	`null`	no
<a name="input_aws_role_enabled"></a> aws_role_enabled	Flag to enable/disable Spacelift to use AWS STS to assume the supplied IAM role and put its temporary credentials in the runtime environment	`bool`	`false`	no
<a name="input_aws_role_external_id"></a> aws_role_external_id	Custom external ID (works only for private workers). See https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html for more details	`string`	`null`	no
<a name="input_aws_role_generate_credentials_in_worker"></a> aws_role_generate_credentials_in_worker	Flag to enable/disable generating AWS credentials in the private worker after assuming the supplied IAM role	`bool`	`true`	no
<a name="input_azure_devops"></a> azure_devops	Azure DevOps VCS settings	`map(any)`	`null`	no
<a name="input_bitbucket_cloud"></a> bitbucket_cloud	Bitbucket Cloud VCS settings	`map(any)`	`null`	no
<a name="input_bitbucket_datacenter"></a> bitbucket_datacenter	Bitbucket Datacenter VCS settings	`map(any)`	`null`	no
<a name="input_branch"></a> branch	Specify which branch to use within your infrastructure repo	`string`	`"main"`	no
<a name="input_child_policy_attachments"></a> child_policy_attachments	List of policy attachments to attach to the child stacks created by this module	`set(string)`	`[]`	no
<a name="input_cloudformation"></a> cloudformation	CloudFormation-specific configuration. Presence means this Stack is a CloudFormation Stack.	`map(any)`	`null`	no
<a name="input_commit_sha"></a> commit_sha	The commit SHA for which to trigger a run. Requires `var.spacelift_run_enabled` to be set to `true`	`string`	`null`	no
<a name="input_component_env"></a> component_env	Map of component ENV variables	`any`	`{}`	no
<a name="input_component_root"></a> component_root	The path, relative to the root of the repository, where the component can be found	`string`	n/a	yes
<a name="input_component_vars"></a> component_vars	All Terraform values to be applied to the stack via a mounted file	`any`	`{}`	no
<a name="input_context"></a> context	Single object for setting entire context at once.<br/>See description of individual variables for details.<br/>Leave string and numeric variables as `null` to use default value.<br/>Individual variable settings (non-null) override settings in context object,<br/>except for attributes, tags, and additional_tag_map, which are merged.	`any`	<pre>{<br/> "additional_tag_map": {},<br/> "attributes": [],<br/> "delimiter": null,<br/> "descriptor_formats": {},<br/> "enabled": true,<br/> "environment": null,<br/> "id_length_limit": null,<br/> "label_key_case": null,<br/> "label_order": [],<br/> "label_value_case": null,<br/> "labels_as_tags": [<br/> "unset"<br/> ],<br/> "name": null,<br/> "namespace": null,<br/> "regex_replace_chars": null,<br/> "stage": null,<br/> "tags": {},<br/> "tenant": null<br/>}</pre>	no
<a name="input_context_attachments"></a> context_attachments	A list of context IDs to attach to this stack	`list(string)`	`[]`	no
<a name="input_context_filters"></a> context_filters	Context filters to select atmos stacks matching specific criteria to create as children.	<pre>object({<br/> namespaces = optional(list(string), [])<br/> environments = optional(list(string), [])<br/> tenants = optional(list(string), [])<br/> stages = optional(list(string), [])<br/> tags = optional(map(string), {})<br/> administrative = optional(bool)<br/> root_administrative = optional(bool)<br/> })</pre>	n/a	yes
<a name="input_delimiter"></a> delimiter	Delimiter to be used between ID elements.<br/>Defaults to `-` (hyphen). Set to `""` to use no delimiter at all.	`string`	`null`	no
<a name="input_description"></a> description	Specify description of stack	`string`	`null`	no
<a name="input_descriptor_formats"></a> descriptor_formats	Describe additional descriptors to be output in the `descriptors` output map.<br/>Map of maps. Keys are names of descriptors. Values are maps of the form<br/>`{<br/> format = string<br/> labels = list(string)<br/>}`<br/>(Type is `any` so the map values can later be enhanced to provide additional options.)<br/>`format` is a Terraform format string to be passed to the `format()` function.<br/>`labels` is a list of labels, in order, to pass to `format()` function.<br/>Label values will be normalized before being passed to `format()` so they will be<br/>identical to how they appear in `id`.<br/>Default is `{}` (`descriptors` output will be empty).	`any`	`{}`	no
<a name="input_drift_detection_enabled"></a> drift_detection_enabled	Flag to enable/disable drift detection on the infrastructure stacks	`bool`	`false`	no
<a name="input_drift_detection_reconcile"></a> drift_detection_reconcile	Flag to enable/disable infrastructure stacks drift automatic reconciliation. If drift is detected and `reconcile` is turned on, Spacelift will create a tracked run to correct the drift	`bool`	`false`	no
<a name="input_drift_detection_schedule"></a> drift_detection_schedule	List of cron expressions to schedule drift detection for the infrastructure stacks	`list(string)`	<pre>[<br/> "0 4 * * *"<br/>]</pre>	no
<a name="input_drift_detection_timezone"></a> drift_detection_timezone	Timezone in which the schedule is expressed. Defaults to UTC.	`string`	`null`	no
<a name="input_enabled"></a> enabled	Set to false to prevent the module from creating any resources	`bool`	`null`	no
<a name="input_environment"></a> environment	ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'	`string`	`null`	no
<a name="input_excluded_context_filters"></a> excluded_context_filters	Context filters to exclude from stacks matching specific criteria of `var.context_filters`.	<pre>object({<br/> namespaces = optional(list(string), [])<br/> environments = optional(list(string), [])<br/> tenants = optional(list(string), [])<br/> stages = optional(list(string), [])<br/> tags = optional(map(string), {})<br/> })</pre>	`{}`	no
<a name="input_github_enterprise"></a> github_enterprise	GitHub Enterprise (self-hosted) VCS settings	`map(any)`	`null`	no
<a name="input_gitlab"></a> gitlab	GitLab VCS settings	`map(any)`	`null`	no
<a name="input_id_length_limit"></a> id_length_limit	Limit `id` to this many characters (minimum 6).<br/>Set to `0` for unlimited length.<br/>Set to `null` for keep the existing setting, which defaults to `0`.<br/>Does not affect `id_full`.	`number`	`null`	no
<a name="input_label_key_case"></a> label_key_case	Controls the letter case of the `tags` keys (label names) for tags generated by this module.<br/>Does not affect keys of tags passed in via the `tags` input.<br/>Possible values: `lower`, `title`, `upper`.<br/>Default value: `title`.	`string`	`null`	no
<a name="input_label_order"></a> label_order	The order in which the labels (ID elements) appear in the `id`.<br/>Defaults to ["namespace", "environment", "stage", "name", "attributes"].<br/>You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.	`list(string)`	`null`	no
<a name="input_label_value_case"></a> label_value_case	Controls the letter case of ID elements (labels) as included in `id`,<br/>set as tag values, and output by this module individually.<br/>Does not affect values of tags passed in via the `tags` input.<br/>Possible values: `lower`, `title`, `upper` and `none` (no transformation).<br/>Set this to `title` and set `delimiter` to `""` to yield Pascal Case IDs.<br/>Default value: `lower`.	`string`	`null`	no
<a name="input_labels"></a> labels	A list of labels for the stack	`list(string)`	`[]`	no
<a name="input_labels_as_tags"></a> labels_as_tags	Set of labels (ID elements) to include as tags in the `tags` output.<br/>Default is to include all labels.<br/>Tags with empty values will not be included in the `tags` output.<br/>Set to `[]` to suppress all generated tags.<br/>Notes:<br/> The value of the `name` tag, if included, will be the `id`, not the `name`.<br/> Unlike other `null-label` inputs, the initial setting of `labels_as_tags` cannot be<br/> changed in later chained modules. Attempts to change it will be silently ignored.	`set(string)`	<pre>[<br/> "default"<br/>]</pre>	no
<a name="input_local_preview_enabled"></a> local_preview_enabled	Indicates whether local preview runs can be triggered on this Stack	`bool`	`false`	no
<a name="input_manage_state"></a> manage_state	Flag to enable/disable manage_state setting in stack	`bool`	`false`	no
<a name="input_name"></a> name	ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.<br/>This is the only ID element not also included as a `tag`.<br/>The "name" tag is set to the full `id` string. There is no tag with the value of the `name` input.	`string`	`null`	no
<a name="input_namespace"></a> namespace	ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique	`string`	`null`	no
<a name="input_protect_from_deletion"></a> protect_from_deletion	Flag to enable/disable deletion protection.	`bool`	`false`	no
<a name="input_pulumi"></a> pulumi	Pulumi-specific configuration. Presence means this Stack is a Pulumi Stack.	`map(any)`	`null`	no
<a name="input_regex_replace_chars"></a> regex_replace_chars	Terraform regular expression (regex) string.<br/>Characters matching the regex will be removed from the ID elements.<br/>If not set, `"/[^a-zA-Z0-9-]/"` is used to remove all characters other than hyphens, letters and digits.	`string`	`null`	no
<a name="input_repository"></a> repository	The name of your infrastructure repo	`string`	n/a	yes
<a name="input_root_admin_stack"></a> root_admin_stack	Flag to indicate if this stack is the root admin stack. In this case, the stack will be created in the root space and will create all the other admin stacks as children.	`bool`	`false`	no
<a name="input_root_stack_policy_attachments"></a> root_stack_policy_attachments	List of policy attachments to attach to the root admin stack	`set(string)`	`[]`	no
<a name="input_runner_image"></a> runner_image	The full image name and tag of the Docker image to use in Spacelift	`string`	`null`	no
<a name="input_showcase"></a> showcase	Showcase settings	`map(any)`	`null`	no
<a name="input_space_id"></a> space_id	Place the stack in the specified space_id	`string`	`"root"`	no
<a name="input_spacelift_run_enabled"></a> spacelift_run_enabled	Enable/disable creation of the `spacelift_run` resource	`bool`	`false`	no
<a name="input_spacelift_spaces_component_name"></a> spacelift_spaces_component_name	The component name of the spacelift spaces component	`string`	`"spacelift/spaces"`	no
<a name="input_spacelift_spaces_environment_name"></a> spacelift_spaces_environment_name	The environment name of the spacelift spaces component	`string`	`null`	no
<a name="input_spacelift_spaces_stage_name"></a> spacelift_spaces_stage_name	The stage name of the spacelift spaces component	`string`	`null`	no
<a name="input_spacelift_spaces_tenant_name"></a> spacelift_spaces_tenant_name	The tenant name of the spacelift spaces component	`string`	`null`	no
<a name="input_spacelift_stack_dependency_enabled"></a> spacelift_stack_dependency_enabled	If enabled, the `spacelift_stack_dependency` Spacelift resource will be used to create dependencies between stacks instead of using the `depends-on` labels. The `depends-on` labels will be removed from the stacks and the trigger policies for dependencies will be detached	`bool`	`false`	no
<a name="input_stack_destructor_enabled"></a> stack_destructor_enabled	Flag to enable/disable the stack destructor to destroy the resources of the stack before deleting the stack itself	`bool`	`false`	no
<a name="input_stack_name"></a> stack_name	The name of the Spacelift stack	`string`	`null`	no
<a name="input_stage"></a> stage	ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'	`string`	`null`	no
<a name="input_tags"></a> tags	Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`).<br/>Neither the tag keys nor the tag values will be modified by this module.	`map(string)`	`{}`	no
<a name="input_tenant"></a> tenant	ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for	`string`	`null`	no
<a name="input_terraform_smart_sanitization"></a> terraform_smart_sanitization	Whether or not to enable Smart Sanitization which will only sanitize values marked as sensitive.	`bool`	`false`	no
<a name="input_terraform_version"></a> terraform_version	Specify the version of Terraform to use for the stack	`string`	`null`	no
<a name="input_terraform_version_map"></a> terraform_version_map	A map to determine which Terraform patch version to use for each minor version	`map(string)`	`{}`	no
<a name="input_terraform_workflow_tool"></a> terraform_workflow_tool	Defines the tool that will be used to execute the workflow. This can be one of OPEN_TOFU, TERRAFORM_FOSS or CUSTOM. Defaults to TERRAFORM_FOSS.	`string`	`"TERRAFORM_FOSS"`	no
<a name="input_terraform_workspace"></a> terraform_workspace	Specify the Terraform workspace to use for the stack	`string`	`null`	no
<a name="input_webhook_enabled"></a> webhook_enabled	Flag to enable/disable the webhook endpoint to which Spacelift sends the POST requests about run state changes	`bool`	`false`	no
<a name="input_webhook_endpoint"></a> webhook_endpoint	Webhook endpoint to which Spacelift sends the POST requests about run state changes	`string`	`null`	no
<a name="input_webhook_secret"></a> webhook_secret	Webhook secret used to sign each POST request so you're able to verify that the requests come from Spacelift	`string`	`null`	no
<a name="input_worker_pool_name"></a> worker_pool_name	The atmos stack name of the worker pool. Example: `acme-core-ue2-auto-spacelift-default-worker-pool`	`string`	`null`	no

Outputs

Name	Description
<a name="output_child_stacks"></a> child_stacks	All children stacks managed by this component
<a name="output_root_stack"></a> root_stack	The root stack, if enabled and created by this component
<a name="output_root_stack_id"></a> root_stack_id	The stack id

[!TIP]

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform. Works with Github Actions, Atlantis, or Spacelift.
<details> <summary>Watch demo of using Atmos with Terraform</summary> <img src="https://github.com/cloudposse/atmos/blob/main/docs/demo.gif?raw=true"/> Example of running <a href="https://atmos.tools"><code>atmos</code></a> to manage infrastructure from our <a href="https://atmos.tools/quick-start/">Quick Start</a> tutorial. </detalis>

Related Projects

Check out these related projects.

Cloud Posse Terraform Modules - Our collection of reusable Terraform modules used by our reference architectures.
Atmos - Atmos is like docker-compose but for your infrastructure

[!TIP]

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team. ✅ Your team owns everything. ✅ 100% Open Source and backed by fanatical support. 

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-spacelift-admin-stack&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>
<details><summary>📚 Learn More</summary> 
Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.

Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.

Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.

Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.

GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-spacelift-admin-stack&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>

Day-2: Your Operational Mastery

Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.

Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.

Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.

Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.

Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.

Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.

Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-spacelift-admin-stack&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>
</details>

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

Review our Code of Conduct and Contributor Guidelines.
Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours <a href="https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-spacelift-admin-stack&utm_content=office_hours"><img src="https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png" align="right" /></a>

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

<details> <summary>Preamble to the Apache License, Version 2.0</summary>

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

</details>

Trademarks

All other trademarks referenced herein are the property of their respective owners.