{Auto Scaling}チュートリアル:Lambda 関数を呼び出すライフサイクルフックの設定

https://docs.aws.amazon.com/ja_jp/autoscaling/ec2/userguide/tutorial-lifecycle-hook-lambda.html

 

-- 1. コマンド等のインストール

-- 1.1 aws cli version 2 インストール

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
aws --version

-- 1.2 jqインストール
sudo yum -y install jq

-- 2. 起動テンプレートの作成

vim a.json

{
  "ImageId": "ami-02c3627b04781eada",
  "InstanceType": "t3.nano",
  "SecurityGroupIds": ["sg-11111111111111111"]
}


aws ec2 create-launch-template \
--launch-template-name lt01 \
--launch-template-data file://a.json

 

aws ec2 describe-launch-templates


aws ec2 describe-launch-template-versions --launch-template-id lt-22222222222222222


-- 3. オートスケーリンググループの作成


aws autoscaling create-auto-scaling-group \
--auto-scaling-group-name asg01 \
--launch-template '{
                "LaunchTemplateName": "lt01",
                "Version": "$Default"
            }' \
--min-size 1 \
--max-size 1 \
--desired-capacity 1 \
--default-cooldown 300 \
--health-check-type "EC2" \
--health-check-grace-period 300 \
--vpc-zone-identifier "subnet-33333333333333333" \
--no-new-instances-protected-from-scale-in


aws autoscaling describe-auto-scaling-groups

 

-- 4. IAMポリシー作成
vim policy01.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "autoscaling:CompleteLifecycleAction"
      ],
      "Resource": "arn:aws:autoscaling:*:999999999999:autoScalingGroup:*:autoScalingGroupName/asg01"
    }
  ]
}


aws iam create-policy \
--policy-name policy01 \
--policy-document file://policy01.json

-- 5. IAMロール作成
vim role01.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "lambda.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

aws iam create-role \
--role-name role01 \
--assume-role-policy-document file://role01.json

-- 6. ポリシーをロールにアタッチ
aws iam attach-role-policy \
--policy-arn arn:aws:iam::999999999999:policy/policy01 \
--role-name role01

aws iam attach-role-policy \
--policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole \
--role-name role01

 

-- 7. Lambda関数作成

vim test.js

var aws = require("aws-sdk");
exports.handler = (event, context, callback) => {
    console.log('LogAutoScalingEvent');
    console.log('Received event:', JSON.stringify(event, null, 2));
    var autoscaling = new aws.AutoScaling({region: event.region});
    var eventDetail = event.detail;
    var params = {
        AutoScalingGroupName: eventDetail['AutoScalingGroupName'], /* required */
        LifecycleActionResult: 'CONTINUE', /* required */
        LifecycleHookName: eventDetail['LifecycleHookName'], /* required */
        InstanceId: eventDetail['EC2InstanceId'],
        LifecycleActionToken: eventDetail['LifecycleActionToken']
    };
    var response; 
    autoscaling.completeLifecycleAction(params, function(err, data) {
        if (err) { 
            console.log(err, err.stack); // an error occurred
            response = {
                statusCode: 500,
                body: JSON.stringify('ERROR'),
            };
        } else {
            console.log(data);           // successful response
            response = {
                statusCode: 200,
                body: JSON.stringify('SUCCESS'),
            };
        }
    });
    return response;
};


chmod 755 test.js
zip test.zip test.js

aws lambda create-function \
--function-name func01 \
--zip-file fileb://test.zip \
--handler test.handler  \
--runtime nodejs14.x  \
--role arn:aws:iam::999999999999:role/role01


aws lambda list-functions | grep func01

aws lambda get-function --function-name func01

 

-- 8. ルールの作成

aws events put-rule \
--name rule01 \
--event-pattern '{"source": ["aws.autoscaling"],"detail-type": ["EC2 Instance-launch Lifecycle Action"]
}' \
--state ENABLED

 

aws events list-rules
aws events describe-rule --name rule01

 

-- 9. ターゲットの作成

aws events put-targets \
--rule rule01 \
--targets "Id"="1","Arn"="arn:aws:lambda:ap-northeast-1:999999999999:function:func01"

aws events list-targets-by-rule \
--rule rule01

 


-- 10. Lambda関数に権限を追加する

