Abstract: A request to add tags (e.g., labels, key-value pairs, or metadata) to resources can be digitally signed by the entity making the request, such that the source can be verified and an authorization determination made for each tag. For a request involving multiple services (or entities) that can each add tags, any tag added by a service can be included in the request and digitally signed by that service. Each service processing the request can also digitally sign the request before forwarding, so that each service signs a version of the request, which includes elements signed by other services earlier in the request chain. When the request is received to a tagging service, the service ensures that every tag was digitally signed by the appropriate authorized entity or service, and validates the signatures to ensure that no data was modified or omitted, before adding the tags to the designated resource(s).

Abstract: A request to add tags (e.g., labels, key-value pairs, or metadata) to resources can be digitally signed by the entity making the request, such that the source can be verified and an authorization determination made for each tag. For a request involving multiple services (or entities) that can each add tags, any tag added by a service can be included in the request and digitally signed by that service. Each service processing the request can also digitally sign the request before forwarding, so that each service signs a version of the request, which includes elements signed by other services earlier in the request chain. When the request is received to a tagging service, the service ensures that every tag was digitally signed by the appropriate authorized entity or service, and validates the signatures to ensure that no data was modified or omitted, before adding the tags to the designated resource(s).

Abstract: A request to add tags (e.g., labels, key-value pairs, or metadata) to resources can be digitally signed by the entity making the request, such that the source can be verified and an authorization determination made for each tag. For a request involving multiple services (or entities) that can each add tags, any tag added by a service can be included in the request and digitally signed by that service. Each service processing the request can also digitally sign the request before forwarding, so that each service signs a version of the request, which includes elements signed by other services earlier in the request chain. When the request is received to a tagging service, the service ensures that every tag was digitally signed by the appropriate authorized entity or service, and validates the signatures to ensure that no data was modified or omitted, before adding the tags to the designated resource(s).

Abstract: Transitive restrictions can be applied to requests received on a session. A session token can be issued for an active session, and a transitivity setting specified to indicate the types of requests for which the transitive restriction is to be enforced. This can include enforcing the restriction on requests received from outside a trusted environment, requests within a scope of enforcement, or enforcing the restriction at request authentication. Any request received from an untrusted source that fails to satisfy the transitive restriction will be denied. Requests from inside the trusted environment may not have the transitive restriction enforced, such as where a new token is issued. This enables services within the environment to make calls on behalf of the customer, while ensuring that third parties obtaining the session token cannot successfully initiate such calls.

Abstract: A request to add tags (e.g., labels, key-value pairs, or metadata) to resources can be digitally signed by the entity making the request, such that the source can be verified and an authorization determination made for each tag. For a request involving multiple services (or entities) that can each add tags, any tag added by a service can be included in the request and digitally signed by that service. Each service processing the request can also digitally sign the request before forwarding, so that each service signs a version of the request, which includes elements signed by other services earlier in the request chain. When the request is received to a tagging service, the service ensures that every tag was digitally signed by the appropriate authorized entity or service, and validates the signatures to ensure that no data was modified or omitted, before adding the tags to the designated resource(s).

Abstract: Security credentials issued by an entity, such as an identity broker, can have a limited lifetime. Access to resources or content under those credentials then can only be obtained for a limited period of time, limiting the ability of an unauthorized entity obtaining the credentials to utilize those credentials for access. Along with the credentials, a refresh token can be issued to a requesting client that can enable the limited lifetime of the credentials to be renewed up to a maximum lifetime of the credentials and/or the token. A service providing access can determine that the client has a valid copy of the refresh token when the credentials are about to expire, and if so can cause the lifetime of the credentials to be extended another credential lifetime. This renewal can be done transparent to a user and without again contacting the identity broker.

