This will use whatever your default AWS access/secret access keys are, either in ~/.aws/credentials or in your env.
The ultimate goal of this stack is to deploy all infra needed to host a Dockerized UI and API + Postgres RDS (not yet implemented) from an empty AWS account, including all network, roles and peripheral resources.
This is a learning exercise and probably sucks in several ways that I am unaware of.
Locally:
tf plan- Verify everything looks good
tf apply
When starting from scratch, I suspect this will throw errors if you do not push any Docker images to the created ECR repositories before executing the portions of the config that rely on the existence of a Docker image in the specified repos.
I had to use docker buildx build --platform=linux/amd64 -t <tag> . when building my images to send to ECR to run on Fargate as apparently building Docker images on Apple silicon will cause problems when running on amd boxes.