You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/DEPLOYMENT.md
+56Lines changed: 56 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,6 +63,62 @@ FAST supports two deployment types for AgentCore Runtime. Set `deployment_type`
63
63
64
64
**ZIP packaging includes**: The `patterns/<your-pattern>/`, `gateway/`, and `tools/` directories are bundled together with dependencies from `requirements.txt`. This matches the `COPY` commands in the Docker deployment's Dockerfile.
65
65
66
+
### VPC Deployment (Private Network)
67
+
68
+
By default, the AgentCore Runtime runs in PUBLIC network mode with internet access. To deploy the runtime into an existing VPC for private network isolation, set `network_mode: VPC` in `infra-cdk/config.yaml` and provide your VPC details:
69
+
70
+
```yaml
71
+
backend:
72
+
pattern: strands-single-agent
73
+
deployment_type: docker
74
+
network_mode: VPC
75
+
vpc:
76
+
vpc_id: vpc-0abc1234def56789a
77
+
subnet_ids:
78
+
- subnet-aaaa1111bbbb2222c
79
+
- subnet-cccc3333dddd4444e
80
+
security_group_ids: # Optional - a default SG is created if omitted
81
+
- sg-0abc1234def56789a
82
+
```
83
+
84
+
The `vpc_id` and `subnet_ids` fields are required. The `security_group_ids` field is optional — if omitted, the CDK construct will create a default security group for the runtime.
85
+
86
+
#### Required VPC Endpoints
87
+
88
+
When deploying in VPC mode, the runtime runs in private subnets without internet access. Your VPC must have the following VPC endpoints configured so the agent can reach the AWS services it depends on:
89
+
90
+
| Endpoint | Service | Type |
91
+
|----------|---------|------|
92
+
| `com.amazonaws.{region}.bedrock-runtime` | Bedrock model invocation | Interface |
Replace `{region}` with your deployment region (e.g. `us-east-1`).
103
+
104
+
All interface endpoints must have private DNS enabled and must be associated with the same subnets and security groups that allow traffic from the AgentCore Runtime.
105
+
106
+
#### Subnet Requirements
107
+
108
+
- Use private subnets (no internet gateway route) for proper network isolation
109
+
- Subnets should be in at least two Availability Zones for high availability
110
+
- Subnets must have sufficient available IP addresses for the runtime ENIs
111
+
112
+
#### NAT Gateway Requirement
113
+
114
+
A NAT Gateway is required for VPC mode. The agent authenticates with Cognito using the OAuth2 client credentials flow, which calls the Cognito hosted UI token endpoint over HTTPS. This endpoint has no VPC endpoint — it can only be reached over the internet. A NAT Gateway in a public subnet with a `0.0.0.0/0` route from your private subnets provides this outbound IPv4 access. All other AWS service traffic (Bedrock, SSM, etc.) stays internal via VPC endpoints.
115
+
116
+
#### Security Group Configuration
117
+
118
+
The CDK stack auto-creates a security group for the AgentCore Runtime. This same security group is typically applied to your VPC endpoints. You must add a self-referencing inbound rule to allow the runtime to reach the endpoints:
119
+
120
+
- Protocol: TCP, Port: 443, Source: the security group itself
0 commit comments