Add test account to the electronic-monitoring-data account #7998
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A reference to the issue / Description of it
Electronic monitoring are going to be receiving data from external suppliers who will be pushing data to an S3 bucket. We want to test and ensure this connection is secure outside of our Production account.
How does this PR fix the problem?
It creates a test account where we can test suppliers sending dummy data before promoting to Prod.
We then have an action to exclude spinning up most infra in our test account as many things won't be needed.
How has this been tested?
Please describe the tests that you ran and provide instructions to reproduce.
Not tested, just eyeballed config file update against other accounts.
Deployment Plan / Instructions
Will this deployment impact the platform and / or services on it?
No
Checklist (check
x
in[ ]
of list items)Additional comments (if any)
Original account request > #5833