@awboost/cfn-resource-types 0.1.34 → 0.1.35
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/lib/AWS-Config-ConfigRule.d.ts +12 -2
- package/lib/AWS-Config-ConfigRule.js +6 -1
- package/lib/AWS-EC2-NetworkAcl.d.ts +13 -4
- package/lib/AWS-EC2-NetworkAcl.js +2 -1
- package/lib/AWS-IoTSiteWise-AssetModel.d.ts +4 -4
- package/lib/AWS-Route53-HostedZone.d.ts +71 -27
- package/lib/AWS-Route53-HostedZone.js +17 -1
- package/package.json +1 -1
|
@@ -5,7 +5,12 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
|
|
|
5
5
|
* You must first create and start the CC configuration recorder in order to create CC managed rules with CFNlong. For more information, see [Managing the Configuration Recorder](https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html).
|
|
6
6
|
Adds or updates an CC rule to evaluate if your AWS resources comply with your desired configurations. For information on how many CC rules you can have per account, see [Service Limits](https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html) in the *Developer Guide*.
|
|
7
7
|
There are two types of rules: *Managed Rules* and *Custom Rules*. You can use the ``ConfigRule`` resource to create both CC Managed Rules and CC Custom Rules.
|
|
8
|
-
CC Managed Rules are predefined, customizable rules created by CC. For a list of managed rules, see [List of Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html). If you are adding an CC managed rule, you must specify the rule's
|
|
8
|
+
CC Managed Rules are predefined, customizable rules created by CC. For a list of managed rules, see [List of Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html). If you are adding an CC managed rule, you must specify the rule's identifier for the ``SourceIdentifier`` key.
|
|
9
|
+
CC Custom Rules are rules that you create from scratch. There are two ways to create CC custom rules: with Lambda functions ([Developer Guide](https://docs.aws.amazon.com/config/latest/developerguide/gettingstarted-concepts.html#gettingstarted-concepts-function)) and with CFNGUARDshort ([Guard GitHub Repository](https://docs.aws.amazon.com/https://github.com/aws-cloudformation/cloudformation-guard)), a policy-as-code language. CC custom rules created with LAMlong are called *Custom Lambda Rules* and CC custom rules created with CFNGUARDshort are called *Custom Policy Rules*.
|
|
10
|
+
If you are adding a new CC Custom LAM rule, you first need to create an LAMlong function that the rule invokes to evaluate your resources. When you use the ``ConfigRule`` resource to add a Custom LAM rule to CC, you must specify the Amazon Resource Name (ARN) that LAMlong assigns to the function. You specify the ARN in the ``SourceIdentifier`` key. This key is part of the ``Source`` object, which is part of the ``ConfigRule`` object.
|
|
11
|
+
For any new CC rule that you add, specify the ``ConfigRuleName`` in the ``ConfigRule`` object. Do not specify the ``ConfigRuleArn`` or the ``ConfigRuleId``. These values are generated by CC for new rules.
|
|
12
|
+
If you are updating a rule that you added previously, you can specify the rule by ``ConfigRuleName``, ``ConfigRuleId``, or ``ConfigRuleArn`` in the ``ConfigRule`` data type that you use in this request.
|
|
13
|
+
For more information about developing and using CC rules, see [Evaluating Resources with Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *Developer Guide*.
|
|
9
14
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-config-configrule.html}
|
|
10
15
|
*/
|
|
11
16
|
export type ConfigConfigRuleProperties = {
|
|
@@ -173,7 +178,12 @@ export type SourceDetail = {
|
|
|
173
178
|
* You must first create and start the CC configuration recorder in order to create CC managed rules with CFNlong. For more information, see [Managing the Configuration Recorder](https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html).
|
|
174
179
|
Adds or updates an CC rule to evaluate if your AWS resources comply with your desired configurations. For information on how many CC rules you can have per account, see [Service Limits](https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html) in the *Developer Guide*.
|
|
175
180
|
There are two types of rules: *Managed Rules* and *Custom Rules*. You can use the ``ConfigRule`` resource to create both CC Managed Rules and CC Custom Rules.
|
|
176
|
-
CC Managed Rules are predefined, customizable rules created by CC. For a list of managed rules, see [List of Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html). If you are adding an CC managed rule, you must specify the rule's
|
|
181
|
+
CC Managed Rules are predefined, customizable rules created by CC. For a list of managed rules, see [List of Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html). If you are adding an CC managed rule, you must specify the rule's identifier for the ``SourceIdentifier`` key.
|
|
182
|
+
CC Custom Rules are rules that you create from scratch. There are two ways to create CC custom rules: with Lambda functions ([Developer Guide](https://docs.aws.amazon.com/config/latest/developerguide/gettingstarted-concepts.html#gettingstarted-concepts-function)) and with CFNGUARDshort ([Guard GitHub Repository](https://docs.aws.amazon.com/https://github.com/aws-cloudformation/cloudformation-guard)), a policy-as-code language. CC custom rules created with LAMlong are called *Custom Lambda Rules* and CC custom rules created with CFNGUARDshort are called *Custom Policy Rules*.
|
|
183
|
+
If you are adding a new CC Custom LAM rule, you first need to create an LAMlong function that the rule invokes to evaluate your resources. When you use the ``ConfigRule`` resource to add a Custom LAM rule to CC, you must specify the Amazon Resource Name (ARN) that LAMlong assigns to the function. You specify the ARN in the ``SourceIdentifier`` key. This key is part of the ``Source`` object, which is part of the ``ConfigRule`` object.
|
|
184
|
+
For any new CC rule that you add, specify the ``ConfigRuleName`` in the ``ConfigRule`` object. Do not specify the ``ConfigRuleArn`` or the ``ConfigRuleId``. These values are generated by CC for new rules.
|
|
185
|
+
If you are updating a rule that you added previously, you can specify the rule by ``ConfigRuleName``, ``ConfigRuleId``, or ``ConfigRuleArn`` in the ``ConfigRule`` data type that you use in this request.
|
|
186
|
+
For more information about developing and using CC rules, see [Evaluating Resources with Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *Developer Guide*.
|
|
177
187
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-config-configrule.html}
|
|
178
188
|
*/
|
|
179
189
|
export declare class ConfigConfigRule extends $Resource<"AWS::Config::ConfigRule", ConfigConfigRuleProperties, ConfigConfigRuleAttributes> {
|
|
@@ -4,7 +4,12 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
|
|
|
4
4
|
* You must first create and start the CC configuration recorder in order to create CC managed rules with CFNlong. For more information, see [Managing the Configuration Recorder](https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html).
|
|
5
5
|
Adds or updates an CC rule to evaluate if your AWS resources comply with your desired configurations. For information on how many CC rules you can have per account, see [Service Limits](https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html) in the *Developer Guide*.
|
|
6
6
|
There are two types of rules: *Managed Rules* and *Custom Rules*. You can use the ``ConfigRule`` resource to create both CC Managed Rules and CC Custom Rules.
|
|
7
|
-
CC Managed Rules are predefined, customizable rules created by CC. For a list of managed rules, see [List of Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html). If you are adding an CC managed rule, you must specify the rule's
|
|
7
|
+
CC Managed Rules are predefined, customizable rules created by CC. For a list of managed rules, see [List of Managed Rules](https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html). If you are adding an CC managed rule, you must specify the rule's identifier for the ``SourceIdentifier`` key.
|
|
8
|
+
CC Custom Rules are rules that you create from scratch. There are two ways to create CC custom rules: with Lambda functions ([Developer Guide](https://docs.aws.amazon.com/config/latest/developerguide/gettingstarted-concepts.html#gettingstarted-concepts-function)) and with CFNGUARDshort ([Guard GitHub Repository](https://docs.aws.amazon.com/https://github.com/aws-cloudformation/cloudformation-guard)), a policy-as-code language. CC custom rules created with LAMlong are called *Custom Lambda Rules* and CC custom rules created with CFNGUARDshort are called *Custom Policy Rules*.
|
|
9
|
+
If you are adding a new CC Custom LAM rule, you first need to create an LAMlong function that the rule invokes to evaluate your resources. When you use the ``ConfigRule`` resource to add a Custom LAM rule to CC, you must specify the Amazon Resource Name (ARN) that LAMlong assigns to the function. You specify the ARN in the ``SourceIdentifier`` key. This key is part of the ``Source`` object, which is part of the ``ConfigRule`` object.
|
|
10
|
+
For any new CC rule that you add, specify the ``ConfigRuleName`` in the ``ConfigRule`` object. Do not specify the ``ConfigRuleArn`` or the ``ConfigRuleId``. These values are generated by CC for new rules.
|
|
11
|
+
If you are updating a rule that you added previously, you can specify the rule by ``ConfigRuleName``, ``ConfigRuleId``, or ``ConfigRuleArn`` in the ``ConfigRule`` data type that you use in this request.
|
|
12
|
+
For more information about developing and using CC rules, see [Evaluating Resources with Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *Developer Guide*.
|
|
8
13
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-config-configrule.html}
|
|
9
14
|
*/
|
|
10
15
|
export class ConfigConfigRule extends $Resource {
|
|
@@ -1,16 +1,17 @@
|
|
|
1
1
|
import { Resource as $Resource } from "@awboost/cfn-template-builder/template/resource";
|
|
2
2
|
import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-builder/template";
|
|
3
3
|
/**
|
|
4
|
-
* Resource
|
|
4
|
+
* Resource type definition for `AWS::EC2::NetworkAcl`.
|
|
5
|
+
* Specifies a network ACL for your VPC.
|
|
5
6
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-networkacl.html}
|
|
6
7
|
*/
|
|
7
8
|
export type EC2NetworkAclProperties = {
|
|
8
9
|
/**
|
|
9
|
-
* The tags
|
|
10
|
+
* The tags for the network ACL.
|
|
10
11
|
*/
|
|
11
12
|
Tags?: Tag[];
|
|
12
13
|
/**
|
|
13
|
-
* The ID of the VPC.
|
|
14
|
+
* The ID of the VPC for the network ACL.
|
|
14
15
|
*/
|
|
15
16
|
VpcId: string;
|
|
16
17
|
};
|
|
@@ -23,14 +24,22 @@ export type EC2NetworkAclAttributes = {
|
|
|
23
24
|
};
|
|
24
25
|
/**
|
|
25
26
|
* Type definition for `AWS::EC2::NetworkAcl.Tag`.
|
|
27
|
+
* Specifies a tag. For more information, see [Add tags to a resource](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html#cloudformation-add-tag-specifications).
|
|
26
28
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-networkacl-tag.html}
|
|
27
29
|
*/
|
|
28
30
|
export type Tag = {
|
|
31
|
+
/**
|
|
32
|
+
* The tag key.
|
|
33
|
+
*/
|
|
29
34
|
Key: string;
|
|
35
|
+
/**
|
|
36
|
+
* The tag value.
|
|
37
|
+
*/
|
|
30
38
|
Value: string;
|
|
31
39
|
};
|
|
32
40
|
/**
|
|
33
|
-
* Resource
|
|
41
|
+
* Resource type definition for `AWS::EC2::NetworkAcl`.
|
|
42
|
+
* Specifies a network ACL for your VPC.
|
|
34
43
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-networkacl.html}
|
|
35
44
|
*/
|
|
36
45
|
export declare class EC2NetworkAcl extends $Resource<"AWS::EC2::NetworkAcl", EC2NetworkAclProperties, EC2NetworkAclAttributes> {
|
|
@@ -1,6 +1,7 @@
|
|
|
1
1
|
import { Resource as $Resource } from "@awboost/cfn-template-builder/template/resource";
|
|
2
2
|
/**
|
|
3
|
-
* Resource
|
|
3
|
+
* Resource type definition for `AWS::EC2::NetworkAcl`.
|
|
4
|
+
* Specifies a network ACL for your VPC.
|
|
4
5
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-networkacl.html}
|
|
5
6
|
*/
|
|
6
7
|
export class EC2NetworkAcl extends $Resource {
|
|
@@ -116,10 +116,6 @@ export type IoTSiteWiseAssetModelAttributes = {
|
|
|
116
116
|
* @pattern `^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$`
|
|
117
117
|
*/
|
|
118
118
|
Id: string;
|
|
119
|
-
/**
|
|
120
|
-
* The path of the composite model. This is only for derived composite models
|
|
121
|
-
*/
|
|
122
|
-
Path: string[];
|
|
123
119
|
}[];
|
|
124
120
|
/**
|
|
125
121
|
* The hierarchy definitions of the asset model. Each hierarchy specifies an asset model whose assets can be children of any other assets created from this asset model. You can specify up to 10 hierarchies per asset model.
|
|
@@ -232,6 +228,10 @@ export type AssetModelCompositeModel = {
|
|
|
232
228
|
* @pattern `[a-zA-Z0-9_][a-zA-Z_\-0-9.:]*[a-zA-Z0-9_]+`
|
|
233
229
|
*/
|
|
234
230
|
ParentAssetModelCompositeModelExternalId?: string;
|
|
231
|
+
/**
|
|
232
|
+
* The path of the composite model. This is only for derived composite models
|
|
233
|
+
*/
|
|
234
|
+
Path?: string[];
|
|
235
235
|
/**
|
|
236
236
|
* The type of the composite model. For alarm composite models, this type is AWS/ALARM
|
|
237
237
|
*/
|
|
@@ -1,36 +1,57 @@
|
|
|
1
1
|
import { Resource as $Resource } from "@awboost/cfn-template-builder/template/resource";
|
|
2
2
|
import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-builder/template";
|
|
3
3
|
/**
|
|
4
|
-
* Resource
|
|
4
|
+
* Resource type definition for `AWS::Route53::HostedZone`.
|
|
5
|
+
* Creates a new public or private hosted zone. You create records in a public hosted zone to define how you want to route traffic on the internet for a domain, such as example.com, and its subdomains (apex.example.com, acme.example.com). You create records in a private hosted zone to define how you want to route traffic for a domain and its subdomains within one or more Amazon Virtual Private Clouds (Amazon VPCs).
|
|
6
|
+
You can't convert a public hosted zone to a private hosted zone or vice versa. Instead, you must create a new hosted zone with the same name and create new resource record sets.
|
|
7
|
+
For more information about charges for hosted zones, see [Amazon Route 53 Pricing](https://docs.aws.amazon.com/route53/pricing/).
|
|
8
|
+
Note the following:
|
|
9
|
+
+ You can't create a hosted zone for a top-level domain (TLD) such as .com.
|
|
10
|
+
+ If your domain is registered with a registrar other than Route 53, you must update the name servers with your registrar to make Route 53 the DNS service for the domain. For more information, see [Migrating DNS Service for an Existing Domain to Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/MigratingDNS.html) in the *Amazon Route 53 Developer Guide*.
|
|
11
|
+
|
|
12
|
+
When you submit a ``CreateHostedZone`` request, the initial status of the hosted zone is ``PENDING``. For public hosted zones, this means that the NS and SOA records are not yet available on all Route 53 DNS servers. When the NS and SOA records are available, the status of the zone changes to ``INSYNC``.
|
|
13
|
+
The ``CreateHostedZone`` request requires the caller to have an ``ec2:DescribeVpcs`` permission.
|
|
14
|
+
When creating private hosted zones, the Amazon VPC must belong to the same partition where the hosted zone is created. A partition is a group of AWS-Regions. Each AWS-account is scoped to one partition.
|
|
15
|
+
The following are the supported partitions:
|
|
16
|
+
+ ``aws`` - AWS-Regions
|
|
17
|
+
+ ``aws-cn`` - China Regions
|
|
18
|
+
+ ``aws-us-gov`` - govcloud-us-region
|
|
19
|
+
|
|
20
|
+
For more information, see [Access Management](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html) in the *General Reference*.
|
|
5
21
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-route53-hostedzone.html}
|
|
6
22
|
*/
|
|
7
23
|
export type Route53HostedZoneProperties = {
|
|
8
24
|
/**
|
|
9
25
|
* A complex type that contains an optional comment.
|
|
10
|
-
|
|
11
|
-
If you don't want to specify a comment, omit the HostedZoneConfig and Comment elements.
|
|
26
|
+
If you don't want to specify a comment, omit the ``HostedZoneConfig`` and ``Comment`` elements.
|
|
12
27
|
*/
|
|
13
28
|
HostedZoneConfig?: HostedZoneConfig;
|
|
14
29
|
/**
|
|
15
30
|
* Adds, edits, or deletes tags for a health check or a hosted zone.
|
|
16
|
-
|
|
17
|
-
For information about using tags for cost allocation, see Using Cost Allocation Tags in the AWS Billing and Cost Management User Guide.
|
|
31
|
+
For information about using tags for cost allocation, see [Using Cost Allocation Tags](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html) in the *User Guide*.
|
|
18
32
|
*/
|
|
19
33
|
HostedZoneTags?: HostedZoneTag[];
|
|
20
34
|
/**
|
|
21
|
-
* The name of the domain. Specify a fully qualified domain name, for example, www.example.com
|
|
22
|
-
|
|
23
|
-
If you're creating a public hosted zone, this is the name you have registered with your DNS registrar. If your domain name is registered with a registrar other than Route 53, change the name servers for your domain to the set of NameServers that are returned by the Fn::GetAtt intrinsic function.
|
|
35
|
+
* The name of the domain. Specify a fully qualified domain name, for example, *www.example.com*. The trailing dot is optional; Amazon Route 53 assumes that the domain name is fully qualified. This means that Route 53 treats *www.example.com* (without a trailing dot) and *www.example.com.* (with a trailing dot) as identical.
|
|
36
|
+
If you're creating a public hosted zone, this is the name you have registered with your DNS registrar. If your domain name is registered with a registrar other than Route 53, change the name servers for your domain to the set of ``NameServers`` that are returned by the ``Fn::GetAtt`` intrinsic function.
|
|
24
37
|
* @maxLength `1024`
|
|
25
38
|
*/
|
|
26
39
|
Name?: string;
|
|
27
40
|
/**
|
|
28
|
-
|
|
29
|
-
|
|
41
|
+
* Creates a configuration for DNS query logging. After you create a query logging configuration, Amazon Route 53 begins to publish log data to an Amazon CloudWatch Logs log group.
|
|
42
|
+
DNS query logs contain information about the queries that Route 53 receives for a specified public hosted zone, such as the following:
|
|
43
|
+
+ Route 53 edge location that responded to the DNS query
|
|
44
|
+
+ Domain or subdomain that was requested
|
|
45
|
+
+ DNS record type, such as A or AAAA
|
|
46
|
+
+ DNS response code, such as ``NoError`` or ``ServFail``
|
|
47
|
+
|
|
48
|
+
+ Log Group and Resource Policy Before you create a query logging configuration, perform the following operations. If you create a query logging configuration using the Route 53 console, Route 53 performs these operations automatically. Create a CloudWatch Logs log group, and make note of the ARN, which you specify when you create a query logging configuration. Note the following: You must create the log group in the us-east-1 region. You must use the same to create the log group and the hosted zone that you want to configure query logging for. When you create log groups for query logging, we recommend that you use a consistent prefix, for example: /aws/route53/hosted zone name In the next step, you'll create a resource policy, which controls access to one or more log groups and the associated resources, such as Route 53 hosted zones. There's a limit on the number of resource policies that you can create, so we recommend that you use a consistent prefix so you can use the same resource policy for all the log groups that you create for query logging. Create a CloudWatch Logs resource policy, and give it the permissions that Route 53 needs to create log streams and to send query logs to log streams. For the value of Resource, specify the ARN for the log group that you created in the previous step. To use the same resource policy for all the CloudWatch Logs log groups that you created for query logging configurations, replace the hosted zone name with *, for example: arn:aws:logs:us-east-1:123412341234:log-group:/aws/route53/* To avoid the confused deputy problem, a security issue where an entity without a permission for an action can coerce a more-privileged entity to perform it, you can optionally limit the permissions that a service has to a resource in a resource-based policy by supplying the following values: For aws:SourceArn, supply the hosted zone ARN used in creating the query logging configuration. For example, aws:SourceArn: arn:aws:route53:::hostedzone/hosted zone ID. For aws:SourceAccount, supply the account ID for the account that creates the query logging configuration. For example, aws:SourceAccount:111111111111. For more information, see The confused deputy problem in the IAM User Guide. You can't use the CloudWatch console to create or edit a resource policy. You must use the CloudWatch API, one of the SDKs, or the . + Log Streams and Edge Locations When Route 53 finishes creating the configuration for DNS query logging, it does the following: Creates a log stream for an edge location the first time that the edge location responds to DNS queries for the specified hosted zone. That log stream is used to log all queries that Route 53 responds to for that edge location. Begins to send query logs to the applicable log stream. The name of each log stream is in the following format: hosted zone ID/edge location code The edge location code is a three-letter code and an arbitrarily assigned number, for example, DFW3. The three-letter code typically corresponds with the International Air Transport Association airport code for an airport near the edge location. (These abbreviations might change in the future.) For a list of edge locations, see "The Route 53 Global Network" on the Route 53 Product Details page. + Queries That Are Logged Query logs contain only the queries that DNS resolvers forward to Route 53. If a DNS resolver has already cached the response to a query (such as the IP address for a load balancer for example.com), the resolver will continue to return the cached response. It doesn't forward another query to Route 53 until the TTL for the corresponding resource record set expires. Depending on how many DNS queries are submitted for a resource record set, and depending on the TTL for that resource record set, query logs might contain information about only one query out of every several thousand queries that are submitted to DNS. For more information about how DNS works, see Routing Internet Traffic to Your Website or Web Application in the Amazon Route 53 Developer Guide. + Log File Format For a list of the values in each query log and the format of each value, see Logging DNS Queries in the Amazon Route 53 Developer Guide. + Pricing For information about charges for query logs, see Amazon CloudWatch Pricing. + How to Stop Logging If you want Route 53 to stop sending query logs to CloudWatch Logs, delete the query logging configuration. For more information, see DeleteQueryLoggingConfig.
|
|
49
|
+
*/
|
|
30
50
|
QueryLoggingConfig?: QueryLoggingConfig;
|
|
31
51
|
/**
|
|
32
|
-
|
|
33
|
-
|
|
52
|
+
* *Private hosted zones:* A complex type that contains information about the VPCs that are associated with the specified hosted zone.
|
|
53
|
+
For public hosted zones, omit ``VPCs``, ``VPCId``, and ``VPCRegion``.
|
|
54
|
+
*/
|
|
34
55
|
VPCs?: VPC[];
|
|
35
56
|
};
|
|
36
57
|
/**
|
|
@@ -43,9 +64,7 @@ export type Route53HostedZoneAttributes = {
|
|
|
43
64
|
};
|
|
44
65
|
/**
|
|
45
66
|
* Type definition for `AWS::Route53::HostedZone.HostedZoneConfig`.
|
|
46
|
-
* A complex type that contains an optional comment.
|
|
47
|
-
|
|
48
|
-
If you don't want to specify a comment, omit the HostedZoneConfig and Comment elements.
|
|
67
|
+
* A complex type that contains an optional comment about your hosted zone. If you don't want to specify a comment, omit both the ``HostedZoneConfig`` and ``Comment`` elements.
|
|
49
68
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-route53-hostedzone-hostedzoneconfig.html}
|
|
50
69
|
*/
|
|
51
70
|
export type HostedZoneConfig = {
|
|
@@ -62,14 +81,20 @@ export type HostedZoneConfig = {
|
|
|
62
81
|
*/
|
|
63
82
|
export type HostedZoneTag = {
|
|
64
83
|
/**
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
84
|
+
* The value of ``Key`` depends on the operation that you want to perform:
|
|
85
|
+
+ *Add a tag to a health check or hosted zone*: ``Key`` is the name that you want to give the new tag.
|
|
86
|
+
+ *Edit a tag*: ``Key`` is the name of the tag that you want to change the ``Value`` for.
|
|
87
|
+
+ *Delete a key*: ``Key`` is the name of the tag you want to remove.
|
|
88
|
+
+ *Give a name to a health check*: Edit the default ``Name`` tag. In the Amazon Route 53 console, the list of your health checks includes a *Name* column that lets you see the name that you've given to each health check.
|
|
89
|
+
* @maxLength `128`
|
|
90
|
+
*/
|
|
68
91
|
Key: string;
|
|
69
92
|
/**
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
93
|
+
* The value of ``Value`` depends on the operation that you want to perform:
|
|
94
|
+
+ *Add a tag to a health check or hosted zone*: ``Value`` is the value that you want to give the new tag.
|
|
95
|
+
+ *Edit a tag*: ``Value`` is the new value that you want to assign the tag.
|
|
96
|
+
* @maxLength `256`
|
|
97
|
+
*/
|
|
73
98
|
Value: string;
|
|
74
99
|
};
|
|
75
100
|
/**
|
|
@@ -85,21 +110,40 @@ export type QueryLoggingConfig = {
|
|
|
85
110
|
};
|
|
86
111
|
/**
|
|
87
112
|
* Type definition for `AWS::Route53::HostedZone.VPC`.
|
|
88
|
-
* A complex type that contains information about an Amazon VPC. Route 53 Resolver uses the records in the private hosted zone to route traffic in that VPC.
|
|
113
|
+
* *Private hosted zones only:* A complex type that contains information about an Amazon VPC. Route 53 Resolver uses the records in the private hosted zone to route traffic in that VPC.
|
|
114
|
+
For public hosted zones, omit ``VPCs``, ``VPCId``, and ``VPCRegion``.
|
|
89
115
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-route53-hostedzone-vpc.html}
|
|
90
116
|
*/
|
|
91
117
|
export type VPC = {
|
|
92
118
|
/**
|
|
93
|
-
|
|
94
|
-
|
|
119
|
+
* *Private hosted zones only:* The ID of an Amazon VPC.
|
|
120
|
+
For public hosted zones, omit ``VPCs``, ``VPCId``, and ``VPCRegion``.
|
|
121
|
+
*/
|
|
95
122
|
VPCId: string;
|
|
96
123
|
/**
|
|
97
|
-
|
|
98
|
-
|
|
124
|
+
* *Private hosted zones only:* The region that an Amazon VPC was created in.
|
|
125
|
+
For public hosted zones, omit ``VPCs``, ``VPCId``, and ``VPCRegion``.
|
|
126
|
+
*/
|
|
99
127
|
VPCRegion: string;
|
|
100
128
|
};
|
|
101
129
|
/**
|
|
102
|
-
* Resource
|
|
130
|
+
* Resource type definition for `AWS::Route53::HostedZone`.
|
|
131
|
+
* Creates a new public or private hosted zone. You create records in a public hosted zone to define how you want to route traffic on the internet for a domain, such as example.com, and its subdomains (apex.example.com, acme.example.com). You create records in a private hosted zone to define how you want to route traffic for a domain and its subdomains within one or more Amazon Virtual Private Clouds (Amazon VPCs).
|
|
132
|
+
You can't convert a public hosted zone to a private hosted zone or vice versa. Instead, you must create a new hosted zone with the same name and create new resource record sets.
|
|
133
|
+
For more information about charges for hosted zones, see [Amazon Route 53 Pricing](https://docs.aws.amazon.com/route53/pricing/).
|
|
134
|
+
Note the following:
|
|
135
|
+
+ You can't create a hosted zone for a top-level domain (TLD) such as .com.
|
|
136
|
+
+ If your domain is registered with a registrar other than Route 53, you must update the name servers with your registrar to make Route 53 the DNS service for the domain. For more information, see [Migrating DNS Service for an Existing Domain to Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/MigratingDNS.html) in the *Amazon Route 53 Developer Guide*.
|
|
137
|
+
|
|
138
|
+
When you submit a ``CreateHostedZone`` request, the initial status of the hosted zone is ``PENDING``. For public hosted zones, this means that the NS and SOA records are not yet available on all Route 53 DNS servers. When the NS and SOA records are available, the status of the zone changes to ``INSYNC``.
|
|
139
|
+
The ``CreateHostedZone`` request requires the caller to have an ``ec2:DescribeVpcs`` permission.
|
|
140
|
+
When creating private hosted zones, the Amazon VPC must belong to the same partition where the hosted zone is created. A partition is a group of AWS-Regions. Each AWS-account is scoped to one partition.
|
|
141
|
+
The following are the supported partitions:
|
|
142
|
+
+ ``aws`` - AWS-Regions
|
|
143
|
+
+ ``aws-cn`` - China Regions
|
|
144
|
+
+ ``aws-us-gov`` - govcloud-us-region
|
|
145
|
+
|
|
146
|
+
For more information, see [Access Management](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html) in the *General Reference*.
|
|
103
147
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-route53-hostedzone.html}
|
|
104
148
|
*/
|
|
105
149
|
export declare class Route53HostedZone extends $Resource<"AWS::Route53::HostedZone", Route53HostedZoneProperties, Route53HostedZoneAttributes> {
|
|
@@ -1,6 +1,22 @@
|
|
|
1
1
|
import { Resource as $Resource } from "@awboost/cfn-template-builder/template/resource";
|
|
2
2
|
/**
|
|
3
|
-
* Resource
|
|
3
|
+
* Resource type definition for `AWS::Route53::HostedZone`.
|
|
4
|
+
* Creates a new public or private hosted zone. You create records in a public hosted zone to define how you want to route traffic on the internet for a domain, such as example.com, and its subdomains (apex.example.com, acme.example.com). You create records in a private hosted zone to define how you want to route traffic for a domain and its subdomains within one or more Amazon Virtual Private Clouds (Amazon VPCs).
|
|
5
|
+
You can't convert a public hosted zone to a private hosted zone or vice versa. Instead, you must create a new hosted zone with the same name and create new resource record sets.
|
|
6
|
+
For more information about charges for hosted zones, see [Amazon Route 53 Pricing](https://docs.aws.amazon.com/route53/pricing/).
|
|
7
|
+
Note the following:
|
|
8
|
+
+ You can't create a hosted zone for a top-level domain (TLD) such as .com.
|
|
9
|
+
+ If your domain is registered with a registrar other than Route 53, you must update the name servers with your registrar to make Route 53 the DNS service for the domain. For more information, see [Migrating DNS Service for an Existing Domain to Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/MigratingDNS.html) in the *Amazon Route 53 Developer Guide*.
|
|
10
|
+
|
|
11
|
+
When you submit a ``CreateHostedZone`` request, the initial status of the hosted zone is ``PENDING``. For public hosted zones, this means that the NS and SOA records are not yet available on all Route 53 DNS servers. When the NS and SOA records are available, the status of the zone changes to ``INSYNC``.
|
|
12
|
+
The ``CreateHostedZone`` request requires the caller to have an ``ec2:DescribeVpcs`` permission.
|
|
13
|
+
When creating private hosted zones, the Amazon VPC must belong to the same partition where the hosted zone is created. A partition is a group of AWS-Regions. Each AWS-account is scoped to one partition.
|
|
14
|
+
The following are the supported partitions:
|
|
15
|
+
+ ``aws`` - AWS-Regions
|
|
16
|
+
+ ``aws-cn`` - China Regions
|
|
17
|
+
+ ``aws-us-gov`` - govcloud-us-region
|
|
18
|
+
|
|
19
|
+
For more information, see [Access Management](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html) in the *General Reference*.
|
|
4
20
|
* @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-route53-hostedzone.html}
|
|
5
21
|
*/
|
|
6
22
|
export class Route53HostedZone extends $Resource {
|