prefect-aws
The prefect-aws library makes it easy to leverage the capabilities of AWS in your workflows. For example, you can retrieve secrets using AWS Secrets Manager, read and write objects with AWS S3, and deploy your flows on AWS ECS.
Getting started
Prerequisites
- An AWS account and the necessary permissions to access desired services.
Install prefect-aws
The following command will install a version of prefect-aws
compatible with your installed version of prefect
.
If you don’t already have prefect
installed, it will install the newest version of prefect
as well.
Upgrade to the latest versions of prefect
and prefect-aws
:
Register newly installed block types
Register the block types in the prefect-aws
module to make them available for use.
Examples
Run flows on AWS ECS
Run flows on AWS Elastic Container Service (ECS) to dynamically scale your infrastructure.
See the ECS work pool docs for a walkthrough of using ECS in a hybrid work pool.
If you’re using Prefect Cloud, ECS push work pools provide all the benefits of ECS with a quick setup and no worker needed.
In the examples below, you create blocks with Python code. Alternatively, each block can be created through the Prefect UI.
Save credentials to an AWS Credentials block
Use of most AWS services requires an authenticated session. Prefect makes it simple to provide credentials via a AWS Credentials block.
Steps:
- Refer to the AWS Configuration documentation to retrieve your access key ID and secret access key.
- Copy the access key ID and secret access key.
- Create an
AwsCredentials
block in the Prefect UI or use a Python script like the one below.
Prefect is using the Boto3 library under the hood. To find credentials for authentication, any data not provided to the block are sourced at runtime in the order shown in the Boto3 docs. Prefect creates the session object using the values in the block and then, any missing values follow the sequence in the Boto3 docs.
See an example of using the AwsCredentials
block with AWS Secrets Manager with third-party services without storing credentials in the block itself in the docs.
Here’s how to load the saved credentials:
The AWS Credentials block is often nested within other blocks, such as S3Bucket
or AwsSecret
, and provides authentication for those services.
Read and write files to AWS S3
Upload a file to an AWS S3 bucket and download the same file under a different filename. The following code assumes that the bucket already exists:
Access secrets with AWS Secrets Manager
Write a secret to AWS Secrets Manager, read the secret data, delete the secret, and return the secret data.
Resources
For assistance using AWS, consult the AWS documentation and, in particular, the Boto3 documentation.
Refer to the prefect-aws
SDK documentation linked in the sidebar to explore all the capabilities of the prefect-aws
library.
Was this page helpful?