Upgrade to Pro — share decks privately, control downloads, hide ads and more …

ECS EBS integation の概要、ユースケース

clouddev-code
March 04, 2024
280

ECS EBS integation の概要、ユースケース

clouddev-code

March 04, 2024
Tweet

Transcript

  1. ECS EBS Integrationの考慮事項 • ( EC2 launch type ) Nitro-base

    Linux instances • (Fargate launch type) platform version 1.4.0 • ( EC2 launch type ) ECS-Optimized AMI 20231219 or later • magnetic EBS Volume type not supported • attach at most one Amazon EBS volume • snapshot of an Amazon EBS that contains partitions not supported • Task がterminateしたら、EBSも削除される https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_data_volumes.html 9
  2. ECS EBS Integrationなかったときどうしていたか • Amazon EFS – EBSに比べて、IO性能はもちろんでない • S3

    Express one zone – ML 用途なら、mount point of S3も使えるが、IO 性能は犠牲になる 12
  3.  KubernetesのVolumesの類似機能 • Persistent Volumesのsnapshotからのプロビジョニ ング • snapshot size未満のディスクプロビジョニングは不 可 •

    snapshot size以上は可 • オンライン拡張も可 https://kubernetes.io/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-sup port 13
  4.  volumeConfigrations • どのvolumeを使うか指定する • L3 Constructsは対応してなさそう Invalid request provided: CreateService

    error: The volume name 'ebs1' in your request does not have a matching volume in your Task Definition that is configurable at launch. (Service: AmazonECS; StatusCode: 400; Error Code: InvalidParameterException; Request ID: 811742b3-0288-4b4c-80a1-b86ffa9e9047; Proxy: null 16
  5. 21