aws lambda add-permission \
--function-name func01 \
--statement-id events \
--action lambda:InvokeFunction \
--principal events.amazonaws.com \
--source-arn arn:aws:events:ap-northeast-1:999999999999:rule/rule01

aws lambda get-policy \
--function-name func01 | jq -r .Policy  | jq .

 

-- 11. ライフサイクルフックを追加

aws autoscaling put-lifecycle-hook \
--lifecycle-hook-name lh01 \
--auto-scaling-group-name asg01 \
--lifecycle-transition "autoscaling:EC2_INSTANCE_LAUNCHING" \
--heartbeat-timeout 300 \
--default-result "ABANDON"

 

aws autoscaling describe-lifecycle-hooks \
--auto-scaling-group-name asg01


-- 12. 動作確認

aws autoscaling describe-auto-scaling-groups

aws autoscaling update-auto-scaling-group \
--auto-scaling-group-name asg01 \
--max-size 2 \
--desired-capacity 2

 


-- 13. クリーンアップ


-- ライフサイクルフックの削除
aws autoscaling describe-lifecycle-hooks \
--auto-scaling-group-name asg01

 

aws autoscaling delete-lifecycle-hook \
--auto-scaling-group-name asg01 \
--lifecycle-hook-name lh01

-- ターゲットの削除
aws events list-targets-by-rule \
--rule rule01

aws events remove-targets \
--rule rule01 \
--ids 1


-- ルールの削除
aws events list-rules

aws events delete-rule \
--name rule01

-- Lambda関数の削除
aws lambda get-function --function-name func01
aws lambda delete-function --function-name func01

-- IAMロールの削除
aws iam list-roles | grep role01

aws iam detach-role-policy \
--role-name role01 \
--policy-arn arn:aws:iam::999999999999:policy/policy01

aws iam detach-role-policy \
--role-name role01 \
--policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole


aws iam delete-role --role-name role01


-- IAMポリシーの削除
aws iam list-policies | grep policy01

aws iam delete-policy \
--policy-arn arn:aws:iam::999999999999:policy/policy01

-- オートスケーリンググループの削除

aws autoscaling describe-auto-scaling-groups


aws autoscaling delete-auto-scaling-group \
--auto-scaling-group-name asg01 --force-delete 


-- 起動テンプレートの削除

aws ec2 describe-launch-templates

aws ec2 delete-launch-template \
--launch-template-name lt01

 

{Auto Scaling}チュートリアル: インスタンスメタデータを使用してターゲットライフサイクル状態を取得するようにユーザーデータを設定する

https://docs.aws.amazon.com/ja_jp/autoscaling/ec2/userguide/tutorial-lifecycle-hook-instance-metadata.html

-- 1. コマンド等のインストール

-- 1.1 aws cli version 2 インストール

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
aws --version

-- 1.2 jqインストール
sudo yum -y install jq

 

-- 2. IAMポリシー作成
vim policy01.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "autoscaling:CompleteLifecycleAction"
      ],
      "Resource": "arn:aws:autoscaling:*:999999999999:autoScalingGroup:*:autoScalingGroupName/asg01"
    }
  ]
}


aws iam create-policy \
--policy-name policy01 \
--policy-document file://policy01.json

-- 3. IAMロール作成
vim role01.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

aws iam create-role \
--role-name role01 \
--assume-role-policy-document file://role01.json

-- 4. ポリシーをロールにアタッチ
aws iam attach-role-policy \
--policy-arn arn:aws:iam::999999999999:policy/policy01 \
--role-name role01

 

-- 5. インスタンスプロファイルを作成
aws iam create-instance-profile --instance-profile-name profile01

aws iam list-instance-profiles | grep InstanceProfileName

 

-- 6. インスタンスプロファイルにロールを追加
aws iam add-role-to-instance-profile --instance-profile-name profile01 --role-name role01

aws iam list-instance-profiles-for-role --role-name role01

 

-- 7. 起動テンプレートの作成

ユーザデータのbase64-encoded textを取得

vim userdata.sh

--------

#!/bin/bash

function get_target_state {
    echo $(curl -s http://169.254.169.254/latest/meta-data/autoscaling/target-lifecycle-state)
}

function get_instance_id {
    echo $(curl -s http://169.254.169.254/latest/meta-data/instance-id)
}

function complete_lifecycle_action {
    instance_id=$(get_instance_id)
    group_name='asg01'
    region='ap-northeast-1'
 
    echo $instance_id
    echo $region
    echo $(aws autoscaling complete-lifecycle-action \
      --lifecycle-hook-name lh01 \
      --auto-scaling-group-name $group_name \
      --lifecycle-action-result CONTINUE \
      --instance-id $instance_id \
      --region $region)
}

function main {
    while true
    do
        target_state=$(get_target_state)
        if [ \"$target_state\" = \"InService\" ]; then
            # Change hostname
            export new_hostname="${group_name}-$instance_id"
            hostname $new_hostname
            # Send callback
            complete_lifecycle_action
        fi
        echo $target_state
        sleep 5
    done
}

main

--------
cat  userdata.sh | base64


vim a.json

{
  "IamInstanceProfile": {
    "Arn": "arn:aws:iam::999999999999:instance-profile/profile01"
  },
  "ImageId": "ami-02c3627b04781eada",
  "InstanceType": "t3.nano",
  "UserData": "IyEvYmluL2Jhc2gKCmZ1bmN0aW9uIGdldF90YXJnZXRfc3RhdGUgewogICAgZWNobyAkKGN1cmwgLXMgaHR0cDovLzE2OS4yNTQuMTY5LjI1NC9sYXRlc3QvbWV0YS1kYXRhL2F1dG9zY2FsaW5nL3RhcmdldC1saWZlY3ljbGUtc3RhdGUpCn0KCmZ1bmN0aW9uIGdldF9pbnN0YW5jZV9pZCB7CiAgICBlY2hvICQoY3VybCAtcyBodHRwOi8vMTY5LjI1NC4xNjkuMjU0L2xhdGVzdC9tZXRhLWRhdGEvaW5zdGFuY2UtaWQpCn0KCmZ1bmN0aW9uIGNvbXBsZXRlX2xpZmVjeWNsZV9hY3Rpb24gewogICAgaW5zdGFuY2VfaWQ9JChnZXRfaW5zdGFuY2VfaWQpCiAgICBncm91cF9uYW1lPSdhc2cwMScKICAgIHJlZ2lvbj0nYXAtbm9ydGhlYXN0LTEnCiAKICAgIGVjaG8gJGluc3RhbmNlX2lkCiAgICBlY2hvICRyZWdpb24KICAgIGVjaG8gJChhd3MgYXV0b3NjYWxpbmcgY29tcGxldGUtbGlmZWN5Y2xlLWFjdGlvbiBcCiAgICAgIC0tbGlmZWN5Y2xlLWhvb2stbmFtZSBsaDAxIFwKICAgICAgLS1hdXRvLXNjYWxpbmctZ3JvdXAtbmFtZSAkZ3JvdXBfbmFtZSBcCiAgICAgIC0tbGlmZWN5Y2xlLWFjdGlvbi1yZXN1bHQgQ09OVElOVUUgXAogICAgICAtLWluc3RhbmNlLWlkICRpbnN0YW5jZV9pZCBcCiAgICAgIC0tcmVnaW9uICRyZWdpb24pCn0KCmZ1bmN0aW9uIG1haW4gewogICAgd2hpbGUgdHJ1ZQogICAgZG8KICAgICAgICB0YXJnZXRfc3RhdGU9JChnZXRfdGFyZ2V0X3N0YXRlKQogICAgICAgIGlmIFsgXCIkdGFyZ2V0X3N0YXRlXCIgPSBcIkluU2VydmljZVwiIF07IHRoZW4KICAgICAgICAgICAgIyBDaGFuZ2UgaG9zdG5hbWUKICAgICAgICAgICAgZXhwb3J0IG5ld19ob3N0bmFtZT0iJHtncm91cF9uYW1lfS0kaW5zdGFuY2VfaWQiCiAgICAgICAgICAgIGhvc3RuYW1lICRuZXdfaG9zdG5hbWUKICAgICAgICAgICAgIyBTZW5kIGNhbGxiYWNrCiAgICAgICAgICAgIGNvbXBsZXRlX2xpZmVjeWNsZV9hY3Rpb24KICAgICAgICBmaQogICAgICAgIGVjaG8gJHRhcmdldF9zdGF0ZQogICAgICAgIHNsZWVwIDUKICAgIGRvbmUKfQoKbWFpbgo=",
  "SecurityGroupIds": ["sg-11111111111111111"]
}


aws ec2 create-launch-template \
--launch-template-name lt01 \
--launch-template-data file://a.json

 

aws ec2 describe-launch-templates


aws ec2 describe-launch-template-versions --launch-template-id lt-33333333333333333

 

-- 8. オートスケーリンググループの作成


aws autoscaling create-auto-scaling-group \
--auto-scaling-group-name asg01 \
--launch-template '{
                "LaunchTemplateName": "lt01",
                "Version": "$Default"
            }' \
--min-size 1 \
--max-size 1 \
--desired-capacity 1 \
--default-cooldown 300 \
--health-check-type "EC2" \
--health-check-grace-period 300 \
--vpc-zone-identifier "subnet-22222222222222222" \
--no-new-instances-protected-from-scale-in

 

 

aws autoscaling describe-auto-scaling-groups

 


-- 9. ライフサイクルフックを追加

aws autoscaling put-lifecycle-hook \
--lifecycle-hook-name lh01 \
--auto-scaling-group-name asg01 \
--lifecycle-transition "autoscaling:EC2_INSTANCE_LAUNCHING" \
--heartbeat-timeout 300 \
--default-result "ABANDON"

 

aws autoscaling describe-lifecycle-hooks \
--auto-scaling-group-name asg01

 

-- 10. 機能をテストして検証する


aws autoscaling describe-auto-scaling-groups

aws autoscaling update-auto-scaling-group \
--auto-scaling-group-name asg01 \
--max-size 2 \
--desired-capacity 2

 

-- 11. クリーンアップ

-- ライフサイクルフックの削除
aws autoscaling describe-lifecycle-hooks \
--auto-scaling-group-name asg01

 

aws autoscaling delete-lifecycle-hook \
--auto-scaling-group-name asg01 \
--lifecycle-hook-name lh01


-- オートスケーリンググループの削除

aws autoscaling describe-auto-scaling-groups


aws autoscaling delete-auto-scaling-group \
--auto-scaling-group-name asg01 --force-delete 

 


-- 起動テンプレートの削除

aws ec2 describe-launch-templates

aws ec2 delete-launch-template \
--launch-template-name lt01


-- インスタンスプロファイルの削除

aws iam remove-role-from-instance-profile --instance-profile-name profile01 --role-name role01


aws iam delete-instance-profile --instance-profile-name profile01

aws iam list-instance-profiles | grep InstanceProfileName

-- IAMロールの削除
aws iam list-roles | grep role01

aws iam detach-role-policy \
--role-name role01 \
--policy-arn arn:aws:iam::999999999999:policy/policy01

aws iam delete-role --role-name role01


-- IAMポリシーの削除
aws iam list-policies | grep policy01

aws iam delete-policy \
--policy-arn arn:aws:iam::999999999999:policy/policy01

 

 

{CloudWatch}複合アラームの作成

https://docs.aws.amazon.com/ja_jp/AmazonCloudWatch/latest/monitoring/Create_Composite_Alarm.html


-- 1. コマンド等のインストール

-- 1.1 aws cli version 2 インストール

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
aws --version

-- 1.2 jqインストール
sudo yum -y install jq

 

-- 2. SNSトピック作成

aws sns list-topics
aws sns list-subscriptions

aws sns create-topic --name topic01

aws sns subscribe \
--topic-arn arn:aws:sns:ap-northeast-1:999999999999:topic01 \
--protocol email \
--notification-endpoint hoge@example.com

 

-- 3. 複合アラームを作成


aws cloudwatch put-metric-alarm \
--alarm-name alarm01 \
--alarm-description "alarm01" \
--metric-name CPUUtilization \
--namespace AWS/EC2 \
--statistic Average \
--period 300 \
--threshold 30.0 \
--comparison-operator GreaterThanOrEqualToThreshold \
--dimensions '[
                {
                    "Name": "InstanceId",
                    "Value": "i-11111111111111111"
                }
            ]' \
--evaluation-periods 1 \
--datapoints-to-alarm 1 \
--treat-missing-data missing


aws cloudwatch put-metric-alarm \
--alarm-name alarm02 \
--alarm-description "alarm02" \
--metric-name EBSWriteBytes \
--namespace AWS/EC2 \
--statistic Average \
--period 300 \
--threshold 100000.0 \
--comparison-operator GreaterThanOrEqualToThreshold \
--dimensions '[
                {
                    "Name": "InstanceId",
                    "Value": "i-11111111111111111"
                }
            ]' \
--evaluation-periods 1 \
--datapoints-to-alarm 1 \
--treat-missing-data missing

 

