Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

Add Terraform support for configuring private origin authentication using signature v4 headers. Used for private S3 buckets or other compatible object stores.

New or Affected Resource(s)

• google_compute_backend_service

Potential Terraform Configuration

resource "google_compute_backend_service" "example" {
  name          = "tf-test-backend-service-example"
  security_settings {
    aws_v4_authentication {
      access_key_id = "ELPMAXEFODNN7EXAMPLE"
      access_key = "EXAMPLEc5771d871763a393e44b703571b55cc28424d1a5e86da6ed3cELPMAXE"
      access_key_version = "prod-access-key-v1.2"
      origin_region = "us-east-2"
    }
  }
  backend {
    group = google_compute_global_network_endpoint_group.group.self_link
  }
}

References

API: Beta API for backendServices.securitySettings.awsV4Authentication

Docs: Configure private origin authentication

b/350514997