AWS App2Container を利用して Java および .NET アプリケーションをリモートでモダナイズする

$ export AWS_DEFAULT_REGION=us-east-1

$ cd /tmp
$ curl -o AWSApp2Container-installer-linux.tar.gz https://app2container-release-us-east-1.s3.us-east-1.amazonaws.com/latest/linux/AWSApp2Container-installer-linux.tar.gz
$ tar xvf AWSApp2Container-installer-linux.tar.gz
$ echo y |sudo ./install.sh

$ sudo app2container --version

$ sudo yum install docker -y
$ sudo systemctl start docker
$ sudo systemctl enable docker

$ aws s3 mb s3://a2c-remote-`date +%s`
make_bucket: a2c-remote-1617832770

$ aws s3 ls |grep a2c-remote
2021-04-07 21:59:31 a2c-remote-1617832770

$ sudo app2container init
Workspace directory path for artifacts[default: /root/app2container]: 
Use AWS EC2 Instance profile 'arn:aws:iam::<Account ID>:instance-profile/<Role Name>' configured with this instance? (Y/N)[default: y]:  
Which AWS Region to use?[default: us-east-1]: 
Optional S3 bucket for application artifacts: a2c-remote-1617832770
Report usage metrics to AWS? (Y/N)[default: y]: 
Automatically upload logs and App2Container generated artifacts on crashes and internal errors? (Y/N)[default: y]: 
Require images to be signed using Docker Content Trust (DCT)? (Y/N)[default: n]: 
Configuration saved
$

$ ssh-keygen -t rsa -f ~/.ssh/a2crsakey -q -P ""
$ aws ec2 import-key-pair --key-name "A2CKEY" \
--public-key-material fileb://~/.ssh/a2crsakey.pub
$ B64KEY=$(base64 ~/.ssh/a2crsakey)
$ echo -e $'{\n "username": "ec2-user",\n "key": "'$B64KEY'"\n}' >> a2ckey.json
$ aws secretsmanager create-secret --name a2ckey --description "A2C secrets" --secret-string file://a2ckey.json

$ echo "User Data creation to install springboot application"
$ cat <<EOF >appuserdata.sh
#!/bin/bash
yum -y install git maven
git clone https://github.com/aws-samples/kubernetes-for-java-developers.git
cd kubernetes-for-java-developers/app
mvn spring-boot:run &
EOF

$ echo "Below commands creates security group and ingress rules"
$ aws ec2 create-security-group --group-name A2CSecurityGroup --description "A2C security group"
$ aws ec2 authorize-security-group-ingress --group-name A2CSecurityGroup \
--protocol tcp --port 22 --cidr 0.0.0.0/0
$ aws ec2 authorize-security-group-ingress --group-name A2CSecurityGroup \
--protocol tcp --port 8080 --cidr 0.0.0.0/0

$ echo "Below commands creates ec2 host with springboot application installed"
$ aws ec2 run-instances \
--image-id resolve:ssm:/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2 \
--count 1 --instance-type t2.medium --key-name A2CKEY \
--block-device-mapping "[ { \"DeviceName\": \"/dev/xvda\", \"Ebs\": { \"VolumeSize\": 32 } } ]" \
--tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=APPHost}]' \
--security-groups A2CSecurityGroup \
--user-data file://appuserdata.sh

$ aws ec2 describe-instances --filter "Name=tag:Name,Values=APPHost" \
--query "Reservations[*].Instances[*].[PublicIpAddress, Tags[?Key=='Name'].Value|[0]]" \
--output text
$ curl http://<IP Address>:8080/hello - Note: IP address is masked in command for security reasons.
Hello

$ aws secretsmanager list-secrets --query "SecretList[?Name=='a2ckey']"
$ aws ec2 describe-instances --filter "Name=tag:Name,Values=APPHost" \
--query "Reservations[*].Instances[*].[PublicIpAddress, Tags[?Key=='Name'].Value|[0]]" \
--output text

$ sudo app2container remote configure
Server IP address: <AppServerIP>
Server FQDN (Fully Qualified Domain Name): 
Authentication method to be used (key/cert)[default: key]: 
Secret ARN for remote connection credentials: arn:aws:secretsmanager:us-east-1:xxxxxxxxxxxx:secret:a2c-remote-1-ezY0tZ
Continue to configure another server? (y/N)[default: n]: 
? Configure successful, you can view hosts config file at: /root/.app2container-config/remote_hosts.conf

$ sudo app2container remote inventory --target <AppServerIP>
✔ Server inventory has been stored under /root/app2container/remote/<AppServerIP>/inventory.json
? Remote inventory retrieved successfully

$ sudo app2container remote analyze --application-id  java-generic-dc310dd41a0a --target <AppServerIP>
? Analysis successful for application java-generic-dc310dd41a0a

? Next Steps:
1. View the application analysis file at /root/app2container/remote/<AppServerIP>/java-generic-dc310dd41a0a/analysis.json.
2. Edit the application analysis file as needed.
3. Start the extraction process using the following command: app2container remote extract --target <AppServerIP> --application-id java-generic-dc310dd41a0a

$ sudo app2container remote extract --application-id  java-generic-dc310dd41a0a --target <AppServerIP>
? Extraction successful for application java-generic-dc310dd41a0a

? Next Step:
1. Please initiate containerization using "app2container containerize --input-archive /root/app2container/remote/<AppServerIP>/java-generic-dc310dd41a0a/java-generic-dc310dd41a0a-extraction.tar"

$ sudo app2container containerize --input-archive /root/app2container/remote/<AppServerIP>/java-generic-dc310dd41a0a/java-generic-dc310dd41a0a-extraction.tar
✔ AWS prerequisite check succeeded
✔ Docker prerequisite check succeeded
✔ Extracted input archive
✔ Entry file generated
✔ Dockerfile generated under /root/app2container/java-generic-dc310dd41a0a/Artifacts
✔ Generated dockerfile.update under /root/app2container/java-generic-dc310dd41a0a/Artifacts
✔ Generated deployment file at /root/app2container/java-generic-dc310dd41a0a/deployment.json
? Containerization successful. Generated docker image java-generic-dc310dd41a0a

? You are all set to test and deploy your container image.

Next Steps:
1. View the container image with "docker images" and test the application with "docker run -it java-generic-dc310dd41a0a".
2. When you are ready to deploy to AWS, please edit the deployment file as needed at /root/app2container/java-generic-dc310dd41a0a/deployment.json.
3. Generate deployment artifacts using "app2container generate app-deployment --application-id java-generic-dc310dd41a0a".

$ sudo docker images
REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE
java-generic-dc310dd41a0a   latest              ae38e940aed9        49 seconds ago      4.27GB
amazonlinux                 2                   935e8db88df5        2 days ago     

       "ecsParameters": {
              "createEcsArtifacts": false,
              ....
              ....
       "eksParameters": {
              "createEksArtifacts": true,
              "stackName": "a2c-java-generic-d15cb42f23d9-EKS",
              "reuseResources": {
                     "vpcId": "",
                     "reuseExistingA2cStack": {
                            "cfnStackName": ""
                     },
                     "sshKeyPairName": ""
              },
              "gMSAParameters": {
                     "domainSecretsArn": "",
                     "domainDNSName": "",
                     "domainNetBIOSName": "",
                     "createGMSA": false,
                     "gMSAName": ""
              }
       }

$ sudo app2container generate app-deployment  --application-id java-generic-dc310dd41a0a --deploy
✔ AWS prerequisite check succeeded
✔ Docker prerequisite check succeeded
✔ Created ECR Repository
✔ Uploaded CloudFormation resources to S3 Bucket: a2c-remote-1614362000
✔ Generated CloudFormation Master template at: /root/app2container/java-generic-dc310dd41a0a/EksDeployment/amazon-eks-entrypoint-new-vpc.yaml
✔ Initiated CloudFormation stack creation. This may take a few minutes. To track progress, open the AWS CloudFormation console.
? Deployment successful for application java-generic-dc310dd41a0a

? You're all set to use AWS CloudFormation to manage your application stack.

Successfully created EKS stack a2c-java-generic-dc310dd41a0a-EKS.  Check the  AWS CloudFormation Console for details.
We have also set up your kubectl config to access your cluster at: /root/.kube/config

Next Steps:
1. Setup a pipeline for your application stack using:

    app2container generate pipeline --application-id java-generic-dc310dd41a0a
$ 

$ sudo curl --silent --location -o /usr/local/bin/kubectl \
   https://amazon-eks.s3.us-west-2.amazonaws.com/1.17.11/2020-09-18/bin/linux/amd64/kubectl
$ sudo chmod +x /usr/local/bin/kubectl
$ sudo aws eks update-kubeconfig --name <EKS Clustername>

$ sudo /usr/local/bin/kubectl get pods
NAME                                                    READY   STATUS    RESTARTS   AGE
java-generic-dc310dd41a0a-deployment-867b54f57f-t6gtq   1/1     Running   0          41m

$ sudo /usr/local/bin/kubectl get services
NAME                                TYPE           CLUSTER-IP     EXTERNAL-IP                                                               PORT(S)          AGE
java-generic-dc310dd41a0a-service   LoadBalancer   172.20.14.56   <DNS Name>.<region>.elb.amazonaws.com   8080:31043/TCP   41m
kubernetes                          ClusterIP      172.20.0.1     <none>                                                                    443/TCP          57m

$ curl http://*<DNS Name>**.<region>*.elb.amazonaws.com:8080/hello
Hello