Sharing code efficiently across different parts of an application can be challenging with AWS Lambda, especially when using Amplify. Today, I’ll walk you through a solution to this common problem, without relying on Lambda Layers or private NPM repositories. The Context In my previous post about Lambda Layers [1], I delved into its limitations, especially …
Amplify: how to share code without Lambda Layers or private NPM Read More »
You might have encountered this issue when using Amplify to host your single-page applications. An image in the public folder would show up perfectly fine when running locally but it was not found on the live site after Amplify deployed your change. Curiously, this only happens with some images – jpeg, avif, webp… The reason …
Amplify: how to fix images that show up locally but not after deployment Read More »
Update 04/08/2022: turns out there are some valid reasons (analytics and potentially SEO) for redirecting from the apex domain to www. Please see comments from Michael Hart, Mike Lamb and Tyler Love to my tweet here for more details. I have used Amplify to host all my single-page applications, including the newly revamped sites …
Amplify: you shouldn’t allow redirect from apex to www Read More »
When you start a new Vue.js project that needs to interface with APIs running in AWS, there’s a good chance you will have these lines of code: import Amplify from ‘aws-amplify’ Amplify.configure({ Auth: { region: ‘us-east-1’, userPoolId: ‘xxx’, userPoolWebClientId: ‘xxx’, mandatorySignIn: true } }) These few lines of code let you use the aws-amplify library …
How to configure environment specific parameters with Vue.js and Amplify Read More »
By continuing to use the site, you agree to the use of cookies. more information
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.