Abstract: In response to receiving a reservation request at a provider network, metadata indicating that a group of network addresses of a subnet is reserved for operations of a particular category is stored. A first request for an operation, requiring assignment of an address of the reserved group is rejected if the operation does not belong to the particular category, even if the address is not in use. In response to a second request for an operation which does belong to the particular category, an address of the reserved group is assigned.

Abstract: Disclosed are various embodiments for self-service management of network address allocations using hierarchical allocation pools. A first network address pool is created for a customer of a cloud provider network. The first network address pool is divided into a second network address pool for a cloud resource of the customer. A first network address block from the second network address pool is assigned to the cloud resource.

Abstract: Systems and methods are provided for creating and running an instance of a dynamic access control system (DACS). Trust providers may be defined in a trust broker of the DACS such that trust information associated with the trust providers can be used to create a custom data structure. Resources and resource groups may be defined in the DACS. Policies may be configured or coded in the DACS to map the custom data structure to recourses or resources groups. Additionally, policies may be configured or coded in the DACS to route the data structure and request to network segments or shared with other parties.

Abstract: A first set of network addresses of a first address family, and a second set of network addresses of a second address family, are assigned to a virtual machine. At a routing device, respective routing information entries for the two sets of network addresses are stored, without storing routing information entries for individual addresses of the sets. A first packet with a destination address within the first set, routed using the routing information entry for the first set, is obtained at the virtual machine. A second packet with a destination address within the second set, routed using the routing information entry for the second set, is obtained at the virtual machine.

Abstract: Systems and methods are provided for creating and running an instance of a dynamic access control system (DACS). Trust providers may be defined in a trust broker of the DACS such that trust information associated with the trust providers can be used to create a custom data structure. Resources and resource groups may be defined in the DACS. Policies may be configured or coded in the DACS to map the custom data structure to recourses or resources groups. Additionally, policies may be configured or coded in the DACS to route the data structure and request to network segments or shared with other parties.

Abstract: Systems and methods are provided for creating and running an instance of a dynamic access control system (DACS). Trust providers may be defined in a trust broker of the DACS such that trust information associated with the trust providers can be used to create a custom data structure. Resources and resource groups may be defined in the DACS. Policies may be configured or coded in the DACS to map the custom data structure to recourses or resources groups. Additionally, policies may be configured or coded in the DACS to route the data structure and request to network segments or shared with other parties.

Abstract: Techniques and technologies for an Internet Protocol (IP) address management (IPAM) system to track and manage IP address workflows in a network. The IPAM system can be used to define and enforce management policies or rules regarding IP address management, such as allocation policies, refill policies, and so forth. For instance, the IPAM system can enforce allocation policies that define rules to allow or deny allocation of IP addresses based on types of resources for which the IP addresses are requested, registered user accounts that are requesting the IP addresses, the purpose of the resources receiving the IP addresses, and so forth. Additionally, the IPAM system can enforce refill policies that define rules for replenishing inventories of IP addresses that have been allocated for different domains in the network. The IPAM system can improve the management of IP address workflows by enforcing policy and tracking IP address workflows in networks.

Abstract: Techniques and technologies for an IP address management (IPAM) system to monitor the usage of IP addresses across regions in one or more networks of resources. The IPAM system may be used to allocate IP addresses to resources in networks and track what IP addresses are being used by resources or available for allocation. The IPAM system may periodically obtain usage information that indicates actual, current IP address usage by the resources in the networks, identify differences between the current IP address usage and an inventory maintained by the IPAM service, and reconcile the differences. Additionally, the IPAM system may further respond to network administrator queries about their resource and IP address usage. Further, the IPAM system may emit various utilization metrics to the network administrators which may be tied to alarms or alerts around non-compliant resources or IP addresses.

Abstract: Techniques implemented by an IP address management (IPAM) system for monitoring the usage of IP addresses in networks of computing resources and automatically notifying networking devices when IP address usage has changed. The IPAM system may create pools of IP addresses (e.g., address groups), and map those pools to prefix lists that are distributed to the networking devices. The IPAM system may monitor changes in IP address usage by resources in the networks (e.g., allocations and releases of IP addresses), update the pools that are affected by the changes, carry those changes through to the appropriate prefix lists, and propagate updated prefix lists to the networking devices (e.g., firewall devices, routing devices, etc.). In this way, the IPAM system may automatically identify and apply IP address changes to prefix lists that are used for networking operations in the networks.

Abstract: Disclosed are various embodiments for distributed network address allocation management. In one embodiment, a first instance of a plurality of instances of an allocation management service assigns a first portion of a network address space to the first instance and a second portion of the network address space to a second instance of the plurality of instances. The second instance receives a request to allocate a particular network address block. The second instance allocates the particular network address block from the second portion of the network address space by updating an allocation data structure. An allocation of the particular network address block is returned in response to the request. A copy of the allocation data structure maintained by the first instance is updated asynchronously based at least in part on the allocation of the particular network address block.

Abstract: Techniques implemented by an IP address management (IPAM) system for monitoring the usage of IP addresses in networks of computing resources and automatically notifying networking devices when IP address usage has changed. The IPAM system may create pools of IP addresses (e.g., address groups), and map those pools to prefix lists that are distributed to the networking devices. The IPAM system may monitor changes in IP address usage by resources in the networks (e.g., allocations and releases of IP addresses), update the pools that are affected by the changes, carry those changes through to the appropriate prefix lists, and propagate updated prefix lists to the networking devices (e.g., firewall devices, routing devices, etc.). In this way, the IPAM system may automatically identify and apply IP address changes to prefix lists that are used for networking operations in the networks.