mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 09:28:55 -04:00
* [docs] Migrate docs from AsciiDoc to Markdown (#123507) * delete asciidoc files * add migrated files * fix errors * Disable docs tests * Clarify release notes page titles * Revert "Clarify release notes page titles" This reverts commit8be688648d
. * Comment out edternal URI images * Clean up query languages landing pages, link to conceptual docs * Add .md to url * Fixes inference processor nesting. --------- Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Co-authored-by: Liam Thompson <leemthompo@gmail.com> Co-authored-by: Martijn Laarman <Mpdreamz@gmail.com> Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com> (cherry picked from commitb7e3a1e14b
) # Conflicts: # docs/build.gradle # docs/reference/migration/index.asciidoc # docs/reference/migration/migrate_9_0.asciidoc # docs/reference/release-notes.asciidoc # docs/reference/release-notes/9.0.0.asciidoc # docs/reference/release-notes/highlights.asciidoc * Fix build file * Really fix build file --------- Co-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>
1.6 KiB
1.6 KiB
mapped_pages | |
---|---|
|
GCE Tips [discovery-gce-usage-tips]
Store project id locally [discovery-gce-usage-tips-projectid]
If you don’t want to repeat the project id each time, you can save it in the local gcloud config
gcloud config set project es-cloud
Machine Permissions [discovery-gce-usage-tips-permissions]
If you have created a machine without the correct permissions, you will see 403 unauthorized
error messages. To change machine permission on an existing instance, first stop the instance then Edit. Scroll down to Access Scopes
to change permission. The other way to alter these permissions is to delete the instance (NOT THE DISK). Then create another with the correct permissions.
- Creating machines with gcloud
- Ensure the following flags are set:
--scopes=compute-rw
- Creating with console (web)
- When creating an instance using the web console, scroll down to Identity and API access.
Select a service account with the correct permissions or choose Compute Engine default service account and select Allow default access for Access scopes.
- Creating with knife google
- Set the service account scopes when creating the machine:
knife google server create www1 \
-m n1-standard-1 \
-I debian-8 \
-Z us-central1-a \
-i ~/.ssh/id_rsa \
-x jdoe \
--gce-service-account-scopes https://www.googleapis.com/auth/compute
Or, you may use the alias:
--gce-service-account-scopes compute-rw