Start by identifying exactly what was exposed: a long-term Amazon Bedrock API key, a short-term Bedrock API key, an IAM access key, or temporary role-session credentials. Each has a different revocation path. Use a separate, trusted AWS identity to investigate and change permissions; AWS says Bedrock API-key management actions must be authenticated with AWS credentials, not with a Bedrock API key.
AWS responds to incidents in the Bedrock service itself. You are responsible for the credentials, IAM policies, agent workload, logs, and recovery actions in your AWS environment. The procedure below preserves evidence while stopping additional use.
As an Amazon Associate I earn from qualifying purchases.
Make the first decision: which credential leaked?
Do not begin by deleting the agent or applying Bedrock API-key instructions to every secret you find. First establish the credential type, its owner, and the session or role that issued it. A secret in source code may be a Bedrock key, an IAM user access key, or a temporary token copied from an agent runtime. The containment control must match that type.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Credential type | What it represents | Documented containment options | Scope and reversibility |
|---|---|---|---|
| Long-term Bedrock API key | A persistent Bedrock API credential managed through AWS. | Set it inactive, reset it to issue a new password, delete it, or remove its permissions with IAM policy changes. See AWS’s Bedrock API-key guidance. | Deactivation is a temporary block; reset changes the secret; deletion is permanent. IAM policy changes can affect every use covered by that policy. |
| Short-term Bedrock API key | A presigned URL that inherits the credentials and expiration of the session that generated it. | It cannot be individually deactivated, reset, or deleted. Invalidate the originating IAM session or deny that identity permission to call Bedrock with an API key, while assessing the effect on other session uses. | The control operates at session or identity level, so it may disrupt more than one request or agent. |
| Long-term IAM access key | An IAM principal’s access key, which may have permissions beyond Bedrock. | Use IAM incident-response controls for that user or principal, including changing effective permissions and replacing or removing the exposed key through a trusted identity. | Impact depends on the principal’s policies and other workloads using the key. |
| Temporary role-session credentials | Time-limited credentials issued for an assumed role or other AWS session. | They normally expire on their own. If the incident occurs before expiration, alter the session’s effective permissions or deny the relevant principal according to how the session was created. AWS’s Security Incident Response User Guide covers temporary credentials separately. | Session and identity controls can affect every workload using that role or session; the exact action depends on the principal and session design. |
If you cannot yet classify the secret, treat it as active until its issuer, expiration, and permissions are confirmed. Record the uncertainty rather than guessing.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Set up a trusted response and preserve context
Use an unaffected administrative identity for all investigation and revocation work. Do not use the suspected Bedrock key, a credential copied from the potentially compromised agent, or a role whose permissions may have been altered. The Bedrock API-key documentation specifically requires AWS credentials for API actions that manage Bedrock keys.
- Assign an incident owner. Give one person responsibility for decisions and a second person responsibility for independent review. Keep the response channel and ticket system free of secret values.
- Record discovery details. Note when and how the disclosure was found, the AWS account and Regions involved, the agent or workload, the credential owner and type, where it appeared (such as code, configuration, logs, an artifact, or a third-party service), and the earliest plausible exposure time.
- Preserve the original evidence safely. Save relevant log references, configuration versions, deployment identifiers, and hashes or object locations under your incident process. Do not paste the key, token, presigned URL, or session secret into tickets, chat, screenshots, or investigation notes.
- Map dependencies before a broad change. Identify which agent tasks, tools, queues, workflows, and deployment systems use the principal. A session-level or role-level denial can stop legitimate work as well as malicious calls.
- Choose a response window. Use the earliest plausible exposure time to bound log review, but keep investigating beyond that window when tokens could have been copied or replayed.
These records let you distinguish confirmed use of the exposed credential from activity that merely shares the same account, role, Region, or time period.
Contain the matching credential
Long-term Amazon Bedrock API key
A long-term key gives you three direct key-level choices. Set it inactive when you need a reversible emergency block and expect to validate the workload before restoring access. Reset it when the workload must continue with a new password; update every consumer through a controlled deployment. Delete it when the key should no longer exist. You can also change IAM policies to remove the key’s ability to call the required Bedrock resources.
Choose one action deliberately. Resetting a key without updating all consumers can create a second outage while leaving uncertainty about copies of the old secret. Deleting a key is appropriate when its purpose has ended, but it removes the simple rollback available from deactivation. AWS states, “If your API key becomes compromised, you should revoke permissions to use it.” The complete procedure and API-key behavior are documented by Amazon Web Services.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Short-term Amazon Bedrock API key
A short-term Bedrock API key is not an independently managed permanent secret. AWS describes it as a presigned URL that inherits the credentials and expiration of the session that generated it. You therefore cannot deactivate, reset, or delete that individual key.
Contain it by invalidating the originating IAM session or denying the originating identity the ability to call Bedrock using an API key. Before applying the denial, identify other requests that depend on the same session or identity. The action may stop legitimate work, but leaving a still-valid session unchanged can allow continued use of the exposed URL until its inherited expiration.
IAM user access key
If the exposed value is an IAM user’s long-term access key, follow IAM incident-response controls for that principal rather than Bedrock API-key controls. Determine every permission attached directly, through groups, or through policies and identify non-Bedrock services that may be affected. Use a trusted administrator to change the key’s status or replace it, then deploy the replacement to consumers without putting the new value in source control or logs.
Because an IAM key can authorize services other than Bedrock, review activity across the account and Regions, not just model invocation. Keep the original key metadata and timestamps for the investigation even after access is blocked.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Temporary role or session credentials
Temporary credentials normally have a limited lifetime. That expiration reduces the window of exposure but is not a containment plan when the event is still active. AWS’s Security Incident Response guidance says that, when temporary credentials are involved before expiration, responders may need to alter their effective permissions. The exact control depends on how the principal and session were created.
Identify the assumed role, session name, issuer, expiration, and policies that determine effective permissions. Apply the narrowest denial that stops the suspicious Bedrock action while considering other workloads using the same role. Continue monitoring until the session expires or the replacement policy is verified.
Agent role or workload identity
If the leak involves the identity used by the agent rather than a standalone key, contain the permissions while retaining the role and evidence needed for analysis. Do not assume that deleting an agent revokes credentials or removes copies held by other services; that effect is not universal across architectures.
Investigate use and determine the blast radius
Review CloudTrail with its actual coverage in mind
Start with CloudTrail records around the exposure window and compare observed actions with the agent’s expected role, normal Regions, source addresses, API operations, and activity volume. Preserve the relevant records and their timestamps under your organization’s incident process.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Console event history provides 90 days of management-event history, according to AWS CloudTrail security best practices. It is not a permanent record and does not contain every possible event type. A missing event therefore does not prove that no use occurred. Confirm which trails were enabled, which Regions and event types they covered, and when logging began.
For an ongoing record, configure a trail for the event types you need. AWS recommends multi-Region logging, log-file integrity validation, and dedicated centralized S3 storage for forensic and auditing purposes. Check the trail’s configuration and delivery status before relying on a gap in the logs as evidence.
Check GuardDuty findings and suspicious Bedrock patterns
Review GuardDuty findings in every relevant Region and correlate them with CloudTrail timestamps and principals. The Amazon Bedrock incident-response guidance gives examples of suspicious Bedrock activity that GuardDuty can detect, including attempts to remove Bedrock Guardrails or change an S3 bucket used for model-training data.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →These examples are indicators, not a complete signature for every leak. Compare the finding’s identity, source, resource, and operation with the agent’s intended behavior. A finding involving the same account does not by itself prove that the exposed credential made the call.
Correlate identity, resource, and workload evidence
- Match the credential or session owner to the role, user, or workload that generated it.
- Compare source addresses, Regions, user agents, and request timing with the agent’s normal execution profile.
- List successful and denied calls, not only successful calls; repeated denials can show attempted use after a policy change.
- Check changes to Bedrock Guardrails, model access, agent configuration, IAM policies, S3 data locations, queues, and deployment artifacts.
- Separate confirmed use of the exposed value from activity by another principal that happened during the same period.
- Preserve relevant log objects and configuration versions before retention or automated lifecycle rules remove them.
Isolate an affected agent without destroying evidence
AWS’s Agentic AI Lens describes a containment pattern for agents. Adapt it to your architecture and approved response plan rather than treating it as a universal command sequence.
- Capture a forensic snapshot. Save the agent’s memory, active sessions, and pending operations to S3. Record the destination, object versions, timestamps, and access controls so the snapshot can be reviewed without changing the live agent.
- Attach a deny-all policy to the agent IAM role. This blocks the role’s effective actions while preserving the role itself for forensic analysis. Coordinate the change with the identity owner and record the policy version that was attached.
- Broadcast quarantine through EventBridge. Publish a quarantine event that dependent workflows understand. Consumers can stop queues, pause downstream automation, or require human approval according to their design.
- Verify the isolation. Check for new activity under the role, pending operations in dependent systems, and workloads that use a different identity but still act on the agent’s resources.
Retaining the role and logs matters: deleting the identity can remove context needed to reconstruct what happened. The pattern is described in AGENTSEC07-BP04: Behavioral anomaly detection and agent containment.
Eradicate the exposure and recover safely
- Remove the secret from its source. Delete it from code, configuration, logs, artifacts, or third-party systems where it was disclosed. Rotate any replacement through a controlled secret-delivery process.
- Deploy the replacement deliberately. Update consuming applications, agent tools, and deployment jobs. Confirm which version is running and which identity it uses.
- Verify old access is gone. Where feasible, test that the old key, session, or permission no longer authorizes the relevant Bedrock operation. Use a trusted test identity for positive checks and avoid replaying a compromised secret unnecessarily.
- Remove unauthorized changes. Review and revert unexpected IAM policies, Guardrail changes, S3 bucket changes, agent configuration, queues, or other resources identified during investigation. Preserve copies of the unauthorized configuration before reverting it.
- Validate dependencies before reopening. Confirm permissions, provider access, logging, alerting, queue behavior, and required human approvals. Restore the agent only after the responsible team accepts the residual risk.
- Keep heightened monitoring. Watch the replacement identity and affected resources for recurrence, denied calls, unusual Regions, and unexpected data access.
AWS’s general incident-response guidance separates containment from eradication and recovery: containment prevents additional unauthorized activity, while eradication removes the cause and recovery returns the workload to a validated state. See the AWS Security Incident Response User Guide for that lifecycle.
Harden the agent and its credential paths
Reduce permissions to the required Bedrock resources
Revisit the agent role and every identity that can invoke Bedrock. AWS recommends least privilege for Bedrock resources. Remove unused actions, narrow resources, and separate administration from runtime access so a leaked runtime credential cannot automatically perform unrelated security or data-management tasks.
Scope credential providers to workload identities
If the agent uses AgentCore credential providers, scope IAM Resource entries to the specific workload identities and provider ARNs that need them. The AWS credential-provider guidance recommends separate workload identities and IAM roles when agents require different providers. This limits the effect of a policy mistake or leaked provider credential.
Separate roles where blast radius differs
Do not make unrelated agents share one broad role merely because they run in the same account. Distinct roles let you quarantine one workload without denying every agent and make CloudTrail attribution clearer. Where sharing is unavoidable, document the shared dependencies and test the effect of a session-level denial before an incident.
Improve detection and audit durability
Review CloudTrail trail coverage, multi-Region settings, log-file integrity validation, centralized S3 storage, GuardDuty coverage, and alert routing. Ensure the response team can retrieve records for the retention period required by your incident policy rather than relying only on the console’s 90-day management-event history.
Recommended Free Tools
Quick Recap
Containment choices and their operational trade-offs
| Action | Best fit | Availability effect | Forensic value |
|---|---|---|---|
| Deactivate a long-term Bedrock API key | Immediate, reversible block while ownership and impact are confirmed. | Stops consumers of that key until it is reactivated or replaced. | Preserves the key record and associated role context. |
| Reset a long-term Bedrock API key | The workload must continue with a new secret. | Old consumers fail until they receive the replacement. | Requires tracking every consumer and deployment version. |
| Delete a long-term Bedrock API key | The key is no longer needed or permanent removal is required. | Irreversible for that key; every dependent consumer must be migrated. | Keep audit records before deletion. |
| Invalidate a short-term key’s IAM session | A presigned key is still within its session lifetime. | May stop every operation using that session, not just the suspected request. | Retains the originating session and identity for correlation. |
| Deny Bedrock API-key use for an identity | The identity must remain available for other work but must not call Bedrock with an API key. | Can interrupt legitimate Bedrock calls by that identity. | Leaves the principal intact for investigation. |
| Attach a deny-all policy to an agent role | The workload itself must be quarantined while evidence is preserved. | Stops the role’s actions and dependent automation until release. | Preserves the IAM role, policy history, and forensic snapshot. |
Common mistakes to avoid
- Using the suspected secret to revoke itself. Administration should come from a separate trusted AWS identity.
- Treating every token as a Bedrock API key. IAM user keys and temporary role credentials require IAM incident-response controls.
- Assuming a short-term key can be deleted. The presigned URL inherits its session’s credentials and expiration; act on the session or identity.
- Deleting the agent first. Deletion may remove operational context without revoking copies held elsewhere.
- Reading a missing CloudTrail event as proof of no use. Console history is limited to 90 days of management events and is not complete for every event type.
- Rotating without inventory. A replacement that reaches only one consumer can leave another service using the exposed value.
- Restoring before validation. Re-enable the agent only after permissions, dependent workflows, logging, and approvals have been checked.
Incident-response checklist
- Credential type, owner, account, Region, exposure location, and earliest plausible exposure time recorded.
- Incident owner assigned and trusted administrative identity selected.
- Secret excluded from tickets, chat, screenshots, and investigation notes.
- Matching control applied: key deactivation, reset, deletion, IAM policy change, session invalidation, identity denial, or agent-role quarantine.
- CloudTrail configuration and retention confirmed before interpreting missing events.
- Relevant CloudTrail records, GuardDuty findings, configuration versions, and timestamps preserved.
- Agent memory, active sessions, and pending operations snapshotted when the quarantine pattern is appropriate.
- Unauthorized changes removed and the exposure path repaired.
- Replacement secret deployed to every consumer and old access tested as invalid where feasible.
- Least privilege, provider-resource scoping, role separation, multi-Region logging, integrity validation, and alert routing reviewed.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
