Master Template does NOT include parameters for DB Restore from Snapshot or Clone EFS

aws-samples / aws-refarch-wordpress

This reference architecture provides best practices and a set of YAML CloudFormation templates for deploying WordPress on AWS.

MIT No Attribution

1.08k stars 601 forks source link

Master Template does NOT include parameters for DB Restore from Snapshot or Clone EFS #42

Open michael-newman opened 6 years ago

michael-newman commented 6 years ago

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.

michael-newman commented 6 years ago

@darrylsosborne ... would welcome your thoughts!

mteichtahl commented 5 years ago

I had the same. I used a default of '' and this resolved the issue.

badcrocodile commented 5 years ago

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?

michael-newman commented 5 years ago

@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.