Abstract: A distributed data storage system may implement determining indexing progress for a table stored in the distributed data storage system. A table may be stored in multiple table partitions. When a secondary index is created for the table, each partition may independently index the items stored within the table partition in order to identify those items in the partition that should be stored in the secondary index. During creation of the secondary index, creation progress points that indicate the progress of the indexing across the table partitions may be determined. The creation progress points may be provided via a programmatic, textual, or graphical interface to the distributed data storage system.

Abstract: Systems and methods for predicting computing system issues include: receiving a set of incident management tickets for a set of computing system issues and a set of computer log files for multiple modules of the computing system; arranging the set of tickets into chronologically ordered groups associated with particular computing system issues; pre-processing the set of computer log files to remove specified information, append to each log entry an indicator of the module of the log file, and merge the log entries; determining for each group a set of patterns for the group's associated computing system issue before the group's associated computing system issue arises; calculating for each pattern in each group a similarity score; selecting a subset of patterns whose similarity scores exceed a specified threshold; and generating a computing model associating the subset of patterns in each group with the group's associated computing system issue.

Abstract: A data storage system may implement recommending throughput capacity for generating a secondary index for an online table. Secondary indexes may be created for a table stored in multiple partitions in the data storage system. The data storage system may allow users to provision throughput capacity to process access requests at secondary indexes. The throughput capacity may also be used to perform updates at the secondary index as part of generating the secondary index. A creation throughput capacity may be determined that compensates for performing the updates to generate the secondary index. A user may receive a recommendation with the creation throughput capacity for creating the secondary index and may accept or modify the creation throughput capacity. The creation throughput may be automatically provisioned to create the secondary index, in some embodiments.

Abstract: A data storage system may implement generating creation performance metrics for a secondary index of a table. Metrics may be collected from different partitions of a table and different partitions of a secondary index in a table store upon initiating creation of the secondary index for the table that utilize provisioned resources for creating the secondary index. The metrics may be analyzed to generate performance metrics for the creation of the table. The performance metrics may be provided to clients of the data store or to monitoring systems. Monitoring systems may send performance event notifications to clients or automatically perform modifications to the provisioned throughput capacity.

Abstract: A local data store may also be configured to process updates using a common API with reference to a common schema. The common API and common schema may also be employed by hosted applications utilizing a remote distributed data store. Behavior of the remote distributed data store may be emulated by the local data store. Behaviors of the distributed data store that may be simulated include eventual consistency, provisioned throughput and latency based on horizontal partitioning.

Abstract: Methods and systems are disclosed which allow secure targeting of advertisements on pages where security is a concern, such as login pages. Cookie information may be received at one or more servers over a first domain from a browser application when a user visits a login page using the browser application. The cookie information may then be transmitted to one or more servers over a second domain. At the one or more servers, targeting information may be extracted from the cookie information, and one or more advertisements may be selected based at least in part on the extracted targeting information. The advertisements may be transmitted to the browser application over the second domain, and displayed by the browser application in an inline frame.

Abstract: Methods and systems are disclosed which allow targeted advertising on pages where security is a concern, such as login pages. Cookie information may be received at one or more servers over a first domain from a browser application when a user visits a login page using the browser application. The cookie information may then be transmitted to one or more servers over a second domain. At the one or more servers, targeting information may be extracted from the cookie information, and the user may be targeted with one or more advertisements based at least in part on the extracted targeting information.

Abstract: A network device and method are directed towards providing a client side sign-in seal for use detecting phishing attempts. In one embodiment, a user of a client device may provide anti-phishing data through a sign-in setup user interface for a website, application, or the like. In one embodiment, the anti-phishing data is an image provided by the user. The user may also provide text, symbols, an audio clip, or the like. The user may also modify aspects of the image, text, symbols, or the like, such as a color. When the user accesses the website, application, or the like, the client device may provide client device data used to locate and display the sign-in seal. If the user is being phished, the anti-phishing data may not be displayed or otherwise played.

Abstract: A network device and method are directed towards providing a client side sign-in seal for use detecting phishing attempts. In one embodiment, a user of a client device may provide anti-phishing data through a sign-in setup user interface for a website, application, or the like. In one embodiment, the anti-phishing data is an image provided by the user. The user may also provide text, symbols, an audio clip, or the like. The user may also modify aspects of the image, text, symbols, or the like, such as a color. When the user accesses the website, application, or the like, the client device may provide client device data used to locate and display the sign-in seal. If the user is being phished, the anti-phishing data may not be displayed or otherwise played.