Note: Please go to docs.rightscale.com to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Reference Info > Dashboard Help Text > Miscellaneous

Miscellaneous

skeletor_services_report_service

Report Manager

Report Manager allows you to tag accounts and deployments to filter within reports, create reports using various types of usage to isolate changes or monitor spending, and schedule CSV dumps of your reports.

  • Reports - Allows you to edit, clone, delete, or create new reports. From the new reports menu, you can define the report name and description as well as the Report Type, manage filters, and the type of information you want returned in a report. Once a report is created, you can click on the report to schedule when you want your report to run.
  • Scheduled Reports - Allows you to edit or delete the reports that run on a reacquiring basis. Reports can be ran weekly, monthly, or yearly.
Add Report

Add Report creates a report based off of specific inputs defined in the section. Fields in this selection include the following:

  • Report Name - Required input used to identify the report.
  • Report Description - Optional input that defines the purpose of the report.
  • Report Type - Defines the type of usage that can be reported on. Depending on the item selected, the information that can be chosen in the Fields section will change. For example, if Volume Usage is selected, items only related to volumes, such as size or the ServerTemplate associated to the volume, can be selected.
  • Filters - Specific information can be tagged to filter the quantity of information returned in a particular account, deployment, or server. For example, if you want to filter information about a particular deployment, you select Deployment Name and enter the information you want to filter on.
  • Fields - Each item that can be checked represents the column of information that will be returned in a report. Depending on the Report Type items selected, these values can change.
Reports > Report Manager

ec2_images_create_replication

Images are AWS region-specific. For example, you cannot use an AMI that stored in 'AWS US-East' to launch a server instance in the 'AWS US-West' region. In order to use the same AMI in multiple regions, you must replicate the image to the new cloud or AWS region.

When you replicate a machine image (AMI) from one AWS region to the next (e.g. 'us-east' to 'us-west'), you are essentially creating a copy of that AMI in the other region. It will essentially be a new AMI. It will be assigned a new AMI ID and will be stored in an S3 bucket in that region. However, for consistency and organizational purposes the image will inherit the same name as the original AMI.

Note: You must create an S3 bucket in the new AWS region before you can replicate an image.

  • Bucket - The S3 bucket (location) where the new image will be stored. You may have to create a new S3 bucket in the new region if one does not already exist. If you are replicating the image to another AWS region, be sure to select a bucket in that region. You can also replicate an image within the same region if you simply want to save a copy of the AMI in a different S3 bucket.
  • Path - The location of the image within your S3 bucket that you're going to replicate. (e.g. image_bundles/myimage_us_east/)
  • Register - By default, the new image will automatically be registered with Amazon.
  • New kernel - Select which Amazon kernel image should be used. Some of Amazon's older kernels are not supported in newer AWS regions.
  • New ramdisk - Select which Amazon ramdisk image should be used. Some of Amazon's older ramdisk images are not supported in newer AWS regions.
Clouds > AWS Region > EC2 Images > Show > Replicate (Cancel)

rds_instances_new_point_in_time

Amazon supports "point-in-time" database restorations of RDS Instances. Specify the following information to restore a running RDS Instance:

  • AWS ID - The name of the RDS Instance you are attempting to restore. This field is prepopulated for you.
  • Restore time - Specify a specific point in time in the past to where you would like to restore the database back to. (YYYY-MM-DD HH:MM:SS) The most recent backup in Amazon's archive that is closest to the desired restoration time (not an RDS Snapshot) will be used to restore the database. Remember, AWS performs regular backups of an RDS Instance. For typical workloads, you should be able to restore your database to any point in time within your retention period, up to the last five minutes. (e.g. 2010-01-25 21:45:42)
Clouds > AWS Region > RDS Instances > Restore

vpcs_new_customer_gateway

To create a new Customer Gateway, specify the following parameters:

  • Type - The type of VPN connection this customer gateway supports. (e.g. ipsec.1)
  • IP Address - The Internet-routable IP address for the customer gateway's outside interface. The address must be static.
  • BgpAsn - The customer gateway's Border Gateway Protocol (BGP) Autonomous System Number (ASN).
Clouds > AWS Region > VPCs > Index > Gateways tab > New Customer Gateway

macros_prerun

When you run a macro, the code under its Commands tab will be executed. Depending on what's defined in the code, you may have to select resources that you want to be reused before you can begin running the macro's code.

Design > Macros > Show > Run button

server_templates_merge_select

Merging ServerTemplates

This dialog allows you to perform a three-way merge of ServerTemplates. The typical use case occurs after you have cloned and slightly customized a public ServerTemplate. When a new revision of the public template is published, you can merge those updates into your customized (editable) ServerTemplate.

The required parameters are:

  • Start ServerTemplate - The common ancestor to both the End ServerTemplate and the current template (To ServerTemplate). This is typically the template that the current template was cloned from.
  • End ServerTemplate - A descendant of the Start ServerTemplate that contains changes you wish to merge. Typically this is the latest published revision of the Start ServerTemplate's lineage.
  • To ServerTemplate - A descendant of the Start ServerTemplate that you wish to merge a set of changes into. Typically this is a customized clone of the Start ServerTemplate.
  • Destination ServerTemplate - This is an editable [HEAD] ServerTemplate where the output of the merge will be saved. The contents of this template will be overwritten, so it is important to make sure any modifications have already been committed.
Design > ServerTemplates > Show > Merge

ec2_images_new_replication

Images are AWS region-specific. For example, you cannot use an AMI that stored in 'AWS US-East' to launch a server instance in the 'AWS US-West' region. In order to use the same AMI in multiple regions, you must migrate/replicate the image to the new cloud or AWS region.

When you replicate a machine image (AMI) from one AWS region to the next (e.g. 'us-east' to 'us-west'), you are essentially creating a copy of that AMI in the other region. It will essentially be a new AMI. It will be assigned a new AMI ID and will be stored in an S3 bucket in that region. However, for consistency and organizational purposes the image will inherit the same name as the original AMI.

  • Bucket - The S3 bucket (location) where the new image will be stored. You may have to create a new S3 bucket in the new region if one does not already exist. If you are replicating the image to another AWS region, be sure to select a bucket in that region. You can also replicate an image within the same region if you simply want to save a copy of the AMI in a different S3 bucket.
  • Path - The location of the image within your S3 bucket that you're going to replicate. (e.g. image_bundles/myimage_us_east/)
  • Register - By default, the new image will automatically be registered with Amazon.
  • New kernel - Select which Amazon kernel image should be used. Some of Amazon's older kernels are not supported in newer AWS regions.
  • New ramdisk - Select which Amazon ramdisk image should be used. Some of Amazon's older ramdisk images are not supported in newer AWS regions.
Clouds > AWS Region > EC2 Images > Show > Replicate

ec2_ssh_keys_pre_import

Create a new EC2 SSH Key pair by using the import feature to use an existing RSA key pair. Once you import your SSH Key, it will be available for use for launching EC2 instances. However, unlike EC2 SSH Keys, no private key material is present. Therefore, you will not be able to use this RSA key pair to successfully launch instances using v4 RightImages because the private key material is required to execute RightScripts on the instance. However, you can use an RSA key pair to launch instances using v5 RightImages because managed SSH is used instead for client-server authentication purposes.

One of the benefits of using the import feature is that you can use the same RSA key pair in multiple AWS regions. Simply repeat the process in other regions in which you would like to use the same key pair.

Clouds > AWS Region > EC2 SSH Keys > New > Import

library_server_templates_landing

Welcome to the MultiCloud Marketplace, where we maintain a library of ServerTemplates, RightScripts, MultiCloud Images and Macros for you. The MultiCloud Marketplace is simple to use, and contains the following functional areas. First, on the left hand side:

  • Browse - Select the RightScale component you wish to browse for in the MultiCloud Marketplace. Note that once selected, this dynamically reflects the remaining sections of the left hand side of the screen.
  • Search - Searches for the text pattern you enter into the Keyword(s) field. The enhanced Search also has the following features to help locate what you need:
    • Search in - Drop down menu to specify whether the search should be the Title only, Title & Description fields, or Publisher name.
    • Show advanced options - Expands to show the following advanced options in a drop-down menu format:
      • Price - Any, Free or Paid
      • Cloud - All (search all registered clouds) or select from a dynamic list of each registered cloud.
      • Sort by - Sort the results of your search query by: Newest First, Oldest First, Title or Rating
  • Categories - Each RightScale component is split into categories. For example, ServerTemplates that are Load Balancing related, Application Servers, etc. Each category also includes an exhaustive listing "All" and "Shared". Shared displays all of the RightScale components that have been shared with you from other RightScale users via Sharing Groups. (Note: The ability to create Sharing Groups and share RightScale components is reserved for users of our Premium and Enterprise editions.) When you accept an invitation to a Sharing Group, you gain access to all of that group's shared RightScale components (ServerTemplates, RightScripts, Macros, and MCIs). The primary part of the display (right hand side) differs depending on what RightScale component you are browsing for. ServerTemplates are handled a bit differently, with additional functionality.

