Ecosyste.ms: Packages

An open API service providing package, version and dependency metadata of many open source software ecosystems and registries.

Top 1.7% on proxy.golang.org
Top 3.7% dependent packages on proxy.golang.org
Top 1.0% dependent repos on proxy.golang.org
Top 1.2% forks on proxy.golang.org
Top 1.1% docker downloads on proxy.golang.org

proxy.golang.org : github.com/aws/aws-sdk-go-v2/service/ivschat

Package ivschat provides the API client, operations, and parameter types for Amazon Interactive Video Service Chat. The Amazon IVS Chat control-plane API enables you to create and manage Amazon IVS Chat resources. You also need to integrate with the Amazon IVS Chat Messaging API, to enable users to interact with chat rooms in real time. The API is an AWS regional service. For a list of supported regions and Amazon IVS Chat HTTPS service endpoints, see the Amazon IVS Chat information on the Amazon IVS pagein the AWS General Reference. Notes on terminology: You create service applications using the Amazon IVS Chat API. We refer to these as applications. You create front-end client applications (browser and Android/iOS apps) using the Amazon IVS Chat Messaging API. We refer to these as clients. Key Concepts LoggingConfiguration — A configuration that allows customers to store and record sent messages in a chat room. Room — The central Amazon IVS Chat resource through which clients connect to and exchange chat messages. A tag is a metadata label that you assign to an AWS resource. A tag comprises a key and a value, both set by you. For example, you might set a tag as topic:nature to label a particular video category. See Tagging AWS Resources for more information, including restrictions that apply to tags and "Tag naming limits and requirements"; Amazon IVS Chat has no service-specific constraints beyond what is documented there. Tags can help you identify and organize your AWS resources. For example, you can use the same tag for different resources to indicate that they are related. You can also use tags to manage access (see Access Tags). The Amazon IVS Chat API has these tag-related endpoints: TagResource, UntagResource, and ListTagsForResource. The following resource supports tagging: Room. At most 50 tags can be applied to a resource. Your Amazon IVS Chat applications (service applications and clients) must be authenticated and authorized to access Amazon IVS Chat resources. Note the differences between these concepts: Authentication is about verifying identity. Requests to the Amazon IVS Chat API must be signed to verify your identity. Authorization is about granting permissions. Your IAM roles need to have permissions for Amazon IVS Chat API requests. Users (viewers) connect to a room using secure access tokens that you create using the CreateChatTokenendpoint through the AWS SDK. You call CreateChatToken for every user’s chat session, passing identity and authorization information about the user. HTTP API requests must be signed with an AWS SigV4 signature using your AWS security credentials. The AWS Command Line Interface (CLI) and the AWS SDKs take care of signing the underlying API calls for you. However, if your application calls the Amazon IVS Chat HTTP API directly, it’s your responsibility to sign the requests. You generate a signature using valid AWS credentials for an IAM role that has permission to perform the requested action. For example, DeleteMessage requests must be made using an IAM role that has the ivschat:DeleteMessage permission. For more information: Authentication and generating signatures — See Authenticating Requests (Amazon Web Services Signature Version 4)in the Amazon Web Services General Reference. Managing Amazon IVS permissions — See Identity and Access Managementon the Security page of the Amazon IVS User Guide. Amazon Resource Names (ARNs) ARNs uniquely identify AWS resources. An ARN is required when you need to specify a resource unambiguously across all of AWS, such as in IAM policies and API calls. For more information, see Amazon Resource Namesin the AWS General Reference. DeleteMessage DisconnectUser SendEvent CreateChatToken CreateRoom DeleteRoom GetRoom ListRooms UpdateRoom CreateLoggingConfiguration DeleteLoggingConfiguration GetLoggingConfiguration ListLoggingConfigurations UpdateLoggingConfiguration ListTagsForResource TagResource UntagResource All the above are HTTP operations. There is a separate messaging API for managing Chat resources; see the Amazon IVS Chat Messaging API Reference.

Registry - Source - Documentation - JSON
purl: pkg:golang/github.com/aws/aws-sdk-go-v2/service/ivschat
Keywords: aws, aws-sdk, go, golang
License: Apache-2.0
Latest release: 4 months ago
First release: about 2 years ago
Namespace: github.com/aws/aws-sdk-go-v2/service
Dependent packages: 6
Dependent repositories: 30
Stars: 2,407 on GitHub
Forks: 587 on GitHub
Docker dependents: 54
Docker downloads: 22,610
Total Commits: 2384
Committers: 101
Average commits per author: 23.604
Development Distribution Score (DDS): 0.573
More commit stats: commits.ecosyste.ms
See more repository details: repos.ecosyste.ms
Last synced: about 3 hours ago

    Loading...
    Readme
    Loading...