Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adds layers to function #1835

Merged
merged 21 commits into from
Oct 9, 2024
Merged

adds layers to function #1835

merged 21 commits into from
Oct 9, 2024

Conversation

ykethan
Copy link
Member

@ykethan ykethan commented Aug 8, 2024

Problem

Issue number, if available:
RFC: #1549

Changes

adds ability to reference Lambda layers and attach to a function.
Can attach up to 5 layers on a function. Auto sets the layer keys as external modules on the function.

example:

resource.ts

import { defineFunction } from "@aws-amplify/backend";

export const sayHello = defineFunction({
  name: "say-hello1",
  entry: "./handler.ts",
  layers: {
   "@aws-lambda-powertools/logger":
      "arn:aws:lambda:us-east-1:094274105915:layer:AWSLambdaPowertoolsTypeScriptV2:11",
  },
});

handler.ts. keep using your dependancy without having to use /opt as the NODE_PATH would point to /opt: https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime

import { Logger } from "@aws-lambda-powertools/logger";

const logger = new Logger({ serviceName: "serverlessAirline" });

export const handler = async (): Promise<void> => {
  logger.info("Hello World");
};

Validation

Checklist

  • If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
  • If this PR requires a change to the Project Architecture README, I have included that update in this PR.
  • If this PR requires a docs update, I have linked to that docs PR above.
  • If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

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

@ykethan ykethan requested a review from a team as a code owner August 8, 2024 14:56
Copy link

changeset-bot bot commented Aug 8, 2024

🦋 Changeset detected

Latest commit: 9f80bfe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@aws-amplify/backend-function Minor
@aws-amplify/backend Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Comment on lines 127 to 139
/**
* Attach Lambda layers to a function
* @example
* import { referenceFunctionLayer } from "@aws-amplify/backend";
*
* layers: {
* myModule: referenceFunctionLayer("arn:aws:lambda:<current-region>:<account-id>:layer:myLayer:1")
* },
*
* The object is keyed by the module name hosted on your existing layer and a value that references to an existing layer using an ARN. The keys will be externalized and available via your layer at runtime
* Maximum of 5 layers can be attached to a function. Layers must be in the same region as the function.
*/
layers?: FunctionLayerReferences;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need referenceFunctionLayer ?

Can't we just

layers: {
   myModule: "arn:aws:lambda:<current-region>:<account-id>:layer:myLayer:1"
},

and have construct/factory validate and resolve necessary pieces inside ?

Copy link
Member Author

@ykethan ykethan Aug 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was built according to the RFC requirements
#1549

@ykethan ykethan requested a review from a team as a code owner August 8, 2024 23:27
@ykethan ykethan requested a review from sobolk August 9, 2024 21:45
@ykethan ykethan changed the title adds referenceLayer to function adds layers to function Aug 14, 2024