ServerTemplates - When browsing for ServerTemplates the screen is split into the following two sections:

  • Featured ServerTemplate - Highlights ServerTemplates that are either new, popular or have recently changed. The Featured ServerTemplate changes pretty often, about every two weeks, so keep your eyes open for ServerTemplates of interest!
  • List of ServerTemplates - Note that in addition to the categories, there are three helpful tabs to help you locate ServerTemplates of interest: Most Popular; Recently Added; Featured

Selecting an individual ServerTemplate also includes the following helpful capabilities:

  • My Rating - 4 Star rating system. 1 (lowest) to 4 (highest) rating.
  • Discussion- Post discussion comments for the ServerTemplate. Try to be as constructive as possible.
Design > MultiCloud Marketplace > ServerTemplates

server_arrays_edit_schedule

You can also define how an alert-based array resizes over the course of the week by using the server array schedule feature. If there are no rules defined, then the default mincount and default maxcount values are used. Remember, any new settings will persist until they are changed. The only way to revert back to your default settings is to add another resize setting.

There are two types of server arrays:

  • Time - Configure the time using the 24hr 'HH:MM' format. (Ex: 14:00 = 2:00pm)
  • Actions - If you change the resize settings, you can click Delete to remove the setting.
Manage > Arrays > Show > Server Array Schedule

s3_images_view_bucket

Select an S3 bucket to perform the following tasks:

  • Analyze bucket - This background process will search for all AMI manifest files in your S3 bucket and will locate all associated image parts. It also checks for image registrations with EC2
    Note: The analysis of a bucket can take anywhere from a minute to several hours, depending on the size of the S3 bucket, so please do not gratuitously analyze large buckets.
  • delete - Permanently delete an AMI.
  • deregister - Deregister an AMI.
Clouds > AWS Global > Image locator > Show

ec2_images_register_ebs_prep

In order to create an EBS-based AMI, you will need to provide the following information. Once you create the AMI, you will need to create an MCI so that you can use the snapshot AMI to launch servers with ServerTemplates.

Clouds > AWS Region > EBS Snapshots > Show > Register EBS Image

ec2_images_new_ebs

Create an EBS-based Image from an EC2 Instance

Specify the following information:

  • EBS Instance - Select which active instance you would like to bundle. The current viewable instance is preselected. You can only create an EBS-based image from instances that were launched with an EBS-based (not S3-based) image.
  • Name - Provide a name for the new image. Amazon will not let you change this name once the image has been created. Note: You can also add an editable 'nickname' with an image, however it only has relevance within the RightScale platform.
  • Description - Provide a description for the image. Amazon will not let you change the description once the image has been created.
  • No reboot - Determines when the bundle of the instance will be created. If you leave this box checked, you may experience odd behavior when launching an instance from the newly bundled image because it looks like you are rebooting an instance that already appears to be running.
    • [checked] - Create a bundle of the running instance. (not recommended)
    • [unchecked] - Create a bundle of the instance after it's been shutdown. (recommended)
Bundling an instance

deployments_show_default

What is a deployment?

A Deployment consists of a cluster or group of Servers that work together and share common Input variables and cloud configurations. In a Deployment, you can manage a group of Servers in the same way that you would manage a single Server. You can define common Input variables, execute RightScripts on some or all Servers, as well as create multiple Server environments for production, development, staging, and maybe even failover scenarios. For example, a typical web site Deployment consists of two front-end application Servers and two back-end, master/slave database Servers. At the Deployment level, you can see all of the Servers, the Inputs that are being used, as well as where the values are being inherited from. To learn more about inputs and the inheritance rules that apply, see Inputs.

What is the 'Default' deployment?
Each account contains a 'Default' Deployment. Typically, you will add Servers to a Deployment from a specific ServerTemplate. However, if you launch a Server directly from a ServerTemplate without assigning it to a particular Deployment, the Server will appear in the Default Deployment. Do not use the Default Deployment for production purposes. Instead, create a new Deployment.
Important! You cannot define/edit Inputs for the Default Deployment. In order to set Deployment-wide inputs, you must create a new Deployment.

Action Buttons

  • Edit - Change a Deployment's title, description, or specify the default availability zone for launching instances (Default: any)
  • Clone - Create an exact duplicate of the definition of your Deployment. The data that is stored on Servers in your Deployment will not be copied over when you clone a Deployment. You are simply cloning the definition of that Deployment so that you can launch a duplicate setup at a later time or modify its configuration accordingly.
Info

The Info tab shows the description and tags for the deployment.

Action Buttons

  • Edit - Edit the description of the deployment.
  • Edit Tags - Create tags to use for servers to address other servers within the deployment.
Manage > Deployments > Index > Default Deployment

multi_cloud_images_diff_select

You can perform a diff MultiCloud Image object to view the differences between two different revisions. You can also merge the changes between two different revisions together into a HEAD version.

Design > MultiCloud Images > Show > Diff

rds_instances_new_read_replica

To launch a Read Replica RDS Instance, provide the following information:

  • Name - Enter the name of the Read Replica instance that you're going to launch. Note: By default, a name will be automatically generated where the name of the source ("master") RDS instance will be used as a prefix. If you plan to launch more than one Read Replica for the source instance (max=5), you might want to add a number in the name for differentiation purposes.
  • Instance Class - Select the instance type that you want to use for launching the new Read Replica RDS instance.
  • Endpoint Port - Enter which port will be used by MySQL. By default, if you leave this field blank, port 3306 will be used.
  • Availability Zone - Select the availability zone where the instance will be launched. If the 'any' option is selected, Amazon will randomly pick an availability zone for you.
  • Auto minor version upgrade - If checked, Amazon will automatically upgrade the instance's MySQL version. For example, if the instance is using MySQL v5.1.50 and Amazon later supports v5.1.51 for RDS instances, your instance's MySQL engine will automatically be upgraded during one of the maintenance windows.
  • IOPS - Enter the IOPS for your Read Replica. Note the value of your IOPS depends on the instance in use. Leave blank if you are not using IOPS.
Clouds > AWS Region > RDS Instances > Launch Read Replica

skeletor_services_sqs_browser

Help Text for SQS Queue

SQS Cloud Service is intended to represent a single queue and its corresponding properties, permissions, and messages. It is an Amazon web service that provides a distributed queue messaging service. It allows for the movement of data between distributed components of applications that perform different tasks without losing messages or requiring each component to be continuously available. The RightScale Dashboard makes creating and managing AWS SQS queues very simple. The following information is seen in the table:

  • Name - A nickname for the SQS queue. Similar to S3 bucket names, SQS queue names must be unique.
  • API Gen - The queue's API generation (Gen1 or Gen2). If you are still using Gen1 SQS Queues see the important note on Simple Queue Service
  • Approx Length - The approximate length of the queue in terms of the number of items.
  • Visibility Timeout - Specifies the time in seconds that a job will remain hidden before it becomes available to other worker instances. Actions - Clear (remove all) messages in the queue or delete the queue.

Actions

  • Create Queue - Creates a New SQS queue.
Help Text for SQS Queue - Info Tab

SQS Cloud Service is intended to represent a single queue and its corresponding properties, permissions, and messages. It is an Amazon web service that provides a distributed queue messaging service. It allows for the movement of data between distributed components of applications that perform different tasks without losing messages or requiring each component to be continuously available. The RightScale Dashboard makes creating and managing AWS SQS queues very simple. The following options display:

  • Message - The available messages in the queue, messages being delivered, and the messages that * **are delayed.
  • General - The URL, Amazon Resource Name (ARN), when the queue was created, and last was last updated.
  • Settings - Allows you to edit how long the message will display before timing out, how long the message will retain in the queue, how large the message size will be, and how long the message will delay before sending.

Actions

  • Queue List - Returns you back to the list of SQS Queues.
  • Delete Queue - Removes the queue that is currently displayed.
  • Refresh - Updates the queue with new data.
Help Text for SQS Queue - Messages Tab

