Hello. Welcome to 'This is My Architecture'.
I'm Andy Kim, Solutions Architect at Amazon Web Services.
Today, I'm with Jawon Choo who is the manager at SK Telecom.
Hello, manager.
Hello. I'm Jawon Choo who is in charge of cloud management platform development
at SK Telecom.
It sounds like a very important service. What is the cloud management platform at SK Telecom?
Our cloud management platform is the next-generation cloud management platform
that can manage mobile edge computing, cloud network, and cloud security businesses
that combine communication and cloud beyond the multi-cloud and hybrid cloud.
It appears the management platform that can utilize multiple cloud business platforms for future SK businesses.
It is divided into two types: CAP and CBP. What do the two mean?
CAP stands for Cloud Admin Portal. You can think of it as a business support platform that provides functions
such as contract management, account management, and billing management necessary for cloud business.
CBP is a platform that collects all BSS, OSS Info from our various cloud ecosystems and
provides better values through AI analysis.
Let's look at the service called CAP above, you've used cloud, serverless, computing service, and Fargate.
What's Fargate for?
The biggest feature of our Cloud Admin Portal is that it is the completely serverless computing architecture.
The reason we chose Fargate was to make good use of the serverless computing.
With Fargate, we have <a href="https://en.dict.naver.com/#/entry/enko/8e93a47e8d7f4a4ea744301399cfd490">cost-efficiency</a> advantages as well as features such as auto scaling.
Let me talk about the CAP for a moment. External users access this through the view page,
and API calls are made from the view. Then, ELB provides authentication or
common information to each Fargate service. ELB also can be used for the user portal.
On the right, It looks like the database-related service.
There are Elasticache and RDS Aurora services.
What are those for?
Yes, for DB, now we use Aurora DB. but in the previous system, we used MySQL.
However, we chose Aurora because it is completely compatible with MySQL
and outperforms MySQL up to ten times. For Elasticache, we use Redis.
It mainly stores session info such as authentication info and role privileges that must be shared between each Fargate service.
You seem to have implemented the microservice architecture well by using these serverless services and managed services.
As you can see below, there is the artificial intelligence service called SageMaker.
What purpose and reasons did you choose SageMaker?
Yes, as mentioned earlier, our cloud business platform functions to collect and analyze data from various cloud ecosystems.
We use three algorithms for our analysis.
Two of them are PCA algorithm and RCF. They're already provided built-in by SageMaker. So I chose them.
In addition, we chose SageMaker because the ARIMA algorithm we need to use provides the BIOC function,
so we can use the custom algorithms.
In fact, the artificial intelligence needs a lot of time and effort.
Using a service called SageMaker, you can use a built-in algorithm.
And you can use a custom algorithm. In addition to that, you can easily create
and use the artificial intelligence service using different functions such as SageMaker Studio, Pilot, and Experiment.
Do you have any plans for the future?
Yes, our plan is to collect more various data in the future and provide better and more valuable data.
And through a service called AWS CodePipeline, we aim to advance a series of CI/CD processes
that are automatically built in Docker images
and distributed to Fargate services through testing.
Thank you for explaining the architecture of SK Telecom's cloud management platform today.
Thank you.
This has been 'This is My Architecture'.
Thank you.