Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS Cloud Plugin: Implement AWS specific cloud plugin with S3 gateway and EC2 discovery #264

Closed
kimchy opened this issue Jul 16, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Jul 16, 2010

Replacing the previous cloud plugin, implements an AWS specific cloud plugin that provides both S3 gateway and EC2 discovery.

Installation

Installing the cloud plugin (once 0.9 is out) can be done using: bin/plugin -install cloud-aws.

h2. Generic Settings

A generic configuration of the AWS that includes the account and key can be set using:

cloud:
  aws:
    access_key: XXXX
    secret_key: YYYY

S3 Gateway

The S3 gateway is configured using:

gateway:
 type: s3
 s3:
   bucket: bucket_name_goes_here

The s3 gateway allows for the following settings:

  • bucket: The bucket name, required.
  • region: The region, defaults to us-standard. Can be one of us-west, EU, and ap-southeast-1.

EC2 Discovery

The EC2 based discovery can be set using:

discovery:
  type: ec2

The ec2 discovery allows for the following settings:

  • host_type: The host that will be used to connect to other instances. Can be private_ip, public_ip, private_dns, and public_dns. Defaults to private_dns.
  • groups: A set of security groups (either as array, or comma separated) to filter instances to connect to. Defaults to no filtering at all.
  • availability_zones: A set of availability zones (either as array, or comma separated) to filter instances to connect to. Defaults to no filtering at all.
@kimchy
Copy link
Member Author

kimchy commented Jul 24, 2010

implemented.

ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
Fix elastic#264

(cherry picked from commit c759218fee9c02e20b7ecc17bbec21f5aa8020a6)
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
MPC-1821: automatic shutdown after x time on startup

* fix pr

* fix pr

* fix pr

* added automatic shutdown after x time

* igor tfvars

* igor tfvars

* edit eng-igor.tfvars

* adding igor tfvars


Approved-by: Can Yildiz
costin pushed a commit that referenced this issue Dec 6, 2022
* Ensures that attributes defined by `row` commands can also be resolved in subsequent commands
* Produce a verification error if the resolution fails (and propose attributes with similar names in case of a resolution error)
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
Previously we have relied that `RUNTIME_JDK` is defined as an
environment variable but this is trappy for usage outside of Jenkins.
Therefore, the benchmark coordinator Night Rally will require that the
runtime JDK is passed as the command line parameter `--runtime-jdk`.

Relates elastic#246
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
Since elastic#264 night-rally requires runtime JDK to be specified as cmd
param.

Relates to elastic/night-rally#264
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant