The Platform Orchestrator is specifically designed to seamlessly integrate with managed file storage solutions such as Amazon S3 and Google Cloud Storage. Although many of the required Drivers are currently in the experimental phase, our team conducts thorough testing before releasing them as out-of-the-box integrations. To gain access to these experimental Drivers, please reach out to us.
The following sections present an overview of the integrations that are readily available as out-of-the-box solutions.
You can easily connect to an Amazon S3 bucket.
Add your AWS Account
You can add your AWS Account in the Cloud Accounts screen.
- Click on the Cloud Accounts item from the navigation bar.
- Select Amazon Web Services.
- Humanitec will ask you to provide an Account name (a memorable name that will be displayed for this account), an Access key ID, and a Secret access key (see how to create AWS access key under IAM user).
- Once the account was authorized, it will show up at the top of the accounts list.
Accounts can be added via the Create Resource Account endpoint.
Connect S3 bucket to Humanitec
You can easily connect Humanitec to an Aiven managed database instance. The following paragraph explains how.
- Start on the Resources Management screen and select Add resource definition. An overlay with all available resource categories and types will be presented to you.
- Below Data storages click on s3 Bucket, which opens a dialog box.
- Select a resource driver. Based on the selected driver, a form will be shown with the required Driver parameters which will be passed to the Driver on every resource creation.
- Below Credentials make sure your AWS account is selected.
- In this use case, the region is a mandatory Driver value and it must match the region that your AWS account has access to.
- Fill out the remaining connection parameters.
- After clicking on Add S3 Bucket the S3 bucket will be successfully registered in Humanitec and show up at the top of the resource list.
Resource definitions can be created through the Create Dynamic Resource endpoint.
Next, you can configure matching criteria for your s3 bucket resource. This enables you to define specific environments or Applications to be deployed to this resource.
- Click on an existing S3 bucket Resource Definition.
- On the Resource Definition details screen select the Matching criteria tab.
- Click on Add new criteria.
- Define Matching Criteria. Each s3 bucket resource can be matched to specific Environment Types, App IDs, Environment IDs or Resource IDs. Empty fields are automatically resolved to match all values of the given category.
Based on this Resource Definition, during the deployment on any of the matching applications or environments, an Active Resource will be provisioned if required.
Matching criteria can be created via the Create new Matching Criteria endpoint.