Cloud Network Technology (Samoa) Limited
Lei 2549001OR2EQQFA3Q216 Legal Form Corporation Registered Address c/o Vistra (Samoa) Limited, Vistra Corporate Services Centre, Beach Road, Apia WS1312, Samoa Headquarter Address No.66 Zhongshan Road, Tu-Cheng Dist, New Taipei City 104 Legal Jurisdiction WS Inferred Jurisdiction Samoa Other Names Cloud Network Technology (Samoa) Limited (Preferred Ascii Transliterated Legal) Business Registry Name RA000509 Business Registry Identifier 78678
Legal Entity Identifier (LEI) details
Registered By 5493001KJTIIGC8Y1R12 Assignment Date 2017-12-19 16:52:51 UTC Record Last Update 2023-03-31 10:58:13 UTC Next Renewal Date 2023-11-26 16:19:47 UTC Status Code ISSUED
Imported from gleif on October 29 2023, 4.13PM
Cloud Network Technology (Samoa)
I have lived at two places in the last six months and at both spots I have noticed this unusual device attached to the WiFi network.
The MAC address for the device shows the manufacturer as cloud network technology (Samoa) limited, which I can’t seem to find any information on at all.
I recently moved and noticed the cloud network technology Samoa IP appearing again on my new network. What’s unusual is that after living at my new home for several weeks I decided to reset my phone and after resetting the phone, my network fing app recognized for the first time the Samoa IP at the exact same time down to the minute as my cell phone. The link below shows screenshots
Does anyone know what this cloud network technology Samoa is? Is it associated with my cell phone for some reason?
cell phone/ cloud network
Cloud network technology samoa limited что это
Office IT Services
Are you tired of setting up multiple locations of your IT infrastructure? Doing the same things all over again, hitting the same problems, and paying the same large bills? You are actually looking for a click-and-go office deployment that delivers NO HASSLES, just functionality.
CNT delivers that NO HASSLE Solution!
CNT delivers to businesses like yours, fixed, all-inclusive monthly fee-based Office-in-the-Cloud services using the latest enterprise graded desktop and server virtualization technology. Our office-in-the-Cloud joins power and flexibility. Desktops, Servers, and functionality are there to make any physical office IT obsolete. With CNT “Office-in-the-Cloud” your office IT becomes easy, flexible, and cost-effective.
With CNT Office-in-the-Cloud service you get a simple Infrastructure-as-a-Service platform. We go all the way! We make sure you have the required servers to power your centralized applications as well as the right number of desktops to serve your employees. Our technology team setups your complete office in our Enterprise graded Cloud infrastructure. All of this delivered for one fixed monthly fee!
Our Office-in-the-Cloud service includes an easily configured and deployed office environment with servers and desktops running on our state-of-the-art multi-tenant Cloud infrastructure. Desktops and/or servers can be easily added or removed based on business needs through a centralized management console.
High Availability and DR Included
All of CNT products and services include a comprehensive set of Disaster Recovery tools! Data image backups are taken every 30 minutes. You have the option to replicate any of your data within the same data center or a secondary data center at a different location. CNT Disaster Recovery is the most comprehensive Service in the marketplace.
With our Office-in-the-Cloud Service any of your data is just that: Yours! All your virtual machines, desktops, and Servers are behind a fully configurable firewall. To guarantee the utmost security from SSAE 16 compliance and 256- bit AES encryption to store your data on our expandable storage pools providing the industries best security to your data images. Oh yea we forgot to mention that your data is stored at locations within the North US and Europe!
The terraform_remote_state Data Source
The terraform_remote_state data source uses the latest state snapshot from a specified state backend to retrieve the root module output values from some other Terraform configuration.
You can use the terraform_remote_state data source without requiring or configuring a provider. It is always available through a built-in provider with the source address terraform.io/builtin/terraform . That provider does not include any other resources or data sources.
Important: We recommend using the tfe_outputs data source in the Terraform Cloud/Enterprise Provider to access remote state outputs in Terraform Cloud or Terraform Enterprise. The tfe_outputs data source is more secure because it does not require full access to workspace state to fetch outputs.
Alternative Ways to Share Data Between Configurations
Sharing data with root module outputs is convenient, but it has drawbacks. Although terraform_remote_state only exposes output values, its user must have access to the entire state snapshot, which often includes some sensitive information.
When possible, we recommend explicitly publishing data for external consumption to a separate location instead of accessing it via remote state. This lets you apply different access controls for shared information and state snapshots.
To share data explicitly between configurations, you can use pairs of managed resource types and data sources in various providers, including (but not limited to) the following:
|System||Publish with.||Read with.|
|Alibaba Cloud DNS
(for IP addresses and hostnames)
|alicloud_alidns_record resource type||Normal DNS lookups, or the dns provider|
(for IP addresses and hostnames)
|aws_route53_record resource type||Normal DNS lookups, or the dns provider|
|Amazon S3||aws_s3_object resource type||aws_s3_object data source|
|Amazon SSM Parameter Store||aws_ssm_parameter resource type||aws_ssm_parameter data source|
|Azure Automation||azurerm_automation_variable_string resource type||azurerm_automation_variable_string data source|
(for IP addresses and hostnames)
|azurerm_dns_a_record resource type, etc||Normal DNS lookups, or the dns provider|
|Google Cloud DNS
(for IP addresses and hostnames)
|google_dns_record_set resource type||Normal DNS lookups, or the dns provider|
|Google Cloud Storage||google_storage_bucket_object resource type||google_storage_bucket_object data source and http data source|
|HashiCorp Consul||consul_key_prefix resource type||consul_key_prefix data source|
|HashiCorp Terraform Cloud||Normal outputs terraform block||tfe_outputs data source|
|Kubernetes||kubernetes_config_map resource type||kubernetes_config_map data source|
|OCI Object Storage||oci_objectstorage_bucket resource type||oci_objectstorage_bucket data source|
These are some common options from the Official Terraform providers, but there are too many configuration storage options for us to list them all here, including some in partner and community providers. Any pair of managed resource type and corresponding data source can potentially be used to share data between Terraform configurations. See individual provider documentation to find other possibilities.
A key advantage of using a separate explicit configuration store instead of terraform_remote_state is that the data can potentially also be read by systems other than Terraform, such as configuration management or scheduler systems within your compute instances. For that reason, we recommend selecting a configuration store that your other infrastructure could potentially make use of. For example:
- If you wish to share IP addresses and hostnames, you could publish them as normal DNS A , AAAA , CNAME , and SRV records in a private DNS zone and then configure your other infrastructure to refer to that zone so you can find infrastructure objects via your system’s built-in DNS resolver.
- If you use HashiCorp Consul then publishing data to the Consul key/value store or Consul service catalog can make that data also accessible via Consul Template or the HashiCorp Nomad template stanza.
- If you use Kubernetes then you can make Config Maps available to your Pods.
Some of the data stores listed above are specifically designed for storing small configuration values, while others are generic blob storage systems. For those generic systems, you can use the jsonencode function and the jsondecode function respectively to store and retrieve structured data.
You can encapsulate the implementation details of retrieving your published configuration data by writing a data-only module containing the necessary data source configuration and any necessary post-processing such as JSON decoding. You can then change that module later if you switch to a different strategy for sharing data between multiple Terraform configurations.
Example Usage ( remote Backend)
data "terraform_remote_state" "vpc" backend = "remote" config = organization = "hashicorp" workspaces = name = "vpc-prod" > > > # Terraform >= 0.12 resource "aws_instance" "foo" # . subnet_id = data.terraform_remote_state.vpc.outputs.subnet_id > # Terraform resource "aws_instance" "foo" # . subnet_id = "$data.terraform_remote_state.vpc.subnet_id>" >
Example Usage ( local Backend)
data "terraform_remote_state" "vpc" backend = "local" config = path = ". " > > # Terraform >= 0.12 resource "aws_instance" "foo" # . subnet_id = data.terraform_remote_state.vpc.outputs.subnet_id > # Terraform resource "aws_instance" "foo" # . subnet_id = "$data.terraform_remote_state.vpc.subnet_id>" >
The following arguments are supported:
- backend — (Required) The remote backend to use.
- workspace — (Optional) The Terraform workspace to use, if the backend supports workspaces.
- config — (Optional; object) The configuration of the remote backend. Although this argument is listed as optional, most backends require some configuration. The config object can use any arguments that would be valid in the equivalent terraform < backend "" < . >> block. See the documentation of your chosen backend for details.
Note: If the backend configuration requires a nested block, specify it here as a normal attribute with an object value. (For example, workspaces = < . >instead of workspaces < . >.)
In addition to the above, the following attributes are exported:
- (v0.12+) outputs — An object containing every root-level output in the remote state.
- ( < = v0.11) - Each root-level output in the remote state appears as a top level attribute on the data source.
Root Outputs Only
Only the root-level output values from the remote state snapshot are exposed for use elsewhere in your module. Resource data and output values from nested modules are not accessible.
If you wish to make a nested module output value accessible as a root module output value, you must explicitly configure a passthrough in the root module. For example:
module "app" source = ". " > output "app_value" # This syntax is for Terraform 0.12 or later. value = module.app.example >
In this example, the output value named example from the «app» module is available as the app_value root module output value. If this configuration didn’t include the output «app_value» block then the data would not be accessible via terraform_remote_state .
Warning: Although terraform_remote_state doesn’t expose any other state snapshot information for use in configuration, the state snapshot data is a single object and so any user or server which has enough access to read the root module output values will also always have access to the full state snapshot data by direct network requests. Don’t use terraform_remote_state if any of the resources in your configuration work with data that you consider sensitive.