aws-amplify/amplify-hosting issues and pull requests

#4058 - Removed elements from data schema do not get removed from amplify_outputs.json after redeployment

Issue - State: open - Opened by nonhaltingmadness 3 months ago
Labels: console, pending-triage

#4057 - Amplify Data Manager crashes when viewing item with an array of a custom type

Issue - State: open - Opened by Orf1 2 months ago - 1 comment
Labels: console, pending-triage

#4056 - AWS Amplify Console Stuck On Loading Spinner

Issue - State: open - Opened by thejohnyu 2 months ago
Labels: transferred, console, pending-triage

#4055 - Completely custom pipeline without any Amplify wrappers or images

Issue - State: open - Opened by OperationalFallacy 2 months ago - 1 comment
Labels: feature-request

#4054 - Slow cache artifact creation and extraction steps

Issue - State: open - Opened by Eazash 3 months ago
Labels: console, pending-triage

#4053 - Unable to access env variables in backend build creation

Issue - State: open - Opened by vishaljkk 3 months ago - 1 comment
Labels: console, pending-triage

#4052 - Rate limit for "Access control" is too agressive

Issue - State: open - Opened by em1382 3 months ago - 1 comment
Labels: feature-request

#4051 - CustomerError: Can't find required-server-files.json in build output directory

Issue - State: open - Opened by wyf-orbiter 3 months ago - 1 comment
Labels: feature-request

#4050 - Repositories dont appear when you have many

Issue - State: open - Opened by emeagenciadigital 3 months ago - 2 comments
Labels: feature-request

#4049 - DNS keeps changing the Subdomain Records each time i try to confirm, causing an endless loop.

Issue - State: open - Opened by dbrunet73 about 1 year ago - 1 comment
Labels: feature-request, hosting

#4048 - Clicking Re-run in Github Checks does not work

Issue - State: open - Opened by mattfirtion about 1 year ago - 1 comment
Labels: feature-request, hosting

#4047 - AWS Amplify Console Web Preview is not finishing

Issue - State: open - Opened by Lychas about 1 year ago - 3 comments
Labels: feature-request, hosting

#4046 - Exclude specific branches detection not working in Amplify

Issue - State: open - Opened by ashokvaddevalli 9 months ago - 1 comment
Labels: feature-request, hosting

#4045 - The Amplify app changed the platform without outside intervention

Issue - State: open - Opened by JZechy 9 months ago - 10 comments
Labels: question, hosting

#4044 - How to access secrets in the nodeJS back end code (AWS Amplify Gen 2)?

Issue - State: open - Opened by swbergmann 7 months ago - 5 comments
Labels: feature-request, hosting

#4043 - Creating Next.js app from AWS Amplify doesn't detect the framework

Issue - State: open - Opened by cloudhx 7 months ago - 2 comments
Labels: question, hosting

#4042 - set retain policy to destroy for resources created by PR deploy previews

Issue - State: open - Opened by josefaidt 7 months ago - 2 comments
Labels: feature-request, hosting, deploy

#4041 - Allow filtering query params for cloudfront policy or custom cloudfront policy

Issue - State: open - Opened by mattrunyon 6 months ago - 2 comments
Labels: feature-request, hosting

#4040 - Could we have access logs

Issue - State: open - Opened by jefflutely 4 months ago - 4 comments
Labels: question, hosting

#4039 - amplify_output.json not updated (updated async after a day) after each deployment

Issue - State: open - Opened by scorobogaci 10 months ago - 9 comments
Labels: bug

#4038 - BootstrapDetectionError: Unable to detect CDK bootstrap stack due to permission issues. On backend build Unable to deploy monorepo.

Issue - State: open - Opened by crafael23 9 months ago - 14 comments
Labels: bug, deploy

#4037 - Amplify deploy fails when using pnpm catalogs

Issue - State: open - Opened by hwwi 8 months ago - 3 comments
Labels: feature-request

#4036 - Turborepo fails when its nested two levels down. CustomerError: The 'node_modules' folder is missing the 'next' dependency.

Issue - State: open - Opened by a3har 7 months ago - 11 comments
Labels: bug

#3994 - Unable to assume specified IAM Role. Please ensure the selected IAM Role has sufficient permissions and the Trust Relationship is configured correctly.

Issue - State: closed - Opened by markcoders1 5 months ago - 6 comments
Labels: question

#3980 - CustomerError: The size of the build output (244749949) exceeds the max allowed size of230686720 bytes. Please reduce the size ofyour build output and try again.

Issue - State: closed - Opened by SoorajCanbridge 7 months ago - 3 comments
Labels: feature-request

#3959 - Amplify Github App posts empty preview link on the PR even if deployment was skipped because of `AMPLIFY_DIFF_DEPLOY`

Issue - State: open - Opened by taraspos 9 months ago - 2 comments
Labels: feature-request

GitHub / aws-amplify/amplify-hosting issues and pull requests