https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
w
Are you passing two subnets?
b
Copy code
vpcOptions          : {
            securityGroupIds: [
                [0]: "sg-0986fd74"
                [1]: "sg-723a380a"
            ]
            subnetIds       : [
                [0]: "subnet-95c904cd"
                [1]: "subnet-a4f0098e"
                [2]: "subnet-457ed533"
            ]
        }
w
Looks like support for ES deployments to 3 AZs was only added recently - https://github.com/aws/aws-sdk-go/blob/master/CHANGELOG.md#release-v11630-2019-02-07 - and that this is not yet available in the Pulumi provider or the upstream Terraform AWS provider (https://github.com/terraform-providers/terraform-provider-aws/issues/7504).
b
But i only get 2 instances. So i used only 2 subnets
w
I see three subnets in the code snippet above. Do you get the same error if you remove one of the subnets?
b
yeah, it works 🙂
The only thing, is when i created a vpc es + domainPolicy + route 53 i’m still enabled to acces my es 😞
Found the problem.
w
Great - was it a Pulumi issue in the end - or something with AWS ES?
b
was something with what are account was setup….
👍 1
4 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by