text:
while deploying my nextjs project with sentry on aws amplify build getting failed

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
Next.js
Amplify APIs
Not applicable
Amplify Categories
Not applicable
Environment information

# Put output below this line

Describe the bug
I am using nextjs 11.1.3 when I added sentry error tracking to my next js project when i build and run it locally it works fine but when i deploy my sentry nextjs project on aws amplyfy my build getting failed with following error,
'> Build error occurred\n' +
                                  'Error: spawn ENOMEM\n' +
                                  '    at ChildProcess.spawn (node:internal/child_process:420:11)\n' +
                                  '    at spawn (node:child_process:733:9)\n' +
                                  '    at fork (node:child_process:169:10)\n' +
                                  '    at ChildProcessWorker.initialize (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:141:45)\n' +
                                  '    at new ChildProcessWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:132:10)\n' +
                                  '    at WorkerPool.createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:44:12)\n' +
                                  '    at new BaseWorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/base/BaseWorkerPool.js:135:27)\n' +
                                  '    at new WorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:30:1)\n' +
                                  '    at new Worker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/index.js:167:26)\n' +
                                  '    at createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:15:28)\n' +
                                  '    at new Worker1 (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:21:9)\n' +
                                  '    at /codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:432:31\n' +
                                  '    at async Span.traceAsyncFn (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/telemetry/trace/trace.js:60:20)\n' +
                                  '    at async Object.build [as default] (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:77:25) {\n' +
                                  '  errno: -12,\n' +
                                  "  code: 'ENOMEM',\n" +
                                  "  syscall: 'spawn'\n" +
                                  '}',
                                  failed: true,
                                  timedOut: false,
                                  isCanceled: false,
                                  killed: false
                                  }
                                  [G
2023-08-10T16:47:33.927Z [ERROR]: [?25h[G[J
                                  300s › darxjey0xrl5c › Error: Command failed with exit code 1: node_modules/.bin/next build

To Reproduce
Below is my aws amplify build logs
'> Build error occurred\n' +
'Error: spawn ENOMEM\n' +
'    at ChildProcess.spawn (node:internal/child_process:420:11)\n' +
'    at spawn (node:child_process:733:9)\n' +
'    at fork (node:child_process:169:10)\n' +
'    at ChildProcessWorker.initialize (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:141:45)\n' +
'    at new ChildProcessWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:132:10)\n' +
'    at WorkerPool.createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:44:12)\n' +
'    at new BaseWorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/base/BaseWorkerPool.js:135:27)\n' +
'    at new WorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:30:1)\n' +
'    at new Worker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/index.js:167:26)\n' +
'    at createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:15:28)\n' +
'    at new Worker1 (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:21:9)\n' +
'    at /codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:432:31\n' +
'    at async Span.traceAsyncFn (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/telemetry/trace/trace.js:60:20)\n' +
'    at async Object.build [as default] (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:77:25) {\n' +
'  errno: -12,\n' +
"  code: 'ENOMEM',\n" +
"  syscall: 'spawn'\n" +
'}',
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
[G
2023-08-10T16:47:33.927Z [ERROR]: [?25h[G[J
300s › darxjey0xrl5c › Error: Command failed with exit code 1: node_modules/.bin/next build
Expected behavior
my nextjs project which contains sentry error tracking build should not fail.
Reproduction steps
after deploying my nextjs sentry project on aws amplify build getting failed.
Code Snippet
// Put your code below this line.
**next.config.js File**
```javascript
const { withSentryConfig } = require("@sentry/nextjs");
const nextConfig = {
  ...nextConfigurations
  productionBrowserSourceMaps: true,
  sentry:{
    widenClientFileUpload: true,
    transpileClientSDK: true,
    hideSourceMaps: true,
    disableLogger: true,
  }
};

const sentryWebpackPluginOptions = {
  org: process.env.NEXT_PUBLIC_SENTRY_ORG_NAME,
  project: process.env.NEXT_PUBLIC_SENTRY_PROJECT_NAME,
  authToken: process.env.NEXT_PUBLIC_SENTRY_AUTH_TOKEN,
  sourceMapFilename: '[name].[hash].js.map',
  silent: true,
};

module.exports = withSentryConfig(nextConfig, sentryWebpackPluginOptions);

sentry.client.config.js

import * as Sentry from "@sentry/nextjs";
import { ContextLines } from "@sentry/integrations";

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  tracesSampleRate: 0.2,
  replaysSessionSampleRate: 0.1,
  replaysOnErrorSampleRate: 0.1,
  integrations: [
    new Sentry.Replay(),
    new ContextLines({
      frameContextLines: 7,
    }),
  ],
});

app.js
 Sentry.init({
        dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
        integrations: [
          new BrowserTracing()
        ],
        tracesSampleRate: 0.2,
      });

So this setup works well for me in locally when i build locally sourcemap getting uploaded to my sentry dashboard and also i get proper stack starce but when i try to deploy on aws amplify my build is failing and getting below error
'> Build error occurred\n' +
                                  'Error: spawn ENOMEM\n' +
                                  '    at ChildProcess.spawn (node:internal/child_process:420:11)\n' +
                                  '    at spawn (node:child_process:733:9)\n' +
                                  '    at fork (node:child_process:169:10)\n' +
                                  '    at ChildProcessWorker.initialize (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:141:45)\n' +
                                  '    at new ChildProcessWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:132:10)\n' +
                                  '    at WorkerPool.createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:44:12)\n' +
                                  '    at new BaseWorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/base/BaseWorkerPool.js:135:27)\n' +
                                  '    at new WorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:30:1)\n' +
                                  '    at new Worker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/index.js:167:26)\n' +
                                  '    at createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:15:28)\n' +
                                  '    at new Worker1 (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:21:9)\n' +
                                  '    at /codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:432:31\n' +
                                  '    at async Span.traceAsyncFn (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/telemetry/trace/trace.js:60:20)\n' +
                                  '    at async Object.build [as default] (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:77:25) {\n' +
                                  '  errno: -12,\n' +
                                  "  code: 'ENOMEM',\n" +
                                  "  syscall: 'spawn'\n" +
                                  '}',
                                  failed: true,
                                  timedOut: false,
                                  isCanceled: false,
                                  killed: false
                                  }
                                  [G
2023-08-10T16:47:33.927Z [ERROR]: [?25h[G[J
                                  300s › darxjey0xrl5c › Error: Command failed with exit code 1: node_modules/.bin/next build

I am not getting why I am getting this problem only when i deploy it on aws amplify locally everything working fine.

### Log output

<details>

// Put your logs below this line

Build error occurred
Error: spawn ENOMEM
at ChildProcess.spawn (node:internal/child_process:420:11)
at spawn (node:child_process:733:9)
at fork (node:child_process:169:10)
at ChildProcessWorker.initialize (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:141:45)
at new ChildProcessWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:132:10)
at WorkerPool.createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:44:12)
at new BaseWorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/base/BaseWorkerPool.js:135:27)
at new WorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:30:1)
at new Worker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/index.js:167:26)
at createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:15:28)
at new Worker1 (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:21:9)
at /codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:432:31
at async Span.traceAsyncFn (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/telemetry/trace/trace.js:60:20)
at async Object.build [as default] (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:77:25) {
errno: -12,
code: 'ENOMEM',
syscall: 'spawn'
}
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info  - Checking validity of types...
info  - Creating an optimized production build...
info  - Using external babel configuration from /codebuild/output/src489982623/src/...-nextjs/.babelrc
info  - Collecting page data...
at makeError (/root/.//node_modules/execa/lib/error.js:60:11)
at handlePromise (/root/.//node_modules/execa/index.js:118:26)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Builder.build (/root/.//node_modules/@sls-next/lambda-at-edge/dist/build.js:377:13)
at async NextjsComponent.build (/root/.//node_modules/@sls-next/-component/dist/component.js:165:13)
at async NextjsComponent.default (/root/.//node_modules/@sls-next/-component/dist/component.js:22:13)
at async fn (/root/.npm/_npx/780a6c1398234b48/node_modules/@/template/utils.js:280:41)
at async Promise.all (index 0)
at async executeGraph (/root/.npm/_npx/780a6c1398234b48/node_modules/@/template/utils.js:294:3)
at async Template.default (/root/.npm/_npx/780a6c1398234b48/node_modules/@/template/.js:67:38)
at async Object.runComponents (/root/.npm/_npx/780a6c1398234b48/node_modules/@/cli/src/index.js:222:17) {
shortMessage: 'Command failed with exit code 1: node_modules/.bin/next build',
command: 'node_modules/.bin/next build',
escapedCommand: '"node_modules/.bin/next" build',
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: 'info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5\n' +
'info  - Checking validity of types...\n' +
'info  - Creating an optimized production build...\n' +
'info  - Using external babel configuration from /codebuild/output/src489982623/src/...-nextjs/.babelrc\n' +
'info  - Collecting page data...',
stderr: '\n' +
'warn - As of Tailwind CSS v2.2, lightBlue has been renamed to sky.\n' +
'warn - Update your configuration file to silence this warning.\n' +
'\n' +
'warn - As of Tailwind CSS v3.0, warmGray has been renamed to stone.\n' +
'warn - Update your configuration file to silence this warning.\n' +
'\n' +
'warn - As of Tailwind CSS v3.0, trueGray has been renamed to neutral.\n' +
'warn - Update your configuration file to silence this warning.\n' +
'\n' +
'warn - As of Tailwind CSS v3.0, coolGray has been renamed to gray.\n' +
'warn - Update your configuration file to silence this warning.\n' +
'\n' +
'warn - As of Tailwind CSS v3.0, blueGray has been renamed to slate.\n' +
'warn - Update your configuration file to silence this warning.\n' +
'(node:4289) [DEP_WEBPACK_CHUNK_HAS_ENTRY_MODULE] DeprecationWarning: Chunk.hasEntryModule: Use new ChunkGraph API\n' +
'(Use node --trace-deprecation ... to show where the warning was created)\n' +
'(node:4289) [DEP_WEBPACK_CHUNK_ADD_MODULE] DeprecationWarning: Chunk.addModule: Use new ChunkGraph API\n' +
'warn  - Compiled with warnings\n' +
'\n' +
'./components/dashB/FooterDashboard.js\n' +
"Attempted import error: 'support_id' is not exported from '../../constants' (imported as 'support_id').\n" +
'\n' +
'./node_modules/typescript/lib/typescript.js\n' +
"Module not found: Can't resolve 'perf_hooks' in '/codebuild/output/src489982623/src/...-nextjs/node_modules/typescript/lib'\n" +
'\n' +
'./node_modules/typescript/lib/typescript.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/typescript/lib/typescript.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/engine.io-client/node_modules/ws/lib/buffer-util.js\n' +
"Module not found: Can't resolve 'bufferutil' in '/codebuild/output/src489982623/src/...-nextjs/node_modules/engine.io-client/node_modules/ws/lib'\n" +
'\n' +
'./node_modules/engine.io-client/node_modules/ws/lib/validation.js\n' +
"Module not found: Can't resolve 'utf-8-validate' in '/codebuild/output/src489982623/src/...-nextjs/node_modules/engine.io-client/node_modules/ws/lib'\n" +
'\n' +
'./components/dashB/FooterDashboard.js\n' +
"Attempted import error: 'support_id' is not exported from '../../constants' (imported as 'support_id').\n" +
'\n' +
'./node_modules/next/dist/server/load-components.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/next/dist/server/load-components.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/next/dist/server/load-components.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/next/dist/server/require.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/next/dist/server/require.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/next/dist/server/require.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/typescript/lib/typescript.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'./node_modules/typescript/lib/typescript.js\n' +
'Critical dependency: the request of a dependency is an expression\n' +
'\n' +
'\n' +
'> Build error occurred\n' +
'Error: spawn ENOMEM\n' +
'    at ChildProcess.spawn (node:internal/child_process:420:11)\n' +
'    at spawn (node:child_process:733:9)\n' +
'    at fork (node:child_process:169:10)\n' +
'    at ChildProcessWorker.initialize (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:141:45)\n' +
'    at new ChildProcessWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/workers/ChildProcessWorker.js:132:10)\n' +
'    at WorkerPool.createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:44:12)\n' +
'    at new BaseWorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/base/BaseWorkerPool.js:135:27)\n' +
'    at new WorkerPool (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/WorkerPool.js:30:1)\n' +
'    at new Worker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/node_modules/jest-worker/build/index.js:167:26)\n' +
'    at createWorker (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:15:28)\n' +
'    at new Worker1 (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/lib/worker.js:21:9)\n' +
'    at /codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:432:31\n' +
'    at async Span.traceAsyncFn (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/telemetry/trace/trace.js:60:20)\n' +
'    at async Object.build [as default] (/codebuild/output/src489982623/src/...-nextjs/node_modules/next/dist/build/index.js:77:25) {\n' +
'  errno: -12,\n' +
"  code: 'ENOMEM',\n" +
"  syscall: 'spawn'\n" +
'}',

</details>

### aws-exports.js

_No response_

### Manual configuration

_No response_

### Additional configuration

_No response_

### Mobile Device

_No response_

### Mobile Operating System

_No response_

### Mobile Browser

_No response_

### Mobile Browser Version

_No response_

### Additional information and screenshots

_No response_

@cwomack ok but can you share me url where you shared this issue ? how caan i see there

@gauravsapkal1 Did you find any solution to this issue?


text:
BUG: SSG Build failed : Failed to find the deploy-manifest.json file in the build output

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature
Deployments
Is your feature request related to a problem? Please describe:
Building SSG next js site gives build error
Describe how you'd like this feature to work
https://github.com/aws-amplify/amplify-hosting/issues/3853
Getting the same error for nextjs SSG deployment :
2024-01-10T10:41:58.716Z [INFO]: ## Completed Frontend Build
2024-01-10T10:41:58.721Z [INFO]: ## Build completed successfully
2024-01-10T10:41:58.722Z [INFO]: # Starting caching...
2024-01-10T10:41:58.732Z [INFO]: # Creating cache artifact...
2024-01-10T10:42:33.446Z [INFO]: # Created cache artifact
2024-01-10T10:42:33.544Z [INFO]: # Uploading cache artifact...
2024-01-10T10:42:37.786Z [INFO]: # Uploaded cache artifact
2024-01-10T10:42:37.881Z [INFO]: # Caching completed
2024-01-10T10:42:37.891Z [ERROR]: !!! CustomerError: Failed to find the deploy-manifest.json file in the build output. Please verify that it exists within the "baseDirectory" specified in your buildSpec. If it's not there, we will also check the .amplify-hosting directory as a fallback. When using a framework adapter for hosting on Amplify, double-check that the adapter settings are correct.
2024-01-10T10:42:37.892Z [INFO]: # Starting environment caching...
2024-01-10T10:42:37.893Z [INFO]: # Environment caching completed
Terminating logging...

This is actually a bug but "bug" option was not there when clicked on "New Issue"

@jitendra-koodo 👋 This repository only accepts new feature requests for AWS Amplify Hosting. For technical support, we encourage you to open a case with AWS technical support if you have AWS support plan. If you do not have an active AWS support plan, we encourage you to leverage our Amplify community Discord server where community members and staff try to help each other with Amplify.

Where are we supposed to report the bugs?

They don't actually care @jitendra-koodo. They do what they want. They lie about ISR and its still included in there docs like it works exactly as vercels infrastructure but it does not. There customer service at AWS web service's is a joke, they just want to upgrade you to premium by ticking you off with their lack of expertise in the first tier support.

Hi @jitendra-koodo 👋 , if you have an AWS support plan we encourage you to report bugs by creating a support case. If you do not have an active AWS support plan, we encourage you to leverage our community Discord server where you can ask questions by creating a new thread in the amplify-help channel and community members and staff will try to answer your queries.

source: gharchive/issue

authors: Jay2113 PythonCircuit arundna jitendra-koodo

repo: aws-amplify/amplify-hosting

license_type: permissive

license_source: github-api


text:
@auth: API_KEY is Supported or not

we have Postgres database and we have selected authentication as API_KEY. and API type is GRAPHQL
Thanks in advanced.

Hi @vishaldroisys can you explain your use case in more detail? Are you trying to make a call directly to the Postgres database or through APIGateway or AppSync with data resolvers?

Closing due to inactivity. Feel free to re-open if you're still experiencing the same issue.

authors: drochetti lawmicha vishaldroisys

repo: aws-amplify/amplify-ios


text:
Attempt to fix circle ci builds for API

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This PR only targets api -- working on datastore ut test in a separate PR

LGTM! Can probably combine this with https://github.com/aws-amplify/amplify-ios/pull/282

source: gharchive/pull-request


text:
❗❗Liveness: Camera preview not centered on screen (Fixed in version 1.0.2)

Which UI component?
Liveness
Describe the bug
Upgrading Material3 UI (androidx.compose.material3:material3) from 1.0.1 to version 1.1.0, caused an issue where the camera preview was top aligned to the screen during the liveness challenge, instead of center aligned. This results in the camera preview not aligning to the face oval.
Impacted Amplify UI Liveness Versions:

1.0.0 (Only if the customer upgraded the androidx.compose.material3:material3 dependency to 1.1.0+)
1.0.1

As a workaround for these versions, you can force downgrade the material3 lib by adding the snippet below to the app build.gradle.
configurations.all {
    resolutionStrategy {
        force('androidx.compose.material3:material3:1.0.1')
    }
}

Amplify UI Liveness 1.0.2 includes a fix to ensure the camera is properly centered on the screen, and is able to render correctly with 'androidx.compose.material3:material3:1.1.0' or later.

Closing, notification has been given.

authors: tjleing tylerjroach

repo: aws-amplify/amplify-ui-android


text:
WS1004

CloudFormation Lint Version
cfn-lint 0.86.0
What operating system are you using?
WSL2 Ubuntu on Windows
Describe the bug
cfn-lint incorrectly reports:

[cfn-lint] WS1004: Lambda function xxx does not have a corresponding log group with a Retention property

When there is a !Ref to a log group with a retention property.
Expected behavior
When there is an explicit !Ref to a defined log group with the RetentionInDays property set then WS1004 should not be flagged.
Reproduction template
AWSTemplateFormatVersion: "2010-09-09"
Transform: AWS::Serverless-2016-10-31

Resources:

  LambdaProxyFunction:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: src/
      FunctionName: MyFunction
      Handler: index.handler
      LoggingConfig:
        LogFormat: JSON
        LogGroup: !Ref LambdaProxyLogGroup
      MemorySize: 512
      PackageType: Zip
      ReservedConcurrentExecutions: 1
      Runtime: nodejs18.x
      Timeout: 10
      Tracing: Active

  LambdaProxyLogGroup:
    DeletionPolicy: Retain
    UpdateReplacePolicy: Retain
    Type: AWS::Logs::LogGroup
    Properties:
      LogGroupClass: STANDARD
      RetentionInDays: 180

cfn-lint itself does not vend WS1004. Seems to be from this popular rule pack:
https://awslabs.github.io/serverless-rules/rules/
https://github.com/awslabs/serverless-rules/issues

authors: PatMyron shawnbucholtz

repo: aws-cloudformation/cfn-lint


text:
Since 1.3.0 Update Template Takes 30+ Minutes or fails to finish linting (redux of old issue #2874)

CloudFormation Lint Version
1.3.0
What operating system are you using?
Windows/AWS Serverless
Describe the bug
An issue that was previously fixed has cropped back up. Below is a copy/paste from the last ticket on this matter but the symptoms exhibited are the exact same and on our previous version 0.80.1 it was working fine.  The more conditions are in this particular template the longer the amount of time it takes to execute as well. It seems exponential as the first condition is instantaneous and subsequent ones are longer and longer.
A template that used to lint in 1.5 seconds now doesn't complete or completes in around 30 minutes.
This is an issue that was previously fixed in #2874
Expected behavior
To complete linting in a reasonable time frame for supported configurations and properly lint the values inside the conditions. In this case I would prefer under 1 minute of execution but in versions of cfn-lint before 0.76.0 it completes in about 1.5 seconds and properly lints the values inside of the conditions.
Reproduction template
#CORP::EC2::EC2::MODULE
AWSTemplateFormatVersion: 2010-09-09
Parameters:
name:
Description: The name tag for the EC2 instance.
Type: String
Default: ""
imageId:
Description: Base AMI for the EC2 instance.
Type: AWS::EC2::Image::Id
Default: ""
instanceType:
Description: EC2 instance type.
Type: String
Default: r5.large
subnetId:
Description: The ID of the subnet to launch the instance into.
Type: String
Default: ""
osVolumeSize:
Description: Size of the volume that has the OS.
Type: Number
Default: 120
securityGroupIds:
Description: The IDs of the security groups.
Type: ListAWS::EC2::SecurityGroup::Id
Default: ""
instanceKeyName:
Type: String
Description: Key pair name
Default: kpnamegoeshere
ebsOptimized:
Type: String
Description: Indicates whether the instance is optimized for Amazon EBS I/O.
Default: false
numberOfAdditionalVolumes:
Description: Additional volumes in addition to OS volume. Max is 25.
Type: Number
MaxValue: 25
Default: 0
volume2Size:
Description: Size of volume 2
Type: Number
Default: 40
volume3Size:
Description: Size of volume 3
Type: Number
Default: 40
volume4Size:
Description: Size of volume 4
Type: Number
Default: 40
volume5Size:
Description: Size of volume 5
Type: Number
Default: 40
volume6Size:
Description: Size of volume 6
Type: Number
Default: 40
volume7Size:
Description: Size of volume 7
Type: Number
Default: 40
volume8Size:
Description: Size of volume 8
Type: Number
Default: 40
volume9Size:
Description: Size of volume 9
Type: Number
Default: 40
volume10Size:
Description: Size of volume 10
Type: Number
Default: 40
volume11Size:
Description: Size of volume 11
Type: Number
Default: 40
volume12Size:
Description: Size of volume 12
Type: Number
Default: 40
volume13Size:
Description: Size of volume 13
Type: Number
Default: 40
volume14Size:
Description: Size of volume 14
Type: Number
Default: 40
volume15Size:
Description: Size of volume 15
Type: Number
Default: 40
volume16Size:
Description: Size of volume 16
Type: Number
Default: 40
volume17Size:
Description: Size of volume 17
Type: Number
Default: 40
volume18Size:
Description: Size of volume 18
Type: Number
Default: 40
volume19Size:
Description: Size of volume 19
Type: Number
Default: 40
volume20Size:
Description: Size of volume 20
Type: Number
Default: 40
volume21Size:
Description: Size of volume 21
Type: Number
Default: 40
volume22Size:
Description: Size of volume 22
Type: Number
Default: 40
volume23Size:
Description: Size of volume 23
Type: Number
Default: 40
volume24Size:
Description: Size of volume 24
Type: Number
Default: 40
volume25Size:
Description: Size of volume 25
Type: Number
Default: 40
volume26Size:
Description: Size of volume 26
Type: Number
Default: 40
Conditions:
hasVolume26: !Equals
- !Ref numberOfAdditionalVolumes
- 25
hasVolume25: !Or
- Condition: hasVolume26
- !Equals
- !Ref numberOfAdditionalVolumes
- 24
hasVolume24: !Or
- Condition: hasVolume25
- !Equals
- !Ref numberOfAdditionalVolumes
- 23
hasVolume23: !Or
- Condition: hasVolume24
- !Equals
- !Ref numberOfAdditionalVolumes
- 22
hasVolume22: !Or
- Condition: hasVolume23
- !Equals
- !Ref numberOfAdditionalVolumes
- 21
hasVolume21: !Or
- Condition: hasVolume22
- !Equals
- !Ref numberOfAdditionalVolumes
- 20
hasVolume20: !Or
- Condition: hasVolume21
- !Equals
- !Ref numberOfAdditionalVolumes
- 19
hasVolume19: !Or
- Condition: hasVolume20
- !Equals
- !Ref numberOfAdditionalVolumes
- 18
hasVolume18: !Or
- Condition: hasVolume19
- !Equals
- !Ref numberOfAdditionalVolumes
- 17
hasVolume17: !Or
- Condition: hasVolume18
- !Equals
- !Ref numberOfAdditionalVolumes
- 16
hasVolume16: !Or
- Condition: hasVolume17
- !Equals
- !Ref numberOfAdditionalVolumes
- 15
hasVolume15: !Or
- Condition: hasVolume16
- !Equals
- !Ref numberOfAdditionalVolumes
- 14
hasVolume14: !Or
- Condition: hasVolume15
- !Equals
- !Ref numberOfAdditionalVolumes
- 13
hasVolume13: !Or
- Condition: hasVolume14
- !Equals
- !Ref numberOfAdditionalVolumes
- 12
hasVolume12: !Or
- Condition: hasVolume13
- !Equals
- !Ref numberOfAdditionalVolumes
- 11
hasVolume11: !Or
- Condition: hasVolume12
- !Equals
- !Ref numberOfAdditionalVolumes
- 10
hasVolume10: !Or
- Condition: hasVolume11
- !Equals
- !Ref numberOfAdditionalVolumes
- 9
hasVolume9: !Or
- Condition: hasVolume10
- !Equals
- !Ref numberOfAdditionalVolumes
- 8
hasVolume8: !Or
- Condition: hasVolume9
- !Equals
- !Ref numberOfAdditionalVolumes
- 7
hasVolume7: !Or
- Condition: hasVolume8
- !Equals
- !Ref numberOfAdditionalVolumes
- 6
hasVolume6: !Or
- Condition: hasVolume7
- !Equals
- !Ref numberOfAdditionalVolumes
- 5
hasVolume5: !Or
- Condition: hasVolume6
- !Equals
- !Ref numberOfAdditionalVolumes
- 4
hasVolume4: !Or
- Condition: hasVolume5
- !Equals
- !Ref numberOfAdditionalVolumes
- 3
hasVolume3: !Or
- Condition: hasVolume4
- !Equals
- !Ref numberOfAdditionalVolumes
- 2
hasVolume2: !Or
- Condition: hasVolume3
- !Equals
- !Ref numberOfAdditionalVolumes
- 1
Resources:
Instance:
Type: AWS::EC2::Instance
Properties:
DisableApiTermination: true
ImageId: !Ref imageId
InstanceType: !Ref instanceType
KeyName: !Ref instanceKeyName
IamInstanceProfile: ssmEc2DelegatedRole
Tenancy: default
SubnetId: !Ref subnetId
EbsOptimized: !Ref ebsOptimized
Tags:
- Key: Name
Value: !Ref name
SecurityGroupIds: !Ref securityGroupIds
BlockDeviceMappings:
- DeviceName: /dev/sda1
Ebs:
Encrypted: true
VolumeSize: !Ref osVolumeSize
VolumeType: gp3
- !If
- hasVolume2
- DeviceName: /dev/sdb
Ebs:
Encrypted: true
VolumeSize: !Ref volume2Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume3
- DeviceName: /dev/sdc
Ebs:
Encrypted: true
VolumeSize: !Ref volume3Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume4
- DeviceName: /dev/sdd
Ebs:
Encrypted: true
VolumeasdfSize: !Ref volume4Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume5
- DeviceName: /dev/sde
Ebs:
Encrypted: true
VolumeSize: !Ref volume5Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume6
- DeviceName: /dev/sdf
Ebs:
Encrypted: true
VolumeSize: !Ref volume6Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume7
- DeviceName: /dev/sdg
Ebs:
Encrypted: true
VolumeSize: !Ref volume7Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume8
- DeviceName: /dev/sdh
Ebs:
Encrypted: true
VolumeSize: !Ref volume8Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume9
- DeviceName: /dev/sdi
Ebs:
Encrypted: true
VolumeSize: !Ref volume9Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume10
- DeviceName: /dev/sdj
Ebs:
Encrypted: true
VolumeSize: !Ref volume10Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume11
- DeviceName: /dev/sdk
Ebs:
Encrypted: true
VolumeSize: !Ref volume11Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume12
- DeviceName: /dev/sdl
Ebs:
Encrypted: true
VolumeSize: !Ref volume12Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume13
- DeviceName: /dev/sdm
Ebs:
Encrypted: true
VolumeSize: !Ref volume13Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume14
- DeviceName: /dev/sdn
Ebs:
Encrypted: true
VolumeSize: !Ref volume14Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume15
- DeviceName: /dev/sdo
Ebs:
Encrypted: true
VolumeSize: !Ref volume15Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume16
- DeviceName: /dev/sdp
Ebs:
Encrypted: true
VolumeSize: !Ref volume16Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume17
- DeviceName: /dev/sdq
Ebs:
Encrypted: true
VolumeSize: !Ref volume17Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume18
- DeviceName: /dev/sdr
Ebs:
Encrypted: true
VolumeSize: !Ref volume18Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume19
- DeviceName: /dev/sds
Ebs:
Encrypted: true
VolumeSize: !Ref volume19Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume20
- DeviceName: /dev/sdt
Ebs:
Encrypted: true
VolumeSize: !Ref volume20Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume21
- DeviceName: /dev/sdu
Ebs:
Encrypted: true
VolumeasdfSize: !Ref volume21Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume22
- DeviceName: /dev/sdv
Ebs:
Encrypted: true
VolumeSize: !Ref volume22Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume23
- DeviceName: /dev/sdw
Ebs:
Encrypted: true
VolumeSize: !Ref volume23Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume24
- DeviceName: /dev/sdx
Ebs:
Encrypted: true
VolumeSize: !Ref volume24Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume25
- DeviceName: /dev/sdy
Ebs:
Encrypted: true
VolumeSize: !Ref volume25Size
VolumeType: gp3
- !Ref 'AWS::NoValue'
- !If
- hasVolume26
- DeviceName: /dev/sdz
Ebs:
Encrypted: true
VolumeSize: !Ref volume26Size
VolumeType: gp3
- !Ref 'AWS::NoValue'

I see this has been merged and after running 1.3.2 I can confirm it indeed does finish linting in a very fast time.
Thank you so much for your continued support on this.


text:
Auto-generate controllers when new runtime released

Regenerate all service controllers to runtime v0.13.0 and code-gen v0.13.0 to include recent bug fixes.

Now up and running!


text:
apigatewayv2 - DomainNameConfigurations missing in DomainNameObservation

for apigatewayv2 in DomainNameObservation struct - DomainNameConfigurations struct is missing
https://github.com/aws/aws-sdk-go/blob/v1.37.10/service/apigatewayv2/api.go#L12137-L12158
at the moment:
type DomainNameObservation struct {
	APIMappingSelectionExpression *string `json:"apiMappingSelectionExpression,omitempty"`

	DomainName *string `json:"domainName,omitempty"`
}

what we need:
type DomainNameObservation struct {
	APIMappingSelectionExpression *string `json:"apiMappingSelectionExpression,omitempty"`

	DomainName *string `json:"domainName,omitempty"`

        DomainNameConfigurations []*DomainNameConfiguration `json:"domainNameConfigurations,omitempty"`
}

we have one Issue in Crossplane Provider-AWS for this: https://github.com/crossplane/provider-aws/issues/826

Hi Thanks for pointing it out.
APIGatewayv2 controller is currently at aws-sdk-go v1.35.5 https://github.com/aws-controllers-k8s/apigatewayv2-controller/blob/main/apis/v1alpha1/ack-generate-metadata.yaml#L8
We are working on upgrading it but have some problems with how controller-gen handles maps of maps , which were introduced after v1.35.5

apigatewayv2 controller now updated to v1.37.10
https://github.com/aws-controllers-k8s/apigatewayv2-controller/blob/main/apis/v1alpha1/ack-generate-metadata.yaml#L8


text:
Updated submodules/lacework-control-tower-cfn.

Updated submodules/lacework-control-tower-cfn. Removed extraneous test parameters from lacework-control-tower-cfn cfn-abi-control-tower-integration.template.yaml.

/do-e2e-tests

@jefferyfry tests fail due to Issues with below resources from ControlTower submodule:

LaceworkAuthFunction
LaceworkSetupFunction
LaceworkAccountFunction

All 3 failed due to S3 permission or incorrect reference to the key.
Resource handler returned message: "Error occurred while GetObject. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist. (

@kkvinjam Added missing lambda zip files for ControlTower submodule.

authors: jefferyfry kkvinjam

repo: aws-ia/cfn-abi-lacework-polygraph


text:
Feature request: allow to pass custom logger for warning and debug logs

Use case
The Metrics utility emits some warning logs to notify customers that certain expected conditions are not being met. This is the case for when a namespace is not specified or when the publishStoredMetrics() method is called on an empty buffer.
Currently customers have no way of suppressing these warnings and some customers have reported wanting to do so (#2036). I think this is a fair ask and whatever implementation we settle for in this issue will also be reused for other utilities that emit either warnings or debug logs (Idempotency, Tracer, and Parameters).
Solution/User Experience
We could define a new type/interface in the commons package and expose it:
interface UtilityLogger {
  trace?: (...content: any[]) => void;
  debug: (...content: any[]) => void;
  info: (...content: any[]) => void;
  warn: (...content: any[]) => void;
  error: (...content: any[]) => void;
}

From there, customers can use it as a reference to create their own logger and pass it to the Metrics utility.
In the example below I'm making the warn method a no-op to disable the warnings entirely, but customers can write their own custom implementation to decide whether the logs are emitted or not.
import { Metrics } from '@aws-lambda-powertools/metrics';
import type { UtilityLogger } from '@aws-lambda-powertools/commons/types';

const myLogger: UtilityLogger = {
  debug: console.debug,
  info: console.info,
  warn: {}, // no-op - but customers can add their own logic
  error: console.error,
};

const metrics = new Metrics({
  namespace: 'serverlessAirline',
  serviceName: 'orders',
  logger: myLogger,
});

Customers should also be able to pass an instance of Powertools Logger if they wish to do so:
import { Metrics } from '@aws-lambda-powertools/metrics';
import { Logger } from '@aws-lambda-powertools/logger';

const logger = new Logger({
  serviceName: 'orders',
  logLevel: 'ERROR',
});

const metrics = new Metrics({
  namespace: 'serverlessAirline',
  serviceName: 'orders',
  logger,
});

My main concern with this is avoiding confusion and conveying clearly that this is only a logger that will be used for debug and warning logs but not to emit the EMF metrics themselves.
The Metrics utility maintain its own Console object that logs the metrics using console.log (notice that the log() method is not part of the suggested interface). This is needed for the Metrics utility to work with the Advanced Logging Configuration feature.
Alternative solutions
If my memory serves me right the AWS Lambda Node.js managed runtime treats warning emitted via process.emitWarning(warning[, options]) as errors rendering this method unviable.
As part of this issue however we should still test this option just in case I'm wrong.
Other alternatives that I'm not inclined to consider would go along the lines of adding a doNotWarnOnEmptyMetrics option to suppress these warnings.
Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

@heitorlessa & @am29d would love your opinion on this and especially your point of view on the concern I share at the end of the "Solution/User Experience" section.
Also please let me know if anything is not clear, happy to clarify & expound on any detail. Thanks!


text:
Customer support Streamlit application with Guardrails

Issue #, if available:
#210
Description of changes:
Features:
CloudFormation Template:
    Defines a guardrail for the customer support chatbot.
    Filters out harmful content and protects sensitive information.
    Configures Content Policy, Sensitive Information Policy, Topic Policy, and Word Policy.

Python Scripts:
    deploy_guardrails_infra.sh: Bash script to deploy the CloudFormation stack and retrieve the guardrail identifier.
    streamlit_guardrails_app.py: Streamlit app to interact with the chatbot, using the guardrails set up in the CloudFormation stack.

Requirements:
    Added requirements.txt to install necessary Python packages, including Streamlit.

Documentation:
    Detailed README with step-by-step instructions to set up the environment, deploy the CloudFormation stack, and run the Streamlit app.
    Included links to relevant resources and documentation for further reference.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please re do this PR following the new layout and the process for creating the required file . We request all files to have a presence on the Cookbook / Recipes Website which is fronting this github repo now. Some of the mandatory sections of the notebook need to include

Overview.
What are we demonstrating .
What use case .
What will you learn.
What is the architectural pattern and why we select this. With a diagram
What are the libraries to install
What model did we choose and why this model
Every cell needs to have a markup

THIS PR needs to go to responsibleai / use-cases

authors: mccartni-aws rsgrewal-aws

repo: aws-samples/amazon-bedrock-samples


text:
Error: Security Constraints Not Satisfied!

❯ sam deploy --guided

Configuring SAM deploy
======================

        Looking for config file [samconfig.toml] :  Not found

        Setting default arguments for 'sam deploy'
        =========================================
        Stack Name [sam-app]: s3Uploader
        AWS Region [us-east-1]: us-east-2
        #Shows you resources changes to be deployed and require a 'Y' to initiate deploy
        Confirm changes before deploy [y/N]: Y
        #SAM needs permission to be able to create roles to connect to the resources in your template
        Allow SAM CLI IAM role creation [Y/n]: y
        #Preserves the state of previously provisioned resources when an operation fails
        Disable rollback [y/N]: y
        UploadRequestFunction has no authentication. Is this okay? [y/N]: n
Error: Security Constraints Not Satisfied!

It shouldn't be prompting me at all.


text:
CFN stack name as argument

seems like CFN stack name is must
Issue #, if available: Without the the CFN stack name Amplify frontend build is failing
Description of changes: Added CFN stack name as the argument to setup_config.py script.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @shankarr-code! Thank you for providing this contribution. I am going to close this PR as the issue addressed by this PR are fixed in #29. More specifically, #29 will default to using the broadcast-monitoring stack name when an argument is not provided. Additionally, it allows for an environment variable(with a custom stack name) to be defined for CI/CD builds.


text:
Embedded stack arn:aws:cloudformation

Hi Team,
We are deploying Compute optimiser dashboard, While running Cloud formation template on  Data Collection account getting below error :
Embedded stack arn:aws:cloudformation:ap-south-1:xxxxxx:stack/OptimizationDataCollectionStack1-ComputeOptimizerModule-xxxxxx was not successfully created: The following resource(s) failed to create: [ReplicaitonBucketsStackSet].
_Creating using the following stack
https://wellarchitectedlabs.com/cost/300_labs/300_optimization_data_collection/2_deploy_main_resources/_
Stack and Stackset created on Management ran successfully, without any issue.
Can you please suggest what can be the probable issue
Thanks
Shweta

can you check in the deleted stacks in cloud formation the stack that starts with "StackSet-"  and check the failure reason?
Most probably, you need to add another exception in your SCP
There are 2 roles involved:

https://github.com/awslabs/aws-well-architected-labs/blob/master/static/Cost/300_Optimization_Data_Collection/Code/module-compute-optimizer.yaml#L132
https://github.com/awslabs/aws-well-architected-labs/blob/master/static/Cost/300_Optimization_Data_Collection/Code/module-compute-optimizer.yaml#L86

Hello Shweta, were you able to allow these roles and deploy the stack?

Please comment / reopen if still an issue


text:
Relicense to MIT-0

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

(FP for missing NOTICE file deletion)

repo: aws-samples/aws-geotagging-logs


text:
Init container isn't started for webserver + TLS handshake error in secret-inject

Hi there!
I'm following instructions but getting only webserver container in my webserver-78578795c6-6l2mx pod
No init container is present there
In my secret-inject-87fd4b8bb-v6jvp pod logs I see http: TLS handshake error from 192.168.183.197:43904: remote error: tls: bad certificate exception on each webserver deploy attempt
Any ideas how to debug / fix it?

Hello,
That can typically occur when there is a cert mismatch between the admission controller and the mutating webhook configuration. I doubt if certs have expired (since they are valid for 3650 days). Is this a new clean-state deployment ? Verify that you dont have an existing secret named "secret-inject-tls" which was created as a part of previous Helm deployment.

I've just completed full k8s redeploy and still getting exactly the same.
Worse mentioning that other sample deploy that is using IAM OIDC, role and policy to reach S3 via Amazon EKS Pod Identity Webhook works just fine.
I have k8s v1.19, nodePool v1.19.6-20210302, CNI v1.7.9-eksbuild.1 if it matters

I have the same issue.
2021/03/11 00:13:02 http: TLS handshake error from ********: remote error: tls: bad certificate
2021/03/11 00:13:02 http: TLS handshake error from ********: remote error: tls: bad certificate

K8s details:
kubectl version --short
Client Version: v1.19.3
Server Version: v1.19.6-eks-49a6c0

@shashankbansal6 and @kagarlickij we're testing this against 1.19 now.  Perhaps something changed in that release.

I'm now also having this issue after upgrading to 1.19

I believe we need to add a SAN to the certificate.

@kagarlickij @shashankbansal6 This should be fixed.

@amit0701 Please can you confirm where you added the SAN? I dont see any commits to the repo and I'm using the multi-secret branch.

We're not actively maintaining that branch @themattkeating. You could ask @dnascimento if he has plans to update the certificate.

Unfortunately the master branch only supports a single secret, which is almost useless in the real world.
@jicowan If you could explain which certificate was updated, Im happy to do a PR for this multi-secret branch. I just wanted to know more about what the fix was.

The changes are in the gh-pages branch:
https://github.com/aws-samples/aws-secret-sidecar-injector/commits/gh-pages

repo: aws-samples/aws-secret-sidecar-injector


text:
fix(core): Fixing SSM-Document-Share

Fixing number of accountIds passing to ssm modify-document-permission
Fixing number of accounts passing to GuardDuty createMembers, updateMembers and deleteMembers
Adding security-hub-excl-regions and not enabling security hub in those regions

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can we add a parameter to disable security hub /guardduty/mach for an ou like sandbox/dev for cost optimizations

Can we add a parameter to disable security hub /guardduty/mach for an ou like sandbox/dev for cost optimizations

For SH, see both: #497 and #516, leaning to #497 as we've received similar feedback from other customers (also waiting to see what SH has for a roadmap).  GD is enabled using AWS Orgs for enablement so we don't have the capability to control per OU, unless GD adds the feature :-).  We do not have any plans to switch back to manual, per-account GD enablement.
I strongly discourage disabling GuardDuty in any OU or account and strongly believe it should be enabled across your entire AWS footprint.  If something bad happens in any account, including Sandbox, you still need to know.  GuardDuty is a cloud native/cloud aware Intrusion Detection Service.  Given Sandbox often has more freedoms and fewer security controls, the utilization of GD in Sandbox is even more important.  GD is one of the best tools to alert you that something unusual is occurring and allow you to act/remediate in the most timely manner.  For the meagre savings you will achieve, I strongly encourage cost optimizing elsewhere :-).
Love all the great feedback you've been providing!

authors: Brian969 naveenkoppula rverma-nsl


text:
Error: Failed to choose a D3D11 Adapter.

I looked at the logs, I saw this:
A D3D11-compatible GPU (Feature Level 11.0, Shader Model 5.0) is required to run the engine.
I think the default instance doesn't have a compatible GPU. I don't know how to proceed.

Thus, the build is not running. Please note the webserver does start:

What instance are you running?
I was using g4ad.xlarge. Even though it was not necessary I installed the vGaming drivers instead of workstation drivers that are default. That was only to get RTX, not necessary for streaming unless your project has RTX ON.

What instance are you running?
I was using g4ad.xlarge. Even though it was not necessary I installed the vGaming drivers instead of workstation drivers that are default. That was only to get RTX, not necessary for streaming unless your project has RTX ON.

What instance are you running?

I am using the default values of the CloudFormation template. So the instance is g4dn.xlarge.

I was using g4ad.xlarge. Even though it was not necessary I installed the vGaming drivers instead of workstation drivers that are default. That was only to get RTX, not necessary for streaming unless your project has RTX ON?
I remember getting similar errors when running RTX-stuff on the default instance.

Very interesting @sebrk. Can you tell me how to install those drivers? Maybe that'll help me solve my issue.
@kashman-amzn I think this shows a pattern with the default configuration. BTW, I am trying to deploy the pixel streaming demo, nothing special.

What instance are you running?

I am using the default values of the CloudFormation template. So the instance is g4dn.xlarge.

I was using g4ad.xlarge. Even though it was not necessary I installed the vGaming drivers instead of workstation drivers that are default. That was only to get RTX, not necessary for streaming unless your project has RTX ON?
I remember getting similar errors when running RTX-stuff on the default instance.

Very interesting @sebrk. Can you tell me how to install those drivers? Maybe that'll help me solve my issue.
@kashman-amzn I think this shows a pattern with the default configuration. BTW, I am trying to deploy the pixel streaming demo, nothing special.

Do you have RTX on?
instructions here: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver.html#nvidia-gaming-driver

Do you have RTX on?
instructions here: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver.html#nvidia-gaming-driver

@sebrk Amazing!, you fixed it! I am not sure if I required RTX or not but this was the solution. I followed the steps you linked until step 3 and that was enough. Do you know how to automate this process or put it in the CloudFormation template?

@sebrk Amazing!, you fixed it! I am not sure if I required RTX or not but this was the solution. I followed the steps you linked until step 3 and that was enough. Do you know how to automate this process or put it in the CloudFormation template?

@sebrk Amazing!, you fixed it! I am not sure if I required RTX or not but this was the solution. I followed the steps you linked until step 3 and that was enough. Do you know how to automate this process or put it in the CloudFormation template?

Great! You probably had a bad case of drivers from the start. I have not automated this but googling around should help you find information on it.

@sebrk Amazing!, you fixed it! I am not sure if I required RTX or not but this was the solution. I followed the steps you linked until step 3 and that was enough. Do you know how to automate this process or put it in the CloudFormation template?

Great! You probably had a bad case of drivers from the start. I have not automated this but googling around should help you find information on it.

@kashman-amzn could you modify the CloudFormation template to include the aforementioned drivers?

@kashman-amzn could you modify the CloudFormation template to include the aforementioned drivers?

Thank you for your collaboration on this issue and working through and identifying the need for the NVIDIA gaming driver. The GRID drivers are installed as part of the NICE DCV installation, and works for many UE4 projects but we will modify the CloudFormation to switch to the gaming driver. Again thanks for digging into this.

Thank you for your collaboration on this issue and working through and identifying the need for the NVIDIA gaming driver. The GRID drivers are installed as part of the NICE DCV installation, and works for many UE4 projects but we will modify the CloudFormation to switch to the gaming driver. Again thanks for digging into this.

Excellent @kashman-amzn!

Excellent @kashman-amzn!

@kashman-amzn thank you very much! When do you think we'll have the new CloudFormation?

@kashman-amzn thank you very much! When do you think we'll have the new CloudFormation?

@kashman-amzn I saw your recent commit. If I wanted to use the NVIDIA gaming driver what steps should I take to modify the CloudFormation template?

I am planning to get to this but it may not happen until next week. One way you can do this is to add a silent install of the latest NVIDIA EC2 gaming driver in the bootstrap script. You could also execute it in the CFn script by adding the file to the download items and executing the silent install. Documentation on NVIDIA driver installation can be found here: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver.html

I have added the installation of the .NET Framework and run the UE4PrereqSetup that is bundled with the build by the engine. This should ensure current and future dependencies are resolved before running the pixel streaming build. As far as the NVIDIA gaming driver, I have added a note on how to install that driver if desired, but with the prerequisite installed the Unreal Engine Pixel Streaming demo that failed before now succeeds and streams as expected at 60fps.

Hey @kashman-amzn, I used the latest scripts and I still get the same issue trying to deploy the pixel streaming demo. Are you sure you were able to deploy it?

I was able to deploy it by changing the DiskSize to 45GB.

That is great. I will be increasing the default storage value to 50GB so that larger sized projects will work by default.

authors: kashman-amzn sebrk yardenshoham


text:
Fix/claude 2.1 support image generation

JSON フォーマット自体はいずれのモデルでも出力しており、前後に余計な文言が出るケースがあるので、{ と } を検索し、その間だけを抜き出す処理を追加

別実装を検討する

repo: aws-samples/generative-ai-use-cases-jp


text:
Fix GraalVM build

Description of changes:
temp downgrade spring-data-commons due to https://github.com/spring-projects/spring-data-commons/issues/3025
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you for the PR, looks good!

Thank you! It worked here!

authors: deki jjeanjacques10 smoell

repo: aws-samples/java-on-aws


text:
updated workshop ami

Updated AWS AMI for Rancher v2.7.4 (release notes)
Tested and Verified comparability with the workshop

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Current workshop AMI (ami-08cdaea7883b8b88a) still exists and public until merge is approved, then will deprecate.

repo: aws-samples/rancher-on-aws-workshop

license: MIT


text:
RAPIDS.ai custom image example

Issue #, if available:
Description of changes:
Added a rapids.ai custom image example. Will be great for users to make use of a readymade image with https://rapids.ai/start.html
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing completed successfully:

Performed local testing as suggested in DEVELOPMENT.md
Performed testing on studio with two types of GPU instances -- g4dn and p3.8xl... Both currently work
Performed additional testing with RAPIDS example, importing various libraries like cuml and testing out the nvidia-smi command
used both docker build and push, as well as sm-docker from studio to create and test images with the same Dockerfile, followed by testing as updated in the rapids/README.md

Thanks for the contribution!


text:
feat: Update zk netplan render to handle docker bridge network interface

Problem: We have noticed when docker has a network interface the zookeeper netplan render is confused and can't correctly pick the ENI ifname. For example with the following network interfaces, the zookeeper_user_data will pick up both br-146bd07d2fbf and eth1 then render into /etc/netplan/99_config.yaml, and the netplan is broken.
ip -j link show | jq .
[
  {
    "ifindex": 3,
    "ifname": "br-146bd07d2fbf",
    "flags": [
      "NO-CARRIER",
      "BROADCAST",
      "MULTICAST",
      "UP"
    ],
    "mtu": 1500,
    "qdisc": "noqueue",
    "operstate": "DOWN",
    "linkmode": "DEFAULT",
    "group": "default",
    "link_type": "ether",
    "address": "02:42:01:07:1e:1c",
    "broadcast": "ff:ff:ff:ff:ff:ff"
  },
  {
    "ifindex": 4,
    "ifname": "eth1",
    "flags": [
      "BROADCAST",
      "MULTICAST"
    ],
    "mtu": 1500,
    "qdisc": "noop",
    "operstate": "DOWN",
    "linkmode": "DEFAULT",
    "group": "default",
    "txqlen": 1000,
    "link_type": "ether",
    "address": "0e:f1:0b:65:44:d3",
    "broadcast": "ff:ff:ff:ff:ff:ff"
  }
]

Solution: We are adding in additional filtering when finding the INTFERFACE_NAME, so it filter out any docker bridge network interface, which start with "br-".
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi Paul,
Thanks for the fix. Nice work. 👍


text:
Can't resolve 'amazon-cognito-auth-js'

This is happening on a regular create react app, not related to typescript like #39.

In package.json:
  "main": "lib/index.js",   "module": "es/index.js",
Are nowhere to be found in amazon-cognito-auth, so I used:
import { CognitoAuth } from 'amazon-cognito-auth-js/dist/amazon-cognito-auth';
To work around the incorrect values in package.json for now

Is your project using React structure?
If yes, this is the correct way to do: import { CognitoAuth } from 'amazon-cognito-auth-js/dist/amazon-cognito-auth';

Still encounter this error following the documentation. This issue should not be closed. If what you said is the right way to import, then please correct the documentation so that we do not waste time searching through all the past issues.

@jaxondu The documentation shows how to use SDK generally. For specific case such as using React structure,  import { CognitoAuth } from 'amazon-cognito-auth-js/dist/amazon-cognito-auth';
should be the correct way. And this is the common sense for importing when using React structure.

@yuntuowang Sorry I'm using VueJS. It is not common sense to have ES import in this manner. You must have export it wrongly.

Hi @jaxondu, I just updated the README.md for the ES modules import:
// ES Modules, e.g. transpiling with Babel
import {CognitoAuth} from 'amazon-cognito-auth-js/dist/amazon-cognito-auth';
If you have any other concerns, feel free to post here, thanks!

I have updated this workaround: import { CognitoAuth } from 'amazon-cognito-auth-js/dist/amazon-cognito-auth';  in our README.md.

which programming language is this
https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_ListUserPools.html
Can you point to any sample code which uses this?
I'm trying to use this in a lambda function.

@yuntuowang I have a problem in my Ionic+angular+typescript Mobile Project. I want to
import {CognitoAuth} from 'amazon-cognito-auth-js/dist/amazon-cognito-auth'

But it does not recognize it?

authors: deeperid engharb jaxondu sam-jg sunsoori yuntuowang

repo: aws/amazon-cognito-auth-js


text:
Projection Expression parsing bug

Hi, I am using Expression Builder to create the Expression for QueryInput. I noticed that Expression Builder Projection delimits with comma and space, eg. "#1, #2".
As a result, when there is more than 1 projection, the output is incorrect.
Below is an example of QueryOutput.Items
[         {             " #2": {                 "B": null,                 "BOOL": null,                 "BS": null,                 "L": null,                 "M": null,                 "N": null,                 "NS": null,                 "NULL": null,                 "S": "0f3028a2-ee87-447e-9a7a-ee2d94798934",                 "SS": null             },             "ID": {                 "B": null,                 "BOOL": null,                 "BS": null,                 "L": null,                 "M": null,                 "N": null,                 "NS": null,                 "NULL": null,                 "S": "9bbef19476623ca56c17da75fd57734dbf82530686043a6e491c6d71befe8f6e",                 "SS": null             }         }     ]
The value of expr.Names() is {         "#0": "RepoID",         "#1": "ID",         "#2": "TokenID"     }
The value of expr.Projection() is #1, #2
The same Expression Builder works without DAX.
Edit: A workaround I am currently using is to specify ProjectionExpression without using Expression Builder

This will be fixed in the next release

authors: anandsas darylnwk

repo: aws/aws-dax-go


text:
Use the SDK with C++ Builder

Hi,
I'm trying to use the sdk in my project in C++ builder (Embarcadero C++ builder 10.3).
I tried to create a new project in C++ builder and create exactly the same structure of the current SDK directory there. But I got never-ending issues.
Is there any other way to do this?
Any help/guidance appreciated.
Thank you

I'd need to see build logs to know what specific issues you're talking about and give advice.
Since you're just getting started on your project, I'd suggest that you pick up the new aws-iot-device-sdk-cpp-v2 instead of this SDK. The V2 SDK is where AWS will be putting its development and support efforts going forward.

authors: Preemali graebm

repo: aws/aws-iot-device-sdk-cpp


text:
Create release

Hi there,
Is there a standard periodic release process for this package or are releases initiated manually by the maintainers?
I had a PR merged in https://github.com/aws/aws-lambda-go/issues/452 which I'd like to use. I see the last release was created 18 days ago.
Looking at the history it doesn't seem like there's a regular cadence, could you please create a release so that the above changes can be used?

done! https://github.com/aws/aws-lambda-go/releases/tag/v1.33.0

Much appreciated.

repo: aws/aws-lambda-go


text:
local runner container has python2.7 environment not 3.7

local runner cannot found my constraints so I tried debugging, I found local runner container has python 2.7 env not 3.7
$ docker exec -it e177d2495fd0 /bin/bash
[airflow@e177d2495fd0 ~]$ python
Python 2.7.18 (default, May 25 2022, 14:30:51)
[GCC 7.3.1 20180712 (Red Hat 7.3.1-15)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', '/usr/lib/python27.zip', '/usr/lib64/python2.7', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7/site-packages', '/usr/lib/python2.7/site-packages']
>>>

You need to run python3 not python to access version 3.7.10 (which airflow is using).

@killingtime-sc perfect. thx

authors: Haebuk killingtime-sc

repo: aws/aws-mwaa-local-runner


text:
Is it possible to change the version?

I want to test it on mwaa 2.6.3.
Now, 2.7.2 is the default setting, so I would like to lower the version being checked.

There are tags you can check out.
git checkout v2.6.3

@erg   Thank you so much ! mr.erg!   it's really helpful  for me!! haha

I'll add this in the README as it might not be clear. Closing this issue


text:
Updating selectedItems in Table component does not update

Describe the bug
I am using the aws-northstar Table component. I am trying to update the selected items in the table based on some state that is being controlled outside of the table component. When I update the selected state, I can see it is updated, however the table component ignores it and does not update the selected checkbox items in the table.
Note: if I swap the aws-northstar Table component for the @cloudscape-design/components Table component, it works fine.
Versions
@aws-northstar/ui v1.1.13
To Reproduce
CodeSandbox link to reproduce the problem
Steps to reproduce the behavior
See CodeSandbox example.
Steps to reproduce:

Click on checkbox items inside the table. The "selectedItems" state updates successfully.
Click on the test button.

Expected behaviour
Clicking on test button should override the selectedItems state and select the 3rd component in the table.
Actual behaviour
The React state for "selectedItems" is updated successfully, however the Table component ignores it and keeps the current selection.
Additional context
Using the @cloudscape-design/components Table works as expected. Swap the "Table" component in the imports in the CodeSandbox to see the difference in behavior.

Hi @adriantadros Thanks for reporting the bug.
Northstar's V2 Table component leverages Cloudscape's Collection hooks on handling the selectedItems updates. The input selectedItems will be passed to the defaultSelectedItems of the hooks params: Items selected on the initial render. The items are matched by trackBy if defined and by reference otherwise.
It will not updated with the props change after the initial rendering.
Sorry for the confusion. We will update the docs to reflect that.

authors: adriantadros jessieweiyi

repo: aws/aws-northstar


text:
feat: Add Popover component

Issue #, if available: https://github.com/aws/aws-northstar/issues/66
Description of changes: Added a Popover component that can be used to display some content on top of another.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

:tada: This PR is included in version 1.0.32 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: abrenaut cogwirrel


text:
IoT Core MQTT with SQS and .NET Framework 4.8 intermittently drops payload attribute

Describe the bug
When ingesting MQTT under load to a single device, where the device sends a message, then the server sends a message over and over, and an SQS payload topic rule is used:
SELECT * as payload, topic() as topic, traceid() as traceId, clientId() as clientId, principal() as principalId, sourceip() as ipAddress FROM 'device/+/mo/#'
Where the .NET Framework CDK is used to read SQS messages, an intermittent SQS message is received without a payload attribute as shown here:
Body: {
"topic": "device/NT-00999/mo/data/38",
"traceId": "3e090b84-30a8-2b9d-e8b5-9163864624dd",
"clientId": "NT-00999",
"principalId": "981307f9ed56b5ebede3f576ac86b027dba5517f8f5eec4e2a7a3d7cd9cc6ce5",
"ipAddress": "207.189.176.142"
}
A similar problem was originally observed when using a base64 MQTT payload, where the payload delivered would intermittently have the \n as the starting character of the payload and be missing a trailing length character.  From here, I switched back to JSON payloads, where the symptom seems to be a complete loss of the payload attribute.
Expected Behavior
The payload attribute should be present and correct with all packets, as it is with most packets.
Current Behavior
The payload attribute is dropped when parsing incoming messages here and as shown in the log snipit above:
    var client = m_sqsClient;

    var request = new ReceiveMessageRequest
    {
      QueueUrl = queueUrl,
      AttributeNames = attributeNames,
      MaxNumberOfMessages = maxNumberOfMessages,
      VisibilityTimeout = visibilityTimeout,
      WaitTimeSeconds = waitTimeSeconds,
    };

    while (true)
    {
      var response = await client.ReceiveMessageAsync(request);

      if (response.Messages.Count > 0)
      {

Reproduction Steps
Using .NET Framework 8, with AWSSDK version 3.7.400.1 (and previous versions).  Client 1 sends a publish to topic A, at which time client 2 sends a response to topic B, and client 1 sends a response to topic C.  From here, there are back to back messages that include client 2 sending a message on topic B and client 1 sending a response to topic C.  After around 30-40 messages, the SQS message received via the .NET SDK is missing the payload attribute.
IoT Payload Rule:
SELECT * as payload, topic() as topic, traceid() as traceId, clientId() as clientId, principal() as principalId, sourceip() as ipAddress FROM 'device/+/mo/#'
delivered SQS message:
Body: {
"topic": "device/NT-00999/mo/data/38",
"traceId": "3e090b84-30a8-2b9d-e8b5-9163864624dd",
"clientId": "NT-00999",
"principalId": "981307f9ed56b5ebede3f576ac86b027dba5517f8f5eec4e2a7a3d7cd9cc6ce5",
"ipAddress": "207.189.176.142"
}
Additionally, and separate, when using a base64 payload, sending a single message from client 2 on topic B results in a malformed base64 encoded payload with the rule:
SELECT encode(*, 'base64') as payload, topic() as topic, traceid() as traceId, clientId() as clientId, principal() as principalId, sourceip() as ipAddress FROM 'device/+/mo/#'
Here, the payload starts with a '\n' character and is missing a trailing length character delimiter.
Possible Solution
Assuming a race condition is present in the IoT Core rule processing, or more likely, on the .NET client SDK receiving the SQS message.
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK 3.7.400.1
Targeted .NET Platform
.NET Framework 4.8
Operating System and version
Windows 11 Pro

If the SQS message is not deleted, upon re-delivery, it also is missing the payload block again.

@nfvelado Good afternoon. Could you please share the following:

Complete minimal reproducible code, rather than a code snippet. The snippet you shared is just a basic code form receiving SQS messages.
List of all packages used in your project, specifically IoT Core MQTT
Was the issue happening earlier or started happening after package upgrade? If yes, please share the list of packages used before and after the error started happening.
Logs, if any.

Thanks,
Ashish

Hi Ashish, thanks for the quick response.  Issue was happening before and after the SDK upgrade.
I meant .NET Framework SDK, not CDK above.
Query above is set as an IoT Core message routing payload rule that forwards to an SQS queue.  Please close for the time being, until I can find a way to reproduce more consistently with a better trace.  Thanks,
Nick

authors: ashishdhingra nfvelado

repo: aws/aws-sdk-net


text:
Renaming account profile throws error

Describe the bug
Opening AWS Explorer in Visual Studio and trying to edit one of the existing profile's name results in an Object reference not set to an instance of an object error, as seen in the screenshot below. The profile name is however successfully renamed, it's only that one has to close and reopen Visual Studio in order to view the change.
To Reproduce

Open AWS Explorer from Visual Studio's View menu
Select a profile and click the "Edit Profile" icon
Change the profile name to something else
Enter the account number and click "Ok"

Expected behavior
The profile to be renamed silently.
Screenshots

Computer (please complete the following information):

Windows Version: Windows 10 1909
Visual Studio Version: 16.5.0 Preview 5
AWS Toolkit for Visual Studio Version: 1.18.1.0

Thank you for reporting this @luckerby - I can confirm that I was able to reproduce this for a basic shared credentials profile (not a .NET Credentials profile)

This issue has been addressed in more recent versions of the Toolkit (I believe version 1.21.0.0 and newer).

authors: awschristou luckerby

repo: aws/aws-toolkit-visual-studio


text:
SerializationError: failed decoding REST JSON error response

I'm running AWS X-Ray daemon version 3.0.0 on my Windows 7 machine with the following options...
./xray_windows.exe -o -n us-east-1 -l debug
... and see SerializationErrors such as the following during idle periods.
2019-02-22T13:38:03-05:00 [Debug] Failed to send telemetry 1 record(s). Re-queue records. SerializationError: failed decoding REST JSON error response
caused by: invalid character '<' looking for beginning of value
2019-02-22T13:39:04-05:00 [Debug] Send 2 telemetry record(s)
2019-02-22T13:40:04-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:41:04-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:42:04-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:43:04-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:44:04-05:00 [Debug] Failed to send telemetry 1 record(s). Re-queue records. SerializationError: failed decoding REST JSON error response
caused by: invalid character '<' looking for beginning of value
2019-02-22T13:45:04-05:00 [Debug] Send 2 telemetry record(s)
2019-02-22T13:46:04-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:47:04-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:48:05-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:49:05-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:50:05-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:51:05-05:00 [Debug] Failed to send telemetry 1 record(s). Re-queue records. SerializationError: failed decoding REST JSON error response
caused by: invalid character '<' looking for beginning of value
2019-02-22T13:52:05-05:00 [Debug] Send 2 telemetry record(s)
2019-02-22T13:53:05-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:54:05-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:55:06-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:56:06-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:57:06-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:58:06-05:00 [Debug] Send 1 telemetry record(s)
2019-02-22T13:59:06-05:00 [Debug] Failed to send telemetry 1 record(s). Re-queue records. SerializationError: failed decoding REST JSON error response
caused by: invalid character '<' looking for beginning of value
2019-02-22T14:00:06-05:00 [Debug] Failed to send telemetry 2 record(s). Re-queue records. SerializationError: failed decoding REST JSON error response
caused by: invalid character '<' looking for beginning of value
2019-02-22T14:01:06-05:00 [Debug] Send 3 telemetry record(s)

Oddly enough, this doesn't seem to interfere with tracing. Is there some way to get more information?! Is this something that I should not worry about (since it's a debug message)?

Hi @tmuldoon ,
Thank for posting the issue. The above debug message wont affect the daemon's ability to send X-Ray traces. The daemon send's telemetry records to X-Ray service to notify daemon health. From the above logs, the telemetry record receiving error are sent in the following interval. Example Send 3 telemetry record(s).
X-Ray daemon uses aws-go-sdk version 1.14.1.
I checked the git repo for aws-go-sdk and found that similar issue is present in the latest version of the aws-go-sdk : issue.
I will work with AWS GO SDK team to understand the scenario. Please stay tuned.
Thanks,
Yogi

I am experiencing the same error in the x-ray daemon log. Coincidentally no traces  in X-Ray console, so seems like the problem affects x-ray monitoring.

Hi @dagb ,
Can you help me understand the application environment, X-Ray SDK you are using and confirm the traces generated by the app are sent to X-Ray daemon address. By default the X-Ray SDK sends traces at UDP localhost:2000 and the daemon also listens on the same address. The above issue happens only when the daemon is ideal (not receiving any traces for longer time) and ideally shouldn't affect tracing abilities.
Thanks,
Yogi

Both the emitting app and X-Ray daemon runs in ECS. I have built the X-Ray daemon docker image with https://s3.dualstack.eu-west-1.amazonaws.com/aws-xray-assets.eu-west-1/xray-daemon/aws-xray-daemon-linux-3.x.zip
Port config of the X-Ray daemon container:
ENTRYPOINT ["/usr/bin/xray", "-b", "0.0.0.0:2000", "-t", "0.0.0.0:2000", "-n", "eu-west-1", "-o", "-l", "debug"]
EXPOSE 2000/udp
EXPOSE 2000/tcp
The emitting app has
AWS_XRAY_DAEMON_ADDRESS=x-ray.local:2000
This was working for almost 4 days, the suddenly started to log errors (debug level), and no traces in the X-Ray console.
Will it help to restart the X-Ray container as a short term mitigation?

In addition I want to add that there is a test environment (different AWS account) using the same X-Ray daemon docker image. No errors and traces appears in the console.

Hi @dagb ,
Thank you for letting me know the setup. There hasn't  been any daemon update recently. From the description, the traces were sent almost for 4 days and suddenly no traces appeared in the X-Ray console.
One possibility is the DNS address of the X-Ray daemon "x-ray.local:2000" might have changed but this is not reflected on the SDK UDP emitter. Can you check the X-Ray SDK logs to check you see any errors? We have a feature request in the backlog for the JAVA SDK to periodically resolve the hostname. This is more of a SDK issue and not related to this daemon issue.
One solution I think is to restart X-Ray container so the X-Ray SDK resolves the DNS for the daemon address and the segments are received by the X-Ray Daemon.
Please feel free to open an issue if you still face the problem on JAVA SDK so we can do  fast followup.
Thanks,
Yogi

Hi @yogiraj07 ,
My bad: this was caused by subnet (mis)configuration in ECS. I'm still a bit puzzled why it worked and stopped working, but at least I got to clean up some mess.
Thank for your feedback and directions.

The original concern in this issue has been resolved with the AWS SDK for Go v1.19.34
Resolving this issue to clear up some clutter. I have opened a new issue for tracking the ocassional UnmarshalError when calling PutTelemetryRecord.

authors: dagb srprash tmuldoon yogiraj07

repo: aws/aws-xray-daemon


text:
Adding unit test for feature operations

Unit test for each feature on for feature operations.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@59e7c24). Click here to learn what that means.
The diff coverage is 65.58%.

@@            Coverage Diff            @@
##             master      #20   +/-   ##
=========================================
  Coverage          ?   49.45%
=========================================
  Files             ?       47
  Lines             ?     3114
  Branches          ?      469
=========================================
  Hits              ?     1540
  Misses            ?     1309
  Partials          ?      265

Impacted Files
Coverage Δ

lib/feature-operations/scripts/user-files-ops.js
92.1% <100%> (ø)

lib/feature-operations/scripts/hosting-ops.js
88.88% <100%> (ø)

lib/feature-operations/scripts/analytics-ops.js
94.87% <100%> (ø)

lib/feature-operations/scripts/lib/mh-yaml-lib.js
53.55% <14.28%> (ø)

lib/feature-operations/scripts/cloud-api-ops.js
67.01% <75%> (ø)

...ture-operations/scripts/lib/function-generation.js
8.43% <8.43%> (ø)

lib/feature-operations/scripts/user-signin-ops.js
83.82% <84.84%> (ø)

lib/feature-operations/scripts/database-ops.js
78.04% <88.42%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 59e7c24...537a144. Read the comment docs.

authors: codecov-io elorzafe

repo: aws/awsmobile-cli


text:
Update CHECKSUMS

Issue #, if available:
#1132
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

repo: aws/eks-anywhere-build-tooling


text:
Sets compute type for arm code build instances

Issue #, if available:
Description of changes:
In the staging build we default to the giant instance type for amd which does not exist for arm. We have to specifically set the arm compute type to the normal large.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/cherrypick release-0.14

/cherrypick release-0.14

authors: abhay-krishna jaxesn


text:
Pin kustomize version to v4.5.7

Kustomize released a new version v5.0.0 today which caused some issues in generating manifests, specifically setting creationTimestamp to "null" (with quotes). So pinning to an older version to avoid this.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test etcdadm-bootstrap-provider-tooling-presubmit

/cherrypick release-0.14


text:
Support dev release image builds from prod image-builder

This feature was added in #2312 but inadvertently removed in the refactor done in #2361.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/cherrypick release-0.16

/cherrypick release-0.17


text:
Fix typo

Issue #, if available:
Description of changes:
Fix typo
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve
/cherrypick release-0.9

authors: jaxesn mdsgabriel

repo: aws/eks-anywhere


text:
Make tinkerbell airgapped tests to dynamically reserve hardware

Issue #, if available:
Add dynamic hardware reservation logic to be extended to airgapped tinkerbell tests.
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


text:
Skip snow e2e tests

Issue #, if available:
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/cherrypick release-0.19


text:
Add CCM patches 1.28-1.30

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve

repo: aws/eks-distro


text:
add yaml struct tags for generated golang structs

:rocket: Feature Request
Affected Languages

[ ] TypeScript or Javascript
[ ] Python
[ ] Java
[ ] .NET (C#, F#, ...)
[x] Go

General Information

JSII Version: 1.46.0

Platform:     N/A

[x] I may be able to implement this feature request

[ ] This feature might incur a breaking change

Description
In Go, JSII generates structs with json struct tags :
type ProviderConfig struct {
    Data *string `json:"data"`
}

It would be nice to have yaml struct tags too. While marshaling/unmarshaling this would help.
Proposed Solution
type ProviderConfig struct {
    Data *string `json:"data" yaml:"data"`
}

Notes
If you could point me to the file which does this I may be able to write a PR.

I see no problem with this, but I'm wondering what your use case is? The JSON struct tags are generated to help marshaling/demarshalling as JSII types are serialized to JSON when passed to the kernel via stdin, and deserialized when received from the kernel via stdout.
Generally the struct tags aren't meant to be seen by consumers of generated JSII Go modules and are an implementation detail, though there may be some uses I'm not considering.

Generally the struct tags aren't meant to be seen by consumers of generated JSII Go modules and are an implementation detail, though there may be some uses I'm not considering.

When we create a construct library in cdk8s using TS, since the generated structs in golang only have JSON struct tags, I cannot use those structs to marshal YAML data into it.
Lets look at an interface:
export interface CustomInterface {
    readonly config: Config;
}

export interface Config {
    readonly containerName: string;
    readonly containerImage: string
}

The generated structs for this would be :
type struct CustomInterface {
    Config Config `json:"config"`
}

type struct Config {
    ContainerName string `json:"containerName"`
    ContainerImage string `json:"containerImage"`
}

The application I'm building marshalls data into the CustomInterface struct from a YAML config which would look like this for our CustomInterface:
config:
  containerName: test
  containerImage: test-image:latest

Then it takes those values and then creates a new container definition in cdk8s.
podSpec := &k8s.PodSpec{
    Containers: &[]*k8s.Container{
        {
            Name:  jsii.String(config.containerName),
            Image: jsii.String(config.containerImage),
        },
    },
}

Sort of like helm without the madness : )
The problem here is that the camelCase is not being respected by the Marshaller, thats why yaml struct tags are necessary. I hope I was able to convey my use case.

gotcha, so your application accepts some yaml configuration loaded and deserialized and passed as args to cdk8s constructs? Seems straightforward enough and I don't see any downside to enabling easier yaml deserialization. 👍🏻

gotcha, so your application accepts some yaml configuration loaded and deserialized and passed as args to cdk8s constructs?

yep you nailed it.

authors: Hunter-Thompson MrArnoldPalmer

repo: aws/jsii


text:
CRD troubleshooting guide needs updating for Beta CRDs

Description
How can the docs be improved?
https://karpenter.sh/docs/troubleshooting/#helm-error-when-installing-the-karpenter-crd-chart
The CRD's in the examples in the troubleshooting guide are the Alpha names.
This guide should be updated to have the Beta (ec2nodeclasses/etc) crd names instead, for fast copy/paste troubleshooting.

example 1 becomes:
kubectl label crd ec2nodeclasses.karpenter.k8s.aws nodepools.karpenter.sh nodeclaims.karpenter.sh app.kubernetes.io/managed-by=Helm --overwrite

example 2 becomes:
kubectl annotate crd ec2nodeclasses.karpenter.k8s.aws nodepools.karpenter.sh nodeclaims.karpenter.sh meta.helm.sh/release-name=karpenter-crd --overwrite
kubectl annotate crd aec2nodeclasses.karpenter.k8s.aws nodepools.karpenter.sh nodeclaims.karpenter.sh meta.helm.sh/release-namespace=karpenter --overwrite

@jsamuel1 Would you be interested in opening a PR to make this change?

repo: aws/karpenter-provider-aws


text:
Use NodeRepair featureGate

Description
How can the docs be improved?
Hello,
I try to use the featureGate NodeRepair, this is correctly enable on my controller pod (FEATURE_GATES: SpotToSpotConsolidation=false,NodeRepair=true), but that doesn't work like I've expected.
We just need to enable the feature gate for work ? I pretty sure we need to wait 30min before the node was considerate as unready but I don't find any documentation on this point.
Also it's look on node object or nodeclaims.karpenter.sh ? Because my node is ready but not my node claim:
╰─➤ k get node ip-10-34-6-212.eu-west-3.compute.internal
NAME                                        STATUS   ROLES    AGE    VERSION
ip-10-34-6-212.eu-west-3.compute.internal   Ready    <none>   129m   v1.30.6-eks-94953ac

╰─➤ k get nodeclaims.karpenter.sh std-linux-cpu-h4g4s
NAME                  TYPE          CAPACITY   ZONE         NODE                                        READY     AGE
std-linux-cpu-h4g4s   m7i.8xlarge   spot       eu-west-3a   ip-10-34-6-212.eu-west-3.compute.internal   Unknown   129m

Regards,

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

The node repair feature works by looking at the node readiness. Karpenter only act against nodes that are not ready for 30 min. The nodeclaim being unknown is a known bug that are planning on pushing to fix. The issue there is the status of how karpenter is marking the status rather then any issue with the nodeclaim

Hello,
With 1.1.1 I've still have Unknown if my node still have the statupTaint
╰─➤ k get nodeclaims.karpenter.sh std-linux-core-pnpgb
NAME                   TYPE         CAPACITY   ZONE         NODE                                         READY     AGE
std-linux-core-pnpgb   t3a.medium   spot       eu-west-3a   ip-10-157-24-78.eu-west-3.compute.internal   Unknown   55m

╰─➤ k get node ip-10-157-24-61.eu-west-3.compute.internal
NAME                                         STATUS   ROLES    AGE    VERSION
ip-10-157-24-61.eu-west-3.compute.internal   Ready    <none>   4d8h   v1.30.6-eks-94953ac

╰─➤ kubectl get nodes ip-10-157-24-61.eu-west-3.compute.internal -o json | jq '.spec.taints | length'
1

The node repair feature works by looking at the node readiness

So they have no possibility to automatically destroy the nodeclaim if it's not at True ?


text:
fix: add missing DELETE method for validating webhook

Fixes #
Description
Minor fix for validation.webhook.karpenter.k8s.aws webhook.
It seems like DELETE method for karpenter.k8s.aws group was removed in #2754.
I see no reason for the deletion, and think it was a mistake.
How was this change tested?

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I don't see the usecase for validating delete requests. Can't remember, but probably why I removed it. Does this break something?

I don't see the usecase for validating delete requests. Can't remember, but probably why I removed it. Does this break something?

I am currently running two EKS clusters with karpenter.
I used helm to install karpenter, but directly installed it using helm cli on one cluster and argocd installed on the another.
On both clusters, deployed webhooks have DELETE method unlike the template. It is fine on cluster where I used helm cli, but on cluster with argocd it seems argocd is constantly re-syncing the webhook. This makes karpenter pods emit reconcile errors every few second and no node is spawned.
I still don't understand why deployed webhooks get DELETE method back again, but so far I believe this PR could fix current problem.

I think this is due to knative's webhook reconciliation behavior. Fix SGTM

authors: ellistarn skdltmxn

repo: aws/karpenter


text:
Getting client certification with rustls mTLS

Security issue notifications
Not a security issue
Problem:
This is more of a question but is there a way in s2n-quic to get the client certificate from the connection that was accepted? I'd like to extract some information from the certificate of the client that the server accepted but I can't find a way to do it. Now I'm using a channel and sending that info to a receiver that the server polls when a new connection has been accepted. That seems very fragile as I can't ascertain whether the next value in the channel is associated with the connection that was accepted (but that may be true anyway).
Is it possible to somehow get access to client's TLS certificate after a connection has been received?

There's currently not an API for this, unfortunately. I think the best solution would be to wire up an event to the TLS provider that emits the client's certificate. You would then handle that event and store it on the connection's event context. This value can then be queried by the application using the Connection::query_event_context function.

Any plan on it?

authors: altonen camshaft thynson


text:
Pod not starting with EKS v20230825

What happened:
When running a pod with a private image with a ruby/rails application we got the following error message on start :
Last State: Terminated
  Reason: StartError
  Message: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start
      container process: exec: "rails": cannot run executable found relative to current directory: unknown
   Exit Code: 128
   Started: Thu, 01 Jan 1970 01:00:00 +0100
   Finished: Wed, 30 Aug 2023 16:55:15 +0200

We notice some strange things :

unknown current working dir
Started at epoch 0

Our image define a PATH environment variable to add a relative path like ENV PATH=bin:$PATH (and WORKDIR is also correctly set on out docker image).
Adding .spec.workingDir on pod definition doesn’t change the behavior.
What you expected to happen:
To run a pod normally without any error.
The same pod definition run perfectly on v1.26.6-eks-a5565ad.
How to reproduce it (as minimally and precisely as possible):
Run the same pod definition on v1.26.7-eks-8ccc7ba  / ami-0c8f13e2e3c8de829 node.
Anything else we need to know?:
Environment:

AWS Region: eu-west-3
Instance Type(s): Spot - with karpenter with the following constraints :

    requirements:
    - key: topology.kubernetes.io/zone
      operator: In
      values:
      - eu-west-3a
      - eu-west-3b
      - eu-west-3c
    - key: kubernetes.io/arch
      operator: In
      values:
      - amd64
    - key: karpenter.k8s.aws/instance-size
      operator: NotIn
      values:
      - nano
      - micro
      - small
      - medium
      - large
      - xlarge
      - metal
    - key: karpenter.k8s.aws/instance-category
      operator: In
      values:
      - m
      - r
      - c
    - key: karpenter.sh/capacity-type
      operator: In
      values:
      - spot
      - on-demand
    - key: kubernetes.io/os
      operator: In
      values:
      - linux

EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion): eks.5
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.26
AMI Version: AMI Release v20230825
Kernel (e.g. uname -a): 5.10.186-179.751.amzn2.x86_64
Release information (run cat /etc/eks/release on a node):

BASE_AMI_ID="ami-0f2b325398f933a81"
BUILD_TIME="Fri Aug 25 20:12:27 UTC 2023"
BUILD_KERNEL="5.10.186-179.751.amzn2.x86_64"
ARCH="x86_64"

This looks related to a restriction introduced in go 1.19 os.Exec that executables in the PWD have to be referenced with “./“: https://tip.golang.org/doc/go1.19#os-exec-path
Does that fix your issue?

The latest release contains a runc that was compiled with a newer version of golang (1.20.x), to address some CVE's that weren't going to be fixed in 1.18.x. That's where the behavior change is coming from.

AMI release
runc
go

v20230816
1.1.7-1.amzn2
1.18.6

v20230825
1.1.7-3.amzn2
1.20.7

GODEBUG=execerrdot=0 is how you get back older behavior until you can fix things. There's some deeper details in https://github.com/golang/proposal/blob/master/design/56986-godebug.md as well.

runc and containerd are Amazon Linux 2 packages, so https://alas.aws.amazon.com/alas2.html

go version $FILE will give you the version of go used to build $FILE as well 👍

Hi,
Sorry, I was OoO.
I confirm that comes from GO security update.
Simply replace : ENV PATH=bin:$PATH to ENV PATH=/my/absolute/path/bin:$PATH fix the issue.
Cheers

authors: cartermckinnon dims jBouyoud

repo: awslabs/amazon-eks-ami