/**
* Attach Lambda layers to a function
* - The object is keyed by the module name hosted on your existing layer and a value that references to an existing layer using an ARN. The keys will be externalized and available via your layer at runtime
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this "module name hosted on your existing layer" mean? Do customers need to do something?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated the jsdoc to be more verbose

Comment on lines 284 to 286
type HydratedFunctionProps = Required<FunctionProps> & {
layers: FunctionLayerReferences;
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need this? Wouldn't layers be automatically be present and required in HydratedFunctionProps

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed this

Comment on lines 300 to 304
const resolvedLayers = resolveLayers(
this.props.layers,
scope,
this.props.name
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be part of hydrateDefaults?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the layers requires the scope for the fromLayerVersionArn to convert to a ILayer.

Comment on lines 9 to 18
export const arnPattern = new RegExp(
'^(arn:(aws[a-zA-Z-]*)?:lambda:[a-z]{2}((-gov)|(-iso([a-z]?)))?-[a-z]+-\\d{1}:\\d{12}:layer:[a-zA-Z0-9-_]+:[0-9]+)|(arn:[a-zA-Z0-9-]+:lambda:::awslayer:[a-zA-Z0-9-_]+)$'
);

/**
* Checks if the provided ARN is valid.
*/
export const isValidLayerArn = (arn: string): boolean => {
return arnPattern.test(arn);
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need these methods exported or used outside of this file? If not, can we bring them into the class as privates.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

separated the logic and added them as private.

Comment on lines 9 to 11
export const arnPattern = new RegExp(
'^(arn:(aws[a-zA-Z-]*)?:lambda:[a-z]{2}((-gov)|(-iso([a-z]?)))?-[a-z]+-\\d{1}:\\d{12}:layer:[a-zA-Z0-9-_]+:[0-9]+)|(arn:[a-zA-Z0-9-]+:lambda:::awslayer:[a-zA-Z0-9-_]+)$'
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add the source of this ARN in the documentation.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got this regex from CFN error, but modified this now to be similar to the docs now and linked the documentation.

Comment on lines 70 to 72
return new Set<FunctionLayerArn>(
Array.from(uniqueArns).map(parseFunctionLayerArn)
);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the method is called validate it shouldn't do anything else but validate what it's supposed to do. This parsing/mapping shouldn't be part of it.

/**
* Class to represent and handle Lambda Layer ARNs.
*/
export class FunctionLayerArn {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need a class to represent the arn? It seems like it's just doing validation.

Recommendation: Create a class FunctionLayerParser/FunctionLayerReferenceAdapter (or something like that) with one public method parse/adapt that takes in the user input, i.e. Record<String, String> and does several validations and finally produces ILayerVersion[]

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

recreated this as a FunctionLayerParser class with parse as suggested

Comment on lines 24 to 25
// @public (undocumented)
export type FunctionLayerReferences = Record<string, string>;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're not inventing anything to constrain this to ARN we should inline this type and rely on jsdocs.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'@aws-amplify/backend': minor
---

adds referenceLayer to function
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this and some code comments don't seem to be accurate now.

'@aws-amplify/backend-function': minor
---

adds layers to defineFunction
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
adds layers to defineFunction
adds support to reference existing layers in defineFunction

Comment on lines 25 to 36
const uniqueArns = new Set<string>(Object.values(layers));
this.validateLayerCount(uniqueArns);

for (const [key, arn] of Object.entries(layers)) {
if (!this.isValidLayerArn(arn)) {
throw new AmplifyUserError('InvalidLayerArnFormatError', {
message: `Invalid ARN format for layer: ${arn}`,
resolution: `Update the layer ARN with the expected format: arn:aws:lambda:<current-region>:<account-id>:layer:<layer-name>:<version> for function: ${functionName}`,
});
}
validLayers[key] = arn;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are validating on the count of uniqueArns not the number of entries in the map. But later we are not deduping it later on. So for example if I provide a map of

{
  key1: arn1,
  key2: arn1,
  key3: arn1,
  key4: arn1,
  key5: arn1,
  key6: arn1,
}

our validation will succeed, but we will be passing/creating 6 reference layers to the NodeJSFunction constructor which may fail later.

Ideally we should dedupe here on the ARN and provide any of the key here since the key is only used for generating the name of the layer.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops thanks for the catch, updated this and also added a test to ensure unique Arn's are passed.

@ykethan ykethan requested a review from Amplifiyer August 28, 2024 17:28
Comment on lines 24 to 37
const uniqueArns = new Map<string, string>();

for (const [key, arn] of Object.entries(layers)) {
if (!this.isValidLayerArn(arn)) {
throw new AmplifyUserError('InvalidLayerArnFormatError', {
message: `Invalid ARN format for layer: ${arn}`,
resolution: `Update the layer ARN with the expected format: arn:aws:lambda:<current-region>:<account-id>:layer:<layer-name>:<version> for function: ${functionName}`,
});
}
// Add ARN to the Map with the first encountered key
if (!uniqueArns.has(arn)) {
uniqueArns.set(arn, key);
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can simplify this a bit by using just a Set instead of Map and build your validLayers directly in this method.

@ykethan ykethan requested a review from Amplifiyer August 28, 2024 18:49
Amplifiyer
Amplifiyer previously approved these changes Aug 28, 2024
@ykethan ykethan requested a review from Amplifiyer October 2, 2024 21:07
@sobolk sobolk merged commit f5d0ab4 into aws-amplify:main Oct 9, 2024
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants