Resource classification
KakaoCloud offers a wide array of services across its interconnected data centers worldwide, enabling seamless access to various resources. These resources are classified into 'Global resources', 'Region resources', and 'Availability zone resources'.
- Global resources are accessible globally, without restrictions by region or Availability Zone.
- Region resources are confined to a specific geographical region.
- Availability zone resources care designated for use within a particular data center or Availability Zone.
This structure ensures that organizations of any size, anywhere, can find services and resources that fit their needs.
| Resource Type | Description |
|---|---|
| Global resources | - Resources that are not part of a region, a higher-level concept - Resources like images that can be used regardless of location - DNS, IAM, etc. |
| Region resources | - Resources in different locations within a specific region - Designed to provide shorter latency and higher performance to users in a specific area |
| Availability zone resources | - Resources that can be used within a specific data center or Availability Zone - Resources in different locations like Public IP - Instance types, Subnet, etc. |
Understanding
Region resources vs. Availability zone resourcesRegion resources can use all resources in that region, but Availability zone resources can only use resources in the same AZ.
For instance, connecting Block Storage or assigning a Public IP requires both the resource and the instance to be in the same AZ.
Available Resources by Service
The services provided by KakaoCloud come with different types of resources tailored to specific requirements.
| Category | Resource | Resource Type | Description |
|---|---|---|---|
| Common | Resource ID | Region | It can only be used in the region where the resource was created - e.g. image ID, instance ID, volume ID, snapshot ID |
| User-defined resource name | Region | - It can only be used in the region where the resource was create - e.g. security group name, key pair name - It is possible to create resources with the same name in multiple regions, but these resources are not related to each other | |
| Beyond Compute Service (BCS) | Key Pair | Global & Region | - Key pairs are associated with the region they are created in, and you can generate your own RSA key pair and upload it to the desired region - Key pairs can be uploaded to each region for global use |
| Image | Region | Can be created and used per region | |
| Snapshot | Region | Can only be used for creating volumes in the corresponding region | |
| Instance | Availability Zone(AZ) | It can be used within an Availability Zone and can access Global resources or resources in the same AZ - e.g. VM, Bare Metal Server | |
| Instance Type | Availability Zone | Can only use instance types in the same AZ | |
| Volume | Availability Zone | Can only be connected to instances in the same AZ | |
| Beyond Networking Service (BNS) | Route Table | Global & Region | Route Tables are applied to the VPC network within a project and are considered a global resource |
| Security Group | Region | Using security group rules within a project prevents instances from communicating with instances outside of that region - Traffic coming from instances in other regions is considered WAN bandwidth | |
| VPC | Region | VPC networks are regional resources, but individual subnets are categorized as availability zone resources | |
| Network Interface | Availability Zone | Can connect the network interface to an instance within the same AZ | |
| Public IP Address | Region | Public IPs reserved for a project belong to a region and can only be connected to instances in the same region | |
| Subnet | Availability Zone | Controls prefixes of network IP space within a region and assigns internal IP addresses of instances to prefixes | |
| DNS | Global | Manages domain names globally and supports distributed DNS | |
| CDN | Global & Region | User-created resources are managed by region, but the provided Edges are global | |
| Load Balancer | Availability Zone | Distributes traffic to instances within an Availability Zone | |
| Transit Gateway | Region | Resides within a region, and currently can only connect to VPCs within the same region | |
| Beyond Storage Service (BSS) | Object Storage | Region | Treats data as individual objects, each with a unique identifier |
| File Storage | Region | Can be used within a region; the file system ID is a unique identifier within the region | |
| Block Storage | Region | Can be used within a region | |
| Management | IAM | Global | It allows admins to set access policies and permissions for specific resources within an organization |
| Container Pack | Container Registry | Region | Managed as repository, image, tag, etc., and provides different registry endpoints for each region |
| Developer Tools | DevOps Pipeline | Region | Pipelines and configurations are managed and utilized per region |
| OSS Library | Region | Provisioning is provided using customer resources in each region |