SQS Cloud Service is intended to represent a single queue and its corresponding properties, permissions, and messages. It is an Amazon web service that provides a distributed queue messaging service. It allows for the movement of data between distributed components of applications that perform different tasks without losing messages or requiring each component to be continuously available. The RightScale Dashboard makes creating and managing AWS SQS queues very simple. The following options display:

  • Create Message - Allows you to create and add a new message to the queue.
  • Message Body - Displays the text of the body.
  • Size - The size in bytes of the message.
  • Count - The amount of times the message was received.
  • Sent - Date and time the message was sent.
  • Actions - Deletes the message in the queue.

Actions

  • Queue List - Returns you back to the list of SQS Queues.
  • Delete Queue - Removes the queue that is currently displayed.
  • Refresh - Updates the queue with new data.
Help Text for SQS Queue - Permissions Tab

SQS Cloud Service is intended to represent a single queue and its corresponding properties, permissions, and messages. It is an Amazon web service that provides a distributed queue messaging service. It allows for the movement of data between distributed components of applications that perform different tasks without losing messages or requiring each component to be continuously available. The RightScale Dashboard makes creating and managing AWS SQS queues very simple. The following options display:

  • User - The RightScale user with access to the available permissions.
  • Permissions - Users can be granted the permissions to receive messages, view queue attributes, view queue URL, modify the message visibility, delete messages, or send messages.
Clouds > AWS Region > SQS Queues

right_scripts_diff_select

Performing a Diff on RightScripts

This dialog allows you to view the differences between two RightScripts. You can either perform a diff between two different RightScripts or between two different revisions of the same RightScript. See Diff and Merging RightScripts for more information.

Simply select which two RightScripts you want to compare. The differences will be highlighted in different colors.

Design > RightScripts > Show > Diff

skeletor_services_maestro

Help Text for Orchestration

RightScale's server orchestration allows for managing entire applications running on the cloud by leveraging the RightScale platform. The orchestration may include activities like configuring and launching servers in order, running operational runlists, scaling server arrays, sending emails, retrieving and analyzing metrics data, sending requests to external applications, prompting users for input, or other various activities. The following options display:

  • Name - The name of the process.
  • State - The processes state can be terminated, active, errored, or other stuff
  • Started At - Date and time the process started.
  • Completed At - Date and time the process completed.
  • Runtime - How long the process will take to run.
  • Active tasks - The number of active tasks. If green, the task is operating normally. If red, there is an error.
  • Actions - Allows you to delete or clone the process.

Actions

  • New Process - Name a new process and input the RightScale CloudFlow code. You can verify the syntax of the code, run it, or identify inputs.
Orchestration - Tasks page

RightScale's server orchestration allows for managing entire applications running on the cloud by leveraging the RightScale platform. The orchestration may include activities like configuring and launching servers in order, running operational runlists, scaling server arrays, sending emails, retrieving and analyzing metrics data, sending requests to external applications, prompting users for input, or other various activities.

Tasks are sequence of activities executed in a CloudFlow job. Tasks can be paused, resumed, cancelled, or aborted. A single CloudFlow job may execute multiple tasks concurrently.

The following options display:

  • Name - The name of the task.
  • State - The tasks state can be Not Started, Running, Paused, In Error, Completed, Cancelled, or Aborted.
  • Created At - Date and time the task started.
  • Updated At - Date and time the task completed.
  • Start Position - The position the task will start at when running.
  • Current Position - The position the task currently is in.
  • Error - Displays if there is an error with the task.
  • Actions - Lists the Local Variables and References of the tasks.

Actions

  • Clone - Clones the process and creates a new process with the same name but a different version (for example, v2).
  • Delete - Deletes the entire process.
Help Text for Orchestration - Definition page

RightScale's server orchestration allows for managing entire applications running on the cloud by leveraging the RightScale platform. The orchestration may include activities like configuring and launching servers in order, running operational runlists, scaling server arrays, sending emails, retrieving and analyzing metrics data, sending requests to external applications, prompting users for input, or other various activities.

Definition expression define a sequence of statements in a define...end block. A definition has a name, zero or more arguments, and zero or more return values.

The following options display:

  • RightScale CloudFlow Code - Output of the RightScale CloudFlow Code.
  • Inputs - Displays the type and hrfs of the resources in the CloudFlow Code.

Actions

  • Clone - Clones the process and creates a new process with the same name but a different version (for example, v2).
  • Delete - Deletes the entire process.
Help Text for Orchestration - Process Info page

