STNO Portal Shows only 1 CIDR about network-orchestration-for-aws-transit-gateway HOT 1 OPEN

@Cupidazul Thanks for diving deep and sharing your feedback.

For Items 1, 2, 3 - We have added this new use case to our backlog and will review in the next release.

For Item 4, the use case is to protect the route changes for TGW route tables that has approval required. We have added a backlog item to require approval if the tag was removed. However, not sure if we can add deletion protection. The user/roles in the spoke account or even SCPs should be implemented to deny VPC attachment deletion permissions.

For Item 5, as per design, you should be able to update the tags and it will trigger the workflow to update the association or propagation. Please advise if update is not working for you with the steps on how to duplicate the issue. It would be best to open a support case for this item if necessary.

For item 6, as per design, the attachment API requires at least one subnet ID. Tagging a VPC first can't create attachments. To start the attachment worflow, you must tag the VPC first then subnets. We can consider improving the UI experience by hiding the Approve/Reject button for VPC change item in the table to avoid confusion. To append a new subnet to the attachment they should be approved individually.

For item 7, this is outside the scope of the use cases and will not be supported as a feature for STNO.

Thanks again for reaching out to us.

from network-orchestration-for-aws-transit-gateway.