Awesome

This component provisions the WorkerPool part of the Kubernetes Operator for Spacelift Worker Pools into an EKS cluster. You can provision this component multiple times to create multiple worker pools in a single EKS cluster.

Usage

[!NOTE]

Before provisioning the eks/spacelift-worker-pool component, the eks/spacelift-worker-pool-controller component must be provisioned first into an EKS cluster to enable the Spacelift Worker Pool Kubernetes Controller. The eks/spacelift-worker-pool-controller component must be provisioned only once per EKS cluster.

The Spacelift worker needs to pull a Docker image from an ECR repository. It will run the Terraform commands inside the Docker container. In the Cloud Posse reference architecture, this image is the "infra" or "infrastructure" image derived from Geodesic. The worker service account needs permission to pull the image from the ECR repository, and the details of where to find the image are configured in the various ecr_* variables.

Stack Level: Regional

# stacks/catalog/eks/spacelift-worker-pool/defaults.yaml
components:
  terraform:
    eks/spacelift-worker-pool:
      enabled: true
      name: "spacelift-worker-pool"
      space_name: root
      # aws_config_file is the path in the Docker container to the AWS_CONFIG_FILE.
      # "/etc/aws-config/aws-config-spacelift" is the usual path in the "infrastructure" image.
      aws_config_file: "/etc/aws-config/aws-config-spacelift"
      spacelift_api_endpoint: "https://yourcompany.app.spacelift.io"
      eks_component_name: "eks/cluster"
      worker_pool_size: 40
      kubernetes_namespace: "spacelift-worker-pool"
      kubernetes_service_account_enabled: true
      kubernetes_service_account_name: "spacelift-worker-pool"
      keep_successful_pods: false
      kubernetes_role_api_groups: [""]
      kubernetes_role_resources: ["*"]
      kubernetes_role_resource_names: null
      kubernetes_role_verbs: ["get", "list"]
      ecr_component_name: ecr
      ecr_environment_name: use1
      ecr_stage_name: artifacts
      ecr_tenant_name: core
      ecr_repo_name: infra

References

Requirements

Name	Version
<a name="requirement_terraform"></a> terraform	>= 1.3.0
<a name="requirement_aws"></a> aws	>= 4.9.0
<a name="requirement_helm"></a> helm	>= 2.0
<a name="requirement_kubernetes"></a> kubernetes	>= 2.18.1, != 2.21.0
<a name="requirement_spacelift"></a> spacelift	>= 0.1.2

Providers

Name	Version
<a name="provider_aws"></a> aws	>= 4.9.0
<a name="provider_kubernetes"></a> kubernetes	>= 2.18.1, != 2.21.0
<a name="provider_spacelift"></a> spacelift	>= 0.1.2

Modules

Name	Source	Version
<a name="module_account_map"></a> account_map	cloudposse/stack-config/yaml//modules/remote-state	1.8.0
<a name="module_ecr"></a> ecr	cloudposse/stack-config/yaml//modules/remote-state	1.8.0
<a name="module_eks"></a> eks	cloudposse/stack-config/yaml//modules/remote-state	1.8.0
<a name="module_eks_iam_policy"></a> eks_iam_policy	cloudposse/iam-policy/aws	2.0.1
<a name="module_eks_iam_role"></a> eks_iam_role	cloudposse/eks-iam-role/aws	2.1.1
<a name="module_iam_roles"></a> iam_roles	../../account-map/modules/iam-roles	n/a
<a name="module_this"></a> this	cloudposse/label/null	0.25.0

Resources