RightScale's server orchestration allows for managing entire applications running on the cloud by leveraging the RightScale platform. The orchestration may include activities like configuring and launching servers in order, running operational runlists, scaling server arrays, sending emails, retrieving and analyzing metrics data, sending requests to external applications, prompting users for input, or other various activities.

The following options display:

  • Overview - Displays the processes state, size, maximum size, and ID.
  • Timestamps - Displays the date and time the process was created, launched, updated, and terminated.
  • Task States - The amount of times a tasks was deemed as not started, running, paused, in error, completed, cancelled, or aborted.
  • Global Variable and References - Contains the variables -- which always start with $ and may contain letters, numbers, and underscores -- and References which store collections of resources. Collections consist of resources of the same type, such as servers or instances.

Actions

  • Clone - Clones the process and creates a new process with the same name but a different version (for example, v2). Delete - Deletes the entire process.
Help Text for Orchestration - Audit Entries page

RightScale's server orchestration allows for managing entire applications running on the cloud by leveraging the RightScale platform. The orchestration may include activities like configuring and launching servers in order, running operational runlists, scaling server arrays, sending emails, retrieving and analyzing metrics data, sending requests to external applications, prompting users for input, or other various activities.

The Audit Entries tab displays all activities that occur within a ClowdFlow Process.

The following options display:

  • Summary - An overview of the activities that occurred within the process.
  • Updated at - The time and date the audit entry was last updated.
  • Selected Audit - Displays the summary of the selected audit.

Actions

  • Clone - Clones the process and creates a new process with the same name but a different version (for example, v2).
  • Delete - Deletes the entire process.

recurring_volume_attachments_new_server

Fields

  • Volume: name of the volume
  • to Server: select the server you would like to attach the volume on boot.
  • as device: select the type of disk you would like to use as a volume to attach on boot.
  • Schedule: confirm your selections to attach your volume at the boot time of the selected server.

multi_cloud_images_merge_select

This dialog allows you to perform a three-way merge of MultiCloud Images. The typical use case occurs after you have cloned and slightly customized a public MultiCloud Image. When a new revision of the public MultiCloud Image is published, you can merge those updates into your customized MultiCloud Image.

The required parameters are:

  • Start MultiCloud Image - The common ancestor to both the End MultiCloud Image and the current MultiCloud Image (To MultiCloud Image). This is typically the MultiCloud Image that the current one was cloned from.
  • End MultiCloud Image - A descendant of the Start MultiCloud Image that contains changes you wish to merge. Typically this is the latest published revision of the Start MultiCloud Image's lineage.
  • To MultiCloud Image - A descendant of the Start MultiCloud Image that you wish to merge a set of changes into. Typically this is a customized clone of the Start MultiCloud Image.
  • Destination MultiCloud Image - This is an editable [HEAD] MultiCloud Image where the output of the merge will be saved. The contents of this MultiCloud Image will be overwritten, so it is important to make sure any modifications have already been committed.
Design > MultiCloud Images > Show > Merge

dashboard_index_trial

Welcome to RightScale!

Thank you for signing up for a free trial account, where you'll receive complimentary EC2 instance time from RightScale. The RightScale Dashboard makes it easy to design, manage, and monitor all of your activities on cloud infrastructures such as Amazon's EC2.

Where should I start?
If you are new to RightScale, we recommend following some of our tutorials on our RightScale Support Site( support.rightscale.com). Other resources include our blog (blog.rightscale.com) and forums (forums.rightscale.com).

Getting Started Tutorials
As a free trial user you can complete several of our tutorials, which will help you become familiar with the RightScale Dashboard, as well as show you how easy it is to launch and manage all of your instances in the cloud. Be sure to validate your email before starting one of the tutorials, otherwise you will not be able to successfully launch an instance. You should receive a confirmation email from notifier@rightscale.com (it might be in your spam folder).

Don't forget to click on the Help button on other screens for more information and relevant tutorials. By default, the Help screens will appear the first time that you visit a new screen.

How do I upgrade?
If you no longer have complimentary instance time, but would like to continue to use the RightScale Dashboard, you can either sign-up for our free Developer edition where you will use your own AWS credentials with a modified version of the Dashboard, or you can sign up for one of our pay editions (Website/Grid/Premium) where you will be able to take full advantage of all the tools in the RightScale Dashboard including:

  • MySQL Manager for creating a redundant MySQL database with failover and recovery
  • Autoscaling based on bandwidth requirements
  • Monitoring and alerting
  • Multi-server clusters
  • Scalable batch processing

If you would like to see a full version demo of all the features of the RightScale Dashboard, please contact us.

NOT SHOWN -- PLACEHOLDER

server_templates_diff_select

Performing a Diff on ServerTemplates

The Diff features allows you to view the differences between two ServerTemplates. You can either perform a diff between two different ServerTemplates or between two different revisions of the same ServerTemplate.

Simply select which two ServerTemplates you want to compare. The differences will be highlighted in different colors.

Design > ServerTemplates > Show > Diff

vpcs_new_vpn_gateway

To create a new VPN Gateway, specify the following parameters:

  • Type - The type of VPN connection that the VPN gateway will support. (i.e. ipsec.1)
  • Availability Zone - The availability zone where the VPN gateway will be created.
Clouds > AWS Region > VPCs > Index > Gateways tab > New VPN Gateway

vpcs_new_vpn_connection

To create a new VPN Gateway, specify the following parameters:

  • Type - The type of VPN Connection that the customer gateway supports. (e.g. ispec.1)
  • Customer gatweay id - Select the ID of the customer gateway. (e.g. cgw-cdcd4aa2)
  • VPN gatweay id - Select the ID of the customer gateway. (e.g. vgw-0cad1234)
Clouds > AWS Region > VPCs > Index > Gateways tab > New VPN Connection

queues_new_policy_statement

To create a policy for your SQS Queue that defines who has access to it (i.e. user permissions). Once a policy is created, you still have the ability to edit it and make changes. When creating a new policy you must define the following information:

  • Sid - A prepopulated unique SID.
  • Principal - A Principal is the person(s) who receive or are denied permission to access your queue. You must specify the principal by providing their AWS account ID (e.g., 1234-5678-9012, with or without the hyphens). You can specify multiple principals, or use a wildcard (*) to indicate all possible users. Multiple principles can be listed by using a space, comma, or semi-colon delimited list. (Ex: 1234-5678-9012,999999999999) Note: There is no validation check to verify a legal principal. Be sure to specify correct Principal IDs and test all of your policies.
  • Action - Specify what actions can be taken by a Principal in a space, comma, or semi-colon delimited list. (Ex: SQS:SendMessage,SQS:ReceiveMessage) See Amazon for a complete list of supported actions. Valid actions include: SQS:SendMessage, SQS:ReceiveMessage, SQS:DeleteMessage, SQS:*
  • Effect - Set the policy to Allow or Deny access.

Note: Wildcards (*) are supported. All supported actions apply with this syntax.

Clouds > AWS Global > Show > Policy Tab > Add Statement

s3_images_view_bucket_no_images

Locate all of your EC2 Images

To locate all AMIs stored in this bucket select the Analyze bucket button. This will start a background process that searches for all AMI manifest files and then locates all associated image parts. It also checks for image registrations with EC2.

The background process shows up in the Recent Events pane and may take anywhere from a minute to hours, depending on the number of items in the bucket. Please do not use gratuitously on large buckets! Note that the background process lists the entire content of the bucket, you will thus incur the associated S3 charges.

After selecting the Analyze bucket button, you should receive a flash message within the RightScale banner similar to the following: "Your S3 images analyze task has been placed to a queue. The S3 images list will be updated soon. (This a long time task and the collecting time depends on the size of the bucket(s).)"

Clouds > AWS Global > Image locator > Show

right_scripts_merge_select

Merging RightScripts

This dialog allows you to perform a three-way merge of RightScripts. The typical use case occurs after you have cloned and slightly customized a public script. When a new revision of the public script is published, you can merge those updates into your customized script. See Diff and Merging RightScripts for more information.

The required parameters are:

  • Start Script - The common ancestor to both the End Script and the current script (To Script). This is typically the script that the current script was cloned from.
  • End Script - A descendant of the Start Script that contains changes you wish to merge. Typically this is the latest published revision of the Start Script's lineage.
  • To Script - A descendant of the Start Script that you wish to merge a set of changes into. Typically this is a customized clone of the Start Script.
  • Destination Script - This is an editable [HEAD] script where the output of the merge will be saved. The contents of this script will be overwritten, so it is important to make sure any modifications have already been committed.
Design > RightScripts > Show > Merge
You must to post a comment.
Last modified
09:45, 15 Jan 2014

Tags

This page has no custom tags.

Classifications

This page has no classifications.

Announcements

None


© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.