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
Launching the stack via the "Launch Stack" button does NOT prompt for:
Clone EFS, use the System ID of an existing EFS Filesystem.
DBRestore from Snapshot, enter the cluster Snapshot name from the RDS console. (formatted rds:wordpress-stack-name-rds-xxxxxxxx-databasecluster-apzdbrozmzcn-snapshot-date)
However, the individual Templates (03-efsfilesystem, 03-rds) clearly have provisions regarding the same.
Additionally, the 2 links to review the [master] template gives a 404 error.
The text was updated successfully, but these errors were encountered:
I've been running into these very same issues @michael-newman, using the files provided here on GitHub. I have noticed that by using the S3 versions, everything builds as expected. Did you ever resolve your issues?
@badcrocodile, yes, resolved; but, I would not say eloquently in the CloudFormation templates. If I’m recalling correctly, there was a disconnect between the Master Template and the individual templates—so, we wound up running templates individually which got us past the RDS issue noted above; however, we had a different issue re EFS w/ VPC peering which is documented in issue #44.
Launching the stack via the "Launch Stack" button does NOT prompt for:
Clone EFS, use the System ID of an existing EFS Filesystem.
DBRestore from Snapshot, enter the cluster Snapshot name from the RDS console. (formatted rds:wordpress-stack-name-rds-xxxxxxxx-databasecluster-apzdbrozmzcn-snapshot-date)
However, the individual Templates (03-efsfilesystem, 03-rds) clearly have provisions regarding the same.
Additionally, the 2 links to review the [master] template gives a 404 error.
The text was updated successfully, but these errors were encountered: