Artificial Genius Orthix version 2

Running a Workflow

Once provisioned in ECS, users can run any number of workflows by invoking the standard container endpoint for Bedrock AgentCore agents, /invocations on port 8080. The POST input for this endpoint is a JSON object with a 'prompt' field that contains the PRD in Markdown format. The POST output is also a JSON object with a 'response' field that contains a log of successes and failures of the workflow items, also in Markdown format.

Configure the Network

In the VPC console, create a VPC consistent with where your resources are located, and create a Security Group that is attached to the VPC above, and configure its Inbound and Outbound Rules to enable network access for the following resources and ports:

• AWS Marketplace Product Registration: TCP port 443
• Bedrock Runtime Agent: TCP port 8080
• S3: TCP ports 80, 443
• HTTP: TCP ports 80, 443
• All ICMP - IPv4

In the VPC console, create corresponding Endpoints, with Private DNS Names, using the above Security Group:

• com.amazonaws.region.sts (Interface);
• com.amazonaws.region.metering-marketplace (Interface);
• com.amazonaws.region.bedrock-runtime (Interface);
• com.amazonaws.region.s3 (Gateway, if access to S3 desired).

Configure Permissions

In the IAM console, create an IAM Role for the Orthix container, for example, 'OrthixRole'.

The Permission Policies attached to OrthixRole should include:

• AmazonEC2ContainerServiceforEC2Role
• AWSMarketplaceMeteringRegisterUsage
• AWSMarketplaceMeteringFullAccess
• AmazonECSTaskExecutionRolePolicy
• AmazonBedrockReadOnly
• BedrockAgentCoreFullAccess (see manual).

The Trust Relationships of the role should follow the template: https://agipub.s3.us-east-1.amazonaws.com/artificial-genius-orthix-trust-relationships.json . Modify the template so that the Statement Id 'AllowRoleToAssumeItself' allows OrthixRole to assume itself. This is necessary because various derived versions of the role may be automatically generated that need to be normalized back to the original role.

Create the ECS Cluster

In ECS console, create a new cluster, give it a name, say 'orthix-cluster'.

• Select Network Settings to point to your above VPC and Security Group.

Create the ECS Service

In ECS console, create a Task according to the template Task Definition https://agipub.s3.us-east-1.amazonaws.com/artificial-genius-orthix-ecs-task.json . Replace the wildcards '*' in this template with your specifics, including the container URI provided to you when you subscribed to the Orthix product, and the OrthixRole above. Select the requiresCompatibilities field to conform to the Infrastructure Capacity type of your cluster. Then, register it as a Task Definition under a name, say 'orthix-task'. Then Deploy the Task Definition as a Service.

• Select Cluster as orthix-cluster.
• Select the Networking to be consistent with the VPC and Security Group above.