World Resiliency is a brand new Amazon Lex functionality that allows close to real-time replication of your Amazon Lex V2 bots in a second AWS Area. If you activate this characteristic, all sources, variations, and aliases related after activation might be synchronized throughout the chosen Areas. With World Resiliency, the replicated bot sources and aliases within the second Area can have the identical identifiers as these within the supply Area. This consistency means that you can seamlessly route site visitors to any Area by merely altering the Area identifier, offering uninterrupted service availability. Within the occasion of a Regional outage or disruption, you possibly can swiftly redirect your bot site visitors to a special Area. Functions now have the flexibility to make use of replicated Amazon Lex bots throughout Areas in an active-active or active-passive method for improved availability and resiliency. With World Resiliency, you now not must manually handle separate bots throughout Areas, as a result of the characteristic routinely replicates and retains Regional configurations in sync. With just some clicks or instructions, you acquire strong Amazon Lex bot replication capabilities. Functions which can be utilizing Amazon Lex bots can now fail over from an impaired Area seamlessly, minimizing the chance of expensive downtime and sustaining enterprise continuity. This characteristic streamlines the method of sustaining strong and extremely out there conversational purposes. These embody interactive voice response (IVR) methods, chatbots for digital channels, and messaging platforms, offering a seamless and resilient buyer expertise.
On this publish, we stroll you thru enabling World Resiliency for a pattern Amazon Lex V2 bot. We showcase the replication technique of bot variations and aliases throughout a number of Areas. Moreover, we talk about the best way to deal with integrations with AWS Lambda and Amazon CloudWatch after enabling World Resiliency.
Resolution overview
For this train, we create a BookHotel bot as our pattern bot. We use an AWS CloudFormation template to construct this bot, together with defining intents, slots, and different required parts corresponding to a model and alias. All through our demonstration, we use the us-east-1 Area because the supply Area, and we replicate the bot within the us-west-2 Area, which serves because the duplicate Area. We then replicate this bot, allow logging, and combine it with a Lambda perform.
To higher perceive the answer, discuss with the next structure diagram.
- Enabling World Resiliency for an Amazon Lex bot is easy utilizing the AWS Administration Console, AWS Command Line Interface (AWS CLI), or APIs. We stroll by way of the directions to copy the bot later on this publish.
- After replication is efficiently enabled, the bot might be replicated throughout Areas, offering a unified expertise. This lets you distribute IVR or chat software requests between Areas in both an active-active or active-passive setup, relying in your use case.
- A key advantage of World Resiliency is that builders can repeatedly work on bot enhancements within the supply Area, and modifications are routinely synchronized to the duplicate Area. This streamlines the event workflow with out compromising resiliency.
On the time of writing, World Resiliency solely works with predetermined pairs of Areas. For extra info, see Use World Resiliency to deploy bots to different Areas.
Stipulations
It is best to have the next stipulations:
- An AWS account with administrator entry
- Entry to Amazon Lex World Resiliency (contact your Amazon Join Options Architect or Technical Account Supervisor)
- Working information of the next companies:
- AWS CloudFormation
- Amazon CloudWatch
- AWS Lambda
- Amazon Lex
Create a pattern Amazon Lex bot
To arrange a pattern bot for our use case, discuss with Handle your Amazon Lex bot through AWS CloudFormation templates. For this instance, we create a bot named BookHotel within the supply Area (us-east-1). Full the next steps:
- Obtain the CloudFormation template and deploy it within the supply Area (
us-east-1). For directions, see Create a stack from the CloudFormation console.
Upon profitable deployment, the BookHotel bot might be created within the supply Area.
- On the Amazon Lex console, select Bots within the navigation pane and find the BookHotel.
Confirm that the World Resiliency possibility is offered beneath Deployment within the navigation pane. If this selection isn’t seen, the World Resiliency characteristic will not be enabled on your account. On this case, discuss with the stipulations part for enabling the World Resiliency characteristic.
Our pattern BookHotel bot has one model (Model 1, along with the draft model) and an alias named BookHotelDemoAlias (along with the TestBotAlias).
Allow World Resiliency
To activate World Resiliency and arrange bot replication in a duplicate Area, full the next steps:
- On the Amazon Lex console, select
us-east-1as your Area. - Select Bots within the navigation pane and find the BookHotel.
- Beneath Deployment within the navigation pane, select World Resiliency.
You’ll be able to see the replication particulars right here. Since you haven’t enabled World Resiliency but, all the small print are clean.
- Select Create duplicate to create a draft model of your bot.
In your supply Area (us-east-1), after the bot replication is full, you will notice Replication standing as Enabled.
- Swap to the duplicate Area (
us-west-2).
You’ll be able to see that the BookHotel bot is replicated. It is a read-only duplicate and the bot ID within the duplicate Area matches the bot ID within the supply Area.
- Beneath Deployment within the navigation pane, select World Resiliency.
You’ll be able to see the replication particulars right here, that are the identical as that within the supply Area BookHotel bot.
You have got verified that the bot is replicated efficiently after World Resiliency is enabled. Solely new variations and aliases created from this level onward might be replicated. As a subsequent step, we create a bot model and alias to display the replication.
Create a brand new bot model and alias
Full the next steps to create a brand new bot model and alias:
- On the Amazon Lex console in your supply Area (
us-east-1), navigate to the BookHotel. - Select Bot variations within the navigation pane, and select Create new model to create Model 2.
Model 2 now has World Resiliency enabled, whereas Model 1 and the draft model don’t, as a result of they had been created previous to enabling World Resiliency.
- Select Aliases within the navigation pane, then select Create new alias.
- Create a brand new alias for the BookHotel bot known as
BookHotelDemoAlias_GRand level that to the brand new model.
Equally, the BookHotelDemoAlias_GR now has World Resiliency enabled, whereas aliases created earlier than enabling World Resiliency, corresponding to BookHotelDemoAlias and TestBotAlias, don’t have World Resiliency enabled.
- Select World Resiliency within the navigation pane to view the supply and replication particulars.
The main points for Final replicated model at the moment are up to date to Model 2.
- Swap to the duplicate Area (
us-west-2) and select World Resiliency within the navigation pane.
You’ll be able to see that the brand new World Resiliency enabled model (Model 2) is replicated and the brand new alias BookHotelDemoAlias_GR can be current.
You have got verified that the brand new model and alias had been created after World Resiliency is replicated to the duplicate Area. Now you can make Amazon Lex runtime calls to each Areas.
Dealing with integrations with Lambda and CloudWatch after enabling World Resiliency
Amazon Lex has integrations with different AWS companies corresponding to enabling customized logic with Lambda features and logging with dialog logs utilizing CloudWatch and Amazon Easy Storage Service (Amazon S3). On this part, we affiliate a Lambda perform and CloudWatch group for the BookHotel bot within the supply Area (us-east-1) and validate its affiliation within the duplicate Area (us-west-2).
- Obtain the CloudFormation template to deploy a pattern Lambda and CloudWatch log group.
- Deploy the CloudFormation stack to the supply Area (
us-east-1). For directions, see Create a stack from the CloudFormation console.
It will deploy a Lambda perform (book-hotel-lambda) and a CloudWatch log group (/lex/book-hotel-bot) within the us-east-1 Area.
- Deploy the CloudFormation stack to the duplicate Area (
us-west-2).
It will deploy a Lambda perform (book-hotel-lambda) and a CloudWatch log group (/lex/book-hotel-bot) within the us-west-2 Area. The Lambda perform identify and CloudWatch log group identify should be the identical in each Areas.
- On the Amazon Lex console within the supply Area (
us-east-1), navigate to the BookHotel. - Select Aliases within the navigation pane, and select the
BookHotelDemoAlias_GR. - Within the Languages part, select English (US).
- Choose the
book-hotel-lambdaperform and affiliate it with the BookHotel bot by selecting Save. - Navigate again to the
BookHotelDemoAlias_GRalias, and within the Dialog logs part, select Handle dialog logs. - Allow Textual content logs and choose the
/lex/book-hotel-bot loggroup, then select Save.
Dialog textual content logs at the moment are enabled for the BookHotel bot in us-east-1.
- Swap to the duplicate Area (
us-west-2) and navigate to the BookHotel. - Select Aliases within the navigation pane, and select the
BookHotelDemoAlias_GR.
You’ll be able to see that the dialog logs are already related to the /lex/book-hotel-bot CloudWatch group the us-west-2 Area.
- Within the Languages part, select English (US).
You’ll be able to see that the book-hotel-lambda perform is related to the BookHotel alias.
By way of this course of, we’ve got demonstrated how Lambda features and CloudWatch log teams are routinely related to the corresponding bot sources within the duplicate Area for the replicated bots, offering a seamless and constant integration throughout each Areas.
Disabling World Resiliency
You have got the flexibleness to disable World Resiliency at any time. By disabling World Resiliency, your supply bot, together with its related aliases and variations, will now not be replicated throughout different Areas. On this part, we display the method to disable World Resiliency.
- On the Amazon Lex console in your supply Area (
us-east-1), select Bots within the navigation pane and find the BookHotel. - Beneath Deployment within the navigation pane, select World Resiliency.
- Select Disable World Resiliency.
- Enter affirm within the affirmation field and select Delete.
This motion initiates the deletion of the replicated BookHotel bot within the duplicate Area.
The replication standing will change to Deleting, and after a couple of minutes, the deletion course of might be full. You’ll then see the Create duplicate possibility out there once more. In the event you don’t see it, strive refreshing the web page.
- Verify the Bot variations web page of the BookHotel bot to verify that Model 2 remains to be the most recent model.
- Verify the Aliases web page to verify that the
BookHotelDemoAlias_GRalias remains to be current on the supply bot.
Functions referring to this alias can proceed to perform as regular within the supply Area.
- Swap to the duplicate Area (
us-west-2) to verify that the BookHotel bot has been deleted from this Area.
You’ll be able to reenable World Resiliency on the supply Area (us-east-1) by going by way of the method described earlier on this publish.
Clear up
To stop incurring prices, full the next steps to wash up the sources created throughout this demonstration:
- Disable World Resiliency for the bot by following the directions detailed earlier on this publish.
- Delete the
book-hotel-lambda-cw-stackCloudFormation stack from theus-west-2. For directions, see Delete a stack on the CloudFormation console. - Delete the
book-hotel-lambda-cw-stackCloudFormation stack from theus-east-1. - Delete the
book-hotel-stackCloudFormation stack from theus-east-1.
Integrations with Amazon Join
Amazon Lex World Resiliency seamlessly enhances Amazon Join World Resiliency, offering you with a complete answer for sustaining enterprise continuity and resilience throughout your conversational AI and get in touch with heart infrastructure. Amazon Join World Resiliency lets you routinely keep your situations synchronized throughout two Areas, ensuring that each one configuration sources, corresponding to contact flows, queues, and brokers, are true replicas of one another.
With the addition of Amazon Lex World Resiliency, Amazon Join clients acquire the additional benefit of automated synchronization of their Amazon Lex V2 bots related to their contact flows. This integration supplies a constant and uninterrupted expertise throughout failover situations, as a result of your Amazon Lex interactions seamlessly transition between Areas with none disruption. By combining these complementary options, you possibly can obtain end-to-end resilience. This minimizes the chance of downtime and makes certain your conversational AI and get in touch with heart operations stay extremely out there and responsive, even within the case of Regional failures or capability constraints.
World Resiliency APIs
World Resiliency supplies API assist to create and handle replicas. These are supported within the AWS CLI and AWS SDKs. On this part, we display utilization with the AWS CLI.
- Create a bot duplicate within the duplicate Area utilizing the CreateBotReplica.
- Monitor the bot replication standing utilizing the DescribeBotReplica.
- Checklist the replicated bots utilizing the ListBotReplicas.
- Checklist all of the model replication statuses relevant for World Resiliency utilizing the ListBotVersionReplicas.
This checklist consists of solely the replicated bot variations, which had been created after World Resiliency was enabled. Within the API response, a botVersionReplicationStatus of Out there signifies that the bot model was replicated efficiently.
- Checklist all of the alias replication statuses relevant for World Resiliency utilizing the ListBotAliasReplicas.
This checklist consists of solely the replicated bot aliases, which had been created after World Resiliency was enabled. Within the API response, a botAliasReplicationStatus of Out there signifies that the bot alias was replicated efficiently.
Conclusion
On this publish, we launched the World Resiliency characteristic for Amazon Lex V2 bots. We mentioned the method to allow World Resiliency utilizing the console and reviewed among the new APIs launched as a part of this characteristic.
As the following step, you possibly can discover World Resiliency and apply the methods mentioned on this publish to copy bots and bot variations throughout Areas. This hands-on observe will solidify your understanding of managing and replicating Amazon Lex V2 bots in your answer structure.
In regards to the Authors
Priti Aryamane is a Specialty Advisor at AWS Skilled Companies. With over 15 years of expertise involved facilities and telecommunications, Priti makes a speciality of serving to clients obtain their desired enterprise outcomes with buyer expertise on AWS utilizing Amazon Lex, Amazon Join, and generative AI options.
Sanjeet Sanda is a Specialty Advisor at AWS Skilled Companies with over 20 years of expertise in telecommunications, contact heart expertise, and buyer expertise. He makes a speciality of designing and delivering customer-centric options with a deal with integrating and adapting present enterprise name facilities into Amazon Join and Amazon Lex environments. Sanjeet is captivated with streamlining adoption processes by utilizing automation wherever doable. Outdoors of labor, Sanjeet enjoys hanging out together with his household, having barbecues, and going to the seaside.
Yogesh Khemka is a Senior Software program Growth Engineer at AWS, the place he works on giant language fashions and pure language processing. He focuses on constructing methods and tooling for scalable distributed deep studying coaching and real-time inference.
