Adrian D.

Hi @mgorny, thanks for reaching out. The warnings are expected as there are Python warnings that we don't have control of that we need to present to users. Please let...

The license warnings for now will be addressed. The package warnings will be looked at thoroughly if it would not impact other dependencies.

Hi @portswigger-katie, thanks for reaching out. I have replicated the issue using both the SDK and AWS Console. I created a Job with parameters and the parameters do not stay...

Hello @FireballDWF, thanks for reaching out. For troubleshooting, can you provide the full debug logs by adding `boto3.set_stream_logger('')` and removing all sensitive information. Also, if possible to provide code replication....

Hi @iliguanghui, thanks for reaching out and finding out the error in the documentation. I have submitted an internal ticket to our SSM Documentation Team for the fix. Let me...

Hello @collimilo, thanks for reaching out and finding the issue. I was able to reproduce the issue. I have reached out to the Bedrock service team. I'll let you know...

Hey drewma2k@, “--include CONFIGURATIONS” would only give outputs if you have certain configurations with the ECS Cluster such as KMS, logging and storage KMS configuration as per API doc [1]....

Hello @drewma2k, thanks for following up. To get the log group associated with the cluster using $ aws ecs describe-clusters --clusters --include CONFIGURATIONS, you must have a cluster log configuration...

Hi nrssutharsanan@, thanks for reaching out. As you have mentioned, the $ aws iam get-role --role-name already includes the Trust Policy. To isolate it, you could do Client side filtering...

Hi @nrssutharsanan, I have submitted a feature request to the IAM team to create an operation that gives the Trust Policy of the role. Please refer to an SDK or...