Updating AWS RDS IAM Auth Documentation #1136
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…grant command to allow the creation of expressions on the coder database
ericpaulsen
approved these changes
Sep 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I ran into an issue recently when trying to enable this for a new RDS DB Cluster within AWS. My proposed changes are what got me to a working solution with my setup. This included updating the Trust Relationship policy condition to only use the IAM Identity Provider name instead of the full ARN. Also, I ran into a permission issue with a fresh database and my non-admin database user, so I needed to provide an extra grant command to allow the ability to create expressions as part of the initial startup.