2 posts tagged with "bns"

Hello, we are introducing two major releases for KakaoCloud Load Balancing.

1. TLS listener added to Network Load Balancer (NLB)​

TLS has been added to the NLB listener protocol among KakaoCloud load balancer types.

Selecting the TLS protocol

A TLS listener can offload encryption and decryption work to the load balancer. To use a TLS listener, you must deploy and specify at least one server certificate on the load balancer. This certificate is called the default SSL certificate, and after creating a TLS listener in the console, you can replace it or add a new certificate. KakaoCloud NLB supports TLS versions from 1.0 through 1.2.

Selecting the minimum TLS version and setting the default SSL certificate

For instructions on creating a TLS listener, see the linked document.

2. Access Log activation feature provided​

An Access Log activation feature has been added to all KakaoCloud load balancer types.
Access Logs are information collected to analyze traffic patterns sent to a load balancer and troubleshoot issues.

Access Log is an optional feature that users can select, and it is set to Disabled by default in the console. If you change the Access Log feature to Enabled and activate it, compressed files of captured logs can be stored in a specified Object Storage bucket. The Object Storage bucket must be located in the same region, and the encryption setting for the bucket must be set to Disabled. When configuring Access Log in the console, you can find a detailed configuration guide in the pop-up window shown below.

Object Storage bucket guidance when configuring Access Log

For reference, networking costs are not charged for transferring log files, but Object Storage costs are charged.

For a more detailed explanation of Access Log, see the linked document.

We will continue working to provide safer and more convenient cloud services.

Thank you.

Hello, a "sharing" feature that lets you share Transit Gateways across projects has been added to the Transit Gateway service.

With the sharing feature in Transit Gateway, you can now share a Transit Gateway across projects and configure communication between VPCs in different projects.

Assume you are using two projects, A and B, as shown in the following diagram. Previously, the administrator of this organization placed a Transit Gateway in each project and managed the VPCs for each project. With this sharing feature, however, the Transit Gateway in project A can also be used from project B. In other words, all VPCs in both projects can be managed conveniently through one shared Transit Gateway.

Unlike the simplified diagram provided to aid understanding, if you need a complex network configuration that connects dozens or hundreds of on-premises and VPC environments in practice, this feature can greatly simplify management points and significantly reduce operational costs.

Understanding the Transit Gateway sharing feature

For a detailed usage example that implements VPC connectivity through Transit Gateway sharing across projects, see the detailed tutorial guide.

KakaoCloud users can use Transit Gateway to improve the efficiency of operating and managing multiple VPCs and respond flexibly to future network scalability needs. Please also remember that Transit Gateway is basically a kr-central-2 regional service, and only users with the Project Admin role can access it. For more information about Transit Gateway, see the technical documentation.

We will continue working to provide safer and more convenient cloud services.

Thank you.