We are building IVR based application where user can talk to voice bot to get his query resolved. as our Team decided to go with amazon connect and amazon lex to build this application.
But our client is from saudi arabia region and we are not sure that does it work In there region.
Please help.
Please find below the list of region Lex is available,
http://docs.aws.amazon.com/lex/latest/dg/API_Reference.html
and list of region-specific services - https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/
Still, you can connect to API of the available region and can pass date of the time zone you want to use.
To set the time zone used to resolve dates so that it is relative to the user's time zone, use the x-amz-lex:time-zone request attribute. If you do not specify a time zone in the x-amz-lex:time-zone attribute, the default is America/New York.
Related
I need to setup a shared processing service that uses a load balancer and several EC2 instances to process incoming requests using a custom .NET application. My issue is that I need to be able to bill based on usage. Only white-listed IPs will be able to call the application, but each IP only gets a set number of calls before each call is a billable event.
Since the AWS documentation for the ELB states "We recommend that you use access logs to understand the nature of the requests, not as a complete accounting of all requests", I do not feel the Access Logs on the ELB is what I'm looking for.
The question I have is how to best manage this so that the accounting team has an easy report each month that says how many calls each client made.
Actually you can use Access logs and since access logs will be written to S3, you can query each IP with Athena by using standard SQL. You can analyze your logs and extract reports.
References:
https://docs.aws.amazon.com/athena/latest/ug/what-is.html
https://aws.amazon.com/premiumsupport/knowledge-center/athena-analyze-access-logs/
I came across the following question during my AWS practice and I have a different opinion and want to post it here for more discussion as it addresses a very common need, thanks.
http://jayendrapatil.com/aws-rds-replication-multi-az-read-replica/?unapproved=227863&moderation-hash=c9a071a3758c183b1cf03e51c44d2373#comment-227863
Your company has HQ in Tokyo and branch offices all over the world and is using logistics software with a multi-regional deployment on AWS in Japan, Europe and US. The logistic software has a 3-tier architecture and currently uses MySQL 5.6 for data persistence. Each region has deployed its own database. In the HQ region you run an hourly batch process reading data from every region to compute cross-regional reports that are sent by email to all offices this batch process must be completed as fast as possible to quickly optimize logistics. How do you build the database architecture in order to meet the requirements?
A. For each regional deployment, use RDS MySQL with a master in the region and a read replica in the HQ region
B. For each regional deployment, use MySQL on EC2 with a master in the region and send hourly EBS snapshots to the HQ region
C. For each regional deployment, use RDS MySQL with a master in the region and send hourly RDS snapshots to the HQ region
D. For each regional deployment, use MySQL on EC2 with a master in the region and use S3 to copy data files hourly to the HQ region
E. Use Direct Connect to connect all regional MySQL deployments to the HQ region and reduce network latency for the batch process
I lean to E, the reason is:
Direct Connect provides bandwidth that bypasses the ISP and more privately, faster (if needed).
The question doesn't factor cost here.
The initial setup time could be longer comparing to other options, however, initial setup time cost should not be the point here, what is asking here is “this batch process must be completed as fast as possible to quickly optimize logistics.”, so it is not about the initial setup, it is about how to implement the right solution to deliver the “as fast as possible” service AFTER the setup
And hence I believe E is the best option for the need.
I am open to discussion, please, if my understanding is wrong. Thank you.
E is not applicable. You cannot use Direct Connect to connect 2 VPCs. Direct Connect is used to connect VPC and your premise. Question asks about multi-regional AWS infrastructure without mentioning anything about HQ not being hosted on AWS.
The easiest solution is A in my opinion.
I purchased a reserved instance in Singapore region on April 17 2017. The instance is going to expire on April 11 2018. Is there any way to renew the my reserved instance before expiration.
From AWS portal we'll get to know only this..
It’s not currently possible to schedule an EC2 Reserved Instance to auto-renew, or to purchase Reserved Instances in advance. Reserved Instances are active as soon as they’re successfully purchased.
To view your active Reserved Instances and see when they expire, check the Amazon EC2 console.
Note: Reserved Instances apply to a specific region, so make sure to check all regions where you have created Reserved Instances.
Although the reservation must be manually renewed, from May 2019 you can be alerted by email prior to reservation expiry using the cost explorer tool.
Here is an excerpt from this aws announcement:
To turn on reservation expiration alerts, navigate to the Reservation Summary page, locate the reservation expiration Key Performance Indicator (KPI) in the top right corner, and click on the “Manage alerts” link. From there, simply indicate when you would like to receive reservation expiration alerts, and AWS will begin monitoring your reservation portfolio and automatically send you alerts. Reservation expiration alerts are supported for Amazon EC2, Amazon RDS, Amazon Redshift, Amazon ElastiCache, and Amazon Elasticsearch reservations.
I'm looking for a way to pick the best AWS region to host a Proof of Concept installation for a potential customer in India.
For this, I'd like to try to ping the customer's web site (I verified that it's hosted in India, I assume by the customer itself since that's part of their business) from multiple AWS regions and see which one gives best results.
I found multiple tools which would allow me to run ping from my own browser to multiple AWS locations (e.g. https://cloudharmony.com/speedtest, http://www.cloudping.info/) but none which will allow me to ping between all AWS regions and a specific third party.
Does such a tool exist, or is my only option to run up an EC2 instance in each region and try to ping from it?
You might want to check the answers to this very similar question.
Keep in mind that not all regions have all AWS services available at this time, so make sure the region you pick has all the services that you plan to use. Also, Amazon has said that an India region is in the works.
I tried to install Restcomm for VoIP Innovations on AWS using the default setup but it didn't work.
This is the error message:
Your recent Restcomm for VoIP Innovations launch failed. Your requested instance type (m1.large) is not supported in your requested Availability Zone (us-east-1e). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1c, us-east-1b. (Service: AmazonEC2; Status Code: 400; Error Code: Unsupported; Request ID: 9654025e-42e7-402f-93f7-969d2eb04845)
I tried small/medium too, with no luck :(
Any clue on how to force it on 1a/B/C rather than 1e?
Thanks!
Sorry that you are having problems with using Restcomm on Amazon Cloud. When you purchase Restcomm, you are only presented with the default Region, which is US East (N. Virginia). Depending on the type of setup you use (One-click or custom) you should be able to configure the instance as needed. It is also possible to start the instance using the EC2 console by searching for the AMI in the Region mentioned above.
When you launch the instance, you will be able to configure the subnet and security groups that will allow you to successfully use Restcomm. Here is a screenshot showing you how to choose the appropriate subnet. If you are not familiar with Restcomm, I suggest you leave this as default so that you can concentrate on familiarizing yourself with the platform.
The screenshot shows the default settings.