Technically in this example there is no real need for the artefacts or any output within the amplify.yml file - as the serverless framework component is actually coordinating the build and deployment of the front end resources. If you had additional static resources however, or were merging items from a larger monorepo type environment that needed to be lifted out to perhaps a public facing s3 bucket, then this is the place to do that.
Thanks for the article Aaron,
I have just one doubt, what do you put as the output in baseDirectory in the amplify.yml file
Cheers Diego,
Technically in this example there is no real need for the artefacts or any output within the amplify.yml file - as the serverless framework component is actually coordinating the build and deployment of the front end resources. If you had additional static resources however, or were merging items from a larger monorepo type environment that needed to be lifted out to perhaps a public facing s3 bucket, then this is the place to do that.
Thank you Aaron, my issue was that I forgot to add the domain to the serverless.yml, after I added it it worked perfectly
Great post!!