Closed t04glovern closed 2 years ago
Ah, sorry; I've just seen this comment in the spoke template; so I presume this is unlikely to be a supported featured. Feel free to close the issue if so.
Conditions:
# Adding an EventBus as a target within an account is not allowed.
IsSpokeAccountEqualToHubAccount: !Not [!Equals [!Ref HubAccount, !Ref "AWS::AccountId"]]
When trying to deploy the Spoke template into the same account as the Hub we recieve the following error
I believe this is because the Service Linked Role is created in both the Hub and Spoke templates https://github.com/aws-solutions/serverless-transit-network-orchestrator/search?q=CustomServiceLinkedRole&type=code
Could the role creation be put behind a Conditional check for a parameter, something like the following?
This would be handy for users who might have other Networking infrastructure such as client VPN configurations that might require VPC's and attachments in the networking account.