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

Add /etc/pki directory to appnet agent's bind mounts #4437

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

sparrc
Copy link
Contributor

@sparrc sparrc commented Nov 22, 2024

Summary

This is the path to the host's PKI directory. The appnet agent container needs
this directory mounted so that it can access the host's PKI directory for the
purpose of utilizing any special CA certs that the underlying EC2 instance has
configured.

Without this change the appnet agent is not able to operate and the service
connect feature does not work in situations where the EC2 instance has
non-standard CA certs configured.

Testing

New tests cover the changes: no, modified existing unit test

Description for the changelog

Enhancement: Add /etc/pki directory to appnet agent's bind mounts for service connect

Licensing

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

@sparrc sparrc requested a review from a team as a code owner November 22, 2024 19:08
@sparrc sparrc force-pushed the sparrc-sc-pki-mount branch from 9208019 to 38ca72c Compare December 4, 2024 21:01
@sparrc sparrc changed the title wip Add /etc/pki directory to appnet agent's bind mounts Dec 4, 2024
This is the path to the host's PKI directory. The appnet agent container needs
this directory mounted so that it can access the host's PKI directory for the
purpose of utilizing any special CA certs that the underlying EC2 instance has
configured.
@sparrc sparrc merged commit 621ea86 into aws:dev Dec 4, 2024
40 checks passed
@sparrc sparrc deleted the sparrc-sc-pki-mount branch December 4, 2024 23:09
sparrc added a commit to sparrc/amazon-ecs-agent that referenced this pull request Dec 5, 2024
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