Skip to content

CD AWS FAQs: fixed typos, curly quotes #11820

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.

Sign up for GitHub

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

Open
stephen-w-pracy wants to merge 1 commit into
base: main
Choose a base branch
from
Open

CD AWS FAQs: fixed typos, curly quotes #11820

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/continuous-delivery/deploy-srv-diff-platforms/aws/aws-deployment-faqs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ sidebar_position: 100

This article addresses some frequently asked questions about AWS deployments in Harness.

### Where does Harness publish it's images for AWS SAM Build and Deploy?
### Where does Harness publish its images for AWS SAM Build and Deploy?

- We publish these images in Harness' DockerHub Registry for user's to reference in their SAM Build or SAM Deploy Steps
- For SAM Build: https://hub.docker.com/r/harnessdev/sam-build
Expand Down Expand Up @@ -86,10 +86,10 @@ In the Step YAML

### How to access the SAM Build Step Outputs?

- SAM build creates a “.aws-sam" directory in the same directory where your template.yml exists.
- SAM build creates a ".aws-sam" directory in the same directory where your template.yml exists.

- By default, Download Manifests Step downloads your repo in `/harness/MANIFEST_IDENTIFIER/` path which should be `/harness/dev/` in this case.
- If you have customized the step and the SAM template.yaml exits in the root level directly, AWS SAM outputs won't be available in the root path. You need to make sure `.aws-sam` should be present `/harness/dev/` path.
- If you have customized the step and the SAM template.yaml exists in the root level directory, AWS SAM outputs won't be available in the root path. You need to make sure `.aws-sam` should be present `/harness/dev/` path.

### How do I pass in the SAM Template path as an environment variable?

Expand Down Expand Up @@ -712,4 +712,4 @@ Harness does not natively support ECS Scheduled Tasks, but users can:
Users can:
- Use the Bitbucket API to retrieve necessary files.
- Implement an AWS CLI-based deployment script.
- Automate the process via a Harness pipeline step.
- Automate the process via a Harness pipeline step.