feat(agentcore): add agentcore runtime L2 construct

[dineshSajwan]

Issue # (if applicable)

Closes #<785>.

Reason for this change

Adding bedrock agent core runtime and runtime endpoint

Description of changes

• Added a new L2 construct for runtime in aws -bedrock-agentcore-alpha package.
• Added a new L2 construct for runtime endpoint
• Added test cases
• Added documentation

Describe any new or updated permissions being added

The runtime creates a role with permission to ecr repo, cloudwatch , xray .

Description of how you validated changes

Unit tests, integration tests, manual tests

Checklist

• [Yes] My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[alvazjor]

Are we expecting this configuration to have more elements in the future? Do you know if there are plans for that? Seems like having this interface at the moment is not adding too much value, you could potentially return the URI directly in the bind method rather than this object (in CDK, we tend to favor flat composition over nested composition if we can)

[dineshSajwan]

This mirrors the cloudformation structure of agentruntimeartifact . IMHO, we should keep it as cloud formation structure because if the underlying service add any new field in this object then the flat structure of containeruri may cause breaking changes for the L2 construct.

[alvazjor]

This and the other methods below are exactly what I was expecting to see instead of https://github.com/aws/aws-cdk/pull/35623/files#r2398909386.
Simple and specific for each type of auth configuration. I would prefer to keep only this idea and drop the possibility for the user to set up manually the auth config with all the possible wrong combinations they could make if we let it fully configurable.

[dineshSajwan]

Ack.

[alvazjor]

What is the difference between this and the agentRuntimeVersion ?

[dineshSajwan]

We actually have two of those liveVersion and targetVersion. I have added liveVersion with this new commit.

this.liveVersion = this.endpointResource.attrLiveVersion;
this.targetVersion = this.endpointResource.attrTargetVersion;

https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-bedrockagentcore-runtimeendpoint.html

https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agent-runtime-versioning.html

As per my understanding

Initial Creation :

• You set agentRuntimeVersion: "1"
• Both liveVersion and targetVersion will be "1"
• Status: READY

During Update :

• Update runtime version to "2"
• liveVersion remains "1"
• targetVersion becomes "2" (transitioning to this)
• Status: UPDATING

After Update Completes :

• Both liveVersion and targetVersion become "2"
• Status: READY

Pull request has been modified.