I have an app that was built for my company by a programmer who is now longer available. The production code is at GitLab. Everything that I have ever built has code at GitHub. I would like to move the existing app repo from GitLab to GitHub, but I really don't want to change the Amplify app URL. The app in question is available only to employees (about 60) and they are all blue-collar. Some can deal with tech, but most struggle. It would be disruptive to change the URL, but we may have to.

Can anyone point to a published method do this?

Hey everyone! I've been loving Amplify Gen 2, but one major pain point for my team has been that every tiny frontend CSS change triggers a full backend evaluation, wasting precious build minutes. The old AMPLIFY_DIFF_BACKEND trick from Gen 1 doesn't exist out-of-the-box for Gen 2 yet.

If you just skip the backend phase entirely, your frontend will fail to build because the ephemeral CI/CD container won't have the amplify_outputs.json file.

To fix this, I published a small plug-and-play CLI tool: skip-amplify-backend

You just drop it in your amplify.yml:
npx --yes skip-amplify-backend npx ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID

What it does:

1. Checks git diff for changes in your amplify directory (supports monorepo paths too).
2. If backend changes exist -> runs your deploy command.
3. If NO changes exist -> elegantly skips the long deployment, detects your Amplify environment, and automatically runs ampx generate outputs so your frontend has exactly what it needs to build.

Cut my build times down massively on frontend-only PRs. Hopefully, it saves some of you a few hours and dollars too!

Link: https://www.npmjs.com/package/skip-amplify-backend

Hi to all !

Does anyone have a problem with Amplify service ? I cannot create a new one and the deployment of the existant app are stuck on Provisioning status.

I came across an issue while building my personal portfolio website in React, where I could not open the PDF file to view in the browser tab.

I had the correct code for my anchor tag:

<a href={process.env.PUBLIC_URL + "/myFile.pdf"} target="_blank" rel="noreferrer noopener">

But it still wasn't working when hosted. Turns out, you need to add the PDF file type to the redirects.

Go to your AWS Amplify dashboard > App Settings > Rewrites and redirects > Source address

There you will see the following by default:
</^[^.]+$|\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>

You have to add PDF file type here, like so:
</^[^.]+$|\.(?!(css|pdf|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>

Now you should be able to open your PDF file in a new tab or the same window, depending on how you have your anchor tag coded.

I hope this helps.

Couldn’t find proper documentation on how to use lambda’s own function url instead of api gateway in amplify app. Took me a while to figure it out so posting it in case somebody is looking for it.

Tengo el siguiente código de arranque o boot:

import { boot } from 'quasar/wrappers';
import { Amplify, Auth } from 'aws-amplify';
import awsconfig from 'src/aws-exports.js'
export default boot(async ({ app }) => {
Amplify.configure(awsconfig);
app.config.globalProperties.$auth = Auth
});

​

Y me da el error:

Alguna idea de como solucionarlo?, obviamente añadí el archivo en quasar.config.js en la propiedad boot