Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(*): add more explanation when using EKS IRSA to access RDS database #5831

Merged
merged 2 commits into from
Jul 27, 2023
Merged

chore(*): add more explanation when using EKS IRSA to access RDS database #5831

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9038743
chore(*): add more explanation when using EKS IRSA to access RDS data…
windmgc Jul 21, 2023
53144b1
Update app/_src/gateway/kong-enterprise/aws-iam-auth-to-rds-database.md
windmgc Jul 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions app/_src/gateway/kong-enterprise/aws-iam-auth-to-rds-database.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Before you enable the AWS IAM authentication, you must configure your AWS RDS da
- **Assign an IAM role to your Kong Gateway instance.** {{site.base_gateway}} can automatically discover and fetch the AWS credentials to use for the IAM role.
- If you use an EC2 environment, use the [EC2 IAM role](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html).
- If you use an ECS cluster, use a [ECS task IAM role](https://docs.aws.amazon.com/AmazonECS/latest/userguide/task-iam-roles.html).
- If you use an EKS cluster, configure a Kubernetes service account that can annotate your assigned role and configure the pods to use an [IAM role defined by serviceaccount](https://docs.aws.amazon.com/eks/latest/userguide/associate-service-account-role.html).
- If you use an EKS cluster, configure a Kubernetes service account that can annotate your assigned role and configure the pods to use an [IAM role defined by serviceaccount](https://docs.aws.amazon.com/eks/latest/userguide/associate-service-account-role.html). Using an IAM role defined by serviceaccount requires a request to the AWS STS service, so you also need to make sure that your Kong inside the Pod can access AWS STS service endpoint without problem. (If you're using STS regional endpoints, please make sure you have `AWS_STS_REGIONAL_ENDPOINTS` defined in your environment variables.)
windmgc marked this conversation as resolved.
Show resolved Hide resolved
- If you run {{site.base_gateway}} locally, use the environment variables, like access key and secret key combination by using `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`, or profile and credential file combination by using `AWS_PROFILE` and `AWS_SHARED_CREDENTIALS_FILE`

{:.warning}
Expand Down Expand Up @@ -85,4 +85,4 @@ pg_ro_iam_auth=on
```

{:.note}
> **Note:** If you enable AWS IAM authentication in the configuration file, you must specify the configuration file with the feature property on when you run the migrations command. For example, `kong migrations bootstrap -c /path/to/kong.conf`.
> **Note:** If you enable AWS IAM authentication in the configuration file, you must specify the configuration file with the feature property on when you run the migrations command. For example, `kong migrations bootstrap -c /path/to/kong.conf`.