Try AWS Native preview for resources not in the classic version.
aws.networkmanager.getCoreNetworkPolicyDocument
Explore with Pulumi AI
Try AWS Native preview for resources not in the classic version.
Generates a Core Network policy document in JSON format for use with resources that expect core network policy documents such as awscc_networkmanager_core_network
. It follows the API definition from the core-network-policy documentation.
Using this data source to generate policy documents is optional. It is also valid to use literal JSON strings in your configuration or to use the file
interpolation function to read a raw JSON policy document from a file.
Example Usage
Basic Example
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
const test = aws.networkmanager.getCoreNetworkPolicyDocument({
coreNetworkConfigurations: [{
vpnEcmpSupport: false,
asnRanges: ["64512-64555"],
edgeLocations: [
{
location: "us-east-1",
asn: "64512",
},
{
location: "eu-central-1",
asn: "64513",
},
],
}],
segments: [
{
name: "shared",
description: "Segment for shared services",
requireAttachmentAcceptance: true,
},
{
name: "prod",
description: "Segment for prod services",
requireAttachmentAcceptance: true,
},
],
segmentActions: [{
action: "share",
mode: "attachment-route",
segment: "shared",
shareWiths: ["*"],
}],
attachmentPolicies: [
{
ruleNumber: 100,
conditionLogic: "or",
conditions: [{
type: "tag-value",
operator: "equals",
key: "segment",
value: "shared",
}],
action: {
associationMethod: "constant",
segment: "shared",
},
},
{
ruleNumber: 200,
conditionLogic: "or",
conditions: [{
type: "tag-value",
operator: "equals",
key: "segment",
value: "prod",
}],
action: {
associationMethod: "constant",
segment: "prod",
},
},
],
});
import pulumi
import pulumi_aws as aws
test = aws.networkmanager.get_core_network_policy_document(core_network_configurations=[{
"vpnEcmpSupport": False,
"asnRanges": ["64512-64555"],
"edgeLocations": [
{
"location": "us-east-1",
"asn": "64512",
},
{
"location": "eu-central-1",
"asn": "64513",
},
],
}],
segments=[
{
"name": "shared",
"description": "Segment for shared services",
"requireAttachmentAcceptance": True,
},
{
"name": "prod",
"description": "Segment for prod services",
"requireAttachmentAcceptance": True,
},
],
segment_actions=[{
"action": "share",
"mode": "attachment-route",
"segment": "shared",
"shareWiths": ["*"],
}],
attachment_policies=[
{
"ruleNumber": 100,
"conditionLogic": "or",
"conditions": [{
"type": "tag-value",
"operator": "equals",
"key": "segment",
"value": "shared",
}],
"action": {
"associationMethod": "constant",
"segment": "shared",
},
},
{
"ruleNumber": 200,
"conditionLogic": "or",
"conditions": [{
"type": "tag-value",
"operator": "equals",
"key": "segment",
"value": "prod",
}],
"action": {
"associationMethod": "constant",
"segment": "prod",
},
},
])
package main
import (
"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/networkmanager"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := networkmanager.GetCoreNetworkPolicyDocument(ctx, &networkmanager.GetCoreNetworkPolicyDocumentArgs{
CoreNetworkConfigurations: []networkmanager.GetCoreNetworkPolicyDocumentCoreNetworkConfiguration{
{
VpnEcmpSupport: pulumi.BoolRef(false),
AsnRanges: []string{
"64512-64555",
},
EdgeLocations: []networkmanager.GetCoreNetworkPolicyDocumentCoreNetworkConfigurationEdgeLocation{
{
Location: "us-east-1",
Asn: pulumi.StringRef("64512"),
},
{
Location: "eu-central-1",
Asn: pulumi.StringRef("64513"),
},
},
},
},
Segments: []networkmanager.GetCoreNetworkPolicyDocumentSegment{
{
Name: "shared",
Description: pulumi.StringRef("Segment for shared services"),
RequireAttachmentAcceptance: pulumi.BoolRef(true),
},
{
Name: "prod",
Description: pulumi.StringRef("Segment for prod services"),
RequireAttachmentAcceptance: pulumi.BoolRef(true),
},
},
SegmentActions: []networkmanager.GetCoreNetworkPolicyDocumentSegmentAction{
{
Action: "share",
Mode: pulumi.StringRef("attachment-route"),
Segment: "shared",
ShareWiths: []string{
"*",
},
},
},
AttachmentPolicies: []networkmanager.GetCoreNetworkPolicyDocumentAttachmentPolicy{
{
RuleNumber: 100,
ConditionLogic: pulumi.StringRef("or"),
Conditions: []networkmanager.GetCoreNetworkPolicyDocumentAttachmentPolicyCondition{
{
Type: "tag-value",
Operator: pulumi.StringRef("equals"),
Key: pulumi.StringRef("segment"),
Value: pulumi.StringRef("shared"),
},
},
Action: {
AssociationMethod: pulumi.StringRef("constant"),
Segment: pulumi.StringRef("shared"),
},
},
{
RuleNumber: 200,
ConditionLogic: pulumi.StringRef("or"),
Conditions: []networkmanager.GetCoreNetworkPolicyDocumentAttachmentPolicyCondition{
{
Type: "tag-value",
Operator: pulumi.StringRef("equals"),
Key: pulumi.StringRef("segment"),
Value: pulumi.StringRef("prod"),
},
},
Action: {
AssociationMethod: pulumi.StringRef("constant"),
Segment: pulumi.StringRef("prod"),
},
},
},
}, nil)
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Aws = Pulumi.Aws;
return await Deployment.RunAsync(() =>
{
var test = Aws.NetworkManager.GetCoreNetworkPolicyDocument.Invoke(new()
{
CoreNetworkConfigurations = new[]
{
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentCoreNetworkConfigurationInputArgs
{
VpnEcmpSupport = false,
AsnRanges = new[]
{
"64512-64555",
},
EdgeLocations = new[]
{
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentCoreNetworkConfigurationEdgeLocationInputArgs
{
Location = "us-east-1",
Asn = "64512",
},
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentCoreNetworkConfigurationEdgeLocationInputArgs
{
Location = "eu-central-1",
Asn = "64513",
},
},
},
},
Segments = new[]
{
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentSegmentInputArgs
{
Name = "shared",
Description = "Segment for shared services",
RequireAttachmentAcceptance = true,
},
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentSegmentInputArgs
{
Name = "prod",
Description = "Segment for prod services",
RequireAttachmentAcceptance = true,
},
},
SegmentActions = new[]
{
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentSegmentActionInputArgs
{
Action = "share",
Mode = "attachment-route",
Segment = "shared",
ShareWiths = new[]
{
"*",
},
},
},
AttachmentPolicies = new[]
{
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentAttachmentPolicyInputArgs
{
RuleNumber = 100,
ConditionLogic = "or",
Conditions = new[]
{
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentAttachmentPolicyConditionInputArgs
{
Type = "tag-value",
Operator = "equals",
Key = "segment",
Value = "shared",
},
},
Action = new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentAttachmentPolicyActionInputArgs
{
AssociationMethod = "constant",
Segment = "shared",
},
},
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentAttachmentPolicyInputArgs
{
RuleNumber = 200,
ConditionLogic = "or",
Conditions = new[]
{
new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentAttachmentPolicyConditionInputArgs
{
Type = "tag-value",
Operator = "equals",
Key = "segment",
Value = "prod",
},
},
Action = new Aws.NetworkManager.Inputs.GetCoreNetworkPolicyDocumentAttachmentPolicyActionInputArgs
{
AssociationMethod = "constant",
Segment = "prod",
},
},
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.networkmanager.NetworkmanagerFunctions;
import com.pulumi.aws.networkmanager.inputs.GetCoreNetworkPolicyDocumentArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var test = NetworkmanagerFunctions.getCoreNetworkPolicyDocument(GetCoreNetworkPolicyDocumentArgs.builder()
.coreNetworkConfigurations(GetCoreNetworkPolicyDocumentCoreNetworkConfigurationArgs.builder()
.vpnEcmpSupport(false)
.asnRanges("64512-64555")
.edgeLocations(
GetCoreNetworkPolicyDocumentCoreNetworkConfigurationEdgeLocationArgs.builder()
.location("us-east-1")
.asn(64512)
.build(),
GetCoreNetworkPolicyDocumentCoreNetworkConfigurationEdgeLocationArgs.builder()
.location("eu-central-1")
.asn(64513)
.build())
.build())
.segments(
GetCoreNetworkPolicyDocumentSegmentArgs.builder()
.name("shared")
.description("Segment for shared services")
.requireAttachmentAcceptance(true)
.build(),
GetCoreNetworkPolicyDocumentSegmentArgs.builder()
.name("prod")
.description("Segment for prod services")
.requireAttachmentAcceptance(true)
.build())
.segmentActions(GetCoreNetworkPolicyDocumentSegmentActionArgs.builder()
.action("share")
.mode("attachment-route")
.segment("shared")
.shareWiths("*")
.build())
.attachmentPolicies(
GetCoreNetworkPolicyDocumentAttachmentPolicyArgs.builder()
.ruleNumber(100)
.conditionLogic("or")
.conditions(GetCoreNetworkPolicyDocumentAttachmentPolicyConditionArgs.builder()
.type("tag-value")
.operator("equals")
.key("segment")
.value("shared")
.build())
.action(GetCoreNetworkPolicyDocumentAttachmentPolicyActionArgs.builder()
.associationMethod("constant")
.segment("shared")
.build())
.build(),
GetCoreNetworkPolicyDocumentAttachmentPolicyArgs.builder()
.ruleNumber(200)
.conditionLogic("or")
.conditions(GetCoreNetworkPolicyDocumentAttachmentPolicyConditionArgs.builder()
.type("tag-value")
.operator("equals")
.key("segment")
.value("prod")
.build())
.action(GetCoreNetworkPolicyDocumentAttachmentPolicyActionArgs.builder()
.associationMethod("constant")
.segment("prod")
.build())
.build())
.build());
}
}
variables:
test:
fn::invoke:
Function: aws:networkmanager:getCoreNetworkPolicyDocument
Arguments:
coreNetworkConfigurations:
- vpnEcmpSupport: false
asnRanges:
- 64512-64555
edgeLocations:
- location: us-east-1
asn: 64512
- location: eu-central-1
asn: 64513
segments:
- name: shared
description: Segment for shared services
requireAttachmentAcceptance: true
- name: prod
description: Segment for prod services
requireAttachmentAcceptance: true
segmentActions:
- action: share
mode: attachment-route
segment: shared
shareWiths:
- '*'
attachmentPolicies:
- ruleNumber: 100
conditionLogic: or
conditions:
- type: tag-value
operator: equals
key: segment
value: shared
action:
associationMethod: constant
segment: shared
- ruleNumber: 200
conditionLogic: or
conditions:
- type: tag-value
operator: equals
key: segment
value: prod
action:
associationMethod: constant
segment: prod
data.aws_networkmanager_core_network_policy_document.test.json
will evaluate to:
{
"version": "2021.12",
"core-network-configuration": {
"asn-ranges": [
"64512-64555"
],
"vpn-ecmp-support": false,
"edge-locations": [
{
"location": "us-east-1",
"asn": 64512
},
{
"location": "eu-central-1",
"asn": 64513
}
]
},
"segments": [
{
"name": "shared",
"description": "Segment for shared services",
"require-attachment-acceptance": true
},
{
"name": "prod",
"description": "Segment for prod services",
"require-attachment-acceptance": true
}
],
"attachment-policies": [
{
"rule-number": 100,
"action": {
"association-method": "constant",
"segment": "shared"
},
"conditions": [
{
"type": "tag-value",
"operator": "equals",
"key": "segment",
"value": "shared"
}
],
"condition-logic": "or"
},
{
"rule-number": 200,
"action": {
"association-method": "constant",
"segment": "prod"
},
"conditions": [
{
"type": "tag-value",
"operator": "equals",
"key": "segment",
"value": "prod"
}
],
"condition-logic": "or"
}
],
"segment-actions": [
{
"action": "share",
"mode": "attachment-route",
"segment": "shared",
"share-with": "*"
}
]
}
Using getCoreNetworkPolicyDocument
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getCoreNetworkPolicyDocument(args: GetCoreNetworkPolicyDocumentArgs, opts?: InvokeOptions): Promise<GetCoreNetworkPolicyDocumentResult>
function getCoreNetworkPolicyDocumentOutput(args: GetCoreNetworkPolicyDocumentOutputArgs, opts?: InvokeOptions): Output<GetCoreNetworkPolicyDocumentResult>
def get_core_network_policy_document(attachment_policies: Optional[Sequence[GetCoreNetworkPolicyDocumentAttachmentPolicy]] = None,
core_network_configurations: Optional[Sequence[GetCoreNetworkPolicyDocumentCoreNetworkConfiguration]] = None,
network_function_groups: Optional[Sequence[GetCoreNetworkPolicyDocumentNetworkFunctionGroup]] = None,
segment_actions: Optional[Sequence[GetCoreNetworkPolicyDocumentSegmentAction]] = None,
segments: Optional[Sequence[GetCoreNetworkPolicyDocumentSegment]] = None,
version: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetCoreNetworkPolicyDocumentResult
def get_core_network_policy_document_output(attachment_policies: Optional[pulumi.Input[Sequence[pulumi.Input[GetCoreNetworkPolicyDocumentAttachmentPolicyArgs]]]] = None,
core_network_configurations: Optional[pulumi.Input[Sequence[pulumi.Input[GetCoreNetworkPolicyDocumentCoreNetworkConfigurationArgs]]]] = None,
network_function_groups: Optional[pulumi.Input[Sequence[pulumi.Input[GetCoreNetworkPolicyDocumentNetworkFunctionGroupArgs]]]] = None,
segment_actions: Optional[pulumi.Input[Sequence[pulumi.Input[GetCoreNetworkPolicyDocumentSegmentActionArgs]]]] = None,
segments: Optional[pulumi.Input[Sequence[pulumi.Input[GetCoreNetworkPolicyDocumentSegmentArgs]]]] = None,
version: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetCoreNetworkPolicyDocumentResult]
func GetCoreNetworkPolicyDocument(ctx *Context, args *GetCoreNetworkPolicyDocumentArgs, opts ...InvokeOption) (*GetCoreNetworkPolicyDocumentResult, error)
func GetCoreNetworkPolicyDocumentOutput(ctx *Context, args *GetCoreNetworkPolicyDocumentOutputArgs, opts ...InvokeOption) GetCoreNetworkPolicyDocumentResultOutput
> Note: This function is named GetCoreNetworkPolicyDocument
in the Go SDK.
public static class GetCoreNetworkPolicyDocument
{
public static Task<GetCoreNetworkPolicyDocumentResult> InvokeAsync(GetCoreNetworkPolicyDocumentArgs args, InvokeOptions? opts = null)
public static Output<GetCoreNetworkPolicyDocumentResult> Invoke(GetCoreNetworkPolicyDocumentInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetCoreNetworkPolicyDocumentResult> getCoreNetworkPolicyDocument(GetCoreNetworkPolicyDocumentArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: aws:networkmanager/getCoreNetworkPolicyDocument:getCoreNetworkPolicyDocument
arguments:
# arguments dictionary
The following arguments are supported:
- Core
Network List<GetConfigurations Core Network Policy Document Core Network Configuration> - 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.
- Segments
List<Get
Core Network Policy Document Segment> - 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
segment_actions
andattachment_policies
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. - Attachment
Policies List<GetCore Network Policy Document Attachment Policy> - In a core network, all attachments use the block argument
attachment_policies
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. - Network
Function List<GetGroups Core Network Policy Document Network Function Group> - Block argument that defines the service insertion actions you want to include. Detailed below.
- Segment
Actions List<GetCore Network Policy Document Segment Action> - A block argument,
segment_actions
define how routing works between segments. By default, attachments can only communicate with other attachments in the same segment. Detailed below. - Version string
- Core
Network []GetConfigurations Core Network Policy Document Core Network Configuration - 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.
- Segments
[]Get
Core Network Policy Document Segment - 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
segment_actions
andattachment_policies
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. - Attachment
Policies []GetCore Network Policy Document Attachment Policy - In a core network, all attachments use the block argument
attachment_policies
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. - Network
Function []GetGroups Core Network Policy Document Network Function Group - Block argument that defines the service insertion actions you want to include. Detailed below.
- Segment
Actions []GetCore Network Policy Document Segment Action - A block argument,
segment_actions
define how routing works between segments. By default, attachments can only communicate with other attachments in the same segment. Detailed below. - Version string
- core
Network List<GetConfigurations Core Network Policy Document Core Network Configuration> - 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.
- segments
List<Get
Core Network Policy Document Segment> - 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
segment_actions
andattachment_policies
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. - attachment
Policies List<GetCore Network Policy Document Attachment Policy> - In a core network, all attachments use the block argument
attachment_policies
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. - network
Function List<GetGroups Core Network Policy Document Network Function Group> - Block argument that defines the service insertion actions you want to include. Detailed below.
- segment
Actions List<GetCore Network Policy Document Segment Action> - A block argument,
segment_actions
define how routing works between segments. By default, attachments can only communicate with other attachments in the same segment. Detailed below. - version String
- core
Network GetConfigurations Core Network Policy Document Core Network Configuration[] - 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.
- segments
Get
Core Network Policy Document Segment[] - 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
segment_actions
andattachment_policies
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. - attachment
Policies GetCore Network Policy Document Attachment Policy[] - In a core network, all attachments use the block argument
attachment_policies
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. - network
Function GetGroups Core Network Policy Document Network Function Group[] - Block argument that defines the service insertion actions you want to include. Detailed below.
- segment
Actions GetCore Network Policy Document Segment Action[] - A block argument,
segment_actions
define how routing works between segments. By default, attachments can only communicate with other attachments in the same segment. Detailed below. - version string
- core_
network_ Sequence[Getconfigurations Core Network Policy Document Core Network Configuration] - 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.
- segments
Sequence[Get
Core Network Policy Document Segment] - 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
segment_actions
andattachment_policies
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. - attachment_
policies Sequence[GetCore Network Policy Document Attachment Policy] - In a core network, all attachments use the block argument
attachment_policies
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. - network_
function_ Sequence[Getgroups Core Network Policy Document Network Function Group] - Block argument that defines the service insertion actions you want to include. Detailed below.
- segment_
actions Sequence[GetCore Network Policy Document Segment Action] - A block argument,
segment_actions
define how routing works between segments. By default, attachments can only communicate with other attachments in the same segment. Detailed below. - version str
- core
Network List<Property Map>Configurations - 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.
- segments List<Property Map>
- 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
segment_actions
andattachment_policies
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. - attachment
Policies List<Property Map> - In a core network, all attachments use the block argument
attachment_policies
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. - network
Function List<Property Map>Groups - Block argument that defines the service insertion actions you want to include. Detailed below.
- segment
Actions List<Property Map> - A block argument,
segment_actions
define how routing works between segments. By default, attachments can only communicate with other attachments in the same segment. Detailed below. - version String
getCoreNetworkPolicyDocument Result
The following output properties are available:
- Core
Network List<GetConfigurations Core Network Policy Document Core Network Configuration> - Id string
- The provider-assigned unique ID for this managed resource.
- Json string
- Standard JSON policy document rendered based on the arguments above.
- Segments
List<Get
Core Network Policy Document Segment> - Attachment
Policies List<GetCore Network Policy Document Attachment Policy> - Network
Function List<GetGroups Core Network Policy Document Network Function Group> - Segment
Actions List<GetCore Network Policy Document Segment Action> - Version string
- Core
Network []GetConfigurations Core Network Policy Document Core Network Configuration - Id string
- The provider-assigned unique ID for this managed resource.
- Json string
- Standard JSON policy document rendered based on the arguments above.
- Segments
[]Get
Core Network Policy Document Segment - Attachment
Policies []GetCore Network Policy Document Attachment Policy - Network
Function []GetGroups Core Network Policy Document Network Function Group - Segment
Actions []GetCore Network Policy Document Segment Action - Version string
- core
Network List<GetConfigurations Core Network Policy Document Core Network Configuration> - id String
- The provider-assigned unique ID for this managed resource.
- json String
- Standard JSON policy document rendered based on the arguments above.
- segments
List<Get
Core Network Policy Document Segment> - attachment
Policies List<GetCore Network Policy Document Attachment Policy> - network
Function List<GetGroups Core Network Policy Document Network Function Group> - segment
Actions List<GetCore Network Policy Document Segment Action> - version String
- core
Network GetConfigurations Core Network Policy Document Core Network Configuration[] - id string
- The provider-assigned unique ID for this managed resource.
- json string
- Standard JSON policy document rendered based on the arguments above.
- segments
Get
Core Network Policy Document Segment[] - attachment
Policies GetCore Network Policy Document Attachment Policy[] - network
Function GetGroups Core Network Policy Document Network Function Group[] - segment
Actions GetCore Network Policy Document Segment Action[] - version string
- core_
network_ Sequence[Getconfigurations Core Network Policy Document Core Network Configuration] - id str
- The provider-assigned unique ID for this managed resource.
- json str
- Standard JSON policy document rendered based on the arguments above.
- segments
Sequence[Get
Core Network Policy Document Segment] - attachment_
policies Sequence[GetCore Network Policy Document Attachment Policy] - network_
function_ Sequence[Getgroups Core Network Policy Document Network Function Group] - segment_
actions Sequence[GetCore Network Policy Document Segment Action] - version str
- core
Network List<Property Map>Configurations - id String
- The provider-assigned unique ID for this managed resource.
- json String
- Standard JSON policy document rendered based on the arguments above.
- segments List<Property Map>
- attachment
Policies List<Property Map> - network
Function List<Property Map>Groups - segment
Actions List<Property Map> - version String
Supporting Types
GetCoreNetworkPolicyDocumentAttachmentPolicy
- Action
Get
Core Network Policy Document Attachment Policy Action - Action to take when a condition is true. Detailed Below.
- Conditions
List<Get
Core Network Policy Document Attachment Policy Condition> - A block argument. Detailed Below.
- Rule
Number int - An integer from
1
to65535
indicating the rule's order number. Rules are processed in order from the lowest numbered rule to the highest. Rules stop processing when a rule is matched. It's important to make sure that you number your rules in the exact order that you want them processed. - Condition
Logic string - Valid values include
and
oror
. This is a mandatory parameter only if you have more than one condition. Thecondition_logic
apply to all of the conditions for a rule, which also means nested conditions ofand
oror
are not supported. Useor
if you want to associate the attachment with the segment by either the segment name or attachment tag value, or by the chosen conditions. Useand
if you want to associate the attachment with the segment by either the segment name or attachment tag value and by the chosen conditions. Detailed Below. - Description string
- A user-defined description that further helps identify the rule.
- Action
Get
Core Network Policy Document Attachment Policy Action - Action to take when a condition is true. Detailed Below.
- Conditions
[]Get
Core Network Policy Document Attachment Policy Condition - A block argument. Detailed Below.
- Rule
Number int - An integer from
1
to65535
indicating the rule's order number. Rules are processed in order from the lowest numbered rule to the highest. Rules stop processing when a rule is matched. It's important to make sure that you number your rules in the exact order that you want them processed. - Condition
Logic string - Valid values include
and
oror
. This is a mandatory parameter only if you have more than one condition. Thecondition_logic
apply to all of the conditions for a rule, which also means nested conditions ofand
oror
are not supported. Useor
if you want to associate the attachment with the segment by either the segment name or attachment tag value, or by the chosen conditions. Useand
if you want to associate the attachment with the segment by either the segment name or attachment tag value and by the chosen conditions. Detailed Below. - Description string
- A user-defined description that further helps identify the rule.
- action
Get
Core Network Policy Document Attachment Policy Action - Action to take when a condition is true. Detailed Below.
- conditions
List<Get
Core Network Policy Document Attachment Policy Condition> - A block argument. Detailed Below.
- rule
Number Integer - An integer from
1
to65535
indicating the rule's order number. Rules are processed in order from the lowest numbered rule to the highest. Rules stop processing when a rule is matched. It's important to make sure that you number your rules in the exact order that you want them processed. - condition
Logic String - Valid values include
and
oror
. This is a mandatory parameter only if you have more than one condition. Thecondition_logic
apply to all of the conditions for a rule, which also means nested conditions ofand
oror
are not supported. Useor
if you want to associate the attachment with the segment by either the segment name or attachment tag value, or by the chosen conditions. Useand
if you want to associate the attachment with the segment by either the segment name or attachment tag value and by the chosen conditions. Detailed Below. - description String
- A user-defined description that further helps identify the rule.
- action
Get
Core Network Policy Document Attachment Policy Action - Action to take when a condition is true. Detailed Below.
- conditions
Get
Core Network Policy Document Attachment Policy Condition[] - A block argument. Detailed Below.
- rule
Number number - An integer from
1
to65535
indicating the rule's order number. Rules are processed in order from the lowest numbered rule to the highest. Rules stop processing when a rule is matched. It's important to make sure that you number your rules in the exact order that you want them processed. - condition
Logic string - Valid values include
and
oror
. This is a mandatory parameter only if you have more than one condition. Thecondition_logic
apply to all of the conditions for a rule, which also means nested conditions ofand
oror
are not supported. Useor
if you want to associate the attachment with the segment by either the segment name or attachment tag value, or by the chosen conditions. Useand
if you want to associate the attachment with the segment by either the segment name or attachment tag value and by the chosen conditions. Detailed Below. - description string
- A user-defined description that further helps identify the rule.
- action
Get
Core Network Policy Document Attachment Policy Action - Action to take when a condition is true. Detailed Below.
- conditions
Sequence[Get
Core Network Policy Document Attachment Policy Condition] - A block argument. Detailed Below.
- rule_
number int - An integer from
1
to65535
indicating the rule's order number. Rules are processed in order from the lowest numbered rule to the highest. Rules stop processing when a rule is matched. It's important to make sure that you number your rules in the exact order that you want them processed. - condition_
logic str - Valid values include
and
oror
. This is a mandatory parameter only if you have more than one condition. Thecondition_logic
apply to all of the conditions for a rule, which also means nested conditions ofand
oror
are not supported. Useor
if you want to associate the attachment with the segment by either the segment name or attachment tag value, or by the chosen conditions. Useand
if you want to associate the attachment with the segment by either the segment name or attachment tag value and by the chosen conditions. Detailed Below. - description str
- A user-defined description that further helps identify the rule.
- action Property Map
- Action to take when a condition is true. Detailed Below.
- conditions List<Property Map>
- A block argument. Detailed Below.
- rule
Number Number - An integer from
1
to65535
indicating the rule's order number. Rules are processed in order from the lowest numbered rule to the highest. Rules stop processing when a rule is matched. It's important to make sure that you number your rules in the exact order that you want them processed. - condition
Logic String - Valid values include
and
oror
. This is a mandatory parameter only if you have more than one condition. Thecondition_logic
apply to all of the conditions for a rule, which also means nested conditions ofand
oror
are not supported. Useor
if you want to associate the attachment with the segment by either the segment name or attachment tag value, or by the chosen conditions. Useand
if you want to associate the attachment with the segment by either the segment name or attachment tag value and by the chosen conditions. Detailed Below. - description String
- A user-defined description that further helps identify the rule.
GetCoreNetworkPolicyDocumentAttachmentPolicyAction
- Add
To stringNetwork Function Group - The name of the network function group to attach to the attachment policy.
- Association
Method string - Defines how a segment is mapped. Values can be
constant
ortag
.constant
statically defines the segment to associate the attachment to.tag
uses the value of a tag to dynamically try to map to a segment.reference_policies_elements_condition_operators.html) to evaluate. - Require
Acceptance bool - Determines if this mapping should override the segment value for
require_attachment_acceptance
. You can only set this totrue
, indicating that this setting applies only to segments that haverequire_attachment_acceptance
set tofalse
. If the segment already has the defaultrequire_attachment_acceptance
, you can set this to inherit segment’s acceptance value. - Segment string
- Name of the
segment
to share as defined in thesegments
section. This is used only when theassociation_method
isconstant
. - Tag
Value stringOf Key - Maps the attachment to the value of a known key. This is used with the
association_method
istag
. For example atag
ofstage = “test”
, will map to a segment namedtest
. The value must exactly match the name of a segment. This allows you to have many segments, but use only a single rule without having to define multiple nearly identical conditions. This prevents creating many similar conditions that all use the same keys to map to segments.
- Add
To stringNetwork Function Group - The name of the network function group to attach to the attachment policy.
- Association
Method string - Defines how a segment is mapped. Values can be
constant
ortag
.constant
statically defines the segment to associate the attachment to.tag
uses the value of a tag to dynamically try to map to a segment.reference_policies_elements_condition_operators.html) to evaluate. - Require
Acceptance bool - Determines if this mapping should override the segment value for
require_attachment_acceptance
. You can only set this totrue
, indicating that this setting applies only to segments that haverequire_attachment_acceptance
set tofalse
. If the segment already has the defaultrequire_attachment_acceptance
, you can set this to inherit segment’s acceptance value. - Segment string
- Name of the
segment
to share as defined in thesegments
section. This is used only when theassociation_method
isconstant
. - Tag
Value stringOf Key - Maps the attachment to the value of a known key. This is used with the
association_method
istag
. For example atag
ofstage = “test”
, will map to a segment namedtest
. The value must exactly match the name of a segment. This allows you to have many segments, but use only a single rule without having to define multiple nearly identical conditions. This prevents creating many similar conditions that all use the same keys to map to segments.
- add
To StringNetwork Function Group - The name of the network function group to attach to the attachment policy.
- association
Method String - Defines how a segment is mapped. Values can be
constant
ortag
.constant
statically defines the segment to associate the attachment to.tag
uses the value of a tag to dynamically try to map to a segment.reference_policies_elements_condition_operators.html) to evaluate. - require
Acceptance Boolean - Determines if this mapping should override the segment value for
require_attachment_acceptance
. You can only set this totrue
, indicating that this setting applies only to segments that haverequire_attachment_acceptance
set tofalse
. If the segment already has the defaultrequire_attachment_acceptance
, you can set this to inherit segment’s acceptance value. - segment String
- Name of the
segment
to share as defined in thesegments
section. This is used only when theassociation_method
isconstant
. - tag
Value StringOf Key - Maps the attachment to the value of a known key. This is used with the
association_method
istag
. For example atag
ofstage = “test”
, will map to a segment namedtest
. The value must exactly match the name of a segment. This allows you to have many segments, but use only a single rule without having to define multiple nearly identical conditions. This prevents creating many similar conditions that all use the same keys to map to segments.
- add
To stringNetwork Function Group - The name of the network function group to attach to the attachment policy.
- association
Method string - Defines how a segment is mapped. Values can be
constant
ortag
.constant
statically defines the segment to associate the attachment to.tag
uses the value of a tag to dynamically try to map to a segment.reference_policies_elements_condition_operators.html) to evaluate. - require
Acceptance boolean - Determines if this mapping should override the segment value for
require_attachment_acceptance
. You can only set this totrue
, indicating that this setting applies only to segments that haverequire_attachment_acceptance
set tofalse
. If the segment already has the defaultrequire_attachment_acceptance
, you can set this to inherit segment’s acceptance value. - segment string
- Name of the
segment
to share as defined in thesegments
section. This is used only when theassociation_method
isconstant
. - tag
Value stringOf Key - Maps the attachment to the value of a known key. This is used with the
association_method
istag
. For example atag
ofstage = “test”
, will map to a segment namedtest
. The value must exactly match the name of a segment. This allows you to have many segments, but use only a single rule without having to define multiple nearly identical conditions. This prevents creating many similar conditions that all use the same keys to map to segments.
- add_
to_ strnetwork_ function_ group - The name of the network function group to attach to the attachment policy.
- association_
method str - Defines how a segment is mapped. Values can be
constant
ortag
.constant
statically defines the segment to associate the attachment to.tag
uses the value of a tag to dynamically try to map to a segment.reference_policies_elements_condition_operators.html) to evaluate. - require_
acceptance bool - Determines if this mapping should override the segment value for
require_attachment_acceptance
. You can only set this totrue
, indicating that this setting applies only to segments that haverequire_attachment_acceptance
set tofalse
. If the segment already has the defaultrequire_attachment_acceptance
, you can set this to inherit segment’s acceptance value. - segment str
- Name of the
segment
to share as defined in thesegments
section. This is used only when theassociation_method
isconstant
. - tag_
value_ strof_ key - Maps the attachment to the value of a known key. This is used with the
association_method
istag
. For example atag
ofstage = “test”
, will map to a segment namedtest
. The value must exactly match the name of a segment. This allows you to have many segments, but use only a single rule without having to define multiple nearly identical conditions. This prevents creating many similar conditions that all use the same keys to map to segments.
- add
To StringNetwork Function Group - The name of the network function group to attach to the attachment policy.
- association
Method String - Defines how a segment is mapped. Values can be
constant
ortag
.constant
statically defines the segment to associate the attachment to.tag
uses the value of a tag to dynamically try to map to a segment.reference_policies_elements_condition_operators.html) to evaluate. - require
Acceptance Boolean - Determines if this mapping should override the segment value for
require_attachment_acceptance
. You can only set this totrue
, indicating that this setting applies only to segments that haverequire_attachment_acceptance
set tofalse
. If the segment already has the defaultrequire_attachment_acceptance
, you can set this to inherit segment’s acceptance value. - segment String
- Name of the
segment
to share as defined in thesegments
section. This is used only when theassociation_method
isconstant
. - tag
Value StringOf Key - Maps the attachment to the value of a known key. This is used with the
association_method
istag
. For example atag
ofstage = “test”
, will map to a segment namedtest
. The value must exactly match the name of a segment. This allows you to have many segments, but use only a single rule without having to define multiple nearly identical conditions. This prevents creating many similar conditions that all use the same keys to map to segments.
GetCoreNetworkPolicyDocumentAttachmentPolicyCondition
GetCoreNetworkPolicyDocumentCoreNetworkConfiguration
- Asn
Ranges List<string> - List of strings containing Autonomous System Numbers (ASNs) to assign to Core Network Edges. By default, the core network automatically assigns an ASN for each Core Network Edge but you can optionally define the ASN in the edge-locations for each Region. The ASN uses an array of integer ranges only from
64512
to65534
and4200000000
to4294967294
expressed as a string like"64512-65534"
. No other ASN ranges can be used. - Edge
Locations List<GetCore Network Policy Document Core Network Configuration Edge Location> - A block value of AWS Region locations where you're creating Core Network Edges. Detailed below.
- Inside
Cidr List<string>Blocks - The Classless Inter-Domain Routing (CIDR) block range used to create tunnels for AWS Transit Gateway Connect. The format is standard AWS CIDR range (for example,
10.0.1.0/24
). You can optionally define the inside CIDR in the Core Network Edges section per Region. The minimum is a/24
for IPv4 or/64
for IPv6. You can provide multiple/24
subnets or a larger CIDR range. If you define a larger CIDR range, new Core Network Edges will be automatically assigned/24
and/64
subnets from the larger CIDR. an Inside CIDR block is required for attaching Connect attachments to a Core Network Edge. - Vpn
Ecmp boolSupport - Indicates whether the core network forwards traffic over multiple equal-cost routes using VPN. The value can be either
true
orfalse
. The default istrue
.
- Asn
Ranges []string - List of strings containing Autonomous System Numbers (ASNs) to assign to Core Network Edges. By default, the core network automatically assigns an ASN for each Core Network Edge but you can optionally define the ASN in the edge-locations for each Region. The ASN uses an array of integer ranges only from
64512
to65534
and4200000000
to4294967294
expressed as a string like"64512-65534"
. No other ASN ranges can be used. - Edge
Locations []GetCore Network Policy Document Core Network Configuration Edge Location - A block value of AWS Region locations where you're creating Core Network Edges. Detailed below.
- Inside
Cidr []stringBlocks - The Classless Inter-Domain Routing (CIDR) block range used to create tunnels for AWS Transit Gateway Connect. The format is standard AWS CIDR range (for example,
10.0.1.0/24
). You can optionally define the inside CIDR in the Core Network Edges section per Region. The minimum is a/24
for IPv4 or/64
for IPv6. You can provide multiple/24
subnets or a larger CIDR range. If you define a larger CIDR range, new Core Network Edges will be automatically assigned/24
and/64
subnets from the larger CIDR. an Inside CIDR block is required for attaching Connect attachments to a Core Network Edge. - Vpn
Ecmp boolSupport - Indicates whether the core network forwards traffic over multiple equal-cost routes using VPN. The value can be either
true
orfalse
. The default istrue
.
- asn
Ranges List<String> - List of strings containing Autonomous System Numbers (ASNs) to assign to Core Network Edges. By default, the core network automatically assigns an ASN for each Core Network Edge but you can optionally define the ASN in the edge-locations for each Region. The ASN uses an array of integer ranges only from
64512
to65534
and4200000000
to4294967294
expressed as a string like"64512-65534"
. No other ASN ranges can be used. - edge
Locations List<GetCore Network Policy Document Core Network Configuration Edge Location> - A block value of AWS Region locations where you're creating Core Network Edges. Detailed below.
- inside
Cidr List<String>Blocks - The Classless Inter-Domain Routing (CIDR) block range used to create tunnels for AWS Transit Gateway Connect. The format is standard AWS CIDR range (for example,
10.0.1.0/24
). You can optionally define the inside CIDR in the Core Network Edges section per Region. The minimum is a/24
for IPv4 or/64
for IPv6. You can provide multiple/24
subnets or a larger CIDR range. If you define a larger CIDR range, new Core Network Edges will be automatically assigned/24
and/64
subnets from the larger CIDR. an Inside CIDR block is required for attaching Connect attachments to a Core Network Edge. - vpn
Ecmp BooleanSupport - Indicates whether the core network forwards traffic over multiple equal-cost routes using VPN. The value can be either
true
orfalse
. The default istrue
.
- asn
Ranges string[] - List of strings containing Autonomous System Numbers (ASNs) to assign to Core Network Edges. By default, the core network automatically assigns an ASN for each Core Network Edge but you can optionally define the ASN in the edge-locations for each Region. The ASN uses an array of integer ranges only from
64512
to65534
and4200000000
to4294967294
expressed as a string like"64512-65534"
. No other ASN ranges can be used. - edge
Locations GetCore Network Policy Document Core Network Configuration Edge Location[] - A block value of AWS Region locations where you're creating Core Network Edges. Detailed below.
- inside
Cidr string[]Blocks - The Classless Inter-Domain Routing (CIDR) block range used to create tunnels for AWS Transit Gateway Connect. The format is standard AWS CIDR range (for example,
10.0.1.0/24
). You can optionally define the inside CIDR in the Core Network Edges section per Region. The minimum is a/24
for IPv4 or/64
for IPv6. You can provide multiple/24
subnets or a larger CIDR range. If you define a larger CIDR range, new Core Network Edges will be automatically assigned/24
and/64
subnets from the larger CIDR. an Inside CIDR block is required for attaching Connect attachments to a Core Network Edge. - vpn
Ecmp booleanSupport - Indicates whether the core network forwards traffic over multiple equal-cost routes using VPN. The value can be either
true
orfalse
. The default istrue
.
- asn_
ranges Sequence[str] - List of strings containing Autonomous System Numbers (ASNs) to assign to Core Network Edges. By default, the core network automatically assigns an ASN for each Core Network Edge but you can optionally define the ASN in the edge-locations for each Region. The ASN uses an array of integer ranges only from
64512
to65534
and4200000000
to4294967294
expressed as a string like"64512-65534"
. No other ASN ranges can be used. - edge_
locations Sequence[GetCore Network Policy Document Core Network Configuration Edge Location] - A block value of AWS Region locations where you're creating Core Network Edges. Detailed below.
- inside_
cidr_ Sequence[str]blocks - The Classless Inter-Domain Routing (CIDR) block range used to create tunnels for AWS Transit Gateway Connect. The format is standard AWS CIDR range (for example,
10.0.1.0/24
). You can optionally define the inside CIDR in the Core Network Edges section per Region. The minimum is a/24
for IPv4 or/64
for IPv6. You can provide multiple/24
subnets or a larger CIDR range. If you define a larger CIDR range, new Core Network Edges will be automatically assigned/24
and/64
subnets from the larger CIDR. an Inside CIDR block is required for attaching Connect attachments to a Core Network Edge. - vpn_
ecmp_ boolsupport - Indicates whether the core network forwards traffic over multiple equal-cost routes using VPN. The value can be either
true
orfalse
. The default istrue
.
- asn
Ranges List<String> - List of strings containing Autonomous System Numbers (ASNs) to assign to Core Network Edges. By default, the core network automatically assigns an ASN for each Core Network Edge but you can optionally define the ASN in the edge-locations for each Region. The ASN uses an array of integer ranges only from
64512
to65534
and4200000000
to4294967294
expressed as a string like"64512-65534"
. No other ASN ranges can be used. - edge
Locations List<Property Map> - A block value of AWS Region locations where you're creating Core Network Edges. Detailed below.
- inside
Cidr List<String>Blocks - The Classless Inter-Domain Routing (CIDR) block range used to create tunnels for AWS Transit Gateway Connect. The format is standard AWS CIDR range (for example,
10.0.1.0/24
). You can optionally define the inside CIDR in the Core Network Edges section per Region. The minimum is a/24
for IPv4 or/64
for IPv6. You can provide multiple/24
subnets or a larger CIDR range. If you define a larger CIDR range, new Core Network Edges will be automatically assigned/24
and/64
subnets from the larger CIDR. an Inside CIDR block is required for attaching Connect attachments to a Core Network Edge. - vpn
Ecmp BooleanSupport - Indicates whether the core network forwards traffic over multiple equal-cost routes using VPN. The value can be either
true
orfalse
. The default istrue
.
GetCoreNetworkPolicyDocumentCoreNetworkConfigurationEdgeLocation
- Location string
- Asn string
- ASN of the Core Network Edge in an AWS Region. By default, the ASN will be a single integer automatically assigned from
asn_ranges
- Inside
Cidr List<string>Blocks - The local CIDR blocks for this Core Network Edge for AWS Transit Gateway Connect attachments. By default, this CIDR block will be one or more optional IPv4 and IPv6 CIDR prefixes auto-assigned from
inside_cidr_blocks
.
- Location string
- Asn string
- ASN of the Core Network Edge in an AWS Region. By default, the ASN will be a single integer automatically assigned from
asn_ranges
- Inside
Cidr []stringBlocks - The local CIDR blocks for this Core Network Edge for AWS Transit Gateway Connect attachments. By default, this CIDR block will be one or more optional IPv4 and IPv6 CIDR prefixes auto-assigned from
inside_cidr_blocks
.
- location String
- asn String
- ASN of the Core Network Edge in an AWS Region. By default, the ASN will be a single integer automatically assigned from
asn_ranges
- inside
Cidr List<String>Blocks - The local CIDR blocks for this Core Network Edge for AWS Transit Gateway Connect attachments. By default, this CIDR block will be one or more optional IPv4 and IPv6 CIDR prefixes auto-assigned from
inside_cidr_blocks
.
- location string
- asn string
- ASN of the Core Network Edge in an AWS Region. By default, the ASN will be a single integer automatically assigned from
asn_ranges
- inside
Cidr string[]Blocks - The local CIDR blocks for this Core Network Edge for AWS Transit Gateway Connect attachments. By default, this CIDR block will be one or more optional IPv4 and IPv6 CIDR prefixes auto-assigned from
inside_cidr_blocks
.
- location str
- asn str
- ASN of the Core Network Edge in an AWS Region. By default, the ASN will be a single integer automatically assigned from
asn_ranges
- inside_
cidr_ Sequence[str]blocks - The local CIDR blocks for this Core Network Edge for AWS Transit Gateway Connect attachments. By default, this CIDR block will be one or more optional IPv4 and IPv6 CIDR prefixes auto-assigned from
inside_cidr_blocks
.
- location String
- asn String
- ASN of the Core Network Edge in an AWS Region. By default, the ASN will be a single integer automatically assigned from
asn_ranges
- inside
Cidr List<String>Blocks - The local CIDR blocks for this Core Network Edge for AWS Transit Gateway Connect attachments. By default, this CIDR block will be one or more optional IPv4 and IPv6 CIDR prefixes auto-assigned from
inside_cidr_blocks
.
GetCoreNetworkPolicyDocumentNetworkFunctionGroup
- Name string
- This identifies the network function group container.
- Require
Attachment boolAcceptance - This will be either
true
, that attachment acceptance is required, orfalse
, that it is not required. - Description string
- Optional description of the network function group.
- Name string
- This identifies the network function group container.
- Require
Attachment boolAcceptance - This will be either
true
, that attachment acceptance is required, orfalse
, that it is not required. - Description string
- Optional description of the network function group.
- name String
- This identifies the network function group container.
- require
Attachment BooleanAcceptance - This will be either
true
, that attachment acceptance is required, orfalse
, that it is not required. - description String
- Optional description of the network function group.
- name string
- This identifies the network function group container.
- require
Attachment booleanAcceptance - This will be either
true
, that attachment acceptance is required, orfalse
, that it is not required. - description string
- Optional description of the network function group.
- name str
- This identifies the network function group container.
- require_
attachment_ boolacceptance - This will be either
true
, that attachment acceptance is required, orfalse
, that it is not required. - description str
- Optional description of the network function group.
- name String
- This identifies the network function group container.
- require
Attachment BooleanAcceptance - This will be either
true
, that attachment acceptance is required, orfalse
, that it is not required. - description String
- Optional description of the network function group.
GetCoreNetworkPolicyDocumentSegment
- Name string
- Unique name for a segment. The name is a string used in other parts of the policy document, as well as in the console for metrics and other reference points. Valid characters are a–z, and 0–9.
- Allow
Filters List<string> - List of strings of segment names that explicitly allows only routes from the segments that are listed in the array. Use the
allow_filter
setting if a segment has a well-defined group of other segments that connectivity should be restricted to. It is applied after routes have been shared insegment_actions
. If a segment is listed inallow_filter
, attachments between the two segments will have routes if they are also shared in the segment-actions area. For example, you might have a segment named "video-producer" that should only ever share routes with a "video-distributor" segment, no matter how many other share statements are created. - Deny
Filters List<string> - An array of segments that disallows routes from the segments listed in the array. It is applied only after routes have been shared in
segment_actions
. If a segment is listed in thedeny_filter
, attachments between the two segments will never have routes shared across them. For example, you might have a "financial" payment segment that should never share routes with a "development" segment, regardless of how many other share statements are created. Adding the payments segment to the deny-filter parameter prevents any shared routes from being created with other segments. - Description string
- A user-defined string describing the segment.
- Edge
Locations List<string> - A list of strings of AWS Region names. Allows you to define a more restrictive set of Regions for a segment. The edge location must be a subset of the locations that are defined for
edge_locations
in thecore_network_configuration
. - Isolate
Attachments bool - This Boolean setting determines whether attachments on the same segment can communicate with each other. If set to
true
, the only routes available will be either shared routes through the share actions, which are attachments in other segments, or static routes. The default value isfalse
. For example, you might have a segment dedicated to "development" that should never allow VPCs to talk to each other, even if they’re on the same segment. In this example, you would keep the default parameter offalse
. - Require
Attachment boolAcceptance - This Boolean setting determines whether attachment requests are automatically approved or require acceptance. The default is
true
, indicating that attachment requests require acceptance. For example, you might use this setting to allow a "sandbox" segment to allow any attachment request so that a core network or attachment administrator does not need to review and approve attachment requests. In this example,require_attachment_acceptance
is set tofalse
.
- Name string
- Unique name for a segment. The name is a string used in other parts of the policy document, as well as in the console for metrics and other reference points. Valid characters are a–z, and 0–9.
- Allow
Filters []string - List of strings of segment names that explicitly allows only routes from the segments that are listed in the array. Use the
allow_filter
setting if a segment has a well-defined group of other segments that connectivity should be restricted to. It is applied after routes have been shared insegment_actions
. If a segment is listed inallow_filter
, attachments between the two segments will have routes if they are also shared in the segment-actions area. For example, you might have a segment named "video-producer" that should only ever share routes with a "video-distributor" segment, no matter how many other share statements are created. - Deny
Filters []string - An array of segments that disallows routes from the segments listed in the array. It is applied only after routes have been shared in
segment_actions
. If a segment is listed in thedeny_filter
, attachments between the two segments will never have routes shared across them. For example, you might have a "financial" payment segment that should never share routes with a "development" segment, regardless of how many other share statements are created. Adding the payments segment to the deny-filter parameter prevents any shared routes from being created with other segments. - Description string
- A user-defined string describing the segment.
- Edge
Locations []string - A list of strings of AWS Region names. Allows you to define a more restrictive set of Regions for a segment. The edge location must be a subset of the locations that are defined for
edge_locations
in thecore_network_configuration
. - Isolate
Attachments bool - This Boolean setting determines whether attachments on the same segment can communicate with each other. If set to
true
, the only routes available will be either shared routes through the share actions, which are attachments in other segments, or static routes. The default value isfalse
. For example, you might have a segment dedicated to "development" that should never allow VPCs to talk to each other, even if they’re on the same segment. In this example, you would keep the default parameter offalse
. - Require
Attachment boolAcceptance - This Boolean setting determines whether attachment requests are automatically approved or require acceptance. The default is
true
, indicating that attachment requests require acceptance. For example, you might use this setting to allow a "sandbox" segment to allow any attachment request so that a core network or attachment administrator does not need to review and approve attachment requests. In this example,require_attachment_acceptance
is set tofalse
.
- name String
- Unique name for a segment. The name is a string used in other parts of the policy document, as well as in the console for metrics and other reference points. Valid characters are a–z, and 0–9.
- allow
Filters List<String> - List of strings of segment names that explicitly allows only routes from the segments that are listed in the array. Use the
allow_filter
setting if a segment has a well-defined group of other segments that connectivity should be restricted to. It is applied after routes have been shared insegment_actions
. If a segment is listed inallow_filter
, attachments between the two segments will have routes if they are also shared in the segment-actions area. For example, you might have a segment named "video-producer" that should only ever share routes with a "video-distributor" segment, no matter how many other share statements are created. - deny
Filters List<String> - An array of segments that disallows routes from the segments listed in the array. It is applied only after routes have been shared in
segment_actions
. If a segment is listed in thedeny_filter
, attachments between the two segments will never have routes shared across them. For example, you might have a "financial" payment segment that should never share routes with a "development" segment, regardless of how many other share statements are created. Adding the payments segment to the deny-filter parameter prevents any shared routes from being created with other segments. - description String
- A user-defined string describing the segment.
- edge
Locations List<String> - A list of strings of AWS Region names. Allows you to define a more restrictive set of Regions for a segment. The edge location must be a subset of the locations that are defined for
edge_locations
in thecore_network_configuration
. - isolate
Attachments Boolean - This Boolean setting determines whether attachments on the same segment can communicate with each other. If set to
true
, the only routes available will be either shared routes through the share actions, which are attachments in other segments, or static routes. The default value isfalse
. For example, you might have a segment dedicated to "development" that should never allow VPCs to talk to each other, even if they’re on the same segment. In this example, you would keep the default parameter offalse
. - require
Attachment BooleanAcceptance - This Boolean setting determines whether attachment requests are automatically approved or require acceptance. The default is
true
, indicating that attachment requests require acceptance. For example, you might use this setting to allow a "sandbox" segment to allow any attachment request so that a core network or attachment administrator does not need to review and approve attachment requests. In this example,require_attachment_acceptance
is set tofalse
.
- name string
- Unique name for a segment. The name is a string used in other parts of the policy document, as well as in the console for metrics and other reference points. Valid characters are a–z, and 0–9.
- allow
Filters string[] - List of strings of segment names that explicitly allows only routes from the segments that are listed in the array. Use the
allow_filter
setting if a segment has a well-defined group of other segments that connectivity should be restricted to. It is applied after routes have been shared insegment_actions
. If a segment is listed inallow_filter
, attachments between the two segments will have routes if they are also shared in the segment-actions area. For example, you might have a segment named "video-producer" that should only ever share routes with a "video-distributor" segment, no matter how many other share statements are created. - deny
Filters string[] - An array of segments that disallows routes from the segments listed in the array. It is applied only after routes have been shared in
segment_actions
. If a segment is listed in thedeny_filter
, attachments between the two segments will never have routes shared across them. For example, you might have a "financial" payment segment that should never share routes with a "development" segment, regardless of how many other share statements are created. Adding the payments segment to the deny-filter parameter prevents any shared routes from being created with other segments. - description string
- A user-defined string describing the segment.
- edge
Locations string[] - A list of strings of AWS Region names. Allows you to define a more restrictive set of Regions for a segment. The edge location must be a subset of the locations that are defined for
edge_locations
in thecore_network_configuration
. - isolate
Attachments boolean - This Boolean setting determines whether attachments on the same segment can communicate with each other. If set to
true
, the only routes available will be either shared routes through the share actions, which are attachments in other segments, or static routes. The default value isfalse
. For example, you might have a segment dedicated to "development" that should never allow VPCs to talk to each other, even if they’re on the same segment. In this example, you would keep the default parameter offalse
. - require
Attachment booleanAcceptance - This Boolean setting determines whether attachment requests are automatically approved or require acceptance. The default is
true
, indicating that attachment requests require acceptance. For example, you might use this setting to allow a "sandbox" segment to allow any attachment request so that a core network or attachment administrator does not need to review and approve attachment requests. In this example,require_attachment_acceptance
is set tofalse
.
- name str
- Unique name for a segment. The name is a string used in other parts of the policy document, as well as in the console for metrics and other reference points. Valid characters are a–z, and 0–9.
- allow_
filters Sequence[str] - List of strings of segment names that explicitly allows only routes from the segments that are listed in the array. Use the
allow_filter
setting if a segment has a well-defined group of other segments that connectivity should be restricted to. It is applied after routes have been shared insegment_actions
. If a segment is listed inallow_filter
, attachments between the two segments will have routes if they are also shared in the segment-actions area. For example, you might have a segment named "video-producer" that should only ever share routes with a "video-distributor" segment, no matter how many other share statements are created. - deny_
filters Sequence[str] - An array of segments that disallows routes from the segments listed in the array. It is applied only after routes have been shared in
segment_actions
. If a segment is listed in thedeny_filter
, attachments between the two segments will never have routes shared across them. For example, you might have a "financial" payment segment that should never share routes with a "development" segment, regardless of how many other share statements are created. Adding the payments segment to the deny-filter parameter prevents any shared routes from being created with other segments. - description str
- A user-defined string describing the segment.
- edge_
locations Sequence[str] - A list of strings of AWS Region names. Allows you to define a more restrictive set of Regions for a segment. The edge location must be a subset of the locations that are defined for
edge_locations
in thecore_network_configuration
. - isolate_
attachments bool - This Boolean setting determines whether attachments on the same segment can communicate with each other. If set to
true
, the only routes available will be either shared routes through the share actions, which are attachments in other segments, or static routes. The default value isfalse
. For example, you might have a segment dedicated to "development" that should never allow VPCs to talk to each other, even if they’re on the same segment. In this example, you would keep the default parameter offalse
. - require_
attachment_ boolacceptance - This Boolean setting determines whether attachment requests are automatically approved or require acceptance. The default is
true
, indicating that attachment requests require acceptance. For example, you might use this setting to allow a "sandbox" segment to allow any attachment request so that a core network or attachment administrator does not need to review and approve attachment requests. In this example,require_attachment_acceptance
is set tofalse
.
- name String
- Unique name for a segment. The name is a string used in other parts of the policy document, as well as in the console for metrics and other reference points. Valid characters are a–z, and 0–9.
- allow
Filters List<String> - List of strings of segment names that explicitly allows only routes from the segments that are listed in the array. Use the
allow_filter
setting if a segment has a well-defined group of other segments that connectivity should be restricted to. It is applied after routes have been shared insegment_actions
. If a segment is listed inallow_filter
, attachments between the two segments will have routes if they are also shared in the segment-actions area. For example, you might have a segment named "video-producer" that should only ever share routes with a "video-distributor" segment, no matter how many other share statements are created. - deny
Filters List<String> - An array of segments that disallows routes from the segments listed in the array. It is applied only after routes have been shared in
segment_actions
. If a segment is listed in thedeny_filter
, attachments between the two segments will never have routes shared across them. For example, you might have a "financial" payment segment that should never share routes with a "development" segment, regardless of how many other share statements are created. Adding the payments segment to the deny-filter parameter prevents any shared routes from being created with other segments. - description String
- A user-defined string describing the segment.
- edge
Locations List<String> - A list of strings of AWS Region names. Allows you to define a more restrictive set of Regions for a segment. The edge location must be a subset of the locations that are defined for
edge_locations
in thecore_network_configuration
. - isolate
Attachments Boolean - This Boolean setting determines whether attachments on the same segment can communicate with each other. If set to
true
, the only routes available will be either shared routes through the share actions, which are attachments in other segments, or static routes. The default value isfalse
. For example, you might have a segment dedicated to "development" that should never allow VPCs to talk to each other, even if they’re on the same segment. In this example, you would keep the default parameter offalse
. - require
Attachment BooleanAcceptance - This Boolean setting determines whether attachment requests are automatically approved or require acceptance. The default is
true
, indicating that attachment requests require acceptance. For example, you might use this setting to allow a "sandbox" segment to allow any attachment request so that a core network or attachment administrator does not need to review and approve attachment requests. In this example,require_attachment_acceptance
is set tofalse
.
GetCoreNetworkPolicyDocumentSegmentAction
- Action string
- Action to take for the chosen segment. Valid values:
create-route
,share
,send-via
andsend-to
. - Segment string
- Name of the segment.
- Description string
- A user-defined string describing the segment action.
- Destination
Cidr List<string>Blocks - List of strings containing CIDRs. You can define the IPv4 and IPv6 CIDR notation for each AWS Region. For example,
10.1.0.0/16
or2001:db8::/56
. This is an array of CIDR notation strings. - Destinations List<string>
- A list of strings. Valid values include
["blackhole"]
or a list of attachment ids. - Mode string
- String. When
action
isshare
, amode
value ofattachment-route
places the attachment and return routes in each of theshare_with
segments. Whenaction
issend-via
, indicates the mode used for packets. Valid values:attachment-route
,single-hop
,dual-hop
. - List<string>
- A set subtraction of segments to not share with.
- List<string>
- A list of strings to share with. Must be a substring is all segments. Valid values include:
["*"]
or["<segment-names>"]
. - Via
Get
Core Network Policy Document Segment Action Via - The network function groups and any edge overrides associated with the action.
- When
Sent GetTo Core Network Policy Document Segment Action When Sent To - The destination segments for the
send-via
orsend-to
action
.
- Action string
- Action to take for the chosen segment. Valid values:
create-route
,share
,send-via
andsend-to
. - Segment string
- Name of the segment.
- Description string
- A user-defined string describing the segment action.
- Destination
Cidr []stringBlocks - List of strings containing CIDRs. You can define the IPv4 and IPv6 CIDR notation for each AWS Region. For example,
10.1.0.0/16
or2001:db8::/56
. This is an array of CIDR notation strings. - Destinations []string
- A list of strings. Valid values include
["blackhole"]
or a list of attachment ids. - Mode string
- String. When
action
isshare
, amode
value ofattachment-route
places the attachment and return routes in each of theshare_with
segments. Whenaction
issend-via
, indicates the mode used for packets. Valid values:attachment-route
,single-hop
,dual-hop
. - []string
- A set subtraction of segments to not share with.
- []string
- A list of strings to share with. Must be a substring is all segments. Valid values include:
["*"]
or["<segment-names>"]
. - Via
Get
Core Network Policy Document Segment Action Via - The network function groups and any edge overrides associated with the action.
- When
Sent GetTo Core Network Policy Document Segment Action When Sent To - The destination segments for the
send-via
orsend-to
action
.
- action String
- Action to take for the chosen segment. Valid values:
create-route
,share
,send-via
andsend-to
. - segment String
- Name of the segment.
- description String
- A user-defined string describing the segment action.
- destination
Cidr List<String>Blocks - List of strings containing CIDRs. You can define the IPv4 and IPv6 CIDR notation for each AWS Region. For example,
10.1.0.0/16
or2001:db8::/56
. This is an array of CIDR notation strings. - destinations List<String>
- A list of strings. Valid values include
["blackhole"]
or a list of attachment ids. - mode String
- String. When
action
isshare
, amode
value ofattachment-route
places the attachment and return routes in each of theshare_with
segments. Whenaction
issend-via
, indicates the mode used for packets. Valid values:attachment-route
,single-hop
,dual-hop
. - List<String>
- A set subtraction of segments to not share with.
- List<String>
- A list of strings to share with. Must be a substring is all segments. Valid values include:
["*"]
or["<segment-names>"]
. - via
Get
Core Network Policy Document Segment Action Via - The network function groups and any edge overrides associated with the action.
- when
Sent GetTo Core Network Policy Document Segment Action When Sent To - The destination segments for the
send-via
orsend-to
action
.
- action string
- Action to take for the chosen segment. Valid values:
create-route
,share
,send-via
andsend-to
. - segment string
- Name of the segment.
- description string
- A user-defined string describing the segment action.
- destination
Cidr string[]Blocks - List of strings containing CIDRs. You can define the IPv4 and IPv6 CIDR notation for each AWS Region. For example,
10.1.0.0/16
or2001:db8::/56
. This is an array of CIDR notation strings. - destinations string[]
- A list of strings. Valid values include
["blackhole"]
or a list of attachment ids. - mode string
- String. When
action
isshare
, amode
value ofattachment-route
places the attachment and return routes in each of theshare_with
segments. Whenaction
issend-via
, indicates the mode used for packets. Valid values:attachment-route
,single-hop
,dual-hop
. - string[]
- A set subtraction of segments to not share with.
- string[]
- A list of strings to share with. Must be a substring is all segments. Valid values include:
["*"]
or["<segment-names>"]
. - via
Get
Core Network Policy Document Segment Action Via - The network function groups and any edge overrides associated with the action.
- when
Sent GetTo Core Network Policy Document Segment Action When Sent To - The destination segments for the
send-via
orsend-to
action
.
- action str
- Action to take for the chosen segment. Valid values:
create-route
,share
,send-via
andsend-to
. - segment str
- Name of the segment.
- description str
- A user-defined string describing the segment action.
- destination_
cidr_ Sequence[str]blocks - List of strings containing CIDRs. You can define the IPv4 and IPv6 CIDR notation for each AWS Region. For example,
10.1.0.0/16
or2001:db8::/56
. This is an array of CIDR notation strings. - destinations Sequence[str]
- A list of strings. Valid values include
["blackhole"]
or a list of attachment ids. - mode str
- String. When
action
isshare
, amode
value ofattachment-route
places the attachment and return routes in each of theshare_with
segments. Whenaction
issend-via
, indicates the mode used for packets. Valid values:attachment-route
,single-hop
,dual-hop
. - Sequence[str]
- A set subtraction of segments to not share with.
- Sequence[str]
- A list of strings to share with. Must be a substring is all segments. Valid values include:
["*"]
or["<segment-names>"]
. - via
Get
Core Network Policy Document Segment Action Via - The network function groups and any edge overrides associated with the action.
- when_
sent_ Getto Core Network Policy Document Segment Action When Sent To - The destination segments for the
send-via
orsend-to
action
.
- action String
- Action to take for the chosen segment. Valid values:
create-route
,share
,send-via
andsend-to
. - segment String
- Name of the segment.
- description String
- A user-defined string describing the segment action.
- destination
Cidr List<String>Blocks - List of strings containing CIDRs. You can define the IPv4 and IPv6 CIDR notation for each AWS Region. For example,
10.1.0.0/16
or2001:db8::/56
. This is an array of CIDR notation strings. - destinations List<String>
- A list of strings. Valid values include
["blackhole"]
or a list of attachment ids. - mode String
- String. When
action
isshare
, amode
value ofattachment-route
places the attachment and return routes in each of theshare_with
segments. Whenaction
issend-via
, indicates the mode used for packets. Valid values:attachment-route
,single-hop
,dual-hop
. - List<String>
- A set subtraction of segments to not share with.
- List<String>
- A list of strings to share with. Must be a substring is all segments. Valid values include:
["*"]
or["<segment-names>"]
. - via Property Map
- The network function groups and any edge overrides associated with the action.
- when
Sent Property MapTo - The destination segments for the
send-via
orsend-to
action
.
GetCoreNetworkPolicyDocumentSegmentActionVia
- Network
Function List<string>Groups - A list of strings. The network function group to use for the service insertion action.
- With
Edge List<GetOverrides Core Network Policy Document Segment Action Via With Edge Override> - Any edge overrides and the preferred edge to use.
- Network
Function []stringGroups - A list of strings. The network function group to use for the service insertion action.
- With
Edge []GetOverrides Core Network Policy Document Segment Action Via With Edge Override - Any edge overrides and the preferred edge to use.
- network
Function List<String>Groups - A list of strings. The network function group to use for the service insertion action.
- with
Edge List<GetOverrides Core Network Policy Document Segment Action Via With Edge Override> - Any edge overrides and the preferred edge to use.
- network
Function string[]Groups - A list of strings. The network function group to use for the service insertion action.
- with
Edge GetOverrides Core Network Policy Document Segment Action Via With Edge Override[] - Any edge overrides and the preferred edge to use.
- network_
function_ Sequence[str]groups - A list of strings. The network function group to use for the service insertion action.
- with_
edge_ Sequence[Getoverrides Core Network Policy Document Segment Action Via With Edge Override] - Any edge overrides and the preferred edge to use.
- network
Function List<String>Groups - A list of strings. The network function group to use for the service insertion action.
- with
Edge List<Property Map>Overrides - Any edge overrides and the preferred edge to use.
GetCoreNetworkPolicyDocumentSegmentActionViaWithEdgeOverride
GetCoreNetworkPolicyDocumentSegmentActionWhenSentTo
- Segments List<string>
- A list of strings. The list of segments that the
send-via
action
uses.
- Segments []string
- A list of strings. The list of segments that the
send-via
action
uses.
- segments List<String>
- A list of strings. The list of segments that the
send-via
action
uses.
- segments string[]
- A list of strings. The list of segments that the
send-via
action
uses.
- segments Sequence[str]
- A list of strings. The list of segments that the
send-via
action
uses.
- segments List<String>
- A list of strings. The list of segments that the
send-via
action
uses.
Package Details
- Repository
- AWS Classic pulumi/pulumi-aws
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
aws
Terraform Provider.
Try AWS Native preview for resources not in the classic version.