Name	Type
kubernetes_manifest.spacelift_worker_pool	resource
kubernetes_role_binding_v1.default	resource
kubernetes_role_v1.default	resource
kubernetes_secret.default	resource
kubernetes_service_account_v1.default	resource
spacelift_worker_pool.default	resource
aws_eks_cluster_auth.eks	data source
aws_partition.current	data source
aws_ssm_parameter.spacelift_key_id	data source
aws_ssm_parameter.spacelift_key_secret	data source
spacelift_spaces.default	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_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_aws_config_file"></a> aws_config_file	The AWS_CONFIG_FILE used by the worker. Can be overridden by `/.spacelift/config.yml`.	`string`	n/a	yes
<a name="input_aws_profile"></a> aws_profile	The AWS_PROFILE used by the worker. If not specified, `"${var.namespace}-identity"` will be used.<br/>Can be overridden by `/.spacelift/config.yml`.	`string`	`null`	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_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_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_ecr_component_name"></a> ecr_component_name	ECR component name	`string`	`"ecr"`	no
<a name="input_ecr_environment_name"></a> ecr_environment_name	The name of the environment where `ecr` is provisioned	`string`	`""`	no
<a name="input_ecr_repo_name"></a> ecr_repo_name	ECR repository name	`string`	n/a	yes
<a name="input_ecr_stage_name"></a> ecr_stage_name	The name of the stage where `ecr` is provisioned	`string`	`"artifacts"`	no
<a name="input_ecr_tenant_name"></a> ecr_tenant_name	The name of the tenant where `ecr` is provisioned.<br/><br/>If the `tenant` label is not used, leave this as `null`.	`string`	`null`	no
<a name="input_eks_component_name"></a> eks_component_name	The name of the eks component	`string`	`"eks/cluster"`	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_grpc_server_resources"></a> grpc_server_resources	Resources for the gRPC server part of the worker pool deployment. The default values are usually sufficient.	<pre>object({<br/> requests = optional(object({<br/> memory = optional(string, "50Mi")<br/> cpu = optional(string, "50m")<br/> }), {})<br/> limits = optional(object({<br/> memory = optional(string, "500Mi")<br/> cpu = optional(string, "500m")<br/> }), {})<br/> })</pre>	`{}`	no
<a name="input_helm_manifest_experiment_enabled"></a> helm_manifest_experiment_enabled	Enable storing of the rendered manifest for helm_release so the full diff of what is changing can been seen in the plan	`bool`	`false`	no
<a name="input_iam_attributes"></a> iam_attributes	Additional attributes to add to the IDs of the IAM role and policy	`list(string)`	`[]`	no
<a name="input_iam_override_policy_documents"></a> iam_override_policy_documents	List of IAM policy documents that are merged together into the exported document with higher precedence.<br/>In merging, statements with non-blank SIDs will override statements with the same SID<br/>from earlier documents in the list and from other "source" documents.	`list(string)`	`null`	no
<a name="input_iam_permissions_boundary"></a> iam_permissions_boundary	ARN of the policy that is used to set the permissions boundary for the IAM Role	`string`	`null`	no
<a name="input_iam_source_json_url"></a> iam_source_json_url	IAM source JSON policy to download	`string`	`null`	no
<a name="input_iam_source_policy_documents"></a> iam_source_policy_documents	List of IAM policy documents that are merged together into the exported document.<br/>Statements defined in `iam_source_policy_documents` must have unique SIDs.<br/>Statements with the same SID as in statements in documents assigned to the<br/>`iam_override_policy_documents` arguments will be overridden.	`list(string)`	`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_keep_successful_pods"></a> keep_successful_pods	Indicates whether run Pods should automatically be removed as soon<br/>as they complete successfully, or be kept so that they can be inspected later. By default<br/>run Pods are removed as soon as they complete successfully. Failed Pods are not automatically<br/>removed to allow debugging.	`bool`	`false`	no
<a name="input_kube_data_auth_enabled"></a> kube_data_auth_enabled	If `true`, use an `aws_eks_cluster_auth` data source to authenticate to the EKS cluster.<br/>Disabled by `kubeconfig_file_enabled` or `kube_exec_auth_enabled`.	`bool`	`false`	no
<a name="input_kube_exec_auth_aws_profile"></a> kube_exec_auth_aws_profile	The AWS config profile for `aws eks get-token` to use	`string`	`""`	no
<a name="input_kube_exec_auth_aws_profile_enabled"></a> kube_exec_auth_aws_profile_enabled	If `true`, pass `kube_exec_auth_aws_profile` as the `profile` to `aws eks get-token`	`bool`	`false`	no
<a name="input_kube_exec_auth_enabled"></a> kube_exec_auth_enabled	If `true`, use the Kubernetes provider `exec` feature to execute `aws eks get-token` to authenticate to the EKS cluster.<br/>Disabled by `kubeconfig_file_enabled`, overrides `kube_data_auth_enabled`.	`bool`	`true`	no
<a name="input_kube_exec_auth_role_arn"></a> kube_exec_auth_role_arn	The role ARN for `aws eks get-token` to use	`string`	`""`	no
<a name="input_kube_exec_auth_role_arn_enabled"></a> kube_exec_auth_role_arn_enabled	If `true`, pass `kube_exec_auth_role_arn` as the role ARN to `aws eks get-token`	`bool`	`true`	no
<a name="input_kubeconfig_context"></a> kubeconfig_context	Context to choose from the Kubernetes config file.<br/>If supplied, `kubeconfig_context_format` will be ignored.	`string`	`""`	no
<a name="input_kubeconfig_context_format"></a> kubeconfig_context_format	A format string to use for creating the `kubectl` context name when<br/>`kubeconfig_file_enabled` is `true` and `kubeconfig_context` is not supplied.<br/>Must include a single `%s` which will be replaced with the cluster name.	`string`	`""`	no
<a name="input_kubeconfig_exec_auth_api_version"></a> kubeconfig_exec_auth_api_version	The Kubernetes API version of the credentials returned by the `exec` auth plugin	`string`	`"client.authentication.k8s.io/v1beta1"`	no
<a name="input_kubeconfig_file"></a> kubeconfig_file	The Kubernetes provider `config_path` setting to use when `kubeconfig_file_enabled` is `true`	`string`	`""`	no
<a name="input_kubeconfig_file_enabled"></a> kubeconfig_file_enabled	If `true`, configure the Kubernetes provider with `kubeconfig_file` and use that kubeconfig file for authenticating to the EKS cluster	`bool`	`false`	no
<a name="input_kubernetes_namespace"></a> kubernetes_namespace	Name of the Kubernetes Namespace the Spacelift worker pool is deployed in to	`string`	n/a	yes
<a name="input_kubernetes_role_api_groups"></a> kubernetes_role_api_groups	List of APIGroups for the Kubernetes Role created for the Kubernetes Service Account	`list(string)`	<pre>[<br/> ""<br/>]</pre>	no
<a name="input_kubernetes_role_resource_names"></a> kubernetes_role_resource_names	List of resource names for the Kubernetes Role created for the Kubernetes Service Account	`list(string)`	`null`	no
<a name="input_kubernetes_role_resources"></a> kubernetes_role_resources	List of resources for the Kubernetes Role created for the Kubernetes Service Account	`list(string)`	<pre>[<br/> "*"<br/>]</pre>	no
<a name="input_kubernetes_role_verbs"></a> kubernetes_role_verbs	List of verbs that apply to ALL the ResourceKinds for the Kubernetes Role created for the Kubernetes Service Account	`list(string)`	<pre>[<br/> "get",<br/> "list"<br/>]</pre>	no
<a name="input_kubernetes_service_account_enabled"></a> kubernetes_service_account_enabled	Flag to enable/disable Kubernetes service account	`bool`	`false`	no
<a name="input_kubernetes_service_account_name"></a> kubernetes_service_account_name	Kubernetes service account name	`string`	`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_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_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_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_region"></a> region	AWS Region	`string`	n/a	yes
<a name="input_space_name"></a> space_name	The name of the Spacelift Space to create the worker pool in	`string`	`"root"`	no
<a name="input_spacelift_api_endpoint"></a> spacelift_api_endpoint	The Spacelift API endpoint URL (e.g. https://example.app.spacelift.io)	`string`	n/a	yes
<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_worker_pool_description"></a> worker_pool_description	Spacelift worker pool description. The default dynamically includes EKS cluster ID and Spacelift Space name.	`string`	`null`	no
<a name="input_worker_pool_size"></a> worker_pool_size	Worker pool size. The number of workers registered with Spacelift.	`number`	`1`	no
<a name="input_worker_spec"></a> worker_spec	Configuration for the Workers in the worker pool	<pre>object({<br/> tmpfs_enabled = optional(bool, false)<br/> resources = optional(object({<br/> limits = optional(object({<br/> cpu = optional(string, "1")<br/> memory = optional(string, "4500Mi")<br/> ephemeral-storage = optional(string, "2G")<br/> }), {})<br/> requests = optional(object({<br/> cpu = optional(string, "750m")<br/> memory = optional(string, "4Gi")<br/> ephemeral-storage = optional(string, "1G")<br/> }), {})<br/> }), {})<br/> annotations = optional(map(string), {})<br/> node_selector = optional(map(string), {})<br/> tolerations = optional(list(object({<br/> key = optional(string)<br/> operator = optional(string)<br/> value = optional(string)<br/> effect = optional(string)<br/> toleration_seconds = optional(number)<br/> })), [])<br/> # activeDeadlineSeconds defines the length of time in seconds before which the Pod will<br/> # be marked as failed. This can be used to set a time limit for your runs.<br/> active_deadline_seconds = optional(number, 4200) # 4200 seconds = 70 minutes<br/> termination_grace_period_seconds = optional(number, 50)<br/> })</pre>	`{}`	no

Outputs

Name	Description
<a name="output_service_account_name"></a> service_account_name	Kubernetes Service Account name
<a name="output_service_account_namespace"></a> service_account_namespace	Kubernetes Service Account namespace
<a name="output_service_account_policy_arn"></a> service_account_policy_arn	IAM policy ARN
<a name="output_service_account_policy_id"></a> service_account_policy_id	IAM policy ID
<a name="output_service_account_policy_name"></a> service_account_policy_name	IAM policy name
<a name="output_service_account_role_arn"></a> service_account_role_arn	IAM role ARN
<a name="output_service_account_role_name"></a> service_account_role_name	IAM role name
<a name="output_service_account_role_unique_id"></a> service_account_role_unique_id	IAM role unique ID
<a name="output_spacelift_worker_pool_manifest"></a> spacelift_worker_pool_manifest	Spacelift worker pool Kubernetes manifest
<a name="output_worker_pool_id"></a> worker_pool_id	Spacelift worker pool ID
<a name="output_worker_pool_name"></a> worker_pool_name	Spacelift worker pool name

[!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-eks-spacelift-worker-pool&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-eks-spacelift-worker-pool&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-eks-spacelift-worker-pool&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-eks-spacelift-worker-pool&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.