Returned by both the S3 and EC2 service codes. However, these IPĪddress ranges are used exclusively by service A, and can't be used by service B.įor example, Amazon S3 uses resources from Amazon EC2, so there are IP address ranges that are Returned by the service codes for both service A and service B. When service A uses resources from service B, there are IP address ranges that are Returned by the S3 service code are also returned by the For example, all IP address ranges that are The IP address ranges returned by any service code are also returned by theĪMAZON service code. ROUTE53 | ROUTE53_HEALTHCHECKS | ROUTE53_HEALTHCHECKS_PUBLISHING | ROUTE53_RESOLVER |Įxample: "service": "AMAZON" Range overlaps GLOBALACCELERATOR | KINESIS_VIDEO_STREAMS | MEDIA_PACKAGE_V2 | Valid values: AMAZON | AMAZON_APPFLOW | AMAZON_CONNECT | API_GATEWAY |ĬHIME_MEETINGS | CHIME_VOICECONNECTOR | CLOUD9 |ĬLOUDFRONT | CLOUDFRONT_ORIGIN_FACING | CODEBUILD |ĭYNAMODB | EBS | EC2 | EC2_INSTANCE_CONNECT | Subset (meaning that they are not also available in another subset). However, some IP address ranges are only in the AMAZON That every subset is also in the AMAZON subset). Specify AMAZON to get all IP address ranges (meaning The addresses listed for API_GATEWAY are egress only. Traffic for GLOBAL services can be attracted to or originate from multiple (up to all) AWS Regions.Īp-northeast-1 | ap-northeast-2 | ap-northeast-3 |Īp-southeast-1 | ap-southeast-2 | ap-southeast-3 | ap-southeast-4 |Įu-central-1 | eu-central-2 | eu-north-1 | Traffic for GLOBAL services can be attracted to or originate from multiple (up to all) Availability Zones or Local Zones from which AWS advertises IP addresses.Įxample: "network_border_group": "us-west-2-lax-1" region The name of the network border group, which is a unique set of Availability Zones or Local Zones from which AWS advertises IP addresses, or GLOBAL. Note that AWS mayĪdvertise a prefix in more specific ranges.Įxample: "ipv6_prefix": "2001:db8:1234::/64" network_border_group The public IPv6 address range, in CIDR notation. Note that AWS mayĪdvertise a prefix in more specific ranges. The public IPv4 address range, in CIDR notation. The IP prefixes for the IPv6 address ranges. The IP prefixes for the IPv4 address ranges. ![]() The publication date and time, in UTC YY-MM-DD-hh-mm-ss format.Įxample: "createDate": "-23-29-02" prefixes The publication time, in Unix epoch time format.Įxample: "syncToken": "1416435608" createDate The IP address ranges that you bring to AWS through bring your own IP addresses (BYOIP)Īlternatively, some services publish their address ranges using AWS-managed prefix lists.įor more information, see Available AWS-managed prefix lists. ![]() Publication time in the current file and compare it to the publication time in the last file Whether there have been changes since the last time that you saved the file, check the To view the current ranges, download the. Services may use the IP address ranges to communicate with other services (for example Route 53 health checks may use an EC2 IP address range to check the health of a web server instance) or services may use the IP ranges to communicate with a customer network. Only some AWS service IP address ranges are published in ip-ranges.json we publish the IP address ranges for services that customers commonly want to perform egress filtering on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |