search

cloudcaptainsh / cloudcaptain

Issue Tracker for CloudCaptain
13 stars 3 forks source link

AWS ElasticSearch service support #110

Open marianfurdui opened 8 years ago

marianfurdui commented 8 years ago

Hi,
It would be nice to have this feature,
Thanks!

axelfontaine commented 8 years ago

Could you describe exactly how you envision this feature could look like?

marianfurdui commented 8 years ago

Hi, I am not familiar at all with AWS but this is roughly how I imagine the flow for a SpringBoot application (steps order might differ).

  1. Create a new Elastic-search domain in AWS (appname-env)
  2. Set the domain access policy to "Allow access to one or more AWS accounts or IAM users" and reuse the ARN used to configure boxfuse.
  3. for the custom iam-role-boxfuse from AWS add "AmazonS3FullAccess" permission.
  4. add a new env variable: "BOXFUSE_ELASTICSEARCH_ENDPOINT" with the Endpoint of the newly created Elasticsearch domain in 1. (each app will use ${BOXFUSE_ELASTICSEARCH_ENDPOINT} in .yaml or .properties)

Thanks for your effort!

jtheuer commented 8 years ago

Hi marianfurdui, I recently started to declare all required AWS resources in a cloudformation yaml file. For example SQS queues, IAM roles, dynamodb tables, .... For me, this is a perfect match with boxfuse: Cloud Formation already supports nearly all AWS resource types, has a good documentation and (since they support YAML) a readable syntax.

HTH,

Jan