This release is a pre-release and may not be stable for production use.
Amazon Route53 Resolver Construct Library
---The APIs of higher level constructs in this module are experimental and under active development. They are subject to non-backward compatible changes or removal in any future version. These are not subject to the Semantic Versioning model and breaking changes will be announced in the release notes. This means that while you may use them, you may need to update your source code when upgrading to a newer version of this package.
DNS Firewall
With Route 53 Resolver DNS Firewall, you can filter and regulate outbound DNS traffic for your virtual private connections (VPCs). To do this, you create reusable collections of filtering rules in DNS Firewall rule groups and associate the rule groups to your VPC.
DNS Firewall provides protection for outbound DNS requests from your VPCs. These requests route through Resolver for domain name resolution. A primary use of DNS Firewall protections is to help prevent DNS exfiltration of your data. DNS exfiltration can happen when a bad actor compromises an application instance in your VPC and then uses DNS lookup to send data out of the VPC to a domain that they control. With DNS Firewall, you can monitor and control the domains that your applications can query. You can deny access to the domains that you know to be bad and allow all other queries to pass through. Alternately, you can deny access to all domains except for the ones that you explicitly trust.
Domain lists
Domain lists can be created using a list of strings, a text file stored in Amazon S3 or a local text file:
block_list = route53resolver.FirewallDomainList(self, "BlockList",
domains=route53resolver.FirewallDomains.from_list(["bad-domain.com", "bot-domain.net"])
)
s3_list = route53resolver.FirewallDomainList(self, "S3List",
domains=route53resolver.FirewallDomains.from_s3_url("s3://bucket/prefix/object")
)
asset_list = route53resolver.FirewallDomainList(self, "AssetList",
domains=route53resolver.FirewallDomains.from_asset("/path/to/domains.txt")
)
The file must be a text file and must contain a single domain per line.
Use FirewallDomainList.fromFirewallDomainListId() to import an existing or AWS managed domain list:
# AWSManagedDomainsMalwareDomainList in us-east-1
malware_list = route53resolver.FirewallDomainList.from_firewall_domain_list_id(self, "Malware", "rslvr-fdl-2c46f2ecbfec4dcc")
Rule group
Create a rule group:
# my_block_list: route53resolver.FirewallDomainList
route53resolver.FirewallRuleGroup(self, "RuleGroup",
rules=[route53resolver.FirewallRule(
priority=10,
firewall_domain_list=my_block_list,
# block and reply with NODATA
action=route53resolver.FirewallRuleAction.block()
)
]
)
Rules can be added at construction time or using addRule():
# my_block_list: route53resolver.FirewallDomainList
# rule_group: route53resolver.FirewallRuleGroup
rule_group.add_rule(
priority=10,
firewall_domain_list=my_block_list,
# block and reply with NXDOMAIN
action=route53resolver.FirewallRuleAction.block(route53resolver.DnsBlockResponse.nx_domain())
)
rule_group.add_rule(
priority=20,
firewall_domain_list=my_block_list,
# block and override DNS response with a custom domain
action=route53resolver.FirewallRuleAction.block(route53resolver.DnsBlockResponse.override("amazon.com"))
)
Use associate() to associate a rule group with a VPC:
import aws_cdk.aws_ec2 as ec2
# rule_group: route53resolver.FirewallRuleGroup
# my_vpc: ec2.Vpc
rule_group.associate("Association",
priority=101,
vpc=my_vpc
)
Metadata
Release files for aws-cdk.aws-route53resolver-alpha 2.274.0a0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aws_cdk_aws_route53resolver_alpha-2.274.0a0.tar.gz | 79.1 kB | Without provenance | Details for aws_cdk_aws_route53resolver_alpha-2.274.0a0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_cdk_aws_route53resolver_alpha-2.274.0a0-py3-none-any.whl | Python 3 | none | any | Details for aws_cdk_aws_route53resolver_alpha-2.274.0a0-py3-none-any.whl |
Total release size: 156.7 kB
Release files / aws_cdk_aws_route53resolver_alpha-2.274.0a0.tar.gz
| Download URL | aws_cdk_aws_route53resolver_alpha-2.274.0a0.tar.gz |
|---|---|
| Size | 79.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9208b950140cda81f64a93cf604bd45c5b415b582c6aab8539c55e93b22a76b2
|
|
BLAKE2b-256 checksum How to use checksums |
ad8701418dec0944e6095cf7d17785bcbe5a29d3f8de75c7988fd6609382c30e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / aws_cdk_aws_route53resolver_alpha-2.274.0a0-py3-none-any.whl
| Download URL | aws_cdk_aws_route53resolver_alpha-2.274.0a0-py3-none-any.whl |
|---|---|
| Size | 77.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
35c0606a5c306ba82dfcb4cf104ce2a9cb370fa9db88d488307c965a5ef225e3
|
|
BLAKE2b-256 checksum How to use checksums |
e65c708372e455daef3d5c210f6d09304b071020bfe60cb78814a9b96a2cdcf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Security for aws-cdk.aws-route53resolver-alpha 2.274.0a0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.