@Kalise Richmond has joined the channel

@Anna Geller has joined the channel

@Mason Menges has joined the channel

@Bianca Hoch has joined the channel

@Jeff Hale has joined the channel

@Khuyen Tran has joined the channel

@Ryan Peden has joined the channel

@Vadym Dytyniak has joined the channel

@Rob Freedy has joined the channel

@Stephen Herron has joined the channel

@Jamie Zieziula has joined the channel

@David Hlavaty has joined the channel

@Claire Herdeman has joined the channel

@Jean Luciano has joined the channel

@Nate has joined the channel

@John Mizerany has joined the channel

@James Sopkin has joined the channel

What's the best way to upload a large file using the S3 block in prefect? It looks like the two options are S3.write_path which expects bytes and means loading the whole thing in memory and put_directory which looks like it uses write_path to do its work. I think maybe I can mmap the file to get adressable bytes object but maybe I am thinking about this all wrong?

this is the apex channel 😉

Hi. I'm running this test code against a docker-compose'd S3 bucket + PrefectHQ Orion server.

with prefect.settings.temporary_settings(updates={prefect.settings.PREFECT_API_URL: prefect_api_url}):

            block = prefect.filesystems.RemoteFileSystem(basepath=f"s3://{bucket_name}/",
                                                         settings={"client_kwargs": {"endpoint_url": endpoint_url}})

            block.save("s3-testbucket", overwrite=True)

            block.register_type_and_schema()

            deployment = prefect.deployments.Deployment.build_from_flow(
                flow=prefect_cc.coreflows.flows.mh_fi_etl_flow.the_flow,
                name=deployment_name,
                storage=block,
                work_queue_name=work_queue_name
            )

            t = deployment.apply()

it's raising

E           prefect.exceptions.PrefectHTTPStatusError: Client error '403 Forbidden' for url '<http://localhost:4200/api/block_types/27b5cbc1-88e9-4378-bd82-3adb9125b432>'
E           Response: {'detail': 'protected block types cannot be updated.'}
E           For more information check: <https://httpstatuses.com/403>

this happens regardless of the

block.register_type_and_schema

or not -- I don't know how to debug -- the offending line is the the line:

deployment.apply()

even this breaks

block = prefect.filesystems.RemoteFileSystem.load("s3-testbucket")
            # leaving the server running and making sure the block exists

            deployment = prefect.deployments.Deployment.build_from_flow(
                flow=prefect_cc.coreflows.flows.mh_fi_etl_flow.the_flow,
                name=deployment_name,
                storage=block,
                work_queue_name=work_queue_name
            )

            t = deployment.apply()

-- both the Block (

s3-testbucket

) and the Flow show up but there is no Deployment or Work Queue

INFO:     172.28.0.1:38624 - "PATCH /block_types/6701d78b-8719-4db5-9303-cfd648460183 HTTP/1.1" 403 Forbidden

-- https://docs.prefect.io/api-ref/rest-api/#/Block%20types/update_block_type_block_types__id__patch -- this is not documented

Hi everyone 👋 My goal is to put Sqlite orion.db in EFS mounted into EC2 instance. It generates an error. Error logs are attached in the thread to keep the channel clean. According to Amazon Elastic File System (Amazon EFS) Now Supports NFSv4 Lock Upgrading and Downgrading it is possible to use Sqlite in EFS. I noticed that in src/prefect/orion/database/configurations.py#L262 you set journal_mode to

WAL

which is not allowed in network file systems. I changed that to

delete

without success - logs do not change. I have seen similar logs to mine here In my project, I have other Sqlite databases in the EFS directory and they work fine.

Hi everyone. First off @Anna Geller (and the rest of the team) thanks for all the work you’ve put into the templating at anna-geller/dataflow-ops 🙌 I am trying to run the flow and I’ve been able to solve most small issues so far. However, at the Prefect Blocks & S3 Upload I am getting an error that I can’t seem to solve. I think its might be a IAM role issue, but the AWS Access is set generously to FullS3. The run fails at

Upload to S3 - maintenance flow

with a permission error.

botocore.exceptions.ClientError: An error occurred (AccessDenied) when calling the PutObject operation: Access Denied

I checked the permissions of

dataflowops_ecs_task_role

and it does have full access to S3

"s3:*"

Hi all, I have a question about using the ECS Task block in prefect2. I've got it working, but I'm trying to figure out how to scale this out to multiple ECS Task blocks (where each block references a different image in ECR). The ECS task block is creating a new revision of the hardcoded "prefect" task definition every time a flow running on ECS infra is executed. Is it intentional that the same "prefect" task definition is continually re-revised with different image references + container configs according to whichever ECS Task block was most recently called?

I’m trying to work out how to run a specific kind of workflow in ECS. The documentation for the ECSTask infrastructure mentions:

• You must configure remote Storage. Local storage is not supported for ECS tasks. The most commonly used type of storage with

ECSTask

is S3. If you leverage that type of block, make sure that

s3fs

is installed within your agent and flow run environment. The easiest way to satisfy all the installation-related points mentioned above is to include the following commands in your Dockerfile:

Normally, I run flows that are stored within the same Docker image that contains the agent, and it looks like the

DockerContainer

and

KubernetesJob

infrastructures both support this (I primarily use

KubernetesJob

and

Process

infra atm): https://prefect-community.slack.com/archives/CL09KU1K7/p1666879201904529 It seems like it should be possible to run flows directly within the agent container on ECS: https://prefect-community.slack.com/archives/CL09KU1K7/p1665145511193949?thread_ts=1665144718.756049&cid=CL09KU1K7, but I see that the example in dataflow-ops utilizes S3 storage. If possible, I would like to just run flows within the agent container itself on ECS and specify that the code is there too - is there a way to specify for ECS that the flow code is inside the image that’s being run? If not, is this on the roadmap anywhere? Thanks for reading :)

Hey! I'm working through this template to get an agents up and running as ECS Service. I've got it running and the agent successfully created the work queue in our Prefect Cloud account. However, the agent logs say that the agent is checking for flow runs, but the work queue in Prefect Cloud is "Unhealthy" and says that the queue has never been polled. Could you help me understand how work queues send and receive updates from the agent? Since the command to create the queue was able to get out, I'm guessing that the issue has to do with our security infrastructure and our rules for inbound traffic. Understanding the communication would help us debug. Thank you!

hi all, I'm trying to create a Prefect deployment from a custom Docker image and get this error when running it

botocore.exceptions.ClientError: An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied

. It is uploading the file correctly, and even the image is building correctly but it is failing when I run the flow from the UI. From what I understand in the error message, when running the flow from the docker image, it can't access S3 to read the code. Here are a few more details: • Storage block --> S3. It uploads correctly • Docker image --> Custom image retrieved from ECR • Code --> It is the same code I use in other non-dockerized deployment. • The EC2 instances for the Prefect Agent, Prefect Server and S3 Bucket are all in the same AWS account • The EC2 instance for the PrefectAgent has S3 full access (should the EC2 instance for the Prefect Server also have full S3 access?) I leave in the image below with the full error I get in the Prefect UI and in the Agent's terminal. I saw a similar

AccessDenied

error in this channel when trying to upload the code to S3 but this seems different. The problem is when the flow is running in docker and can't retrieve the code. Any ideas why this could be? Thanks a lot for your help!

Hey! A question about using a

task_definition_arn

in an

ECSTask

block, details below

Has anyone had any luck creating a

DockerRegistry

block with AWS ECR?

Hey! One more issue I'm running into with infra deployment on an agent as a service, details in 🧵