Skip to content

Commit 6e3b0df

Browse files
ekristenekristen
authored
Merge pull request #795 from ekristen/bedrock-agents
feat: Bedrock AgentCore Resources
2 parents d9feefe + 09e7094 commit 6e3b0df

33 files changed

+2715
-0
lines changed

‎AGENTS.md‎

Lines changed: 966 additions & 0 deletions
Large diffs are not rendered by default.

‎CLAUDE.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
AGENTS.md

‎docs/resources/bedrock-agent-core-agent-runtime.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreAgentRuntime
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreAgentRuntime
12+
```
13+
14+
## Properties
15+
16+
17+
- `AgentRuntimeID`: No Description
18+
- `AgentRuntimeName`: No Description
19+
- `AgentRuntimeVersion`: No Description
20+
- `Description`: No Description
21+
- `LastUpdatedAt`: No Description
22+
- `Status`: No Description
23+
- `tag:<key>:`: This resource has tags with property `Tags`. These are key/value pairs that are
24+
added as their own property with the prefix of `tag:` (e.g. [tag:example: "value"])
25+
26+
!!! note - Using Properties
27+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
28+
names to write filters for what you want to **keep** and omit from the nuke process.
29+
30+
### String Property
31+
32+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
33+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
34+
the filter.
35+
36+
The string value is always what is used in the output of the log format when a resource is identified.
37+

‎docs/resources/bedrock-agent-core-api-key-credential-provider.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreAPIKeyCredentialProvider
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreAPIKeyCredentialProvider
12+
```
13+
14+
## Properties
15+
16+
17+
- `CreatedTime`: No Description
18+
- `CredentialProviderArn`: No Description
19+
- `LastUpdatedTime`: No Description
20+
- `Name`: No Description
21+
22+
!!! note - Using Properties
23+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
24+
names to write filters for what you want to **keep** and omit from the nuke process.
25+
26+
### String Property
27+
28+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
29+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
30+
the filter.
31+
32+
The string value is always what is used in the output of the log format when a resource is identified.
33+

‎docs/resources/bedrock-agent-core-browser.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreBrowser
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreBrowser
12+
```
13+
14+
## Properties
15+
16+
17+
- `CreatedAt`: No Description
18+
- `ID`: No Description
19+
- `LastUpdatedAt`: No Description
20+
- `Name`: No Description
21+
- `Status`: No Description
22+
- `tag:<key>:`: This resource has tags with property `Tags`. These are key/value pairs that are
23+
added as their own property with the prefix of `tag:` (e.g. [tag:example: "value"])
24+
25+
!!! note - Using Properties
26+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
27+
names to write filters for what you want to **keep** and omit from the nuke process.
28+
29+
### String Property
30+
31+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
32+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
33+
the filter.
34+
35+
The string value is always what is used in the output of the log format when a resource is identified.
36+

‎docs/resources/bedrock-agent-core-code-interpreter.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreCodeInterpreter
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreCodeInterpreter
12+
```
13+
14+
## Properties
15+
16+
17+
- `CreatedAt`: No Description
18+
- `ID`: No Description
19+
- `LastUpdatedAt`: No Description
20+
- `Name`: No Description
21+
- `Status`: No Description
22+
- `tag:<key>:`: This resource has tags with property `Tags`. These are key/value pairs that are
23+
added as their own property with the prefix of `tag:` (e.g. [tag:example: "value"])
24+
25+
!!! note - Using Properties
26+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
27+
names to write filters for what you want to **keep** and omit from the nuke process.
28+
29+
### String Property
30+
31+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
32+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
33+
the filter.
34+
35+
The string value is always what is used in the output of the log format when a resource is identified.
36+

‎docs/resources/bedrock-agent-core-gateway-target.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreGatewayTarget
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreGatewayTarget
12+
```
13+
14+
## Properties
15+
16+
17+
- `CreatedAt`: No Description
18+
- `Description`: No Description
19+
- `GatewayIdentifier`: No Description
20+
- `Name`: No Description
21+
- `Status`: No Description
22+
- `TargetID`: No Description
23+
- `UpdatedAt`: No Description
24+
25+
!!! note - Using Properties
26+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
27+
names to write filters for what you want to **keep** and omit from the nuke process.
28+
29+
### String Property
30+
31+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
32+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
33+
the filter.
34+
35+
The string value is always what is used in the output of the log format when a resource is identified.
36+

‎docs/resources/bedrock-agent-core-gateway.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreGateway
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreGateway
12+
```
13+
14+
## Properties
15+
16+
17+
- `AuthorizerType`: No Description
18+
- `CreatedAt`: No Description
19+
- `ID`: No Description
20+
- `Name`: No Description
21+
- `ProtocolType`: No Description
22+
- `Status`: No Description
23+
- `UpdatedAt`: No Description
24+
- `tag:<key>:`: This resource has tags with property `Tags`. These are key/value pairs that are
25+
added as their own property with the prefix of `tag:` (e.g. [tag:example: "value"])
26+
27+
!!! note - Using Properties
28+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
29+
names to write filters for what you want to **keep** and omit from the nuke process.
30+
31+
### String Property
32+
33+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
34+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
35+
the filter.
36+
37+
The string value is always what is used in the output of the log format when a resource is identified.
38+

‎docs/resources/bedrock-agent-core-memory.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreMemory
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreMemory
12+
```
13+
14+
## Properties
15+
16+
17+
- `CreatedAt`: No Description
18+
- `ID`: No Description
19+
- `Status`: No Description
20+
- `UpdatedAt`: No Description
21+
- `tag:<key>:`: This resource has tags with property `Tags`. These are key/value pairs that are
22+
added as their own property with the prefix of `tag:` (e.g. [tag:example: "value"])
23+
24+
!!! note - Using Properties
25+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
26+
names to write filters for what you want to **keep** and omit from the nuke process.
27+
28+
### String Property
29+
30+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
31+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
32+
the filter.
33+
34+
The string value is always what is used in the output of the log format when a resource is identified.
35+

‎docs/resources/bedrock-agent-core-oauth-2credential-provider.md‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
generated: true
3+
---
4+
5+
# BedrockAgentCoreOauth2CredentialProvider
6+
7+
8+
## Resource
9+
10+
```text
11+
BedrockAgentCoreOauth2CredentialProvider
12+
```
13+
14+
## Properties
15+
16+
17+
- `CreatedTime`: No Description
18+
- `LastUpdatedTime`: No Description
19+
- `Name`: No Description
20+
- `Vendor`: No Description
21+
- `tag:<key>:`: This resource has tags with property `Tags`. These are key/value pairs that are
22+
added as their own property with the prefix of `tag:` (e.g. [tag:example: "value"])
23+
24+
!!! note - Using Properties
25+
Properties are what [Filters](../config-filtering.md) are written against in your configuration. You use the property
26+
names to write filters for what you want to **keep** and omit from the nuke process.
27+
28+
### String Property
29+
30+
The string representation of a resource is generally the value of the Name, ID or ARN field of the resource. Not all
31+
resources support properties. To write a filter against the string representation, simply omit the `property` field in
32+
the filter.
33+
34+
The string value is always what is used in the output of the log format when a resource is identified.
35+

0 commit comments

Comments
 (0)