aws cloudwatch put-composite-alarm \
--actions-enabled \
--alarm-actions arn:aws:sns:ap-northeast-1:999999999999:topic01 \
--alarm-description "alarm03" \
--alarm-name alarm03 \
--alarm-rule "ALARM("alarm01") AND ALARM("alarm02")"

 

aws cloudwatch describe-alarms


※管理者権限があるが、複合アラームがdescribe-alarmsで表示されない
「cloudwatch:DescribeAlarms」権限を付与しても変わらず

 

 

-- 4. 複合アラームをテスト

aws cloudwatch set-alarm-state \
--alarm-name alarm03 \
--state-reason "OK" \
--state-value OK

 

aws cloudwatch set-alarm-state \
--alarm-name alarm03 \
--state-reason "ALARM" \
--state-value ALARM

aws cloudwatch set-alarm-state \
--alarm-name alarm03 \
--state-reason "INSUFFICIENT_DATA" \
--state-value INSUFFICIENT_DATA


-- 5. クリーンアップ


-- アラームの削除

aws cloudwatch describe-alarms


aws cloudwatch delete-alarms \
--alarm-names alarm03

aws cloudwatch delete-alarms \
--alarm-names alarm02

aws cloudwatch delete-alarms \
--alarm-names alarm01


-- SNSトピック削除

