Skip to content
This repository was archived by the owner on Feb 27, 2024. It is now read-only.
This repository was archived by the owner on Feb 27, 2024. It is now read-only.

Add support for Injecting an "instrumentation" Security Group #11

Description

@ferricoxide

Expected behavior

When operating in a dashboarded environment, need the ability for CMDB tools (and the like) to connect to the EC2 elements.

Actual behavior

EC2 elements exist inside a sealed silo

Steps to reproduce behavior

Context/Specifications

Suggestions for fix

Add a stanza similar to:

"Fn::If": [
  "AssignExtraSecurityGroup",
  { "Ref": "ExtraSecurityGroupId"},
  { "Ref": "AWS::NoValue" }
]

To the EC2's NetworkInterfaces » GroupSet section (and relevant supporting Conditions and Parameters)

Relevant references

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions