Google Compute Engine Organization Security Policy Association
This page shows how to write Terraform for Compute Engine Organization Security Policy Association and write them securely.
The Organization Security Policy Association in Compute Engine can be configured in Terraform with the resource name
google_compute_organization_security_policy_association. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
The following arguments are supported:
name- (Required) The name for an association.
attachment_id- (Required) The resource that the security policy is attached to.
policy_id- (Required) The security policy ID of the association.
In addition to the arguments listed above, the following computed attributes are exported:
id- an identifier for the resource with format
display_name- The display name of the security policy of the association.
Explanation in Terraform Registry
An association for the OrganizationSecurityPolicy.
Warning: This resource is in beta, and should be used with the terraform-provider-google-beta provider. See Provider Versions for more details on beta resources. To get more information about OrganizationSecurityPolicyAssociation, see:
Tips: Best Practices for The Other Google Compute Engine Resources
In addition to the google_compute_disk, Google Compute Engine has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.
Ensure the encryption key for your GCE disk is stored securely
It is better to store the encryption key for your GCE disk securely. Secret Manager could be used instead.
Ensure your VPC firewall blocks unwanted outbound traffic
It is better to block unwanted outbound traffic not to expose resources in the VPC to unwanted attacks.
Ensure appropriate service account is assigned to your GCE instance
It is better to create a custom service account for the instance and assign it.
Ensure OS login for your GCE instances is enabled at project level
It is better to enable OS login for your GCE instances. Enabling OS login ensures that SSH keys used to connect to instances are mapped with IAM users, allowing centralized and automated SSH key management.
Ensure to use modern TLS protocols
It's better to adopt TLS v1.2+ instead of outdated TLS protocols.
Ensure VPC flow logging is enabled
It is better to enable VPC flow logging. VPC flow logging allows us to audit traffic in your network.