Implement IAM service specific credentials CRUD #12351
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
LocalStack Community integration with Pro 2 files 2 suites 1h 57m 13s ⏱️ Results for commit 72a9f8b. ♻️ This comment has been updated with latest results. |
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.
Motivation
IAM users can have service specific credentials assigned to them, they can be used for AWS CodeCommit (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_ssh-keys.html) and Amazon Keyspaces (for Apache Cassandra) (https://docs.aws.amazon.com/keyspaces/latest/devguide/programmatic.credentials.ssc.html).
For now, we need to have an implementation of the CRUD part of this functionality.
This initally depended on localstack/localstack-snapshot#10, but the last commit removes that dependency to avoid this PR being blocked by it.
Changes