AWS Amazon SageMaker Studio Lifecycle Config

This page shows how to write Terraform for Amazon SageMaker Studio Lifecycle Config and write them securely.

aws_sagemaker_studio_lifecycle_config (Terraform)

The Studio Lifecycle Config in Amazon SageMaker can be configured in Terraform with the resource name aws_sagemaker_studio_lifecycle_config. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Review your Terraform file for AWS best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).


The following arguments are supported:

  • studio_lifecycle_config_name - (Required) The name of the Studio Lifecycle Configuration to create.
  • studio_lifecycle_config_app_type - (Required) The App type that the Lifecycle Configuration is attached to. Valid values are JupyterServer and KernelGateway.
  • studio_lifecycle_config_content - (Required) The content of your Studio Lifecycle Configuration script. This content must be base64 encoded.
  • tags - (Optional) A map of tags to assign to the resource. If configured with a provider default_tags configuration block present, tags with matching keys will overwrite those defined at the provider-level.

In addition to all arguments above, the following attributes are exported:

  • id - The name of the Studio Lifecycle Config.
  • arn - The Amazon Resource Name (ARN) assigned by AWS to this Studio Lifecycle Config.
  • tags_all - A map of tags assigned to the resource, including those inherited from the provider default_tags configuration block.

Explanation in Terraform Registry

Provides a Sagemaker Studio Lifecycle Config resource.

CloudFormation Example

CloudFormation code does not have the related resource.

Frequently asked questions

What is AWS Amazon SageMaker Studio Lifecycle Config?

AWS Amazon SageMaker Studio Lifecycle Config is a resource for Amazon SageMaker of Amazon Web Service. Settings can be wrote in Terraform.


Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.