Until INSERT S3 object into EC2 DB with Lambda @ java: AWS

This article is a memorandum from S3 to INSERT data to DB on EC2 via Lambda (java). (As of 09/2018) This is my first post, so please look at it with warm eyes. (You are welcome to point out. Please comment.)

1: AWS edition 2: Java part [Part 1] 3: Java [Part 2] 3.5: Java version [continued]

Creating an IAM user

Log in to the AWS Management Console and open the IAM dashboard.

Select "User" from the navigation bar on the left side of the screen. Create a user for S3 access from [Add User] at the top left of the screen. For later use, check "Programmatic access" in "Access type".

[Next step: Access authority] will take you to the access authority setting page, so select the block [Attach existing policy directly] on the right and select Filter the policy with "S3".

Some will be listed, so this time check the permissions for full access (read / wirte). Since the boundary is not set, go to the next step.

A confirmation screen will be displayed. After confirming that the user name and management policy are correct, click [Create User] at the bottom center of the screen to complete the creation of the user who has been granted the IAM role.

• The result screen will be displayed, so make a note of the "access key ID" and "secret access key". You can save it as CSV

Create VPC and subnet

Let's create a VPC to which the EC2 instance belongs.

• I think that there is no problem with the default, so if you want to skip the creation, please go to the next step "Create EC2 instance".

Access the VPC console. When you select [Create VPC] at the top of the screen, a pop-up will appear. Enter the VPC name (optional) and the IPv4 CIDR block. Determine the address range according to the number of instances you need.

After you create your VPC, create a subnet within your VPC. Select "Subnet" from the navigation bar on the left side of the screen and click [Create Subnet] at the top. Enter the subnet name (optional), select the VPC you created earlier, and create a subnet.

• Availability zone is not explained here, so it is set as "Not specified".
• Regarding the IPv4 CIDR block, if you do not need to prepare another subnet, make it the same as VPC.

Creating an internet gateway and attaching it to a VPC

Next, create an SSH entrance to connect to the created EC2 instance from the outside. Select "Internet Gateway" from the navigation bar of the VPC console. Similarly, click [Create Internet Gateway] from the top of the screen to create a gateway (Name tag is optional).

The gateway you just created is not tied to the VPC (not attached), so From [Action]-> "Attach to VPC", attach to the test_vpc created earlier. After attaching to the VPC, select "Route Table" from the navigation bar on the left side of the screen.

When you select the created VPC (test_vpc), the details of the VPC route information will be displayed at the bottom of the screen, so With the [Route] tab selected, click [Edit] to add a route.

Set the destination to 0.0.0.0/0 and move the cursor to the target, the gateway ID will be displayed, so click it. Click [Save] to confirm the edit.

• If the created subnet is not associated, associate it separately from the [Subnet Association] tab.

This completes the VPC area settings.

Creating an EC2 instance

Select Create Instance from the EC2 dashboard. Basically, it just pops according to the screen, but the specifications this time are as follows.

Instance type: t2.medium

DB has installed SQL Server (Express).

Creating an S3 bucket

After connecting to the S3 management console, click [+ Create bucket] at the top left of the screen.

Proceed as follows according to the wizard.

Next, let's upload an appropriate file with the [Upload] button at the top of the screen.

Here, the following CSV is created and uploaded.

test_people.csv

Id,Name,Age
1001,Dean,28
1002,Sam,25
1003,John,51
1004,Bobby,54
1005,Meg,26

Next time, I would like to get the information of this uploaded file by executing the Lambda function.

Summary

~~ (I forgot to take a capture) ~~ The EC2 part has been omitted. m (_ _) m The java edition will be posted soon.