diff options
author | CoprDistGit <infra@openeuler.org> | 2023-05-31 03:24:00 +0000 |
---|---|---|
committer | CoprDistGit <infra@openeuler.org> | 2023-05-31 03:24:00 +0000 |
commit | 8e4fd9ab68c64296274ac1b3ee63deac7ddac98d (patch) | |
tree | 60d3bf1e51033aa61a2aba3c30e0e424b32c7ae8 | |
parent | 0f4967c8ba07346378146c732d3e23df69355ea0 (diff) |
automatic import of python-aws-cdk-aws-route53resolver-alpha
-rw-r--r-- | .gitignore | 1 | ||||
-rw-r--r-- | python-aws-cdk-aws-route53resolver-alpha.spec | 296 | ||||
-rw-r--r-- | sources | 1 |
3 files changed, 298 insertions, 0 deletions
@@ -0,0 +1 @@ +/aws-cdk.aws-route53resolver-alpha-2.81.0a0.tar.gz diff --git a/python-aws-cdk-aws-route53resolver-alpha.spec b/python-aws-cdk-aws-route53resolver-alpha.spec new file mode 100644 index 0000000..2236da9 --- /dev/null +++ b/python-aws-cdk-aws-route53resolver-alpha.spec @@ -0,0 +1,296 @@ +%global _empty_manifest_terminate_build 0 +Name: python-aws-cdk.aws-route53resolver-alpha +Version: 2.81.0a0 +Release: 1 +Summary: The CDK Construct Library for AWS::Route53Resolver +License: Apache-2.0 +URL: https://github.com/aws/aws-cdk +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/04/ef/e2ff19f52a6c05b714cba10b0a13ba50c9e2997378b90c68d9716f248fcf/aws-cdk.aws-route53resolver-alpha-2.81.0a0.tar.gz +BuildArch: noarch + +Requires: python3-aws-cdk-lib +Requires: python3-constructs +Requires: python3-jsii +Requires: python3-publication +Requires: python3-typeguard + +%description +<!--END STABILITY BANNER--> +## 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: +```python +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](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-dns-firewall-managed-domain-lists.html): +```python +# 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: +```python +# 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()`: +```python +# 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: +```python +import aws_cdk.aws_ec2 as ec2 +# rule_group: route53resolver.FirewallRuleGroup +# my_vpc: ec2.Vpc +rule_group.associate("Association", + priority=101, + vpc=my_vpc +) +``` + +%package -n python3-aws-cdk.aws-route53resolver-alpha +Summary: The CDK Construct Library for AWS::Route53Resolver +Provides: python-aws-cdk.aws-route53resolver-alpha +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-aws-cdk.aws-route53resolver-alpha +<!--END STABILITY BANNER--> +## 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: +```python +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](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-dns-firewall-managed-domain-lists.html): +```python +# 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: +```python +# 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()`: +```python +# 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: +```python +import aws_cdk.aws_ec2 as ec2 +# rule_group: route53resolver.FirewallRuleGroup +# my_vpc: ec2.Vpc +rule_group.associate("Association", + priority=101, + vpc=my_vpc +) +``` + +%package help +Summary: Development documents and examples for aws-cdk.aws-route53resolver-alpha +Provides: python3-aws-cdk.aws-route53resolver-alpha-doc +%description help +<!--END STABILITY BANNER--> +## 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: +```python +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](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-dns-firewall-managed-domain-lists.html): +```python +# 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: +```python +# 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()`: +```python +# 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: +```python +import aws_cdk.aws_ec2 as ec2 +# rule_group: route53resolver.FirewallRuleGroup +# my_vpc: ec2.Vpc +rule_group.associate("Association", + priority=101, + vpc=my_vpc +) +``` + +%prep +%autosetup -n aws-cdk.aws-route53resolver-alpha-2.81.0a0 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-aws-cdk.aws-route53resolver-alpha -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Wed May 31 2023 Python_Bot <Python_Bot@openeuler.org> - 2.81.0a0-1 +- Package Spec generated @@ -0,0 +1 @@ +817a03218839302e492bc6de4f952577 aws-cdk.aws-route53resolver-alpha-2.81.0a0.tar.gz |