aws sns unsubscribe --subscription-arn arn:aws:sns:ap-northeast-1:999999999999:topic01:11111111-2222-3333-4444-555555555555
aws sns delete-topic --topic-arn arn:aws:sns:ap-northeast-1:999999999999:topic01


aws sns list-topics
aws sns list-subscriptions

 

{ALB}固定レスポンス機能

https://dev.classmethod.jp/articles/alb-fixed-response/


-- 1. コマンド等のインストール

-- 1.1 aws cli version 2 インストール

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install

aws --version

-- 1.2 jqインストール
sudo yum -y install jq

 

-- 2. ロードバランサーの作成


aws elbv2 create-load-balancer \
--name alb01  \
--subnets subnet-11111111111111111  subnet-22222222222222222 \
--security-groups sg-33333333333333333


aws elbv2 describe-load-balancers
aws elbv2 describe-load-balancers| jq -r .LoadBalancers.LoadBalancerArn

 


-- 3. リスナーの作成

aws elbv2 create-listener \
--load-balancer-arn arn:aws:elasticloadbalancing:ap-northeast-1:999999999999:loadbalancer/app/alb01/4444444444444444 \
--protocol HTTP \
--port 80  \
--default-actions '[
  {
      "Type": "fixed-response",
      "FixedResponseConfig": {
          "StatusCode": "200",
          "ContentType": "text/plain",
          "MessageBody": "Hello world"
      }
  }
]'

 


aws elbv2 describe-listeners \
--load-balancer-arn arn:aws:elasticloadbalancing:ap-northeast-1:999999999999:loadbalancer/app/alb01/4444444444444444

aws elbv2 describe-listeners \
--load-balancer-arn arn:aws:elasticloadbalancing:ap-northeast-1:999999999999:loadbalancer/app/alb01/4444444444444444 | jq -r .Listeners.ListenerArn

 

 

-- 4. 動作確認


http://alb01-6666666666.ap-northeast-1.elb.amazonaws.com

 

 

-- 5. クリーンアップ

 

-- リスナーの削除

aws elbv2 describe-listeners \
--load-balancer-arn arn:aws:elasticloadbalancing:ap-northeast-1:999999999999:loadbalancer/app/alb01/4444444444444444


aws elbv2 delete-listener \
--listener-arn arn:aws:elasticloadbalancing:ap-northeast-1:999999999999:listener/app/alb01/4444444444444444/5555555555555555

 

-- ロードバランサーの削除

aws elbv2 describe-load-balancers

aws elbv2 delete-load-balancer \
--load-balancer-arn arn:aws:elasticloadbalancing:ap-northeast-1:999999999999:loadbalancer/app/alb01/4444444444444444

 

 

 

 

{VPC}クロスリージョントランジットゲートウェイ

https://docs.aws.amazon.com/ja_jp/vpc/latest/tgw/transit-gateway-peering-scenario.html
https://docs.aws.amazon.com/ja_jp/vpc/latest/tgw/tgw-peering.html


前提: 
東京リージョンと大阪リージョンで以下を設定済み

サブネット作成
東京リージョン -> 172.31.48.0/24
大阪リージョン -> 10.0.1.0/24

作成したサブネットにEC2インスタンス作成
(セキュリティグループはping通信許可)

 

 

-- 1. コマンド等のインストール

-- 1.1 aws cli version 2 インストール

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
aws --version


-- 1.2 jqインストール
sudo yum -y install jq

 

-- 2. Transit Gateway作成 [ 東京リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-1

aws ec2 describe-transit-gateways

 

aws ec2 create-transit-gateway \
--options '{
  "AmazonSideAsn": 64512,
  "AutoAcceptSharedAttachments": "enable",
  "DefaultRouteTableAssociation": "enable",
  "DefaultRouteTablePropagation": "enable",
  "VpnEcmpSupport": "enable",
  "DnsSupport": "enable",
  "MulticastSupport": "disable"
}' \
--tag-specifications '[
  {
    "ResourceType": "transit-gateway",
    "Tags": [ {"Key": "Name", "Value" : "tgw01" } ]
  }
]'

 


-- 3. Transit Gatewayアタッチメントの作成 [ 東京リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-1

aws ec2 describe-transit-gateway-attachments
aws ec2 describe-transit-gateway-vpc-attachments
aws ec2 describe-transit-gateway-peering-attachments
aws ec2 describe-transit-gateway-route-tables

aws ec2 create-transit-gateway-vpc-attachment \
--transit-gateway-id tgw-00000000000000000 \
--vpc-id vpc-11111111111111111 \
--subnet-ids subnet-22222222222222222 \
--options '{
  "DnsSupport": "enable",
  "Ipv6Support": "disable",
  "ApplianceModeSupport": "disable"
}' \
--tag-specifications '[
  {
    "ResourceType": "transit-gateway-attachment",
    "Tags": [ {"Key": "Name", "Value" : "tgwa01" } ]
  }
]'

 

-- 4. Transit Gateway作成 [ 大阪リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-3

aws ec2 describe-transit-gateways

 

aws ec2 create-transit-gateway \
--options '{
  "AmazonSideAsn": 64512,
  "AutoAcceptSharedAttachments": "enable",
  "DefaultRouteTableAssociation": "enable",
  "DefaultRouteTablePropagation": "enable",
  "VpnEcmpSupport": "enable",
  "DnsSupport": "enable",
  "MulticastSupport": "disable"
}' \
--tag-specifications '[
  {
    "ResourceType": "transit-gateway",
    "Tags": [ {"Key": "Name", "Value" : "tgw02" } ]
  }
]'

 

 

-- 5. Transit Gatewayアタッチメントの作成 [ 大阪リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-3

aws ec2 describe-transit-gateway-attachments
aws ec2 describe-transit-gateway-vpc-attachments
aws ec2 describe-transit-gateway-peering-attachments
aws ec2 describe-transit-gateway-route-tables


aws ec2 create-transit-gateway-vpc-attachment \
--transit-gateway-id tgw-33333333333333333 \
--vpc-id vpc-44444444444444444 \
--subnet-ids subnet-55555555555555555 \
--options '{
  "DnsSupport": "enable",
  "Ipv6Support": "disable",
  "ApplianceModeSupport": "disable"
}' \
--tag-specifications '[
  {
    "ResourceType": "transit-gateway-attachment",
    "Tags": [ {"Key": "Name", "Value" : "tgwa02" } ]
  }
]'

 


-- 6. Transit Gateway ピアリングアタッチメントの作成 [ 東京リージョンでの作業、大阪リージョンでの作業 ]

