Amazon Simple Notification Service (SNS) is a highly available, durable, secure, fully managed pub/sub messaging service that enables you to decouple microservices, distributed systems, and serverless applications. Amazon SNS provides topics for high-throughput, push-based, many-to-many messaging. Using Amazon SNS topics, your publisher systems can fan out messages to a large number of subscriber endpoints for parallel processing, including Amazon SQS queues, AWS Lambda functions, and HTTP/S webhooks. Additionally, SNS can be used to fan out notifications to end users using mobile push, SMS, and email. You can get started with Amazon SNS in minutes by using the AWS Management Console, AWS Command Line Interface (CLI), or AWS Software Development Kit (SDK). FEATURES: Event Sources and Destinations Event-driven computing is a model in which subscriber services automatically perform work in response to events triggered by publisher services. This paradigm can be applied to automate workflows while decoupling the services that collectively and independently work to fulfil these workflows. Amazon SNS is an event-driven computing hub that has native integration with a wide variety of AWS event sources (including Amazon EC2, Amazon S3, and Amazon RDS) and AWS event destinations (including Amazon SQS, and Lambda). The full set of Amazon SNS event sources includes the following services:

• Compute: Amazon EC2 Auto Scaling, AWS Elastic Beanstalk, AWS Lambda, Elastic Load Balancing
• Storage: Amazon Elastic File System, Amazon Glacier, Amazon Simple Storage Service, AWS Snowball
• Database: Amazon DynamoDB, Amazon ElastiCache, Amazon Redshift, Amazon Relational Database Service, AWS Database Migration Service
• Networking: Amazon Route 53, Amazon VPC, AWS Direct Connect
• Developer Tools: AWS CodeBuild, AWS CodeCommit, AWS CodeDeploy, AWS CodePipeline
• Management Tools: Amazon CloudWatch Alarms, Amazon CloudWatch Events, AWS CloudFormation, AWS CloudTrail, AWS Config
• Customer Engagement: Amazon Pinpoint, Amazon Simple Email Service
• Analytics: AWS Data Pipeline
• Security, Identity and Compliance: Amazon Inspector
• Media: Amazon Elastic Transcoder
• Internet of Things: AWS IoT

Amazon SNS can filter and fanout events to the following destinations to support event-driven computing use cases:

• Amazon Simple Queue Service
• AWS Lambda
• Webhook (HTTP/S)

