ecs-files-composer VS wordpress-demo

I have an app where I used Files-Composer as the container that gets the secrets. In there I have a Jinja2 template for the final fine, and the files-composer just renders the config file into a docker volume that is then shared with the main app (once it is finished). That way for apps that do not support to use env vars to set properties, you have a way around it :)

Enough talking about it from me, please post back some feedback and open Feature Requests on GH.

You could probably near copy-paste the wordpress example to change your DNS Settings, certificates etc., adopt the DB as you need, into a docker extension file specifically for your AWS environment. It could create a new VPC and all for you, but given you already did that, you can simply get to plug and play into your existing VPC via Lookup.

Hope this helps you in your journey to AWS. PS: Got a demo with wordpress which I use continuously you can find here.

Here is a GH repo with a wordpress demo that uses compose-x to deploy bitnami/wordpress using RDS, ALB and EFS. I deployed it adding ACM certificate to get HTTPS going, and works like a charm.

The wordpress-demo has been updated to add EFS and volumes to show-case that new feature.

Here is an example using wordpress (and the blog post going with it) which might given you a good reference.