From faf4ff070d27b0a23f743f0b21e05062deb6e1b9 Mon Sep 17 00:00:00 2001 From: Tim Colson Date: Mon, 13 Nov 2023 17:45:11 -0700 Subject: [PATCH] Replace 'arch64' with 'arm64' TIL that the architecture is actually **AArch64** - not 'arch64' but that arm64 is a synonym and is what 'arch' returns on an Apple Silicon mac. https://en.wikipedia.org/wiki/AArch64 Fortunately, this change makes the Lambda architecture choice of 'arm64' easier since it matches. Nice! --- .../function-sample-aws-native/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-cloud-function-samples/function-sample-aws-native/README.md b/spring-cloud-function-samples/function-sample-aws-native/README.md index 4f3eb926f..1804097aa 100644 --- a/spring-cloud-function-samples/function-sample-aws-native/README.md +++ b/spring-cloud-function-samples/function-sample-aws-native/README.md @@ -16,7 +16,7 @@ public Function uppercase() { > Note: If your function takes a Spring Message as an input parameter (e.g., Function), the Lambda Context object will be available in the message header `aws-context`. See [AWSLambdaUtils.java](https://github.com/spring-cloud/spring-cloud-function/blob/main/spring-cloud-function-adapters/spring-cloud-function-adapter-aws/src/main/java/org/springframework/cloud/function/adapter/aws/AWSLambdaUtils.java#L67C44-L67C55) for details. -## To run the sample on macOS (Apple silicon arch64) +## To build the sample on macOS (Apple silicon arm64) You first need to build the function, then you will deploy it to AWS Lambda.