-
### Describe the bug.
The following is seen over and over now that Data Platform have been off-boarded
```
# module.managed_grafana.aws_grafana_role_association.this["EDITOR"] will be updated iā¦
-
As a user I would like to be able to log into AWS CLI via SSO and have Vault read from SSO credentials stored in `~/.aws/sso`. Currently I have to perform an STS login using explicit `aws_access_key_iā¦
-
### Community Note
* Please vote on this issue by adding a š [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to helpā¦
-
**Describe the bug**
```
$ amplify env pull
ā ¦ Fetching updates to backend environment: dev from the cloud.(node:10308) UnhandledPromiseRejectionWarning: Error: connect EHOSTUNREACH 169.254.169.254:ā¦
-
Full error is (with obfuscating of sensible data):
```
ā Error: reading AWS SSO Identity Store Group Data Source (): operation error identitystore: GetGroupId, https response error StatusCode: 400ā¦
-
### Describe the bug
I have a somewhat complex IAM assume-role configuration that *should* work using the SDK and *does* work using the CLI.
* You have a SSO-based AWS profile set up in ~/.aws/cā¦
-
When you add a new AWS SSO integration, Leapp sets the wrong region for the individual accounts. In my case I selected `euāwestā1` when adding a new AWS SSO integration, but Leapp added all the accounā¦
-
I've just caught up on [the last community standup](https://www.youtube.com/watch?v=SzpFCVg3JbA) and was interested to hear the direction for completions, and wanted to share how I'm solving this todaā¦
-
**User Need**
**As a** Hosting Team
**I want** to replace the existing process used to manage access to YJAF associated AWS accounts with AWS SO
**so that** we have a consistent approach for how userā¦
-
### Terraform Version
```shell
Terraform v1.6.6
on darwin_arm64
```
### Terraform Configuration Files
```terraform
terraform {
required_providers {
aws = {
source = "hashicorp/awā¦