Skip to content

Conversation

@chloe1818
Copy link
Contributor

Issue #, if available:
N/A

Description of changes:
These are the initial project files being added to the repository.

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

Config Outdated
Copy link
Contributor

Choose a reason for hiding this comment

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

This Config file is only used for internal Amazon packages, so we shouldn't have it here

Comment on lines +39 to +49
- uses: actions/checkout@v3

- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v2
with:
role-to-assume: arn:aws:iam::123456789012:role/GitHubActionRole
- name: Deploy Lambda function
uses: aws-actions/amazon-lambda-deploy@v1
with:
function-name: my-lambda-function
code-artifacts-dir: ./dist
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we have a build step in the example so that a user is not required to build and commit the build artifacts for things to work?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was thinking about that, but realized that different runtimes have different build steps.

code-artifacts-dir: ./dist
```

To use OIDC authentication, you must configure a trust policy in AWS IAM that allows GitHub Actions to assume an IAM role. Here's an example trust policy:
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there some docs of the configure-aws-credentials that we could link to in our README when it comes to setting up credentials?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

node_module directory should be excluded via .gitignore

Copy link
Contributor

Choose a reason for hiding this comment

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

It looks like .gitignore was excluded from this change. We should be ignoring directories like node_modules and coverage.

e.g. https://github.com/aws-actions/amazon-ecs-deploy-task-definition/blob/master/.gitignore

@chloe1818 chloe1818 force-pushed the initial branch 2 times, most recently from 3baf077 to 79929a4 Compare July 29, 2025 22:43
Copy link
Contributor Author

@chloe1818 chloe1818 left a comment

Choose a reason for hiding this comment

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

Updated initial files

@chloe1818 chloe1818 changed the title Add initial project files build: Add initial project files Jul 29, 2025
@chloe1818 chloe1818 changed the title build: Add initial project files Add initial project files Jul 29, 2025
@greyshi
Copy link
Contributor

greyshi commented Jul 29, 2025

Looks like these checks require the repo to be public in order to run properly. Besides this the changes look good.

@chloe1818 chloe1818 merged commit 23208dd into main Jul 29, 2025
3 of 7 checks passed
chloe1818 added a commit that referenced this pull request Jul 30, 2025
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.

2 participants