IPAM Synchronization for Amazon AWS Cloud PlatformCentralized Cloud Network Visibility
Avoid Losing Control of Your Cloud Infrastructure
Amazon Web Services offers a great platform for pushing corporate datacenter boundaries with a very flexible model. By using the API or Cloud Formation descriptive model to build and destroy infrastructure, I&O teams are gaining in elasticity and agility. To an extent, they have proposed directly to development teams, through a portal, to manage their own infrastructure based on predefined templates. This allows dev teams to easily have environments for demoing and testing their progress in an agile and devops approach. This leads to a lot of deployments in AWS, some ephemeral and some more durable, but in the meantime I&O teams need to deal with security, continuity, cost optimization, auditing and coherence.
Whereas deployment in well known datacenters is straightforward to manage and troubleshoot, it is a bit more complex when multiple clouds are used. The scenario becomes even worse when autonomy is provided to other teams which can be far away from I&O teams and build infrastructure on their own.
The DDI ecosystem needs to be fully interfaced with all the cloud environments used by the corporation in order to guarantee central visibility and offer the ability to automate all processes.
IPAM for Cloud Infrastructure Visibility
Servers and workloads are spread across multiple clouds, including in Amazon Web Services, so have become complex to control. Understand how to improve global visibility over cloud resources and keep your network repository always up to date.
Global Visibility using Single Pane of Glass
SOLIDserver IPAM integrates a global view over AWS Virtual Private Cloud (VPC) network resources. This offers complete IP topology visibility of any networks deployed in the AWS public cloud, alongside the ones hosted on premises. All the computing servers hosted in AWS EC2 and using an IP address on a subnet are also visible directly in the central IPAM, allowing unification of the administration process and reporting.
Once synchronization information is provided to the central IPAM, all AWS cloud networks are, throughout their lifetime, automatically created, modified or removed. IPAM still remains the central repository even with EC2 cloud hosted workloads. This enables visibility for I&O teams in processes like policy control, auditing or accounting in addition to standard management and troubleshooting.
Push Cloud Limits with Seamless Integration
SOLIDserver Cloud IPAM Sync is based on AWS API and requires no additional tools or solutions to be set up. Security of access is controlled directly in the Identity and Access Management service (IAM) via a dedicated API token. All communications are using an encrypted channel in order to guarantee confidentiality and integrity of the data exchanges.
Provisioning of the link between AWS Cloud Services and the SOLIDserver is a very simple task, requiring an IAM API key to be associated with an identity and a few parameters to be set in the IPAM. It only takes 5 minutes to perform all actions on both sides and directly see the blocks, subnets and endpoints created in the space during synchronization.
Ease Automation Tasks with Object and Concept Mapping
SOLIDserver IPAM has a very clever way to present IP network information to the network administrator. The object hierarchy is presented on overlapping views from the entire VLSM topology down to the single IP address associated with an endpoint.
From AWS topology, Cloud IPAM Sync maps VPC address range, subnets and endpoints into the IPAM topology based on blocks, networks and IP addresses. As region and AZ (availability zones) are also synchronized in meta-data, any network can easily be positioned in the AWS topology. If the name tag is positioned on resources in AWS, the name of each object is used on the IPAM in preference to its ID, easing navigation and network automation tasks.
Ensure Data Protection Through Synchronization and Filtering
AWS hosting is organized by region and virtual private cloud resources. A region is large enough and generally composed of enough distant datacenters to provide overall redundancy for any application. Resources can be spread across different availability zones (AZ) to provide geographical distancing and redundancy. The VPC entity can be used to separate applications or businesses environments or be able to apply specific security patterns like segmentation and zoning.
The IPAM cloud network synchronization is mainly based on region as the pivotal point to an IPAM space. All subnets within the AWS IPAM inside region VPC can be kept in sync with the network topology in the IPAM central view. Filtering by VPC is an option to limit which networks will be synchronized, for confidentiality, performance or regulation reasons.
Flexible APIs and Automated Process for Advanced Orchestration
With all IP networking objects synchronized from AWS VPC, the flexible APIs and automation process available by default in the SOLIDserver can be used for richer orchestration, control and security automation within the whole ecosystem. All existing tools and solutions already connected to the SOLIDserver DDI solution can directly benefit from AWS networking information and extend their coverage without any major change.
Single Pane of Glass Management
Accurate Cloud Usage Reporting
Easy Integration with Open APIs
Only 5-Minute Installation
Discover a DDI solution for global visibility and rich automation across multi-cloud infrastructures.
Discover what a DDI solution is and how it works.
Rising Prominence of DDI in Making Multi‐Cloud Strategies Secure and Successful