ピアリングアタッチメントをアクティブにするには、アクセプタ Transit Gateway の所有者がピアリングアタッチメントリクエストを受け入れる必要があります。
これは、両方の Transit Gateway が同じアカウントにある場合でも必要です。


export AWS_DEFAULT_REGION=ap-northeast-1

aws ec2 describe-transit-gateway-attachments
aws ec2 describe-transit-gateway-vpc-attachments
aws ec2 describe-transit-gateway-peering-attachments
aws ec2 describe-transit-gateway-route-tables


aws ec2 create-transit-gateway-peering-attachment \
--transit-gateway-id tgw-00000000000000000 \
--peer-transit-gateway-id tgw-33333333333333333 \
--peer-account-id 999999999999 \
--peer-region ap-northeast-3 \
--tag-specifications '[
  {
    "ResourceType": "transit-gateway-attachment",
    "Tags": [ {"Key": "Name", "Value" : "tgwpa01" } ]
  }
]'

export AWS_DEFAULT_REGION=ap-northeast-3

aws ec2 accept-transit-gateway-peering-attachment \
--transit-gateway-attachment-id tgw-attach-66666666666666666


-- 7. Transit Gatewayのルートテーブルに経路追加 [ 東京リージョン、大阪リージョンでの作業 ]

ピアリングされた Transit Gateway 間でトラフィックをルーティングするには、
Transit Gateway のピアリングアタッチメントをポイントする静的ルートを Transit Gateway のルートテーブルに追加する必要があります。


export AWS_DEFAULT_REGION=ap-northeast-1

aws ec2 create-transit-gateway-route \
--destination-cidr-block 10.0.1.0/24 \
--transit-gateway-route-table-id tgw-rtb-77777777777777777 \
--transit-gateway-attachment-id tgw-attach-66666666666666666

 


export AWS_DEFAULT_REGION=ap-northeast-3

aws ec2 create-transit-gateway-route \
--destination-cidr-block 172.31.48.0/24  \
--transit-gateway-route-table-id tgw-rtb-88888888888888888 \
--transit-gateway-attachment-id tgw-attach-66666666666666666

 


-- 8. サブネットのルートテーブルに経路追加 [ 東京リージョン、大阪リージョンでの作業 ]

大阪リージョン:
 172.31.48.0/24 -> TGW

 

東京リージョン:
 10.0.1.0/24 -> TGW

 

-- 9. 動作確認  [ 東京リージョンでの作業 ]

ping 10.0.1.150

 

-- 10. クリーンアップ


-- Transit Gateway ピアリングアタッチメントの削除  [ 東京リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-1

aws ec2 describe-transit-gateway-attachments
aws ec2 describe-transit-gateway-vpc-attachments
aws ec2 describe-transit-gateway-peering-attachments
aws ec2 describe-transit-gateway-route-tables


aws ec2 delete-transit-gateway-peering-attachment \
--transit-gateway-attachment-id tgw-attach-66666666666666666

 

-- Transit Gatewayアタッチメントの削除 [ 大阪リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-3

aws ec2 describe-transit-gateway-attachments
aws ec2 describe-transit-gateway-vpc-attachments
aws ec2 describe-transit-gateway-peering-attachments
aws ec2 describe-transit-gateway-route-tables

aws ec2 delete-transit-gateway-vpc-attachment \
--transit-gateway-attachment-id tgw-attach-aaaaaaaaaaaaaaaaa

 

-- Transit Gatewayの削除 [ 大阪リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-3

aws ec2 describe-transit-gateways

aws ec2 delete-transit-gateway \
--transit-gateway-id tgw-33333333333333333


-- Transit Gatewayアタッチメントの削除 [ 東京リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-1

aws ec2 describe-transit-gateway-attachments
aws ec2 describe-transit-gateway-vpc-attachments
aws ec2 describe-transit-gateway-peering-attachments
aws ec2 describe-transit-gateway-route-tables

aws ec2 delete-transit-gateway-vpc-attachment \
--transit-gateway-attachment-id tgw-attach-bbbbbbbbbbbbbbbbb

 

-- Transit Gatewayの削除 [ 東京リージョンでの作業 ]

export AWS_DEFAULT_REGION=ap-northeast-1

aws ec2 describe-transit-gateways

aws ec2 delete-transit-gateway \
--transit-gateway-id tgw-00000000000000000