Background
A change was made in 1.6.0 where security groups were deleted and replaced with another set of rationalized security groups. It was discovered after-the-fact that some clients had reused those old security groups in other assets in their environment (e.g. AWS Batch CE).
The old security groups were reintroduced in 1.6.1 as an update bridge. with the intention to deprecate (see: 1.6.1 deprecation warning). This was delayed for another release to give affected parties more time to transition, but the components must be ripped out in Release 1.8
Tasks
TBD
Background
A change was made in 1.6.0 where security groups were deleted and replaced with another set of rationalized security groups. It was discovered after-the-fact that some clients had reused those old security groups in other assets in their environment (e.g. AWS Batch CE).
The old security groups were reintroduced in 1.6.1 as an update bridge. with the intention to deprecate (see: 1.6.1 deprecation warning). This was delayed for another release to give affected parties more time to transition, but the components must be ripped out in Release 1.8
Tasks
TBD