You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More and more network engineers are being tasked with needing to manage cloud networks. AWS has a number of different resources and configuration files. While tools like terraform can help to setup and maintain the current configuration, they don't keep the actual state of the configs of cloud resources (For AWS, it is JSON files).
Given how many cloud networks are setup, many resources can be changed by multiple teams and may have shared controls. Being able to take snapshots of AWS along with the current on-premise network for comparison can help in diagnosing if there are issues due to recent changes or not.
This would require creating a new model, and AWS does have library support for AWS. Oxidized would need to be provided with credentials in a similar manner as on-premise devices, log into each configured account and download the json configuration for resources that affect the network. For example VPCs, security groups, transit gateways would be retrieved but things like IAM would not.
The text was updated successfully, but these errors were encountered:
More and more network engineers are being tasked with needing to manage cloud networks. AWS has a number of different resources and configuration files. While tools like terraform can help to setup and maintain the current configuration, they don't keep the actual state of the configs of cloud resources (For AWS, it is JSON files).
Given how many cloud networks are setup, many resources can be changed by multiple teams and may have shared controls. Being able to take snapshots of AWS along with the current on-premise network for comparison can help in diagnosing if there are issues due to recent changes or not.
This would require creating a new model, and AWS does have library support for AWS. Oxidized would need to be provided with credentials in a similar manner as on-premise devices, log into each configured account and download the json configuration for resources that affect the network. For example VPCs, security groups, transit gateways would be retrieved but things like IAM would not.
The text was updated successfully, but these errors were encountered: