@aws-sdk/client-bedrock-agentcore-control 3.1123.0 → 3.1124.0

package/dist-cjs/index.js

@@ -69,7 +69,7 @@ const commonParams = {
     UseDualStack: { type: "builtInParams", name: "useDualstackEndpoint" },
 };
 
-var version = "3.1122.0";
+var version = "3.1123.0";
 var packageInfo = {
 	version: version};
 
@@ -5038,8 +5038,8 @@ var UpdateCapacityProviderOutput$ = [3, n0, _UCPO,
 ];
 var UpdateConfigurationBundleRequest$ = [3, n0, _UCBR,
     0,
-    [_bIu, _cT, _bN, _d, _com, _pVI, _bNr, _cM, _cB, _kKA],
-    [[0, 1], [0, 4], 0, [() => ConfigurationBundleDescription, 0], [() => ComponentConfigurationMap, 0], 64 | 0, 0, 0, () => VersionCreatedBySource$, 0], 1
+    [_bIu, _pVI, _cT, _bN, _d, _com, _bNr, _cM, _cB, _kKA],
+    [[0, 1], 64 | 0, [0, 4], 0, [() => ConfigurationBundleDescription, 0], [() => ComponentConfigurationMap, 0], 0, 0, () => VersionCreatedBySource$, 0], 2
 ];
 var UpdateConfigurationBundleResponse$ = [3, n0, _UCBRp,
     0,

package/dist-es/schemas/schemas_0.js

@@ -4697,8 +4697,8 @@ export var UpdateCapacityProviderOutput$ = [3, n0, _UCPO,
 ];
 export var UpdateConfigurationBundleRequest$ = [3, n0, _UCBR,
     0,
-    [_bIu, _cT, _bN, _d, _com, _pVI, _bNr, _cM, _cB, _kKA],
-    [[0, 1], [0, 4], 0, [() => ConfigurationBundleDescription, 0], [() => ComponentConfigurationMap, 0], 64 | 0, 0, 0, () => VersionCreatedBySource$, 0], 1
+    [_bIu, _pVI, _cT, _bN, _d, _com, _bNr, _cM, _cB, _kKA],
+    [[0, 1], 64 | 0, [0, 4], 0, [() => ConfigurationBundleDescription, 0], [() => ComponentConfigurationMap, 0], 0, 0, () => VersionCreatedBySource$, 0], 2
 ];
 export var UpdateConfigurationBundleResponse$ = [3, n0, _UCBRp,
     0,

package/dist-types/commands/CreatePolicyCommand.d.ts

@@ -24,7 +24,7 @@ declare const CreatePolicyCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a policy within the AgentCore Policy system. Policies provide real-time, deterministic control over agentic interactions with AgentCore Gateway. Using the Cedar policy language, you can define fine-grained policies that specify which interactions with Gateway tools are permitted based on input parameters and OAuth claims, ensuring agents operate within defined boundaries and business rules. The policy is validated during creation against the Cedar schema generated from the Gateway's tools' input schemas, which defines the available tools, their parameters, and expected data types. This is an asynchronous operation. Use the <a href="https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_GetPolicy.html">GetPolicy</a> operation to poll the <code>status</code> field to track completion.</p> <p>If the new policy is a temporal policy, creating it invalidates the policy engine's active temporal sessions. For more information about temporal policy sessions, see <a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-session-based-temporal.html">session-based temporal policies</a>. The policy engine returns an HTTP 409 <code>ConflictException</code> to in-flight sessions. To resume, you must start a new session with a new session ID.</p>
+ * <p>Creates a policy within the AgentCore Policy system. Policies provide real-time, deterministic control over agentic interactions with AgentCore Gateway. Using Cedar or Dogwood, you can define fine-grained policies that specify which interactions with Gateway tools are permitted based on input parameters and OAuth claims, ensuring agents operate within defined boundaries and business rules. The policy is validated during creation against the Cedar schema generated from the Gateway's tools' input schemas, which defines the available tools, their parameters, and expected data types. This is an asynchronous operation. Use the <a href="https://docs.aws.amazon.com/bedrock-agentcore-control/latest/APIReference/API_GetPolicy.html">GetPolicy</a> operation to poll the <code>status</code> field to track completion.</p> <p>If the new policy is a temporal policy, creating it invalidates the policy engine's active temporal sessions. For more information about temporal policy sessions, see <a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-session-based-temporal.html">session-based temporal policies</a>. The policy engine returns an HTTP 409 <code>ConflictException</code> to in-flight sessions. To resume, you must start a new session with a new session ID.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/GetPolicyGenerationCommand.d.ts

@@ -24,7 +24,7 @@ declare const GetPolicyGenerationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
- * <p>Retrieves information about a policy generation request within the AgentCore Policy system. Policy generation converts natural language descriptions into Cedar policy statements using AI-powered translation, enabling non-technical users to create policies.</p>
+ * <p>Retrieves information about a policy generation request within the AgentCore Policy system. Policy generation converts natural language descriptions into Dogwood policy statements using AI-powered translation, enabling non-technical users to create policies.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/ListPolicyGenerationAssetsCommand.d.ts

@@ -24,7 +24,7 @@ declare const ListPolicyGenerationAssetsCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
- * <p>Retrieves a list of generated policy assets from a policy generation request within the AgentCore Policy system. This operation returns the actual Cedar policies and related artifacts produced by the AI-powered policy generation process, allowing users to review and select from multiple generated policy options.</p>
+ * <p>Retrieves a list of generated policy assets from a policy generation request within the AgentCore Policy system. This operation returns the actual Dogwood policies and related artifacts produced by the AI-powered policy generation process, allowing users to review and select from multiple generated policy options.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/StartPolicyGenerationCommand.d.ts

@@ -24,7 +24,7 @@ declare const StartPolicyGenerationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
- * <p>Initiates the AI-powered generation of Cedar policies from natural language descriptions within the AgentCore Policy system. This feature enables both technical and non-technical users to create policies by describing their authorization requirements in plain English, which is then automatically translated into formal Cedar policy statements. The generation process analyzes the natural language input along with the Gateway's tool context to produce validated policy options. Generated policy assets are automatically deleted after 7 days, so you should review and create policies from the generated assets within this timeframe. Once created, policies are permanent and not subject to this expiration. Generated policies should be reviewed and tested in log-only mode before deploying to production. Use this when you want to describe policy intent naturally rather than learning Cedar syntax, though generated policies may require refinement for complex scenarios.</p>
+ * <p>Initiates the AI-powered generation of Dogwood policies from natural language descriptions within the AgentCore Policy system. This feature enables both technical and non-technical users to create policies by describing their authorization requirements in plain English, which is then automatically translated into formal Dogwood policy statements. The generation process analyzes the natural language input along with the Gateway's tool context to produce validated policy options. Generated policy assets are automatically deleted after 7 days, so you should review and create policies from the generated assets within this timeframe. Once created, policies are permanent and not subject to this expiration. Generated policies should be reviewed and tested in log-only mode before deploying to production. Use this when you want to describe policy intent naturally rather than learning Dogwood syntax, though generated policies may require refinement for complex scenarios.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/UpdateConfigurationBundleCommand.d.ts

@@ -43,7 +43,7 @@ declare const UpdateConfigurationBundleCommand_base: {
  *       configuration: "DOCUMENT_VALUE", // required
  *     },
  *   },
- *   parentVersionIds: [ // ConfigurationBundleVersionList
+ *   parentVersionIds: [ // ConfigurationBundleVersionList // required
  *     "STRING_VALUE",
  *   ],
  *   branchName: "STRING_VALUE",

package/dist-types/models/models_0.d.ts

@@ -4616,7 +4616,7 @@ export interface UpdateConfigurationBundleRequest {
      * <p>A list of parent version identifiers for lineage tracking. Regular commits have a single parent. Merge commits have two parents: the target branch parent and the source branch parent. If the branch already exists, the first parent must be the latest version on that branch.</p>
      * @public
      */
-    parentVersionIds?: string[] | undefined;
+    parentVersionIds: string[] | undefined;
     /**
      * <p>The branch name for this version. If not specified, inherits the parent's branch or defaults to <code>mainline</code>.</p>
      * @public
@@ -6520,7 +6520,7 @@ export interface GatewayInterceptorConfiguration {
  */
 export interface GatewayPolicyEngineConfiguration {
     /**
-     * <p>The ARN of the policy engine. The policy engine contains Cedar policies that define fine-grained authorization rules specifying who can perform what actions on which resources as agents interact through the gateway.</p>
+     * <p>The ARN of the policy engine. The policy engine contains Cedar or Dogwood policies that define fine-grained authorization rules specifying who can perform what actions on which resources as agents interact through the gateway.</p>
      * @public
      */
     arn: string | undefined;

package/dist-types/models/models_2.d.ts

@@ -271,18 +271,18 @@ export interface CedarPolicy {
     statement: string | undefined;
 }
 /**
- * <p>An AgentCore policy statement, which supports plain Cedar policies as well as guardrails definitions.</p>
+ * <p>An AgentCore Cedar or Dogwood policy statement, which supports plain Cedar policies, temporal policies, and guardrails definitions.</p>
  * @public
  */
 export interface PolicyStatement {
     /**
-     * <p>The body of the AgentCore policy statement. Contains the policy logic, which can be a Cedar policy or a guardrails definition.</p>
+     * <p>The body of the AgentCore Cedar or Dogwood policy statement. Contains the policy logic, which can be a Cedar policy, a temporal policy, or a guardrails definition.</p>
      * @public
      */
     statement: string | undefined;
 }
 /**
- * <p>Represents the information identifying a generated policy asset from the AI-powered policy generation process within the AgentCore Policy system. Each asset contains a Cedar policy statement generated from natural language input, along with associated metadata and analysis findings to help users evaluate and select the most appropriate policy option.</p>
+ * <p>Represents the information identifying a generated policy asset from the AI-powered policy generation process within the AgentCore Policy system. Each asset contains a Dogwood policy statement generated from natural language input, along with associated metadata and analysis findings to help users evaluate and select the most appropriate policy option.</p>
  * @public
  */
 export interface PolicyGenerationDetails {
@@ -317,7 +317,7 @@ export declare namespace PolicyDefinition {
         $unknown?: never;
     }
     /**
-     * <p>The generated policy asset information within the policy definition structure. This contains information identifying a generated policy asset from the AI-powered policy generation process within the AgentCore Policy system. Each asset contains a Cedar policy statement generated from natural language input, along with associated metadata and analysis findings to help users evaluate and select the most appropriate policy option.</p>
+     * <p>The generated policy asset information within the policy definition structure. This contains information identifying a generated policy asset from the AI-powered policy generation process within the AgentCore Policy system. Each asset contains a Dogwood policy statement generated from natural language input, along with associated metadata and analysis findings to help users evaluate and select the most appropriate policy option.</p>
      * @public
      */
     interface PolicyGenerationMember {
@@ -327,7 +327,7 @@ export declare namespace PolicyDefinition {
         $unknown?: never;
     }
     /**
-     * <p>An AgentCore policy statement that defines the access control rules. The statement can be a Cedar policy or a guardrails definition.</p>
+     * <p>The Dogwood policy statement that defines the access control rules. This policy definition can include Dogwood policies and supports temporal conditions and information providers such as guardrails.</p>
      * @public
      */
     interface PolicyMember {
@@ -373,7 +373,7 @@ export interface Finding {
     description?: string | undefined;
 }
 /**
- * <p>Represents a generated policy asset from the AI-powered policy generation process within the AgentCore Policy system. Each asset contains a Cedar policy statement generated from natural language input, along with associated metadata and analysis findings to help users evaluate and select the most appropriate policy option.</p>
+ * <p>Represents a generated policy asset from the AI-powered policy generation process within the AgentCore Policy system. Each asset contains a Dogwood policy statement generated from natural language input, along with associated metadata and analysis findings to help users evaluate and select the most appropriate policy option.</p>
  * @public
  */
 export interface PolicyGenerationAsset {
@@ -388,7 +388,7 @@ export interface PolicyGenerationAsset {
      */
     definition?: PolicyDefinition | undefined;
     /**
-     * <p>The portion of the original natural language input that this generated policy asset addresses. This helps users understand which part of their policy description was translated into this specific Cedar policy statement, enabling better policy selection and refinement. When a single natural language input describes multiple authorization requirements, the generation process creates separate policy assets for each requirement, with each asset's rawTextFragment showing which requirement it addresses. Use this mapping to verify that all parts of your natural language input were correctly translated into Cedar policies.</p>
+     * <p>The portion of the original natural language input that this generated policy asset addresses. This helps users understand which part of their policy description was translated into this specific Dogwood policy statement, enabling better policy selection and refinement. When a single natural language input describes multiple authorization requirements, the generation process creates separate policy assets for each requirement, with each asset's rawTextFragment showing which requirement it addresses. Use this mapping to verify that all parts of your natural language input were correctly translated into Dogwood policies.</p>
      * @public
      */
     rawTextFragment: string | undefined;
@@ -403,7 +403,7 @@ export interface PolicyGenerationAsset {
  */
 export interface ListPolicyGenerationAssetsResponse {
     /**
-     * <p>An array of generated policy assets including Cedar policies and related artifacts from the AI-powered policy generation process. Each asset represents a different policy option or variation generated from the original natural language input.</p>
+     * <p>An array of generated policy assets including Dogwood policies and related artifacts from the AI-powered policy generation process. Each asset represents a different policy option or variation generated from the original natural language input.</p>
      * @public
      */
     policyGenerationAssets?: PolicyGenerationAsset[] | undefined;
@@ -434,7 +434,7 @@ export interface ListPolicyGenerationsRequest {
     policyEngineId: string | undefined;
 }
 /**
- * <p>Represents a policy generation request within the AgentCore Policy system. Tracks the AI-powered conversion of natural language descriptions into Cedar policy statements, enabling users to author policies by describing authorization requirements in plain English. The generation process analyzes the natural language input along with the Gateway's tool context and Cedar schema to produce one or more validated policy options. Each generation request tracks the status of the conversion process and maintains findings about the generated policies, including validation results and potential issues. Generated policy assets remain available for one week after successful generation, allowing time to review and create policies from the generated options.</p>
+ * <p>Represents a policy generation request within the AgentCore Policy system. Tracks the AI-powered conversion of natural language descriptions into Dogwood policy statements, enabling users to author policies by describing authorization requirements in plain English. The generation process analyzes the natural language input along with the Gateway's tool context and Cedar schema to produce one or more validated policy options. Each generation request tracks the status of the conversion process and maintains findings about the generated policies, including validation results and potential issues. Generated policy assets remain available for one week after successful generation, allowing time to review and create policies from the generated options.</p>
  * @public
  */
 export interface PolicyGeneration {
@@ -600,7 +600,7 @@ export type Content = Content.RawTextMember | Content.$UnknownMember;
  */
 export declare namespace Content {
     /**
-     * <p>The raw text content containing natural language descriptions of desired policy behavior. This text is processed by AI to generate corresponding Cedar policy statements that match the described intent.</p>
+     * <p>The raw text content containing natural language descriptions of desired policy behavior. This text is processed by AI to generate corresponding Dogwood policy statements that match the described intent.</p>
      * @public
      */
     interface RawTextMember {
@@ -638,7 +638,7 @@ export interface StartPolicyGenerationRequest {
      */
     resource: Resource | undefined;
     /**
-     * <p>The natural language description of the desired policy behavior. This content is processed by AI to generate corresponding Cedar policy statements that match the described intent.</p>
+     * <p>The natural language description of the desired policy behavior. This content is processed by AI to generate corresponding Dogwood policy statements that match the described intent.</p>
      * @public
      */
     content: Content | undefined;
@@ -718,7 +718,7 @@ export interface CreatePolicyRequest {
      */
     name: string | undefined;
     /**
-     * <p>The Cedar policy statement that defines the access control rules. This contains the actual policy logic written in Cedar policy language, specifying effect (permit or forbid), principals, actions, resources, and conditions for agent behavior control.</p>
+     * <p>The Cedar or Dogwood policy statement that defines the access control rules. This contains the actual policy logic written in Cedar or Dogwood, specifying effect (permit or forbid), principals, actions, resources, and conditions for agent behavior control.</p>
      * @public
      */
     definition: PolicyDefinition | undefined;
@@ -793,7 +793,7 @@ export interface CreatePolicyResponse {
      */
     enforcementMode?: EnforcementMode | undefined;
     /**
-     * <p>The Cedar policy statement that was created. This is the validated policy definition that will be used for agent behavior control and access decisions.</p>
+     * <p>The Cedar or Dogwood policy statement that was created. This is the validated policy definition that will be used for agent behavior control and access decisions.</p>
      * @public
      */
     definition: PolicyDefinition | undefined;
@@ -943,7 +943,7 @@ export interface GetPolicyResponse {
      */
     enforcementMode?: EnforcementMode | undefined;
     /**
-     * <p>The Cedar policy statement that defines the access control rules. This contains the actual policy logic used for agent behavior control and access decisions.</p>
+     * <p>The Cedar or Dogwood policy statement that defines the access control rules. This contains the actual policy logic used for agent behavior control and access decisions.</p>
      * @public
      */
     definition: PolicyDefinition | undefined;
@@ -1044,7 +1044,7 @@ export interface ListPoliciesRequest {
     targetResourceScope?: string | undefined;
 }
 /**
- * <p>Represents a complete policy resource within the AgentCore Policy system. Policies are ARN-able resources that contain Cedar policy statements and associated metadata for controlling agent behavior and access decisions. Each policy belongs to a policy engine and defines fine-grained authorization rules that are evaluated in real-time as agents interact with tools through Gateway. Policies use the Cedar policy language to specify who (principals based on OAuth claims like username, role, or scope) can perform what actions (tool calls) on which resources (Gateways), with optional conditions for attribute-based access control. Multiple policies can apply to a single request, with Cedar's forbid-wins semantics ensuring that security restrictions are never accidentally overridden.</p>
+ * <p>Represents a complete policy resource within the AgentCore Policy system. Policies are ARN-able resources that contain Cedar or Dogwood policy statements and associated metadata for controlling agent behavior and access decisions. Each policy belongs to a policy engine and defines fine-grained authorization rules that are evaluated in real-time as agents interact with tools through Gateway. Policies use Cedar or Dogwood to specify who (principals based on OAuth claims like username, role, or scope) can perform what actions (tool calls) on which resources (Gateways), with optional conditions for attribute-based access control. Multiple policies can apply to a single request, with forbid-wins semantics ensuring that security restrictions are never accidentally overridden.</p>
  * @public
  */
 export interface Policy {
@@ -1089,7 +1089,7 @@ export interface Policy {
      */
     enforcementMode?: EnforcementMode | undefined;
     /**
-     * <p>The Cedar policy statement that defines the access control rules. This contains the actual policy logic used for agent behavior control and access decisions.</p>
+     * <p>The Cedar or Dogwood policy statement that defines the access control rules. This contains the actual policy logic used for agent behavior control and access decisions.</p>
      * @public
      */
     definition: PolicyDefinition | undefined;
@@ -1225,7 +1225,7 @@ export interface UpdatePolicyRequest {
      */
     description?: UpdatedDescription | undefined;
     /**
-     * <p>The new Cedar policy statement that defines the access control rules. This replaces the existing policy definition with new logic while maintaining the policy's identity.</p>
+     * <p>The new Cedar or Dogwood policy statement that defines the access control rules. This replaces the existing policy definition with new logic while maintaining the policy's identity.</p>
      * @public
      */
     definition?: PolicyDefinition | undefined;
@@ -1285,7 +1285,7 @@ export interface UpdatePolicyResponse {
      */
     enforcementMode?: EnforcementMode | undefined;
     /**
-     * <p>The updated Cedar policy statement.</p>
+     * <p>The updated Cedar or Dogwood policy statement.</p>
      * @public
      */
     definition: PolicyDefinition | undefined;

package/dist-types/ts3.4/models/models_0.d.ts

@@ -1375,7 +1375,7 @@ export interface UpdateConfigurationBundleRequest {
   bundleName?: string | undefined;
   description?: string | undefined;
   components?: Record<string, ComponentConfiguration> | undefined;
-  parentVersionIds?: string[] | undefined;
+  parentVersionIds: string[] | undefined;
   branchName?: string | undefined;
   commitMessage?: string | undefined;
   createdBy?: VersionCreatedBySource | undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aws-sdk/client-bedrock-agentcore-control",
-  "version": "3.1123.0",
+  "version": "3.1124.0",
   "description": "AWS SDK for JavaScript Bedrock Agentcore Control Client for Node.js, Browser and React Native",
   "homepage": "https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-bedrock-agentcore-control",
   "license": "Apache-2.0",