What authentication does the Amazon CodeGuru Reviewer API use?

CodeGuru Reviewer uses AWS Signature Version 4 (HMAC) signed requests with an IAM access key and secret. Through Jentic, those credentials live encrypted in your Jentic One instance and the SigV4 signature is computed server-side, so the agent context never holds the raw secret.

Can I trigger a code review on a specific pull request through the API?

Yes. CreateCodeReview accepts a Type with a RepositoryAnalysis sub-object that takes a RepositoryHead containing a BranchName. Once created, poll DescribeCodeReview until State equals Completed, then call ListRecommendations on the CodeReviewArn to fetch results.

How do I submit feedback on a CodeGuru recommendation?

Call PutRecommendationFeedback with the CodeReviewArn, RecommendationId, and a Reactions array containing ThumbsUp or ThumbsDown. ListRecommendationFeedback returns aggregate feedback so an agent can review sentiment across recommendations.

What are the rate limits for the Amazon CodeGuru Reviewer API?

AWS enforces per-account, per-region throttling on CodeGuru Reviewer; throttled requests return ThrottlingException. Code review creation is also rate-limited per repository. Use exponential backoff via the AWS SDKs that Jentic wraps.

How do I run a CodeGuru review through Jentic with an AI agent?

Run pip install jentic, then have the agent search for 'run a CodeGuru code review', load the CreateCodeReview schema, and execute it with the AssociationArn and branch. Poll DescribeCodeReview for completion, then ListRecommendations to fetch findings the agent can post back as PR comments.

Can I limit what my agent is allowed to do with the CodeGuru Reviewer API?

Yes. Because you run Jentic One yourself, your own rules decide which CodeGuru Reviewer operations and AWS credentials the agent may use. Since the association and review ARNs are minted by AWS at creation time rather than chosen by you, the honest control is by operation: you allow only the calls the agent needs, such as CreateCodeReview and ListRecommendations, so a destructive operation like DisassociateRepository is not available unless you add it. The AWS access key and secret are injected at signing time and never enter the agent's prompt or context.