![]() In case of failure, there is sufficient capacity to enable traffic to be load-balanced to the remaining sites.Ĭustomers are responsible for implementing contingency planning, training and testing for their systems hosted on AWS. All data centres are online and serving traffic. Components (N) have at least one independent backup component. Each data centre is built to physical, environmental, and security standards in an active-active configuration, employing an n+1 redundancy model, ensuring system availability in the event of component failure. This approach ensures that AWS performs system recovery and reconstitution efforts in a methodical sequence, maximizing the effectiveness of the recovery and reconstitution efforts and minimizing system outage time due to errors and omissions.ĪWS maintains a ubiquitous security control environment across all regions. AWS has developed a three-phased approach: Activation and Notification Phase, Recovery Phase, and Reconstitution Phase. The following are the available attributes and sample return values.įor more information about using the Fn::GetAtt intrinsic function, see Fn::GetAtt.The AWS Business Continuity plan details the process that AWS follows in the case of an outage, from detection to deactivation. The Fn::GetAtt intrinsic function returns a value for a specified attribute of this type. Update requires: No interruption Return values Fn::GetAtt The IAM role that studio users assume when logging in to the Nimble Studio portal. The name of the studio, as included in the URL when accessing it in the Nimble Studio portal.Īn array of key-value pairs to apply to this resource. Update requires: No interruption StudioName Update requires: No interruption StudioEncryptionConfigurationĬonfiguration of the encryption method that is used for the studio. Update requires: No interruption DisplayName The IAM role that studio admins assume when logging in to the Nimble Studio portal. ![]() To declare this entity in your AWS CloudFormation template, use the following syntax: If you delete the studio AWS Key Management Service key, your studio will no ![]() If you delete this grant, the studio will no longer be accessible to your When providing anĪWS Key Management Service key during studio creation, Amazon Nimble Studio creates AWS Key Management Service grants in yourĪccount to provide your studio user and admin roles access to these AWS Key Management Service keys. You may provide your own AWS Key Management Service key when callingĬreateStudio to encrypt this data using a key that you own and manage. ![]() Initialization scripts, and other data you provide are always encrypted at rest using anĪWS Key Management Service key. In Nimble Studio, resource names, descriptions, You can optionally specify an AWS Key Management Service key in the The Admin Role must have the AmazonNimbleStudio-StudioAdmin managed policyĪttached for the portal to function properly. The user role must have theĪmazonNimbleStudio-StudioUser managed policy attached for the portal to function These roles are assumed by your users when they log in to the Amazon Nimble Studio portal. When creating a studio, two IAM roles must be provided: the admin role and the user InĪmazon Nimble Studio, all other resources are contained in The AWS::NimbleStudio::Studio resource creates a new studio resource.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |