Workflow
To harness the full power of AWS-EC2, we need to connect to the ecosystem and deploy apps on the edge of the platform (machines are on the “edge” of a given network when they are physically close to the systems or applications that are creating the data being used by the server).
First, we need to make an AWS account and an EC2 server (for its computing capacity). Then follow these steps:
Create an AMI (Amazon Mission Image). This contains all of the application and software packages necessary to execute the application.
Decide what hardware to use. In order to make this decision, you need to know the instance type as well as the size of the hardware, which is determined by the amount of workload needed.
Customize cases for different contexts. For example, customize subnets, decide which instances stop or revoke actions, or choose whether or not to update versions once the instance is fully operational. All of these details can be managed here until we configure the instance. These initial steps are particularly dependent on both the operating system (OS) volume and fundamental hardware.
Add storage, meaning assign more storage to the same operating system.
Add tags. You can apply/create tags that allow you to find things more quickly and recognize an EC2 system. We create tags with relevant names so that we can understand which team they correspond to, know which accounting unit they relate to, and launch an instance goal. Recognizing an instance and knowing its purpose is critical when operating 700-800+ instances. It can be a packed schedule, so tagging comes to the rescue.
Set up a security group. For the EC2 instance, you would establish a firewall, also known as a security group. This is where we allow or restrict connections from the outside community to this particular EC2 instance. This firewall restricts connections relying on the port number and IP address from both the outside and the inside.
Review. Look over all of the parameters and double-check that they're exactly what is intended before clicking submit to activate an EC2 instance.