Abstract: Security credentials issued by an entity, such as an identity broker, can have a limited lifetime. Access to resources or content under those credentials then can only be obtained for a limited period of time, limiting the ability of an unauthorized entity obtaining the credentials to utilize those credentials for access. Along with the credentials, a refresh token can be issued to a requesting client that can enable the limited lifetime of the credentials to be renewed up to a maximum lifetime of the credentials and/or the token. A service providing access can determine that the client has a valid copy of the refresh token when the credentials are about to expire, and if so can cause the lifetime of the credentials to be extended another credential lifetime. This renewal can be done transparent to a user and without again contacting the identity broker.

Abstract: A request to add tags (e.g., labels, key-value pairs, or metadata) to resources can be digitally signed by the entity making the request, such that the source can be verified and an authorization determination made for each tag. For a request involving multiple services (or entities) that can each add tags, any tag added by a service can be included in the request and digitally signed by that service. Each service processing the request can also digitally sign the request before forwarding, so that each service signs a version of the request, which includes elements signed by other services earlier in the request chain. When the request is received to a tagging service, the service ensures that every tag was digitally signed by the appropriate authorized entity or service, and validates the signatures to ensure that no data was modified or omitted, before adding the tags to the designated resource(s).

Abstract: A load balancing service receives a request from a customer to configure a load balancer for distributing incoming requests to one or more computing resources of the customer. The load balancing service uses configuration information specified in the request to configure the load balancer such that the load balancer, in response to an incoming request, can determine whether the incoming request satisfies a set of request processing rules usable to determine whether the request is to be transmitted to any computing resource of the one or more computing resources. The load balancer transmits the incoming request to a computing resource of the customer as a result of the rules being satisfied.

Abstract: Security credentials issued by an entity, such as an identity broker, can have a limited lifetime. Access to resources or content under those credentials then can only be obtained for a limited period of time, limiting the ability of an unauthorized entity obtaining the credentials to utilize those credentials for access. Along with the credentials, a refresh token can be issued to a requesting client that can enable the limited lifetime of the credentials to be renewed up to a maximum lifetime of the credentials and/or the token. A service providing access can determine that the client has a valid copy of the refresh token when the credentials are about to expire, and if so can cause the lifetime of the credentials to be extended another credential lifetime. This renewal can be done transparent to a user and without again contacting the identity broker.

Abstract: A request to add tags (e.g., labels, key-value pairs, or metadata) to resources can be digitally signed by the entity making the request, such that the source can be verified and an authorization determination made for each tag. For a request involving multiple services (or entities) that can each add tags, any tag added by a service can be included in the request and digitally signed by that service. Each service processing the request can also digitally sign the request before forwarding, so that each service signs a version of the request, which includes elements signed by other services earlier in the request chain. When the request is received to a tagging service, the service ensures that every tag was digitally signed by the appropriate authorized entity or service, and validates the signatures to ensure that no data was modified or omitted, before adding the tags to the designated resource(s).

Abstract: Embodiments are directed towards determining an overall success of a plurality of features and recommending a subset of those features to a user for generating new content. For each feature that is associated with content, an overall success may be determined based on a success of each of a plurality of content that the feature is associated. A subset of the features may be displayed to the user—from which the user can select features to utilize for generating the new content. Based on the features selected by the user, the displayed features may be dynamically updated to include one or more recommended features. A feature may be recommended to the user based on a combination of the overall success of each selected feature and the overall success of each recommended feature. The selected features may be utilized to create the new content.

Abstract: Embodiments are directed towards personalizing content to be provided to a user. A recommendation score may be determined for a piece of content for a user. The recommendation score may be based on a combination of an intrinsic value and/or a social value of the content to the user. The social value may be calculated based on a combination of an individual social value for each of the user's friends, which may be determined based on the combination of a social weight, an interest probability, and a recommendation score for the friend. Online personalization of content for a user may provide the user with the tools to be a valuable, appreciated member of the user's social network. By employing embodiments, as described herein, content may be determined and provided to a user, which may help the user gain the attention of their social circles.

