You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/installation/installation.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -268,6 +268,8 @@ If deploying to an internal AWS employee account, to successfully install the so
268
268
Current Issues:
269
269
270
270
- Occasionally CloudFormation fails to return a completion signal. After the credentials eventually fail (1 hr), the state machine fails. Simply rerun the state machine.
271
+
- In v1.3.5 new deployments the State Machine fails in Phase 1 on a GuardDuty delegated admin issue which causes the stack to rollback and then causes an issue with Macie. In the Organization Management account, in every 'supported-region' defined in the config file, check for the existance of a completed Phase 1 stack. If the Phase 1 stack does NOT exist in the region, disable or ensure the Macie Delegated Admin account is removed from Macie for that region. If the Phase 1 stack exists, Macie Delegated Admin should be and remain enabled. Once validated for all regions, rerun the state machine.
272
+
- In v1.3.6 the Macie issue from v1.3.5 has been resolved, but Guardduty continues to cause the state machine to fail. Simply rerun the state machine. We are working on a fix.
- Resources will have the 'Name' tag assigned, where Name={name}{suffix}
4
+
- No prefix or suffix will be applied to DNS records/zones (as that breaks them)
5
+
- When \_ is not supported, a - will be used
6
+
- Stacks/stacksets/functions and **_non-end user_** accessed objects deployed in all accounts will also start with the {AcceleratorPrefix} prefix (i.e. "**_PBMMAccel-_**" or "**_ASEA-_**")
7
+
- The prefix does not apply to objects like VPC's, subnets, or TGW's which customers need to directly access. This is for objects deployed to build the customer accessible objects
8
+
- This prefix will be protected by SCP's so customers don't break 'managed' features
9
+
- Resources will have the tag 'Accelerator={AcceleratorName}' assigned when tags are supported
10
+
- Stacks will have the tag 'AcceleratorName={AcceleratorName}' assigned, which will often (but not always) be inherited by objects created by the stack (due to TGW duplicate tag issue)
11
+
12
+
### Defaults
13
+
14
+
- the default {AcceleratorName} is 'PBMM' before v1.5.0 and 'ASEA' after v1.5.0
15
+
- the default {AcceleratorPrefix} is 'PBMMAccel-' before v1.5.0 and 'ASEA-' after v1.5.0
1. Log into the AWS console as a Full Administrator to the Organization Management account.
72
+
2. Start a CloudShell session.
73
+
3. Copy the files from this folder and your `config.json` to the CloudShell session;
74
+
- ensure the management account name is properly reflected in the config file, or the script will fail;
75
+
- the script does not handle the use of the {HOME_REGION} variable (at this time), replace all occurances with the actual name of the home region (i.e. ca-central-1).
0 commit comments