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

Error updating Lambda function using credentials from environment variables in PowerShell #188

Open
1 task
ashovlin opened this issue Sep 27, 2021 · 3 comments
Labels
breaking-change This issue requires a breaking change to remediate. bug This issue is a bug. module/cli-ext needs-major-version Can only be considered for the next major release p2 This is a standard priority issue queued

Comments

@ashovlin
Copy link
Member

Description

I have a [default] profile in my shared config/credentials files with an access key and secret for one account.

I attempt to deploy a Lambda function into another account using temporary credentials in my PowerShell session

$Env:AWS_ACCESS_KEY_ID="<redacted>"
$Env:AWS_SECRET_ACCESS_KEY="<redacted>"
$Env:AWS_SESSION_TOKEN="<redacted>"
dotnet lambda deploy-function

Results in an error like Error updating configuration for Lambda function: Cross-account pass role is not allowed.

I am able to proceed by temporarily renaming my [default] profile to something else.

Environment

  • Build Version: Amazon Lambda Tools for .NET Core applications (5.1.4)
  • OS Info: Windows 10
  • Build Environment:
  • Targeted .NET Platform:

Resolution

  • 👋 I can/would-like-to implement a fix for this problem myself

This is a 🐛 bug-report

@ashovlin ashovlin added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Sep 27, 2021
@ashovlin ashovlin changed the title Error updating Lambda function using credentials from environment varables in PowerShell Error updating Lambda function using credentials from environment variables in PowerShell Sep 27, 2021
@ashishdhingra
Copy link
Contributor

ashishdhingra commented Oct 1, 2021

Similar to aws/aws-sdk-net#1779.

This should be fixed when it is implemented in next major version of SDK.

@ashishdhingra ashishdhingra added breaking-change This issue requires a breaking change to remediate. and removed needs-triage This issue or PR still needs to be triaged. labels Oct 1, 2021
@github-actions
Copy link

github-actions bot commented Oct 2, 2022

We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Oct 2, 2022
@github-actions github-actions bot closed this as completed Oct 4, 2022
@ashishdhingra ashishdhingra reopened this Oct 4, 2022
@ashishdhingra
Copy link
Contributor

No close

@ashishdhingra ashishdhingra added needs-major-version Can only be considered for the next major release p1 This is a high priority issue needs-review and removed closed-for-staleness labels Dec 24, 2022
@ashishdhingra ashishdhingra added p2 This is a standard priority issue and removed p1 This is a high priority issue labels May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change This issue requires a breaking change to remediate. bug This issue is a bug. module/cli-ext needs-major-version Can only be considered for the next major release p2 This is a standard priority issue queued
Projects
None yet
Development

No branches or pull requests

2 participants