Must-see for developers! How to operate security groups without logging in to AWS
We will introduce specific usage scenarios for Glip, examples of cost reduction, and methods to achieve operational efficiency while ensuring security, including procedures for setting up IAM.
Automating security group configuration in a staging environment
When creating and developing a website, content is often uploaded to a test environment called a staging environment to check for any errors in the content.
In this case, in order for the "person checking the contents" to access the staging environment, the IP address and port permission settings must be added or updated to the security group.
To change the settings of this security group, you need to log in to AWS and access the security group, but it is time-consuming for the person changing the settings to change the security group manually every time, and it may lead to mistakes.
Glip Automation Solution
Glip offers a solution that allows the person who checks the contents to change security group settings without having to request the person who changes the settings to do the work.
The operation image is to access the IP address change request screen and press the Next button. The "person in charge of changing the settings" just needs to approve the authentication email that is received.
Specific usage scenarios
The following are some specific usage scenarios:
- When checking website content, have the test team members set IP address permissions to display and check staging content.
- When creating a website, have the remote work environment workers set up IP address permissions when uploading content to staging.
- During server-side development, have members of our partner company set up IP address permissions for logging in to the staging server.
How to use Glip
To use Glip, you need to configure AWS IAM (Identity and Access Management). To do so, follow the steps below.
- Creating an IAM User: Create an IAM user in the AWS console and grant it the necessary permissions. IAM users are an important element for managing access to AWS resources. By setting appropriate permissions, you can ensure security while allowing only necessary operations.
- Setting up Glip:In the Glip administration screen, configure your AWS account and AWS security group.
Setting these up is less expensive than developing them in-house and is a relatively easy task for engineers.
IAM configuration
In IAM settings, you can set detailed permissions for each user. For example, you can allow a specific user to only manage the power supply of EC2 instances and restrict other operations. This allows you to allow only necessary operations while maintaining security.
You can use IAM policies to set granular access rights for users and groups. For example, you can allow a specific user to start and stop EC2 instances, but restrict other operations. This allows you to ensure security while allowing only the necessary operations.
Usage cost
The usage cost is 660 yen per month as of September 2024. This cost is very cost-effective when you consider the cost savings of having the power off and the development costs of solving the problem in-house.
summary
In this way, automating security group settings in the staging environment is expected to improve work efficiency and reduce errors. It will be a very useful tool for operations teams as it improves operational efficiency.
Take this opportunity to consider using Glip's solutions.