Answer: Follow these security guidelines: use IAM roles with minimum required permissions, rotate access keys regularly if using the API Key method, never store credentials in code or version control, prefer the AWS Profile method for better credential management, and consider using AWS SSO/federated roles for enhanced security. Status: Confirmed Entry: tool/cline/permissions-and-security/bedrock-security-best-practices Revision: 1 Digest: sha256:0e7edd28baa70004 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:06:44Z Last changed: 2026-11-13T03:06:44Z Last verified: 2026-11-20T12:27:59Z Next check: 2026-11-21T12:27:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of IAM permissions | Use IAM roles with minimum required permissions | [1] | 2026-11-20 Access key rotation | Rotate access keys regularly if using the API Key method | [1] | 2026-11-20 Credential storage | Never store credentials in code or version control | [1] | 2026-11-20 Preferred method | Prefer AWS Profile method for better credential management | [1] | 2026-11-20 SSO/federated roles | Consider using AWS SSO/federated roles for enhanced security | [1] | 2026-11-20 Sources: [1] Cline. "Configure AWS Bedrock in VS Code (Members)". https://docs.cline.bot/enterprise-solutions/configuration/remote-configuration/aws-bedrock/member-configuration.md Role: primary. Accessed: 2026-11-20T12:27:59Z Quote: "Use IAM roles with minimum required permissions" (Supports: IAM permissions) Quote: "Rotate access keys regularly if using the API Key method" (Supports: Access key rotation) Quote: "Never store credentials in code or version control" (Supports: Credential storage) Quote: "Prefer AWS Profile method for better credential management" (Supports: Preferred method) Quote: "Consider using AWS SSO/federated roles for enhanced security" (Supports: SSO/federated roles) Published: 2026-11-20T06:01:05Z Snapshot SHA-256: 1049858a5ccea0e720e7dfce98cc1b85adf357ca78323249e93cc02893ffca50 (captured 2026-11-13T03:06:43Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:06:44Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:27:59Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:27:59Z Last attempt: 2026-11-20T12:27:59Z Notes and limitations: Extracted automatically from a single official source (section "Security Best Practices"). Related: https://latestn.com/tool/cline/permissions-and-security/block-ignored-file-access How do I block ignored file access in Cline with a plugin? https://latestn.com/tool/cline/permissions-and-security/cline-action-approval Does Cline require my approval before it runs commands or edits files? https://latestn.com/tool/cline/permissions-and-security/connector-security-settings What security settings are available for Cline Telegram and Discord connectors? https://latestn.com/tool/cline/permissions-and-security/anthropic-api-key-security What security best practices should I follow when using an Anthropic API key with Cline? https://latestn.com/tool/cline/permissions-and-security/authentication-methods What authentication methods does the Cline API support? https://latestn.com/tool/cline/permissions-and-security/bedrock-api-key-iam-policy What IAM policy does a Bedrock API key use by default with Cline? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:06:44Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/permissions-and-security/bedrock-security-best-practices/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cline/permissions-and-security/bedrock-security-best-practices POST: https://latestn.com/dispute/tool/cline/permissions-and-security/bedrock-security-best-practices with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/permissions-and-security/bedrock-security-best-practices?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What security best practices should I follow when configuring AWS Bedrock credentials in Cline? Revision 1, last verified 2026-11-20T12:27:59Z. https://latestn.com/tool/cline/permissions-and-security/bedrock-security-best-practices (accessed 2026-11-21T10:08:26Z). @misc{LatestN_tool_cline_permissions_and_security_bedrock_security_best_practices_r1, title = {What security best practices should I follow when configuring AWS Bedrock credentials in Cline?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/permissions-and-security/bedrock-security-best-practices}}, note = {Revision 1; digest sha256:0e7edd28baa70004; last verified 2026-11-20T12:27:59Z; accessed 2026-11-21T10:08:26Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cline/permissions-and-security/bedrock-security-best-practices