Message Filtering Message filtering empowers the subscriber to create a filter policy so that it only gets the notifications it is interested in, as opposed to receiving every single message posted to the topic. Additionally, you may monitor your Amazon SNS message filtering activity with Amazon CloudWatch and manage Amazon SNS filter policies with AWS CloudFormation. Message Fanout Message fanout occurs when a message is sent to a topic and then replicated and pushed to multiple endpoints. Fanout provides asynchronous event notifications, which in turn allows for parallel processing. Message Encryption Amazon SNS provides encrypted topics to protect your messages from unauthorized and anonymous access. When you publish messages to encrypted topics, Amazon SNS immediately encrypts your messages. The encryption takes place on the server, using a 256-bit AES-GCM algorithm and a customer master key (CMK) issued with AWS Key Management Service (KMS). The messages are stored in encrypted form and decrypted as they are delivered to subscribing endpoints (Amazon SQS queues, AWS Lambda functions, HTTP/S webhooks). Message Privacy Amazon SNS supports VPC Endpoints (VPCE) via AWS PrivateLink. You can use VPC Endpoints to privately publish messages to Amazon SNS topics, from an Amazon Virtual Private Cloud (VPC), without traversing the public internet. This feature brings additional security, helps promote data privacy, and aligns with assurance programs. When you use AWS PrivateLink, you don’t need to set up an Internet Gateway (IGW), Network Address Translation (NAT) device, or Virtual Private Network (VPN) connection. You don’t need to use public IP addresses, either. Mobile Notifications Amazon SNS mobile notifications make it simple and cost-effective to fanout mobile push notifications to iOS, Android, Fire OS, Windows and Baidu-based devices. You can also use SNS to fanout text messages (SMS) to 200+ countries and fanout email messages (SMTP). Alternatively, if your use case can benefit from advanced user engagement and retention features such as mobile notification templates, delivery schedules, targeted customer segments, campaigns, analytics, and A/B testing, then Amazon Pinpoint is the recommended AWS service to support your mobile messaging use case. BENEFITS: Reliably deliver messages with durability Amazon SNS uses cross availability zone message storage to provide high message durability. Running within Amazon’s proven network infrastructure and datacenters, Amazon SNS topics are available whenever your applications need them. All messages published to Amazon SNS are stored redundantly across multiple geographically separated servers and data centers. Amazon SNS reliably delivers messages to all valid AWS endpoints, such as Amazon SQS queues and AWS Lambda functions. Automatically scale your workload Amazon SNS leverages the proven AWS cloud to dynamically scale with your application. Amazon SNS is a fully managed service, taking care of the heavy lifting related to capacity planning, provisioning, monitoring, and patching. The service is designed to handle high-throughput, bursty traffic patterns. Moreover, there is no upfront cost, and no need to acquire, install, configure, or upgrade messaging software. Simplify your architecture with Message Filtering Amazon SNS helps you simplify your pub/sub messaging architecture by offloading the message filtering logic from your subscriber systems, and message routing logic from your publisher systems. With Amazon SNS message filtering, subscribing endpoints receive only the messages of interest, instead of all messages published to the topic. Amazon CloudWatch gives visibility into your filtering activity, and AWS CloudFormation enables you to deploy subscription filter policies in an automated and secure manner. Keep messages private and secure Amazon SNS topic owners can keep sensitive data secure by setting topic policies that restrict who can publish and subscribe to a topic. Amazon SNS also ensures that data is encrypted in transit by applying Amazon ATS certificates to support its HTTPS API, and can also encrypt data at rest by using AWS KMS keys. Additionally, using AWS PrivateLink, you can privately publish messages to Amazon SNS topics from your Amazon VPC subnets without traversing the public Internet. Amazon SNS can also support use cases in regulated markets, and is in-scope with compliance programs, including HIPAA, PCI, ISO, FIPS, SOC and FedRAMP.

Amazon Simple Queue Service (SQS) is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. SQS eliminates the complexity and overhead associated with managing and operating message oriented middleware, and empowers developers to focus on differentiating work. Using SQS, you can send, store, and receive messages between software components at any volume, without losing messages or requiring other services to be available. Get started with SQS in minutes using the AWS console, Command Line Interface or SDK of your choice, and three simple commands. SQS offers two types of message queues. Standard queues offer maximum throughput, best-effort ordering, and at-least-once delivery. SQS FIFO queues are designed to guarantee that messages are processed exactly once, in the exact order that they are sent. FEATURES: Queue types Amazon SQS offers two queue types for different application requirements: Standard Queues Unlimited Throughput: Standard queues support a nearly unlimited number of transactions per second (TPS) per API action. At-Least-Once Delivery: A message is delivered at least once, but occasionally more than one copy of a message is delivered. Best-Effort Ordering: Occasionally, messages might be delivered in an order different from which they were sent. You can use standard message queues in many scenarios, as long as your application can process messages that arrive more than once and out of order, for example:

• Decouple live user requests from intensive background work: Let users upload media while resizing or encoding it.
• Allocate tasks to multiple worker nodes: Process a high number of credit card validation requests.
• Batch messages for future processing: Schedule multiple entries to be added to a database.

FIFO Queues High Throughput: By default, FIFO queues support up to 300 messages per second (300 send, receive, or delete operations per second). When you batch 10 messages per operation (maximum), FIFO queues can support up to 3,000 messages per second. Exactly-Once Processing: A message is delivered once and remains available until a consumer processes and deletes it. Duplicates aren't introduced into the queue. First-In-First-Out Delivery: The order in which messages are sent and received is strictly preserved (i.e. First-In-First-Out). FIFO queues are designed to enhance messaging between applications when the order of operations and events is critical, or where duplicates can't be tolerated, for example:

• Ensure that user-entered commands are executed in the right order.
• Display the correct product price by sending price modifications in the right order.
• Prevent a student from enrolling in a course before registering for an account.

Functionality

• Unlimited queues and messages: Create unlimited Amazon SQS queues with an unlimited number of message in any region
• Payload Size: Message payloads can contain up to 256KB of text in any format. Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests. To send messages larger than 256KB, you can use the Amazon SQS Extended Client Library for Java, which uses Amazon S3 to store the message payload. A reference to the message payload is sent using SQS.
• Batches: Send, receive, or delete messages in batches of up to 10 messages or 256KB. Batches cost the same amount as single messages, meaning SQS can be even more cost effective for customers that use batching.
• Long polling: Reduce extraneous polling to minimize cost while receiving new messages as quickly as possible. When your queue is empty, long-poll requests wait up to 20 seconds for the next message to arrive. Long poll requests cost the same amount as regular requests.
• Retain messages in queues for up to 14 days.
• Send and read messages simultaneously.
• Message locking: When a message is received, it becomes “locked” while being processed. This keeps other computers from processing the message simultaneously. If the message processing fails, the lock will expire and the message will be available again.
• Queue sharing: Securely share Amazon SQS queues anonymously or with specific AWS accounts. Queue sharing can also be restricted by IP address and time-of-day.
• Server-side encryption (SSE): Protect the contents of messages in Amazon SQS queues using keys managed in the AWS Key Management Service (AWS KMS). SSE encrypts messages as soon as Amazon SQS receives them. The messages are stored in encrypted form and Amazon SQS decrypts messages only when they are sent to an authorized consumer.
• Dead Letter Queues (DLQ): Handle messages that have not been successfully processed by a consumer with Dead Letter Queues. When the maximum receive count is exceeded for a message it will be moved to the DLQ associated with the original queue. Set up separate consumer processes for DLQs which can help analyze and understand why messages are getting stuck. DLQs must be of the same type as the source queue (standard or FIFO).

Using Amazon SQS with other AWS infrastructure web services Amazon SQS message queuing can be used with other AWS Services such as Redshift, DynamoDB, RDS, EC2, ECS, Lambda, and S3, to make distributed applications more scalable and reliable. Below are some common design patterns:

• Work Queues: Decouple components of a distributed application that may not all process the same amount of work simultaneously.
• Buffer and Batch Operations: Add scalability and reliability to your architecture, and smooth out temporary volume spikes without losing messages or increasing latency.
• Request Offloading: Move slow operations off of interactive request paths by enqueing the request.
• Fanout: Combine SQS with Simple Notification Service (SNS) to send identical copies of a message to multiple queues in parallel.
• Priority: Use separate queues to provide prioritization of work.
• Scalability: Because message queues decouple your processes, it’s easy to scale up the send or receive rate of messages - simply add another process.
• Resiliency: When part of your system fails, it doesn’t need to take the entire system down. Message queues decouple components of your system, so if a process that is reading messages from the queue fails, messages can still be added to the queue to be processed when the system recovers.

PRICING:

• Pay only for what you use
• No minimum fee

Amazon SQS Free Tier You can get started with Amazon SQS for free. All customers can make 1 million Amazon SQS requests for free each month. Some applications might be able to operate within this Free Tier limit. How are Amazon SQS requests priced? The first 1 million monthly requests are free. After that, the pricing is as follows for all regions: Price per 1 Million Requests after Free Tier (Monthly)

• Standard Queue $0.40 ($0.00000040 per request)
• FIFO Queue $0.50 ($0.00000050 per request)

