You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Select this option if this issue appears to be a regression.
Expected Behavior
To be able to create a new CostExplorerClient instance and access the various CostExplorer methods using the newly created user account.
Current Behavior
It creates the user account and role fine, attaches the policy to them, and then pukes when it tries to actually do the thing.
Error executing "GetAnomalyMonitors" on "https://ce.us-east-1.amazonaws.com"; AWS HTTP error: Client error: `POST https://ce.us-east-1.amazonaws.com` resulted in a `400 Bad Request` response:
{"__type":"UnrecognizedClientException","message":"The security token included in the request is invalid."}
UnrecognizedClientException (client): The security token included in the request is invalid. - {"__type":"UnrecognizedClientException","message":"The security token included in the request is invalid."}
I understand that some services need tokens from STS but if I try to add an intermediary step of going to STS to assumeRole and get the keys, I get the same error, which makes even less sense (why would you need a token to fetch a token)?
I was concerned that maybe I have some cached token data somewhere (e.g. ~/.aws/credentials or in my current environment variables) but I made absolutely sure to clear those out (delete the file entirely, and unset those VARs).
I ran the CostExplorerClient in debug mode to make sure there wasn't a bad token being detected somewhere else and being injected, but nothing showed up there either.
I know I'm doing something wrong but I don't know where else to look.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Describe the bug
Ok, I am sure I'm doing something wrong here (user error vs. system error) but I am losing my mind and can't figure out where else to look.
The flow I'm trying to achieve is:
This is the User policy I am attempting to attach:
Regression Issue
Expected Behavior
To be able to create a new CostExplorerClient instance and access the various CostExplorer methods using the newly created user account.
Current Behavior
It creates the user account and role fine, attaches the policy to them, and then pukes when it tries to actually do the thing.
I understand that some services need tokens from STS but if I try to add an intermediary step of going to STS to assumeRole and get the keys, I get the same error, which makes even less sense (why would you need a token to fetch a token)?
I was concerned that maybe I have some cached token data somewhere (e.g.
~/.aws/credentials
or in my current environment variables) but I made absolutely sure to clear those out (delete the file entirely, and unset those VARs).I ran the CostExplorerClient in debug mode to make sure there wasn't a bad token being detected somewhere else and being injected, but nothing showed up there either.
I know I'm doing something wrong but I don't know where else to look.
Reproduction Steps
Possible Solution
At this point, I'm at a loss
Additional Information/Context
No response
SDK version used
3.321.13
Environment details (Version of PHP (
php -v
)? OS name and version, etc.)PHP 8.3.11 (cli) (built: Sep 10 2024 15:12:42) (NTS), macOS
The text was updated successfully, but these errors were encountered: