This message was deleted.
# awss
sparse-intern-71089
02/10/2023, 2:53 PMThis message was deleted.
b
billowy-army-68599
02/10/2023, 2:55 PM
AWS classic is our recommended provider for AWS at this stage
f
faint-balloon-33174
02/10/2023, 2:56 PMBecause it is more stable?
b
billowy-army-68599
02/10/2023, 3:05 PM
at this stage yes, we expect that to change as time goes on. In any case, but will be supported fully
f
faint-balloon-33174
02/10/2023, 3:06 PMDo you think there might come a time when it is recommended over classic? Would it be a bad idea for me to use it for less critical features to future-proof them?
b
billowy-army-68599
02/10/2023, 3:10 PM
you don’t really need to future proof, but we’ll recommend native over classic when the resource footprint is higher
billowy-army-68599
02/10/2023, 3:10 PM
anything you implment in classic will be supported fully, so no future proofing required
f
faint-balloon-33174
02/10/2023, 3:11 PMOk great, thank you!
m
melodic-tomato-39005
02/10/2023, 3:13 PMAgree with @billowy-army-68599, and want to add some points:
• Native is stable enough to use, that’s not a problem
• Native is built on Cloud Control which is “the future” and allows us to autogenerate it. However, not all AWS services and resources are modeled in CC yet, which is one major reason our native provider isn’t GA yet.