GetCoreNetworkPolicyDocumentArgs constructor
- Input<
List< ? attachmentPolicies,GetCoreNetworkPolicyDocumentAttachmentPolicy> ?> - Input<
List< ? attachmentRoutingPolicyRules,GetCoreNetworkPolicyDocumentAttachmentRoutingPolicyRule> ?> - required Input<
List< coreNetworkConfigurations,GetCoreNetworkPolicyDocumentCoreNetworkConfiguration> > - Input<
List< ? networkFunctionGroups,GetCoreNetworkPolicyDocumentNetworkFunctionGroup> ?> - Input<
List< ? routingPolicies,GetCoreNetworkPolicyDocumentRoutingPolicy> ?> - Input<
List< ? segmentActions,GetCoreNetworkPolicyDocumentSegmentAction> ?> - required Input<
List< segments,GetCoreNetworkPolicyDocumentSegment> > - Input<
String?> ? version,
Creates a new GetCoreNetworkPolicyDocumentArgs.
attachmentPolicies In a core network, all attachments use the block argument attachmentPolicies section to map an attachment to a segment. Instead of manually associating a segment to each attachment, attachments use tags, and then the tags are used to associate the attachment to the specified segment. Detailed below.
attachmentRoutingPolicyRules Block argument that applies routing policies to attachments. Available in policy version 2025.11 and later. Detailed below.
coreNetworkConfigurations The core network configuration section defines the Regions where a core network should operate. For AWS Regions that are defined in the policy, the core network creates a Core Network Edge where you can connect attachments. After it's created, each Core Network Edge is peered with every other defined Region and is configured with consistent segment and routing across all Regions. Regions cannot be removed until the associated attachments are deleted. Detailed below.
networkFunctionGroups Block argument that defines the service insertion actions you want to include. Detailed below.
routingPolicies Block argument that defines routing policies for controlling route propagation. Routing policies allow you to filter, modify, and control BGP routes advertised to and from your core network. Available in policy version 2025.11 and later. Detailed below.
segmentActions A block argument, segmentActions define how routing works between segments. By default, attachments can only communicate with other attachments in the same segment. Detailed below.
segments Block argument that defines the different segments in the network. Here you can provide descriptions, change defaults, and provide explicit Regional operational and route filters. The names defined for each segment are used in the segmentActions and attachmentPolicies section. Each segment is created, and operates, as a completely separated routing domain. By default, attachments can only communicate with other attachments in the same segment. Detailed below.
version Version of the core network policy. Valid values: 2021.12, 2025.11. Default: 2021.12.
Implementation
const GetCoreNetworkPolicyDocumentArgs({
this.attachmentPolicies,
this.attachmentRoutingPolicyRules,
required this.coreNetworkConfigurations,
this.networkFunctionGroups,
this.routingPolicies,
this.segmentActions,
required this.segments,
this.version,
});