sparse-intern-71089
08/11/2020, 8:26 PMgifted-vase-28337
08/11/2020, 8:32 PMlocalstack
.
Things I've tried:
1. Running the IAM commands directly with aws --endpoint-url=<http://localhost:456> iam the-command...
-- works as expected.
2. Running pulumi up
with all aws:endpoints
included, except cloudwatch
-- works as expected.
3. Eliminating all custom endpoints but cloudwatch
and iam
-- the iam
endpoint is ignored in this minimal case.
4. Starting localstack
with SERVICES=iam,cloudwatch
-- the issue persists.gifted-vase-28337
08/11/2020, 8:34 PM➜ pulumi version
v2.8.2
➜ pip list | grep pulumi-aws
pulumi-aws 2.13.1
➜ python --version
Python 3.8.5
gifted-vase-28337
08/11/2020, 10:28 PMiam
, cloudwatch
, or sns
endpoints is set, the s3
endpoint is ignored and requests are sent to <http://s3.amazonaws.com|s3.amazonaws.com>
.gifted-vase-28337
08/12/2020, 5:46 PMiam
and s3
endpoints are set, the iam
requests are sent to <http://iam.amazonaws.com|iam.amazonaws.com>
.gifted-vase-28337
08/12/2020, 6:06 PMlocalstack
and the aws terraform provider as the sources of the issue, I've successfully created the resources via the aws
CLI tool and also via terraform apply
.gifted-vase-28337
08/13/2020, 10:16 PMaws:endpoints:
- s3: '...'
iam: '...'
ec2: '...'
...
and not like this:
aws:endpoints:
- s3: '...'
- iam: '...'
- ec2: '...'
- ...