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

AWS SageMaker : IAM Roles for Service Account #3718

Closed
akartsky opened this issue May 8, 2020 · 4 comments
Closed

AWS SageMaker : IAM Roles for Service Account #3718

akartsky opened this issue May 8, 2020 · 4 comments
Assignees
Labels
platform/aws status/triaged Whether the issue has been explicitly triaged

Comments

@akartsky
Copy link
Contributor

akartsky commented May 8, 2020

Use IAM Roles for Service Account instead of aws-secret in all AWS SageMaker example pipelines

1] Change the example pipeline code
2] Change Readme

@stale
Copy link

stale bot commented Aug 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Aug 13, 2020
@Bobgy
Copy link
Contributor

Bobgy commented Aug 14, 2020

/assign @PatrickXYS
Do you want to take a look?

@stale stale bot removed the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Aug 14, 2020
@PatrickXYS
Copy link
Member

I think the PR has addressed the issue and merged.

/close

@k8s-ci-robot
Copy link
Contributor

@PatrickXYS: Closing this issue.

In response to this:

I think the PR has addressed the issue and merged.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform/aws status/triaged Whether the issue has been explicitly triaged
Projects
None yet
Development

No branches or pull requests

4 participants