AWS Amazon S3 Working Storage

aws_storagegateway_working_storage (Terraform)

The Working Storage in Amazon S3 can be configured in Terraform with the resource name aws_storagegateway_working_storage. The following sections describe 2 examples of how to use the resource and its parameters.

Example Usage from GitHub

asrkata/SebastianUA-terraform

resource "aws_storagegateway_working_storage" "storagegateway_working_storage" {
  count = var.enable_storagegateway_working_storage ? 1 : 0

  gateway_arn = var.storagegateway_working_storage_gateway_arn != "" ? var.storagegateway_working_storage_gateway_arn : (var.enable_storagegateway_gateway ? aws_storagegateway_gateway.storagegateway_gateway[count.index].arn : null)
  disk_id     = var.storagegateway_working_storage_disk_id

niveklabs/aws

resource "aws_storagegateway_working_storage" "this" {
  disk_id     = var.disk_id
  gateway_arn = var.gateway_arn
}

Parameters

• disk_id required - string
• gateway_arn required - string
• id optional computed - string

Explanation in Terraform Registry

Manages an AWS Storage Gateway working storage.

NOTE: The Storage Gateway API provides no method to remove a working storage disk. Destroying this Terraform resource does not perform any Storage Gateway actions.

Tips: Best Practices for The Other AWS Amazon S3 Resources

In addition to the aws_s3_bucket_public_access_block, AWS Amazon S3 has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.

aws_s3_bucket_public_access_block

Ensure S3 bucket-level Public Access Block restricts public bucket policies

It is better to enable S3 bucket-level Public Access Block if you don't need public buckets.

aws_s3_bucket

Ensure S3 bucket access policy is well configured

It is better to configure the S3 bucket access policy properly to limit it unless explicitly required.