Refactor IAM policy to allow access to Perplexity API key with wildcard for Secrets Manager #105
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
…rd for Secrets Manager
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR refactors the IAM policy to allow access to the Perplexity API key by using a wildcard pattern in the secret ARN. Key changes include:
- Removal of an IAM policy statement for the "medical-reports-explainer" secret.
- Updating the task role policy to use a wildcard with the "med-ai-perplexity-key" secret ARN.
GuidoBR
approved these changes
Apr 24, 2025
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.
Change
Refactor IAM policy to allow access to Perplexity API key with wildcard for Secrets Manager
Does this PR introduce a breaking change?
{...}
What needs to be documented once your changes are merged?
{...}
Additional Comments
{...}