Abstract: Embodiments are directed towards modifying when to publish content to a channel for distribution based on monitored actions associated with previously published content. A plurality of publishing slots may be determined from a plurality of time slots. Each publishing slot may indicate a time to publish content to the channel. Content may be published to the channel at each of the plurality of publishing slots. User actions associated with the published content may be monitored. The plurality of publishing slots may be ranked based on these monitored actions. At least one of the plurality of publishing slots may be modified to a different time slot based on the rankings of the publishing slots. The publication of content at a publishing slot may be delayed based on a success of other content published at a previous publishing slot being above a threshold.

Abstract: Embodiments are directed towards personalizing content to be provided to a user. A recommendation score may be determined for a piece of content for a user. The recommendation score may be based on a combination of an intrinsic value and/or a social value of the content to the user. The social value may be calculated based on a combination of an individual social value for each of the user's friends, which may be determined based on the combination of a social weight, an interest probability, and a recommendation score for the friend. Online personalization of content for a user may provide the user with the tools to be a valuable, appreciated member of the user's social network. By employing embodiments, as described herein, content may be determined and provided to a user, which may help the user gain the attention of their social circles.

Abstract: Embodiments are directed towards modifying when to publish content to a channel for distribution based on monitored actions associated with previously published content. A plurality of publishing slots may be determined from a plurality of time slots. Each publishing slot may indicate a time to publish content to the channel. Content may be published to the channel at each of the plurality of publishing slots. User actions associated with the published content may be monitored. The plurality of publishing slots may be ranked based on these monitored actions. At least one of the plurality of publishing slots may be modified to a different time slot based on the rankings of the publishing slots. The publication of content at a publishing slot may be delayed based on a success of other content published at a previous publishing slot being above a threshold.

Abstract: Embodiments are directed towards modifying when to publish content to a channel for distribution based on monitored actions associated with previously published content. A plurality of publishing slots may be determined from a plurality of time slots. Each publishing slot may indicate a time to publish content to the channel. Content may be published to the channel at each of the plurality of publishing slots. User actions associated with the published content may be monitored. The plurality of publishing slots may be ranked based on these monitored actions. At least one of the plurality of publishing slots may be modified to a different time slot based on the rankings of the publishing slots. The publication of content at a publishing slot may be delayed based on a success of other content published at a previous publishing slot being above a threshold.

Abstract: Embodiments are directed towards personalizing content to be provided to a user. A recommendation score may be determined for a piece of content for a user. The recommendation score may be based on a combination of an intrinsic value and/or a social value of the content to the user. The social value may be calculated based on a combination of an individual social value for each of the user's friends, which may be determined based on the combination of a social weight, an interest probability, and a recommendation score for the friend. Online personalization of content for a user may provide the user with the tools to be a valuable, appreciated member of the user's social network. By employing embodiments, as described herein, content may be determined and provided to a user, which may help the user gain the attention of their social circles.

Abstract: Embodiments are directed towards dynamically managing contextual recommendations that can be employed with content when provided to a channel. A test for a variable having at least two outcomes may be determined to be employed with selected content. Each outcome may correspond to a different contextual recommendation. An outcome to employ with the content may be randomly determined/selected such that each of the outcomes of the test is selected a substantially similar number of times. The content may be modified and/or provided to the channel based on contextual recommendations that correspond to the determined outcome. Actions associated with a plurality of content may be monitored and/or analyzed to determine metrics for each outcome of a test. A comparison of the metrics for each outcome may be utilized to determine a preferred outcome for the test.

Abstract: Embodiments are directed towards dynamically managing a plurality of channels for providing content to users. New channels may be automatically generated based on sub-interest groups of existing channels, which may generate a hierarchy of channels, where new content may be posted and/or provided to the new channel, and/or a parent channel. The new channel may be proposed to a user, that accesses content on a channel, to invite the user to subscribe to the new channel. The proposed channel may be determined based on a weight of channels associated with the accessed content. Similarly, a proposed channel may be provided to a publisher for new content based on the weight of channels associated with the new content. Channels may be discontinued if a value of the channel falls below a predetermined threshold. Channels with overlapping characteristics may be merged together if the overlapping channels satisfy merging criteria.