Channels
pacc-may-31-2023
prefect-ai
pacc-clearcover-june-12-2023
marvin-in-the-wild
data-ecosystem
geo-israel
geo-japan
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
prefect-community
data-tricks-and-tips
prefect-aws
prefect-gcp
introductions
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-server
prefect-ui
prefect-kubernetes
Title
a
Andrei Tulbure
10/28/2022, 8:25 AMHi. Does anybody had any issues with Prefect 1.x ECS deployment ? Regarding the flow register not having the Fargate machine you requested ? I registered 16vCPU and have in the task definition only a 2vCPU machine. Spoke with AWS support but it was not helpful and our AWS Account does have a vCPU limit at 2000. So enough bandwidth.
m
Mason Menges
10/28/2022, 9:31 PMHey @Andrei Tulbure Would you be able to provide the output you're seeing when you're attempting to register the flow?
a
Andrei Tulbure
10/29/2022, 12:20 PM@Mason Menges no issues with registering. It registers and it works. It`s just that in the task definition the machine appears as a 2vCPU one, while I Register it as a 16vCPU one. Hence, which output do you need ? The one in the PRefect UI after it starts running? Sorry but I am kind of a newbie to prefect
z
Zanie
10/31/2022, 4:28 PMDepending on the mode (Fargate, EC2), we request the CPU at the task run level instead of the task definition level.
In [5]: print(ECSTask(command=["prefect", "version"], cpu=16).preview())
---
# Task definition
containerDefinitions:
- image: prefecthq/prefect:dev-python3.8
name: prefect
cpu: '16'
family: prefect
memory: '2048'
networkMode: awsvpc
requiresCompatibilities:
- FARGATE
---
# Task run request
launchType: FARGATE
networkConfiguration:
awsvpcConfiguration:
assignPublicIp: ENABLED
subnets: <loaded from the default VPC at runtime>
overrides:
containerOverrides:
- command:
- prefect
- version
cpu: 16
environment: []
name: prefect
cpu: '16'
tags: []
taskDefinition: <registered at runtime>a
Andrei Tulbure
11/01/2022, 6:45 PM@Zanie so that means that even though the Task def shows a 2 vCPU machine, if we register it with 16 vCPUs we are using the underlying 16vCPU machinie right ?
z
Zanie
11/01/2022, 7:27 PMI believe that it will set it to 16vCPU at runtime. Can you share the output of a preview?
a
Andrei Tulbure
11/07/2022, 3:00 PMsorry, did not get a notification. I think you are right, it will be set to 16vCPU. What exactly do you mean by preview?
z
Zanie
11/07/2022, 4:45 PMIn my comment above I used the
.preview()