Name of the resource
AWS::DMS::Endpoint
Resource name
No response
Description
In preparation for an ongoing replication project (SQL Server on RDS to SQL Server on EC2), I'm reviewing the following documentation:
- (DMS user guide) Using a Microsoft SQL Server database as a source for AWS DMS
- (DMS user guide) Using a Microsoft SQL Server database as a target for AWS Database Migration Service
- (CFN user guide) AWS::DMS::Endpoint - particularly the
ExtraConnectionAttributes property
- (CFN user guide) AWS::DMS::Endpoint MicrosoftSqlServerSettings
The first 2 links, from the DMS User Guide, refer to some settings as "Endpoint settings" and others as "extra connection attributes". Likewise, the AWS::DMS::Endpoint resource includes both a MicrosoftSqlServerSettings property (presumably corresponding to "Endpoint settings" and an ExtraConnectionAttributes property (clearly corresponding to "extra connection attributes").
So far, so good! But when I start digging into the details of particular settings and attributes, things get confusing ...
- At link #1, several configs are listed both in a table inventorying "Endpoint settings" and in a table inventorying "extra connection attributes", making it unclear which CFN resource property should be used to specify them. None of these are referenced in CFN docs (i.e. link #3 and link #4). Does this mean they aren't yet covered by CFN?
ActivateSafeguard
AlwaysOnSharedSynchedBackupIsEnabled
ApplicationIntent
MultiSubnetFailover
SetUpMsCdcForTables
- Several other configs listed in tables inventorying "Endpoint settings" (both at link #1 and link #2) are referred to as "extra connection attributes" in bulleted lists of limitations on the same respective pages. In these cases, the configs are referenced at link #4 - seemingly validating that they are more likely "Endpoint settings" than "extra connection attributes" ...
UseBcpFullLoad (target)
ReadBackupOnly (source)
Use3rdPartyBackupDevice (source)
- Speaking of
Use3rdPartyBackupDevice (source), link #4 indicates it was implemented in CFN with a variation on the name (UseThirdPartyBackupDevice). That seems like either a needless trap, or a documentation error on one side or the other.
- Several configs are listed only as "Endpoint settings" at link #1, but aren't mentioned in link #4. Does this mean they aren't yet covered by CFN?
EnableNonSysadminWrapper
FatalOnSimpleModel
ForceLobLookup
TlogAccessMode
- A handful of configs are mentioned in link #4, but at neither link #1 nor link #2. Does that mean they've been deprecated? Probably not, in the case of the latter two, but I'm less clear on the former two. If they remain supported, it would be nice to mention them somewhere in the DMS User Guide ...
BcpPacketSize
QuerySingleAlwaysOnNode
SecretsManagerAccessRoleArn
SecretsManagerSecretId
- On the bright side, I did find 2 config values where the docs all seem aligned. In both cases, they are only ever referred to as "Endpoint Settings" by link #1 and link #2, and they are listed at link #4 ...
SafeguardPolicy (source)
ControlTablesFileGroup (target)
Other Details
No response
Name of the resource
AWS::DMS::Endpoint
Resource name
No response
Description
In preparation for an ongoing replication project (SQL Server on RDS to SQL Server on EC2), I'm reviewing the following documentation:
ExtraConnectionAttributespropertyThe first 2 links, from the DMS User Guide, refer to some settings as "Endpoint settings" and others as "extra connection attributes". Likewise, the
AWS::DMS::Endpointresource includes both aMicrosoftSqlServerSettingsproperty (presumably corresponding to "Endpoint settings" and anExtraConnectionAttributesproperty (clearly corresponding to "extra connection attributes").So far, so good! But when I start digging into the details of particular settings and attributes, things get confusing ...
ActivateSafeguardAlwaysOnSharedSynchedBackupIsEnabledApplicationIntentMultiSubnetFailoverSetUpMsCdcForTablesUseBcpFullLoad(target)ReadBackupOnly(source)Use3rdPartyBackupDevice(source)Use3rdPartyBackupDevice(source), link #4 indicates it was implemented in CFN with a variation on the name (UseThirdPartyBackupDevice). That seems like either a needless trap, or a documentation error on one side or the other.EnableNonSysadminWrapperFatalOnSimpleModelForceLobLookupTlogAccessModeBcpPacketSizeQuerySingleAlwaysOnNodeSecretsManagerAccessRoleArnSecretsManagerSecretIdSafeguardPolicy(source)ControlTablesFileGroup(target)Other Details
No response