Build failng due to environment variables access

Hello, So my site failed to build because it says it doesn’t have access to the environment variables, I added the variables to the build settings and to netlify.toml file so not sure why this would be an issue. the apps works just fine locally.

Site Name:
Buil Log:
11:43:51 AM: build-image version: 3d3c7e8b4321e2c1a54a2c4584fb46ba742b1630 (focal)
11:43:51 AM: buildbot version: 72ed9578274f76ae72cdce4c5312615aeecc32fb
11:43:51 AM: Fetching cached dependencies
11:43:51 AM: Starting to download cache of 111.7MB
11:43:52 AM: Finished downloading cache in 1.263s
11:43:52 AM: Starting to extract cache
11:43:53 AM: Finished extracting cache in 736ms
11:43:53 AM: Finished fetching cache in 2.045s
11:43:53 AM: Starting to prepare the repo for build
11:43:54 AM: Preparing Git Reference refs/heads/main
11:43:55 AM: Custom publish path detected. Proceeding with the specified path: ‘public’
11:43:56 AM: Starting to install dependencies
11:43:56 AM: Python version set to 3.8
11:43:56 AM: Attempting Ruby version 2.7.2, read from environment
11:43:57 AM: Using Ruby version 2.7.2
11:43:57 AM: Started restoring cached go cache
11:43:57 AM: Finished restoring cached go cache
11:43:59 AM: go version go1.19.13 linux/amd64
11:44:00 AM: Using PHP version 8.0
11:44:01 AM: Started restoring cached Node.js version
11:44:02 AM: Finished restoring cached Node.js version
11:44:02 AM: v18.20.2 is already installed.
11:44:02 AM: Now using node v18.20.2 (npm v10.5.0)
11:44:02 AM: Enabling Node.js Corepack
11:44:02 AM: Started restoring cached build plugins
11:44:02 AM: Finished restoring cached build plugins
11:44:02 AM: Started restoring cached corepack dependencies
11:44:02 AM: Finished restoring cached corepack dependencies
11:44:02 AM: No npm workspaces detected
11:44:02 AM: Started restoring cached node modules
11:44:02 AM: Finished restoring cached node modules
11:44:03 AM: Installing npm packages using npm version 10.5.0
11:44:10 AM: npm WARN deprecated source-map-url@0.4.1: See GitHub - lydell/source-map-url: [DEPRECATED] Tools for working with sourceMappingURL comments.
11:44:10 AM: npm WARN deprecated resolve-url@0.2.1: GitHub - lydell/resolve-url: [DEPRECATED] Like Node.js’ `path.resolve`/`url.resolve` for the browser.
11:44:10 AM: npm WARN deprecated urix@0.1.0: Please see GitHub - lydell/urix: [DEPRECATED] Makes Windows-style paths more unix and URI friendly.
11:44:10 AM: npm WARN deprecated source-map-resolve@0.5.3: See GitHub - lydell/source-map-resolve: [DEPRECATED] Resolve the source map and/or sources for a generated file.
11:44:17 AM: added 1359 packages, and audited 1539 packages in 15s
11:44:17 AM: 241 packages are looking for funding
11:44:17 AM: run npm fund for details
11:44:17 AM: 2 high severity vulnerabilities
11:44:17 AM: Some issues need review, and may require choosing
11:44:17 AM: a different dependency.
11:44:17 AM: Run npm audit for details.
11:44:17 AM: npm packages installed
11:44:18 AM: Failed during stage ‘building site’: Environment variable ‘AWS_ACCESS_KEY’ isn’t available for direct interaction
11:44:18 AM: Successfully installed dependencies
11:44:18 AM: Failing build: Failed to build site
11:44:18 AM: Finished processing build request in 27.435s

any assistance would be greatly appreciated, a used the same repository for and the build is successful but its 404 page not found error.
in desperate need of help please.

can you share a link to your repo?

Sure, thx for responding, I also attached screen shots of my build settings and environment variables

Hi @sxyjon,

Thanks for following up.

I believe you’re running into this issue (based on the error message) as the AWS_ is reserved name. Here’s a link to a similar post:

Could you give the solution mentioned a try and see if that resolves the issue?

Hello Melvin,
Thank you for that response it worked my app successfully built but now I have to figure out hpw to get it to connect to my bucket. it doesn’t seem to be uploading the file, getting 404 error when it tries, weird because it works just fine locally. gonna do some research and check file paths.