How are Amazon SQS charges metered? API Actions. Every Amazon SQS action counts as a request. FIFO Requests. API actions for sending, receiving, deleting, and changing visibility of messages from FIFO queues are charged at FIFO rates.  All other API requests are charged at standard rates. Contents of Requests. A single request can have from 1 to 10 messages, up to a maximum total payload of 256 KB. Size of Payloads. Each 64 KB chunk of a payload is billed as 1 request (for example, an API action with a 256 KB payload is billed as 4 requests). Interaction with Amazon S3. When using the Amazon SQS Extended Client Library to send payloads using Amazon S3, you incur Amazon S3 charges for any Amazon S3 storage you use to send message payloads.
Interaction with AWS KMS. When using the AWS Key Management Service to manage keys for SQS server-side encryption, you incur charges for calls from Amazon SQS to AWS KMS. BENEFITS: Eliminate Administrative Overhead AWS manages all ongoing operations and underlying infrastructure needed to provide a highly available and scalable message queuing service. With SQS, there is no upfront cost, no need to acquire, install, and configure messaging software, and no time-consuming build-out and maintenance of supporting infrastructure. SQS queues are dynamically created and scale automatically so you can build and grow applications quickly and efficiently. Reliably Deliver Messages Use Amazon SQS to transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be available. SQS lets you decouple application components so that they run and fail independently, increasing the overall fault tolerance of the system. Multiple copies of every message are stored redundantly across multiple availability zones so that they are available whenever needed. Keep Sensitive Data Secure You can use Amazon SQS to exchange sensitive data between applications using server-side encryption (SSE) to encrypt each message body. Amazon SQS SSE integration with AWS Key Management Service (KMS) allows you to centrally manage the keys that protect SQS messages along with keys that protect your other AWS resources. AWS KMS logs every use of your encryption keys to AWS CloudTrail to help meet your regulatory and compliance needs. Scale Elastically and Cost-Effectively Amazon SQS leverages the AWS cloud to dynamically scale based on demand. SQS scales elastically with your application so you don’t have to worry about capacity planning and pre-provisioning. There is no limit to the number of messages per queue, and standard queues provide nearly unlimited throughput. Costs are based on usage which provides significant cost saving versus the “always-on” model of self-managed messaging middleware.

Kerio Connect - кроссплатформенный почтовый сервер с улучшенной поддержкой мобильных устройств.

Почтовый сервер Kerio Connect предоставляет такие функции как электронная почта бизнес-класса, мгновенные сообщения с групповым чатом, делегирование доступа к почте и календарю, управление общими календарями и контактами в большинстве почтовых клиентов, клиентов мгновенных сообщений, браузеров и мобильных устройств с минимальными затратами.

 

Kerio Connect включает все, что нужно для безопасной работы с почтой: интегрированный антивирус, мощный анти-спам, встроенную, система архивации, автоматическое резервное копирование, и удобный интерфейс администрирования.Все это - в одном продукте за небольшую цену. 

Kerio Connect можно интегрировать практически в любую ИТ-инфраструктуру, благодаря возможности развертывания на различных платформах: Windows, Linux, Mac OS X, VMware а также в "облаке".

Work smarter, anywhere Microsoft Exchange lets you accomplish more with a rich, business-class email experience on phones, tablets, desktops, and the web. Enjoy enterprise email capabilities with bigger and more reliable mailboxes Experience better collaboration with document sharing Add enhanced archiving, security, and compliance features Exchange Online Exchange is available as a standalone hosted service from Microsoft. You can also get Exchange as part of an Office 365 plan that includes Office apps, SharePoint, and Skype for Business. Exchange Server 2016 Increase productivity and keep your business information safe, while maintaining the control you need. Other Exchange products Exchange Online Archiving Exchange Online Protection Office 365 Advanced Threat Protection Exchange Online Kiosk Exchange for government agencies

Функции omChat®

На веб-сайте компании клиенты могут общаться с Виртуальным агентом каждый раз, когда у них возникают трудности с навигацией или по требованию, для улучшения удобства пользователей.

omChat® можно легко интегрировать со многими поставщиками инфраструктуры агента-чата, чтобы при необходимости передать разговор живому агенту.

С omChat® предприятие также может открыть Facebook Messenger в качестве прямого канала связи с клиентами и обеспечить, чтобы они получали тот же отличный опыт общения, что и на любом другом канале.