我需要实现的是具有Lambda函数来创建EBS卷,将其附加到EC2实例,对其进行格式化并将其安装在/data
目录下。
我正在使用ssm:RunCommand
(client.send_command
)执行应该格式化和装入卷的Shell脚本,但是代码失败,因为在我调用RunCommand时卷尚未附加到实例上
我正在使用EC2.Waiter.VolumeInUse
等到卷连接好之后,但看来它无法正常工作。
这是我的代码
import boto3
# HARDCODED VALUES FOR TESTING
AVAILABILITY_ZONE = 'us-east-1d'
INSTANCE_ID = 'i-0bd640b495fd7d77c'
ec2_client = boto3.client('ec2')
ssm_client = boto3.client('ssm')
volume_available_waiter = ec2_client.get_waiter('volume_available')
volume_attached_waiter = ec2_client.get_waiter('volume_in_use')
def lambda_handler(event, context):
try:
# create 8 GB general purpose volume in given AZ
create_volume_response = ec2_client.create_volume(
AvailabilityZone=AVAILABILITY_ZONE,
Size=8,
VolumeType='gp2'
)
# retrieve volume id and wait till it is available
volume_id = create_volume_response['VolumeId']
volume_available_waiter.wait(
VolumeIds=[volume_id]
)
# attach newly created volume to a given instance
ec2_client.attach_volume(
Device='/dev/xvdh',
InstanceId=INSTANCE_ID,
VolumeId=volume_id
)
# wait till the volume is properly attached to EC2 instance
volume_attached_waiter.wait(
VolumeIds=[volume_id]
)
# use SSM RunCommand to format and mount volume
ssm_client.send_command(
InstanceIds=[INSTANCE_ID],
DocumentName='AWS-RunShellScript',
Parameters={
'commands': [
'echo "STARTING MOUNT SEQUENCE"'
'echo $(lsblk)'
'mkfs -t xfs /dev/xvdh',
'mkdir /data',
'mount /dev/xvdh /data'
]
}
)
except Exception as e:
print(e)
return 0
检查日志cat /var/log/messages
时,我可以清楚地看到echo $(lsblk)
的输出中尚未附加新卷。
等待将卷连接到EC2实例的正确方法是什么?
答案 0 :(得分:2)
在这种情况下,正确的方法是等待直到在SSM中附加了卷为止,而不是让lambda挂起并等待。
由于您已经在使用SSM,因此您将需要创建一个SSM Automation document,它将等待卷被附加,然后执行RunCommand来格式化和装入该卷。
您的文档需要添加2个步骤:
1- aws:waitForAwsResourceProperty等到卷连接好
2- aws:runCommand执行您的Shell脚本
首先,创建您的SSM自动化文档:
z
然后,您将需要创建一个IAM Role for SSM,并具有对Runcommand和DescribeVolumes的必需权限。
然后将lambda中的send命令块替换为:
---
description: "Automation Document Example YAML Template"
schemaVersion: "0.3"
assumeRole: "{{ AutomationAssumeRole }}"
parameters:
InstanceId:
type: "String"
description: "(Required) The ID of the EC2 Instance."
VolumeId:
type: "String"
description: "(Required) The ID of the volume."
AutomationAssumeRole:
type: "String"
description: "(Optional) The ARN of the role that allows Automation to perform the actions on your behalf."
default: ""
mainSteps:
- name: "VerifyVolumeAttached"
action: "aws:waitForAwsResourceProperty"
timeoutSeconds: 600
inputs:
Service: "ec2"
Api: "DescribeVolumes"
VolumeIds: ["{{ VolumeId }}"]
PropertySelector: "$.Volumes[0].Attachments[0].State"
DesiredValues:
- "attached"
- name: "MountVolume"
action: "aws:runCommand"
inputs:
DocumentName: "AWS-RunShellScript"
InstanceIds:
- "{{InstanceId}}"
Parameters:
commands: ['echo "STARTING MOUNT SEQUENCE"','echo $(lsblk)','mkfs -t xfs /dev/xvdh','mkdir /data','mount /dev/xvdh /data']