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
Just did a fresh setup via the CDK, and when I was walking through the manual steps under Option 2: DataSync and S3 section of the readme, there's a couple things missing that might've changed since the last time these steps were updated:
Under "Step 2: Create an EFS -> S3 DataSync Task", there's 2 additional fields that the form requires for the EFS location:
Subnet - I think any of the subnets created during setup will work, I've tested with my minecraft-server-stack/Vpc/PublicSubnet1 and minecraft-server-stack/Vpc/IsolatedSubnet3 and they both work (as long as the next setting is correct)
Security Group - this must be the one that starts with minecraft-server-stack-ServiceSecurityGroup, using the other SG created (minecraft-server-stack-FileSystemEfsSecurityGroup) or a default SG will not work OOTB
For the files included, you have to specify a / in front of the file names, which is weird but the form fails validation if any of the fields are missing it (personally, I just use the "Entire source location" option to avoid the hassle)
The text was updated successfully, but these errors were encountered:
Just did a fresh setup via the CDK, and when I was walking through the manual steps under Option 2: DataSync and S3 section of the readme, there's a couple things missing that might've changed since the last time these steps were updated:
minecraft-server-stack/Vpc/PublicSubnet1
andminecraft-server-stack/Vpc/IsolatedSubnet3
and they both work (as long as the next setting is correct)minecraft-server-stack-ServiceSecurityGroup
, using the other SG created (minecraft-server-stack-FileSystemEfsSecurityGroup
) or a default SG will not work OOTB/
in front of the file names, which is weird but the form fails validation if any of the fields are missing it (personally, I just use the "Entire source location" option to avoid the hassle)The text was updated successfully, but these errors were encountered: