As I began my journey in development, I encountered numerous developers. As I delved into development tasks, I naturally learned about setting up instances and deploying them in the cloud. I thought anyone would eventually start this way, as deploying is a crucial step regardless of whether you're developing API servers or clients. I believed this process would be learned gradually as one gained experience.
However, I discovered that both junior and senior developers, like myself, faced difficulties in this process. This realization led me to ponder if there was a way to alleviate these challenges, and thus, I created EC2 DMS.
The idea was conceived as illustrated in the image below.
Let's assume you want to deploy a Java JAR build project to a Private EC2. According to the diagram, using SWS EC2 DMS functionality, you would upload the JAR build file to Bastion EC2, then transfer the file from Bastion EC2 to Private EC2. Following that, you would configure the environment on Private EC2 based on the build stack, execute the project, and connect the instance to the ALB target group.
However, the process doesn't end there. You also need to configure Security Groups for Bastion EC2, Private EC2, and the Public ALB as shown in the image.
In this process, there are numerous AWS Cloud concepts to learn, which can be overwhelming and headache-inducing. But using the SteveWebService Console, you can build this architecture with minimal input, ensuring it's set up in your AWS Cloud environment as depicted.
The process is as follows:
First, create an AWS VPC Turn Key (SWS Project). When you create an AWS VPC Turn Key (SWS Project), it generates Security Groups structured as shown below. (While various resources are created, the crucial aspect for this scenario is Security Groups, so only the image related to them is shared.)
Once created according to the above structure, users no longer need to design Security Groups. Isn't that easy?
Go to Steve Web Service Page to check
Go to see Steve Web Service AWS VPC Turn Key functionality
Now, through EC2 DMS, you only need to make minimal inputs and selections as shown in the image below. Refer to the image below:
First, select the previously created SWS Project and enter the Project Name. Then, choose the Stack, upload the Java project's JAR build file, and if it's a custom port, change the port number accordingly. Simply click "Create Project".
By doing so, Bastion EC2, Private EC2, a new ALB to connect to the instances, and the target group connected to the Private EC2, as depicted in the initially shared image structure, will be created in just 10 minutes.
Go to Steve Web Service Page to check
Go to see Steve Web Service AWS EC2 DMS functionality
Isn't it easy?
We don't stop at just creating; we also provide management capabilities for these instances. Functions include resizing instance sizes, managing Bastion EC2 IP, issuing SSL certificates for domains purchased through Route 53, and connecting them to ALB, as shown in the image below.
In the provided image, selecting the domain purchased through Route 53 as in step 6 and clicking the "Create SSL Certificate" button completes the SSL certificate setup for that domain.
Next, in step 9, the user only needs to input the Subdomain name, and upon clicking the "Connect Domain" button, the connection to Route 53 with HTTPS:// for the respective subdomain is established.
Isn't it incredibly easy? Users can deploy projects to the cloud and deliver them to users without any knowledge of AWS Cloud.
Go to Steve Web Service Page to check
Go to see Steve Web Service AWS EC2 DMS usage guide
We continue to develop tools that enable users to build cloud architectures without the need for learning AWS Cloud. This helps developers focus more on their business, and further provides value by allowing even small teams of developers to utilize AWS resources to the fullest.
The next article will delve into solving the issue of connecting multiple instances to a single ALB and routing based on paths. End.
Go to Steve Web Service Page to check
