Amazon MWAA variables
Airflow variables on one MWAA environment. Values are written, never read back.
Airflow variables on one MWAA environment. Values are written, never read back.
The connection
| What | This provider |
|---|---|
| Vendor | Amazon Web Services |
| Key | mwaa-airflow-variables |
| Availability | available. You can connect it today. |
| Credential penv holds | aws-role |
| Values read back | no |
| Activation | immediate |
What it moves
| Direction | What it does |
|---|---|
export | Writes names and values from penv into the store. |
Amazon Web Services returns no value once it holds one, so penv can write here and cannot read back.
When a written value goes live
immediate. The running app sees a new value at once.
What happens to a name that exists
| Direction | Policies you can pick |
|---|---|
export | create_only, overwrite, overwrite_and_prune |
How syncs work says what each one does.
How you connect
You grant penv access in your own AWS account. Pick one of these in the wizard.
penv generates the shared value the grant is conditioned on, so there is nothing for you to invent.
Terraform: recommended, the grant is reviewable before it exists
Review the grant in code, then paste the role ARN back. Apply a rendered policy or template. You paste the result back into the wizard.
Set aside about 10 minutes.
- Add the snippet to your AWS account's Terraform and apply it.
- Paste the
penv_role_arnoutput back here.
It gives you:
| Name | Label | Kind | What it is |
|---|---|---|---|
snippet | Terraform | read only, a block to copy | |
externalId | External ID | read only, filled in for you | Already baked into the snippet. Only Penv-cloud can assume the role with it. |
You paste back:
| Field | Label | Kind | Required | What it is |
|---|---|---|---|---|
roleArn | Role ARN | text | yes | The ARN the grant printed. We assume it once to check it before saving. |
Manual
Create the role manually from the two policies below. Paste a credential you already hold. You paste the result back into the wizard.
Set aside about 10 minutes.
- In IAM, create a role for another AWS account and paste the trust policy below.
- Attach the permissions policy below as an inline policy.
- Paste the role's ARN back here.
It gives you:
| Name | Label | Kind | What it is |
|---|---|---|---|
penvAccountId | Penv-cloud AWS account ID | read only, filled in for you | The account the role trusts. |
roleName | Suggested role name | read only, filled in for you | Unique to this attempt, so it cannot collide with a role another connection made. |
externalId | External ID | read only, filled in for you | Required in the trust policy. Only Penv-cloud can assume the role with it. |
trustPolicy | Trust policy | read only, a block to copy | |
permissionsPolicy | Permissions policy | read only, a block to copy |
You paste back:
| Field | Label | Kind | Required | What it is |
|---|---|---|---|---|
roleArn | Role ARN | text | yes | The ARN the grant printed. We assume it once to check it before saving. |
What the connection asks for
Fixed when you connect, and shared by every mapping on it.
| Field | Label | Kind | Required | Advanced | What it is |
|---|---|---|---|---|---|
environmentName | Environment | text | yes | no | The MWAA environment this connection may touch. The grant is scoped to it. |
region | Region | text | yes | no | The region this connection reaches. One connection covers one region. |
accountId | Account ID | text | no | yes | If supplied, the generated policy names the account instead of a wildcard. |
roleArn | Role ARN | read only, filled in for you | yes | no | The role we assume. Filled in by the grant you just completed. |
Permissions it needs
penv probes for these when it verifies the connection.
| Permission | Directions | Blocking | Without it |
|---|---|---|---|
sts:GetCallerIdentity | every direction | yes | We cannot confirm which IAM identity this credential is. |
airflow:InvokeRestApi | export | yes | Export cannot reach the Airflow API on this environment. |